Remove unnecessary doc locales

Change-Id: Id2f101783973dd935b41403442f1f78533d7ac73
This commit is contained in:
Vladimir Kozhukalov 2023-10-18 20:28:07 -05:00
parent 82a6aa8ce9
commit 5500b2ae0b
25 changed files with 1 additions and 21131 deletions

View File

@ -1,958 +0,0 @@
# Andreas Jaeger <jaegerandi@gmail.com>, 2018. #zanata
# Frank Kloeker <eumel@arcor.de>, 2018. #zanata
msgid ""
msgstr ""
"Project-Id-Version: openstack-helm 0.1.1.dev3631\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2022-02-23 21:11+0000\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"PO-Revision-Date: 2018-10-25 07:38+0000\n"
"Last-Translator: Andreas Jaeger <jaegerandi@gmail.com>\n"
"Language-Team: German\n"
"Language: de\n"
"Plural-Forms: nplurals=2; plural=(n != 1)\n"
"X-Generator: Zanata 4.3.3\n"
msgid ""
"**Note:** The values defined in a PodDisruptionBudget may conflict with "
"other values that have been provided if an operator chooses to leverage "
"Rolling Updates for deployments. In the case where an operator defines a "
"``maxUnavailable`` and ``maxSurge`` within an update strategy that is higher "
"than a ``minAvailable`` within a pod disruption budget, a scenario may occur "
"where pods fail to be evicted from a deployment."
msgstr ""
"**Hinweis:** Die in einem PodDisruptionBudget definierten Werte können zu "
"Konflikten mit anderen Werten führen, die bereitgestellt wurden, wenn ein "
"Benutzer sich für die Verwendung von Rolling Updates für Bereitstellungen "
"entscheidet. In dem Fall, in dem ein Operator ein ``maxUnavailable`` und ein "
"``maxSurge`` innerhalb einer Aktualisierungsstrategie definiert, die höher "
"als ein ``minAvailable`` innerhalb eines Pod-Unterbrechungsbudgets ist, kann "
"ein Szenario auftreten, bei dem die Pods nicht entfernt werden eine "
"Bereitstellung"
msgid ""
":code:`neutron/templates/bin/_neutron-linuxbridge-agent-init.sh.tpl` is "
"configuring the tunnel IP, external bridge and all bridge mappings defined "
"in config. It is done in init container, and the IP for tunneling is shared "
"using file :code:`/tmp/pod-shared/ml2-local-ip.ini` with main linuxbridge "
"container."
msgstr ""
":code:`neutron/templates/bin/_neutron-linuxbridge-agent-init.sh.tpl` "
"konfiguriert die Tunnel-IP, die externe Bridge und alle in config "
"definierten bridge-Mappings. Es wird im init-Container gemacht, und die IP "
"für das Tunneln wird unter Verwendung der Datei :code:`/tmp/pod-shared/ml2-"
"local-ip.ini` mit dem Haupt-linuxbridge-Container geteilt."
msgid ""
"A detail worth mentioning is that ovs is configured to use sockets, rather "
"than the default loopback mechanism."
msgstr ""
"Ein erwähnenswertes Detail ist, dass ovs so konfiguriert ist, dass es "
"Sockets anstelle des Standard-Loopback-Mechanismus verwendet."
msgid ""
"A long-term goal, besides being image agnostic, is to also be able to "
"support any of the container runtimes that Kubernetes supports, even those "
"that might not use Docker's own packaging format. This will allow the "
"project to continue to offer maximum flexibility with regard to operator "
"choice."
msgstr ""
"Ein langfristiges Ziel ist es, nicht nur abbildunabhängig zu sein, sondern "
"auch alle Containerlaufzeiten unterstützen zu können, die von Kubernetes "
"unterstützt werden, auch solche, die nicht das eigene Packungsformat von "
"Docker verwenden. Auf diese Weise kann das Projekt weiterhin maximale "
"Flexibilität hinsichtlich der Betreiberauswahl bieten."
msgid ""
"All ``Deployment`` chart components are outfitted by default with rolling "
"update strategies:"
msgstr ""
"Alle ``Deployment``-Chart-Komponenten sind standardmäßig mit rollierenden "
"Update-Strategien ausgestattet:"
msgid "All dependencies described in neutron-dhcp-agent are valid here."
msgstr "Alle in neutron-dhcp-agent beschriebenen Abhängigkeiten gelten hier."
msgid ""
"All of the above configs are endpoints or path to the specific class "
"implementing the interface. You can see the endpoints to class mapping in "
"`setup.cfg <https://github.com/openstack/neutron/"
"blob/412c49b3930ce8aecb0a07aec50a9607058e5bc7/setup.cfg#L69>`_."
msgstr ""
"Alle oben genannten Konfigurationen sind Endpunkte oder Pfade zu der "
"spezifischen Klasse, die die Schnittstelle implementiert. Sie können die "
"Endpunkte für die Klassenzuordnung in `setup.cfg sehen <https://github.com/"
"openstack/neutron/blob/412c49b3930ce8aecb0a07aec50a9607058e5bc7/setup."
"cfg#L69>`_."
msgid ""
"An illustrative example of an ``images:`` section taken from the heat chart:"
msgstr ""
"Ein anschauliches Beispiel für einen ``images:``-Abschnitt aus dem Heat-"
"Chart:"
msgid ""
"Another place where the DHCP agent is dependent on L2 agent is the "
"dependency for the L2 agent daemonset:"
msgstr ""
"Ein anderer Ort, an dem der DHCP-Agent vom L2-Agenten abhängig ist, ist die "
"Abhängigkeit für den L2-Agent-Daemonset:"
msgid ""
"As part of Neutron chart, this daemonset is running Neutron OVS agent. It is "
"dependent on having :code:`openvswitch-db` and :code:`openvswitch-vswitchd` "
"deployed and ready. Since its the default choice of the networking backend, "
"all configuration is in place in `neutron/values.yaml`. :code:`neutron-ovs-"
"agent` should not be deployed when another SDN is used in `network.backend`."
msgstr ""
"Als Teil des Neutron-Charts wird in diesem Daemonset der Neutronen-OVS-Agent "
"ausgeführt. Es ist abhängig von :code:`openvswitch-db` und :code:"
"`openvswitch-vswitchd` bereitgestellt und bereit. Da es die Standardauswahl "
"des Netzwerk-Backends ist, ist die gesamte Konfiguration in `neutron/values."
"yaml` vorhanden. :code:`neutron-ovs-agent` sollte nicht eingesetzt werden, "
"wenn ein anderes SDN in` network.backend` verwendet wird."
msgid ""
"By default, each endpoint is located in the same namespace as the current "
"service's helm chart. To connect to a service which is running in a "
"different Kubernetes namespace, a ``namespace`` can be provided for each "
"individual endpoint."
msgstr ""
"Standardmäßig befindet sich jeder Endpunkt im selben Namespace wie das "
"Steuerdiagramm des aktuellen Dienstes. Um eine Verbindung zu einem Dienst "
"herzustellen, der in einem anderen Kubernetes-Namespace ausgeführt wird, "
"kann für jeden einzelnen Endpunkt ein ``Namespace`` bereitgestellt werden."
msgid ""
"Charts should not use hard coded values such as ``http://keystone-api:5000`` "
"because these are not compatible with operator overrides and do not support "
"spreading components out over various namespaces."
msgstr ""
"Charts sollten keine fest codierten Werte wie ``http://keystone-api:5000`` "
"verwenden, da diese nicht mit Operator-Überschreibungen kompatibel sind und "
"keine Verteilung von Komponenten über verschiedene Namespaces unterstützen."
msgid ""
"Configure neutron-server with SDN specific core_plugin/mechanism_drivers."
msgstr ""
"Konfigurieren Sie den Neutronenserver mit SDN-spezifischen core_plugin/"
"mechanism_drivers."
msgid "Configuring network plugin"
msgstr "Netzwerk-Plugin konfigurieren"
msgid "Contents:"
msgstr "Inhalt:"
msgid "Create separate chart with new SDN deployment method."
msgstr ""
"Erstellen Sie ein separates Chart mit der neuen SDN-Bereitstellungsmethode."
msgid ""
"Currently OpenStack-Helm supports OpenVSwitch and LinuxBridge as a network "
"virtualization engines. In order to support many possible backends (SDNs), "
"modular architecture of Neutron chart was developed. OpenStack-Helm can "
"support every SDN solution that has Neutron plugin, either core_plugin or "
"mechanism_driver."
msgstr ""
"Derzeit unterstützt OpenStack-Helm OpenVSwitch und LinuxBridge als Netzwerk-"
"Virtualisierungs-Engines. Um viele mögliche Backends (SDNs) zu unterstützen, "
"wurde die modulare Architektur des Neutronendiagramms entwickelt. OpenStack-"
"Helm kann jede SDN-Lösung unterstützen, die über das Neutron-Plugin "
"core_plugin oder mechanism_driver verfügt."
msgid "DHCP - auto-assign IP address and DNS info"
msgstr "DHCP - Automatische Zuweisung von IP-Adresse und DNS-Informationen"
msgid ""
"DHCP agent is running dnsmasq process which is serving the IP assignment and "
"DNS info. DHCP agent is dependent on the L2 agent wiring the interface. So "
"one should be aware that when changing the L2 agent, it also needs to be "
"changed in the DHCP agent. The configuration of the DHCP agent includes "
"option `interface_driver`, which will instruct how the tap interface created "
"for serving the request should be wired."
msgstr ""
"Der DHCP-Agent führt den dnsmasq-Prozess aus, der die IP-Zuweisung und DNS-"
"Informationen bereitstellt. Der DHCP-Agent ist abhängig vom L2-Agenten, der "
"die Schnittstelle verkabelt. Daher sollte man sich bewusst sein, dass beim "
"Ändern des L2-Agenten auch der DHCP-Agent geändert werden muss. Die "
"Konfiguration des DHCP-Agenten enthält die Option `interface_driver`, die "
"anweist, wie die Tap-Schnittstelle, die zum Versorgen der Anfrage erstellt "
"wurde, verdrahtet sein sollte."
msgid "Developer References"
msgstr "Entwicklerreferenzen"
msgid ""
"EFK (Elasticsearch, Fluent-bit & Fluentd, Kibana) based Logging Mechanism"
msgstr ""
"EFK (Elasticsearch, Fluent-Bit & Fluentd, Kibana) basierte Logging "
"Mechanismus"
msgid "Endpoints"
msgstr "Endpunkte"
msgid ""
"Fluent-bit, Fluentd meet OpenStack-Helm's logging requirements for "
"gathering, aggregating, and delivering of logged events. Fluent-bit runs as "
"a daemonset on each node and mounts the `/var/lib/docker/containers` "
"directory. The Docker container runtime engine directs events posted to "
"stdout and stderr to this directory on the host. Fluent-bit then forward the "
"contents of that directory to Fluentd. Fluentd runs as deployment at the "
"designated nodes and expose service for Fluent-bit to forward logs. Fluentd "
"should then apply the Logstash format to the logs. Fluentd can also write "
"kubernetes and OpenStack metadata to the logs. Fluentd will then forward the "
"results to Elasticsearch and to optionally Kafka. Elasticsearch indexes the "
"logs in a logstash-* index by default. Kafka stores the logs in a ``logs`` "
"topic by default. Any external tool can then consume the ``logs`` topic."
msgstr ""
"Fluent-Bit, Fluentd erfüllt die Protokollierungsanforderungen von OpenStack-"
"Helm zum Sammeln, Aggregieren und Liefern protokollierter Ereignisse. Fluent-"
"Bit wird auf jedem Knoten als Daemonset ausgeführt und lädt das Verzeichnis /"
"var/lib/docker/containers. Die Docker-Container-Laufzeit-Engine leitet "
"Ereignisse, die an stdout und stderr gesendet wurden, in dieses Verzeichnis "
"auf dem Host. Fluent-Bit leitet dann den Inhalt dieses Verzeichnisses an "
"Fluentd weiter. Fluentd wird als Bereitstellung an den angegebenen Knoten "
"ausgeführt und stellt den Dienst für Fluent-Bit für die Weiterleitung von "
"Protokollen bereit. Fluentd sollte dann das Logstash-Format auf die "
"Protokolle anwenden. Fluentd kann auch Kubernetes und OpenStack-Metadaten in "
"die Protokolle schreiben. Fluentd wird die Ergebnisse dann an Elasticsearch "
"und optional an Kafka weiterleiten. Elasticsearch indexiert standardmäßig "
"die Logs in einem logstash-Index*. Kafka speichert die Logs standardmäßig in "
"einem ``logs``-Thema. Jedes externe Tool kann dann das ``logs``-Thema "
"konsumieren."
msgid ""
"For instance, in the Neutron chart ``values.yaml`` the following endpoints "
"are defined:"
msgstr ""
"Zum Beispiel sind im Neutron-Chart ``values.yaml`` die folgenden Endpunkte "
"definiert:"
msgid "Host overrides supercede label overrides"
msgstr "Der Host überschreibt Supercede-Label-Overrides"
msgid ""
"If :code:`.Values.manifests.daemonset_ovs_agent` will be set to false, "
"neutron ovs agent would not be launched. In that matter, other type of L2 or "
"L3 agent on compute node can be run."
msgstr ""
"Wenn :code:`.Values.manifests.daemonset_ovs_agent auf false gesetzt wird, "
"wird der neutron ovs-Agent nicht gestartet. In diesem Fall kann ein anderer "
"Typ von L2- oder L3-Agenten auf dem Rechenknoten ausgeführt werden."
msgid "If required, add new networking agent label type."
msgstr ""
"Fügen Sie bei Bedarf einen neuen Label-Typ für den Netzwerkagenten hinzu."
msgid ""
"If the SDN implements its own version of L3 networking, neutron-l3-agent "
"should not be started."
msgstr ""
"Wenn das SDN eine eigene Version des L3-Netzwerkes implementiert, sollte "
"neutron-l3-agent nicht gestartet werden."
msgid ""
"If the SDN of your choice is using the ML2 core plugin, then the extra "
"options in `neutron/ml2/plugins/ml2_conf.ini` should be configured:"
msgstr ""
"Wenn das SDN Ihrer Wahl das ML2 Core-Plugin verwendet, sollten die "
"zusätzlichen Optionen in `neutron/ml2/plugins/ml2_conf.ini` konfiguriert "
"werden:"
msgid "Images"
msgstr "Abbilder"
msgid ""
"In ``values.yaml`` in each chart, the same defaults are supplied in every "
"chart, which allows the operator to override at upgrade or deployment time."
msgstr ""
"In ``values.yaml`` in jedem Chart werden die gleichen Standardwerte in jedem "
"Chart bereitgestellt, wodurch der Bediener beim Upgrade oder bei der "
"Bereitstellung überschreiben kann."
msgid ""
"In order to add support for more SDNs, these steps need to be performed:"
msgstr ""
"Um weitere SDNs zu unterstützen, müssen diese Schritte ausgeführt werden:"
msgid ""
"In order to meet modularity criteria of Neutron chart, section `manifests` "
"in :code:`neutron/values.yaml` contains boolean values describing which "
"Neutron's Kubernetes resources should be deployed:"
msgstr ""
"Um die Modularitätskriterien des Neutron-Chart zu erfüllen, enthält der "
"Abschnitt ``manifests`` in :code:`neutron/values.yaml` boolesche Werte, die "
"beschreiben, welche Kubernetes-Ressourcen von Neutron eingesetzt werden "
"sollten:"
msgid ""
"In order to use linuxbridge in your OpenStack-Helm deployment, you need to "
"label the compute and controller/network nodes with `linuxbridge=enabled` "
"and use this `neutron/values.yaml` override:"
msgstr ""
"Um linuxbridge in Ihrer OpenStack-Helm-Implementierung zu verwenden, müssen "
"Sie die Knoten compute und controller/network mit linuxbridge = enabled "
"kennzeichnen und diese `neutron/values.yaml`-Überschreibung verwenden:"
msgid ""
"Introducing a new SDN solution should consider how the above services are "
"provided. It maybe required to disable built-in Neutron functionality."
msgstr ""
"Die Einführung einer neuen SDN-Lösung sollte überlegen, wie die oben "
"genannten Dienste bereitgestellt werden. Es ist möglicherweise erforderlich, "
"die eingebaute Neutronenfunktionalität zu deaktivieren."
msgid ""
"L3 agent is serving the routing capabilities for Neutron networks. It is "
"also dependent on the L2 agent wiring the tap interface for the routers."
msgstr ""
"Der L3-Agent bedient die Routing-Funktionen für Neutron-Netzwerke. Es hängt "
"auch davon ab, dass der L2-Agent die Abgriffschnittstelle für die Router "
"verkabelt."
msgid "L3 routing - creation of routers"
msgstr "L3 Routing - Erstellung von Routern"
msgid "Linuxbridge"
msgstr "Linuxbridge"
msgid ""
"Linuxbridge is the second type of Neutron reference architecture L2 agent. "
"It is running on nodes labeled `linuxbridge=enabled`. As mentioned before, "
"all nodes that are requiring the L2 services need to be labeled with "
"linuxbridge. This includes both the compute and controller/network nodes. It "
"is not possible to label the same node with both openvswitch and linuxbridge "
"(or any other network virtualization technology) at the same time."
msgstr ""
"Linuxbridge ist der zweite Typ des Neutronen-Referenzarchitektur-L2-Agenten. "
"Es läuft auf Knoten mit der Bezeichnung `linuxbridge = enabled`. Wie bereits "
"erwähnt, müssen alle Knoten, die L2-Dienste benötigen, mit linuxbridge "
"gekennzeichnet werden. Dies umfasst sowohl die Rechner- als auch die "
"Controller-/Netzwerkknoten. Es ist nicht möglich, denselben Knoten "
"gleichzeitig mit openvswitch und linuxbridge (oder einer anderen "
"Netzwerkvirtualisierungstechnologie) zu beschriften."
msgid "Logging Mechanism"
msgstr "Protokollierungsmechanismus"
msgid "Logging Requirements"
msgstr "Protokollierungsanforderungen"
msgid "Metadata - Provide proxy for Nova metadata service"
msgstr "Metadaten - Stellt einen Proxy für den Nova-Metadaten-Service bereit"
msgid ""
"Metadata-agent is a proxy to nova-metadata service. This one provides "
"information about public IP, hostname, ssh keys, and any tenant specific "
"information. The same dependencies apply for metadata as it is for DHCP and "
"L3 agents. Other SDNs may require to force the config driver in nova, since "
"the metadata service is not exposed by it."
msgstr ""
"Der Metadata-Agent ist ein Proxy für den Nova-Metadata-Service. Dieser "
"enthält Informationen zu öffentlichen IP-Adressen, Hostnamen, SSH-Schlüsseln "
"und mandantenspezifischen Informationen. Für Metadaten gelten die gleichen "
"Abhängigkeiten wie für DHCP- und L3-Agenten. Bei anderen SDNs kann es "
"erforderlich sein, den Konfigurationstreiber in Nova zu erzwingen, da der "
"Metadatendienst dadurch nicht verfügbar gemacht wird."
msgid "Networking"
msgstr "Vernetzung"
msgid "Neutron architecture"
msgstr "Neutron-Architektur"
msgid "Neutron chart includes the following services:"
msgstr "Neutronendiagramm beinhaltet folgende Dienste:"
msgid ""
"Neutron-server service is scheduled on nodes with `openstack-control-"
"plane=enabled` label."
msgstr ""
"Der Neutron-Server-Dienst wird auf Knoten mit der Markierung ``openstack-"
"control-plane = enabled`` geplant."
msgid "Note that only one set of overrides is applied per node, such that:"
msgstr ""
"Beachten Sie, dass nur ein Satz von Überschreibungen pro Knoten angewendet "
"wird, so dass:"
msgid ""
"Note that some additional values have been injected into the config file, "
"this is performed via statements in the configmap template, which also calls "
"the ``helm-toolkit.utils.to_oslo_conf`` to convert the yaml to the required "
"layout:"
msgstr ""
"Beachten Sie, dass einige zusätzliche Werte in die Konfigurationsdatei "
"eingefügt wurden. Dies geschieht über Anweisungen in der Vorlage configmap, "
"die auch ``helm-toolkit.utils.to_oslo_conf`` aufrufen, um das yaml in das "
"gewünschte Layout zu konvertieren:"
msgid ""
"Note: Rolling update values can conflict with values defined in each "
"service's PodDisruptionBudget. See `here <https://docs.openstack.org/"
"openstack-helm/latest/devref/pod-disruption-budgets.html>`_ for more "
"information."
msgstr ""
"Hinweis: Rollende Aktualisierungswerte können zu Konflikten mit Werten "
"führen, die im PodDisruptionBudget jedes Service definiert sind. Siehe `hier "
"<https://docs.openstack.org/openstack-helm/latest/devref/pod-disruption-"
"budgets.html>`_ für weitere Informationen."
msgid "Nova config dependency"
msgstr "Nova-Konfigurationsabhängigkeit"
msgid "OSLO-Config Values"
msgstr "OSLO-Config Werte"
msgid ""
"OpenStack-Helm defines a centralized logging mechanism to provide insight "
"into the state of the OpenStack services and infrastructure components as "
"well as underlying Kubernetes platform. Among the requirements for a logging "
"platform, where log data can come from and where log data need to be "
"delivered are very variable. To support various logging scenarios, OpenStack-"
"Helm should provide a flexible mechanism to meet with certain operation "
"needs."
msgstr ""
"OpenStack-Helm definiert einen zentralen Protokollierungsmechanismus, der "
"Einblick in den Status der OpenStack-Services und der "
"Infrastrukturkomponenten sowie der zugrunde liegenden Kubernetes-Plattform "
"gibt. Zu den Anforderungen für eine Protokollierungsplattform, von der "
"Protokolldaten kommen und wo Protokolldaten geliefert werden müssen, gehören "
"sehr unterschiedliche. Um verschiedene Protokollierungsszenarien zu "
"unterstützen, sollte OpenStack-Helm einen flexiblen Mechanismus "
"bereitstellen, um bestimmte Betriebsanforderungen zu erfüllen."
msgid ""
"OpenStack-Helm generates oslo-config compatible formatted configuration "
"files for services dynamically from values specified in a yaml tree. This "
"allows operators to control any and all aspects of an OpenStack services "
"configuration. An example snippet for an imaginary Keystone configuration is "
"described here:"
msgstr ""
"OpenStack-Helm generiert oslo-config-kompatible formatierte "
"Konfigurationsdateien für Dienste dynamisch aus Werten, die in einer Yaml-"
"Struktur angegeben sind. Dies ermöglicht Betreibern, alle Aspekte einer "
"OpenStack-Dienstkonfiguration zu steuern. Ein Beispiel-Snippet für eine "
"imaginäre Keystone-Konfiguration wird hier beschrieben:"
msgid ""
"OpenStack-Helm provides fast and lightweight log forwarder and full featured "
"log aggregator complementing each other providing a flexible and reliable "
"solution. Especially, Fluent-bit is used as a log forwarder and Fluentd is "
"used as a main log aggregator and processor."
msgstr ""
"OpenStack-Helm bietet einen schnellen und leichten Log Forwarder und einen "
"voll funktionsfähigen Log Aggregator, die sich gegenseitig ergänzen und eine "
"flexible und zuverlässige Lösung bieten. Insbesondere wird Fluent-Bit als "
"Protokollweiterleitung und Fluentd als Hauptprotokollaggregator und -"
"prozessor verwendet."
msgid "OpenVSwitch"
msgstr "OpenVSwitch"
msgid "Other SDNs"
msgstr "Andere SDNs"
msgid "Other networking services provided by Neutron are:"
msgstr "Andere Netzwerkdienste von Neutron sind:"
msgid "Pod Disruption Budgets"
msgstr "Pod Disruption Budgets"
msgid ""
"SDNs implementing ML2 driver can add extra/plugin-specific configuration "
"options in `neutron/ml2/plugins/ml2_conf.ini`. Or define its own "
"`ml2_conf_<name>.ini` file where configs specific to the SDN would be placed."
msgstr ""
"SDNs, die ML2-Treiber implementieren, können zusätzliche/pluginspezifische "
"Konfigurationsoptionen in `neutron/ml2/plugins/ml2_conf.ini` hinzufügen. "
"Oder definieren Sie eine eigene `ml2_conf_ <name> .ini` Datei, in der "
"Configs, die für das SDN spezifisch sind, platziert werden."
msgid ""
"Script in :code:`neutron/templates/bin/_neutron-openvswitch-agent-init.sh."
"tpl` is responsible for determining the tunnel interface and its IP for "
"later usage by :code:`neutron-ovs-agent`. The IP is set in init container "
"and shared between init container and main container with :code:`neutron-ovs-"
"agent` via file :code:`/tmp/pod-shared/ml2-local-ip.ini`."
msgstr ""
"Das Skript in :code:`neutron/templates/bin/_neutron-openvswitch-agent-init."
"sh.tpl` ist verantwortlich für die Bestimmung der Tunnelschnittstelle und "
"ihrer IP für die spätere Verwendung durch :code:`neutron-ovs-agent`. Die IP "
"wird im init-Container gesetzt und zwischen dem init-Container und dem Haupt-"
"Container mit folgendem Code geteilt :code:`neutron-ovs-agent` via Datei :"
"code:`/tmp/pod-shared/ml2-local-ip.ini`."
msgid ""
"Specify if new SDN would like to use existing services from Neutron: L3, "
"DHCP, metadata."
msgstr ""
"Geben Sie an, ob ein neues SDN vorhandene Dienste von Neutron verwenden "
"möchte: L3, DHCP, Metadaten."
msgid ""
"The Neutron reference architecture provides mechanism_drivers :code:"
"`OpenVSwitch` (OVS) and :code:`linuxbridge` (LB) with ML2 :code:"
"`core_plugin` framework."
msgstr ""
"Die Neutron-Referenzarchitektur liefert mechanism_drivers :code:"
"`OpenVSwitch` (OVS) und :code:`linuxbridge` (LB) mit ML2 :code:`core_plugin` "
"framework."
msgid ""
"The OpenStack-Helm project also implements annotations across all chart "
"configmaps so that changing resources inside containers, such as "
"configuration files, triggers a Kubernetes rolling update. This means that "
"those resources can be updated without deleting and redeploying the service "
"and can be treated like any other upgrade, such as a container image change."
msgstr ""
"Das OpenStack-Helm-Projekt implementiert auch Anmerkungen über alle "
"Chartkonfigurationen hinweg, sodass das Ändern von Ressourcen in Containern, "
"z.B. Konfigurationsdateien, ein aktualisierendes Kubernetes-Rollup-Update "
"auslöst. Dies bedeutet, dass diese Ressourcen aktualisiert werden können, "
"ohne dass der Service gelöscht und erneut bereitgestellt werden muss. Sie "
"können wie jedes andere Upgrade behandelt werden, z.B. eine Container-Image-"
"Änderung."
msgid ""
"The OpenStack-Helm project assumes all upgrades will be done through Helm. "
"This includes handling several different resource types. First, changes to "
"the Helm chart templates themselves are handled. Second, all of the "
"resources layered on top of the container image, such as ``ConfigMaps`` "
"which includes both scripts and configuration files, are updated during an "
"upgrade. Finally, any image references will result in rolling updates of "
"containers, replacing them with the updating image."
msgstr ""
"Das OpenStack-Helm-Projekt geht davon aus, dass alle Upgrades über Helm "
"erfolgen. Dies umfasst die Behandlung mehrerer verschiedener "
"Ressourcentypen. Zuerst werden Änderungen an den Helmchartvorlagen selbst "
"vorgenommen. Zweitens werden alle Ressourcen, die über dem Container-Image "
"liegen, wie z.B. ``ConfigMaps``, die sowohl Skripts als auch "
"Konfigurationsdateien enthalten, während eines Upgrades aktualisiert. "
"Abschließend führen alle Abbildreferenzen dazu, dass Aktualisierungen von "
"Containern aktualisiert und durch das Update-Image ersetzt werden."
msgid ""
"The OpenStack-Helm project today uses a mix of Docker images from "
"Stackanetes and Kolla, but will likely standardize on a default set of "
"images for all charts without any reliance on image-specific utilities."
msgstr ""
"Das OpenStack-Helm-Projekt verwendet heute eine Mischung aus Docker-Images "
"von Stackanetes und Kolla, standardisiert aber wahrscheinlich einen "
"Standardsatz von Abbildern für alle Charts, ohne auf abbildspezifische "
"Utilities angewiesen zu sein."
msgid ""
"The ``hash`` function defined in the ``helm-toolkit`` chart ensures that any "
"change to any file referenced by configmap-bin.yaml or configmap-etc.yaml "
"results in a new hash, which will then trigger a rolling update."
msgstr ""
"Die im ``helm-toolkit``-Chart definierte ``hash``-Funktion stellt sicher, "
"dass jede Änderung an einer beliebigen Datei, auf die configmap-bin.yaml "
"oder configmap-etc.yaml verweist, zu einem neuen Hash führt, der dann ein "
"Rolling auslöst aktualisieren."
msgid "The above configuration options are handled by `neutron/values.yaml`:"
msgstr ""
"Die obigen Konfigurationsoptionen werden von `neutron/values.yaml` "
"gehandhabt:"
msgid ""
"The farther down the list the label appears, the greater precedence it has. "
"e.g., \"another-label\" overrides will apply to a node containing both "
"labels."
msgstr ""
"Je weiter unten in der Liste das Label erscheint, desto größer ist die "
"Priorität. z.B. ``another-label`` Überschreibungen gelten für einen Knoten, "
"der beide Labels enthält."
msgid ""
"The following standards are in use today, in addition to any components "
"defined by the service itself:"
msgstr ""
"Die folgenden Standards werden heute zusätzlich zu den Komponenten "
"verwendet, die vom Dienst selbst definiert werden:"
msgid ""
"The macros that help translate these into the actual URLs necessary are "
"defined in the ``helm-toolkit`` chart. For instance, the cinder chart "
"defines a ``glance_api_servers`` definition in the ``cinder.conf`` template:"
msgstr ""
"Die Makros, die dabei helfen, diese in die tatsächlich benötigten URLs zu "
"übersetzen, sind im ``helm-toolkit`` Chart definiert. Zum Beispiel definiert "
"das Cinder-Chart eine ``glance_api_servers`` Definition in der `` cinder."
"conf`` Vorlage:"
msgid ""
"The ovs set of daemonsets are running on the node labeled "
"`openvswitch=enabled`. This includes the compute and controller/network "
"nodes. For more flexibility, OpenVSwitch as a tool was split out of Neutron "
"chart, and put in separate chart dedicated OpenVSwitch. Neutron OVS agent "
"remains in Neutron chart. Splitting out the OpenVSwitch creates "
"possibilities to use it with different SDNs, adjusting the configuration "
"accordingly."
msgstr ""
"Die ovs Daemonsets laufen auf dem Knoten `openvswitch = enabled`. Dies "
"umfasst die Rechner- und Controller-/Netzwerkknoten. Für mehr Flexibilität "
"wurde OpenVSwitch als ein Tool aus dem Neutron-Chart herausgenommen und in "
"einen separaten Chart-dedizierten OpenVSwitch gesetzt. Neutron OVS Agent "
"bleibt inm Neutron-Chart. Wenn Sie den OpenVSwitch aufteilen, können Sie ihn "
"mit verschiedenen SDNs verwenden und die Konfiguration entsprechend anpassen."
msgid ""
"The project's core philosophy regarding images is that the toolsets required "
"to enable the OpenStack services should be applied by Kubernetes itself. "
"This requires OpenStack-Helm to develop common and simple scripts with "
"minimal dependencies that can be overlaid on any image that meets the "
"OpenStack core library requirements. The advantage of this is that the "
"project can be image agnostic, allowing operators to use Stackanetes, Kolla, "
"LOCI, or any image flavor and format they choose and they will all function "
"the same."
msgstr ""
"Die Kernphilosophie des Projekts in Bezug auf Abbilder besteht darin, dass "
"die für die Aktivierung der OpenStack-Services erforderlichen Toolsets von "
"Kubernetes selbst angewendet werden sollten. Dies erfordert, dass OpenStack-"
"Helm allgemeine und einfache Skripte mit minimalen Abhängigkeiten "
"entwickelt, die jedem Abbild überlagert werden können, das die Anforderungen "
"der OpenStack-Kernbibliothek erfüllt. Der Vorteil davon ist, dass das "
"Projekt abbbildunabhängig sein kann und es den Betreibern ermöglicht, "
"Stackanetes, Kolla, LOCI oder jedes andere Bildformat und -format zu "
"verwenden, das sie wählen, und sie werden alle gleich funktionieren."
msgid ""
"The project's goal is to provide a consistent mechanism for endpoints. "
"OpenStack is a highly interconnected application, with various components "
"requiring connectivity details to numerous services, including other "
"OpenStack components and infrastructure elements such as databases, queues, "
"and memcached infrastructure. The project's goal is to ensure that it can "
"provide a consistent mechanism for defining these \"endpoints\" across all "
"charts and provide the macros necessary to convert those definitions into "
"usable endpoints. The charts should consistently default to building "
"endpoints that assume the operator is leveraging all charts to build their "
"OpenStack cloud. Endpoints should be configurable if an operator would like "
"a chart to work with their existing infrastructure or run elements in "
"different namespaces."
msgstr ""
"Ziel des Projekts ist es, einen konsistenten Mechanismus für Endpunkte "
"bereitzustellen. OpenStack ist eine stark miteinander verbundene Anwendung, "
"bei der verschiedene Komponenten Konnektivitätsdetails für zahlreiche "
"Dienste benötigen, einschließlich anderer OpenStack-Komponenten und "
"Infrastrukturelemente wie Datenbanken, Warteschlangen und Memcached-"
"Infrastruktur. Ziel des Projekts ist es, sicherzustellen, dass es einen "
"konsistenten Mechanismus für die Definition dieser \"Endpunkte\" in allen "
"Charts bereitstellt und die erforderlichen Makros bereitstellt, um diese "
"Definitionen in nutzbare Endpunkte umzuwandeln. Die Charts sollten "
"konsistent standardmäßig Build-Endpunkte erstellen, die davon ausgehen, dass "
"der Benutzer alle Charts nutzt, um seine OpenStack-Cloud zu erstellen. "
"Endpunkte sollten konfigurierbar sein, wenn ein Operator ein Chart mit der "
"vorhandenen Infrastruktur arbeiten oder Elemente in verschiedenen Namespaces "
"ausführen möchte."
msgid ""
"The resulting logs can then be queried directly through Elasticsearch, or "
"they can be viewed via Kibana. Kibana offers a dashboard that can create "
"custom views on logged events, and Kibana integrates well with Elasticsearch "
"by default."
msgstr ""
"Die resultierenden Protokolle können dann direkt über Elasticsearch "
"abgefragt werden oder über Kibana eingesehen werden. Kibana bietet ein "
"Dashboard, das benutzerdefinierte Ansichten für protokollierte Ereignisse "
"erstellen kann, und Kibana integriert sich standardmäßig gut in "
"Elasticsearch."
msgid ""
"There is also a need for DHCP agent to pass ovs agent config file (in :code:"
"`neutron/templates/bin/_neutron-dhcp-agent.sh.tpl`):"
msgstr ""
"Es ist auch notwendig, dass der DHCP-Agent die Konfigurationsdatei des "
"Agenten übergibt (in :code:`neutron/templates/bin/_neutron-dhcp-agent.sh."
"tpl`):"
msgid ""
"These values define all the endpoints that the Neutron chart may need in "
"order to build full URL compatible endpoints to various services. Long-term, "
"these will also include database, memcached, and rabbitmq elements in one "
"place. Essentially, all external connectivity can be defined centrally."
msgstr ""
"Diese Werte definieren alle Endpunkte, die das Neutron-Chart möglicherweise "
"benötigt, um vollständige URL-kompatible Endpunkte für verschiedene Dienste "
"zu erstellen. Langfristig werden diese auch Datenbank-, Memcached- und "
"Rabbitmq-Elemente an einem Ort umfassen. Im Wesentlichen kann die gesamte "
"externe Konnektivität zentral definiert werden."
msgid ""
"This daemonset includes the linuxbridge Neutron agent with bridge-utils and "
"ebtables utilities installed. This is all that is needed, since linuxbridge "
"uses native kernel libraries."
msgstr ""
"Dieses Daemonset enthält den Neutron-Agent linuxbridge mit den installierten "
"Dienstprogrammen bridge-utils und ebtables. Dies ist alles was benötigt "
"wird, da linuxbridge native Kernel-Bibliotheken verwendet."
msgid "This is accomplished with the following annotation:"
msgstr "Dies wird mit der folgenden Anmerkung erreicht:"
msgid ""
"This option will allow to configure the Neutron services in proper way, by "
"checking what is the actual backed set in :code:`neutron/values.yaml`."
msgstr ""
"Mit dieser Option können Sie die Neutron-Dienste auf die richtige Weise "
"konfigurieren, indem Sie überprüfen, was das tatsächlich hinterlegte Set "
"ist :code:`neutron/values.yaml`."
msgid ""
"This requirement is OVS specific, the `ovsdb_connection` string is defined "
"in `openvswitch_agent.ini` file, specifying how DHCP agent can connect to "
"ovs. When using other SDNs, running the DHCP agent may not be required. When "
"the SDN solution is addressing the IP assignments in another way, neutron's "
"DHCP agent should be disabled."
msgstr ""
"Diese Anforderung ist OVS-spezifisch, die Zeichenfolge ``ovsdb_connection`` "
"ist in der Datei ``openvswitch_agent.ini`` definiert und gibt an, wie der "
"DHCP-Agent eine Verbindung zu ovs herstellen kann. Bei Verwendung anderer "
"SDNs ist die Ausführung des DHCP-Agenten möglicherweise nicht erforderlich. "
"Wenn die SDN-Lösung die IP-Zuweisungen auf andere Weise anspricht, sollte "
"der DHCP-Agent von Neutron deaktiviert werden."
msgid ""
"This runs the OVS tool and database. OpenVSwitch chart is not Neutron "
"specific, it may be used with other technologies that are leveraging the OVS "
"technology, such as OVN or ODL."
msgstr ""
"Dies führt das OVS-Tool und die Datenbank aus. OpenVSwitch-Chart ist nicht "
"Neutron-spezifisch, es kann mit anderen Technologien verwendet werden, die "
"die OVS-Technologie nutzen, wie OVN oder ODL."
msgid ""
"This will be consumed by the templated ``configmap-etc.yaml`` manifest to "
"produce the following config file:"
msgstr ""
"Dies wird vom Manifest ``configmap-etc.yaml`` konsumiert, um die folgende "
"Konfigurationsdatei zu erzeugen:"
msgid ""
"To be able to configure multiple networking plugins inside of OpenStack-"
"Helm, a new configuration option is added:"
msgstr ""
"Um mehrere Netzwerk-Plugins innerhalb von OpenStack-Helm konfigurieren zu "
"können, wurde eine neue Konfigurationsoption hinzugefügt:"
msgid ""
"To enable new SDN solution, there should be separate chart created, which "
"would handle the deployment of service, setting up the database and any "
"related networking functionality that SDN is providing."
msgstr ""
"Um die neue SDN-Lösung zu aktivieren, sollte ein separates Chart erstellt "
"werden, das die Bereitstellung des Dienstes, die Einrichtung der Datenbank "
"und alle zugehörigen Netzwerkfunktionen, die SDN bereitstellt, übernimmt."
msgid ""
"To that end, all charts provide an ``images:`` section that allows operators "
"to override images. Also, all default image references should be fully "
"spelled out, even those hosted by Docker or Quay. Further, no default image "
"reference should use ``:latest`` but rather should be pinned to a specific "
"version to ensure consistent behavior for deployments over time."
msgstr ""
"Zu diesem Zweck enthalten alle Charts einen Abschnitt ``images:``, mit dem "
"Operatoren Abbilder überschreiben können. Außerdem sollten alle Standard-"
"Abbildreferenzen vollständig angegeben werden, selbst wenn sie von Docker "
"oder Quay gehostet werden. Darüber hinaus sollte keine "
"Standardabbildreferenz ``:latest`` verwenden, sondern sollte an eine "
"bestimmte Version angeheftet werden, um ein konsistentes Verhalten für "
"Bereitstellungen im Zeitverlauf sicherzustellen."
msgid ""
"To use other Neutron reference architecture types of SDN, these options "
"should be configured in :code:`neutron.conf`:"
msgstr ""
"Um andere Neutron-Referenzarchitekturtypen von SDN zu verwenden, sollten "
"diese Optionen in folgendem Code konfiguriert werden :code:`neutron.conf`:"
msgid ""
"Today, the ``images:`` section has several common conventions. Most "
"OpenStack services require a database initialization function, a database "
"synchronization function, and a series of steps for Keystone registration "
"and integration. Each component may also have a specific image that composes "
"an OpenStack service. The images may or may not differ, but regardless, "
"should all be defined in ``images``."
msgstr ""
"Heute hat der Abschnitt ``images:`` einige allgemeine Konventionen. Die "
"meisten OpenStack-Dienste erfordern eine Datenbankinitialisierungsfunktion, "
"eine Datenbanksynchronisierungsfunktion und eine Reihe von Schritten für die "
"Keystone-Registrierung und -Integration. Jede Komponente kann auch ein "
"bestimmtes Abbild haben, aus dem ein OpenStack-Service besteht. Die Abbilder "
"können sich unterscheiden oder nicht, aber unabhängig davon sollten alle in "
"``images`` definiert sein."
msgid "Typical networking API request is an operation of create/update/delete:"
msgstr ""
"Eine typische Netzwerk-API-Anfrage ist eine Operation von create / update / "
"delete:"
msgid "Upgrades and Reconfiguration"
msgstr "Upgrades und Neukonfigurationen"
msgid ""
"``host1.fqdn`` with labels ``compute-type: dpdk, sriov`` and ``another-"
"label: another-value``:"
msgstr ""
"``host1.fqdn`` mit den Labels ``compute-type: dpdk, sriov`` und ``another-"
"label: another-value``:"
msgid ""
"``host2.fqdn`` with labels ``compute-type: dpdk, sriov`` and ``another-"
"label: another-value``:"
msgstr ""
"``host2.fqdn`` mit den Labels ``compute-type: dpdk, sriov`` und ``another-"
"label: another-value``:"
msgid ""
"``host3.fqdn`` with labels ``compute-type: dpdk, sriov`` and ``another-"
"label: another-value``:"
msgstr ""
"``host3.fqdn`` mit den Labels ``compute-type: dpdk, sriov`` und ``another-"
"label: another-value``:"
msgid "``host4.fqdn`` with labels ``compute-type: dpdk, sriov``:"
msgstr "``host4.fqdn`` mit Label ``compute-type: dpdk, sriov``:"
msgid "``host5.fqdn`` with no labels:"
msgstr "``host5.fqdn`` ohne Label:"
msgid ""
"db\\_drop: The image that will perform database deletion operations for the "
"OpenStack service."
msgstr ""
"db \\ _drop: Das Abbild, das Datenbanklöschvorgänge für den OpenStack-"
"Service ausführt."
msgid ""
"db\\_init: The image that will perform database creation operations for the "
"OpenStack service."
msgstr ""
"db \\ _init: Das Abbild, das Datenbankerstellungsvorgänge für den OpenStack-"
"Service ausführt."
msgid ""
"db\\_sync: The image that will perform database sync (schema initialization "
"and migration) for the OpenStack service."
msgstr ""
"db \\ _sync: Das Abbild, das die Datenbanksynchronisierung "
"(Schemainitialisierung und -migration) für den OpenStack-Service durchführt."
msgid ""
"dep\\_check: The image that will perform dependency checking in an init-"
"container."
msgstr ""
"dep \\ _check: Das Abbild, das die Abhängigkeitsprüfung in einem init-"
"Container durchführt."
msgid ""
"image: This is the OpenStack service that the endpoint is being built for. "
"This will be mapped to ``glance`` which is the image service for OpenStack."
msgstr ""
"image: Dies ist der OpenStack-Dienst, für den der Endpunkt erstellt wird. "
"Dies wird auf ``glance`` abgebildet, was der Abbild-Dienst für OpenStack ist."
msgid ""
"internal: This is the OpenStack endpoint type we are looking for - valid "
"values would be ``internal``, ``admin``, and ``public``"
msgstr ""
"internal: Dies ist der OpenStack-Endpunkttyp, nach dem wir suchen - gültige "
"Werte wären ``internal``, `admin`` und` public``"
msgid ""
"ks\\_endpoints: The image that will perform keystone endpoint registration "
"for the service."
msgstr ""
"ks \\ _endpoints: Das Abbild, das die Keystone-Endpunktregistrierung für den "
"Service durchführt."
msgid ""
"ks\\_service: The image that will perform keystone service registration for "
"the service."
msgstr ""
"ks \\ _service: Das Abbild, das die Registrierung des Keystone-Service für "
"den Service durchführt."
msgid ""
"ks\\_user: The image that will perform keystone user creation for the "
"service."
msgstr ""
"ks \\ _user: Das Abbild, das die Keystone-Nutzererstellung für den Service "
"durchführt."
msgid "network"
msgstr "Netzwerk"
msgid "neutron-dhcp-agent"
msgstr "Neutron-dhcp-Agent"
msgid ""
"neutron-dhcp-agent service is scheduled to run on nodes with the label "
"`openstack-control-plane=enabled`."
msgstr ""
"Der Neutron-dhcp-Agent-Dienst wird auf Knoten mit der Bezeichnung openstack-"
"control-plane = enabled ausgeführt."
msgid "neutron-l3-agent"
msgstr "Neutron-I3-agent"
msgid ""
"neutron-l3-agent service is scheduled to run on nodes with the label "
"`openstack-control-plane=enabled`."
msgstr ""
"Der Dienst von neutron-l3-agent soll auf Knoten mit der Bezeichnung "
"openstack-control-plane = enabled ausgeführt werden."
msgid "neutron-lb-agent"
msgstr "Neutron-lb-agent"
msgid "neutron-metadata-agent"
msgstr "Neutron-metadata-agent"
msgid ""
"neutron-metadata-agent service is scheduled to run on nodes with the label "
"`openstack-control-plane=enabled`."
msgstr ""
"Der Neutron-Metadaten-Agent-Dienst soll auf Knoten mit der Bezeichnung "
"openstack-control-plane = enabled ausgeführt werden."
msgid "neutron-ovs-agent"
msgstr "Neutron-ovs-agent"
msgid "neutron-server"
msgstr "Neutron-Server"
msgid ""
"neutron-server is serving the networking REST API for operator and other "
"OpenStack services usage. The internals of Neutron are highly flexible, "
"providing plugin mechanisms for all networking services exposed. The "
"consistent API is exposed to the user, but the internal implementation is up "
"to the chosen SDN."
msgstr ""
"Neutron-Server bedient die Netzwerk-REST-API für die Nutzung von Betreibern "
"und anderen OpenStack-Diensten. Die Interna von Neutron sind sehr flexibel "
"und bieten Plug-in-Mechanismen für alle verfügbaren Netzwerkdienste. Die "
"konsistente API wird dem Benutzer zur Verfügung gestellt, die interne "
"Implementierung unterliegt jedoch dem ausgewählten SDN."
msgid "openvswitch-db and openvswitch-vswitchd"
msgstr "openvswitch-db und openvswitch-vswitchd"
msgid "port"
msgstr "port"
msgid ""
"pull\\_policy: The image pull policy, one of \"Always\", \"IfNotPresent\", "
"and \"Never\" which will be used by all containers in the chart."
msgstr ""
"pull \\ _policy: Die Image-Pull-Richtlinie, eine der Optionen ``Always``, "
"``IfNotPresent`` und ``Never``, die von allen Containern im Chart verwendet "
"wird."
msgid "subnet"
msgstr "Teilnetz"

