Imported Translations from Zanata

For more information about this automatic import see:
https://docs.openstack.org/i18n/latest/reviewing-translation-import.html

Change-Id: I16ac647725e260d75a489d33766246e7acd9baf7
This commit is contained in:
OpenStack Proposal Bot 2018-09-24 06:41:42 +00:00
parent 8e4ee070e6
commit c2459fe4e2
8 changed files with 4585 additions and 0 deletions

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

View File

@ -0,0 +1,759 @@
# Frank Kloeker <eumel@arcor.de>, 2018. #zanata
msgid ""
msgstr ""
"Project-Id-Version: openstack-helm\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-09-21 23:50+0000\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"PO-Revision-Date: 2018-09-15 08:14+0000\n"
"Last-Translator: Copied by Zanata <copied-by-zanata@zanata.org>\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 ""
"5. Replace the failed disk with a new one. If you repair (not replace) the "
"failed disk, you may need to run the following:"
msgstr ""
"5. Ersetzen Sie die fehlerhafte Festplatte durch eine neue. Wenn Sie die "
"fehlerhafte Festplatte reparieren (nicht ersetzen), müssen Sie "
"möglicherweise Folgendes ausführen:"
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 can be upgreade without downtime for Openstack components in a multinoe "
"env."
msgstr ""
"Ceph kann ohne Downtime für Openstack-Komponenten in einem Multiino-"
"Environment erweitert werden."
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 k8 cluster"
msgstr ""
"Gefolgt OSH Multinode Guide Schritte zum Einrichten von Knoten und "
"installieren k8-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 "Steps:"
msgstr "Schritte:"
msgid "Symptom:"
msgstr "Symptom:"
msgid "Test Environment"
msgstr "Testumgebung"
msgid "Test Scenario:"
msgstr "Testszenario:"
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 an OSD pod is deleted by ``kubectl delete "
"$OSD_POD_NAME``. Meanwhile, we monitor the status of Ceph and noted that it "
"takes about 90 seconds for the OSD running in deleted pod to recover from "
"``down`` to ``up``."
msgstr ""
"Dies dient zum Testen eines Szenarios, wenn ein OSD-Pod durch ``kubectl "
"delete $ OSD_POD_NAME`` gelöscht wird. In der Zwischenzeit überwachen wir "
"den Status von Ceph und stellen fest, dass es etwa 90 Sekunden dauert, bis "
"das OSD, das in dem gelöschten Pod läuft, von ``down`` nach ``up`` "
"zurückkehrt."
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 "To replace the failed OSD, excecute the following procedure:"
msgstr ""
"Um das fehlerhafte OSD zu ersetzen, führen Sie die folgenden Schritte aus:"
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 pod status through ``kubectl get pods -n ceph`` during "
"this process. The deleted OSD pod status changed as follows: ``Terminating`` "
"-> ``Init:1/3`` -> ``Init:2/3`` -> ``Init:3/3`` -> ``Running``, and this "
"process taks about 90 seconds. The reason is that Kubernetes automatically "
"restarts OSD pods whenever they are deleted."
msgstr ""
"Wir haben auch den Status der Pods über ``kubectl get pods -n ceph`` während "
"dieses Vorgangs überwacht. Der Status des gelöschten OSD-Pods ändert sich "
"wie folgt: ``Terminating`` -> ``Init:1/3`` -> ``Init:2/3`` -> ``Init:3/3`` -"
"> ``Running``, und dieser Vorgang dauert etwa 90 Sekunden. Der Grund dafür "
"ist, dass Kubernetes OSD-Pods automatisch neu startet, wenn sie gelöscht "
"werden."
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 ""
"``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