View File

@ -1,968 +0,0 @@
# Frank Kloeker <eumel@arcor.de>, 2018. #zanata
# Robert Simai <robert.simai@suse.com>, 2018. #zanata
msgid ""
msgstr ""
"Project-Id-Version: openstack-helm 0.1.1.dev3685\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2022-04-06 21:47+0000\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"PO-Revision-Date: 2018-10-25 10:34+0000\n"
"Last-Translator: Robert Simai <robert.simai@suse.com>\n"
"Language-Team: German\n"
"Language: de\n"
"Plural-Forms: nplurals=2; plural=(n != 1)\n"
"X-Generator: Zanata 4.3.3\n"
msgid "**Check Chart Status**"
msgstr "**Chart Status überprüfen**"
msgid ""
"**First**, edit the ``values.yaml`` for Neutron, Glance, Horizon, Keystone, "
"and Nova."
msgstr ""
"**Zuerst**, editieren Sie die ``values.yaml`` für Neutron, Glance, Horizon, "
"Keystone und Nova."
msgid "**Review the Ingress configuration.**"
msgstr "**Überprüfen Sie die Ingress-Konfiguration.**"
msgid ""
"**Second** option would be as ``--set`` flags when calling ``helm install``"
msgstr ""
"**Zweiten** Option wäre als ``set`` Flags beim Aufruf von` `helm install``"
msgid "16GB of RAM"
msgstr "16 GB RAM"
msgid "4 Cores"
msgstr "4 Kerne"
msgid "48GB HDD"
msgstr "48 GB HDD"
msgid "8 Cores"
msgstr "8 Kerne"
msgid "8GB of RAM"
msgstr "8 GB RAM"
msgid "Activate the OpenStack namespace to be able to use Ceph"
msgstr "Aktivieren Sie den OpenStack-Namespace, um Ceph verwenden zu können"
msgid "Activate the openstack namespace to be able to use Ceph"
msgstr "Aktivieren Sie den Openstack-Namespace, um Ceph verwenden zu können"
msgid ""
"Add the address of the Kubernetes API, ``172.17.0.1``, and ``.svc.cluster."
"local`` to your ``no_proxy`` and ``NO_PROXY`` environment variables."
msgstr ""
"Fügen Sie die Adresse der Kubernetes-API ``172.17.0.1`` und ``.svc.cluster."
"local`` zu Ihren Umgebungsvariablen ``no_proxy`` und ``NO_PROXY`` hinzu."
msgid ""
"Add to the Install steps these flags - also adding a shell environment "
"variable to save on repeat code."
msgstr ""
"Fügen Sie zu den Installationsschritten diese Flags hinzu, und fügen Sie "
"außerdem eine Shell-Umgebungsvariable hinzu, um den Wiederholungscode zu "
"speichern."
msgid ""
"Additional configuration variables can be found `here <https://github.com/"
"openstack/openstack-helm-infra/blob/master/roles/deploy-kubeadm-aio-common/"
"defaults/main.yml>`_. In particular, ``kubernetes_cluster_pod_subnet`` can "
"be used to override the pod subnet set up by Calico (the default container "
"SDN), if you have a preexisting network that conflicts with the default pod "
"subnet of 192.168.0.0/16."
msgstr ""
"Zusätzliche Konfigurationsvariablen finden Sie `hier <https://github.com/"
"openstack/openstack-helm-infra/blob/master/roles/deploy-kubeadm-aio-common/"
"defaults/main.yml>`_. Insbesondere kann ``kubernetes_cluster_pod_subnet`` "
"verwendet werden, um das von Calico (dem Standard-Container SDN) "
"eingerichtete Pod-Subnetz zu überschreiben, wenn ein bereits bestehendes "
"Netzwerk mit dem Standard-Pod-Subnetz von 192.168.0.0/16 in Konflikt steht."
msgid ""
"Additional information on Kubernetes Ceph-based integration can be found in "
"the documentation for the `CephFS <https://github.com/kubernetes-incubator/"
"external-storage/blob/master/ceph/cephfs/README.md>`_ and `RBD <https://"
"github.com/kubernetes-incubator/external-storage/blob/master/ceph/rbd/README."
"md>`_ storage provisioners, as well as for the alternative `NFS <https://"
"github.com/kubernetes-incubator/external-storage/blob/master/nfs/README."
"md>`_ provisioner."
msgstr ""
"Weitere Informationen zur Kubernetes Ceph-basierten Integration finden Sie "
"in der Dokumentation zum `CephFS <https://github.com/kubernetes-incubator/"
"external-storage/blob/master/ceph/cephfs/README.md>`_ und` RBD <https://"
"github.com/kubernetes-incubator/external-storage/blob/master/ceph/rbd/README."
"md>`_ Speicher-Provisioner, sowie für die Alternative `NFS <https://github."
"com/kubernetes-incubator/external-storage/blob/master/nfs/README.md>`_ "
"Bereitsteller."
msgid ""
"After making the configuration changes, run a ``make`` and then install as "
"you would from AIO or MultiNode instructions."
msgstr ""
"Nachdem Sie die Konfigurationsänderungen vorgenommen haben, führen Sie ein "
"``make`` aus und installieren Sie dann wie von AIO- oder MultiNode-"
"Anweisungen."
msgid ""
"All commands below should be run as a normal user, not as root. Appropriate "
"versions of Docker, Kubernetes, and Helm will be installed by the playbooks "
"used below, so there's no need to install them ahead of time."
msgstr ""
"Alle folgenden Befehle sollten als normaler Benutzer und nicht als root "
"ausgeführt werden. Entsprechende Versionen von Docker, Kubernetes und Helm "
"werden von den unten verwendeten Playbooks installiert, so dass es nicht "
"notwendig ist, sie vorher zu installieren."
msgid ""
"Alternatively, this step can be performed by running the script directly:"
msgstr ""
"Alternativ kann dieser Schritt ausgeführt werden, indem das Skript direkt "
"ausgeführt wird:"
msgid ""
"An Ingress is a collection of rules that allow inbound connections to reach "
"the cluster services."
msgstr ""
"Ein Ingress ist eine Sammlung von Regeln, die es eingehenden Verbindungen "
"erlauben, die Cluster-Dienste zu erreichen."
msgid ""
"By default the Calico CNI will use ``192.168.0.0/16`` and Kubernetes "
"services will use ``10.96.0.0/16`` as the CIDR for services. Check that "
"these CIDRs are not in use on the development node before proceeding, or "
"adjust as required."
msgstr ""
"Standardmäßig verwendet der Calico CNI `192.168.0.0/16`` und Kubernetes "
"Dienste` `10.96.0.0/16`` als CIDR für Dienste. Stellen Sie sicher, dass "
"diese CIDRs nicht auf dem Entwicklungsknoten verwendet werden, bevor Sie "
"fortfahren, oder passen Sie sie wie erforderlich an."
msgid "Cleaning the Deployment"
msgstr "Reinigung der Bereitstellung"
msgid "Clone the OpenStack-Helm Repos"
msgstr "Klonen Sie die OpenStack-Helm Repos"
msgid "Code examples below."
msgstr "Codebeispiele unten."
msgid "Common Deployment Requirements"
msgstr "Allgemeine Bereitstellungsanforderungen"
msgid "Configure OpenStack"
msgstr "Konfigurieren Sie OpenStack"
msgid ""
"Configuring OpenStack for a particular production use-case is beyond the "
"scope of this guide. Please refer to the OpenStack `Configuration <https://"
"docs.openstack.org/latest/configuration/>`_ documentation for your selected "
"version of OpenStack to determine what additional values overrides should be "
"provided to the OpenStack-Helm charts to ensure appropriate networking, "
"security, etc. is in place."
msgstr ""
"Die Konfiguration von OpenStack für einen bestimmten Produktions-"
"Anwendungsfall würde den Rahmen dieses Handbuchs sprengen. Bitte beachten "
"Sie die OpenStack `Konfiguration <https://docs.openstack.org/latest/"
"configuration/>`_ Dokumentation für Ihre Version von OpenStack, um zu "
"ermitteln, welche zusätzlichen Werte den OpenStack-Helm-Charts hinzugefügt "
"werden sollten, um eine angemessene Vernetzung, Sicherheit usw. "
"sicherzustellen."
msgid "Contents:"
msgstr "Inhalt:"
msgid ""
"Copy the key: ``sudo cp ~/.ssh/id_rsa /etc/openstack-helm/deploy-key.pem``"
msgstr ""
"Kopieren Sie den Schlüssel: ``sudo cp ~/.ssh/id_rsa /etc/openstack-helm/"
"deploy-key.pem``"
msgid "Create an environment file"
msgstr "Erstellen Sie eine Umgebungsdatei"
msgid "Create an inventory file"
msgstr "Erstellen Sie eine Inventardatei"
msgid ""
"Create an ssh-key on the master node, and add the public key to each node "
"that you intend to join the cluster."
msgstr ""
"Erstellen Sie auf dem Master-Knoten einen SSH-Schlüssel, und fügen Sie jedem "
"Knoten, dem Sie den Cluster beitreten möchten, den öffentlichen Schlüssel "
"hinzu."
msgid "Deploy Barbican"
msgstr "Bereitstellen von Barbican"
msgid "Deploy Ceph"
msgstr "Stellen Sie Ceph bereit"
msgid "Deploy Cinder"
msgstr "Bereitstellen von Cinder"
msgid "Deploy Compute Kit (Nova and Neutron)"
msgstr "Bereitstellen eines Compute Kit (Nova und Neutron)"
msgid "Deploy Glance"
msgstr "Bereitstellen von Glance"
msgid "Deploy Heat"
msgstr "Bereitstellen von Heat"
msgid "Deploy Horizon"
msgstr "Bereitstellen von Horizont"
msgid "Deploy Keystone"
msgstr "Stellen Sie Keystone bereit"
msgid "Deploy Kubernetes & Helm"
msgstr "Stellen Sie Kubernetes & Helm bereit"
msgid "Deploy Libvirt"
msgstr "Stellen Sie Libvirt bereit"
msgid "Deploy MariaDB"
msgstr "Stellen Sie MariaDB bereit"
msgid "Deploy Memcached"
msgstr "Bereitstellen von Memcached"
msgid "Deploy NFS Provisioner"
msgstr "Bereitstellen von NFS-Provisioner"
msgid "Deploy OpenStack-Helm"
msgstr "Stellen Sie OpenStack-Helm bereit"
msgid "Deploy OpenvSwitch"
msgstr "Stellen Sie OpenvSwitch bereit"
msgid "Deploy RabbitMQ"
msgstr "Stellen Sie RabbitMQ bereit"
msgid "Deploy Rados Gateway for object store"
msgstr "Stellen Sie Rados Gateway für den Objektspeicher bereit"
msgid "Deploy the ingress controller"
msgstr "Stellen Sie den Ingress-Controller bereit"
msgid "Deployment With Ceph"
msgstr "Einsatz mit Ceph"
msgid "Deployment With NFS"
msgstr "Bereitstellung mit NFS"
msgid "Development"
msgstr "Entwicklung"
msgid "Environment tear-down"
msgstr "Environment-Abbau"
msgid ""
"Essentially the use of Ingress for OpenStack-Helm is an Nginx proxy service. "
"Ingress (Nginx) is accessible by your cluster public IP - e.g. the IP "
"associated with ``kubectl get pods -o wide --all-namespaces | grep ingress-"
"api`` Ingress/Nginx will be listening for server name requests of \"keystone"
"\" or \"keystone.openstack\" and will route those requests to the proper "
"internal K8s Services. These public listeners in Ingress must match the "
"external DNS that you will set up to access your OpenStack deployment. Note "
"each rule also has a Service that directs Ingress Controllers allow access "
"to the endpoints from within the cluster."
msgstr ""
"Im Wesentlichen ist die Verwendung von Ingress für OpenStack-Helm ein Nginx-"
"Proxy-Dienst. Auf Ingress (Nginx) kann über die öffentliche IP-Adresse des "
"Clusters zugegriffen werden - z.B. die mit ``kubectl get pods -o wide --all-"
"namespaces |`` verbundene IP grep ingress-api`` Ingress / Nginx wird auf die "
"Server-Namensanforderungen ``keystone`` oder ``keystone.openstack`` warten "
"und diese Anfragen an die richtigen internen K8s-Dienste weiterleiten. Diese "
"öffentlichen Listener in Ingress müssen mit dem externen DNS übereinstimmen, "
"den Sie für den Zugriff auf Ihre OpenStack-Bereitstellung einrichten. "
"Beachten Sie, dass jede Regel auch über einen Dienst verfügt, der Ingress-"
"Controllern den Zugriff auf die Endpunkte innerhalb des Clusters ermöglicht."
msgid "Examples"
msgstr "Beispiele"
msgid "Exercise the Cloud"
msgstr "Trainieren der Cloud"
msgid "External DNS and FQDN"
msgstr "Externer DNS und FQDN"
msgid "External DNS to FQDN/Ingress"
msgstr "Externer DNS zu FQDN/Ingress"
msgid ""
"For ``identity`` and ``dashboard`` at ``host_fdqn_override.public`` replace "
"``null`` with the value as ``keystone.os.foo.org`` and ``horizon.os.foo.org``"
msgstr ""
"Für ``identity`` und ``dashboard`` bei ``host_fdqn_override.public`` "
"ersetzen Sie ``null`` durch den Wert ``keystone.os.foo.org`` und ``horizon."
"os.foo. org``"
msgid ""
"For a deployment without cinder and horizon the system requirements are:"
msgstr ""
"Für eine Bereitstellung ohne Cinder und Horizon sind die Systemanforderungen:"
msgid ""
"For a lab or proof-of-concept environment, the OpenStack-Helm gate scripts "
"can be used to quickly deploy a multinode Kubernetes cluster using KubeADM "
"and Ansible. Please refer to the deployment guide `here <./kubernetes-gate."
"html>`__."
msgstr ""
"Für eine Labor- oder Proof-of-Concept-Umgebung können die OpenStack-Helm-"
"Gate-Scripts verwendet werden, um einen Multinode-Kubernetes-Cluster "
"mithilfe von KubeADM und Ansible schnell bereitzustellen. Weitere "
"Informationen finden Sie im Bereitstellungshandbuch `hier <./kubernetes-gate."
"html>`__."
msgid ""
"For other deployment options, select appropriate ``Deployment with ...`` "
"option from `Index <../developer/index.html>`__ page."
msgstr ""
"Wählen Sie für andere Bereitstellungsoptionen die entsprechende Option `` "
"Deployment with ... `` von der Seite `Index <../developer/index.html>`__."
msgid "Gate-Based Kubernetes"
msgstr "Gate-Based Kubernetes"
msgid "Get the Nginx configuration from the Ingress Pod:"
msgstr "Holen Sie sich die Nginx-Konfiguration vom Ingress Pod:"
msgid "Get the ``helm status`` of your chart."
msgstr "Erhalten Sie den ``Helm Status`` Ihres Charts."
msgid "Helm Chart Installation"
msgstr "Helm Chart Installation"
msgid "Host Configuration"
msgstr "Hostkonfiguration"
msgid ""
"If doing an `AIO install <https://docs.openstack.org/openstack-helm/latest/"
"install/developer/index.html>`__, all the ``--set`` flags"
msgstr ""
"Wenn Sie eine `AIO-Installation durchführen <https://docs.openstack.org/"
"openstack-helm/latest/install/developer/index.html>`__, alle ``set`` Flags"
msgid ""
"Implementing the FQDN overrides **must** be done at install time. If you run "
"these as helm upgrades, Ingress will notice the updates though none of the "
"endpoint build-out jobs will run again, unless they are cleaned up manually "
"or using a tool like Armada."
msgstr ""
"Die Implementierung der FQDN-Überschreibungen **muss** zur Installationszeit "
"erfolgen. Wenn Sie diese als Helm-Upgrades ausführen, wird Ingress die "
"Updates bemerken, aber keiner der Endpoint-Build-Out-Jobs wird erneut "
"ausgeführt, es sei denn, sie werden manuell bereinigt oder mit einem Tool "
"wie Armada."
msgid ""
"In order to access your OpenStack deployment on Kubernetes we can use the "
"Ingress Controller or NodePorts to provide a pathway in. A background on "
"Ingress, OpenStack-Helm fully qualified domain name (FQDN) overrides, "
"installation, examples, and troubleshooting will be discussed here."
msgstr ""
"Um auf Ihre OpenStack-Implementierung auf Kubernetes zuzugreifen, können wir "
"den Ingress-Controller oder die NodePorts verwenden, um einen Pfad "
"anzugeben. Ein Hintergrund zu Ingress, OpenStack-Helm vollständig "
"qualifizierten Domänennamen (FQDN), Installation, Beispielen und "
"Fehlerbehebung wird hier besprochen ."
msgid ""
"In order to deploy OpenStack-Helm behind corporate proxy servers, add the "
"following entries to ``openstack-helm-infra/tools/gate/devel/local-vars."
"yaml``."
msgstr ""
"Um OpenStack-Helm hinter Corporate Proxy Servern zu deployen, fügen Sie "
"folgende Einträge zu ``openstack-helm-infra/tools/gate/devel/local-vars."
"yaml`` hinzu."
msgid ""
"In order to drive towards a production-ready OpenStack solution, our goal is "
"to provide containerized, yet stable `persistent volumes <https://kubernetes."
"io/docs/concepts/storage/persistent-volumes/>`_ that Kubernetes can use to "
"schedule applications that require state, such as MariaDB (Galera). Although "
"we assume that the project should provide a \"batteries included\" approach "
"towards persistent storage, we want to allow operators to define their own "
"solution as well. Examples of this work will be documented in another "
"section, however evidence of this is found throughout the project. If you "
"find any issues or gaps, please create a `story <https://storyboard."
"openstack.org/#!/project/886>`_ to track what can be done to improve our "
"documentation."
msgstr ""
"Um zu einer produktionsfertigen OpenStack-Lösung zu gelangen, ist es unser "
"Ziel, containerisierte und dennoch stabile `persistente Datenträger "
"bereitzustellen <https://kubernetes.io/docs/concepts/storage/persistent-"
"volumes/>`_, die Kubernetes verwenden kann, um Anwendungen zu planen, die "
"einen Zustand benötigen, wie MariaDB (Galera). Obwohl wir davon ausgehen, "
"dass das Projekt einen ``Batteries included``-Ansatz für persistenten "
"Speicher bereitstellen sollte, wollen wir es den Betreibern ermöglichen, "
"auch ihre eigene Lösung zu definieren. Beispiele für diese Arbeit werden in "
"einem anderen Abschnitt dokumentiert, der Nachweis dafür findet sich jedoch "
"im gesamten Projekt. Wenn Sie Probleme oder Lücken finden, erstellen Sie "
"bitte eine Story <https://storyboard.openstack.org/#!/project/886>`_ um zu "
"verfolgen, was getan werden kann, um unsere Dokumentation zu verbessern."
msgid "Ingress"
msgstr "Ingress"
msgid "Install OpenStack-Helm"
msgstr "Installiere OpenStack-Helm"
msgid "Installation"
msgstr "Installation"
msgid ""
"It can be configured to give services externally-reachable URLs, load "
"balance traffic, terminate SSL, offer name based virtual hosting, and more."
msgstr ""
"Es kann so konfiguriert werden, dass es extern erreichbare URLs "
"bereitstellt, Last-Balance-Verkehr aufteilt, SSL beendet, namensbasiertes "
"virtuelles Hosting anbietet und vieles mehr."
msgid "Kubernetes Preparation"
msgstr "Kubernetes Vorbereitung"
msgid "Kubernetes and Common Setup"
msgstr "Kubernetes und gemeinsames Setup"
msgid "Latest Version Installs"
msgstr "Neueste Version installiert"
msgid ""
"Look for *server* configuration with a *server_name* matching your desired "
"FQDN"
msgstr ""
"Suchen Sie nach *server* configuration mit einem *server_name*, der Ihrem "
"gewünschten FQDN entspricht"
msgid ""
"Managing and configuring a Kubernetes cluster is beyond the scope of "
"OpenStack-Helm and this guide."
msgstr ""
"Das Verwalten und Konfigurieren eines Kubernetes-Clusters geht über den "
"Umfang von OpenStack-Helm und diesem Handbuch hinaus."
msgid ""
"Many of the default container images that are referenced across OpenStack-"
"Helm charts are not intended for production use; for example, while LOCI and "
"Kolla can be used to produce production-grade images, their public reference "
"images are not prod-grade. In addition, some of the default images use "
"``latest`` or ``master`` tags, which are moving targets and can lead to "
"unpredictable behavior. For production-like deployments, we recommend "
"building custom images, or at minimum caching a set of known images, and "
"incorporating them into OpenStack-Helm via values overrides."
msgstr ""
"Viele der Standard-Containerabbilder, auf die in den OpenStack-Helmet-Charts "
"verwiesen wird, sind nicht für den produktiven Einsatz vorgesehen. Während "
"beispielsweise LOCI und Kolla für die Produktion von Abbildern in "
"Produktionsqualität verwendet werden können, sind ihre öffentlichen "
"Referenzabbilder keine Produktqualität. Darüber hinaus verwenden einige der "
"Standardabbilder ``latest`` oder ``master``-Tags, bei denen es sich um "
"bewegte Ziele handelt, die zu unvorhersehbarem Verhalten führen können. Für "
"produktionsähnliche Bereitstellungen empfehlen wir, benutzerdefinierte "
"Abbiler zu erstellen oder mindestens eine Reihe bekannter Abbildern "
"zwischenzuspeichern und sie über Werteüberschreibungen in OpenStack-Helm zu "
"integrieren."
msgid "Multinode"
msgstr "Multinode"
msgid ""
"Note if you need to make a DNS change, you will have to do uninstall (``helm "
"delete <chart>``) and install again."
msgstr ""
"Hinweis: Wenn Sie eine DNS-Änderung vornehmen, müssen Sie eine "
"Deinstallation durchführen (``helm delete <chart> ``) und erneut "
"installieren."
msgid ""
"Note that this command will only enable you to auth successfully using the "
"``python-openstackclient`` CLI. To use legacy clients like the ``python-"
"novaclient`` from the CLI, reference the auth values in ``/etc/openstack/"
"clouds.yaml`` and run::"
msgstr ""
"Beachten Sie, dass Sie mit diesem Befehl nur autorisieren können, wenn Sie "
"die CLI ``python-openstackclient`` verwenden. Um Legacy-Clients wie den `` "
"python-novaclient`` aus der CLI zu verwenden, referenzieren Sie die Auth-"
"Werte in ``/etc/openstack/clouds.yaml`` und führen Sie folgendes aus:"
msgid ""
"On the host or master node, install the latest versions of Git, CA Certs & "
"Make if necessary"
msgstr ""
"Installieren Sie auf dem Host- oder Master-Knoten die neuesten Versionen von "
"Git, CA Certs & Make, falls erforderlich"
msgid "On the master node create an environment file for the cluster:"
msgstr ""
"Erstellen Sie auf dem Master-Knoten eine Umgebungsdatei für den Cluster:"
msgid "On the master node create an inventory file for the cluster:"
msgstr ""
"Erstellen Sie auf dem Master-Knoten eine Inventardatei für den Cluster:"
msgid "On the master node run the playbooks:"
msgstr "Führen Sie auf dem Master-Knoten die Playbooks aus:"
msgid "On the worker nodes:"
msgstr "Auf den Worker-Knoten:"
msgid ""
"Once OpenStack-Helm has been deployed, the cloud can be exercised either "
"with the OpenStack client, or the same heat templates that are used in the "
"validation gates."
msgstr ""
"Sobald OpenStack-Helm implementiert wurde, kann die Cloud entweder mit dem "
"OpenStack-Client oder mit den gleichen Heat-Vorlagen, die in den "
"Validierungsgates verwendet werden, ausgeführt werden."
msgid ""
"Once installed, access the API's or Dashboard at `http://horizon.os.foo.org`"
msgstr ""
"Nach der Installation greifen Sie auf die APIs oder das Dashboard unter "
"``http://horizon.os.foo.org`` zu"
msgid ""
"Once the host has been configured the repos containing the OpenStack-Helm "
"charts should be cloned onto each node in the cluster:"
msgstr ""
"Sobald der Host konfiguriert wurde, sollten die Repos, die die OpenStack-"
"Helm-Charts enthalten, auf jeden Knoten im Cluster geklont werden:"
msgid ""
"Once the host has been configured the repos containing the OpenStack-Helm "
"charts should be cloned:"
msgstr ""
"Sobald der Host konfiguriert wurde, sollten die Repos mit den OpenStack-Helm "
"Charts geklont werden:"
msgid ""
"OpenStack-Helm uses the hosts networking namespace for many pods including, "
"Ceph, Neutron and Nova components. For this, to function, as expected pods "
"need to be able to resolve DNS requests correctly. Ubuntu Desktop and some "
"other distributions make use of ``mdns4_minimal`` which does not operate as "
"Kubernetes expects with its default TLD of ``.local``. To operate at "
"expected either change the ``hosts`` line in the ``/etc/nsswitch.conf``, or "
"confirm that it matches:"
msgstr ""
"OpenStack-Helm verwendet den Namensraum des Hosts für viele Pods, "
"einschließlich Ceph-, Neutron- und Nova-Komponenten. Damit dies "
"funktioniert, müssen Pods in der Lage sein, DNS-Anfragen korrekt aufzulösen. "
"Ubuntu Desktop und einige andere Distributionen benutzen `` mdns4_minimal``, "
"was nicht funktioniert, wie es Kubernetes mit seiner Standard-TLD `` ."
"local`` erwartet. Um bei erwartet zu arbeiten, ändern Sie entweder die `` "
"hosts`` Zeile in der ``/etc/nsswitch.conf``, oder bestätigen Sie, dass sie "
"übereinstimmt:"
msgid ""
"OpenStack-Helm utilizes the `Kubernetes Ingress Controller <https://"
"kubernetes.io/docs/concepts/services-networking/ingress/>`__"
msgstr ""
"OpenStack-Helm verwendet den `Kubernetes Ingress Controller <https://"
"kubernetes.io/docs/concepts/services-networking/ingress/>`__"
msgid "OpenStack-Helm-Infra KubeADM deployment"
msgstr "OpenStack-Helm-Infra KubeADM-Bereitstellung"
msgid ""
"Other versions and considerations (such as other CNI SDN providers), config "
"map data, and value overrides will be included in other documentation as we "
"explore these options further."
msgstr ""
"Andere Versionen und Überlegungen (wie z.B. andere CNI-SDN-Anbieter), "
"Konfigurationskartendaten und Wertüberschreibungen werden in der weiteren "
"Dokumentation enthalten sein, wenn wir diese Optionen weiter untersuchen."
msgid "Overview"
msgstr "Überblick"
msgid "Passwordless Sudo"
msgstr "Passwortloses Sudo"
msgid ""
"Please see the supported application versions outlined in the `source "
"variable file <https://github.com/openstack/openstack-helm-infra/blob/master/"
"roles/build-images/defaults/main.yml>`_."
msgstr ""
"Bitte beachten Sie die unterstützten Anwendungsversionen, die in der "
"`Quellvariablendatei beschrieben sind <https://github.com/openstack/"
"openstack-helm-infra/blob/master/roles/build-images/defaults/main.yml>`_."
msgid ""
"Prepare ahead of time your FQDN and DNS layouts. There are a handful of "
"OpenStack endpoints you will want to expose for API and Dashboard access."
msgstr ""
"Bereiten Sie Ihre FQDN- und DNS-Layouts im Voraus vor. Es gibt eine Handvoll "
"OpenStack-Endpunkte, die für API- und Dashboard-Zugriff verfügbar sein "
"sollen."
msgid "Proxy Configuration"
msgstr "Proxy-Konfiguration"
msgid "Removing Helm Charts"
msgstr "Helm-Charts entfernen"
msgid "Requirements"
msgstr "Anforderungen"
msgid "Requirements and Host Configuration"
msgstr "Anforderungen und Hostkonfiguration"
msgid "Run the playbooks"
msgstr "Führen Sie die Playbooks aus"
msgid "SSH-Key preparation"
msgstr "SSH-Schlüssel Vorbereitung"
msgid ""
"Set correct ownership: ``sudo chown ubuntu /etc/openstack-helm/deploy-key."
"pem``"
msgstr ""
"Setzen Sie die korrekten Dateirechte: ``sudo chown ubuntu /etc/openstack-"
"helm/deploy-key.pem``"
msgid "Setup Clients on the host and assemble the charts"
msgstr ""
"Richten Sie Clients auf dem Host ein und stellen Sie die Charts zusammen"
msgid "Setup the gateway to the public network"
msgstr "Richten Sie das Gateway zum öffentlichen Netzwerk ein"
msgid "System Requirements"
msgstr "System Anforderungen"
msgid ""
"Test this by ssh'ing to a node and then executing a command with 'sudo'. "
"Neither operation should require a password."
msgstr ""
"Testen Sie dies, indem Sie einen ssh-Befehl an einen Knoten senden und dann "
"einen Befehl mit 'sudo' ausführen. Keine Operation sollte ein Passwort "
"erfordern."
msgid ""
"The OpenStack clients and Kubernetes RBAC rules, along with assembly of the "
"charts can be performed by running the following commands:"
msgstr ""
"Die OpenStack-Clients und Kubernetes-RBAC-Regeln können zusammen mit dem "
"Zusammenstellen der Charts ausgeführt werden, indem Sie die folgenden "
"Befehle ausführen:"
msgid ""
"The `./tools/deployment/multinode/kube-node-subnet.sh` script requires "
"docker to run."
msgstr ""
"Das Skript ``./tools/deployment/multinode/kube-node-subnet.sh`` erfordert "
"das Ausführen von docker."
msgid ""
"The ``.svc.cluster.local`` address is required to allow the OpenStack client "
"to communicate without being routed through proxy servers. The IP address "
"``172.17.0.1`` is the advertised IP address for the Kubernetes API server. "
"Replace the addresses if your configuration does not match the one defined "
"above."
msgstr ""
"Die ``.svc.cluster.local``-Adresse ist erforderlich, damit der OpenStack-"
"Client kommunizieren kann, ohne über Proxy-Server weitergeleitet zu werden. "
"Die IP-Adresse ``172.17.0.1`` ist die angekündigte IP-Adresse für den "
"Kubernetes-API-Server. Ersetzen Sie die Adressen, wenn Ihre Konfiguration "
"nicht mit der oben definierten Konfiguration übereinstimmt."
msgid "The default FQDN's for OpenStack-Helm are"
msgstr "Die Standard-FQDNs für OpenStack-Helm sind"
msgid ""
"The example above uses the default values used by ``openstack-helm-infra``."
msgstr ""
"Das obige Beispiel verwendet die Standardwerte von ``openstack-helm-infra``."
msgid ""
"The following commands all assume that they are run from the ``/opt/"
"openstack-helm`` directory."
msgstr ""
"Die folgenden Befehle gehen alle davon aus, dass sie vom Verzeichnis ``/opt/"
"openstack-helm`` ausgeführt werden."
msgid ""
"The following commands all assume that they are run from the ``openstack-"
"helm`` directory and the repos have been cloned as above."
msgstr ""
"Die folgenden Befehle gehen alle davon aus, dass sie vom Verzeichnis "
"``openstack-helm`` ausgeführt werden und die Repos wie oben geklont wurden."
msgid ""
"The installation procedures below, will take an administrator from a new "
"``kubeadm`` installation to OpenStack-Helm deployment."
msgstr ""
"Die folgenden Installationsverfahren führen einen Administrator von einer "
"neuen ``kubeadm``-Installation zur OpenStack-Helm-Bereitstellung."
msgid "The recommended minimum system requirements for a full deployment are:"
msgstr ""
"Die empfohlenen Mindestsystemanforderungen für eine vollständige "
"Bereitstellung sind:"
msgid ""
"The upstream Ceph image repository does not currently pin tags to specific "
"Ceph point releases. This can lead to unpredictable results in long-lived "
"deployments. In production scenarios, we strongly recommend overriding the "
"Ceph images to use either custom built images or controlled, cached images."
msgstr ""
"Das vorgelagerte Ceph-Bild-Repository bindet derzeit keine Tags an bestimmte "
"Ceph-Point-Releases. Dies kann zu unvorhersehbaren Ergebnissen in "
"langlebigen Bereitstellungen führen. In Produktionsszenarien empfehlen wir "
"dringend, die Ceph-Abbilder zu überschreiben, um entweder benutzerdefinierte "
"Abbilder oder gesteuerte, zwischengespeicherte Abbilder zu verwenden."
msgid ""
"These commands will restore the environment back to a clean Kubernetes "
"deployment, that can either be manually removed or over-written by "
"restarting the deployment process. It is recommended to restart the host "
"before doing so to ensure any residual state, eg. Network interfaces are "
"removed."
msgstr ""
"Mit diesen Befehlen wird die Umgebung wieder in einer sauberen Kubernetes-"
"Bereitstellung wiederhergestellt, die entweder manuell entfernt oder "
"überschrieben werden kann, indem der Bereitstellungsprozess neu gestartet "
"wird. Es wird empfohlen, den Host vorher neu zu starten, um einen Reststatus "
"sicherzustellen, z.B. Netzwerkschnittstellen werden entfernt."
msgid ""
"This guide assumes that users wishing to deploy behind a proxy have already "
"defined the conventional proxy environment variables ``http_proxy``, "
"``https_proxy``, and ``no_proxy``."
msgstr ""
"In diesem Handbuch wird davon ausgegangen, dass Benutzer, die hinter einem "
"Proxy-Server installieren möchten, bereits die herkömmlichen Proxy-"
"Umgebungsvariablen ``http_proxy``, ``https_proxy`` und ``no_proxy`` "
"definiert haben."
msgid "This guide covers the minimum number of requirements to get started."
msgstr ""
"In diesem Handbuch wird die Mindestanzahl von Anforderungen für den Start "
"beschrieben."
msgid ""
"This installation, by default will use Google DNS servers, 8.8.8.8 or "
"8.8.4.4 and updates resolv.conf. These DNS nameserver entries can be changed "
"by updating file ``/opt/openstack-helm-infra/tools/images/kubeadm-aio/assets/"
"opt/playbooks/vars.yaml`` under section ``external_dns_nameservers``. This "
"change must be done on each node in your cluster."
msgstr ""
"Diese Installation verwendet standardmäßig die Google DNS-Server 8.8.8.8 "
"oder 8.8.4.4 und aktualisiert resolv.conf. Diese DNS-Nameserver-Einträge "
"können geändert werden, indem die Datei ``/opt/openstack-helm-infra/tools/"
"images/kubeadm-aio/assets/opt/playbooks/vars.yaml`` im Abschnitt "
"``external_dns_nameservers`` aktualisiert wird. Diese Änderung muss für "
"jeden Knoten in Ihrem Cluster durchgeführt werden."
msgid ""
"This will delete all Kubernetes resources generated when the chart was "
"instantiated. However for OpenStack charts, by default, this will not delete "
"the database and database users that were created when the chart was "
"installed. All OpenStack projects can be configured such that upon deletion, "
"their database will also be removed. To delete the database when the chart "
"is deleted the database drop job must be enabled before installing the "
"chart. There are two ways to enable the job, set the job_db_drop value to "
"true in the chart's ``values.yaml`` file, or override the value using the "
"helm install command as follows:"
msgstr ""
"Dadurch werden alle Kubernetes-Ressourcen gelöscht, die beim Instanziieren "
"des Charts generiert wurden. Bei OpenStack-Charts werden jedoch "
"standardmäßig nicht die Datenbank- und Datenbankbenutzer gelöscht, die bei "
"der Installation des Charts erstellt wurden. Alle OpenStack-Projekte können "
"so konfiguriert werden, dass ihre Datenbank beim Löschen ebenfalls entfernt "
"wird. Um die Datenbank zu löschen, wenn das Chart gelöscht wird, muss der "
"Datenbank-Drop-Job vor der Installation des Charts aktiviert werden. Es gibt "
"zwei Möglichkeiten, den Job zu aktivieren, den Wert job_db_drop in der Datei "
"``values.yaml`` des Charts auf true zu setzen oder den Wert mithilfe des "
"Befehls helm install wie folgt zu überschreiben:"
msgid ""
"Throughout this guide the assumption is that the user is: ``ubuntu``. "
"Because this user has to execute root level commands remotely to other "
"nodes, it is advised to add the following lines to ``/etc/sudoers`` for each "
"node:"
msgstr ""
"In diesem Handbuch wird angenommen, dass der Benutzer ``ubuntu`` ist. Da "
"dieser Benutzer Befehle auf root-Ebene remote an andere Knoten ausführen "
"muss, wird empfohlen, die folgenden Zeilen für jeden Knoten zu ``/etc/"
"sudoers`` hinzuzufügen:"
msgid ""
"To copy the ssh key to each node, this can be accomplished with the ``ssh-"
"copy-id`` command, for example: *ssh-copy-id ubuntu@192.168.122.178*"
msgstr ""
"Um den ssh-Schlüssel auf jeden Knoten zu kopieren, kann dies mit dem Befehl "
"``ssh-copy-id`` durchgeführt werden, zum Beispiel: *ssh-copy-id "
"ubuntu@192.168.122.178*"
msgid "To delete an installed helm chart, use the following command:"
msgstr ""
"Verwenden Sie den folgenden Befehl, um ein installiertes Helm-Chart zu "
"löschen:"
msgid "To generate the key you can use ``ssh-keygen -t rsa``"
msgstr ""
"Um den Schlüssel zu generieren, können Sie ``ssh-keygen -t rsa`` benutzen"
msgid ""
"To run further commands from the CLI manually, execute the following to set "
"up authentication credentials::"
msgstr ""
"Um weitere Befehle von der CLI manuell auszuführen, führen Sie Folgendes "
"aus, um die Anmeldedaten für die Authentifizierung einzurichten:"
msgid ""
"To tear-down, the development environment charts should be removed first "
"from the 'openstack' namespace and then the 'ceph' namespace using the "
"commands from the `Removing Helm Charts` section. Additionally charts should "
"be removed from the 'nfs' and 'libvirt' namespaces if deploying with NFS "
"backing or bare metal development support. You can run the following "
"commands to loop through and delete the charts, then stop the kubelet "
"systemd unit and remove all the containers before removing the directories "
"used on the host by pods."
msgstr ""
"Zum Abbau sollten die Entwicklungsumgebungsdiagramme zuerst aus dem "
"Namespace ``openstack`` und dann aus dem Namespace ``ceph`` mit den Befehlen "
"aus dem Abschnitt ``Entfernen der Helm-Charts`` entfernt werden. Außerdem "
"sollten Charts aus den Namespaces 'nfs' und 'libvirt' entfernt werden, wenn "
"sie mit Unterstützung für NFS-Unterstützung oder Bare-Metal-Entwicklung "
"bereitgestellt werden. Sie können die folgenden Befehle ausführen, um die "
"Charts zu durchlaufen und zu löschen. Stoppen Sie dann die Kubelet-"
"Systemeinheit und entfernen Sie alle Container, bevor Sie die auf dem Host "
"verwendeten Verzeichnisse durch Pods entfernen."
msgid "Troubleshooting"
msgstr "Fehlerbehebung"
msgid ""
"Two similar options exist to set the FQDN overrides for External DNS mapping."
msgstr ""
"Es gibt zwei ähnliche Optionen, um die FQDN-Überschreibungen für die externe "
"DNS-Zuordnung festzulegen."
msgid ""
"Until the Ubuntu kernel shipped with 16.04 supports CephFS subvolume mounts "
"by default the `HWE Kernel <../troubleshooting/ubuntu-hwe-kernel.html>`__ is "
"required to use CephFS."
msgstr ""
"Bis der Ubuntu-Kernel, der mit 16.04 ausgeliefert wird, standardmäßig CephFS-"
"Subvolume-Mounts unterstützt, ist der `HWE-Kernel <../troubleshooting/ubuntu-"
"hwe-kernel.html>`__ erforderlich, um CephFS zu verwenden."
msgid ""
"Update your lab/environment DNS server with your appropriate host values "
"creating A Records for the edge node IP's and various FQDN's. Alternatively "
"you can test these settings locally by editing your ``/etc/hosts``. Below is "
"an example with a dummy domain ``os.foo.org`` and dummy Ingress IP "
"``1.2.3.4``."
msgstr ""
"Aktualisieren Sie Ihren Labor-/Umgebungs-DNS-Server mit Ihren entsprechenden "
"Host-Werten, indem Sie A-Datensätze für die IP-Adressen des Randknotens und "
"verschiedene FQDNs erstellen. Alternativ können Sie diese Einstellungen "
"lokal testen, indem Sie Ihre ``/etc/hosts`` bearbeiten. Unten ist ein "
"Beispiel mit einer Dummy-Domain ``os.foo.org`` und einer Dummy-Ingress-IP "
"``1.2.3.4``."
msgid "Using Horizon as an example, find the ``endpoints`` config."
msgstr "Am Beispiel von Horizon finden Sie die Konfiguration ``endpoints``."
msgid ""
"Using the Helm packages previously pushed to the local Helm repository, run "
"the following commands to instruct tiller to create an instance of the given "
"chart. During installation, the helm client will print useful information "
"about resources created, the state of the Helm releases, and whether any "
"additional configuration steps are necessary."
msgstr ""
"Führen Sie mithilfe der Helm-Pakete, die zuvor in das lokale Helm-Repository "
"gepusht wurden, die folgenden Befehle aus, um Tiller anzuweisen, eine "
"Instanz des angegebenen Charts zu erstellen. Während der Installation wird "
"der Helm-Client nützliche Informationen über die erstellten Ressourcen, den "
"Status der Helm-Versionen und darüber, ob zusätzliche Konfigurationsschritte "
"erforderlich sind, drucken."
msgid "Verify the *v1beta1/Ingress* resource has a Host with your FQDN value"
msgstr ""
"Überprüfen Sie, ob die Ressource *v1beta1/Ingress* über einen Host mit Ihrem "
"FQDN-Wert verfügt"
msgid ""
"We want to change the **public** configurations to match our DNS layouts "
"above. In each Chart ``values.yaml`` is a ``endpoints`` configuration that "
"has ``host_fqdn_override``'s for each API that the Chart either produces or "
"is dependent on. `Read more about how Endpoints are developed <https://docs."
"openstack.org/openstack-helm/latest/devref/endpoints.html>`__. Note while "
"Glance Registry is listening on a Ingress http endpoint, you will not need "
"to expose the registry for external services."
msgstr ""
"Wir möchten die **public** Konfigurationen so ändern, dass sie unseren "
"obigen DNS-Layouts entsprechen. In jedem Chart ist `values.yaml`` eine `` "
"endpoints`` Konfiguration, die ``host_fqdn_override``s für jede API hat, die "
"das Chart entweder erzeugt oder von der es abhängig ist. `Lesen Sie mehr "
"darüber, wie Endpunkte entwickelt werden <https://docs.openstack.org/"
"openstack-helm/latest/devref/endpoints.html>`__ . Hinweis: Während Glance "
"Registry einen Ingress-HTTP-Endpunkt überwacht, müssen Sie die Registrierung "
"für externe Dienste nicht verfügbar machen."
msgid ""
"You can use any Kubernetes deployment tool to bring up a working Kubernetes "
"cluster for use with OpenStack-Helm. For production deployments, please "
"choose (and tune appropriately) a highly-resilient Kubernetes distribution, "
"e.g.:"
msgstr ""
"Sie können ein beliebiges Kubernetes-Bereitstellungstool verwenden, um einen "
"funktionierenden Kubernetes-Cluster zur Verwendung mit OpenStack-Helm "
"aufzurufen. Bei Produktionsbereitstellungen wählen Sie bitte eine hoch "
"belastbare Kubernetes-Distribution aus, z.B.:"
msgid ""
"You can use any Kubernetes deployment tool to bring up a working Kubernetes "
"cluster for use with OpenStack-Helm. This guide describes how to simply "
"stand up a multinode Kubernetes cluster via the OpenStack-Helm gate scripts, "
"which use KubeADM and Ansible. Although this cluster won't be production-"
"grade, it will serve as a quick starting point in a lab or proof-of-concept "
"environment."
msgstr ""
"Sie können ein beliebiges Kubernetes-Bereitstellungstool verwenden, um einen "
"funktionierenden Kubernetes-Cluster zur Verwendung mit OpenStack-Helm "
"aufzurufen. Dieser Leitfaden beschreibt, wie man einen Multinode-Kubernetes-"
"Cluster einfach über die OpenStack-Helm-Gate-Skripte, die KubeADM und "
"Ansible verwenden, aufstellt. Obwohl dieser Cluster keine "
"Produktionsqualität hat, wird er als ein schneller Ausgangspunkt in einer "
"Labor- oder Proof-of-Concept-Umgebung dienen."
msgid ""
"You may now deploy kubernetes, and helm onto your machine, first move into "
"the ``openstack-helm`` directory and then run the following:"
msgstr ""
"Sie können nun kubernetes und helm auf Ihrem Rechner installieren, zuerst in "
"das Verzeichnis ``openstack-helm`` wechseln und dann folgendes ausführen:"
msgid ""
"`Airship <https://airshipit.org/>`_, a declarative open cloud infrastructure "
"platform"
msgstr ""
"`Airship <https://airshipit.org/>`_, eine deklarative Open-Cloud-"
"Infrastrukturplattform"
msgid ""
"`KubeADM <https://kubernetes.io/docs/setup/independent/high-availability/"
">`_, the foundation of a number of Kubernetes installation solutions"
msgstr ""
"`KubeADM <https://kubernetes.io/docs/setup/independent/high-availability/> "
"`_, die Grundlage für eine Reihe von Kubernetes Installationslösungen"
msgid ""
"node_one, node_two and node_three below are all worker nodes, children of "
"the master node that the commands below are executed on."
msgstr ""
"node_one, node_two und node_three unten sind alle Worker-Knoten, Kinder des "
"Master-Knotens, auf dem die folgenden Befehle ausgeführt werden."

View File

@ -1,757 +0,0 @@
# Andreas Jaeger <jaegerandi@gmail.com>, 2018. #zanata
# Frank Kloeker <eumel@arcor.de>, 2018. #zanata
msgid ""
msgstr ""
"Project-Id-Version: openstack-helm\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-03-23 00:21+0000\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"PO-Revision-Date: 2018-10-25 07:45+0000\n"
"Last-Translator: Andreas Jaeger <jaegerandi@gmail.com>\n"
"Language-Team: German\n"
"Language: de\n"
"Plural-Forms: nplurals=2; plural=(n != 1)\n"
"X-Generator: Zanata 4.3.3\n"
msgid "3 Node (VM based) env."
msgstr "3 Knoten (VM-basiert) env."
msgid "6 Nodes (VM based) env"
msgstr "6 Knoten (VM-basiert) Env."
msgid ""
"A Ceph Monitor running on voyager3 (whose Monitor database is destroyed) "
"becomes out of quorum, and the mon-pod's status stays in ``Running`` -> "
"``Error`` -> ``CrashLoopBackOff`` while keeps restarting."
msgstr ""
"Ein Ceph-Monitor, der auf voyager3 läuft (dessen Monitor-Datenbank zerstört "
"ist), wird aus dem Quorum und der Status des Mon-Pods bleibt in ``Running`` -"
"> ``Error`` -> ``CrashLoopBackOff``, während der Neustart fortgesetzt wird."
msgid "Adding Tests"
msgstr "Hinzufügen von Tests"
msgid ""
"Additional information on Helm tests for OpenStack-Helm and how to execute "
"these tests locally via the scripts used in the gate can be found in the "
"gates_ directory."
msgstr ""
"Weitere Informationen zu Helm-Tests für OpenStack-Helm und wie diese Tests "
"lokal über die im Gate verwendeten Skripte ausgeführt werden, finden Sie im "
"Verzeichnis gates_."
msgid ""
"After 10+ miniutes, Ceph starts rebalancing with one node lost (i.e., 6 osds "
"down) and the status stablizes with 18 osds."
msgstr ""
"Nach 10+ Minuten beginnt Ceph mit einem verlorenen Knoten (d.h. 6 OSDs nach "
"unten) und der Status stabilisiert sich mit 18 OSDs."
msgid "After reboot (node voyager3), the node status changes to ``NotReady``."
msgstr ""
"Nach dem Neustart (Knoten voyager3) ändert sich der Knotenstatus in "
"``NotReady``."
msgid ""
"After the host is down (node voyager3), the node status changes to "
"``NotReady``."
msgstr ""
"Nachdem der Host ausgefallen ist (Knoten voyager3), ändert sich der "
"Knotenstatus in ``NotReady``."
msgid ""
"All tests should be added to the gates during development, and are required "
"for any new service charts prior to merging. All Helm tests should be "
"included as part of the deployment script. An example of this can be seen "
"in this script_."
msgstr ""
"Alle Tests sollten während der Entwicklung zu den Gates hinzugefügt werden "
"und sind für alle neuen Dienst-Charts vor dem Zusammenführen erforderlich. "
"Alle Helm-Tests sollten als Teil des Bereitstellungsskripts enthalten sein. "
"Ein Beispiel dafür ist in diesem Skript zu sehen."
msgid ""
"Also, the pod status of ceph-mon and ceph-osd changes from ``NodeLost`` back "
"to ``Running``."
msgstr ""
"Außerdem ändert sich der Pod-Status von ceph-mon und ceph-osd von "
"``NodeLost`` zurück zu ``Running``."
msgid "Any Helm tests associated with a chart can be run by executing:"
msgstr ""
"Alle Helm-Tests, die mit einem Chart verknüpft sind, können ausgeführt "
"werden, indem Sie Folgendes ausführen:"
msgid ""
"Any templates for Helm tests submitted should follow the philosophies "
"applied in the other templates. These include: use of overrides where "
"appropriate, use of endpoint lookups and other common functionality in helm-"
"toolkit, and mounting any required scripting templates via the configmap-bin "
"template for the service chart. If Rally tests are not appropriate or "
"adequate for a service chart, any additional tests should be documented "
"appropriately and adhere to the same expectations."
msgstr ""
"Alle Vorlagen für Helm-Tests sollten den Philosophien folgen, die in den "
"anderen Vorlagen angewendet wurden. Dazu gehören: gegebenenfalls die "
"Verwendung von Überschreibungen, die Verwendung von Endpunkt-Suchvorgängen "
"und anderen allgemeinen Funktionen in helm-toolkit sowie das Bereitstellen "
"aller erforderlichen Skriptvorlagen über die Vorlage configmap-bin für das "
"Dienstdiagramm. Wenn Rally-Tests für ein Dienst-Chart nicht angemessen oder "
"angemessen sind, sollten alle zusätzlichen Tests angemessen dokumentiert "
"werden und den gleichen Erwartungen entsprechen."
msgid "Capture Ceph pods statuses."
msgstr "Capture Ceph Pods Status."
msgid "Capture Openstack pods statuses."
msgstr "Capture Openstack Pods Status."
msgid "Capture final Ceph pod statuses:"
msgstr "Erfassen Sie die endgültigen Ceph-Pod-Status:"
msgid "Capture final Openstack pod statuses:"
msgstr "Erfassen Sie die letzten Openstack-Pod-Status:"
msgid "Case: 1 out of 3 Monitor Processes is Down"
msgstr "Fall: 1 von 3 Überwachungsprozesse ist inaktiv"
msgid "Case: 2 out of 3 Monitor Processes are Down"
msgstr "Fall: 2 von 3 Monitor-Prozesse sind inaktiv"
msgid "Case: 3 out of 3 Monitor Processes are Down"
msgstr "Fall: 3 von 3 Monitor-Prozesse sind inaktiv"
msgid "Case: A OSD pod is deleted"
msgstr "Fall: Ein OSD-Pod wurde gelöscht"
msgid "Case: A disk fails"
msgstr "Fall: Eine Festplatte geht kaputt"
msgid "Case: A host machine where ceph-mon is running is down"
msgstr "Fall: Ein Host-Computer, auf dem ceph-mon läuft, ist inaktiv"
msgid "Case: Monitor database is destroyed"
msgstr "Fall: Die Monitor-Datenbank ist zerstört"
msgid "Case: OSD processes are killed"
msgstr "Fall: OSD-Prozesse werden abgebrochen"
msgid "Case: One host machine where ceph-mon is running is rebooted"
msgstr "Fall: Ein Host-Rechner, auf dem ceph-mon läuft, wird neu gestartet"
msgid "Caveats:"
msgstr "Vorbehalte:"
msgid "Ceph Cephfs provisioner docker images."
msgstr "Ceph Cephfs Provisioner Docker Abbilder."
msgid "Ceph Luminous point release images for Ceph components"
msgstr "Ceph Luminous Point Release Abbilder für Ceph-Komponenten"
msgid "Ceph RBD provisioner docker images."
msgstr "Ceph-RBD-Provisioner-Docker-Abbilder."
msgid "Ceph Resiliency"
msgstr "Ceph-Ausfallsicherheit"
msgid "Ceph Upgrade"
msgstr "Ceph Upgrade"
msgid ""
"Ceph status shows that ceph-mon running on ``voyager3`` becomes out of "
"quorum. Also, 6 osds running on ``voyager3`` are down (i.e., 18 out of 24 "
"osds are up). Some placement groups become degraded and undersized."
msgstr ""
"Der Ceph-Status zeigt, dass Ceph-mon, das auf ``voyager3`` läuft, das Quorum "
"verlässt. Außerdem sind 6 osds, die auf ``voyager3`` laufen, "
"heruntergefahren (d.h. 18 von 24 ods sind oben). Einige Placement-Gruppen "
"werden degradiert und zu klein."
msgid ""
"Ceph status shows that ceph-mon running on ``voyager3`` becomes out of "
"quorum. Also, six osds running on ``voyager3`` are down; i.e., 18 osds are "
"up out of 24 osds."
msgstr ""
"Der Ceph-Status zeigt, dass Ceph-mon, das auf ``voyager3`` läuft, das Quorum "
"verlässt. Sechs osds, die auf `` voyager3`` laufen, sind ebenfalls nicht "
"erreichbar. Das heißt, 18 Osts sind aus 24 Osts heraus."
msgid "Ceph version: 12.2.3"
msgstr "Ceph-Version: 12.2.3"
msgid "Check Ceph Pods"
msgstr "Überprüfen Sie Ceph Pods"
msgid "Check version of each Ceph components."
msgstr "Überprüfen Sie die Version der einzelnen Ceph-Komponenten."
msgid "Check which images Provisionors and Mon-Check PODs are using"
msgstr ""
"Überprüfen Sie, welche Abbilder Provisioner und Mon-Check-PODs verwenden"
msgid "Cluster size: 4 host machines"
msgstr "Clustergröße: 4 Host-Maschinen"
msgid "Conclusion:"
msgstr "Fazit:"
msgid "Confirm Ceph component's version."
msgstr "Bestätigen Sie die Version der Ceph-Komponente."
msgid "Continue with OSH multinode guide to install other Openstack charts."
msgstr ""
"Fahren Sie mit OSH multinode guide fort, um weitere Openstack-Charts zu "
"installieren."
msgid "Deploy and Validate Ceph"
msgstr "Bereitstellen und Validieren von Ceph"
msgid "Disk Failure"
msgstr "Festplattenfehler"
msgid "Docker Images:"
msgstr "Docker Abbilder:"
msgid ""
"Every OpenStack-Helm chart should include any required Helm tests necessary "
"to provide a sanity check for the OpenStack service. Information on using "
"the Helm testing framework can be found in the Helm repository_. Currently, "
"the Rally testing framework is used to provide these checks for the core "
"services. The Keystone Helm test template can be used as a reference, and "
"can be found here_."
msgstr ""
"Jedes OpenStack-Helm-Chart sollte alle erforderlichen Helm-Tests enthalten, "
"die für eine Plausibilitätsprüfung des OpenStack-Dienstes erforderlich sind. "
"Informationen zur Verwendung des Helm-Test-Frameworks finden Sie im Helm-"
"Repository. Momentan wird das Rallyetest-Framework verwendet, um diese "
"Überprüfungen für die Kerndienste bereitzustellen. Die Keystone Helm "
"Testvorlage kann als Referenz verwendet werden und kann hier gefunden werden."
msgid "Find that Ceph is healthy with a lost OSD (i.e., a total of 23 OSDs):"
msgstr ""
"Finde heraus, dass Ceph gesund ist mit einem verlorenen OSD (d.h. insgesamt "
"23 OSDs):"
msgid "Follow all steps from OSH multinode guide with below changes."
msgstr ""
"Befolgen Sie alle Schritte des OSH-Multinode-Handbuchs mit den folgenden "
"Änderungen."
msgid ""
"Followed OSH multinode guide steps to setup nodes and install K8s cluster"
msgstr ""
"Gefolgt OSH Multinode Guide Schritte zum Einrichten von Knoten und "
"installieren K8s-Cluster"
msgid "Followed OSH multinode guide steps upto Ceph install"
msgstr "Gefolgt OSH Multinode Guide Schritte bis Ceph Installation"
msgid "Following is a partial part from script to show changes."
msgstr "Es folgt ein Teil des Skripts, um Änderungen anzuzeigen."
msgid ""
"From the Kubernetes cluster, remove the failed OSD pod, which is running on "
"``voyager4``:"
msgstr ""
"Entfernen Sie im Kubernetes-Cluster den fehlerhaften OSD-Pod, der auf "
"``voyager4`` läuft:"
msgid "Hardware Failure"
msgstr "Hardwarefehler"
msgid "Helm Tests"
msgstr "Helm-Tests"
msgid "Host Failure"
msgstr "Hostfehler"
msgid ""
"In the mean time, we monitor the status of Ceph and noted that it takes "
"about 30 seconds for the 6 OSDs to recover from ``down`` to ``up``. The "
"reason is that Kubernetes automatically restarts OSD pods whenever they are "
"killed."
msgstr ""
"In der Zwischenzeit überwachen wir den Status von Ceph und stellen fest, "
"dass es etwa 30 Sekunden dauert, bis die 6 OSDs von ``down`` nach ``up`` "
"zurückkehren. Der Grund dafür ist, dass Kubernetes OSD-Pods automatisch neu "
"startet, wenn sie getötet werden."
msgid ""
"In the mean time, we monitored the status of Ceph and noted that it takes "
"about 24 seconds for the killed Monitor process to recover from ``down`` to "
"``up``. The reason is that Kubernetes automatically restarts pods whenever "
"they are killed."
msgstr ""
"In der Zwischenzeit haben wir den Status von Ceph überwacht und "
"festgestellt, dass es etwa 24 Sekunden dauert, bis sich der getötete Monitor-"
"Prozess von ``down`` nach ``up`` zurückholt. Der Grund ist, dass Kubernetes "
"automatisch Pods neu startet, wenn sie getötet werden."
msgid "Install Ceph charts (12.2.4) by updating Docker images in overrides."
msgstr ""
"Installieren Sie Ceph-Diagramme (12.2.4), indem Sie Docker-Abbilder in "
"Overrides aktualisieren."
msgid "Install Ceph charts (version 12.2.4)"
msgstr "Installieren Sie Ceph-Diagramme (Version 12.2.4)"
msgid "Install OSH components as per OSH multinode guide."
msgstr ""
"Installieren Sie die Arbeitsschutzkomponenten gemäß dem OSH multinode guide."
msgid "Install Openstack charts"
msgstr "Installieren Sie Openstack-Charts"
msgid ""
"It takes longer (about 1 minute) for the killed Monitor processes to recover "
"from ``down`` to ``up``."
msgstr ""
"Es dauert länger (etwa 1 Minute), bis die getöteten Monitor-Prozesse von "
"``down`` nach ``up`` zurückkehren."
msgid "Kubernetes version: 1.10.5"
msgstr "Kubernetes Version: 1.10.5"
msgid "Kubernetes version: 1.9.3"
msgstr "Kubernetes Version: 1.9.3"
msgid "Mission"
msgstr "Mission"
msgid "Monitor Failure"
msgstr "Fehler beim Überwachen"
msgid ""
"Note: To find the daemonset associated with a failed OSD, check out the "
"followings:"
msgstr ""
"Hinweis: Um den mit einem fehlgeschlagenen OSD verbundenen Daemonset zu "
"finden, überprüfen Sie Folgendes:"
msgid "Number of disks: 24 (= 6 disks per host * 4 hosts)"
msgstr "Anzahl der Festplatten: 24 (= 6 Festplatten pro Host * 4 Hosts)"
msgid "OSD Failure"
msgstr "OSD-Fehler"
msgid "OSD count is set to 3 based on env setup."
msgstr "Die OSD-Anzahl wird basierend auf dem env-Setup auf 3 festgelegt."
msgid "OpenStack-Helm commit: 25e50a34c66d5db7604746f4d2e12acbdd6c1459"
msgstr "OpenStack-Helm commit: 25e50a34c66d5db7604746f4d2e12acbdd6c1459"
msgid "OpenStack-Helm commit: 28734352741bae228a4ea4f40bcacc33764221eb"
msgstr "OpenStack-Helm commit: 28734352741bae228a4ea4f40bcacc33764221eb"
msgid ""
"Our focus lies on resiliency for various failure scenarios but not on "
"performance or stress testing."
msgstr ""
"Unser Fokus liegt auf der Ausfallsicherheit für verschiedene "
"Fehlerszenarien, jedoch nicht auf der Leistung oder dem Stresstest."
msgid "Plan:"
msgstr "Planen:"
msgid "Recovery:"
msgstr "Wiederherstellung:"
msgid ""
"Remove the entire ceph-mon directory on voyager3, and then Ceph will "
"automatically recreate the database by using the other ceph-mons' database."
msgstr ""
"Entfernen Sie das gesamte Verzeichnis ceph-mon auf voyager3, und Ceph "
"erstellt dann automatisch die Datenbank neu, indem es die Datenbank der "
"anderen ceph-mons verwendet."
msgid ""
"Remove the failed OSD (OSD ID = 2 in this example) from the Ceph cluster:"
msgstr ""
"Entfernen Sie das fehlerhafte OSD (OSD ID = 2 in diesem Beispiel) vom Ceph-"
"Cluster:"
msgid "Resiliency Tests for OpenStack-Helm/Ceph"
msgstr "Resiliency Tests für OpenStack-Helm/Ceph"
msgid "Running Tests"
msgstr "Tests ausführen"
msgid "Setup:"
msgstr "Konfiguration:"
msgid ""
"Showing partial output from kubectl describe command to show which image is "
"Docker container is using"
msgstr ""
"Teilausgabe von kubectl anzeigen Befehl beschreiben, welches Abbild der "
"Docker-Container verwendet"
msgid "Software Failure"
msgstr "Softwarefehler"
msgid "Solution:"
msgstr "Lösung:"
msgid "Start a new OSD pod on ``voyager4``:"
msgstr "Starten Sie einen neuen OSD-Pod auf ``voyager4``:"
msgid "Step 1: Initial Ceph and OpenStack deployment"
msgstr "Schritt 1: Initiales Ceph und OpenStack Deployment"
msgid "Steps:"
msgstr "Schritte:"
msgid "Symptom:"
msgstr "Symptom:"
msgid "Test Environment"
msgstr "Testumgebung"
msgid "Test Scenario:"
msgstr "Testszenario:"
msgid "Test Scenarios:"
msgstr "Testszenarien:"
msgid "Testing"
msgstr "Testen"
msgid "Testing Expectations"
msgstr "Erwartungen testen"
msgid ""
"The goal of our resiliency tests for `OpenStack-Helm/Ceph <https://github."
"com/openstack/openstack-helm/tree/master/ceph>`_ is to show symptoms of "
"software/hardware failure and provide the solutions."
msgstr ""
"Das Ziel unserer Elastizitätstests für `OpenStack-Helm/Ceph <https://github."
"com/openstack/openstack-helm/tree/master/ceph>`_ soll Symptome von Software/"
"Hardware-Versagen zeigen und die Lösungen bereitstellen."
msgid ""
"The logs of the failed mon-pod shows the ceph-mon process cannot run as ``/"
"var/lib/ceph/mon/ceph-voyager3/store.db`` does not exist."
msgstr ""
"Die Protokolle des fehlgeschlagenen Mon-Pods zeigen, dass der Ceph-Mon-"
"Prozess nicht ausgeführt werden kann, da ``/var/lib/ceph/mon/ceph-voyager3/"
"store.db``` nicht existiert."
msgid ""
"The node status of ``voyager3`` changes to ``Ready`` after the node is up "
"again. Also, Ceph pods are restarted automatically. Ceph status shows that "
"the monitor running on ``voyager3`` is now in quorum."
msgstr ""
"Der Knotenstatus von ``voyager3`` ändert sich in ``Ready``, nachdem der "
"Knoten wieder geöffnet wurde. Außerdem werden Ceph-Pods automatisch neu "
"gestartet. Der Ceph-Status zeigt an, dass der Monitor, der auf ``voyager3`` "
"läuft, jetzt im Quorum ist."
msgid ""
"The node status of ``voyager3`` changes to ``Ready`` after the node is up "
"again. Also, Ceph pods are restarted automatically. The Ceph status shows "
"that the monitor running on ``voyager3`` is now in quorum and 6 osds gets "
"back up (i.e., a total of 24 osds are up)."
msgstr ""
"Der Knotenstatus von ``voyager3`` ändert sich in ``Ready``, nachdem der "
"Knoten wieder geöffnet wurde. Außerdem werden Ceph-Pods automatisch neu "
"gestartet. Der Ceph-Status zeigt an, dass der Monitor, der auf ``voyager3`` "
"läuft, jetzt im Quorum ist und 6 ods zurück geht (d.h. insgesamt 24 ods sind "
"aktiv)."
msgid ""
"The output of the Helm tests can be seen by looking at the logs of the pod "
"created by the Helm tests. These logs can be viewed with:"
msgstr ""
"Die Ergebnisse der Helm-Tests können Sie sehen, wenn Sie sich die Logs des "
"Pods ansehen, die mit den Helm-Tests erstellt wurden. Diese Protokolle "
"können angezeigt werden mit:"
msgid "The pod status of ceph-mon and ceph-osd shows as ``NodeLost``."
msgstr ""
"Der Pod-Status von ceph-mon und ceph-osd wird als ``NodeLost`` angezeigt."
msgid ""
"The status of the pods (where the three Monitor processes are killed) "
"changed as follows: ``Running`` -> ``Error`` -> ``CrashLoopBackOff`` -> "
"``Running`` and this recovery process takes about 1 minute."
msgstr ""
"Der Status der Pods (wo die drei Monitor-Prozesse beendet werden) hat sich "
"wie folgt geändert: ``Running`` -> ``Error`` -> ``CrashLoopBackOff`` -> "
"``Running`` und dieser Wiederherstellungsprozess dauert ungefähr 1 Minute."
msgid ""
"The status of the pods (where the two Monitor processes are killed) changed "
"as follows: ``Running`` -> ``Error`` -> ``CrashLoopBackOff`` -> ``Running`` "
"and this recovery process takes about 1 minute."
msgstr ""
"Der Status der Pods (wo die beiden Monitor-Prozesse beendet sind) hat sich "
"wie folgt geändert: ``Running`` -> ``Error`` -> ``CrashLoopBackOff`` -> "
"``Running`` und dieser Wiederherstellungsprozess dauert ungefähr 1 Minute."
msgid ""
"This guide documents steps showing Ceph version upgrade. The main goal of "
"this document is to demostrate Ceph chart update without downtime for OSH "
"components."
msgstr ""
"Dieser Leitfaden dokumentiert Schritte, die das Upgrade der Ceph-Version "
"zeigen. Das Hauptziel dieses Dokuments besteht darin, das Ceph-Diagramm-"
"Update ohne Ausfallzeiten für Arbeitsschutzkomponenten zu demonstrieren."
msgid ""
"This is for the case when a host machine (where ceph-mon is running) is down."
msgstr ""
"Dies ist der Fall, wenn eine Host-Maschine (auf der ceph-mon läuft) nicht "
"läuft."
msgid "This is to test a scenario when 1 out of 3 Monitor processes is down."
msgstr ""
"Dies dient zum Testen eines Szenarios, wenn 1 von 3 Überwachungsprozessen "
"ausfällt."
msgid ""
"This is to test a scenario when 2 out of 3 Monitor processes are down. To "
"bring down 2 Monitor processes (out of 3), we identify two Monitor processes "
"and kill them from the 2 monitor hosts (not a pod)."
msgstr ""
"Dies dient dazu, ein Szenario zu testen, wenn 2 von 3 Monitor-Prozessen "
"ausgefallen sind. Um 2 Monitor-Prozesse (von 3) zu reduzieren, "
"identifizieren wir zwei Monitor-Prozesse und töten sie von den 2 Monitor-"
"Hosts (kein Pod)."
msgid ""
"This is to test a scenario when 3 out of 3 Monitor processes are down. To "
"bring down 3 Monitor processes (out of 3), we identify all 3 Monitor "
"processes and kill them from the 3 monitor hosts (not pods)."
msgstr ""
"Dies dient zum Testen eines Szenarios, wenn 3 von 3 Monitor-Prozessen nicht "
"verfügbar sind. Um 3 Monitor-Prozesse (von 3) zu reduzieren, identifizieren "
"wir alle 3 Monitor-Prozesse und töten sie von den 3 Monitor-Hosts (nicht "
"Pods)."
msgid ""
"This is to test a scenario when a disk failure happens. We monitor the ceph "
"status and notice one OSD (osd.2) on voyager4 which has ``/dev/sdh`` as a "
"backend is down."
msgstr ""
"Dies dient zum Testen eines Szenarios, wenn ein Festplattenfehler auftritt. "
"Wir überwachen den Ceph-Status und bemerken ein OSD (osd.2) auf voyager4, "
"das ``/dev/sdh`` hat, da ein Backend nicht läuft."
msgid "This is to test a scenario when some of the OSDs are down."
msgstr ""
"Dies dient dazu, ein Szenario zu testen, wenn einige der OSDs nicht "
"verfügbar sind."
msgid ""
"To bring down 1 Monitor process (out of 3), we identify a Monitor process "
"and kill it from the monitor host (not a pod)."
msgstr ""
"Um einen Monitor-Prozess (von 3) zu reduzieren, identifizieren wir einen "
"Monitor-Prozess und töten ihn vom Monitor-Host (kein Pod)."
msgid ""
"To bring down 6 OSDs (out of 24), we identify the OSD processes and kill "
"them from a storage host (not a pod)."
msgstr ""
"Um 6 OSDs (von 24) zu reduzieren, identifizieren wir die OSD-Prozesse und "
"löschen sie von einem Storage-Host (nicht einem Pod)."
msgid "Update Ceph Client chart with new overrides:"
msgstr "Aktualisieren Sie das Ceph-Client-Diagramm mit neuen Überschreibungen:"
msgid "Update Ceph Mon chart with new overrides"
msgstr "Aktualisieren Sie das Ceph Mon-Chart mit neuen Überschreibungen"
msgid "Update Ceph OSD chart with new overrides:"
msgstr "Aktualisieren Sie das Ceph-OSD-Diagramm mit neuen Überschreibungen:"
msgid "Update Ceph Provisioners chart with new overrides:"
msgstr ""
"Aktualisieren Sie das Ceph Provisioners-Chart mit neuen Überschreibungen:"
msgid ""
"Update ceph install script ``./tools/deployment/multinode/030-ceph.sh`` to "
"add ``images:`` section in overrides as shown below."
msgstr ""
"Aktualisieren Sie ceph install script ``./tools/deployment/multinode/ 030-"
"ceph.sh``, um ``images:`` in Überschreibungen hinzuzufügen, wie unten "
"gezeigt."
msgid ""
"Update, image section in new overrides ``ceph-update.yaml`` as shown below"
msgstr ""
"Update, Abbildausschnitt in neuen überschreibt ``ceph-update.yaml`` wie "
"unten gezeigt"
msgid "Upgrade Ceph charts to update version"
msgstr "Aktualisieren Sie Ceph-Charts, um die Version zu aktualisieren"
msgid ""
"Upgrade Ceph charts to version 12.2.5 by updating docker images in overrides."
msgstr ""
"Aktualisieren Sie Ceph-Diagramme auf Version 12.2.5, indem Sie Docker-"
"Abbilder in Overrides aktualisieren."
msgid ""
"Upgrade Ceph component version from ``12.2.4`` to ``12.2.5`` without "
"downtime to OSH components."
msgstr ""
"Aktualisieren Sie die Ceph-Komponentenversion von ``12.2.4`` nach ``12.2.5`` "
"ohne Ausfallzeiten für die OSH Komponenten."
msgid ""
"Use Ceph override file ``ceph.yaml`` that was generated previously and "
"update images section as below"
msgstr ""
"Verwenden Sie die zuvor generierte Ceph Override-Datei ``ceph.yaml`` und "
"aktualisieren Sie den Abbildbereich wie folgt"
msgid ""
"Validate the Ceph status (i.e., one OSD is added, so the total number of "
"OSDs becomes 24):"
msgstr ""
"Überprüfen Sie den Ceph-Status (d.h., ein OSD wird hinzugefügt, so dass die "
"Gesamtzahl der OSDs 24 wird):"
msgid ""
"We also monitored the status of the Monitor pod through ``kubectl get pods -"
"n ceph``, and the status of the pod (where a Monitor process is killed) "
"changed as follows: ``Running`` -> ``Error`` -> ``Running`` and this "
"recovery process takes about 24 seconds."
msgstr ""
"Wir haben auch den Status des Monitor-Pods über ``kubectl get pods -n ceph`` "
"überwacht, und der Status des Pods (wo ein Monitor-Prozess beendet wird) hat "
"sich wie folgt geändert: ``Running`` -> ``Error`` -> ``Running`` und dieser "
"Wiederherstellungsprozess dauert ungefähr 24 Sekunden."
msgid ""
"We have 3 Monitors in this Ceph cluster, one on each of the 3 Monitor hosts."
msgstr ""
"Wir haben 3 Monitore in diesem Ceph-Cluster, einen auf jedem der 3 Monitor-"
"Hosts."
msgid ""
"We intentionlly destroy a Monitor database by removing ``/var/lib/openstack-"
"helm/ceph/mon/mon/ceph-voyager3/store.db``."
msgstr ""
"Wir zerstören absichtlich eine Monitor-Datenbank, indem wir ``/var/lib/"
"openstack-helm/ceph/mon/mon/ceph-voyager3/store.db`` entfernen."
msgid ""
"We monitored the status of Ceph Monitor pods and noted that the symptoms are "
"similar to when 1 or 2 Monitor processes are killed:"
msgstr ""
"Wir haben den Status von Ceph Monitor-Pods überwacht und festgestellt, dass "
"die Symptome ähnlich sind, wenn 1 oder 2 Monitor-Prozesse beendet werden:"
msgid ""
"We monitored the status of Ceph when the Monitor processes are killed and "
"noted that the symptoms are similar to when 1 Monitor process is killed:"
msgstr ""
"Wir haben den Status von Ceph überwacht, als die Überwachungsprozesse "
"beendet wurden, und festgestellt, dass die Symptome ähnlich sind, wenn 1 "
"Überwachungsprozess beendet wird:"
msgid "`Disk failure <./disk-failure.html>`_"
msgstr "`Festplattenfehler <./disk-failure.html>`_"
msgid "`Host failure <./host-failure.html>`_"
msgstr "`Hostfehler <./host-failure.html>`_"
msgid "`Monitor failure <./monitor-failure.html>`_"
msgstr "`Monitorfehler <./monitor-failure.html>`_"
msgid "`OSD failure <./osd-failure.html>`_"
msgstr "`OSD Fehler <./osd-failure.html>`_"
msgid "``Ceph MON Status:``"
msgstr "``Ceph MON Status:``"
msgid "``Ceph PODs:``"
msgstr "``Ceph PODs:``"
msgid "``Ceph PODs``"
msgstr "``Ceph PODs``"
msgid "``Ceph Status:``"
msgstr "``Ceph Status:``"
msgid "``Ceph quorum status:``"
msgstr "``Ceph Quorum Status:``"
msgid "``Ceph quorum status``"
msgstr "``Ceph Quorum Status``"
msgid "``Ceph status:``"
msgstr "``Ceph Status:``"
msgid "``Ceph status``"
msgstr "``Ceph Status``"
msgid "``OpenStack PODs:``"
msgstr "``OpenStack PODs:``"
msgid "``OpenStack PODs``"
msgstr "``OpenStack PODs``"
msgid "``Result/Observation:``"
msgstr "``Resultat/Observation:``"
msgid ""
"``Results:`` All provisioner pods got terminated at once (same time). Other "
"ceph pods are running. No interruption to OSH pods."
msgstr ""
"``Results: ``Alle Provisioner-Pods wurden gleichzeitig beendet (gleiche "
"Zeit). Andere Ceph-Kapseln laufen. Keine Unterbrechung der OSH-Pods."
msgid ""
"``Results:`` Mon pods got updated one by one (rolling updates). Each Mon pod "
"got respawn and was in 1/1 running state before next Mon pod got updated. "
"Each Mon pod got restarted. Other ceph pods were not affected with this "
"update. No interruption to OSH pods."
msgstr ""
"`` Ergebnisse: ``Mon-Pods wurden nacheinander aktualisiert (rollende "
"Updates). Jeder Mon-Pod wurde respawn und war im 1/1 Laufstatus, bevor der "
"nächste Mon-Pod aktualisiert wurde. Jeder Mon-Pod wurde neu gestartet. "
"Andere Ceph-Pods waren von diesem Update nicht betroffen. Keine "
"Unterbrechung der OSH-Pods."
msgid ""
"``Results:`` Rolling updates (one pod at a time). Other ceph pods are "
"running. No interruption to OSH pods."
msgstr ""
"`` Ergebnisse: ``Rollende Updates (jeweils ein Pod). Andere Ceph-Kapseln "
"laufen. Keine Unterbrechung der OSH-Pods."
msgid ""
"``ceph_bootstrap``, ``ceph-config_helper`` and ``ceph_rbs_pool`` images are "
"used for jobs. ``ceph_mon_check`` has one script that is stable so no need "
"to upgrade."
msgstr ""
"`ceph_bootstrap``, ``ceph-config_helper`` und ``ceph_rbs_pool`` Abbilder "
"werden für Jobs verwendet. ``ceph_mon_check`` hat ein Skript, das stabil "
"ist, also kein Upgrade nötig ist."
msgid "``cp /tmp/ceph.yaml ceph-update.yaml``"
msgstr "``cp /tmp/ceph.yaml ceph-update.yaml``"
msgid "``helm upgrade ceph-client ./ceph-client --values=ceph-update.yaml``"
msgstr "``helm upgrade ceph-client ./ceph-client --values=ceph-update.yaml``"
msgid "``helm upgrade ceph-mon ./ceph-mon --values=ceph-update.yaml``"
msgstr "`` helm upgrade ceph-mon ./ceph-mon --values=ceph-update.yaml``"
msgid "``helm upgrade ceph-osd ./ceph-osd --values=ceph-update.yaml``"
msgstr "``helm upgrade ceph-osd ./ceph-osd --values=ceph-update.yaml``"
msgid ""
"``helm upgrade ceph-provisioners ./ceph-provisioners --values=ceph-update."
"yaml``"
msgstr ""
"``helm upgrade ceph-provisioners ./ceph-provisioners --values=ceph-update."
"yaml``"
msgid "``series of console outputs:``"
msgstr "``Reihe der Konsolenausgaben:``"