@ -0,0 +1,216 @@
# Frank Kloeker <eumel@arcor.de>, 2018. #zanata
msgid ""
msgstr ""
"Project-Id-Version: openstack-helm\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-09-21 23:50+0000\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"PO-Revision-Date: 2018-09-15 06:21+0000\n"
"Last-Translator: Copied by Zanata <copied-by-zanata@zanata.org>\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 `IRC <irc://chat.freenode.net:6697/openstack-helm>`_: #openstack-"
"helm on freenode"
msgstr ""
"Begleiten Sie uns auf `IRC <irc://chat.freenode.net:6697/openstack-helm>`_: "
"#openstack-helm auf freenode"
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 ""
"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 ""
"When discovering a new bug, please report a bug in `Storyboard <https://"
"storyboard.openstack.org/#!/project/886>`_."
msgstr ""
"Wenn Sie einen neuen Fehler entdecken, melden Sie bitte einen Fehler im "
"`Storyboard <https://storyboard.openstack.org/#!/project/886>`_."
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

@ -0,0 +1,437 @@
# Frank Kloeker <eumel@arcor.de>, 2018. #zanata
msgid ""
msgstr ""
"Project-Id-Version: openstack-helm\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-09-21 23:50+0000\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"PO-Revision-Date: 2018-09-15 03:03+0000\n"
"Last-Translator: Copied by Zanata <copied-by-zanata@zanata.org>\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:`modindex`"
msgstr ":ref: `modindex`"
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 "Bugs should be filed as stories in Storyboard, not GitHub:"
msgstr "Bugs sollten als Story im Storyboard abgelegt werden, nicht GitHub:"
msgid "Communication"
msgstr "Kommunikation"
msgid ""
"Community IRC Meetings: [Every Tuesday @ 3PM UTC], #openstack-meeting-5 on "
"freenode"
msgstr ""
"Community IRC Meetings: [Jeden Dienstag um 15:00 UTC], #openstack-meeting-5 "
"auf freenode"
msgid "Contents:"
msgstr "Inhalt:"
msgid "Contributing"
msgstr "Beitragend"
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 ""
"If you would like to contribute to the development of OpenStack, you must "
"follow the steps in this page:"
msgstr ""
"Wenn Sie zur Entwicklung von OpenStack beitragen möchten, müssen Sie die "
"Schritte auf dieser Seite befolgen:"
msgid "Indices and Tables"
msgstr "Indizes und Tabellen"
msgid "Installation and Development"
msgstr "Installation und Entwicklung"
msgid ""
"Join us on `IRC <irc://chat.freenode.net:6697/openstack-helm>`_: #openstack-"
"helm on freenode"
msgstr ""
"Begleiten Sie uns auf `IRC <irc://chat.freenode.net:6697/openstack-helm>`_: "
"#openstack-helm auf freenode"
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 ""
"Once those steps have been completed, changes to OpenStack should be "
"submitted for review via the Gerrit tool, following the workflow documented "
"at:"
msgstr ""
"Sobald diese Schritte abgeschlossen sind, sollten Änderungen an OpenStack "
"zur Überprüfung mit dem Gerrit-Tool gemäß dem dokumentierten Workflow "
"gesendet werden:"
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 ""
"Please review our `documentation <https://docs.openstack.org/openstack-helm/"
"latest/>`_. For quick installation, evaluation, and convenience, we have a "
"kubeadm based all-in-one solution that runs in a Docker container. The "
"Kubeadm-AIO set up can be found `here <https://docs.openstack.org/openstack-"
"helm/latest/install/developer/index.html>`_."
msgstr ""
"Bitte lesen Sie unsere `Dokumentation <https://docs.openstack.org/openstack-"
"helm/latest/>`_. Für schnelle Installation, Evaluierung und Komfort haben "
"wir eine kubeadm-basierte All-in-One-Lösung, die in einem Docker-Container "
"ausgeführt wird. Das Kubeadm-AIO-Setup finden Sie hier <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 ""
"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 "Pull requests submitted through GitHub will be ignored."
msgstr "Pull-Anfragen, die über GitHub gesendet werden, werden ignoriert."
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 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 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 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 "Welcome to OpenStack-Helm's documentation!"
msgstr "Willkommen zur Dokumentation von OpenStack-Helm!"
msgid "https://docs.openstack.org/infra/manual/developers.html"
msgstr "https://docs.openstack.org/infra/manual/developers.html"
msgid ""
"https://docs.openstack.org/infra/manual/developers.html#development-workflow"
msgstr ""
"https://docs.openstack.org/infra/manual/developers.html#development-workflow"
msgid "https://storyboard.openstack.org/#!/project/886"
msgstr "https://storycard.openstack.org/#!/project/886"