View File

@ -1,210 +0,0 @@
# Frank Kloeker <eumel@arcor.de>, 2018. #zanata
# Andreas Jaeger <jaegerandi@gmail.com>, 2021. #zanata
msgid ""
msgstr ""
"Project-Id-Version: openstack-helm 0.1.1.dev3462\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2021-06-22 20:22+0000\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"PO-Revision-Date: 2021-04-16 08:41+0000\n"
"Last-Translator: Andreas Jaeger <jaegerandi@gmail.com>\n"
"Language-Team: German\n"
"Language: de\n"
"Plural-Forms: nplurals=2; plural=(n != 1)\n"
"X-Generator: Zanata 4.3.3\n"
msgid "Backing up a PVC"
msgstr "Ein PVC sichern"
msgid ""
"Backing up a PVC stored in Ceph, is fairly straigthforward, in this example "
"we use the PVC ``mysql-data-mariadb-server-0`` as an example, but this will "
"also apply to any other services using PVCs eg. RabbitMQ, Postgres."
msgstr ""
"Die Sicherung eines in Ceph gespeicherten PVCs ist ziemlich geradlinig, in "
"diesem Beispiel verwenden wir als Beispiel den PVC-Server ``mysql-data-"
"mariab-server-0``, aber dies gilt auch für alle anderen Dienste, die PVCs "
"verwenden, z. RabbitMQ, Postgres."
msgid ""
"Before proceeding, it is important to ensure that you have deployed a client "
"key in the namespace you wish to fulfill ``PersistentVolumeClaims``. To "
"verify that your deployment namespace has a client key:"
msgstr ""
"Bevor Sie fortfahren, müssen Sie sicherstellen, dass Sie einen "
"Clientschlüssel in dem Namespace implementiert haben, den Sie mit "
"``PersistentVolumeClaims`` erfüllen möchten. So überprüfen Sie, ob Ihr "
"Implementierungsnamespace über einen Clientschlüssel verfügt:"
msgid "Bugs and Feature requests"
msgstr "Bugs und Feature Anfragen"
msgid "Ceph"
msgstr "Ceph"
msgid "Ceph Deployment Status"
msgstr "Ceph-Bereitstellungsstatus"
msgid "Ceph Validating PVC Operation"
msgstr "Ceph Validierung des PVC-Betriebs"
msgid "Ceph Validating StorageClass"
msgstr "Ceph Validierung von StorageClass"
msgid "Channels"
msgstr "Kanäle"
msgid "Database Deployments"
msgstr "Datenbankbereitstellungen"
msgid ""
"First, we want to validate that Ceph is working correctly. This can be done "
"with the following Ceph command:"
msgstr ""
"Zuerst wollen wir bestätigen, dass Ceph korrekt funktioniert. Dies kann mit "
"dem folgenden Ceph-Befehl geschehen:"
msgid "Galera Cluster"
msgstr "Galera-Cluster"
msgid "Getting help"
msgstr "Hilfe bekommen"
msgid "Installation"
msgstr "Installation"
msgid "Join us on `Slack <http://slack.k8s.io/>`_ - #openstack-helm"
msgstr ""
"Begleiten Sie uns auf `Slack <http://slack.k8s.io/>`_ - #openstack-helm"
msgid ""
"Next we can look at the storage class, to make sure that it was created "
"correctly:"
msgstr ""
"Als nächstes können wir uns die Speicherklasse ansehen, um sicherzustellen, "
"dass sie korrekt erstellt wurde:"
msgid ""
"Note: This step is not relevant for PVCs within the same namespace Ceph was "
"deployed."
msgstr ""
"Hinweis: Dieser Schritt ist nicht relevant für PVCs in demselben Namespace, "
"in dem Ceph implementiert wurde."
msgid "Once this has been done the workload can be restarted."
msgstr "Sobald dies erledigt ist, kann die Arbeitslast neu gestartet werden."
msgid "PVC Preliminary Validation"
msgstr "PVC-Vorprüfung"
msgid "Persistent Storage"
msgstr "Dauerspeicher"
msgid ""
"Please, refer to `Contribution guidelines <../contributor/contributing."
"html>`_."
msgstr ""
"Lesen Sie die `Richtlinien für Mitwirkende <../contributor/contributing."
"html>`_."
msgid ""
"Restoring is just as straightforward. Once the workload consuming the device "
"has been stopped, and the raw RBD device removed the following will import "
"the back up and create a device:"
msgstr ""
"Das Wiederherstellen ist genauso einfach. Sobald die Arbeitslast, die das "
"Gerät verbraucht, beendet wurde und das RBD-Gerät entfernt wurde, wird das "
"Folgende in die Sicherung importiert und ein Gerät erstellt:"
msgid ""
"Sometimes things go wrong. These guides will help you solve many common "
"issues with the following:"
msgstr ""
"Manchmal gehen Dinge schief. Diese Handbücher helfen Ihnen bei der Lösung "
"vieler häufig auftretender Probleme:"
msgid ""
"The parameters are what we're looking for here. If we see parameters passed "
"to the StorageClass correctly, we will see the ``ceph-mon.ceph.svc.cluster."
"local:6789`` hostname/port, things like ``userid``, and appropriate secrets "
"used for volume claims."
msgstr ""
"Nach den Parametern suchen wir hier. Wenn wir sehen, dass die Parameter "
"korrekt an die StorageClass übergeben werden, sehen wir den ``ceph-mon.ceph."
"svc.cluster.local:6789`` Hostnamen/Port, Dinge wie ``userid`` und "
"entsprechende Secrets, die für Volume Claims verwendet werden ."
msgid ""
"This guide is to help users debug any general storage issues when deploying "
"Charts in this repository."
msgstr ""
"Dieser Leitfaden soll Benutzern helfen, allgemeine Speicherprobleme beim "
"Bereitstellen von Charts in diesem Repository zu beheben."
msgid ""
"This guide is to help users debug any general storage issues when deploying "
"charts in this repository."
msgstr ""
"Dieses Handbuch soll Benutzern helfen, allgemeine Speicherprobleme beim "
"Bereitstellen von Diagrammen in diesem Repository zu beheben."
msgid ""
"To deploy the HWE kernel, prior to deploying Kubernetes and OpenStack-Helm "
"the following commands should be run on each node:"
msgstr ""
"Zur Bereitstellung des HWE-Kernels sollten vor der Bereitstellung von "
"Kubernetes und OpenStack-Helm die folgenden Befehle auf jedem Knoten "
"ausgeführt werden:"
msgid ""
"To make use of CephFS in Ubuntu the HWE Kernel is required, until the issue "
"described `here <https://github.com/kubernetes-incubator/external-storage/"
"issues/345>`_ is fixed."
msgstr ""
"Um CephFS in Ubuntu nutzen zu können, wird der HWE-Kernel benötigt, bis das "
"Problem hier beschrieben wird <https://github.com/kubernetes-incubator/"
"external-storage/issues/345>`_ ist behoben."
msgid "To test MariaDB, do the following:"
msgstr "Um MariaDB zu testen, machen Sie folgendes:"
msgid ""
"To validate persistent volume claim (PVC) creation, we've placed a test "
"manifest `here <https://raw.githubusercontent.com/openstack/openstack-helm/"
"master/tests/pvc-test.yaml>`_. Deploy this manifest and verify the job "
"completes successfully."
msgstr ""
"Um die Erstellung eines persistenten Volumenanspruchs (PVC) zu validieren, "
"haben wir ein Testmanifest `hier platziert <https://raw.githubusercontent."
"com/openstack/openstack-helm/master/tests/pvc-test.yaml>`_. Stellen Sie "
"dieses Manifest bereit und überprüfen Sie, ob der Job erfolgreich "
"abgeschlossen wurde."
msgid "Troubleshooting"
msgstr "Fehlerbehebung"
msgid "Ubuntu HWE Kernel"
msgstr "Ubuntu HWE Kernel"
msgid ""
"Use one of your Ceph Monitors to check the status of the cluster. A couple "
"of things to note above; our health is `HEALTH\\_OK`, we have 3 mons, we've "
"established a quorum, and we can see that all of our OSDs are up and in the "
"OSD map."
msgstr ""
"Verwenden Sie einen Ihrer Ceph-Monitore, um den Status des Clusters zu "
"überprüfen. Ein paar Dinge zu beachten; unser Gesundheitszustand ist HEALTH "
"\\_OK`, wir haben 3 Mons, wir haben ein Quorum eingerichtet, und wir können "
"sehen, dass alle unsere OSDs in der OSD-Karte aufgeführt sind."
msgid ""
"Without this, your RBD-backed PVCs will never reach the ``Bound`` state. "
"For more information, see how to `activate namespace for ceph <../install/"
"multinode.html#activating-control-plane-namespace-for-ceph>`_."
msgstr ""
"Ohne dies werden Ihre RBD-unterstützten PVCs niemals den ``Bound`` -Zustand "
"erreichen. Weitere Informationen finden Sie unter `namespace für ceph "
"aktivieren <../install/multinode.html#activating-control-plane-namespace-for-"
"ceph>`_."

View File

@ -1,403 +0,0 @@
# Andreas Jaeger <jaegerandi@gmail.com>, 2018. #zanata
# Frank Kloeker <eumel@arcor.de>, 2018. #zanata
# Robert Simai <robert.simai@suse.com>, 2019. #zanata
# Andreas Jaeger <jaegerandi@gmail.com>, 2021. #zanata
msgid ""
msgstr ""
"Project-Id-Version: openstack-helm 0.1.1.dev3879\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2022-10-24 20:45+0000\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"PO-Revision-Date: 2021-04-16 08:40+0000\n"
"Last-Translator: Andreas Jaeger <jaegerandi@gmail.com>\n"
"Language-Team: German\n"
"Language: de\n"
"Plural-Forms: nplurals=2; plural=(n != 1)\n"
"X-Generator: Zanata 4.3.3\n"
msgid ":ref:`genindex`"
msgstr ":ref: `genindex`"
msgid ":ref:`search`"
msgstr ":ref: `suchen`"
msgid "Adding Services"
msgstr "Hinzufügen von Diensten"
msgid "Adding Tests"
msgstr "Hinzufügen von Tests"
msgid ""
"Any additional functions required for testing new charts or improving the "
"gate workflow should be placed in the appropriate location."
msgstr ""
"Alle zusätzlichen Funktionen, die zum Testen neuer Diagramme oder zum "
"Verbessern des Gate-Workflows erforderlich sind, sollten an der "
"entsprechenden Stelle platziert werden."
msgid ""
"Any tests that do not use the Rally testing framework would need to be "
"handled in the appropriate manner in launch script. This would ideally "
"result in new functions that could be reused, or expansion of the gate "
"scripts to include scenarios beyond basic service launches."
msgstr ""
"Alle Tests, die das Rally-Test-Framework nicht verwenden, müssen im Start-"
"Skript entsprechend behandelt werden. Dies würde idealerweise zu neuen "
"Funktionen führen, die wiederverwendet werden könnten, oder eine Erweiterung "
"der Gate-Scripts um Szenarien, die über die Einführung von Basisdiensten "
"hinausgehen."
msgid ""
"As charts for additional services are added to OpenStack-Helm, they should "
"be included in the gates. Adding new services to the gates allows a chart "
"developer and the review team to identify any potential issues associated "
"with a new service. All services are currently launched in the gate via a "
"series of launch scripts of the format ``NNN-service-name.sh`` where ``NNN`` "
"dictates the order these scripts are launched. The script should contain an "
"installation command like:"
msgstr ""
"Da Charts für zusätzliche Dienste zu OpenStack-Helm hinzugefügt werden, "
"sollten sie in den Gates enthalten sein. Durch Hinzufügen neuer Dienste zu "
"den Gates können ein Charts-Entwickler und das Überprüfungsteam potenzielle "
"Probleme identifizieren, die mit einem neuen Dienst verbunden sind. Alle "
"Dienste werden derzeit über eine Reihe von Start-Skripts im Format ``NNN-"
"service-name.sh`` gestartet, wobei ``NNN`` die Reihenfolge angibt, in der "
"diese Skripte gestartet werden. Das Skript sollte einen Installationsbefehl "
"enthalten wie:"
msgid ""
"As new charts are developed and the services are added to the gate, an "
"associated Helm test should be introduced to the gates. The appropriate "
"place for executing these tests is in the respective service's launch "
"script, and must be placed after the entry for installing the service and "
"any associated overrides. Any tests that use the Rally testing framework "
"should leverage the helm_test_deployment function in the aforementioned "
"funcs/helm.sh file. For example, a Helm test for Mistral might look like:"
msgstr ""
"Wenn neue Charts entwickelt werden und die Dienste dem gate hinzugefügt "
"werden, sollte ein zugehöriger Helm-Test zu den Gates eingeführt werden. Der "
"entsprechende Ort zum Ausführen dieser Tests befindet sich im Startskript "
"des jeweiligen Diensts und muss nach dem Eintrag für die Installation des "
"Diensts und den zugehörigen Überschreibungen platziert werden. Alle Tests, "
"die das Rally-Test-Framework verwenden, sollten die Funktion "
"helm_test_deployment in der oben genannten Datei funcs/helm.sh nutzen. Zum "
"Beispiel könnte ein Helm-Test für Mistral wie folgt aussehen:"
msgid ""
"Bugs and enhancements are tracked via OpenStack-Helm's `Storyboard <https://"
"storyboard.openstack.org/#!/project_group/64>`_."
msgstr ""
"Bugs und Verbesserungen werden über das Storyboard von OpenStack-Helm "
"verfolgt <https://storyboard.openstack.org/#!/project_group/64>`_."
msgid "Communication"
msgstr "Kommunikation"
msgid "Contents:"
msgstr "Inhalt:"
msgid "Contributing"
msgstr "Beitragend"
msgid ""
"Developers wishing to work on the OpenStack-Helm project should always base "
"their work on the latest code, available from the OpenStack-Helm git "
"repository."
msgstr ""
"Entwickler, welche am OpenStack-Helm Projekt mitarbeiten wollen, sollen "
"immer ihre Arbeit auf den aktuellen Code basieren, welcher im OpenStack-Helm "
"Git Repository verfügbar ist."
msgid ""
"Functions for Helm specific operations, found in helm.sh. These functions "
"include: installing Helm, serving a Helm repository locally, linting and "
"building all Helm charts, running Helm tests on a release, installing the "
"helm template plugin, and running the helm template plugin against a chart."
msgstr ""
"Funktionen für helmspezifische Operationen, gefunden in helm.sh. Zu diesen "
"Funktionen gehören: Helm installieren, ein Helm-Repository lokal "
"bereitstellen, alle Helm-Diagramme filtern und erstellen, Helm-Tests für ein "
"Release ausführen, das Helm-Vorlagen-Plugin installieren und das Helm-"
"Vorlagen-Plugin gegen ein Diagramm ausführen."
msgid ""
"Functions for Kubernetes specific operations, found in kube.sh. These "
"functions include: waiting for pods in a specific namespace to register as "
"ready, waiting for all nodes to register as ready, install the requirements "
"for the kubeadm-aio container used in the gates, building the kubeadm-aio "
"container, launching the kubeadm-aio container, and replacing the kube-"
"controller-manager with a specific image necessary for ceph functionality."
msgstr ""
"Funktionen für Kubernetes-spezifische Operationen, gefunden in kube.sh. Zu "
"diesen Funktionen gehören: Warten auf Pods in einem bestimmten Namespace, um "
"sich als bereit zu registrieren, Warten auf die Registrierung aller Knoten "
"als bereit, Installieren der Anforderungen für den in den Gates verwendeten "
"kubeadm-aio-Container, Erstellen des kubeadm-aio-Containers, Starten des "
"kubeadm-aio-Containers aio container, und ersetzen Sie den kube-controller-"
"manager durch ein spezielles Abbild, das für die ceph-Funktionalität "
"benötigt wird."
msgid ""
"Functions for OpenStack specific operations, found in openstack.sh. These "
"functions include: waiting for a successful ping, and waiting for a booted "
"virtual machine's status to return as ACTIVE."
msgstr ""
"Funktionen für OpenStack-spezifische Operationen, die in openstack.sh "
"enthalten sind. Zu diesen Funktionen gehören: Warten auf einen erfolgreichen "
"Ping und Warten auf den Status einer gestarteten virtuellen Maschine als "
"ACTIVE."
msgid "Functions for common host preparation operations, found in common.sh"
msgstr ""
"Funktionen für allgemeine Hostvorbereitungsoperationen, die unter common.sh "
"zu finden sind"
msgid ""
"Functions for network specific operations, found in network.sh. These "
"functions include: creating a backup of the host's resolv.conf file before "
"deploying the kubeadm environments, restoring the original resolv.conf "
"settings, creating a backup of the host's /etc/hosts file before adding the "
"hosts interface and address, and restoring the original /etc/hosts file."
msgstr ""
"Funktionen für netzwerkspezifische Operationen, gefunden in network.sh. Zu "
"diesen Funktionen gehören: Erstellen einer Sicherungskopie der resolv.conf-"
"Datei des Hosts vor dem Bereitstellen der kubeadm-Umgebungen, "
"Wiederherstellen der ursprünglichen resolv.conf-Einstellungen, Erstellen "
"einer Sicherungskopie der Datei /etc/hosts des Hosts vor dem Hinzufügen der "
"Hostschnittstelle und -adresse und Wiederherstellen der Original /etc/hosts "
"Datei."
msgid "Gate Checks"
msgstr "Gate Checks"
msgid "Gate Functions"
msgstr "Gate-Funktionen"
msgid "Gate Output"
msgstr "Gate-Ausgang"
msgid "Indices and Tables"
msgstr "Indizes und Tabellen"
msgid "Installation and Development"
msgstr "Installation und Entwicklung"
msgid ""
"Join us on `Slack <https://kubernetes.slack.com/messages/C3WERB7DE/>`_ - "
"#openstack-helm"
msgstr ""
"Begleiten Sie uns auf `Slack <https://kubernetes.slack.com/messages/"
"C3WERB7DE/>`_ - #openstack-helm"
msgid ""
"Meeting Agenda Items: `Agenda <https://etherpad.openstack.org/p/openstack-"
"helm-meeting-agenda>`_"
msgstr ""
"Tagesordnungspunkte: `Agenda <https://etherpad.openstack.org/p/openstack-"
"helm-meeting-agenda>`_"
msgid "Mission"
msgstr "Mission"
msgid "OpenStack-Helm"
msgstr "OpenStack-Helm"
msgid "OpenStack-Helm Gates"
msgstr "OpenStack-Helm Gates"
msgid "OpenStack-Helm currently checks the following scenarios:"
msgstr "OpenStack-Helm überprüft derzeit die folgenden Szenarien:"
msgid ""
"OpenStack-Helm's single node and multinode gates leverage the kubeadm-aio "
"environment created and maintained for use as a development environment. "
"All information regarding the kubeadm-aio environment can be found here_."
msgstr ""
"Die Single-Node- und Multinode-Gates von OpenStack-Helm nutzen die kubeadm-"
"aio-Umgebung, die zur Verwendung als Entwicklungsumgebung erstellt und "
"verwaltet wird. Alle Informationen zur kubeadm-aio-Umgebung finden Sie hier."
msgid ""
"Provisioning a multi-node Ubuntu-1604 cluster and deploying the OpenStack "
"services. This check is provided for both a two node cluster and a three "
"node cluster."
msgstr ""
"Bereitstellung eines Ubuntu-1604-Clusters mit mehreren Knoten und "
"Bereitstellung der OpenStack-Dienste. Diese Überprüfung wird sowohl für "
"einen Cluster mit zwei Knoten als auch für einen Cluster mit drei Knoten "
"bereitgestellt."
msgid ""
"Provisioning a single node cluster and deploying the OpenStack services. "
"This check is provided for: Ubuntu-1604, CentOS-7, and Fedora-25."
msgstr ""
"Bereitstellen eines einzelnen Knotenclusters und Bereitstellen der OpenStack-"
"Dienste. Dieser Check ist vorgesehen für: Ubuntu-1604, CentOS-7 und "
"Fedora-25."
msgid "Repository"
msgstr "Repository"
msgid ""
"Running Make on each chart, which lints and packages the charts. This gate "
"does not stand up a Kubernetes cluster."
msgstr ""
"Starte Make für jedes Chart, welches Charts mit Lint überprüft und packt. "
"Dieses Gate startet keinen Kubernetes-Cluster."
msgid ""
"Some services in the gate require specific overrides to the default values "
"in the chart's values.yaml file. If a service requires multiple overrides "
"to function in the gate, the service should include a separate values.yaml "
"file placed in the tools/overrides/mvp directory. The <service>.yaml MVP "
"files provide a configuration file to use for overriding default "
"configuration values in the chart's values.yaml as an alternative to "
"overriding individual values during installation. A chart that requires a "
"MVP overrides file requires the following format:"
msgstr ""
"Einige Dienste im Gate erfordern bestimmte Überschreibungen zu den "
"Standardwerten in der values.yaml-Datei des Charts. Wenn ein Dienst mehrere "
"Überschreibungen benötigt, um im Gate zu funktionieren, sollte der Dienst "
"eine separate Datei values.yaml enthalten, die im Verzeichnis tools/"
"overrides/mvp abgelegt ist. Die <service>.yaml MVP-Dateien bieten eine "
"Konfigurationsdatei, die zum Überschreiben von Standardkonfigurationswerten "
"in den values.yaml des Diagramms als Alternative zum Überschreiben einzelner "
"Werte während der Installation verwendet werden kann. Ein Diagramm, für das "
"eine MVP-Überschreibungsdatei erforderlich ist, muss das folgende Format "
"aufweisen:"
msgid "Storyboard"
msgstr "Storyboard"
msgid "Testing any documentation changes and impacts."
msgstr "Testen von Änderungen und Auswirkungen der Dokumentation"
msgid ""
"The K8s directory contains the logs and output of the Kubernetes objects. "
"It includes: pods, nodes, secrets, services, namespaces, configmaps, "
"deployments, daemonsets, and statefulsets. Descriptions for the state of "
"all resources during execution are found here, and this information can "
"prove valuable when debugging issues raised during a check. When a single "
"node or multi-node check fails, this is the first place to look. The logs "
"found here are helpful when the templates render correctly, but the services "
"are not functioning correctly, whether due to service configuration issues "
"or issues with the pods themselves."
msgstr ""
"Das Verzeichnis K8s enthält die Protokolle und die Ausgabe der Kubernetes-"
"Objekte. Dazu gehören: Pods, Knoten, Secrets, Services, Namespaces, "
"Configmaps, Bereitstellungen, Daemonsets und Statefulsets. Beschreibungen "
"für den Status aller Ressourcen während der Ausführung finden Sie hier. "
"Diese Informationen können sich beim Debuggen von Problemen während einer "
"Prüfung als nützlich erweisen. Wenn eine Prüfung mit einem einzelnen Knoten "
"oder mehreren Knoten fehlschlägt, sollten Sie zuerst nachsehen. Die hier "
"gefundenen Protokolle sind hilfreich, wenn die Vorlagen korrekt gerendert "
"werden, die Dienste jedoch nicht ordnungsgemäß funktionieren, unabhängig "
"davon, ob Probleme mit der Dienstkonfiguration oder Probleme mit den Pods "
"auftreten."
msgid ""
"The dry-runs directory contains the rendered output of Helm dry-run installs "
"on each of the OpenStack service charts. This gives visibility into the "
"manifests created by the templates with the supplied values. When the dry-"
"run gate fails, the reason should be apparent in the dry-runs output. The "
"logs found here are helpful in identifying issues resulting from using helm-"
"toolkit functions incorrectly or other rendering issues with gotpl."
msgstr ""
"Das Dry-runs-Verzeichnis enthält die gerenderte Ausgabe von Helm-Dry-Run-"
"Installationen auf jedem der OpenStack-Dienstchart. Dadurch erhalten Sie "
"Einblick in die Manifeste, die von den Vorlagen mit den angegebenen Werten "
"erstellt wurden. Wenn das Dry-run-Gate versagt, sollte der Grund in der Dry-"
"Run-Ausgabe offensichtlich sein. Die hier gefundenen Logs sind hilfreich, um "
"Probleme zu identifizieren, die sich aus der falschen Verwendung von Helm-"
"Toolkit-Funktionen oder anderen Rendering-Problemen mit gotpl ergeben."
msgid ""
"The goal of OpenStack-Helm is to provide a collection of Helm charts that "
"simply, resiliently, and flexibly deploy OpenStack and related services on "
"Kubernetes."
msgstr ""
"Das Ziel von OpenStack-Helm ist es, eine Sammlung von Helm-Charts zur "
"Verfügung zu stellen, die OpenStack und zugehörige Dienste auf Kubernetes "
"einfach, flexibel und flexibel bereitstellen."
msgid ""
"The nodes directory contains information about the node the gate tests are "
"running on in openstack-infra. This includes: the network interfaces, the "
"contents of iptables, the host's resolv.conf, and the kernel IP routing "
"table. These logs can be helpful when trying to identify issues with host "
"networking or other issues at the node level."
msgstr ""
"Das Knotenverzeichnis enthält Informationen zu dem Knoten, auf dem die Gate-"
"Tests in openstack-infra ausgeführt werden. Dazu gehören: die "
"Netzwerkschnittstellen, der Inhalt von iptables, die resolv.conf des Hosts "
"und die Kernel-IP-Routingtabelle. Diese Protokolle können hilfreich sein, "
"wenn Sie versuchen, Probleme mit dem Hostnetzwerk oder andere Probleme auf "
"Knotenebene zu identifizieren."
msgid ""
"This project is under active development. We encourage anyone interested in "
"OpenStack-Helm to review our `Installation <https://docs.openstack.org/"
"openstack-helm/latest/install/index.html>`_ documentation. Feel free to ask "
"questions or check out our current `Storyboard backlog <https://storyboard."
"openstack.org/#!/project_group/64>`_."
msgstr ""
"Dieses Projekt wird aktiv weiterentwickelt. Wir empfehlen jedem, der an "
"OpenStack-Helm interessiert ist, unsere `Installation` zu überprüfen "
"<https://docs.openstack.org/openstack-helm/latest/install/index.html>`_ "
"Dokumentation. Sie können Fragen stellen oder unseren aktuellen Storyboard-"
"Backlog lesen <https://storyboard.openstack.org/#!/project_group/64>`_."
msgid "This results in the gate running the following:"
msgstr "Dies führt dazu, dass das Gate folgendes ausführt:"
msgid ""
"To evaluate a multinode installation, follow the `Bare Metal <https://docs."
"openstack.org/openstack-helm/latest/install/multinode.html>`_ install guide."
msgstr ""
"Um eine Multinode-Installation zu evaluieren, folgen Sie dem Bare Metal "
"<https://docs.openstack.org/openstack-helm/latest/install/multinode.html>`_ "
"Installationsanleitung."
msgid ""
"To facilitate ease of testing and debugging, information regarding gates and "
"their functionality can be found here."
msgstr ""
"Um das Testen und Debuggen zu erleichtern, finden Sie hier Informationen zu "
"Gates und deren Funktionalität."
msgid ""
"To provide meaningful output from the gates, all information pertaining to "
"the components of the cluster and workflow are output to the logs directory "
"inside each gate. The contents of the log directory are as follows:"
msgstr ""
"Um eine sinnvolle Ausgabe von den Gates bereitzustellen, werden alle "
"Informationen bezüglich der Komponenten des Clusters und des Arbeitsablaufs "
"in das Protokollverzeichnis innerhalb jedes Gates ausgegeben. Der Inhalt des "
"Protokollverzeichnisses ist wie folgt:"
msgid ""
"To provide reusable components for gate functionality, functions have been "
"provided in the gates/funcs directory. These functions include:"
msgstr ""
"Um wiederverwendbare Komponenten für die Gate-Funktionalität "
"bereitzustellen, wurden Funktionen im Verzeichnis gates/funcs "
"bereitgestellt. Diese Funktionen umfassen:"
msgid ""
"We welcome contributions. Check out `this <CONTRIBUTING.rst>`_ document if "
"you would like to get involved."
msgstr ""
"Wir freuen uns über Beiträge. Schauen Sie sich `dieses <CONTRIBUTING.rst>`_ "
"Dokument um, falls Sie mitmachen wollen."
msgid "Welcome to OpenStack-Helm's documentation!"
msgstr "Willkommen zur Dokumentation von OpenStack-Helm!"
msgid ""
"`OpenStack-Helm git repository <https://opendev.org/openstack/openstack-helm/"
">`_"
msgstr ""
"`OpenStack-Helm git Repository <https://opendev.org/openstack/openstack-helm/"
">`_"

View File

@ -1,175 +0,0 @@
# Andi Chandler <andi@gowling.com>, 2020. #zanata
# Andi Chandler <andi@gowling.com>, 2021. #zanata
msgid ""
msgstr ""
"Project-Id-Version: openstack-helm 0.1.1.dev3462\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2021-06-22 20:22+0000\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"PO-Revision-Date: 2021-06-24 03:48+0000\n"
"Last-Translator: Andi Chandler <andi@gowling.com>\n"
"Language-Team: English (United Kingdom)\n"
"Language: en_GB\n"
"X-Generator: Zanata 4.3.3\n"
"Plural-Forms: nplurals=2; plural=(n != 1)\n"
msgid ""
"Additional information could be found in `OpenDev Developer's Guide <https://"
"docs.opendev.org/opendev/infra-manual/latest/developers.html>`_."
msgstr ""
"Additional information could be found in `OpenDev Developer's Guide <https://"
"docs.opendev.org/opendev/infra-manual/latest/developers.html>`_."
msgid ""
"All common PTL duties are enumerated in the `PTL guide <https://docs."
"openstack.org/project-team-guide/ptl.html>`_."
msgstr ""
"All common PTL duties are enumerated in the `PTL guide <https://docs."
"openstack.org/project-team-guide/ptl.html>`_."
msgid ""
"Below will cover the more project specific information you need to get "
"started with OpenStack-Helm."
msgstr ""
"Below will cover the more project specific information you need to get "
"started with OpenStack-Helm."
msgid "Bugs should be filed as stories in Storyboard, not GitHub."
msgstr "Bugs should be filed as stories in Storyboard, not GitHub."
msgid ""
"Changes affecting code base often require CI tests and documentation to be "
"added in the same patch set."
msgstr ""
"Changes affecting code base often require CI tests and documentation to be "
"added in the same patch set."
msgid "Communication"
msgstr "Communication"
msgid ""
"Community `IRC Meetings <http://eavesdrop.openstack.org/#OpenStack-"
"Helm_Team_Meeting>`_: [Every Tuesday @ 3PM UTC], #openstack-meeting-alt on "
"oftc"
msgstr ""
"Community `IRC Meetings <http://eavesdrop.openstack.org/#OpenStack-"
"Helm_Team_Meeting>`_: [Every Tuesday @ 3PM UTC], #openstack-meeting-alt on "
"oftc"
msgid "Contacting the Core Team"
msgstr "Contacting the Core Team"
msgid ""
"For general information on contributing to OpenStack, please check out the "
"`contributor guide <https://docs.openstack.org/contributors/>`_ to get "
"started. It covers all the basics that are common to all OpenStack projects: "
"the accounts you need, the basics of interacting with our Gerrit review "
"system, how we communicate as a community, etc."
msgstr ""
"For general information on contributing to OpenStack, please check out the "
"`contributor guide <https://docs.openstack.org/contributors/>`_ to get "
"started. It covers all the basics that are common to all OpenStack projects: "
"the accounts you need, the basics of interacting with our Gerrit review "
"system, how we communicate as a community, etc."
msgid "Getting Your Patch Merged"
msgstr "Getting Your Patch Merged"
msgid ""
"If issue is on one of other OpenStack-Helm components, report it to the "
"appropriate `group Storyboard`_."
msgstr ""
"If issue is on one of other OpenStack-Helm components, report it to the "
"appropriate `group Storyboard`_."
msgid ""
"If you're looking for some smaller, easier work item to pick up and get "
"started on, search for the 'low-hanging-fruit' tag."
msgstr ""
"If you're looking for some smaller, easier work item to pick up and get "
"started on, search for the 'low-hanging-fruit' tag."
msgid ""
"Join us on `IRC <irc://chat.oftc.net/openstack-helm>`_: #openstack-helm on "
"oftc"
msgstr ""
"Join us on `IRC <irc://chat.oftc.net/openstack-helm>`_: #openstack-helm on "
"oftc"
msgid ""
"Join us on `Slack <https://kubernetes.slack.com/messages/C3WERB7DE/>`_ - "
"#openstack-helm"
msgstr ""
"Join us on `Slack <https://kubernetes.slack.com/messages/C3WERB7DE/>`_ - "
"#openstack-helm"
msgid ""
"Meeting Agenda Items: `Agenda <https://etherpad.openstack.org/p/openstack-"
"helm-meeting-agenda>`_"
msgstr ""
"Meeting Agenda Items: `Agenda <https://etherpad.openstack.org/p/openstack-"
"helm-meeting-agenda>`_"
msgid "New Feature Planning"
msgstr "New Feature Planning"
msgid ""
"New features are planned and implemented trough the process described in "
"`Project Specifications <../specs/index.html>`_ section of this document."
msgstr ""
"New features are planned and implemented trough the process described in "
"`Project Specifications <../specs/index.html>`_ section of this document."
msgid ""
"Other OpenStack-Helm component's tasks could be found on the `group "
"Storyboard`_."
msgstr ""
"Other OpenStack-Helm component's tasks could be found on the `group "
"Storyboard`_."
msgid "Project Team Lead Duties"
msgstr "Project Team Lead Duties"
msgid ""
"Project's Core Team could be contacted via IRC or Slack, usually during "
"weekly meetings. List of current Cores could be found on a Members tab of "
"`openstack-helm-core <https://review.opendev.org/#/admin/groups/1749,info>`_ "
"Gerrit group."
msgstr ""
"Project's Core Team could be contacted via IRC or Slack, usually during "
"weekly meetings. List of current Cores could be found on a Members tab of "
"`openstack-helm-core <https://review.opendev.org/#/admin/groups/1749,info>`_ "
"Gerrit group."
msgid "Pull requests submitted through GitHub will be ignored."
msgstr "Pull requests submitted through GitHub will be ignored."
msgid "Reporting a Bug"
msgstr "Reporting a Bug"
msgid "So You Want to Contribute..."
msgstr "So You Want to Contribute..."
msgid "Task Tracking"
msgstr "Task Tracking"
msgid ""
"We require two Code-Review +2's from reviewers, before getting your patch "
"merged with giving Workforce +1. Trivial patches (e.g. typos) could be "
"merged with one Code-Review +2."
msgstr ""
"We require two Code-Review +2's from reviewers, before getting your patch "
"merged with giving Workforce +1. Trivial patches (e.g. typos) could be "
"merged with one Code-Review +2."
msgid "We track our tasks on our StoryBoard_."
msgstr "We track our tasks on our StoryBoard_."
msgid ""
"You found an issue and want to make sure we are aware of it? You can do so "
"on our Storyboard_."
msgstr ""
"You found an issue and want to make sure we are aware of it? You can do so "
"on our Storyboard_."

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

View File

@ -1,212 +0,0 @@
# Andi Chandler <andi@gowling.com>, 2018. #zanata
# Andi Chandler <andi@gowling.com>, 2020. #zanata
# Andi Chandler <andi@gowling.com>, 2021. #zanata
msgid ""
msgstr ""
"Project-Id-Version: openstack-helm 0.1.1.dev3462\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2021-06-22 20:22+0000\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"PO-Revision-Date: 2021-06-24 03:47+0000\n"
"Last-Translator: Andi Chandler <andi@gowling.com>\n"
"Language-Team: English (United Kingdom)\n"
"Language: en_GB\n"
"X-Generator: Zanata 4.3.3\n"
"Plural-Forms: nplurals=2; plural=(n != 1)\n"
msgid "Backing up a PVC"
msgstr "Backing up a PVC"
msgid ""
"Backing up a PVC stored in Ceph, is fairly straigthforward, in this example "
"we use the PVC ``mysql-data-mariadb-server-0`` as an example, but this will "
"also apply to any other services using PVCs eg. RabbitMQ, Postgres."
msgstr ""
"Backing up a PVC stored in Ceph, is fairly straightforward, in this example "
"we use the PVC ``mysql-data-mariadb-server-0`` as an example, but this will "
"also apply to any other services using PVCs e.g. RabbitMQ, Postgres."
msgid ""
"Before proceeding, it is important to ensure that you have deployed a client "
"key in the namespace you wish to fulfill ``PersistentVolumeClaims``. To "
"verify that your deployment namespace has a client key:"
msgstr ""
"Before proceeding, it is important to ensure that you have deployed a client "
"key in the namespace you wish to fulfil ``PersistentVolumeClaims``. To "
"verify that your deployment namespace has a client key:"
msgid "Bugs and Feature requests"
msgstr "Bugs and Feature requests"
msgid "Ceph"
msgstr "Ceph"
msgid "Ceph Deployment Status"
msgstr "Ceph Deployment Status"
msgid "Ceph Validating PVC Operation"
msgstr "Ceph Validating PVC Operation"
msgid "Ceph Validating StorageClass"
msgstr "Ceph Validating StorageClass"
msgid "Channels"
msgstr "Channels"
msgid "Database Deployments"
msgstr "Database Deployments"
msgid ""
"First, we want to validate that Ceph is working correctly. This can be done "
"with the following Ceph command:"
msgstr ""
"First, we want to validate that Ceph is working correctly. This can be done "
"with the following Ceph command:"
msgid "Galera Cluster"
msgstr "Galera Cluster"
msgid "Getting help"
msgstr "Getting help"
msgid "Installation"
msgstr "Installation"
msgid ""
"Join us on `IRC <irc://chat.oftc.net/openstack-helm>`_: #openstack-helm on "
"oftc"
msgstr ""
"Join us on `IRC <irc://chat.oftc.net/openstack-helm>`_: #openstack-helm on "
"oftc"
msgid "Join us on `Slack <http://slack.k8s.io/>`_ - #openstack-helm"
msgstr "Join us on `Slack <http://slack.k8s.io/>`_ - #openstack-helm"
msgid ""
"Next we can look at the storage class, to make sure that it was created "
"correctly:"
msgstr ""
"Next we can look at the storage class, to make sure that it was created "
"correctly:"
msgid ""
"Note: This step is not relevant for PVCs within the same namespace Ceph was "
"deployed."
msgstr ""
"Note: This step is not relevant for PVCs within the same namespace Ceph was "
"deployed."
msgid "Once this has been done the workload can be restarted."
msgstr "Once this has been done the workload can be restarted."
msgid "PVC Preliminary Validation"
msgstr "PVC Preliminary Validation"
msgid "Persistent Storage"
msgstr "Persistent Storage"
msgid ""
"Please, refer to `Contribution guidelines <../contributor/contributing."
"html>`_."
msgstr ""
"Please, refer to `Contribution guidelines <../contributor/contributing."
"html>`_."
msgid ""
"Restoring is just as straightforward. Once the workload consuming the device "
"has been stopped, and the raw RBD device removed the following will import "
"the back up and create a device:"
msgstr ""
"Restoring is just as straightforward. Once the workload consuming the device "
"has been stopped, and the raw RBD device removed the following will import "
"the back up and create a device:"
msgid ""
"Sometimes things go wrong. These guides will help you solve many common "
"issues with the following:"
msgstr ""
"Sometimes things go wrong. These guides will help you solve many common "
"issues with the following:"
msgid ""
"The parameters are what we're looking for here. If we see parameters passed "
"to the StorageClass correctly, we will see the ``ceph-mon.ceph.svc.cluster."
"local:6789`` hostname/port, things like ``userid``, and appropriate secrets "
"used for volume claims."
msgstr ""
"The parameters are what we're looking for here. If we see parameters passed "
"to the StorageClass correctly, we will see the ``ceph-mon.ceph.svc.cluster."
"local:6789`` hostname/port, things like ``userid``, and appropriate secrets "
"used for volume claims."
msgid ""
"This guide is to help users debug any general storage issues when deploying "
"Charts in this repository."
msgstr ""
"This guide is to help users debug any general storage issues when deploying "
"Charts in this repository."
msgid ""
"This guide is to help users debug any general storage issues when deploying "
"charts in this repository."
msgstr ""
"This guide is to help users debug any general storage issues when deploying "
"charts in this repository."
msgid ""
"To deploy the HWE kernel, prior to deploying Kubernetes and OpenStack-Helm "
"the following commands should be run on each node:"
msgstr ""
"To deploy the HWE kernel, prior to deploying Kubernetes and OpenStack-Helm "
"the following commands should be run on each node:"
msgid ""
"To make use of CephFS in Ubuntu the HWE Kernel is required, until the issue "
"described `here <https://github.com/kubernetes-incubator/external-storage/"
"issues/345>`_ is fixed."
msgstr ""
"To make use of CephFS in Ubuntu the HWE Kernel is required, until the issue "
"described `here <https://github.com/kubernetes-incubator/external-storage/"
"issues/345>`_ is fixed."
msgid "To test MariaDB, do the following:"
msgstr "To test MariaDB, do the following:"
msgid ""
"To validate persistent volume claim (PVC) creation, we've placed a test "
"manifest `here <https://raw.githubusercontent.com/openstack/openstack-helm/"
"master/tests/pvc-test.yaml>`_. Deploy this manifest and verify the job "
"completes successfully."
msgstr ""
"To validate persistent volume claim (PVC) creation, we've placed a test "
"manifest `here <https://raw.githubusercontent.com/openstack/openstack-helm/"
"master/tests/pvc-test.yaml>`_. Deploy this manifest and verify the job "
"completes successfully."
msgid "Troubleshooting"
msgstr "Troubleshooting"
msgid "Ubuntu HWE Kernel"
msgstr "Ubuntu HWE Kernel"
msgid ""
"Use one of your Ceph Monitors to check the status of the cluster. A couple "
"of things to note above; our health is `HEALTH\\_OK`, we have 3 mons, we've "
"established a quorum, and we can see that all of our OSDs are up and in the "
"OSD map."
msgstr ""
"Use one of your Ceph Monitors to check the status of the cluster. A couple "
"of things to note above; our health is `HEALTH\\_OK`, we have 3 mons, we've "
"established a quorum, and we can see that all of our OSDs are up and in the "
"OSD map."
msgid ""
"Without this, your RBD-backed PVCs will never reach the ``Bound`` state. "
"For more information, see how to `activate namespace for ceph <../install/"
"multinode.html#activating-control-plane-namespace-for-ceph>`_."
msgstr ""
"Without this, your RBD-backed PVCs will never reach the ``Bound`` state. "
"For more information, see how to `activate namespace for Ceph <../install/"
"multinode.html#activating-control-plane-namespace-for-ceph>`_."

View File

@ -1,410 +0,0 @@
# Andi Chandler <andi@gowling.com>, 2018. #zanata
# Andi Chandler <andi@gowling.com>, 2019. #zanata
# Andi Chandler <andi@gowling.com>, 2020. #zanata
# Andi Chandler <andi@gowling.com>, 2021. #zanata
# Andi Chandler <andi@gowling.com>, 2022. #zanata
msgid ""
msgstr ""
"Project-Id-Version: openstack-helm 0.1.1.dev3879\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2022-10-24 20:45+0000\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"PO-Revision-Date: 2022-11-07 02:36+0000\n"
"Last-Translator: Andi Chandler <andi@gowling.com>\n"
"Language-Team: English (United Kingdom)\n"
"Language: en_GB\n"
"X-Generator: Zanata 4.3.3\n"
"Plural-Forms: nplurals=2; plural=(n != 1)\n"
msgid ":ref:`genindex`"
msgstr ":ref:`genindex`"
msgid ":ref:`search`"
msgstr ":ref:`search`"
msgid "Adding Services"
msgstr "Adding Services"
msgid "Adding Tests"
msgstr "Adding Tests"
msgid ""
"Any additional functions required for testing new charts or improving the "
"gate workflow should be placed in the appropriate location."
msgstr ""
"Any additional functions required for testing new charts or improving the "
"gate workflow should be placed in the appropriate location."
msgid ""
"Any tests that do not use the Rally testing framework would need to be "
"handled in the appropriate manner in launch script. This would ideally "
"result in new functions that could be reused, or expansion of the gate "
"scripts to include scenarios beyond basic service launches."
msgstr ""
"Any tests that do not use the Rally testing framework would need to be "
"handled in the appropriate manner in launch script. This would ideally "
"result in new functions that could be reused, or expansion of the gate "
"scripts to include scenarios beyond basic service launches."
msgid ""
"As charts for additional services are added to OpenStack-Helm, they should "
"be included in the gates. Adding new services to the gates allows a chart "
"developer and the review team to identify any potential issues associated "
"with a new service. All services are currently launched in the gate via a "
"series of launch scripts of the format ``NNN-service-name.sh`` where ``NNN`` "
"dictates the order these scripts are launched. The script should contain an "
"installation command like:"
msgstr ""
"As charts for additional services are added to OpenStack-Helm, they should "
"be included in the gates. Adding new services to the gates allows a chart "
"developer and the review team to identify any potential issues associated "
"with a new service. All services are currently launched in the gate via a "
"series of launch scripts of the format ``NNN-service-name.sh`` where ``NNN`` "
"dictates the order these scripts are launched. The script should contain an "
"installation command like:"
msgid ""
"As new charts are developed and the services are added to the gate, an "
"associated Helm test should be introduced to the gates. The appropriate "
"place for executing these tests is in the respective service's launch "
"script, and must be placed after the entry for installing the service and "
"any associated overrides. Any tests that use the Rally testing framework "
"should leverage the helm_test_deployment function in the aforementioned "
"funcs/helm.sh file. For example, a Helm test for Mistral might look like:"
msgstr ""
"As new charts are developed and the services are added to the gate, an "
"associated Helm test should be introduced to the gates. The appropriate "
"place for executing these tests is in the respective service's launch "
"script, and must be placed after the entry for installing the service and "
"any associated overrides. Any tests that use the Rally testing framework "
"should leverage the helm_test_deployment function in the aforementioned "
"funcs/helm.sh file. For example, a Helm test for Mistral might look like:"
msgid ""
"Bugs and enhancements are tracked via OpenStack-Helm's `Storyboard <https://"
"storyboard.openstack.org/#!/project_group/64>`_."
msgstr ""
"Bugs and enhancements are tracked via OpenStack-Helm's `Storyboard <https://"
"storyboard.openstack.org/#!/project_group/64>`_."
msgid "Communication"
msgstr "Communication"
msgid ""
"Community `IRC Meetings <http://eavesdrop.openstack.org/#OpenStack-"
"Helm_Team_Meeting>`_: [Every Tuesday @ 1500 UTC], #openstack-helm in IRC "
"(OFTC)"
msgstr ""
"Community `IRC Meetings <http://eavesdrop.openstack.org/#OpenStack-"
"Helm_Team_Meeting>`_: [Every Tuesday @ 1500 UTC], #openstack-helm in IRC "
"(OFTC)"
msgid "Contents:"
msgstr "Contents:"
msgid "Contributing"
msgstr "Contributing"
msgid ""
"Developers wishing to work on the OpenStack-Helm project should always base "
"their work on the latest code, available from the OpenStack-Helm git "
"repository."
msgstr ""
"Developers wishing to work on the OpenStack-Helm project should always base "
"their work on the latest code, available from the OpenStack-Helm git "
"repository."
msgid ""
"Functions for Helm specific operations, found in helm.sh. These functions "
"include: installing Helm, serving a Helm repository locally, linting and "
"building all Helm charts, running Helm tests on a release, installing the "
"helm template plugin, and running the helm template plugin against a chart."
msgstr ""
"Functions for Helm specific operations, found in helm.sh. These functions "
"include: installing Helm, serving a Helm repository locally, linting and "
"building all Helm charts, running Helm tests on a release, installing the "
"helm template plugin, and running the helm template plugin against a chart."
msgid ""
"Functions for Kubernetes specific operations, found in kube.sh. These "
"functions include: waiting for pods in a specific namespace to register as "
"ready, waiting for all nodes to register as ready, install the requirements "
"for the kubeadm-aio container used in the gates, building the kubeadm-aio "
"container, launching the kubeadm-aio container, and replacing the kube-"
"controller-manager with a specific image necessary for ceph functionality."
msgstr ""
"Functions for Kubernetes specific operations, found in kube.sh. These "
"functions include: waiting for pods in a specific namespace to register as "
"ready, waiting for all nodes to register as ready, install the requirements "
"for the kubeadm-aio container used in the gates, building the kubeadm-aio "
"container, launching the kubeadm-aio container, and replacing the kube-"
"controller-manager with a specific image necessary for Ceph functionality."
msgid ""
"Functions for OpenStack specific operations, found in openstack.sh. These "
"functions include: waiting for a successful ping, and waiting for a booted "
"virtual machine's status to return as ACTIVE."
msgstr ""
"Functions for OpenStack specific operations, found in openstack.sh. These "
"functions include: waiting for a successful ping, and waiting for a booted "
"virtual machine's status to return as ACTIVE."
msgid "Functions for common host preparation operations, found in common.sh"
msgstr "Functions for common host preparation operations, found in common.sh"
msgid ""
"Functions for network specific operations, found in network.sh. These "
"functions include: creating a backup of the host's resolv.conf file before "
"deploying the kubeadm environments, restoring the original resolv.conf "
"settings, creating a backup of the host's /etc/hosts file before adding the "
"hosts interface and address, and restoring the original /etc/hosts file."
msgstr ""
"Functions for network specific operations, found in network.sh. These "
"functions include: creating a backup of the host's resolv.conf file before "
"deploying the kubeadm environments, restoring the original resolv.conf "
"settings, creating a backup of the host's /etc/hosts file before adding the "
"hosts interface and address, and restoring the original /etc/hosts file."
msgid "Gate Checks"
msgstr "Gate Checks"
msgid "Gate Functions"
msgstr "Gate Functions"
msgid "Gate Output"
msgstr "Gate Output"
msgid "Indices and Tables"
msgstr "Indices and Tables"
msgid "Installation and Development"
msgstr "Installation and Development"
msgid ""
"Join us on `IRC <irc://chat.oftc.net/openstack-helm>`_: #openstack-helm on "
"oftc"
msgstr ""
"Join us on `IRC <irc://chat.oftc.net/openstack-helm>`_: #openstack-helm on "
"oftc"
msgid ""
"Join us on `Slack <https://kubernetes.slack.com/messages/C3WERB7DE/>`_ - "
"#openstack-helm"
msgstr ""
"Join us on `Slack <https://kubernetes.slack.com/messages/C3WERB7DE/>`_ - "
"#openstack-helm"
msgid ""
"Meeting Agenda Items: `Agenda <https://etherpad.openstack.org/p/openstack-"
"helm-meeting-agenda>`_"
msgstr ""
"Meeting Agenda Items: `Agenda <https://etherpad.openstack.org/p/openstack-"
"helm-meeting-agenda>`_"
msgid "Mission"
msgstr "Mission"
msgid "OpenStack-Helm"
msgstr "OpenStack-Helm"
msgid "OpenStack-Helm Gates"
msgstr "OpenStack-Helm Gates"
msgid "OpenStack-Helm currently checks the following scenarios:"
msgstr "OpenStack-Helm currently checks the following scenarios:"
msgid ""
"OpenStack-Helm's single node and multinode gates leverage the kubeadm-aio "
"environment created and maintained for use as a development environment. "
"All information regarding the kubeadm-aio environment can be found here_."
msgstr ""
"OpenStack-Helm's single node and multinode gates leverage the kubeadm-aio "
"environment created and maintained for use as a development environment. "
"All information regarding the kubeadm-aio environment can be found here_."
msgid ""
"Please review our `documentation <https://docs.openstack.org/openstack-helm/"
"latest/>`_. For quick installation, evaluation, and convenience, we have a "
"minikube based all-in-one solution that runs in a Docker container. The set "
"up can be found `here <https://docs.openstack.org/openstack-helm/latest/"
"install/developer/index.html>`_."
msgstr ""
"Please review our `documentation <https://docs.openstack.org/openstack-helm/"
"latest/>`_. For quick installation, evaluation, and convenience, we have a "
"minikube based all-in-one solution that runs in a Docker container. The set "
"up can be found `here <https://docs.openstack.org/openstack-helm/latest/"
"install/developer/index.html>`_."
msgid ""
"Provisioning a multi-node Ubuntu-1604 cluster and deploying the OpenStack "
"services. This check is provided for both a two node cluster and a three "
"node cluster."
msgstr ""
"Provisioning a multi-node Ubuntu-1604 cluster and deploying the OpenStack "
"services. This check is provided for both a two node cluster and a three "
"node cluster."
msgid ""
"Provisioning a single node cluster and deploying the OpenStack services. "
"This check is provided for: Ubuntu-1604, CentOS-7, and Fedora-25."
msgstr ""
"Provisioning a single node cluster and deploying the OpenStack services. "
"This check is provided for: Ubuntu-1604, CentOS-7, and Fedora-25."
msgid "Repository"
msgstr "Repository"
msgid ""
"Running Make on each chart, which lints and packages the charts. This gate "
"does not stand up a Kubernetes cluster."
msgstr ""
"Running Make on each chart, which lints and packages the charts. This gate "
"does not stand up a Kubernetes cluster."
msgid ""
"Some services in the gate require specific overrides to the default values "
"in the chart's values.yaml file. If a service requires multiple overrides "
"to function in the gate, the service should include a separate values.yaml "
"file placed in the tools/overrides/mvp directory. The <service>.yaml MVP "
"files provide a configuration file to use for overriding default "
"configuration values in the chart's values.yaml as an alternative to "
"overriding individual values during installation. A chart that requires a "
"MVP overrides file requires the following format:"
msgstr ""
"Some services in the gate require specific overrides to the default values "
"in the chart's values.yaml file. If a service requires multiple overrides "
"to function in the gate, the service should include a separate values.yaml "
"file placed in the tools/overrides/mvp directory. The <service>.yaml MVP "
"files provide a configuration file to use for overriding default "
"configuration values in the chart's values.yaml as an alternative to "
"overriding individual values during installation. A chart that requires a "
"MVP overrides file requires the following format:"
msgid "Storyboard"
msgstr "Storyboard"
msgid "Testing any documentation changes and impacts."
msgstr "Testing any documentation changes and impacts."
msgid ""
"The K8s directory contains the logs and output of the Kubernetes objects. "
"It includes: pods, nodes, secrets, services, namespaces, configmaps, "
"deployments, daemonsets, and statefulsets. Descriptions for the state of "
"all resources during execution are found here, and this information can "
"prove valuable when debugging issues raised during a check. When a single "
"node or multi-node check fails, this is the first place to look. The logs "
"found here are helpful when the templates render correctly, but the services "
"are not functioning correctly, whether due to service configuration issues "
"or issues with the pods themselves."
msgstr ""
"The K8s directory contains the logs and output of the Kubernetes objects. "
"It includes: pods, nodes, secrets, services, namespaces, configmaps, "
"deployments, daemonsets, and statefulsets. Descriptions for the state of "
"all resources during execution are found here, and this information can "
"prove valuable when debugging issues raised during a check. When a single "
"node or multi-node check fails, this is the first place to look. The logs "
"found here are helpful when the templates render correctly, but the services "
"are not functioning correctly, whether due to service configuration issues "
"or issues with the pods themselves."
msgid ""
"The dry-runs directory contains the rendered output of Helm dry-run installs "
"on each of the OpenStack service charts. This gives visibility into the "
"manifests created by the templates with the supplied values. When the dry-"
"run gate fails, the reason should be apparent in the dry-runs output. The "
"logs found here are helpful in identifying issues resulting from using helm-"
"toolkit functions incorrectly or other rendering issues with gotpl."
msgstr ""
"The dry-runs directory contains the rendered output of Helm dry-run installs "
"on each of the OpenStack service charts. This gives visibility into the "
"manifests created by the templates with the supplied values. When the dry-"
"run gate fails, the reason should be apparent in the dry-runs output. The "
"logs found here are helpful in identifying issues resulting from using helm-"
"toolkit functions incorrectly or other rendering issues with gotpl."
msgid ""
"The goal of OpenStack-Helm is to provide a collection of Helm charts that "
"simply, resiliently, and flexibly deploy OpenStack and related services on "
"Kubernetes."
msgstr ""
"The goal of OpenStack-Helm is to provide a collection of Helm charts that "
"simply, resiliently, and flexibly deploy OpenStack and related services on "
"Kubernetes."
msgid ""
"The nodes directory contains information about the node the gate tests are "
"running on in openstack-infra. This includes: the network interfaces, the "
"contents of iptables, the host's resolv.conf, and the kernel IP routing "
"table. These logs can be helpful when trying to identify issues with host "
"networking or other issues at the node level."
msgstr ""
"The nodes directory contains information about the node the gate tests are "
"running on in openstack-infra. This includes: the network interfaces, the "
"contents of iptables, the host's resolv.conf, and the kernel IP routing "
"table. These logs can be helpful when trying to identify issues with host "
"networking or other issues at the node level."
msgid ""
"This project is under active development. We encourage anyone interested in "
"OpenStack-Helm to review our `Installation <https://docs.openstack.org/"
"openstack-helm/latest/install/index.html>`_ documentation. Feel free to ask "
"questions or check out our current `Storyboard backlog <https://storyboard."
"openstack.org/#!/project_group/64>`_."
msgstr ""
"This project is under active development. We encourage anyone interested in "
"OpenStack-Helm to review our `Installation <https://docs.openstack.org/"
"openstack-helm/latest/install/index.html>`_ documentation. Feel free to ask "
"questions or check out our current `Storyboard backlog <https://storyboard."
"openstack.org/#!/project_group/64>`_."
msgid "This results in the gate running the following:"
msgstr "This results in the gate running the following:"
msgid ""
"To evaluate a multinode installation, follow the `Bare Metal <https://docs."
"openstack.org/openstack-helm/latest/install/multinode.html>`_ install guide."
msgstr ""
"To evaluate a multinode installation, follow the `Bare Metal <https://docs."
"openstack.org/openstack-helm/latest/install/multinode.html>`_ install guide."
msgid ""
"To facilitate ease of testing and debugging, information regarding gates and "
"their functionality can be found here."
msgstr ""
"To facilitate ease of testing and debugging, information regarding gates and "
"their functionality can be found here."
msgid ""
"To provide meaningful output from the gates, all information pertaining to "
"the components of the cluster and workflow are output to the logs directory "
"inside each gate. The contents of the log directory are as follows:"
msgstr ""
"To provide meaningful output from the gates, all information pertaining to "
"the components of the cluster and workflow are output to the logs directory "
"inside each gate. The contents of the log directory are as follows:"
msgid ""
"To provide reusable components for gate functionality, functions have been "
"provided in the gates/funcs directory. These functions include:"
msgstr ""
"To provide reusable components for gate functionality, functions have been "
"provided in the gates/funcs directory. These functions include:"
msgid ""
"We welcome contributions. Check out `this <CONTRIBUTING.rst>`_ document if "
"you would like to get involved."
msgstr ""
"We welcome contributions. Check out `this <CONTRIBUTING.rst>`_ document if "
"you would like to get involved."
msgid "Welcome to OpenStack-Helm's documentation!"
msgstr "Welcome to OpenStack-Helm's documentation!"
msgid ""
"`OpenStack-Helm git repository <https://opendev.org/openstack/openstack-helm/"
">`_"
msgstr ""
"`OpenStack-Helm git repository <https://opendev.org/openstack/openstack-helm/"
">`_"

View File