View File

@ -0,0 +1,213 @@
# suhartono <cloudsuhartono@gmail.com>, 2018. #zanata
msgid ""
msgstr ""
"Project-Id-Version: openstack-helm\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-09-21 23:50+0000\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"PO-Revision-Date: 2018-09-19 11:32+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 `IRC <irc://chat.freenode.net:6697/openstack-helm>`_: #openstack-"
"helm on freenode"
msgstr ""
"Bergabunglah dengan kami `IRC <irc://chat.freenode.net:6697/openstack-"
"helm>`_: #openstack-helm on freenode"
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 ""
"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 ""
"When discovering a new bug, please report a bug in `Storyboard <https://"
"storyboard.openstack.org/#!/project/886>`_."
msgstr ""
"Saat menemukan bug baru, laporkan bug di `Storyboard <https://storyboard."
"openstack.org/#!/project/886>`_."
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

@ -0,0 +1,421 @@
# suhartono <cloudsuhartono@gmail.com>, 2018. #zanata
msgid ""
msgstr ""
"Project-Id-Version: openstack-helm\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-09-21 23:50+0000\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"PO-Revision-Date: 2018-09-23 12:49+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:`modindex`"
msgstr ":ref:`modindex`"
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 "Bugs should be filed as stories in Storyboard, not GitHub:"
msgstr "Bug harus diajukan sebagai cerita di Storyboard, bukan GitHub:"
msgid "Communication"
msgstr "Komunikasi"
msgid ""
"Community IRC Meetings: [Every Tuesday @ 3PM UTC], #openstack-meeting-5 on "
"freenode"
msgstr ""
"Rapat IRC Komunitas: [Setiap Selasa @ 3PM UTC], #openstack-meeting-5 di "
"freenode"
msgid "Contents:"
msgstr "Isi:"
msgid "Contributing"
msgstr "Berkontribusi"
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 ""
"If you would like to contribute to the development of OpenStack, you must "
"follow the steps in this page:"
msgstr ""
"Jika Anda ingin berkontribusi pada pengembangan OpenStack, Anda harus "
"mengikuti langkah-langkah di halaman ini:"
msgid "Indices and Tables"
msgstr "Indeks dan Tabel"
msgid "Installation and Development"
msgstr "Instalasi dan Pengembangan"
msgid ""
"Join us on `IRC <irc://chat.freenode.net:6697/openstack-helm>`_: #openstack-"
"helm on freenode"
msgstr ""
"Bergabunglah dengan kami `IRC <irc://chat.freenode.net:6697/openstack-"
"helm>`_: #openstack-helm di freenode"
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 ""
"Once those steps have been completed, changes to OpenStack should be "
"submitted for review via the Gerrit tool, following the workflow documented "
"at:"
msgstr ""
"Setelah langkah-langkah tersebut selesai, perubahan OpenStack harus dikirim "
"untuk ditinjau melalui alat Gerrit, mengikuti alur kerja yang "
"didokumentasikan di:"
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 ""
"Please review our `documentation <https://docs.openstack.org/openstack-helm/"
"latest/>`_. For quick installation, evaluation, and convenience, we have a "
"kubeadm based all-in-one solution that runs in a Docker container. The "
"Kubeadm-AIO set up can be found `here <https://docs.openstack.org/openstack-"
"helm/latest/install/developer/index.html>`_."
msgstr ""
"Harap tinjau kami `documentation <https://docs.openstack.org/openstack-helm/"
"latest/>`_. Untuk instalasi cepat, evaluasi, dan kenyamanan, kami memiliki "
"solusi all-in-one berbasis kubeadm yang berjalan dalam kontainer Docker. "
"Pengaturan Kubeadm-AIO dapat ditemukan `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 ""
"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 "Pull requests submitted through GitHub will be ignored."
msgstr ""
"Permintaan tarik (pull request) yang dikirimkan melalui GitHub akan "
"diabaikan."
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 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 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 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 "Welcome to OpenStack-Helm's documentation!"
msgstr "Selamat datang di dokumentasi OpenStack-Helm!"
msgid "https://docs.openstack.org/infra/manual/developers.html"
msgstr "https://docs.openstack.org/infra/manual/developers.html"
msgid ""
"https://docs.openstack.org/infra/manual/developers.html#development-workflow"
msgstr ""
"https://docs.openstack.org/infra/manual/developers.html#development-workflow"
msgid "https://storyboard.openstack.org/#!/project/886"
msgstr "https://storyboard.openstack.org/#!/project/886"