@ -1,158 +0,0 @@
# suhartono <cloudsuhartono@gmail.com>, 2020. #zanata
msgid ""
msgstr ""
"Project-Id-Version: openstack-helm 0.1.1.dev3685\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2022-04-06 21:47+0000\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"PO-Revision-Date: 2020-05-09 05:05+0000\n"
"Last-Translator: suhartono <cloudsuhartono@gmail.com>\n"
"Language-Team: Indonesian\n"
"Language: id\n"
"X-Generator: Zanata 4.3.3\n"
"Plural-Forms: nplurals=1; plural=0\n"
msgid ""
"Additional information could be found in `OpenDev Developer's Guide <https://"
"docs.opendev.org/opendev/infra-manual/latest/developers.html>`_."
msgstr ""
"Informasi tambahan dapat ditemukan di `OpenDev Developer's Guide <https://"
"docs.opendev.org/opendev/infra-manual/latest/developers.html>`_."
msgid ""
"All common PTL duties are enumerated in the `PTL guide <https://docs."
"openstack.org/project-team-guide/ptl.html>`_."
msgstr ""
"Semua tugas PTL umum disebutkan dalam `PTL guide <https://docs.openstack.org/"
"project-team-guide/ptl.html>`_."
msgid ""
"Below will cover the more project specific information you need to get "
"started with OpenStack-Helm."
msgstr ""
"Di bawah ini akan mencakup informasi spesifik proyek lebih lanjut yang Anda "
"perlukan untuk memulai dengan OpenStack-Helm."
msgid "Bugs should be filed as stories in Storyboard, not GitHub."
msgstr "Bug harus diajukan sebagai cerita di Storyboard, bukan GitHub."
msgid ""
"Changes affecting code base often require CI tests and documentation to be "
"added in the same patch set."
msgstr ""
"Changes affecting code base often require CI tests and documentation to be "
"added in the same patch set."
msgid "Communication"
msgstr "Komunikasi"
msgid "Contacting the Core Team"
msgstr "Menghubungi Tim Inti (Core Team)"
msgid ""
"For general information on contributing to OpenStack, please check out the "
"`contributor guide <https://docs.openstack.org/contributors/>`_ to get "
"started. It covers all the basics that are common to all OpenStack projects: "
"the accounts you need, the basics of interacting with our Gerrit review "
"system, how we communicate as a community, etc."
msgstr ""
"Untuk informasi umum tentang kontribusi ke OpenStack, silakan periksa "
"`panduan kontributor <https://docs.openstack.org/contributors/>` _ untuk "
"memulai. Ini mencakup semua dasar-dasar yang umum untuk semua proyek "
"OpenStack: akun yang Anda butuhkan, dasar-dasar berinteraksi dengan sistem "
"ulasan Gerrit kami, cara kami berkomunikasi sebagai komunitas, dll."
msgid "Getting Your Patch Merged"
msgstr "Mendapatkan Patch Anda Digabung (Getting Your Patch Merged)"
msgid ""
"If issue is on one of other OpenStack-Helm components, report it to the "
"appropriate `group Storyboard`_."
msgstr ""
"Jika ada masalah pada salah satu komponen OpenStack-Helm lainnya, laporkan "
"ke `grup Storyboard`_ yang sesuai."
msgid ""
"If you're looking for some smaller, easier work item to pick up and get "
"started on, search for the 'low-hanging-fruit' tag."
msgstr ""
"Jika Anda mencari item pekerjaan yang lebih kecil dan lebih mudah untuk "
"diambil dan memulai, cari tag 'low-hanging-fruit'."
msgid ""
"Join us on `Slack <https://kubernetes.slack.com/messages/C3WERB7DE/>`_ - "
"#openstack-helm"
msgstr ""
"Bergabunglah dengan kami di `Slack <https://kubernetes.slack.com/messages/"
"C3WERB7DE/>`_ - #openstack-helm"
msgid ""
"Meeting Agenda Items: `Agenda <https://etherpad.openstack.org/p/openstack-"
"helm-meeting-agenda>`_"
msgstr ""
"Item Agenda Rapat: `Agenda <https://etherpad.openstack.org/p/openstack-helm-"
"meeting-agenda>`_"
msgid "New Feature Planning"
msgstr "Perencanaan Fitur Baru"
msgid ""
"New features are planned and implemented trough the process described in "
"`Project Specifications <../specs/index.html>`_ section of this document."
msgstr ""
"Fitur-fitur baru direncanakan dan diimplementasikan melalui proses yang "
"diuraikan dalam bagian `Project Specifications <../specs/index.html>`_ pada "
"dokumen ini."
msgid ""
"Other OpenStack-Helm component's tasks could be found on the `group "
"Storyboard`_."
msgstr ""
"Tugas komponen OpenStack-Helm lain dapat ditemukan di `group Storyboard`_."
msgid "Project Team Lead Duties"
msgstr "Project Team Lead Duties"
msgid ""
"Project's Core Team could be contacted via IRC or Slack, usually during "
"weekly meetings. List of current Cores could be found on a Members tab of "
"`openstack-helm-core <https://review.opendev.org/#/admin/groups/1749,info>`_ "
"Gerrit group."
msgstr ""
"Tim Inti Proyek dapat dihubungi melalui IRC atau Slack, biasanya selama "
"pertemuan mingguan. Daftar Core saat ini dapat ditemukan di tab Anggota "
"`openstack-helm-core <https://review.opendev.org/#/admin/groups/1749,info>` "
"_ grup Gerrit."
msgid "Pull requests submitted through GitHub will be ignored."
msgstr "Permintaan penarikan yang diajukan melalui GitHub akan diabaikan."
msgid "Reporting a Bug"
msgstr "Melaporkan Bug"
msgid "So You Want to Contribute..."
msgstr "Jadi Anda Ingin Berkontribusi ..."
msgid "Task Tracking"
msgstr "Pelacakan Tugas (Task Tracking)"
msgid ""
"We require two Code-Review +2's from reviewers, before getting your patch "
"merged with giving Workforce +1. Trivial patches (e.g. typos) could be "
"merged with one Code-Review +2."
msgstr ""
"Kami memerlukan dua Code-Review +2 dari reviewer, sebelum patch Anda "
"digabung dengan memberikan Workforce +1. Patches sepele (mis. Kesalahan "
"ketik) dapat digabung dengan satu Code-Review +2."
msgid "We track our tasks on our StoryBoard_."
msgstr "Kami melacak tugas Anda di StoryBoard Anda."
msgid ""
"You found an issue and want to make sure we are aware of it? You can do so "
"on our Storyboard_."
msgstr ""
"Anda menemukan masalah dan ingin memastikan kami mengetahuinya? Anda dapat "
"melakukannya di Storyboard_ kami."

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

View File

@ -1,207 +0,0 @@
# suhartono <cloudsuhartono@gmail.com>, 2018. #zanata
# suhartono <cloudsuhartono@gmail.com>, 2020. #zanata
msgid ""
msgstr ""
"Project-Id-Version: openstack-helm 0.1.1.dev3685\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2022-04-06 21:47+0000\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"PO-Revision-Date: 2020-05-08 08:25+0000\n"
"Last-Translator: suhartono <cloudsuhartono@gmail.com>\n"
"Language-Team: Indonesian\n"
"Language: id\n"
"X-Generator: Zanata 4.3.3\n"
"Plural-Forms: nplurals=1; plural=0\n"
msgid "Backing up a PVC"
msgstr "Mencadangkan PVC"
msgid ""
"Backing up a PVC stored in Ceph, is fairly straigthforward, in this example "
"we use the PVC ``mysql-data-mariadb-server-0`` as an example, but this will "
"also apply to any other services using PVCs eg. RabbitMQ, Postgres."
msgstr ""
"Mencadangkan PVC yang disimpan di Ceph, cukup ketat, dalam contoh ini kita "
"menggunakan PVC ``mysql-data-mariadb-server-0`` sebagai contoh, tetapi ini "
"juga akan berlaku untuk layanan lain yang menggunakan PVC misalnya. "
"RabbitMQ, Postgres."
msgid ""
"Before proceeding, it is important to ensure that you have deployed a client "
"key in the namespace you wish to fulfill ``PersistentVolumeClaims``. To "
"verify that your deployment namespace has a client key:"
msgstr ""
"Sebelum melanjutkan, penting untuk memastikan bahwa Anda telah menggunakan "
"kunci klien di ruang nama (namespace) yang ingin Anda penuhi "
"``PersistentVolumeClaims``. Untuk memverifikasi bahwa namespace penyebaran "
"Anda memiliki kunci klien:"
msgid "Bugs and Feature requests"
msgstr "Permintaan Bug dan Fitur"
msgid "Ceph"
msgstr "Ceph"
msgid "Ceph Deployment Status"
msgstr "Status Penerapan Ceph"
msgid "Ceph Validating PVC Operation"
msgstr "Ceph Memvalidasi Operasi PVC"
msgid "Ceph Validating StorageClass"
msgstr "Ceph Validating StorageClass"
msgid "Channels"
msgstr "Channels"
msgid "Database Deployments"
msgstr "Database Deployments"
msgid ""
"First, we want to validate that Ceph is working correctly. This can be done "
"with the following Ceph command:"
msgstr ""
"Pertama, kami ingin memvalidasi bahwa Ceph berfungsi dengan benar. Ini dapat "
"dilakukan dengan perintah Ceph berikut:"
msgid "Galera Cluster"
msgstr "Galera Cluster"
msgid "Getting help"
msgstr "Mendapatkan bantuan"
msgid "Installation"
msgstr "Instalasi"
msgid "Join us on `Slack <http://slack.k8s.io/>`_ - #openstack-helm"
msgstr ""
"Bergabunglah dengan kami `Slack <http://slack.k8s.io/>`_ - #openstack-helm"
msgid ""
"Next we can look at the storage class, to make sure that it was created "
"correctly:"
msgstr ""
"Selanjutnya kita dapat melihat kelas penyimpanan, untuk memastikan bahwa itu "
"dibuat dengan benar:"
msgid ""
"Note: This step is not relevant for PVCs within the same namespace Ceph was "
"deployed."
msgstr ""
"Catatan: Langkah ini tidak relevan untuk PVC dalam ruang nama (namespace) "
"yang sama Ceph dikerahkan."
msgid "Once this has been done the workload can be restarted."
msgstr "Setelah ini selesai, beban kerja (workload) dapat dimulai kembali."
msgid "PVC Preliminary Validation"
msgstr "Validasi Pendahuluan PVC"
msgid "Persistent Storage"
msgstr "Penyimpanan Persisten"
msgid ""
"Please, refer to `Contribution guidelines <../contributor/contributing."
"html>`_."
msgstr ""
"Silakan merujuk `Contribution guidelines <../contributor/contributing."
"html>`_."
msgid ""
"Restoring is just as straightforward. Once the workload consuming the device "
"has been stopped, and the raw RBD device removed the following will import "
"the back up and create a device:"
msgstr ""
"Memulihkan sama mudahnya. Setelah beban kerja yang memakan perangkat telah "
"dihentikan, dan perangkat RBD mentah yang dihapus berikut ini akan mengimpor "
"cadangan dan membuat perangkat:"
msgid ""
"Sometimes things go wrong. These guides will help you solve many common "
"issues with the following:"
msgstr ""
"Terkadang ada yang salah. Panduan ini akan membantu Anda memecahkan banyak "
"masalah umum dengan hal-hal berikut:"
msgid ""
"The parameters are what we're looking for here. If we see parameters passed "
"to the StorageClass correctly, we will see the ``ceph-mon.ceph.svc.cluster."
"local:6789`` hostname/port, things like ``userid``, and appropriate secrets "
"used for volume claims."
msgstr ""
"Parameternya adalah apa yang kami cari di sini. Jika kita melihat parameter "
"yang dikirimkan ke StorageClass dengan benar, kita akan melihat hostname/"
"port ``ceph-mon.ceph.svc.cluster.local: 6789``, hal-hal seperti ``userid``, "
"dan rahasia yang sesuai digunakan untuk klaim volume ."
msgid ""
"This guide is to help users debug any general storage issues when deploying "
"Charts in this repository."
msgstr ""
"Panduan ini untuk membantu pengguna mendebug masalah penyimpanan umum apa "
"pun saat menerapkan Charts dalam repositori ini."
msgid ""
"This guide is to help users debug any general storage issues when deploying "
"charts in this repository."
msgstr ""
"Panduan ini untuk membantu pengguna mendebug masalah penyimpanan umum apa "
"pun saat menerapkan grafik di repositori ini."
msgid ""
"To deploy the HWE kernel, prior to deploying Kubernetes and OpenStack-Helm "
"the following commands should be run on each node:"
msgstr ""
"Untuk menyebarkan kernel HWE, sebelum menyebarkan Kubernetes dan OpenStack-"
"Helm, perintah berikut harus dijalankan pada setiap node:"
msgid ""
"To make use of CephFS in Ubuntu the HWE Kernel is required, until the issue "
"described `here <https://github.com/kubernetes-incubator/external-storage/"
"issues/345>`_ is fixed."
msgstr ""
"Untuk menggunakan CephFS di Ubuntu, Kernel HWE diperlukan, sampai masalah "
"tersebut dijelaskan `here <https://github.com/kubernetes-incubator/external-"
"storage/issues/345>`_ telah diperbaiki."
msgid "To test MariaDB, do the following:"
msgstr "Untuk menguji MariaDB, lakukan hal berikut:"
msgid ""
"To validate persistent volume claim (PVC) creation, we've placed a test "
"manifest `here <https://raw.githubusercontent.com/openstack/openstack-helm/"
"master/tests/pvc-test.yaml>`_. Deploy this manifest and verify the job "
"completes successfully."
msgstr ""
"Untuk memvalidasi pembuatan persistent volume claim (PVC, kami menempatkan "
"manifes tes `here <https://raw.githubusercontent.com/openstack/openstack-"
"helm/master/tests/pvc-test.yaml>`_. Gunakan manifes ini dan verifikasi bahwa "
"pekerjaan telah selesai dengan sukses."
msgid "Troubleshooting"
msgstr "Penyelesaian masalah"
msgid "Ubuntu HWE Kernel"
msgstr "Ubuntu HWE Kernel"
msgid ""
"Use one of your Ceph Monitors to check the status of the cluster. A couple "
"of things to note above; our health is `HEALTH\\_OK`, we have 3 mons, we've "
"established a quorum, and we can see that all of our OSDs are up and in the "
"OSD map."
msgstr ""
"Gunakan salah satu Ceph Monitors Anda untuk memeriksa status cluster. "
"Beberapa hal yang perlu diperhatikan di atas; kesehatan kita adalah `HEALTH"
"\\_OK`, kita memiliki 3 mons, kita telah membentuk kuorum, dan kita dapat "
"melihat bahwa semua OSD kita sudah naik dan di peta OSD."
msgid ""
"Without this, your RBD-backed PVCs will never reach the ``Bound`` state. "
"For more information, see how to `activate namespace for ceph <../install/"
"multinode.html#activating-control-plane-namespace-for-ceph>`_."
msgstr ""
"Tanpa ini, RBD-backed PVCs Anda tidak akan pernah mencapai status ``Bound``. "
"Untuk informasi lebih lanjut, lihat caranya `activate namespace for ceph <../"
"install/multinode.html#activating-control-plane-namespace-for-ceph>`_."

View File

@ -1,384 +0,0 @@
# suhartono <cloudsuhartono@gmail.com>, 2018. #zanata
# suhartono <cloudsuhartono@gmail.com>, 2019. #zanata
# suhartono <cloudsuhartono@gmail.com>, 2020. #zanata
msgid ""
msgstr ""
"Project-Id-Version: openstack-helm 0.1.1.dev3879\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2022-10-24 20:45+0000\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"PO-Revision-Date: 2020-05-08 08:23+0000\n"
"Last-Translator: suhartono <cloudsuhartono@gmail.com>\n"
"Language-Team: Indonesian\n"
"Language: id\n"
"X-Generator: Zanata 4.3.3\n"
"Plural-Forms: nplurals=1; plural=0\n"
msgid ":ref:`genindex`"
msgstr ":ref:`genindex`"
msgid ":ref:`search`"
msgstr ":ref:`search`"
msgid "Adding Services"
msgstr "Menambahkan Layanan"
msgid "Adding Tests"
msgstr "Menambahkan Tes"
msgid ""
"Any additional functions required for testing new charts or improving the "
"gate workflow should be placed in the appropriate location."
msgstr ""
"Setiap fungsi tambahan yang diperlukan untuk menguji chart baru atau "
"meningkatkan gate workflow harus ditempatkan di lokasi yang tepat."
msgid ""
"Any tests that do not use the Rally testing framework would need to be "
"handled in the appropriate manner in launch script. This would ideally "
"result in new functions that could be reused, or expansion of the gate "
"scripts to include scenarios beyond basic service launches."
msgstr ""
"Setiap tes yang tidak menggunakan kerangka pengujian Rally harus ditangani "
"dengan cara yang sesuai dalam skrip peluncuran. Ini idealnya menghasilkan "
"fungsi baru yang dapat digunakan kembali, atau perluasan skrip gate untuk "
"memasukkan skenario di luar peluncuran layanan dasar."
msgid ""
"As charts for additional services are added to OpenStack-Helm, they should "
"be included in the gates. Adding new services to the gates allows a chart "
"developer and the review team to identify any potential issues associated "
"with a new service. All services are currently launched in the gate via a "
"series of launch scripts of the format ``NNN-service-name.sh`` where ``NNN`` "
"dictates the order these scripts are launched. The script should contain an "
"installation command like:"
msgstr ""
"Karena chart untuk layanan tambahan ditambahkan ke OpenStack-Helm, mereka "
"harus dimasukkan ke dalam gate. Menambahkan layanan baru ke gate "
"memungkinkan pengembang chart dan tim peninjau untuk mengidentifikasi setiap "
"potensi masalah yang terkait dengan layanan baru. Semua layanan saat ini "
"diluncurkan di gate melalui serangkaian skrip peluncuran format ``NNN-"
"service-name.sh`` dimana ``NNN`` mendikte perintah skrip ini diluncurkan. "
"Skrip harus berisi perintah pemasangan seperti:"
msgid ""
"As new charts are developed and the services are added to the gate, an "
"associated Helm test should be introduced to the gates. The appropriate "
"place for executing these tests is in the respective service's launch "
"script, and must be placed after the entry for installing the service and "
"any associated overrides. Any tests that use the Rally testing framework "
"should leverage the helm_test_deployment function in the aforementioned "
"funcs/helm.sh file. For example, a Helm test for Mistral might look like:"
msgstr ""
"Ketika chart baru dikembangkan dan layanan ditambahkan ke gate, tes Helm "
"yang terkait harus diperkenalkan ke gate. Tempat yang tepat untuk "
"mengeksekusi tes ini adalah di skrip peluncuran layanan masing-masing, dan "
"harus ditempatkan setelah entri untuk menginstal layanan dan menimpa yang "
"terkait. Setiap tes yang menggunakan kerangka pengujian Rally harus "
"memanfaatkan fungsi helm_test_deployment di file funcs/helm.sh yang "
"disebutkan di atas. Misalnya, tes Helm untuk Mistral mungkin terlihat "
"seperti:"
msgid ""
"Bugs and enhancements are tracked via OpenStack-Helm's `Storyboard <https://"
"storyboard.openstack.org/#!/project_group/64>`_."
msgstr ""
"Bug dan perangkat tambahan dilacak via OpenStack-Helm's `Storyboard <https://"
"storyboard.openstack.org/#!/project_group/64>`_."
msgid "Communication"
msgstr "Komunikasi"
msgid "Contents:"
msgstr "Isi:"
msgid "Contributing"
msgstr "Berkontribusi"
msgid ""
"Developers wishing to work on the OpenStack-Helm project should always base "
"their work on the latest code, available from the OpenStack-Helm git "
"repository."
msgstr ""
"Pengembang yang ingin bekerja pada proyek OpenStack-Helm harus selalu "
"mendasarkan pekerjaan mereka pada kode terbaru, tersedia dari repositori git "
"OpenStack-Helm."
msgid ""
"Functions for Helm specific operations, found in helm.sh. These functions "
"include: installing Helm, serving a Helm repository locally, linting and "
"building all Helm charts, running Helm tests on a release, installing the "
"helm template plugin, and running the helm template plugin against a chart."
msgstr ""
"Fungsi untuk operasi khusus Helm, ditemukan di helm.sh. Fungsi-fungsi ini "
"meliputi: memasang Helm, melayani repositori Helm secara lokal, membuat "
"linting dan membangun semua Helm chart, menjalankan tes Helm pada rilis, "
"menginstal plugin template kemudi, dan menjalankan plugin template helm "
"terhadap chart."
msgid ""
"Functions for Kubernetes specific operations, found in kube.sh. These "
"functions include: waiting for pods in a specific namespace to register as "
"ready, waiting for all nodes to register as ready, install the requirements "
"for the kubeadm-aio container used in the gates, building the kubeadm-aio "
"container, launching the kubeadm-aio container, and replacing the kube-"
"controller-manager with a specific image necessary for ceph functionality."
msgstr ""
"Fungsi untuk Kubernetes operasi spesifik, ditemukan di kube.sh. Fungsi-"
"fungsi ini meliputi: menunggu pod dalam namespace tertentu untuk mendaftar "
"sebagai siap (ready), menunggu semua node untuk mendaftar sebagai siap, "
"menginstal persyaratan untuk kontainer kubeadm-aio yang digunakan di gate, "
"membangun kontainer kubeadm-aio, meluncurkan kontainer kubeadm- aio, dan "
"mengganti kube-controller-manager dengan image spesifik yang diperlukan "
"untuk fungsi ceph."
msgid ""
"Functions for OpenStack specific operations, found in openstack.sh. These "
"functions include: waiting for a successful ping, and waiting for a booted "
"virtual machine's status to return as ACTIVE."
msgstr ""
"Fungsi untuk operasi spesifik OpenStack, ditemukan di openstack.sh. Fungsi-"
"fungsi ini meliputi: menunggu ping yang berhasil, dan menunggu status mesin "
"virtual boot untuk kembali sebagai AKTIF."
msgid "Functions for common host preparation operations, found in common.sh"
msgstr "Fungsi untuk operasi persiapan host umum, ditemukan di common.sh"
msgid ""
"Functions for network specific operations, found in network.sh. These "
"functions include: creating a backup of the host's resolv.conf file before "
"deploying the kubeadm environments, restoring the original resolv.conf "
"settings, creating a backup of the host's /etc/hosts file before adding the "
"hosts interface and address, and restoring the original /etc/hosts file."
msgstr ""
"Fungsi untuk operasi spesifik jaringan, ditemukan di network.sh. Fungsi-"
"fungsi ini meliputi: membuat cadangan file resolv.conf host sebelum "
"menyebarkan lingkungan kubeadm, memulihkan pengaturan resolv.conf asli, "
"membuat cadangan file /etc/hosts milik host sebelum menambahkan antarmuka "
"dan alamat host, dan memulihkan file /etc/hosts asli."
msgid "Gate Checks"
msgstr "Gate Checks (pemeriksaan gate)"
msgid "Gate Functions"
msgstr "Gate Functions (fungsi gate)"
msgid "Gate Output"
msgstr "Gate Output"
msgid "Indices and Tables"
msgstr "Indeks dan Tabel"
msgid "Installation and Development"
msgstr "Instalasi dan Pengembangan"
msgid ""
"Join us on `Slack <https://kubernetes.slack.com/messages/C3WERB7DE/>`_ - "
"#openstack-helm"
msgstr ""
"Bergabunglah dengan kami `Slack <https://kubernetes.slack.com/messages/"
"C3WERB7DE/>`_ - #openstack-helm"
msgid ""
"Meeting Agenda Items: `Agenda <https://etherpad.openstack.org/p/openstack-"
"helm-meeting-agenda>`_"
msgstr ""
"Item Agenda Rapat: `Agenda <https://etherpad.openstack.org/p/openstack-helm-"
"meeting-agenda>`_"
msgid "Mission"
msgstr "Misi"
msgid "OpenStack-Helm"
msgstr "OpenStack-Helm"
msgid "OpenStack-Helm Gates"
msgstr "OpenStack-Helm Gates"
msgid "OpenStack-Helm currently checks the following scenarios:"
msgstr "OpenStack-Helm saat ini memeriksa skenario berikut:"
msgid ""
"OpenStack-Helm's single node and multinode gates leverage the kubeadm-aio "
"environment created and maintained for use as a development environment. "
"All information regarding the kubeadm-aio environment can be found here_."
msgstr ""
"Node tunggal OpenStack-Helm dan gate multinode memanfaatkan lingkungan "
"kubeadm-aio yang dibuat dan dipelihara untuk digunakan sebagai lingkungan "
"pengembangan. Semua informasi mengenai lingkungan kubeadm-aio dapat "
"ditemukan di sini_."
msgid ""
"Provisioning a multi-node Ubuntu-1604 cluster and deploying the OpenStack "
"services. This check is provided for both a two node cluster and a three "
"node cluster."
msgstr ""
"Menyediakan multi-node klaster Ubuntu-1604 dan menyebarkan layanan "
"OpenStack. Pemeriksaan ini disediakan untuk dua klaster node dan tiga "
"klaster node."
msgid ""
"Provisioning a single node cluster and deploying the OpenStack services. "
"This check is provided for: Ubuntu-1604, CentOS-7, and Fedora-25."
msgstr ""
"Menyediakan satu klaster node dan menyebarkan layanan OpenStack. Pemeriksaan "
"ini disediakan untuk: Ubuntu-1604, CentOS-7, dan Fedora-25."
msgid "Repository"
msgstr "Repository (repositori)"
msgid ""
"Running Make on each chart, which lints and packages the charts. This gate "
"does not stand up a Kubernetes cluster."
msgstr ""
"Menjalankan Make pada setiap chart, yang lint dan package chart. Gate ini "
"tidak memiliki kluster Kubernetes."
msgid ""
"Some services in the gate require specific overrides to the default values "
"in the chart's values.yaml file. If a service requires multiple overrides "
"to function in the gate, the service should include a separate values.yaml "
"file placed in the tools/overrides/mvp directory. The <service>.yaml MVP "
"files provide a configuration file to use for overriding default "
"configuration values in the chart's values.yaml as an alternative to "
"overriding individual values during installation. A chart that requires a "
"MVP overrides file requires the following format:"
msgstr ""
"Beberapa layanan di gate memerlukan pengunggahan spesifik ke nilai default "
"di file values.yaml chart. Jika suatu layanan memerlukan beberapa override "
"untuk berfungsi di gate, layanan harus menyertakan file values.yaml yang "
"terpisah yang ditempatkan di direktori tools/overrides/mvp. File MVP "
"<service>.yaml menyediakan file konfigurasi yang digunakan untuk "
"mengesampingkan nilai konfigurasi default di values.yaml milik chart sebagai "
"alternatif untuk menimpa nilai individual selama instalasi. Sebuah chart "
"yang membutuhkan file menimpa MVP membutuhkan format berikut:"
msgid "Storyboard"
msgstr "Storyboard (papan cerita)"
msgid "Testing any documentation changes and impacts."
msgstr "Menguji perubahan dan dampak dokumentasi apa pun."
msgid ""
"The K8s directory contains the logs and output of the Kubernetes objects. "
"It includes: pods, nodes, secrets, services, namespaces, configmaps, "
"deployments, daemonsets, and statefulsets. Descriptions for the state of "
"all resources during execution are found here, and this information can "
"prove valuable when debugging issues raised during a check. When a single "
"node or multi-node check fails, this is the first place to look. The logs "
"found here are helpful when the templates render correctly, but the services "
"are not functioning correctly, whether due to service configuration issues "
"or issues with the pods themselves."
msgstr ""
"Direktori K8s berisi log dan output dari objek Kubernetes. Ini termasuk: "
"pod, node, rahasia, layanan, namespace, configaps, penyebaran, daemon, dan "
"statefulset. Deskripsi untuk keadaan semua sumber daya selama eksekusi "
"ditemukan di sini, dan informasi ini dapat terbukti bermanfaat ketika "
"masalah debug dinaikkan selama pemeriksaan. Ketika pemeriksaan node tunggal "
"atau multi-node gagal, ini adalah tempat pertama untuk melihat. Log yang "
"ditemukan di sini bermanfaat ketika template dirender dengan benar, tetapi "
"layanan tidak berfungsi dengan benar, baik karena masalah konfigurasi "
"layanan atau masalah dengan pod itu sendiri."
msgid ""
"The dry-runs directory contains the rendered output of Helm dry-run installs "
"on each of the OpenStack service charts. This gives visibility into the "
"manifests created by the templates with the supplied values. When the dry-"
"run gate fails, the reason should be apparent in the dry-runs output. The "
"logs found here are helpful in identifying issues resulting from using helm-"
"toolkit functions incorrectly or other rendering issues with gotpl."
msgstr ""
"Direktori dry-run berisi output yang diberikan dari pemasangan Helm dry-run "
"pada masing-masing chart layanan OpenStack. Ini memberikan visibilitas ke "
"manifes yang dibuat oleh template dengan nilai yang disediakan. Ketika gate "
"dry-run gagal, alasannya harus jelas dalam output dry-run. Log ditemukan di "
"sini sangat membantu dalam mengidentifikasi masalah yang dihasilkan dari "
"penggunaan fungsi-fungsi helm-toolkit yang salah atau masalah rendering "
"lainnya dengan gotpl."
msgid ""
"The goal of OpenStack-Helm is to provide a collection of Helm charts that "
"simply, resiliently, and flexibly deploy OpenStack and related services on "
"Kubernetes."
msgstr ""
"Tujuan OpenStack-Helm adalah untuk menyediakan koleksi grafik Helm yang "
"sederhana, tangguh, dan secara fleksibel menggunakan OpenStack dan layanan "
"terkait di Kubernetes."
msgid ""
"The nodes directory contains information about the node the gate tests are "
"running on in openstack-infra. This includes: the network interfaces, the "
"contents of iptables, the host's resolv.conf, and the kernel IP routing "
"table. These logs can be helpful when trying to identify issues with host "
"networking or other issues at the node level."
msgstr ""
"Direktori node berisi informasi tentang node dimana gate test sedang "
"berjalan di openstack-infra. Ini termasuk: antarmuka jaringan, isi iptables, "
"resolv.conf host, dan tabel routing IP kernel. Log ini dapat membantu ketika "
"mencoba mengidentifikasi masalah dengan jaringan host atau masalah lain di "
"tingkat node."
msgid ""
"This project is under active development. We encourage anyone interested in "
"OpenStack-Helm to review our `Installation <https://docs.openstack.org/"
"openstack-helm/latest/install/index.html>`_ documentation. Feel free to ask "
"questions or check out our current `Storyboard backlog <https://storyboard."
"openstack.org/#!/project_group/64>`_."
msgstr ""
"Proyek ini sedang dalam pengembangan aktif. Kami mendorong siapa pun yang "
"tertarik dengan OpenStack-Helm untuk meninjau dokumentasi kami `Installation "
"<https://docs.openstack.org/openstack-helm/latest/install/index.html>`_. "
"Jangan ragu untuk bertanya atau memeriksa saat ini `Storyboard backlog "
"<https://storyboard.openstack.org/#!/project_group/64>`_."
msgid "This results in the gate running the following:"
msgstr "Ini menghasilkan gate menjalankan berikut:"
msgid ""
"To evaluate a multinode installation, follow the `Bare Metal <https://docs."
"openstack.org/openstack-helm/latest/install/multinode.html>`_ install guide."
msgstr ""
"Untuk mengevaluasi instalasi multinode, ikuti panduan pemasangan `Bare Metal "
"<https://docs.openstack.org/openstack-helm/latest/install/multinode.html>` _."
msgid ""
"To facilitate ease of testing and debugging, information regarding gates and "
"their functionality can be found here."
msgstr ""
"Untuk memfasilitasi kemudahan pengujian dan debugging, informasi mengenai "
"gate dan fungsinya dapat ditemukan di sini."
msgid ""
"To provide meaningful output from the gates, all information pertaining to "
"the components of the cluster and workflow are output to the logs directory "
"inside each gate. The contents of the log directory are as follows:"
msgstr ""
"Untuk memberikan output yang berarti dari gate, semua informasi yang "
"berkaitan dengan komponen cluster dan alur kerja adalah output ke direktori "
"log di dalam setiap gate. Isi dari direktori log adalah sebagai berikut:"
msgid ""
"To provide reusable components for gate functionality, functions have been "
"provided in the gates/funcs directory. These functions include:"
msgstr ""
"Untuk menyediakan komponen yang dapat digunakan kembali untuk fungsi gate, "
"fungsi telah disediakan di direktori gates/funcs. Fungsi-fungsi ini termasuk:"
msgid ""
"We welcome contributions. Check out `this <CONTRIBUTING.rst>`_ document if "
"you would like to get involved."
msgstr ""
"Kami menyambut kontribusi. Lihatlah dokumen `CONTRIBUTING.rst>` _ ini jika "
"Anda ingin terlibat."
msgid "Welcome to OpenStack-Helm's documentation!"
msgstr "Selamat datang di dokumentasi OpenStack-Helm!"
msgid ""
"`OpenStack-Helm git repository <https://opendev.org/openstack/openstack-helm/"
">`_"
msgstr ""
"`OpenStack-Helm git repository <https://opendev.org/openstack/openstack-helm/"
">`_"

View File

@ -1,891 +0,0 @@
# Soonyeul Park <ardentpark@gmail.com>, 2018. #zanata
# Sungjin Kang <gang.sungjin@gmail.com>, 2018. #zanata
# Sungjin Kang <gang.sungjin@gmail.com>, 2019. #zanata
msgid ""
msgstr ""
"Project-Id-Version: openstack-helm 0.1.1.dev3631\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2022-02-23 21:11+0000\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"PO-Revision-Date: 2019-03-19 09:34+0000\n"
"Last-Translator: Sungjin Kang <gang.sungjin@gmail.com>\n"
"Language-Team: Korean (South Korea)\n"
"Language: ko_KR\n"
"X-Generator: Zanata 4.3.3\n"
"Plural-Forms: nplurals=1; plural=0\n"
msgid ""
"**Note:** The values defined in a PodDisruptionBudget may conflict with "
"other values that have been provided if an operator chooses to leverage "
"Rolling Updates for deployments. In the case where an operator defines a "
"``maxUnavailable`` and ``maxSurge`` within an update strategy that is higher "
"than a ``minAvailable`` within a pod disruption budget, a scenario may occur "
"where pods fail to be evicted from a deployment."
msgstr ""
"**참고:** PodDisruptionBudget 에 정의된 값들은 운영자가 배포를 위한 롤링 업데"
"이트를 활용하도록 선택한 경우 제공되는 다른 값들과 충돌할 수 있습니다. 운영자"
"가 pod 중단 비용에서의 ``minAvailable`` 보다 큰 ``maxUnavailable`` 과 "
"``maxSurge`` 를 업데이트 전략으로 정의한 경우, 배포에서 pod가 제거되지 않는 "
"시나리오가 발생할 수 있습니다."
msgid ""
":code:`neutron/templates/bin/_neutron-linuxbridge-agent-init.sh.tpl` is "
"configuring the tunnel IP, external bridge and all bridge mappings defined "
"in config. It is done in init container, and the IP for tunneling is shared "
"using file :code:`/tmp/pod-shared/ml2-local-ip.ini` with main linuxbridge "
"container."
msgstr ""
":code:`neutron/templates/bin/_neutron-linuxbridge-agent-init.sh.tpl`은 터널 "
"IP, 외부 브리지, 그리고 config에 정의된 모든 브리지 매핑을 구성합니다.그것은 "
"init 컨테이너에서 완료되고, 터널링을 위한 IP는 :code:`/tmp/pod-shared/ml2-"
"local-ip.ini` 파일을 사용하여 linuxbridge 컨테이너와 공유됩니다."
msgid ""
"A detail worth mentioning is that ovs is configured to use sockets, rather "
"than the default loopback mechanism."
msgstr ""
"언급할 가치가 있는 세부사항은 ovs가 기본 루프백 메커니즘 대신에 소켓을 사용하"
"여 구성된다는 것입니다. "
msgid ""
"A long-term goal, besides being image agnostic, is to also be able to "
"support any of the container runtimes that Kubernetes supports, even those "
"that might not use Docker's own packaging format. This will allow the "
"project to continue to offer maximum flexibility with regard to operator "
"choice."
msgstr ""
"이미지에서 자유로워지는 것 외에도 장기 목표는 Kubernetes가 지원하는 모든 컨테"
"이너 런타임도 지원할 수 있으며, Docker의 자체 패키징 포맷을 사용하지 않는 컨"
"테이너 런타임도 지원할 수 있습니다. 이는 프로젝트에 운영자의 선택과 관련하여 "
"최대한의 유연성을 허용할 것입니다."
msgid ""
"All ``Deployment`` chart components are outfitted by default with rolling "
"update strategies:"
msgstr ""
"모든 ``Deployment`` 차트 구성요소는 기본적으로 롤링 업데이트 전략으로 갖춰집"
"니다:"
msgid "All dependencies described in neutron-dhcp-agent are valid here."
msgstr "neutron-dhcp-agent에 서술된 모든 의존성은 여기에서 유효합니다."
msgid ""
"All of the above configs are endpoints or path to the specific class "
"implementing the interface. You can see the endpoints to class mapping in "
"`setup.cfg <https://github.com/openstack/neutron/"
"blob/412c49b3930ce8aecb0a07aec50a9607058e5bc7/setup.cfg#L69>`_."
msgstr ""
"위의 모든 구성은 인터페이스를 구현하는 특정 클래스에 대한 endpoints나 경로입"
"니다. `setup.cfg <https://github.com/openstack/neutron/"
"blob/412c49b3930ce8aecb0a07aec50a9607058e5bc7/setup.cfg#L69>`_에서 클래스 매"
"핑에 대한 endpoints를 볼 수 있습니다."
msgid ""
"An illustrative example of an ``images:`` section taken from the heat chart:"
msgstr "heat 차트에서 가져온 ``images:`` 섹션의 실제 사례:"
msgid ""
"Another place where the DHCP agent is dependent on L2 agent is the "
"dependency for the L2 agent daemonset:"
msgstr ""
"DHCP 에이전트가 L2 에이전트에 종속된 위치는 L2 에이전트 deamonset에 대한 종속"
"성입니다:"
msgid ""
"As part of Neutron chart, this daemonset is running Neutron OVS agent. It is "
"dependent on having :code:`openvswitch-db` and :code:`openvswitch-vswitchd` "
"deployed and ready. Since its the default choice of the networking backend, "
"all configuration is in place in `neutron/values.yaml`. :code:`neutron-ovs-"
"agent` should not be deployed when another SDN is used in `network.backend`."
msgstr ""
"Neutron 차트의 일부로서, 이 데몬세트는 Neutron OVS 에이전트를 실행 중입니다. "
"그것은 :code:`openvswitch-db`와 :code:`openvswitch-vswitchd`를 배포하고 준비"
"하는데 의존합니다. 네트워킹 백엔드 기본 선택이기 때문에, 모든 구성은 "
"`neutron/values.yaml`에 위치합니다. 다른 SDN이 `network.backend`에서 사용될 "
"때 :code:`neutron-ovs-agent`를 배포해서는 안됩니다."
msgid ""
"By default, each endpoint is located in the same namespace as the current "
"service's helm chart. To connect to a service which is running in a "
"different Kubernetes namespace, a ``namespace`` can be provided for each "
"individual endpoint."
msgstr ""
"기본적으로, 각 endpoint는 현재 서비스의 helm 차트와 같은 네임스페이스에 위치"
"합니다. 다른 Kubernetes 네임 스페이스에서 실행중인 서비스에 연결하여 각 "
"endpoint에 ``namespace`` 를 제공할 수 있습니다."
msgid ""
"Charts should not use hard coded values such as ``http://keystone-api:5000`` "
"because these are not compatible with operator overrides and do not support "
"spreading components out over various namespaces."
msgstr ""
"차트는 ``http://keystone-api:5000`` 과 같은 하드 코딩된 값을 사용하면 안됩니"
"다. 왜냐하면 이 값들은 운영자의 오버라이드와 호환되지 않으며 다양한 네임스페"
"이스로 확장되는 구성요소들을 지원하지 않기 때문입니다."
msgid ""
"Configuration of OVS bridges can be done via `neutron/templates/bin/_neutron-"
"openvswitch-agent-init.sh.tpl`. The script is configuring the external "
"network bridge and sets up any bridge mappings defined in :code:`conf."
"auto_bridge_add`. These values should align with :code:`conf.plugins."
"openvswitch_agent.ovs.bridge_mappings`."
msgstr ""
"OVS 브릿지 구성은 `neutron/templates/bin/_neutron-openvswitch-agent-init.sh."
"tpl`에서 할 수 있습니다. 이 스크립트는 외부 네트워크 브릿지를 구성하고, :"
"code:`conf.auto_bridge_add` 에서 정의하는 브릿지 매핑을 설정합니다. 이 값들"
"은 :code:`conf.plugins.openvswitch_agent.ovs.bridge_mappings`와 같아야합니다."
msgid ""
"Configure neutron-server with SDN specific core_plugin/mechanism_drivers."
msgstr ""
"SDN 특정 core_plugin/mechanism_drivers를 사용하여 neutron-server를 구성하십시"
"오."
msgid "Configuring network plugin"
msgstr "네트워크 플러그인 구성"
msgid "Contents:"
msgstr "목차:"
msgid "Create separate chart with new SDN deployment method."
msgstr "새로운 SDN 배포 방법으로 별도의 차트를 생성하십시오."
msgid ""
"Currently OpenStack-Helm supports OpenVSwitch and LinuxBridge as a network "
"virtualization engines. In order to support many possible backends (SDNs), "
"modular architecture of Neutron chart was developed. OpenStack-Helm can "
"support every SDN solution that has Neutron plugin, either core_plugin or "
"mechanism_driver."
msgstr ""
"현재 OpenStack-Helm은 OpenVSwitch 및 LinuxBridge를 네트워크 가상화 엔진으로 "
"지원합니다. 가능한 많은 backend(SDNs)들을 지원하기 위해, Neutron 차트의 모듈"
"식 구조가 개발되었습니다. OpenStack-Helm은 core_plugin 또는 mechanism_driver"
"인 Neutron 플러그인이 있는 모든 SDN 솔루션을 지원할 수 있습니다."
msgid "DHCP - auto-assign IP address and DNS info"
msgstr "DHCP - IP 주소와 DNS 정보 자동 할당"
msgid ""
"DHCP agent is running dnsmasq process which is serving the IP assignment and "
"DNS info. DHCP agent is dependent on the L2 agent wiring the interface. So "
"one should be aware that when changing the L2 agent, it also needs to be "
"changed in the DHCP agent. The configuration of the DHCP agent includes "
"option `interface_driver`, which will instruct how the tap interface created "
"for serving the request should be wired."
msgstr ""
"DHCP 에이전트가 IP 할당 및 DNS 정보를 제공하는 dnsmasq 프로세스를 실행 중입니"
"다. DHCP 에이전트는 인터페이스를 연결하는 L2 에이전트에 의존합니다. 그래서 "
"L2 에이전트를 변경할 때 DHCP 에이전트에서 알고 있어야 하고, 또한 DHCP 에이전"
"트에서 변경될 필요가 있습니다. DHCP 에이전트 구성은 요청을 제공하기 위해 생성"
"된 탭 인터페이스가 어떻게 연결되어야 할지 지시할 interface_driver 옵션을 포함"
"합니다."
msgid "Developer References"
msgstr "개발자 참고자료"
msgid ""
"EFK (Elasticsearch, Fluent-bit & Fluentd, Kibana) based Logging Mechanism"
msgstr "EFK (Elasticsearch, Fluent-bit & Fluentd, Kibana) 기반 로깅 매커니즘"
msgid "Endpoints"
msgstr "Endpoints"
msgid ""
"Fluent-bit, Fluentd meet OpenStack-Helm's logging requirements for "
"gathering, aggregating, and delivering of logged events. Fluent-bit runs as "
"a daemonset on each node and mounts the `/var/lib/docker/containers` "
"directory. The Docker container runtime engine directs events posted to "
"stdout and stderr to this directory on the host. Fluent-bit then forward the "
"contents of that directory to Fluentd. Fluentd runs as deployment at the "
"designated nodes and expose service for Fluent-bit to forward logs. Fluentd "
"should then apply the Logstash format to the logs. Fluentd can also write "
"kubernetes and OpenStack metadata to the logs. Fluentd will then forward the "
"results to Elasticsearch and to optionally Kafka. Elasticsearch indexes the "
"logs in a logstash-* index by default. Kafka stores the logs in a ``logs`` "
"topic by default. Any external tool can then consume the ``logs`` topic."
msgstr ""
"Fluent-bit, Fluentd는 기록된 이벤트의 수집, 집계, 그리고 전달을 위한 로깅 요"
"구사항을 충족합니다. Fluent-bit는 각 노드에서 daemonset으로 실행하고 `/var/"
"lib/docker/containers` 디렉터리를 마운트합니다. Docker 컨테이너 런타임 엔진"
"은 stdout과 stderr에 게시된 이벤트를 호스트의 상기 디렉터리로 보냅니다. 그런 "
"다음 Fluent-bit는 해당 디렉터리의 내용을 Fluentd로 전달합니다. Fluentd는 지정"
"된 노드에서 배포로 동작하고 Fluent-bit의 전달 로그로 서비스를 표시합니다. 그"
"런 다음 Fluentd는 Logstash 포맷을 로그에 적용해야 합니다. Fluentd는 또한 "
"kubernetes와 OpenStack의 메타데이터를 로그에 작성합니다. Fluentd는 그 결과를 "
"Elasticsearch와 선택적으로 Kafka에 전달합니다. Elasticsearch는 기본적으로 로"
"그를 logstash-*로 색인합니다. Kafka는 기본적으로 로그를 ``logs`` 주제로 보관"
"합니다. 그러면 외부 도구가 ``logs`` 주제를 사용할 수 있습니다."
msgid ""
"For instance, in the Neutron chart ``values.yaml`` the following endpoints "
"are defined:"
msgstr ""
"예를 들어, Neutron 차트 ``values.yaml`` 에서 다음과 같은 endpoints가 정의됩니"
"다:"
msgid "Host overrides supercede label overrides"
msgstr "호스트가 대체 라벨의 오버라이드를 오버라이드합니다."
msgid ""
"If :code:`.Values.manifests.daemonset_ovs_agent` will be set to false, "
"neutron ovs agent would not be launched. In that matter, other type of L2 or "
"L3 agent on compute node can be run."
msgstr ""
":code:`.Values.manifests.daemonset_ovs_agent` 가 false로 설정된다면, neutron "
"ovs 에이전트는 시작되지 않을 것입니다. 그 때, 컴퓨트 노드의 다른 타입의 L2나 "
"L3 에이전트가 실행됩니다."
msgid "If required, add new networking agent label type."
msgstr "필요하다면, 새로운 네트워킹 에이전트 라벨 타입을 추가하십시오."
msgid ""
"If the SDN implements its own version of L3 networking, neutron-l3-agent "
"should not be started."
msgstr ""
"SDN이 L3 네트워킹의 한 버전을 구현한다면, neutron-l3-agent는 시작되어서는 안"
"됩니다."
msgid ""
"If the SDN of your choice is using the ML2 core plugin, then the extra "
"options in `neutron/ml2/plugins/ml2_conf.ini` should be configured:"
msgstr ""
"선택한 SDN이 ML2 코어 플러그인을 사용하고 있다면, `neutron/ml2/plugins/"
"ml2_conf.ini` 의 추가 옵션이 구성되어야 합니다:"
msgid "Images"
msgstr "이미지"
msgid ""
"In ``values.yaml`` in each chart, the same defaults are supplied in every "
"chart, which allows the operator to override at upgrade or deployment time."
msgstr ""
"각 차트의 ``values.yaml`` 에는, 업그레이드나 배포 시기에 운영자의 오버라이드"
"가 허용되는 동일한 기본값이 모든 차트에 제공됩니다."
msgid ""
"In order to add support for more SDNs, these steps need to be performed:"
msgstr "더 많은 SDN들을 추가하기 위해서, 이 과정들을 수행할 필요가 있습니다:"
msgid ""
"In order to meet modularity criteria of Neutron chart, section `manifests` "
"in :code:`neutron/values.yaml` contains boolean values describing which "
"Neutron's Kubernetes resources should be deployed:"
msgstr ""
"Neutron 차트의 모듈성 기준을 충족하기 위해서, :code:`neutron/values.yaml`의 "
"섹션 매니페스트는 어떤 Neutron의 Kubernetes 리소스가 배포되어야 하는지 서술하"
"는 boolean 값들을 포함하고 있습니다:"
msgid ""
"In order to use linuxbridge in your OpenStack-Helm deployment, you need to "
"label the compute and controller/network nodes with `linuxbridge=enabled` "
"and use this `neutron/values.yaml` override:"
msgstr ""
"OpenStack-Helm 배치에서 linuxbridge를 사용하기 위해, compute와 controller/"
"network 노드를 `linuxbridge=enabled`로 라벨할 필요가 있고 이것을 `neutron/"
"values.yaml`에 오버라이드하여 사용합니다."
msgid ""
"Introducing a new SDN solution should consider how the above services are "
"provided. It maybe required to disable built-in Neutron functionality."
msgstr ""
"새로운 SDN 솔루션 도입은 위의 서비스가 어떻게 제공되는지를 고려해야합니다. "
"Neutron 내장 함수를 비활성화가 필요할 수도 있습니다."
msgid ""
"L3 agent is serving the routing capabilities for Neutron networks. It is "
"also dependent on the L2 agent wiring the tap interface for the routers."
msgstr ""
"L3 에이전트는 Neutron 네트워크를 위한 라우팅 능력을 제공하고 있습니다. 또한 "
"라우터를 위한 탭 인터페이스를 연결하는 L2 에이전트에 의존합니다."
msgid "L3 routing - creation of routers"
msgstr "L3 라우팅 - 라우터 생성"
msgid "Linuxbridge"
msgstr "Linuxbridge"
msgid ""
"Linuxbridge is the second type of Neutron reference architecture L2 agent. "
"It is running on nodes labeled `linuxbridge=enabled`. As mentioned before, "
"all nodes that are requiring the L2 services need to be labeled with "
"linuxbridge. This includes both the compute and controller/network nodes. It "
"is not possible to label the same node with both openvswitch and linuxbridge "
"(or any other network virtualization technology) at the same time."
msgstr ""
"Linuxbridge는 Neutron 참조 구조 L2 에이전트의 두 번째 타입입니다. 그것은 "
"`linuxbridge=enabled`로 라벨된 노드에서 실행 중입니다. 앞서 언급했듯이, L2 서"
"비스를 요구하는 모든 노드는 linuxbridge로 라벨될 필요가 있습니다. 이는 "
"compute와 controller/network 노드 모두를 포함합니다. 같은 노드에 openvswitch"
"와 linuxbridge (또는 다른 네트워크 가상화 기술)를 동시에 라벨하는 것은 불가능"
"합니다."
msgid "Logging Mechanism"
msgstr "로깅 매커니즘"
msgid "Logging Requirements"
msgstr "로깅 요구사항"
msgid "Metadata - Provide proxy for Nova metadata service"
msgstr "메타데이터 - Nova 메타데이터 서비스를 위한 프록시 제공"
msgid ""
"Metadata-agent is a proxy to nova-metadata service. This one provides "
"information about public IP, hostname, ssh keys, and any tenant specific "
"information. The same dependencies apply for metadata as it is for DHCP and "
"L3 agents. Other SDNs may require to force the config driver in nova, since "
"the metadata service is not exposed by it."
msgstr ""
"Metadata-agent는 nova-metadata 서비스에 대한 프록시입니다. 이것은 공용 IP, 호"
"스트명, ssh 키, 그리고 tenant 특정 정보에 대한 정보를 제공합니다. DHCP와 L3 "
"에이전트와 마찬가지로 메타데이터에도 동일한 의존성을 적용합니다. 다른 SDN은 "
"메타데이터 서비스가 노출되어 있지 않으므로 nova에서 드라이버 구성을 강제할 것"
"을 요구할지도 모릅니다."
msgid "Networking"
msgstr "네트워킹"
msgid "Neutron architecture"
msgstr "Neutron 구조"
msgid "Neutron chart includes the following services:"
msgstr "Neutron 차트는 다음의 서비스들을 포함합니다:"
msgid ""
"Neutron-server service is scheduled on nodes with `openstack-control-"
"plane=enabled` label."
msgstr ""
"Neutron-server 서비스는 `openstack-control-plane=enabled` 라벨로 노드에 스케"
"줄됩니다."
msgid "Note that only one set of overrides is applied per node, such that:"
msgstr ""
"노드마다 다음과 같이 단 하나의 오버라이드 세트만 적용되는 점을 참고하십시오:"
msgid ""
"Note that some additional values have been injected into the config file, "
"this is performed via statements in the configmap template, which also calls "
"the ``helm-toolkit.utils.to_oslo_conf`` to convert the yaml to the required "
"layout:"
msgstr ""
"구성 파일에 몇 가지 추가 값들이 주입되었음을 참고하십시오, 이는 configmap 템"
"플릿의 문장을 통해 수행되며, 또한 yaml을 필요한 레이아웃으로 변환하기 위해 "
"``helm-toolkit.utils.to_oslo_conf`` 를 호출합니다:"
msgid ""
"Note: Rolling update values can conflict with values defined in each "
"service's PodDisruptionBudget. See `here <https://docs.openstack.org/"
"openstack-helm/latest/devref/pod-disruption-budgets.html>`_ for more "
"information."
msgstr ""
"참고: 롤링 업데이트 값은 각 서비스의 PodDisruptionBudget에 정의된 값들과 충돌"
"할 수 있습니다. 자세한 정보는 `여기 <https://docs.openstack.org/openstack-"
"helm/latest/devref/pod-disruption-budgets.html>`_ 를 참조하십시오."
msgid "Nova config dependency"
msgstr "Nova config 의존성"
msgid "OSLO-Config Values"
msgstr "OSLO-Config 값"
msgid ""
"OpenStack-Helm defines a centralized logging mechanism to provide insight "
"into the state of the OpenStack services and infrastructure components as "
"well as underlying Kubernetes platform. Among the requirements for a logging "
"platform, where log data can come from and where log data need to be "
"delivered are very variable. To support various logging scenarios, OpenStack-"
"Helm should provide a flexible mechanism to meet with certain operation "
"needs."
msgstr ""
"OpenStack-Helm은 OpenStack 서비스와 인프라 구성요소의 상태 뿐만 아니라 기본 "
"Kubernetes 플랫폼에 대한 통찰력을 제공하는 중앙 집중식 로깅 메커니즘을 정의합"
"니다. 로깅 플랫폼에 대한 요구사항 중 로그 데이터를 가져올 곳과 로그 데이터를 "
"전달되어야 할 곳은 매우 다양합니다. 다양한 로깅 시나리오를 지원하기 위해서, "
"OpenStack-Helm은 특정 작업 요구를 충족할 수 있는 유연한 메커니즘을 제공해야 "
"합니다."
msgid ""
"OpenStack-Helm generates oslo-config compatible formatted configuration "
"files for services dynamically from values specified in a yaml tree. This "
"allows operators to control any and all aspects of an OpenStack services "
"configuration. An example snippet for an imaginary Keystone configuration is "
"described here:"
msgstr ""
"OpenStack-Helm은 yaml 트리에 지정된 값에서 동적으로 서비스를 위한 oslo-"
"config 호환 형식의 구성 파일을 생성합니다. 이는 운영자가 OpenStack 서비스 구"
"성 전반을 제어할 수 있도록 합니다. 가상의 키스톤 구성에 대한 짧은 예시가 여"
"기 있습니다:"
msgid ""
"OpenStack-Helm provides fast and lightweight log forwarder and full featured "
"log aggregator complementing each other providing a flexible and reliable "
"solution. Especially, Fluent-bit is used as a log forwarder and Fluentd is "
"used as a main log aggregator and processor."
msgstr ""
"OpenStack-Helm은 신속하고 가벼운 로그 전달자와 완전한 기능을 갖춘 로그 수집기"
"를 제공하여 서로 보완하여 유연하고 신뢰할 수 있는 솔루션을 제공합니다. 특히, "
"Fluent-bit는 로그 전달자로 사용되고 Fluentd는 주 로그 수집기와 프로세서로 사"
"용됩니다."
msgid "OpenVSwitch"
msgstr "OpenVSwitch"
msgid "Other SDNs"
msgstr "다른 SDN들"
msgid "Other networking services provided by Neutron are:"
msgstr "Neutron에 의해 제공되는 다른 네트워킹 서비스:"
msgid "Pod Disruption Budgets"
msgstr "Pod 중단 비용"
msgid ""
"SDNs implementing ML2 driver can add extra/plugin-specific configuration "
"options in `neutron/ml2/plugins/ml2_conf.ini`. Or define its own "
"`ml2_conf_<name>.ini` file where configs specific to the SDN would be placed."
msgstr ""
"ML2 드라이버를 구현하는 SDN은 extra/plugin-specific 구성 옵션을 `neutron/ml2/"
"plugins/ml2_conf.ini`에 추가할 수 있습니다. 또는 SDN의 고유 구성이 배치될 자"
"체 `ml2_conf_<name>.ini` 파일을 정의하십시오."
msgid ""
"Script in :code:`neutron/templates/bin/_neutron-openvswitch-agent-init.sh."
"tpl` is responsible for determining the tunnel interface and its IP for "
"later usage by :code:`neutron-ovs-agent`. The IP is set in init container "
"and shared between init container and main container with :code:`neutron-ovs-"
"agent` via file :code:`/tmp/pod-shared/ml2-local-ip.ini`."
msgstr ""
":code:`neutron/templates/bin/_neutron-openvswitch-agent-init.sh.tpl`의 스크립"
"트는 :code:`neutron-ovs-agent`에 의한 나중의 사용을 위한 터널 인터페이스와 IP"
"를 결정할 책임이 있습니다. IP는 init 컨테이너에 설정되고 init 컨테이너와 "
"main 컨테이너 사이에서 :code:`/tmp/pod-shared/ml2-local-ip.ini`을 통한 :code:"
"`neutron-ovs-agent`로 공유됩니다."
msgid ""
"Specify if new SDN would like to use existing services from Neutron: L3, "
"DHCP, metadata."
msgstr ""
"새로운 SDN이 Neutron의 기존 서비스들을 사용할지 명시하십시오: L3, DHCP, 메타"
"데이터."
msgid ""
"The Neutron reference architecture provides mechanism_drivers :code:"
"`OpenVSwitch` (OVS) and :code:`linuxbridge` (LB) with ML2 :code:"
"`core_plugin` framework."
msgstr ""
"Neutron 참조 구조는 ML2 :code:`core_plugin` 프레임워크와 함께 :code:"
"`OpenVSwitch` (OVS) 와 :code:`linuxbridge` (LB) mechanism_drivers를 제공합니"
"다."
msgid ""
"The OpenStack-Helm project also implements annotations across all chart "
"configmaps so that changing resources inside containers, such as "
"configuration files, triggers a Kubernetes rolling update. This means that "
"those resources can be updated without deleting and redeploying the service "
"and can be treated like any other upgrade, such as a container image change."
msgstr ""
"OpenStack-Helm 프로젝트는 또한 모든 차트 configmap에 annotations를 구현하여 "
"구성 파일과 같은 컨테이너 내부의 변경 리소스가 Kubernetes 롤링 업데이트를 촉"
"발합니다. 이는 서비스를 삭제하거나 재배포하지 않고 해당 리소스들에 대한 업데"
"이트를 할 수 있으며 컨테이너 이미비 변경과 같은 다른 업그레이드와 같이 처리 "
"할 수 있음을 의미합니다."
msgid ""
"The OpenStack-Helm project assumes all upgrades will be done through Helm. "
"This includes handling several different resource types. First, changes to "
"the Helm chart templates themselves are handled. Second, all of the "
"resources layered on top of the container image, such as ``ConfigMaps`` "
"which includes both scripts and configuration files, are updated during an "
"upgrade. Finally, any image references will result in rolling updates of "
"containers, replacing them with the updating image."
msgstr ""
"OpenStack-Helm 프로젝트는 모든 업그레이드가 Helm을 통해 수행된다고 가정합니"
"다. 이는 몇몇 다른 리소스 타입의 처리를 포함합니다. 첫째, Helm 차트 템플릿 자"
"체의 변경이 처리됩니다. 둘째, ``ConfigMaps`` 와 같이 컨테이너 이미지 위에 계"
"층화된 모든 리소스가 업그레이드 중에 업데이트 됩니다. 마지막으로, 모든 이미"
"지 참조는 컨테이너의 롤링 업데이트를 가져오고, 업데이트한 이미지로 대체합니"
"다."
msgid ""
"The OpenStack-Helm project today uses a mix of Docker images from "
"Stackanetes and Kolla, but will likely standardize on a default set of "
"images for all charts without any reliance on image-specific utilities."
msgstr ""
"OpenStack-Helm 프로젝트는 현재 Stackanetes와 Kolla의 Docker 이미지를 혼합하"
"여 사용하지만, 이미지 특정 유틸리티에 의존하지 않고 모든 차트를 위한 기본 이"
"미지 세트를 표준화할 것입니다."
msgid ""
"The ``hash`` function defined in the ``helm-toolkit`` chart ensures that any "
"change to any file referenced by configmap-bin.yaml or configmap-etc.yaml "
"results in a new hash, which will then trigger a rolling update."
msgstr ""
"``helm-toolkit`` 차트에서 정의된 ``hash`` 함수는 configmap-bin.yaml 또는 "
"configmap-etc.yaml에서 참조되는 모든 파일에 대한 변화가 롤링 업데이트를 촉발"
"할 새로운 hash를 생성하는 것을 보장합니다."
msgid "The above configuration options are handled by `neutron/values.yaml`:"
msgstr "위의 구성 옵션은 'neutrol/values.yaml` 에 의해 조절됩니다:"
msgid ""
"The farther down the list the label appears, the greater precedence it has. "
"e.g., \"another-label\" overrides will apply to a node containing both "
"labels."
msgstr ""
"라벨이 표시된 목록이 낮을수록, 우선순위가 높아집니다. 예를 들어, \\\"another-"
"label\\\" 의 오버라이드는 두 라벨 모두를 포함한 노드에 적용될 것입니다. "
msgid ""
"The following standards are in use today, in addition to any components "
"defined by the service itself:"
msgstr ""
"서비스 자체로 정의된 구성요소 외에도, 다음의 표준들이 현재 사용되고 있습니다."
msgid ""
"The macros that help translate these into the actual URLs necessary are "
"defined in the ``helm-toolkit`` chart. For instance, the cinder chart "
"defines a ``glance_api_servers`` definition in the ``cinder.conf`` template:"
msgstr ""
"이들을 실제 필요한 URL로 변환하는 데 도움이 되는 매크로는 ``helm-toolkit`` 차"
"트에 정의되어 있습니다. 예를 들어, cinder 차트는 ``glance_api_servers`` 정의"
"를 ``cinder.conf`` 템플릿에 정의합니다:"
msgid ""
"The ovs set of daemonsets are running on the node labeled "
"`openvswitch=enabled`. This includes the compute and controller/network "
"nodes. For more flexibility, OpenVSwitch as a tool was split out of Neutron "
"chart, and put in separate chart dedicated OpenVSwitch. Neutron OVS agent "
"remains in Neutron chart. Splitting out the OpenVSwitch creates "
"possibilities to use it with different SDNs, adjusting the configuration "
"accordingly."
msgstr ""
"데몬세트의 ovs 세트는 `openvswitch=enabled`로 라벨된 노드에서 실행 중입니다. "
"이는 compute와 controller/network 노드를 포함합니다. 유연성을 높이기 위해서, "
"OpenVSwitch를 도구로 사용하여 Neutron 차트를 분리하고 OpenVSwitch 전용의 별"
"도 차트를 넣었습니다. Neutron OVS 에이전트는 Neutron 차트에 남아있습니다. "
"OpenVSwitch를 분할하면 다른 SDN과 함께 사용할 수 있는 가능성이 생기기 때문"
"에, 적절하게 구성을 조정합니다."
msgid ""
"The project's core philosophy regarding images is that the toolsets required "
"to enable the OpenStack services should be applied by Kubernetes itself. "
"This requires OpenStack-Helm to develop common and simple scripts with "
"minimal dependencies that can be overlaid on any image that meets the "
"OpenStack core library requirements. The advantage of this is that the "
"project can be image agnostic, allowing operators to use Stackanetes, Kolla, "
"LOCI, or any image flavor and format they choose and they will all function "
"the same."
msgstr ""
"이미지에 관한 프로젝트의 핵심 철학은 OpenStack 서비스를 활성화하는 데 필요한 "
"도구모음이 Kubernetes 자체에서 적용되어야 한다는 것입니다. 이는 OpenStack-"
"Helm에 OpenStack 핵심 라이브러리의 요구사항을 충족하는 이미지들에 중첩될 수 "
"있는 최소한의 의존성으로 일반적이고 단순한 스크립트를 개발할 것을 요구합니"
"다. 이것의 장점은 운영자들이 Stackanetes, Kolla, LOCI, 또는 그들이 선택하고 "
"동일하게 기능할 이미지 flavor와 포맷을 사용하는 것을 허락하여 프로젝트가 이미"
"지에서 자유로워지는 것입니다."
msgid ""
"The project's goal is to provide a consistent mechanism for endpoints. "
"OpenStack is a highly interconnected application, with various components "
"requiring connectivity details to numerous services, including other "
"OpenStack components and infrastructure elements such as databases, queues, "
"and memcached infrastructure. The project's goal is to ensure that it can "
"provide a consistent mechanism for defining these \"endpoints\" across all "
"charts and provide the macros necessary to convert those definitions into "
"usable endpoints. The charts should consistently default to building "
"endpoints that assume the operator is leveraging all charts to build their "
"OpenStack cloud. Endpoints should be configurable if an operator would like "
"a chart to work with their existing infrastructure or run elements in "
"different namespaces."
msgstr ""
"프로젝트의 목표는 endpoints에 대한 일관된 매커니즘을 제공하는 것입니다. "
"OpenStack은 다른 OpenStack 구성요소 와 데이터베이스, 큐, 그리고 memcached 인"
"프라와 같은 인프라 요소를 포함하여 다양한 서비스에 대한 연결 세부 사항을 필요"
"로 하는 다양한 구성요소와 고도로 상호 연결된 응용 프로그램입니다. 프로젝트의 "
"목표는 모든 차트에서 이러한 \"endpoints\"를 정의하는 일관된 메커니즘을 제공하"
"고 이러한 정의를 유용한 endpoints로 변환하는 데 필요한 매크로를 제공하는 것입"
"니다. 차트는 운영자가 그들의 OpenStack 클라우드를 구축하기 위하여 모든 차트"
"를 활용하고 있다고 가정하고 endpoints 구축을 일관되게 기본값으로 설정해야 합"
"니다. 운영자가 차트를 그들의 기존 인프라와 함께 사용하기를 원하거나 다른 네임"
"스페이스의 요소를 실행하려면 Endpoints를 구성 할 수 있어야 합니다."
msgid ""
"The resulting logs can then be queried directly through Elasticsearch, or "
"they can be viewed via Kibana. Kibana offers a dashboard that can create "
"custom views on logged events, and Kibana integrates well with Elasticsearch "
"by default."
msgstr ""
"로그의 결과는 Elasticsearch를 통해 직접 쿼리하거나 Kibana를 통해 볼 수 있습니"
"다. Kibana는 기록된 이벤트에 대한 사용자 정의 뷰를 만들 수 있는 대시보드를 제"
"공하며 Kibana는 기본적으로 Elasticsearch와 잘 통합됩니다."
msgid ""
"There is also a need for DHCP agent to pass ovs agent config file (in :code:"
"`neutron/templates/bin/_neutron-dhcp-agent.sh.tpl`):"
msgstr ""
"또한 DHCP 에이전트가 ovs 에이전트 구성 파일을 전달할 필요가 있습니다(:code:"
"`neutron/templates/bin/_neutron-dhcp-agent.sh.tpl` 내):"
msgid ""
"These values define all the endpoints that the Neutron chart may need in "
"order to build full URL compatible endpoints to various services. Long-term, "
"these will also include database, memcached, and rabbitmq elements in one "
"place. Essentially, all external connectivity can be defined centrally."
msgstr ""
"이 값들은 Neutron 차트가 다양한 서비스에 URL과 완전 호환되는 endpoints를 구축"
"하는데 필요할 수 있는 모든 endpoints를 정의합니다. 장기적으로, 이들은 또한 데"
"이터베이스, memcached, 그리고 rabbitmq 요소들을 한 곳에 포함할 것입니다. 근본"
"적으로, 모든 외부 연결을 중앙에서 정의할 수 있습니다."
msgid ""
"This daemonset includes the linuxbridge Neutron agent with bridge-utils and "
"ebtables utilities installed. This is all that is needed, since linuxbridge "
"uses native kernel libraries."
msgstr ""
"이 daemonset은 bridge-utils와 ebtables 유틸리티가 설치된 linuxbridge Neutron "
"에이전트를 포함합니다.linuxbridge가 네이티브 커널 라이브러리를 사용하기 때문"
"에 이 모든 것이 필요합니다."
msgid "This is accomplished with the following annotation:"
msgstr "이는 다음 annotation으로 수행됩니다:"
msgid ""
"This option will allow to configure the Neutron services in proper way, by "
"checking what is the actual backed set in :code:`neutron/values.yaml`."
msgstr ""
"이 옵션은 :code:`neutron/values.yaml`의 실제 backend set이 무엇인지 확인하"
"여, Neuron 서비스를 적절한 방법으로 구성할 수 있도록 허락할 것입니다."
msgid ""
"This requirement is OVS specific, the `ovsdb_connection` string is defined "
"in `openvswitch_agent.ini` file, specifying how DHCP agent can connect to "
"ovs. When using other SDNs, running the DHCP agent may not be required. When "
"the SDN solution is addressing the IP assignments in another way, neutron's "
"DHCP agent should be disabled."
msgstr ""
"이 요구사항은 OVS 특정이며, `ovsdb_connection` 문자열은 DHCP 에이전트가 어떻"
"게 ovs에 연결할 수 있는지 명세하는 `openvswitch_agent.ini` 파일에 정의됩니"
"다. 다른 SDN을 사용할 때, DHCP 에이전트 실행은 요구되지 않을 것입니다. SDN 솔"
"루션이 다른 방식으로 IP 할당을 지정할 때, neutron의 DHCP 에이전트를 비활성화"
"해야 합니다."
msgid ""
"This runs the OVS tool and database. OpenVSwitch chart is not Neutron "
"specific, it may be used with other technologies that are leveraging the OVS "
"technology, such as OVN or ODL."
msgstr ""
"이것은 OVS 툴과 데이터베이스를 실행합니다. OpenVSwitch 차트는 특정 Neutron이 "
"아니라, OVN이나 ODL과 같은 OVS 기술을 활용하는 다른 기술들에 사용될 것입니다."
msgid ""
"This will be consumed by the templated ``configmap-etc.yaml`` manifest to "
"produce the following config file:"
msgstr ""
"이것은 템플릿화 된 ``configmap-etc.yaml`` 매니페스트에 의해 다음의 구성 파일"
"을 생산하기 위해 소비될 것입니다:"
msgid ""
"To be able to configure multiple networking plugins inside of OpenStack-"
"Helm, a new configuration option is added:"
msgstr ""
"OpenStack-Helm 내 다중 네트워킹 플러그인을 구성하는 것을 가능하게 하기 위해"
"서, 새로운 구성 옵션이 추가되었습니다:"
msgid ""
"To enable new SDN solution, there should be separate chart created, which "
"would handle the deployment of service, setting up the database and any "
"related networking functionality that SDN is providing."
msgstr ""
"새로운 SDN 솔루션을 가능하게 하기 위해 서비스 배포, 데이터베이스 설정, 그리"
"고 SDN이 제공하고 있는 관련된 모든 네트워크 기능을 처리하는 별도의 차트가 생"
"성되어 있어야 합니다."
msgid ""
"To that end, all charts provide an ``images:`` section that allows operators "
"to override images. Also, all default image references should be fully "
"spelled out, even those hosted by Docker or Quay. Further, no default image "
"reference should use ``:latest`` but rather should be pinned to a specific "
"version to ensure consistent behavior for deployments over time."
msgstr ""
"이를 위해, 모든 차트는 운영자들이 이미지를 오버라이드할 수 있는 ``images`` 섹"
"션을 제공합니다. 또한, 모든 기본 이미지 참조는 Docker 또는 Quay에 의해 호스팅"
"되었더라도 완전히 작성되어야 합니다. 나아가, 어떤 기본 이미지 참조도 ``:"
"latest` 를 사용하면 안되지만, 대신에 배포 후에 일관된 동작을 보장하는 특정 버"
"전으로 고정되어야 합니다."
msgid ""
"To use other Neutron reference architecture types of SDN, these options "
"should be configured in :code:`neutron.conf`:"
msgstr ""
"다른 Neutron 참조 구조 타입의 SDN을 사용하려면, 이러한 옵션을 neutron.conf에"
"서 구성해야 합니다:"
msgid ""
"Today, the ``images:`` section has several common conventions. Most "
"OpenStack services require a database initialization function, a database "
"synchronization function, and a series of steps for Keystone registration "
"and integration. Each component may also have a specific image that composes "
"an OpenStack service. The images may or may not differ, but regardless, "
"should all be defined in ``images``."
msgstr ""
"현재, ``images:`` 섹션에는 몇가지 규칙이 있습니다. 대부분의 OpenStack 서비스"
"는 데이터베이스 초기화 기능, 데이터베이스 동기화 기능, 그리고 Keystone 등록"
"과 통합을 위한 단계를 요구합니다. 각 구성요소에는 OpenStack 서비스를 구성하"
"는 특정 이미지가 있을 수도 있습니다. 이미지는 다를 수 있지만, 이에 관계없이 "
"모두 ``images``에 정의되어야 합니다."
msgid "Typical networking API request is an operation of create/update/delete:"
msgstr "일반적인 네트워킹 API 요청은 생성/갱신/삭제 작업입니다:"
msgid "Upgrades and Reconfiguration"
msgstr "업그레이드 및 재구성"
msgid ""
"``host1.fqdn`` with labels ``compute-type: dpdk, sriov`` and ``another-"
"label: another-value``:"
msgstr ""
"``compute-type: dpdk, sriov`` 와 ``another-label: another-value`` 라벨의 "
"``host1.fqdn`` :"
msgid ""
"``host2.fqdn`` with labels ``compute-type: dpdk, sriov`` and ``another-"
"label: another-value``:"
msgstr ""
"``compute-type: dpdk, sriov`` 와 ``another-label: another-value`` 라벨의 "
"``host2.fqdn`` :"
msgid ""
"``host3.fqdn`` with labels ``compute-type: dpdk, sriov`` and ``another-"
"label: another-value``:"
msgstr ""
"``compute-type: dpdk, sriov`` 와 ``another-label: another-value`` 라벨의 "
"``host3.fqdn`` :"
msgid "``host4.fqdn`` with labels ``compute-type: dpdk, sriov``:"
msgstr "``compute-type: dpdk, sriov`` 라벨의 ``host4.fqdn`` :"
msgid "``host5.fqdn`` with no labels:"
msgstr "라벨이 없는 ``host5.fqdn`` :"
msgid ""
"db\\_drop: The image that will perform database deletion operations for the "
"OpenStack service."
msgstr "db\\_drop: OpenStack 서비스를 위한 데이터베이스 삭제를 수행할 이미지"
msgid ""
"db\\_init: The image that will perform database creation operations for the "
"OpenStack service."
msgstr ""
"db\\_init: OpenStack 서비스를 위한 데이터베이스 생성 작업을 수행할 이미지"
msgid ""
"db\\_sync: The image that will perform database sync (schema initialization "
"and migration) for the OpenStack service."
msgstr ""
"db\\_sync: OpenStack 서비스를 위한 데이터베이스 동기화(초기화와 이동 스키마)"
"를 수행할 이미지"
msgid ""
"dep\\_check: The image that will perform dependency checking in an init-"
"container."
msgstr "dep\\_check: init-container에서 의존성 검사를 수행할 이미지."
msgid ""
"image: This is the OpenStack service that the endpoint is being built for. "
"This will be mapped to ``glance`` which is the image service for OpenStack."
msgstr ""
"image : 이것은 endpoint가 구축하고 있는 OpenStack 서비스입니다. 이것은 "
"OpenStack을 위한 이미지 서비스인 ``glance``로 매핑될 것입니다."
msgid ""
"internal: This is the OpenStack endpoint type we are looking for - valid "
"values would be ``internal``, ``admin``, and ``public``"
msgstr ""
"internal : 이것은 우리가 찾고 있는 OpenStack endpoint 타입입니다. - 유효한 값"
"은 ``internal``, ``admin``, 그리고 ``public`` 입니다."
msgid ""
"ks\\_endpoints: The image that will perform keystone endpoint registration "
"for the service."
msgstr "ks\\_endpoints: 서비스를 위한 키스톤 endpoint 등록을 수행할 이미지"
msgid ""
"ks\\_service: The image that will perform keystone service registration for "
"the service."
msgstr "ks\\_service: 서비스를 위한 키스톤 사용자 등록을 수행할 이미지"
msgid ""
"ks\\_user: The image that will perform keystone user creation for the "
"service."
msgstr "ks\\_user : 서비스를 위한 키스톤 사용자 생성을 수행할 이미지"
msgid "network"
msgstr "네트워크"
msgid "neutron-dhcp-agent"
msgstr "neutron-dhcp-agent"
msgid ""
"neutron-dhcp-agent service is scheduled to run on nodes with the label "
"`openstack-control-plane=enabled`."
msgstr ""
"neutron-dhcp-agent 서비스는 `openstack-control-plane=enabled` 라벨로 노드에"
"서 실행되도록 스케줄됩니다."
msgid "neutron-l3-agent"
msgstr "neutron-l3-agent"
msgid ""
"neutron-l3-agent service is scheduled to run on nodes with the label "
"`openstack-control-plane=enabled`."
msgstr ""
"neutron-l3-agent 서비스는 `openstack-control-plane=enabled` 라벨로 노드에서 "
"실행되도록 스케줄됩니다."
msgid "neutron-lb-agent"
msgstr "neutron-lb-agent"
msgid "neutron-metadata-agent"
msgstr "neutron-metadata-agent"
msgid ""
"neutron-metadata-agent service is scheduled to run on nodes with the label "
"`openstack-control-plane=enabled`."
msgstr ""
"neutron-metadata-agent 서비스는 `openstack-control-plane=enabled` 라벨로 노드"
"에서 실행되도록 스케줄됩니다."
msgid "neutron-ovs-agent"
msgstr "neutron-ovs-agent"
msgid "neutron-server"
msgstr "neutron-server"
msgid ""
"neutron-server is serving the networking REST API for operator and other "
"OpenStack services usage. The internals of Neutron are highly flexible, "
"providing plugin mechanisms for all networking services exposed. The "
"consistent API is exposed to the user, but the internal implementation is up "
"to the chosen SDN."
msgstr ""
"neutron-server는 운영자와 다른 OpenStack 서비스 사용을 위한 네트워킹 REST API"
"를 제공합니다. Neutron 내부 구조는 유연성이 뛰어나, 노출된 모든 네트워킹 서비"
"스를 위한 플러그인 매커니즘을 제공합니다. 일관된 API는 사용자에게 노출되지"
"만, 내부 구현은 선택된 SDN가 결정합니다."
msgid "openvswitch-db and openvswitch-vswitchd"
msgstr "openvswitch-db와 openvswitch-vswitchd"
msgid "port"
msgstr "포트"
msgid ""
"pull\\_policy: The image pull policy, one of \"Always\", \"IfNotPresent\", "
"and \"Never\" which will be used by all containers in the chart."
msgstr ""
"pull\\_policy: 차트 내 모든 컨테이너가 사용할 \"Always\", \"IfNotPresent\", "
"그리고 \"Never\" 중 하나의 이미지 pull 정책"
msgid "subnet"
msgstr "서브넷"