View File

@ -0,0 +1,406 @@
# Ian Y. Choi <ianyrchoi@gmail.com>, 2018. #zanata
# Soonyeul Park <ardentpark@gmail.com>, 2018. #zanata
msgid ""
msgstr ""
"Project-Id-Version: openstack-helm\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-09-21 23:50+0000\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"PO-Revision-Date: 2018-09-21 09:47+0000\n"
"Last-Translator: Soonyeul Park <ardentpark@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:`modindex`"
msgstr ":ref:`modindex`"
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 "Bugs should be filed as stories in Storyboard, not GitHub:"
msgstr "버그는 GitHub가 아닌 Storyboard에 스토리 단위로 제출되어야 합니다:"
msgid "Communication"
msgstr "의사소통"
msgid ""
"Community IRC Meetings: [Every Tuesday @ 3PM UTC], #openstack-meeting-5 on "
"freenode"
msgstr ""
"Community IRC Meetings: [매주 화요일 @ 3PM UTC], freenode 내 #openstack-"
"meeting-5"
msgid "Contents:"
msgstr "목차:"
msgid "Contributing"
msgstr "기여하기"
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 ""
"If you would like to contribute to the development of OpenStack, you must "
"follow the steps in this page:"
msgstr ""
"OpenStack 개발에 기여하고자 한다면, 이 페이지에 있는 다음 단계를 따라야 합니"
"다:"
msgid "Indices and Tables"
msgstr "색인 및 표"
msgid "Installation and Development"
msgstr "설치 및 배포"
msgid ""
"Join us on `IRC <irc://chat.freenode.net:6697/openstack-helm>`_: #openstack-"
"helm on freenode"
msgstr ""
"`IRC <irc://chat.freenode.net:6697/openstack-helm>`_: freenode 내 #openstack-"
"helm 에 가입합니다"
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 ""
"Once those steps have been completed, changes to OpenStack should be "
"submitted for review via the Gerrit tool, following the workflow documented "
"at:"
msgstr ""
"해당 단계를 완료한 이후에는, OpenStack 변경 사항이 Gerrit 도구를 통해 리뷰 제"
"출이 이루어집니다. 이후 워크 플로우는 아래에 문서화되어 있습니다:"
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 ""
"Please review our `documentation <https://docs.openstack.org/openstack-helm/"
"latest/>`_. For quick installation, evaluation, and convenience, we have a "
"kubeadm based all-in-one solution that runs in a Docker container. The "
"Kubeadm-AIO set up can be found `here <https://docs.openstack.org/openstack-"
"helm/latest/install/developer/index.html>`_."
msgstr ""
"우리의 `문서 <https://docs.openstack.org/openstack-helm/latest/>`_ 를 검토해"
"주세요. 빠른 설치, 평가, 그리고 편의를 위해서, 우리는 kubeadm 기반의 Docker "
"컨테이너에서 실행되는 올인원 솔루션을 갖고 있습니다. Kubeadm-AIO 설치는 `여"
"기 <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 ""
"다중 노드의 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 "Pull requests submitted through GitHub will be ignored."
msgstr "GitHub를 통한 풀 리퀘스트는 다루어지지 않을 것입니다."
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 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 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 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의 문서에 오신 것을 환영합니다!"
msgid "https://docs.openstack.org/infra/manual/developers.html"
msgstr "https://docs.openstack.org/infra/manual/developers.html"
msgid ""
"https://docs.openstack.org/infra/manual/developers.html#development-workflow"
msgstr ""
"https://docs.openstack.org/infra/manual/developers.html#development-workflow"
msgid "https://storyboard.openstack.org/#!/project/886"
msgstr "https://storyboard.openstack.org/#!/project/886"