File diff suppressed because it is too large Load Diff

View File

@ -1,202 +0,0 @@
# Soonyeul Park <ardentpark@gmail.com>, 2018. #zanata
# KEONWOO LEE <lkeonw0o@naver.com>, 2020. #zanata
msgid ""
msgstr ""
"Project-Id-Version: openstack-helm 0.1.1.dev3462\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2021-06-22 20:22+0000\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"PO-Revision-Date: 2020-09-08 02:58+0000\n"
"Last-Translator: KEONWOO LEE <lkeonw0o@naver.com>\n"
"Language-Team: Korean (South Korea)\n"
"Language: ko_KR\n"
"X-Generator: Zanata 4.3.3\n"
"Plural-Forms: nplurals=1; plural=0\n"
msgid "Backing up a PVC"
msgstr "PVC 백업"
msgid ""
"Backing up a PVC stored in Ceph, is fairly straigthforward, in this example "
"we use the PVC ``mysql-data-mariadb-server-0`` as an example, but this will "
"also apply to any other services using PVCs eg. RabbitMQ, Postgres."
msgstr ""
"Ceph에 저장된 PVC를 백업하는 것은 아주 간단합니다. 본 예시에서 PVC의 ``mysql-"
"data-mariadb-server-0`` 을 예로 들겠지만, 이는 또한 RabbitMQ, Postgres 와 같"
"은 다른 서비스에도 적용 가능할 것입니다."
msgid ""
"Before proceeding, it is important to ensure that you have deployed a client "
"key in the namespace you wish to fulfill ``PersistentVolumeClaims``. To "
"verify that your deployment namespace has a client key:"
msgstr ""
"진행하기 전에, ``PersistentVolumeClaims`` 를 만족하기를 원하는 네임스페이스"
"에 클라이언트 키를 배포했는지 보장하는 것이 중요합니다. 네임스페이스가 클라이"
"언트 키를 가지고 있는지에 대한 검증은 다음과 같습니다:"
msgid "Bugs and Feature requests"
msgstr "버그와 기능 요청"
msgid "Ceph"
msgstr "Ceph"
msgid "Ceph Deployment Status"
msgstr "Ceph 배포 상태"
msgid "Ceph Validating PVC Operation"
msgstr "Ceph의 PVC 작업 검증"
msgid "Ceph Validating StorageClass"
msgstr "Ceph의 StorageClass 검증"
msgid "Channels"
msgstr "채널"
msgid "Database Deployments"
msgstr "데이터베이스 배포"
msgid ""
"First, we want to validate that Ceph is working correctly. This can be done "
"with the following Ceph command:"
msgstr ""
"먼저, Ceph가 정확하게 작동하고 있는지 확인하고 싶습니다. 이는 다음과 같은 "
"Ceph 명령을 통해 수행될 수 있습니다:"
msgid "Galera Cluster"
msgstr "Galera 클러스터"
msgid "Getting help"
msgstr "도움말"
msgid "Installation"
msgstr "설치"
msgid "Join us on `Slack <http://slack.k8s.io/>`_ - #openstack-helm"
msgstr "`Slack <http://slack.k8s.io/>`_ - #openstack-helm 에 가입합니다."
msgid ""
"Next we can look at the storage class, to make sure that it was created "
"correctly:"
msgstr ""
"다음으로 올바르게 생성되었는지를 확인하기 위해, 저장소 클래스를 살펴볼 수 있"
"습니다:"
msgid ""
"Note: This step is not relevant for PVCs within the same namespace Ceph was "
"deployed."
msgstr ""
"참고: 이 단계는 Ceph가 배포된 동일한 네임스페이스 내의 PVC와는 관련이 없습니"
"다."
msgid "Once this has been done the workload can be restarted."
msgstr "이 작업이 완료되면 워크로드를 재시작할 수 있습니다."
msgid "PVC Preliminary Validation"
msgstr "PVC 사전 검증"
msgid "Persistent Storage"
msgstr "Persistent 스토리지"
msgid ""
"Please, refer to `Contribution guidelines <../contributor/contributing."
"html>`_."
msgstr ""
" `컨트리뷰션 가이드라인 <../contributor/contributing.html>`_ 을 참조하세요"
msgid ""
"Restoring is just as straightforward. Once the workload consuming the device "
"has been stopped, and the raw RBD device removed the following will import "
"the back up and create a device:"
msgstr ""
"복구도 마찬가지로 간단합니다. 장치를 소비하는 워크로드가 멈추고 raw RBD 장치"
"가 제거되면, 다음과 같이 백업을 가져와 장치를 생성할 것입니다:"
msgid ""
"Sometimes things go wrong. These guides will help you solve many common "
"issues with the following:"
msgstr ""
"가끔 이상이 발생할 때, 이 안내서가 다음과 같은 여러가지 일반적인 문제들을 해"
"결하는 데 도움이 될 것입니다."
msgid ""
"The parameters are what we're looking for here. If we see parameters passed "
"to the StorageClass correctly, we will see the ``ceph-mon.ceph.svc.cluster."
"local:6789`` hostname/port, things like ``userid``, and appropriate secrets "
"used for volume claims."
msgstr ""
"여기서 찾고있는 것은 매개 변수입니다. 매개 변수가 StorageClass를 올바르게 통"
"과했는지 확인했다면, ``userid``, 그리고 볼륨 클레임을 위해 사용되는 적절한 비"
"밀과 같은 ``ceph-mon.ceph.svc.cluster.local:6789`` hostname/port 를 확인할 "
"수 있습니다."
msgid ""
"This guide is to help users debug any general storage issues when deploying "
"Charts in this repository."
msgstr ""
"이 안내서는 사용자가 저장소에 차트를 배포할 때의 일반적인 저장소 문제들을 디"
"버그하는 것을 돕기 위한 것입니다."
msgid ""
"This guide is to help users debug any general storage issues when deploying "
"charts in this repository."
msgstr ""
"이 안내서는 사용자가 저장소에 차트를 배포할 때의 일반적인 저장소 문제들을 디"
"버그하는 것을 돕기 위한 것입니다."
msgid ""
"To deploy the HWE kernel, prior to deploying Kubernetes and OpenStack-Helm "
"the following commands should be run on each node:"
msgstr ""
"HWE 커널을 배포하려면, Kubernetes와 OpenStack-Helm을 배포하기 전에 각 노드에"
"서 다음과 같은 명령을 실행해야 합니다."
msgid ""
"To make use of CephFS in Ubuntu the HWE Kernel is required, until the issue "
"described `here <https://github.com/kubernetes-incubator/external-storage/"
"issues/345>`_ is fixed."
msgstr ""
"Ubuntu에서 CephFS를 사용하려면, `여기 <https://github.com/kubernetes-"
"incubator/external-storage/issues/345>`_ 에 기술된 문제가 해결될 때까지 HWE "
"커널이 필요합니다."
msgid "To test MariaDB, do the following:"
msgstr "MariaDB를 테스트하려면, 다음과 같이 수행하십시오:"
msgid ""
"To validate persistent volume claim (PVC) creation, we've placed a test "
"manifest `here <https://raw.githubusercontent.com/openstack/openstack-helm/"
"master/tests/pvc-test.yaml>`_. Deploy this manifest and verify the job "
"completes successfully."
msgstr ""
"persistent volume claim (PVC) 생성을 검증하기 위해서, `여기 <https://raw."
"githubusercontent.com/openstack/openstack-helm/master/tests/pvc-test.yaml>`_ "
"에 테스트 매니페스트를 배치하였습니다. 이 매니페스트를 배포하고 작업이 성공적"
"으로 완료되었는지 확인합니다."
msgid "Troubleshooting"
msgstr "트러블슈팅"
msgid "Ubuntu HWE Kernel"
msgstr "Ubuntu HWE 커널"
msgid ""
"Use one of your Ceph Monitors to check the status of the cluster. A couple "
"of things to note above; our health is `HEALTH\\_OK`, we have 3 mons, we've "
"established a quorum, and we can see that all of our OSDs are up and in the "
"OSD map."
msgstr ""
"Ceph 모니터 중 하나를 사용하여 클러스터의 상태를 점검하십시오. 위의 몇 가지 "
"사항을 참고했을 때; health는 `HEALTH\\_OK`, mon은 3개로 quorum을 설정하였고, "
"모든 OSD가 up되어 OSD 맵 안에 있음을 확인할 수 있습니다."
msgid ""
"Without this, your RBD-backed PVCs will never reach the ``Bound`` state. "
"For more information, see how to `activate namespace for ceph <../install/"
"multinode.html#activating-control-plane-namespace-for-ceph>`_."
msgstr ""
"이것 없이는, RBD-backed PVC 는 절대로 ``Bound`` 상태가 될 수 없을 것입니다. "
"더 많은 정보를 위해서는, 어떻게 `ceph를 위한 네임스페이스를 활성화 <../"
"install/multinode.html#activating-control-plane-namespace-for-ceph>`_ 하는지 "
"보십시오."

View File

@ -1,356 +0,0 @@
# Ian Y. Choi <ianyrchoi@gmail.com>, 2018. #zanata
# Soonyeul Park <ardentpark@gmail.com>, 2018. #zanata
# Sungjin Kang <gang.sungjin@gmail.com>, 2018. #zanata
msgid ""
msgstr ""
"Project-Id-Version: openstack-helm 0.1.1.dev3879\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2022-10-24 20:45+0000\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"PO-Revision-Date: 2018-10-21 06:41+0000\n"
"Last-Translator: Sungjin Kang <gang.sungjin@gmail.com>\n"
"Language-Team: Korean (South Korea)\n"
"Language: ko_KR\n"
"X-Generator: Zanata 4.3.3\n"
"Plural-Forms: nplurals=1; plural=0\n"
msgid ":ref:`genindex`"
msgstr ":ref:`genindex`"
msgid ":ref:`search`"
msgstr ":ref:`search`"
msgid "Adding Services"
msgstr "서비스 추가"
msgid "Adding Tests"
msgstr "테스트 추가"
msgid ""
"Any additional functions required for testing new charts or improving the "
"gate workflow should be placed in the appropriate location."
msgstr ""
"새로운 차트들을 테스트하거나 게이트 워크 플로우를 개선하기 위한 추가적인 기능"
"들은 적절한 장소에 위치해야 합니다."
msgid ""
"Any tests that do not use the Rally testing framework would need to be "
"handled in the appropriate manner in launch script. This would ideally "
"result in new functions that could be reused, or expansion of the gate "
"scripts to include scenarios beyond basic service launches."
msgstr ""
"Rally 테스팅 프레임워크를 사용하지 않은 테스트는 시작 스크립트에서 적절한 방"
"식으로 처리해야 합니다. 이는 재사용 될 수 있는 새로운 기능이나, 기본 서비스 "
"시작 이상의 시나리오들을 포함하기 위한 게이트 스크립트들의 확장이라는 이상적"
"인 결과를 가져올 것입니다."
msgid ""
"As charts for additional services are added to OpenStack-Helm, they should "
"be included in the gates. Adding new services to the gates allows a chart "
"developer and the review team to identify any potential issues associated "
"with a new service. All services are currently launched in the gate via a "
"series of launch scripts of the format ``NNN-service-name.sh`` where ``NNN`` "
"dictates the order these scripts are launched. The script should contain an "
"installation command like:"
msgstr ""
"추가적인 서비스들을 위한 차트로서 OpenStack-Helm에 추가되기 위해, 그들은 그 "
"게이트에 포함되어야만 합니다. 새로운 서비스들을 게이트에 추가하는 것은 차트 "
"개발자와 검토 팀에게 새로운 서비스와 연관된 잠재적인 문제를 확인하는 것을 허"
"락합니다. 모든 서비스는 현재 게이트 내에서 ``NNN``이 이 스크립트들이 시작되"
"는 순서를 지정하는 ``NNN-service-name.sh``라는 일련의 시작 스크립트 형식을 통"
"해 시작됩니다."
msgid ""
"As new charts are developed and the services are added to the gate, an "
"associated Helm test should be introduced to the gates. The appropriate "
"place for executing these tests is in the respective service's launch "
"script, and must be placed after the entry for installing the service and "
"any associated overrides. Any tests that use the Rally testing framework "
"should leverage the helm_test_deployment function in the aforementioned "
"funcs/helm.sh file. For example, a Helm test for Mistral might look like:"
msgstr ""
"새 차트들이 개발되고 서비스가 게이트에 추가되기 위해서, 연관된 Helm 테스트가 "
"게이트에 도입되어야 합니다. 이러한 테스트들을 실행하기 위한 최적 위치는 각 서"
"비스의 시작 스크립트에 있으며, 서비스와 관련 오버라이드들을 설치하기 위한 엔"
"트리 뒤에 있어야 합니다. Rally 테스팅 프레임워크를 사용하는 테스트들은 앞서 "
"언급한 funcs/helm.sh 파일의 helm_test_deployment 기능을 활용해야 합니다. 예"
"를 들어, Mistral을 위한 Helm 테스트는 아래와 같이 보일 것입니다:"
msgid ""
"Bugs and enhancements are tracked via OpenStack-Helm's `Storyboard <https://"
"storyboard.openstack.org/#!/project_group/64>`_."
msgstr ""
"버그 및 개선사항은 OpenStack-Helm의 `Storyboard <https://storyboard."
"openstack.org/#!/project_group/64>`_ 에서 추적이 이루어집니다."
msgid "Communication"
msgstr "의사소통"
msgid "Contents:"
msgstr "목차:"
msgid "Contributing"
msgstr "기여하기"
msgid ""
"Developers wishing to work on the OpenStack-Helm project should always base "
"their work on the latest code, available from the OpenStack-Helm git "
"repository."
msgstr ""
"OpenStack-Helm 프로젝트에서 작업하고자 하는 개발자는 OpenStack-Helm git 저장"
"소에서 제공하는 최신 코드를 가지고서 작업하여야 합니다."
msgid ""
"Functions for Helm specific operations, found in helm.sh. These functions "
"include: installing Helm, serving a Helm repository locally, linting and "
"building all Helm charts, running Helm tests on a release, installing the "
"helm template plugin, and running the helm template plugin against a chart."
msgstr ""
"Helm 특정 작업들을 위한 기능들은, helm.sh에서 찾을 수 있습니다. 이 기능들은 "
"포함합니다: Helm 설치, 로컬의 Helm 저장소 제공, 모든 Helm 차트에 대한 linting"
"과 building, 배포 상에서 Helm 테스트를 수행, Helm 템플릿 플러그인 설치, 그리"
"고 차트에 대한 Helm 템플릿 플러그인을 실행합니다."
msgid ""
"Functions for Kubernetes specific operations, found in kube.sh. These "
"functions include: waiting for pods in a specific namespace to register as "
"ready, waiting for all nodes to register as ready, install the requirements "
"for the kubeadm-aio container used in the gates, building the kubeadm-aio "
"container, launching the kubeadm-aio container, and replacing the kube-"
"controller-manager with a specific image necessary for ceph functionality."
msgstr ""
"Kubernetes 특정 작업들을 위한 기능들은, kube.sh에서 찾을 수 있습니다. 이 기능"
"들은 포함합니다: 준비 상태로 등록하기 위해 특정 namespace 내의 pod들을 대기, "
"준비 상태로 등록하기 위해 모든 node를 대기, 게이트들에서 사용되는 kubeadm-"
"aio 컨테이너를 위한 요구사항들을 설치, kubeadm-aio 컨테이너 빌드, kubeadm-"
"aio 컨테이너 시작, 그리고 kube-controller-manager를 ceph 기능을 위해 필요한 "
"특정 이미지로 대체."
msgid ""
"Functions for OpenStack specific operations, found in openstack.sh. These "
"functions include: waiting for a successful ping, and waiting for a booted "
"virtual machine's status to return as ACTIVE."
msgstr ""
"OpenStack 특정 작업들을 위한 기능들은, openstack.sh에서 찾을 수 있습니다. 이 "
"기능들은 포함합니다: 성공적인 ping을 대기, 그리고 부팅된 가상머신의 상태를 "
"ACTIVE로 반환하기 위해 대기."
msgid "Functions for common host preparation operations, found in common.sh"
msgstr "일반 호스트 작업 준비 기능은, common.sh에서 찾을 수 있습니다."
msgid ""
"Functions for network specific operations, found in network.sh. These "
"functions include: creating a backup of the host's resolv.conf file before "
"deploying the kubeadm environments, restoring the original resolv.conf "
"settings, creating a backup of the host's /etc/hosts file before adding the "
"hosts interface and address, and restoring the original /etc/hosts file."
msgstr ""
"네트워크 특정 작업들을 위한 기능들은, network.sh에서 찾을 수 있습니다. 이 기"
"능들은 포함합니다: kubeadm 환경들에 배포하기 전에 호스트의 resolv.conf 파일"
"의 백업을 생성, 원본 resolv.conf 설정들을 복구, hosts의 인터페이스와 주소를 "
"추가하기 전에 호스트의 /etc/hosts 파일의 백업을 생성, 그리고 원본 /etc/hosts "
"파일을 복구."
msgid "Gate Checks"
msgstr "게이트 점검 사항"
msgid "Gate Functions"
msgstr "게이트 기능"
msgid "Gate Output"
msgstr "게이트 출력"
msgid "Indices and Tables"
msgstr "색인 및 표"
msgid "Installation and Development"
msgstr "설치 및 배포"
msgid ""
"Join us on `Slack <https://kubernetes.slack.com/messages/C3WERB7DE/>`_ - "
"#openstack-helm"
msgstr ""
"`Slack <https://kubernetes.slack.com/messages/C3WERB7DE/>`_ - #openstack-"
"helm 에 가입합니다"
msgid ""
"Meeting Agenda Items: `Agenda <https://etherpad.openstack.org/p/openstack-"
"helm-meeting-agenda>`_"
msgstr ""
"미팅 아젠다 항목: `Agenda <https://etherpad.openstack.org/p/openstack-helm-"
"meeting-agenda>`_"
msgid "Mission"
msgstr "임무"
msgid "OpenStack-Helm"
msgstr "OpenStack-Helm"
msgid "OpenStack-Helm Gates"
msgstr "OpenStack-Helm 게이트"
msgid "OpenStack-Helm currently checks the following scenarios:"
msgstr "OpenStack-Helm은 현재 다음의 시나리오들을 점검합니다:"
msgid ""
"OpenStack-Helm's single node and multinode gates leverage the kubeadm-aio "
"environment created and maintained for use as a development environment. "
"All information regarding the kubeadm-aio environment can be found here_."
msgstr ""
"OpenStack-Helm의 단일 노드와 다중 노드 게이트를 개발환경으로 사용하기 위해 생"
"성되고 유지되는 kubeadm-aio 환경을 활용합니다. kubeadm-aio 환경에 관한 모든 "
"정보는 여기에서 찾을 수 있습니다."
msgid ""
"Provisioning a multi-node Ubuntu-1604 cluster and deploying the OpenStack "
"services. This check is provided for both a two node cluster and a three "
"node cluster."
msgstr ""
"다중 노드의 Ubuntu-1604 클러스터를 프로비저닝하고 OpenStack 서비스에 배포합니"
"다. 두 노드와 세 노드의 클러스터 모두 이를 제공합니다."
msgid ""
"Provisioning a single node cluster and deploying the OpenStack services. "
"This check is provided for: Ubuntu-1604, CentOS-7, and Fedora-25."
msgstr ""
"단일 노드를 프로비저닝하고 OpenStack 서비스에 배포합니다. Ubuntu-1604, "
"CentOS-7, 그리고 Fedora-25가 이를 제공합니다. "
msgid "Repository"
msgstr "저장소"
msgid ""
"Running Make on each chart, which lints and packages the charts. This gate "
"does not stand up a Kubernetes cluster."
msgstr ""
"lint하고 package한 각 chart마다 make를 실행합니다. 이 게이트는 Kubernes 클러"
"스터를 유지하지 않습니다."
msgid ""
"Some services in the gate require specific overrides to the default values "
"in the chart's values.yaml file. If a service requires multiple overrides "
"to function in the gate, the service should include a separate values.yaml "
"file placed in the tools/overrides/mvp directory. The <service>.yaml MVP "
"files provide a configuration file to use for overriding default "
"configuration values in the chart's values.yaml as an alternative to "
"overriding individual values during installation. A chart that requires a "
"MVP overrides file requires the following format:"
msgstr ""
"게이트의 어떤 서비스는 차트의 value.yaml 파일의 기본값에 대한 특정 오버라이"
"드들을 요구합니다. 서비스가 게이트에서 기능하기 위한 다수의 오버라이드를 요구"
"한다면, 그 서비스는 tools/overrides/mvp 디렉터리 내 별도의 values.yaml 파일"
"을 포함해야 합니다. <service>.yaml MVP 파일들은 설치 중에 오버라이딩한 개개"
"의 값들에 대한 대안으로 차트의 values.yaml의 기본 구성 값들을 오버라이딩 하"
"여 사용하기 위한 구성 파일을 제공합니다. MVP 오버라이드 파일이 요구한 차트는 "
"다음의 포맷을 요구로 합니다:"
msgid "Storyboard"
msgstr "Storyboard"
msgid "Testing any documentation changes and impacts."
msgstr "문서 변경과 영향 테스트"
msgid ""
"The K8s directory contains the logs and output of the Kubernetes objects. "
"It includes: pods, nodes, secrets, services, namespaces, configmaps, "
"deployments, daemonsets, and statefulsets. Descriptions for the state of "
"all resources during execution are found here, and this information can "
"prove valuable when debugging issues raised during a check. When a single "
"node or multi-node check fails, this is the first place to look. The logs "
"found here are helpful when the templates render correctly, but the services "
"are not functioning correctly, whether due to service configuration issues "
"or issues with the pods themselves."
msgstr ""
"K8s 디렉터리는 Kubernetes 오즈젝트에 대한 로그와 출력물이 저장됩니다. 여기에"
"는 pods, nodes, secrets, services, namespaces, configmaps, deployments, "
"daemonsets, statefulsets 들이 포함됩니다. 실행 중인 모든 자원의 상태를 확인"
"할 수 있는 설명들이 여기에 있으며, 이 정보는 검사 중 발생하는 문제를 디버깅할"
"때 유용합니다. 단일 노드 또는 다중 노드 검사가 실패했을 때, 여기를 가장 먼저 "
"확인합니다. 이곳에 있는 로그는 템플릿으로 올바르게 렌더링되지만 서비스 구성 "
"문제나 pods 자체 관련된 문제로 인해 제대로 작동하지 않을때 유용합니다."
msgid ""
"The dry-runs directory contains the rendered output of Helm dry-run installs "
"on each of the OpenStack service charts. This gives visibility into the "
"manifests created by the templates with the supplied values. When the dry-"
"run gate fails, the reason should be apparent in the dry-runs output. The "
"logs found here are helpful in identifying issues resulting from using helm-"
"toolkit functions incorrectly or other rendering issues with gotpl."
msgstr ""
"dry-runs 디렉터리는 각 OpenStack 서비스 차트의 Helm 모의 설치들에서 만들어진 "
"출력을 포함하고 있습니다. 이렇게하면 제공된 값으로 템플릿들이 만든 매니페스트"
"를 볼 수 있습니다. 모의 게이트가 실패하면, 모의 출력에서 그 이유가 분명해야 "
"합니다. 이곳에서 발견할 수 있는 로그는 helm-toolkit 기능들의 오용이나 gotpl"
"로 만들어진 다른 문제들의 결과에 따른 문제들을 확인하는데 도움이 됩니다."
msgid ""
"The goal of OpenStack-Helm is to provide a collection of Helm charts that "
"simply, resiliently, and flexibly deploy OpenStack and related services on "
"Kubernetes."
msgstr ""
"OpenStack-Helm 목표는 Kubernetes 위에 OpenStack 및 관련 서비스들을 단순하고, "
"탄력적이며, 유연하게 배포하는 Helm 차트에 대한 집합을 제공하는 데 있습니다."
msgid ""
"The nodes directory contains information about the node the gate tests are "
"running on in openstack-infra. This includes: the network interfaces, the "
"contents of iptables, the host's resolv.conf, and the kernel IP routing "
"table. These logs can be helpful when trying to identify issues with host "
"networking or other issues at the node level."
msgstr ""
"노드의 디렉터리는 해당 노드에 대한 정보를 포함합니다. 게이트 테스트는 "
"openstack-infra 내에서 동작합니다. 이것은 포함합니다: 네트워크 인터페이스, "
"iptables 내용, 호스트의 resolv.conf, 그리고 커널 IP 라우팅 테이블. 이 로그들"
"은 노드 레벨에서 호스트 네트워킹이나 다른 문제들을 확인하고자 할 때 도움이 됩"
"니다."
msgid ""
"This project is under active development. We encourage anyone interested in "
"OpenStack-Helm to review our `Installation <https://docs.openstack.org/"
"openstack-helm/latest/install/index.html>`_ documentation. Feel free to ask "
"questions or check out our current `Storyboard backlog <https://storyboard."
"openstack.org/#!/project_group/64>`_."
msgstr ""
"이 프로젝트는 적극적으로 개발 중인 상태입니다. OpenStack-Helm에 대해 관심있"
"는 분들은 `Installation <https://docs.openstack.org/openstack-helm/latest/"
"install/index.html>`_ 문서를 살펴 보십시오. 자유롭게 질문하거나 현재 "
"`Storyboard 백로그 <https://storyboard.openstack.org/#!/project_group/64>`_ "
"를 살펴봅니다."
msgid "This results in the gate running the following:"
msgstr "게이트 실행 결과는 다음과 같습니다."
msgid ""
"To evaluate a multinode installation, follow the `Bare Metal <https://docs."
"openstack.org/openstack-helm/latest/install/multinode.html>`_ install guide."
msgstr ""
"멀티노드 설치를 평가해 보려면 `Bare Metal <https://docs.openstack.org/"
"openstack-helm/latest/install/multinode.html>`_ 설치 가이드를 따릅니다."
msgid ""
"To facilitate ease of testing and debugging, information regarding gates and "
"their functionality can be found here."
msgstr ""
"테스팅 및 디버깅을 보다 쉽게 해 주는, 게이트 및 해당 기능에 대한 정보를 여기"
"에서 찾을 수 있습니다."
msgid ""
"To provide meaningful output from the gates, all information pertaining to "
"the components of the cluster and workflow are output to the logs directory "
"inside each gate. The contents of the log directory are as follows:"
msgstr ""
"게이트로부터 의미 있는 출력을 제공하기 위해서는, 클러스터와 워크 플로우의 구"
"성요소와 관련된 모든 정보가 각 게이트 내부의 logs 디렉터리에 출력됩니다. 로"
"그 디렉터리의 내용들은 다음과 같습니다:"
msgid ""
"To provide reusable components for gate functionality, functions have been "
"provided in the gates/funcs directory. These functions include:"
msgstr ""
"게이트의 기능을 위한 재사용 가능한 구성요소들을 제공하기 위해, gates/funcs 디"
"렉터리 내에 기능들을 제공합니다. 이 기능들은 포함합니다:"
msgid "Welcome to OpenStack-Helm's documentation!"
msgstr "OpenStack-Helm의 문서에 오신 것을 환영합니다!"

View File

@ -1,204 +0,0 @@
# Roman Gorshunov <roman.gorshunov@att.com>, 2020. #zanata
msgid ""
msgstr ""
"Project-Id-Version: openstack-helm 0.1.1.dev3462\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2021-06-22 20:22+0000\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"PO-Revision-Date: 2020-03-06 04:06+0000\n"
"Last-Translator: Roman Gorshunov <roman.gorshunov@att.com>\n"
"Language-Team: Russian\n"
"Language: ru\n"
"X-Generator: Zanata 4.3.3\n"
"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2)\n"
msgid "Backing up a PVC"
msgstr "Резервное копирование PVC"
msgid ""
"Backing up a PVC stored in Ceph, is fairly straigthforward, in this example "
"we use the PVC ``mysql-data-mariadb-server-0`` as an example, but this will "
"also apply to any other services using PVCs eg. RabbitMQ, Postgres."
msgstr ""
"Резервное копирование PVC, хранящегося в Ceph, достаточно просто. Ниже для "
"примера приведён PVC ``mysql-data-mariadb-server-0``, но та же процедура "
"подходит и для любых других сервисов, использующих PVC, таких как RabbitMQ "
"или Postgres."
msgid ""
"Before proceeding, it is important to ensure that you have deployed a client "
"key in the namespace you wish to fulfill ``PersistentVolumeClaims``. To "
"verify that your deployment namespace has a client key:"
msgstr ""
"Перед тем, как продолжить далее, важно убедиться, что вы установили "
"клиентский ключ в том пространстве имён, в котором вы собираетесь заполнять "
"``PersistentVolumeClaims``. Выполните нижеприведённую команду для проверки "
"того, что в этом пространстве имён есть клиеннтский ключ:"
msgid "Bugs and Feature requests"
msgstr "Сообщения об ошибках и запросы нового функционала"
msgid "Ceph"
msgstr "Ceph"
msgid "Ceph Deployment Status"
msgstr "Статус развёртывания Ceph"
msgid "Ceph Validating PVC Operation"
msgstr "Проверка работы PVC Ceph"
msgid "Ceph Validating StorageClass"
msgstr "Проверка StorageClass'а Ceph"
msgid "Channels"
msgstr "Чаты"
msgid "Database Deployments"
msgstr "Развёртывание баз данных"
msgid ""
"First, we want to validate that Ceph is working correctly. This can be done "
"with the following Ceph command:"
msgstr ""
"В начале давайте проверим, что Ceph работоспособен. Это можно сделать с "
"помощью следующей команды Ceph:"
msgid "Galera Cluster"
msgstr "Кластер Galera"
msgid "Getting help"
msgstr "Помощь"
msgid "Installation"
msgstr "Установка и развёртывание"
msgid "Join us on `Slack <http://slack.k8s.io/>`_ - #openstack-helm"
msgstr ""
"Присоединяйтесь к нам в `Slack <http://slack.k8s.io/>`_ - #openstack-helm"
msgid ""
"Next we can look at the storage class, to make sure that it was created "
"correctly:"
msgstr ""
"Далее мы можем посмотреть на класс хранилища, чтобы убедиться, что он создан "
"корректно:"
msgid ""
"Note: This step is not relevant for PVCs within the same namespace Ceph was "
"deployed."
msgstr ""
"Важно: Этот шаг не имеет отношения к PVC в тех же пространствах имён, в "
"которых развёрнут Ceph."
msgid "Once this has been done the workload can be restarted."
msgstr "После вполнения процедуры рабочая нагрузка может быть перезапущена."
msgid "PVC Preliminary Validation"
msgstr "Предварительная проверка PVC"
msgid "Persistent Storage"
msgstr "Постоянное хранилище"
msgid ""
"Restoring is just as straightforward. Once the workload consuming the device "
"has been stopped, and the raw RBD device removed the following will import "
"the back up and create a device:"
msgstr ""
"Восстановление - так же достаточно простая процедура. Как только рабочая "
"нагрузка использующая устройство остановлена, и отключено устройство с "
"сырыми данными RBD, нижеприведённая процедура импортирует резерную копию и "
"создаст устройство."
msgid ""
"Sometimes things go wrong. These guides will help you solve many common "
"issues with the following:"
msgstr ""
"Иногда что-то идёт не так. Эти руководства помогут вам разрешить многие из "
"типичных проблем:"
msgid ""
"The parameters are what we're looking for here. If we see parameters passed "
"to the StorageClass correctly, we will see the ``ceph-mon.ceph.svc.cluster."
"local:6789`` hostname/port, things like ``userid``, and appropriate secrets "
"used for volume claims."
msgstr ""
"Здесь мы должны обратить внимание на параметры. Если они корректно преданы "
"StorageClass'у, то мы увидим имя хоста/порт как ``ceph-mon.ceph.svc.cluster."
"local:6789``, а так же ``userid``, и соответствующие секреты, использующиеся "
"для запроса томов хранилищ."
msgid ""
"This guide is to help users debug any general storage issues when deploying "
"Charts in this repository."
msgstr ""
"Это руководство предназначается для помощи пользователям в поиске и "
"исправлении типичных ошибок в подсистеме хранения данных при развёртывании "
"Chart'ов этого репозитория."
msgid ""
"This guide is to help users debug any general storage issues when deploying "
"charts in this repository."
msgstr ""
"Это руководство предназначается для помощи пользователям в поиске и "
"исправлении типичных ошибок в подсистеме хранения данных при развёртывании "
"Chart'ов этого репозитория."
msgid ""
"To deploy the HWE kernel, prior to deploying Kubernetes and OpenStack-Helm "
"the following commands should be run on each node:"
msgstr ""
"Для развёртывания HWE ядра перед установкой Kubernetes и OpenStack-Helm, "
"команды, приведённые ниже, должны быть выполнены на каждом узле:"
msgid ""
"To make use of CephFS in Ubuntu the HWE Kernel is required, until the issue "
"described `here <https://github.com/kubernetes-incubator/external-storage/"
"issues/345>`_ is fixed."
msgstr ""
"До исправления проблемы, описанной `здесь <https://github.com/kubernetes-"
"incubator/external-storage/issues/345>`_, для использования CephFS в Ubuntu "
"требуется использовать HWE ядро."
msgid "To test MariaDB, do the following:"
msgstr "Выполните эти команды для тестирования MariaDB:"
msgid ""
"To validate persistent volume claim (PVC) creation, we've placed a test "
"manifest `here <https://raw.githubusercontent.com/openstack/openstack-helm/"
"master/tests/pvc-test.yaml>`_. Deploy this manifest and verify the job "
"completes successfully."
msgstr ""
"Для проверки создания требования постоянного хранилища (PVC) мы "
"`опубликовали <https://raw.githubusercontent.com/openstack/openstack-helm/"
"master/tests/pvc-test.yaml>`_ тестовый манифест. Разверните его, и "
"убедитесь, что задание успешно завершается."
msgid "Troubleshooting"
msgstr "Поиск и устранение неполадок"
msgid "Ubuntu HWE Kernel"
msgstr "HWE ядро Ubuntu"
msgid ""
"Use one of your Ceph Monitors to check the status of the cluster. A couple "
"of things to note above; our health is `HEALTH\\_OK`, we have 3 mons, we've "
"established a quorum, and we can see that all of our OSDs are up and in the "
"OSD map."
msgstr ""
"Для проверки статуса кластера, воспользуйтесь одним из мониторов Ceph. "
"Некоторые замечания: статус здоровья - `HEALTH\\_OK`, у нас 3 монитора, "
"установлен кворум, а так же мы можем видеть, что все наши OSD работоспособны "
"и присутствуют в карте OSD."
msgid ""
"Without this, your RBD-backed PVCs will never reach the ``Bound`` state. "
"For more information, see how to `activate namespace for ceph <../install/"
"multinode.html#activating-control-plane-namespace-for-ceph>`_."
msgstr ""
"Без этого ваш PVC с RBD бэкэндом никогда не достигнет состояния ``Bound`` "
"(Подключен). За более подробной информацией обратитесь к разделу `активация "
"пространства имён Ceph <../install/multinode.html#activating-control-plane-"
"namespace-for-ceph>`_."

View File

@ -19,7 +19,7 @@ deps =
-r{toxinidir}/doc/requirements.txt
commands =
rm -rf doc/build
docstheme-build-translated.sh
sphinx-build -W --keep-going -b html -j auto doc/source doc/build/html
allowlist_externals =
rm