diff --git a/doc/source/locale/de/LC_MESSAGES/doc-devref.po b/doc/source/locale/de/LC_MESSAGES/doc-devref.po
deleted file mode 100644
index f06c95dacb..0000000000
--- a/doc/source/locale/de/LC_MESSAGES/doc-devref.po
+++ /dev/null
@@ -1,958 +0,0 @@
-# Andreas Jaeger <jaegerandi@gmail.com>, 2018. #zanata
-# Frank Kloeker <eumel@arcor.de>, 2018. #zanata
-msgid ""
-msgstr ""
-"Project-Id-Version: openstack-helm 0.1.1.dev3631\n"
-"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2022-02-23 21:11+0000\n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-"PO-Revision-Date: 2018-10-25 07:38+0000\n"
-"Last-Translator: Andreas Jaeger <jaegerandi@gmail.com>\n"
-"Language-Team: German\n"
-"Language: de\n"
-"Plural-Forms: nplurals=2; plural=(n != 1)\n"
-"X-Generator: Zanata 4.3.3\n"
-
-msgid ""
-"**Note:** The values defined in a PodDisruptionBudget may conflict with "
-"other values that have been provided if an operator chooses to leverage "
-"Rolling Updates for deployments.  In the case where an operator defines a "
-"``maxUnavailable`` and ``maxSurge`` within an update strategy that is higher "
-"than a ``minAvailable`` within a pod disruption budget, a scenario may occur "
-"where pods fail to be evicted from a deployment."
-msgstr ""
-"**Hinweis:** Die in einem PodDisruptionBudget definierten Werte können zu "
-"Konflikten mit anderen Werten führen, die bereitgestellt wurden, wenn ein "
-"Benutzer sich für die Verwendung von Rolling Updates für Bereitstellungen "
-"entscheidet. In dem Fall, in dem ein Operator ein ``maxUnavailable`` und ein "
-"``maxSurge`` innerhalb einer Aktualisierungsstrategie definiert, die höher "
-"als ein ``minAvailable`` innerhalb eines Pod-Unterbrechungsbudgets ist, kann "
-"ein Szenario auftreten, bei dem die Pods nicht entfernt werden eine "
-"Bereitstellung"
-
-msgid ""
-":code:`neutron/templates/bin/_neutron-linuxbridge-agent-init.sh.tpl` is "
-"configuring the tunnel IP, external bridge and all bridge mappings defined "
-"in config. It is done in init container, and the IP for tunneling is shared "
-"using file :code:`/tmp/pod-shared/ml2-local-ip.ini` with main linuxbridge "
-"container."
-msgstr ""
-":code:`neutron/templates/bin/_neutron-linuxbridge-agent-init.sh.tpl` "
-"konfiguriert die Tunnel-IP, die externe Bridge und alle in config "
-"definierten bridge-Mappings. Es wird im init-Container gemacht, und die IP "
-"für das Tunneln wird unter Verwendung der Datei :code:`/tmp/pod-shared/ml2-"
-"local-ip.ini` mit dem Haupt-linuxbridge-Container geteilt."
-
-msgid ""
-"A detail worth mentioning is that ovs is configured to use sockets, rather "
-"than the default loopback mechanism."
-msgstr ""
-"Ein erwähnenswertes Detail ist, dass ovs so konfiguriert ist, dass es "
-"Sockets anstelle des Standard-Loopback-Mechanismus verwendet."
-
-msgid ""
-"A long-term goal, besides being image agnostic, is to also be able to "
-"support any of the container runtimes that Kubernetes supports, even those "
-"that might not use Docker's own packaging format. This will allow the "
-"project to continue to offer maximum flexibility with regard to operator "
-"choice."
-msgstr ""
-"Ein langfristiges Ziel ist es, nicht nur abbildunabhängig zu sein, sondern "
-"auch alle Containerlaufzeiten unterstützen zu können, die von Kubernetes "
-"unterstützt werden, auch solche, die nicht das eigene Packungsformat von "
-"Docker verwenden. Auf diese Weise kann das Projekt weiterhin maximale "
-"Flexibilität hinsichtlich der Betreiberauswahl bieten."
-
-msgid ""
-"All ``Deployment`` chart components are outfitted by default with rolling "
-"update strategies:"
-msgstr ""
-"Alle ``Deployment``-Chart-Komponenten sind standardmäßig mit rollierenden "
-"Update-Strategien ausgestattet:"
-
-msgid "All dependencies described in neutron-dhcp-agent are valid here."
-msgstr "Alle in neutron-dhcp-agent beschriebenen Abhängigkeiten gelten hier."
-
-msgid ""
-"All of the above configs are endpoints or path to the specific class "
-"implementing the interface. You can see the endpoints to class mapping in "
-"`setup.cfg <https://github.com/openstack/neutron/"
-"blob/412c49b3930ce8aecb0a07aec50a9607058e5bc7/setup.cfg#L69>`_."
-msgstr ""
-"Alle oben genannten Konfigurationen sind Endpunkte oder Pfade zu der "
-"spezifischen Klasse, die die Schnittstelle implementiert. Sie können die "
-"Endpunkte für die Klassenzuordnung in `setup.cfg sehen <https://github.com/"
-"openstack/neutron/blob/412c49b3930ce8aecb0a07aec50a9607058e5bc7/setup."
-"cfg#L69>`_."
-
-msgid ""
-"An illustrative example of an ``images:`` section taken from the heat chart:"
-msgstr ""
-"Ein anschauliches Beispiel für einen ``images:``-Abschnitt aus dem Heat-"
-"Chart:"
-
-msgid ""
-"Another place where the DHCP agent is dependent on L2 agent is the "
-"dependency for the L2 agent daemonset:"
-msgstr ""
-"Ein anderer Ort, an dem der DHCP-Agent vom L2-Agenten abhängig ist, ist die "
-"Abhängigkeit für den L2-Agent-Daemonset:"
-
-msgid ""
-"As part of Neutron chart, this daemonset is running Neutron OVS agent. It is "
-"dependent on having :code:`openvswitch-db` and :code:`openvswitch-vswitchd` "
-"deployed and ready. Since its the default choice of the networking backend, "
-"all configuration is in place in `neutron/values.yaml`. :code:`neutron-ovs-"
-"agent` should not be deployed when another SDN is used in `network.backend`."
-msgstr ""
-"Als Teil des Neutron-Charts wird in diesem Daemonset der Neutronen-OVS-Agent "
-"ausgeführt. Es ist abhängig von :code:`openvswitch-db` und :code:"
-"`openvswitch-vswitchd` bereitgestellt und bereit. Da es die Standardauswahl "
-"des Netzwerk-Backends ist, ist die gesamte Konfiguration in `neutron/values."
-"yaml` vorhanden. :code:`neutron-ovs-agent` sollte nicht eingesetzt werden, "
-"wenn ein anderes SDN in` network.backend` verwendet wird."
-
-msgid ""
-"By default, each endpoint is located in the same namespace as the current "
-"service's helm chart. To connect to a service which is running in a "
-"different Kubernetes namespace, a ``namespace`` can be provided for each "
-"individual endpoint."
-msgstr ""
-"Standardmäßig befindet sich jeder Endpunkt im selben Namespace wie das "
-"Steuerdiagramm des aktuellen Dienstes. Um eine Verbindung zu einem Dienst "
-"herzustellen, der in einem anderen Kubernetes-Namespace ausgeführt wird, "
-"kann für jeden einzelnen Endpunkt ein ``Namespace`` bereitgestellt werden."
-
-msgid ""
-"Charts should not use hard coded values such as ``http://keystone-api:5000`` "
-"because these are not compatible with operator overrides and do not support "
-"spreading components out over various namespaces."
-msgstr ""
-"Charts sollten keine fest codierten Werte wie ``http://keystone-api:5000`` "
-"verwenden, da diese nicht mit Operator-Überschreibungen kompatibel sind und "
-"keine Verteilung von Komponenten über verschiedene Namespaces unterstützen."
-
-msgid ""
-"Configure neutron-server with SDN specific core_plugin/mechanism_drivers."
-msgstr ""
-"Konfigurieren Sie den Neutronenserver mit SDN-spezifischen core_plugin/"
-"mechanism_drivers."
-
-msgid "Configuring network plugin"
-msgstr "Netzwerk-Plugin konfigurieren"
-
-msgid "Contents:"
-msgstr "Inhalt:"
-
-msgid "Create separate chart with new SDN deployment method."
-msgstr ""
-"Erstellen Sie ein separates Chart mit der neuen SDN-Bereitstellungsmethode."
-
-msgid ""
-"Currently OpenStack-Helm supports OpenVSwitch and LinuxBridge as a network "
-"virtualization engines. In order to support many possible backends (SDNs), "
-"modular architecture of Neutron chart was developed. OpenStack-Helm can "
-"support every SDN solution that has Neutron plugin, either core_plugin or "
-"mechanism_driver."
-msgstr ""
-"Derzeit unterstützt OpenStack-Helm OpenVSwitch und LinuxBridge als Netzwerk-"
-"Virtualisierungs-Engines. Um viele mögliche Backends (SDNs) zu unterstützen, "
-"wurde die modulare Architektur des Neutronendiagramms entwickelt. OpenStack-"
-"Helm kann jede SDN-Lösung unterstützen, die über das Neutron-Plugin "
-"core_plugin oder mechanism_driver verfügt."
-
-msgid "DHCP - auto-assign IP address and DNS info"
-msgstr "DHCP - Automatische Zuweisung von IP-Adresse und DNS-Informationen"
-
-msgid ""
-"DHCP agent is running dnsmasq process which is serving the IP assignment and "
-"DNS info. DHCP agent is dependent on the L2 agent wiring the interface. So "
-"one should be aware that when changing the L2 agent, it also needs to be "
-"changed in the DHCP agent. The configuration of the DHCP agent includes "
-"option `interface_driver`, which will instruct how the tap interface created "
-"for serving the request should be wired."
-msgstr ""
-"Der DHCP-Agent führt den dnsmasq-Prozess aus, der die IP-Zuweisung und DNS-"
-"Informationen bereitstellt. Der DHCP-Agent ist abhängig vom L2-Agenten, der "
-"die Schnittstelle verkabelt. Daher sollte man sich bewusst sein, dass beim "
-"Ändern des L2-Agenten auch der DHCP-Agent geändert werden muss. Die "
-"Konfiguration des DHCP-Agenten enthält die Option `interface_driver`, die "
-"anweist, wie die Tap-Schnittstelle, die zum Versorgen der Anfrage erstellt "
-"wurde, verdrahtet sein sollte."
-
-msgid "Developer References"
-msgstr "Entwicklerreferenzen"
-
-msgid ""
-"EFK (Elasticsearch, Fluent-bit & Fluentd, Kibana) based Logging Mechanism"
-msgstr ""
-"EFK (Elasticsearch, Fluent-Bit & Fluentd, Kibana) basierte Logging "
-"Mechanismus"
-
-msgid "Endpoints"
-msgstr "Endpunkte"
-
-msgid ""
-"Fluent-bit, Fluentd meet OpenStack-Helm's logging requirements for "
-"gathering, aggregating, and delivering of logged events. Fluent-bit runs as "
-"a daemonset on each node and mounts the `/var/lib/docker/containers` "
-"directory. The Docker container runtime engine directs events posted to "
-"stdout and stderr to this directory on the host. Fluent-bit then forward the "
-"contents of that directory to Fluentd. Fluentd runs as deployment at the "
-"designated nodes and expose service for Fluent-bit to forward logs. Fluentd "
-"should then apply the Logstash format to the logs. Fluentd can also write "
-"kubernetes and OpenStack metadata to the logs. Fluentd will then forward the "
-"results to Elasticsearch and to optionally Kafka. Elasticsearch indexes the "
-"logs in a logstash-* index by default. Kafka stores the logs in a ``logs`` "
-"topic by default. Any external tool can then consume the ``logs`` topic."
-msgstr ""
-"Fluent-Bit, Fluentd erfüllt die Protokollierungsanforderungen von OpenStack-"
-"Helm zum Sammeln, Aggregieren und Liefern protokollierter Ereignisse. Fluent-"
-"Bit wird auf jedem Knoten als Daemonset ausgeführt und lädt das Verzeichnis /"
-"var/lib/docker/containers. Die Docker-Container-Laufzeit-Engine leitet "
-"Ereignisse, die an stdout und stderr gesendet wurden, in dieses Verzeichnis "
-"auf dem Host. Fluent-Bit leitet dann den Inhalt dieses Verzeichnisses an "
-"Fluentd weiter. Fluentd wird als Bereitstellung an den angegebenen Knoten "
-"ausgeführt und stellt den Dienst für Fluent-Bit für die Weiterleitung von "
-"Protokollen bereit. Fluentd sollte dann das Logstash-Format auf die "
-"Protokolle anwenden. Fluentd kann auch Kubernetes und OpenStack-Metadaten in "
-"die Protokolle schreiben. Fluentd wird die Ergebnisse dann an Elasticsearch "
-"und optional an Kafka weiterleiten. Elasticsearch indexiert standardmäßig "
-"die Logs in einem logstash-Index*. Kafka speichert die Logs standardmäßig in "
-"einem ``logs``-Thema. Jedes externe Tool kann dann das ``logs``-Thema "
-"konsumieren."
-
-msgid ""
-"For instance, in the Neutron chart ``values.yaml`` the following endpoints "
-"are defined:"
-msgstr ""
-"Zum Beispiel sind im Neutron-Chart ``values.yaml`` die folgenden Endpunkte "
-"definiert:"
-
-msgid "Host overrides supercede label overrides"
-msgstr "Der Host überschreibt Supercede-Label-Overrides"
-
-msgid ""
-"If :code:`.Values.manifests.daemonset_ovs_agent` will be set to false, "
-"neutron ovs agent would not be launched. In that matter, other type of L2 or "
-"L3 agent on compute node can be run."
-msgstr ""
-"Wenn :code:`.Values.manifests.daemonset_ovs_agent auf false gesetzt wird, "
-"wird der neutron ovs-Agent nicht gestartet. In diesem Fall kann ein anderer "
-"Typ von L2- oder L3-Agenten auf dem Rechenknoten ausgeführt werden."
-
-msgid "If required, add new networking agent label type."
-msgstr ""
-"Fügen Sie bei Bedarf einen neuen Label-Typ für den Netzwerkagenten hinzu."
-
-msgid ""
-"If the SDN implements its own version of L3 networking, neutron-l3-agent "
-"should not be started."
-msgstr ""
-"Wenn das SDN eine eigene Version des L3-Netzwerkes implementiert, sollte "
-"neutron-l3-agent nicht gestartet werden."
-
-msgid ""
-"If the SDN of your choice is using the ML2 core plugin, then the extra "
-"options in `neutron/ml2/plugins/ml2_conf.ini` should be configured:"
-msgstr ""
-"Wenn das SDN Ihrer Wahl das ML2 Core-Plugin verwendet, sollten die "
-"zusätzlichen Optionen in `neutron/ml2/plugins/ml2_conf.ini` konfiguriert "
-"werden:"
-
-msgid "Images"
-msgstr "Abbilder"
-
-msgid ""
-"In ``values.yaml`` in each chart, the same defaults are supplied in every "
-"chart, which allows the operator to override at upgrade or deployment time."
-msgstr ""
-"In ``values.yaml`` in jedem Chart werden die gleichen Standardwerte in jedem "
-"Chart bereitgestellt, wodurch der Bediener beim Upgrade oder bei der "
-"Bereitstellung überschreiben kann."
-
-msgid ""
-"In order to add support for more SDNs, these steps need to be performed:"
-msgstr ""
-"Um weitere SDNs zu unterstützen, müssen diese Schritte ausgeführt werden:"
-
-msgid ""
-"In order to meet modularity criteria of Neutron chart, section `manifests` "
-"in :code:`neutron/values.yaml` contains boolean values describing which "
-"Neutron's Kubernetes resources should be deployed:"
-msgstr ""
-"Um die Modularitätskriterien des Neutron-Chart zu erfüllen, enthält der "
-"Abschnitt ``manifests`` in :code:`neutron/values.yaml` boolesche Werte, die "
-"beschreiben, welche Kubernetes-Ressourcen von Neutron eingesetzt werden "
-"sollten:"
-
-msgid ""
-"In order to use linuxbridge in your OpenStack-Helm deployment, you need to "
-"label the compute and controller/network nodes with `linuxbridge=enabled` "
-"and use this `neutron/values.yaml` override:"
-msgstr ""
-"Um linuxbridge in Ihrer OpenStack-Helm-Implementierung zu verwenden, müssen "
-"Sie die Knoten compute und controller/network mit linuxbridge = enabled "
-"kennzeichnen und diese `neutron/values.yaml`-Überschreibung verwenden:"
-
-msgid ""
-"Introducing a new SDN solution should consider how the above services are "
-"provided. It maybe required to disable built-in Neutron functionality."
-msgstr ""
-"Die Einführung einer neuen SDN-Lösung sollte überlegen, wie die oben "
-"genannten Dienste bereitgestellt werden. Es ist möglicherweise erforderlich, "
-"die eingebaute Neutronenfunktionalität zu deaktivieren."
-
-msgid ""
-"L3 agent is serving the routing capabilities for Neutron networks. It is "
-"also dependent on the L2 agent wiring the tap interface for the routers."
-msgstr ""
-"Der L3-Agent bedient die Routing-Funktionen für Neutron-Netzwerke. Es hängt "
-"auch davon ab, dass der L2-Agent die Abgriffschnittstelle für die Router "
-"verkabelt."
-
-msgid "L3 routing - creation of routers"
-msgstr "L3 Routing - Erstellung von Routern"
-
-msgid "Linuxbridge"
-msgstr "Linuxbridge"
-
-msgid ""
-"Linuxbridge is the second type of Neutron reference architecture L2 agent. "
-"It is running on nodes labeled `linuxbridge=enabled`. As mentioned before, "
-"all nodes that are requiring the L2 services need to be labeled with "
-"linuxbridge. This includes both the compute and controller/network nodes. It "
-"is not possible to label the same node with both openvswitch and linuxbridge "
-"(or any other network virtualization technology) at the same time."
-msgstr ""
-"Linuxbridge ist der zweite Typ des Neutronen-Referenzarchitektur-L2-Agenten. "
-"Es läuft auf Knoten mit der Bezeichnung `linuxbridge = enabled`. Wie bereits "
-"erwähnt, müssen alle Knoten, die L2-Dienste benötigen, mit linuxbridge "
-"gekennzeichnet werden. Dies umfasst sowohl die Rechner- als auch die "
-"Controller-/Netzwerkknoten. Es ist nicht möglich, denselben Knoten "
-"gleichzeitig mit openvswitch und linuxbridge (oder einer anderen "
-"Netzwerkvirtualisierungstechnologie) zu beschriften."
-
-msgid "Logging Mechanism"
-msgstr "Protokollierungsmechanismus"
-
-msgid "Logging Requirements"
-msgstr "Protokollierungsanforderungen"
-
-msgid "Metadata - Provide proxy for Nova metadata service"
-msgstr "Metadaten - Stellt einen Proxy für den Nova-Metadaten-Service bereit"
-
-msgid ""
-"Metadata-agent is a proxy to nova-metadata service. This one provides "
-"information about public IP, hostname, ssh keys, and any tenant specific "
-"information. The same dependencies apply for metadata as it is for DHCP and "
-"L3 agents. Other SDNs may require to force the config driver in nova, since "
-"the metadata service is not exposed by it."
-msgstr ""
-"Der Metadata-Agent ist ein Proxy für den Nova-Metadata-Service. Dieser "
-"enthält Informationen zu öffentlichen IP-Adressen, Hostnamen, SSH-Schlüsseln "
-"und mandantenspezifischen Informationen. Für Metadaten gelten die gleichen "
-"Abhängigkeiten wie für DHCP- und L3-Agenten. Bei anderen SDNs kann es "
-"erforderlich sein, den Konfigurationstreiber in Nova zu erzwingen, da der "
-"Metadatendienst dadurch nicht verfügbar gemacht wird."
-
-msgid "Networking"
-msgstr "Vernetzung"
-
-msgid "Neutron architecture"
-msgstr "Neutron-Architektur"
-
-msgid "Neutron chart includes the following services:"
-msgstr "Neutronendiagramm beinhaltet folgende Dienste:"
-
-msgid ""
-"Neutron-server service is scheduled on nodes with `openstack-control-"
-"plane=enabled` label."
-msgstr ""
-"Der Neutron-Server-Dienst wird auf Knoten mit der Markierung ``openstack-"
-"control-plane = enabled`` geplant."
-
-msgid "Note that only one set of overrides is applied per node, such that:"
-msgstr ""
-"Beachten Sie, dass nur ein Satz von Überschreibungen pro Knoten angewendet "
-"wird, so dass:"
-
-msgid ""
-"Note that some additional values have been injected into the config file, "
-"this is performed via statements in the configmap template, which also calls "
-"the ``helm-toolkit.utils.to_oslo_conf`` to convert the yaml to the required "
-"layout:"
-msgstr ""
-"Beachten Sie, dass einige zusätzliche Werte in die Konfigurationsdatei "
-"eingefügt wurden. Dies geschieht über Anweisungen in der Vorlage configmap, "
-"die auch ``helm-toolkit.utils.to_oslo_conf`` aufrufen, um das yaml in das "
-"gewünschte Layout zu konvertieren:"
-
-msgid ""
-"Note: Rolling update values can conflict with values defined in each "
-"service's PodDisruptionBudget.  See `here <https://docs.openstack.org/"
-"openstack-helm/latest/devref/pod-disruption-budgets.html>`_ for more "
-"information."
-msgstr ""
-"Hinweis: Rollende Aktualisierungswerte können zu Konflikten mit Werten "
-"führen, die im PodDisruptionBudget jedes Service definiert sind. Siehe `hier "
-"<https://docs.openstack.org/openstack-helm/latest/devref/pod-disruption-"
-"budgets.html>`_ für weitere Informationen."
-
-msgid "Nova config dependency"
-msgstr "Nova-Konfigurationsabhängigkeit"
-
-msgid "OSLO-Config Values"
-msgstr "OSLO-Config Werte"
-
-msgid ""
-"OpenStack-Helm defines a centralized logging mechanism to provide insight "
-"into the state of the OpenStack services and infrastructure components as "
-"well as underlying Kubernetes platform. Among the requirements for a logging "
-"platform, where log data can come from and where log data need to be "
-"delivered are very variable. To support various logging scenarios, OpenStack-"
-"Helm should provide a flexible mechanism to meet with certain operation "
-"needs."
-msgstr ""
-"OpenStack-Helm definiert einen zentralen Protokollierungsmechanismus, der "
-"Einblick in den Status der OpenStack-Services und der "
-"Infrastrukturkomponenten sowie der zugrunde liegenden Kubernetes-Plattform "
-"gibt. Zu den Anforderungen für eine Protokollierungsplattform, von der "
-"Protokolldaten kommen und wo Protokolldaten geliefert werden müssen, gehören "
-"sehr unterschiedliche. Um verschiedene Protokollierungsszenarien zu "
-"unterstützen, sollte OpenStack-Helm einen flexiblen Mechanismus "
-"bereitstellen, um bestimmte Betriebsanforderungen zu erfüllen."
-
-msgid ""
-"OpenStack-Helm generates oslo-config compatible formatted configuration "
-"files for services dynamically from values specified in a yaml tree. This "
-"allows operators to control any and all aspects of an OpenStack services "
-"configuration. An example snippet for an imaginary Keystone configuration is "
-"described here:"
-msgstr ""
-"OpenStack-Helm generiert oslo-config-kompatible formatierte "
-"Konfigurationsdateien für Dienste dynamisch aus Werten, die in einer Yaml-"
-"Struktur angegeben sind. Dies ermöglicht Betreibern, alle Aspekte einer "
-"OpenStack-Dienstkonfiguration zu steuern. Ein Beispiel-Snippet für eine "
-"imaginäre Keystone-Konfiguration wird hier beschrieben:"
-
-msgid ""
-"OpenStack-Helm provides fast and lightweight log forwarder and full featured "
-"log aggregator complementing each other providing a flexible and reliable "
-"solution. Especially, Fluent-bit is used as a log forwarder and Fluentd is "
-"used as a main log aggregator and processor."
-msgstr ""
-"OpenStack-Helm bietet einen schnellen und leichten Log Forwarder und einen "
-"voll funktionsfähigen Log Aggregator, die sich gegenseitig ergänzen und eine "
-"flexible und zuverlässige Lösung bieten. Insbesondere wird Fluent-Bit als "
-"Protokollweiterleitung und Fluentd als Hauptprotokollaggregator und -"
-"prozessor verwendet."
-
-msgid "OpenVSwitch"
-msgstr "OpenVSwitch"
-
-msgid "Other SDNs"
-msgstr "Andere SDNs"
-
-msgid "Other networking services provided by Neutron are:"
-msgstr "Andere Netzwerkdienste von Neutron sind:"
-
-msgid "Pod Disruption Budgets"
-msgstr "Pod Disruption Budgets"
-
-msgid ""
-"SDNs implementing ML2 driver can add extra/plugin-specific configuration "
-"options in `neutron/ml2/plugins/ml2_conf.ini`. Or define its own "
-"`ml2_conf_<name>.ini` file where configs specific to the SDN would be placed."
-msgstr ""
-"SDNs, die ML2-Treiber implementieren, können zusätzliche/pluginspezifische "
-"Konfigurationsoptionen in `neutron/ml2/plugins/ml2_conf.ini` hinzufügen. "
-"Oder definieren Sie eine eigene `ml2_conf_ <name> .ini` Datei, in der "
-"Configs, die für das SDN spezifisch sind, platziert werden."
-
-msgid ""
-"Script in :code:`neutron/templates/bin/_neutron-openvswitch-agent-init.sh."
-"tpl` is responsible for determining the tunnel interface and its IP for "
-"later usage by :code:`neutron-ovs-agent`. The IP is set in init container "
-"and shared between init container and main container with :code:`neutron-ovs-"
-"agent` via file :code:`/tmp/pod-shared/ml2-local-ip.ini`."
-msgstr ""
-"Das Skript in :code:`neutron/templates/bin/_neutron-openvswitch-agent-init."
-"sh.tpl` ist verantwortlich für die Bestimmung der Tunnelschnittstelle und "
-"ihrer IP für die spätere Verwendung durch :code:`neutron-ovs-agent`. Die IP "
-"wird im init-Container gesetzt und zwischen dem init-Container und dem Haupt-"
-"Container mit folgendem Code geteilt :code:`neutron-ovs-agent` via Datei :"
-"code:`/tmp/pod-shared/ml2-local-ip.ini`."
-
-msgid ""
-"Specify if new SDN would like to use existing services from Neutron: L3, "
-"DHCP, metadata."
-msgstr ""
-"Geben Sie an, ob ein neues SDN vorhandene Dienste von Neutron verwenden "
-"möchte: L3, DHCP, Metadaten."
-
-msgid ""
-"The Neutron reference architecture provides mechanism_drivers :code:"
-"`OpenVSwitch` (OVS) and :code:`linuxbridge` (LB) with ML2 :code:"
-"`core_plugin` framework."
-msgstr ""
-"Die Neutron-Referenzarchitektur liefert mechanism_drivers :code:"
-"`OpenVSwitch` (OVS) und :code:`linuxbridge` (LB) mit ML2 :code:`core_plugin` "
-"framework."
-
-msgid ""
-"The OpenStack-Helm project also implements annotations across all chart "
-"configmaps so that changing resources inside containers, such as "
-"configuration files, triggers a Kubernetes rolling update. This means that "
-"those resources can be updated without deleting and redeploying the service "
-"and can be treated like any other upgrade, such as a container image change."
-msgstr ""
-"Das OpenStack-Helm-Projekt implementiert auch Anmerkungen über alle "
-"Chartkonfigurationen hinweg, sodass das Ändern von Ressourcen in Containern, "
-"z.B. Konfigurationsdateien, ein aktualisierendes Kubernetes-Rollup-Update "
-"auslöst. Dies bedeutet, dass diese Ressourcen aktualisiert werden können, "
-"ohne dass der Service gelöscht und erneut bereitgestellt werden muss. Sie "
-"können wie jedes andere Upgrade behandelt werden, z.B. eine Container-Image-"
-"Änderung."
-
-msgid ""
-"The OpenStack-Helm project assumes all upgrades will be done through Helm. "
-"This includes handling several different resource types. First, changes to "
-"the Helm chart templates themselves are handled. Second, all of the "
-"resources layered on top of the container image, such as ``ConfigMaps`` "
-"which includes both scripts and configuration files, are updated during an "
-"upgrade. Finally, any image references will result in rolling updates of "
-"containers, replacing them with the updating image."
-msgstr ""
-"Das OpenStack-Helm-Projekt geht davon aus, dass alle Upgrades über Helm "
-"erfolgen. Dies umfasst die Behandlung mehrerer verschiedener "
-"Ressourcentypen. Zuerst werden Änderungen an den Helmchartvorlagen selbst "
-"vorgenommen. Zweitens werden alle Ressourcen, die über dem Container-Image "
-"liegen, wie z.B. ``ConfigMaps``, die sowohl Skripts als auch "
-"Konfigurationsdateien enthalten, während eines Upgrades aktualisiert. "
-"Abschließend führen alle Abbildreferenzen dazu, dass Aktualisierungen von "
-"Containern aktualisiert und durch das Update-Image ersetzt werden."
-
-msgid ""
-"The OpenStack-Helm project today uses a mix of Docker images from "
-"Stackanetes and Kolla, but will likely standardize on a default set of "
-"images for all charts without any reliance on image-specific utilities."
-msgstr ""
-"Das OpenStack-Helm-Projekt verwendet heute eine Mischung aus Docker-Images "
-"von Stackanetes und Kolla, standardisiert aber wahrscheinlich einen "
-"Standardsatz von Abbildern für alle Charts, ohne auf abbildspezifische "
-"Utilities angewiesen zu sein."
-
-msgid ""
-"The ``hash`` function defined in the ``helm-toolkit`` chart ensures that any "
-"change to any file referenced by configmap-bin.yaml or configmap-etc.yaml "
-"results in a new hash, which will then trigger a rolling update."
-msgstr ""
-"Die im ``helm-toolkit``-Chart definierte ``hash``-Funktion stellt sicher, "
-"dass jede Änderung an einer beliebigen Datei, auf die configmap-bin.yaml "
-"oder configmap-etc.yaml verweist, zu einem neuen Hash führt, der dann ein "
-"Rolling auslöst aktualisieren."
-
-msgid "The above configuration options are handled by `neutron/values.yaml`:"
-msgstr ""
-"Die obigen Konfigurationsoptionen werden von `neutron/values.yaml` "
-"gehandhabt:"
-
-msgid ""
-"The farther down the list the label appears, the greater precedence it has. "
-"e.g., \"another-label\" overrides will apply to a node containing both "
-"labels."
-msgstr ""
-"Je weiter unten in der Liste das Label erscheint, desto größer ist die "
-"Priorität. z.B. ``another-label`` Überschreibungen gelten für einen Knoten, "
-"der beide Labels enthält."
-
-msgid ""
-"The following standards are in use today, in addition to any components "
-"defined by the service itself:"
-msgstr ""
-"Die folgenden Standards werden heute zusätzlich zu den Komponenten "
-"verwendet, die vom Dienst selbst definiert werden:"
-
-msgid ""
-"The macros that help translate these into the actual URLs necessary are "
-"defined in the ``helm-toolkit`` chart. For instance, the cinder chart "
-"defines a ``glance_api_servers`` definition in the ``cinder.conf`` template:"
-msgstr ""
-"Die Makros, die dabei helfen, diese in die tatsächlich benötigten URLs zu "
-"übersetzen, sind im ``helm-toolkit`` Chart definiert. Zum Beispiel definiert "
-"das Cinder-Chart eine ``glance_api_servers`` Definition in der `` cinder."
-"conf`` Vorlage:"
-
-msgid ""
-"The ovs set of daemonsets are running on the node labeled "
-"`openvswitch=enabled`. This includes the compute and controller/network "
-"nodes. For more flexibility, OpenVSwitch as a tool was split out of Neutron "
-"chart, and put in separate chart dedicated OpenVSwitch. Neutron OVS agent "
-"remains in Neutron chart. Splitting out the OpenVSwitch creates "
-"possibilities to use it with different SDNs, adjusting the configuration "
-"accordingly."
-msgstr ""
-"Die ovs Daemonsets laufen auf dem Knoten `openvswitch = enabled`. Dies "
-"umfasst die Rechner- und Controller-/Netzwerkknoten. Für mehr Flexibilität "
-"wurde OpenVSwitch als ein Tool aus dem Neutron-Chart herausgenommen und in "
-"einen separaten Chart-dedizierten OpenVSwitch gesetzt. Neutron OVS Agent "
-"bleibt inm Neutron-Chart. Wenn Sie den OpenVSwitch aufteilen, können Sie ihn "
-"mit verschiedenen SDNs verwenden und die Konfiguration entsprechend anpassen."
-
-msgid ""
-"The project's core philosophy regarding images is that the toolsets required "
-"to enable the OpenStack services should be applied by Kubernetes itself. "
-"This requires OpenStack-Helm to develop common and simple scripts with "
-"minimal dependencies that can be overlaid on any image that meets the "
-"OpenStack core library requirements. The advantage of this is that the "
-"project can be image agnostic, allowing operators to use Stackanetes, Kolla, "
-"LOCI, or any image flavor and format they choose and they will all function "
-"the same."
-msgstr ""
-"Die Kernphilosophie des Projekts in Bezug auf Abbilder besteht darin, dass "
-"die für die Aktivierung der OpenStack-Services erforderlichen Toolsets von "
-"Kubernetes selbst angewendet werden sollten. Dies erfordert, dass OpenStack-"
-"Helm allgemeine und einfache Skripte mit minimalen Abhängigkeiten "
-"entwickelt, die jedem Abbild überlagert werden können, das die Anforderungen "
-"der OpenStack-Kernbibliothek erfüllt. Der Vorteil davon ist, dass das "
-"Projekt abbbildunabhängig sein kann und es den Betreibern ermöglicht, "
-"Stackanetes, Kolla, LOCI oder jedes andere Bildformat und -format zu "
-"verwenden, das sie wählen, und sie werden alle gleich funktionieren."
-
-msgid ""
-"The project's goal is to provide a consistent mechanism for endpoints. "
-"OpenStack is a highly interconnected application, with various components "
-"requiring connectivity details to numerous services, including other "
-"OpenStack components and infrastructure elements such as databases, queues, "
-"and memcached infrastructure. The project's goal is to ensure that it can "
-"provide a consistent mechanism for defining these \"endpoints\" across all "
-"charts and provide the macros necessary to convert those definitions into "
-"usable endpoints. The charts should consistently default to building "
-"endpoints that assume the operator is leveraging all charts to build their "
-"OpenStack cloud. Endpoints should be configurable if an operator would like "
-"a chart to work with their existing infrastructure or run elements in "
-"different namespaces."
-msgstr ""
-"Ziel des Projekts ist es, einen konsistenten Mechanismus für Endpunkte "
-"bereitzustellen. OpenStack ist eine stark miteinander verbundene Anwendung, "
-"bei der verschiedene Komponenten Konnektivitätsdetails für zahlreiche "
-"Dienste benötigen, einschließlich anderer OpenStack-Komponenten und "
-"Infrastrukturelemente wie Datenbanken, Warteschlangen und Memcached-"
-"Infrastruktur. Ziel des Projekts ist es, sicherzustellen, dass es einen "
-"konsistenten Mechanismus für die Definition dieser \"Endpunkte\" in allen "
-"Charts bereitstellt und die erforderlichen Makros bereitstellt, um diese "
-"Definitionen in nutzbare Endpunkte umzuwandeln. Die Charts sollten "
-"konsistent standardmäßig Build-Endpunkte erstellen, die davon ausgehen, dass "
-"der Benutzer alle Charts nutzt, um seine OpenStack-Cloud zu erstellen. "
-"Endpunkte sollten konfigurierbar sein, wenn ein Operator ein Chart mit der "
-"vorhandenen Infrastruktur arbeiten oder Elemente in verschiedenen Namespaces "
-"ausführen möchte."
-
-msgid ""
-"The resulting logs can then be queried directly through Elasticsearch, or "
-"they can be viewed via Kibana. Kibana offers a dashboard that can create "
-"custom views on logged events, and Kibana integrates well with Elasticsearch "
-"by default."
-msgstr ""
-"Die resultierenden Protokolle können dann direkt über Elasticsearch "
-"abgefragt werden oder über Kibana eingesehen werden. Kibana bietet ein "
-"Dashboard, das benutzerdefinierte Ansichten für protokollierte Ereignisse "
-"erstellen kann, und Kibana integriert sich standardmäßig gut in "
-"Elasticsearch."
-
-msgid ""
-"There is also a need for DHCP agent to pass ovs agent config file (in :code:"
-"`neutron/templates/bin/_neutron-dhcp-agent.sh.tpl`):"
-msgstr ""
-"Es ist auch notwendig, dass der DHCP-Agent die Konfigurationsdatei des "
-"Agenten übergibt (in :code:`neutron/templates/bin/_neutron-dhcp-agent.sh."
-"tpl`):"
-
-msgid ""
-"These values define all the endpoints that the Neutron chart may need in "
-"order to build full URL compatible endpoints to various services. Long-term, "
-"these will also include database, memcached, and rabbitmq elements in one "
-"place. Essentially, all external connectivity can be defined centrally."
-msgstr ""
-"Diese Werte definieren alle Endpunkte, die das Neutron-Chart möglicherweise "
-"benötigt, um vollständige URL-kompatible Endpunkte für verschiedene Dienste "
-"zu erstellen. Langfristig werden diese auch Datenbank-, Memcached- und "
-"Rabbitmq-Elemente an einem Ort umfassen. Im Wesentlichen kann die gesamte "
-"externe Konnektivität zentral definiert werden."
-
-msgid ""
-"This daemonset includes the linuxbridge Neutron agent with bridge-utils and "
-"ebtables utilities installed. This is all that is needed, since linuxbridge "
-"uses native kernel libraries."
-msgstr ""
-"Dieses Daemonset enthält den Neutron-Agent linuxbridge mit den installierten "
-"Dienstprogrammen bridge-utils und ebtables. Dies ist alles was benötigt "
-"wird, da linuxbridge native Kernel-Bibliotheken verwendet."
-
-msgid "This is accomplished with the following annotation:"
-msgstr "Dies wird mit der folgenden Anmerkung erreicht:"
-
-msgid ""
-"This option will allow to configure the Neutron services in proper way, by "
-"checking what is the actual backed set in :code:`neutron/values.yaml`."
-msgstr ""
-"Mit dieser Option können Sie die Neutron-Dienste auf die richtige Weise "
-"konfigurieren, indem Sie überprüfen, was das tatsächlich hinterlegte Set "
-"ist :code:`neutron/values.yaml`."
-
-msgid ""
-"This requirement is OVS specific, the `ovsdb_connection` string is defined "
-"in `openvswitch_agent.ini` file, specifying how DHCP agent can connect to "
-"ovs. When using other SDNs, running the DHCP agent may not be required. When "
-"the SDN solution is addressing the IP assignments in another way, neutron's "
-"DHCP agent should be disabled."
-msgstr ""
-"Diese Anforderung ist OVS-spezifisch, die Zeichenfolge ``ovsdb_connection`` "
-"ist in der Datei ``openvswitch_agent.ini`` definiert und gibt an, wie der "
-"DHCP-Agent eine Verbindung zu ovs herstellen kann. Bei Verwendung anderer "
-"SDNs ist die Ausführung des DHCP-Agenten möglicherweise nicht erforderlich. "
-"Wenn die SDN-Lösung die IP-Zuweisungen auf andere Weise anspricht, sollte "
-"der DHCP-Agent von Neutron deaktiviert werden."
-
-msgid ""
-"This runs the OVS tool and database. OpenVSwitch chart is not Neutron "
-"specific, it may be used with other technologies that are leveraging the OVS "
-"technology, such as OVN or ODL."
-msgstr ""
-"Dies führt das OVS-Tool und die Datenbank aus. OpenVSwitch-Chart ist nicht "
-"Neutron-spezifisch, es kann mit anderen Technologien verwendet werden, die "
-"die OVS-Technologie nutzen, wie OVN oder ODL."
-
-msgid ""
-"This will be consumed by the templated ``configmap-etc.yaml`` manifest to "
-"produce the following config file:"
-msgstr ""
-"Dies wird vom Manifest ``configmap-etc.yaml`` konsumiert, um die folgende "
-"Konfigurationsdatei zu erzeugen:"
-
-msgid ""
-"To be able to configure multiple networking plugins inside of OpenStack-"
-"Helm, a new configuration option is added:"
-msgstr ""
-"Um mehrere Netzwerk-Plugins innerhalb von OpenStack-Helm konfigurieren zu "
-"können, wurde eine neue Konfigurationsoption hinzugefügt:"
-
-msgid ""
-"To enable new SDN solution, there should be separate chart created, which "
-"would handle the deployment of service, setting up the database and any "
-"related networking functionality that SDN is providing."
-msgstr ""
-"Um die neue SDN-Lösung zu aktivieren, sollte ein separates Chart erstellt "
-"werden, das die Bereitstellung des Dienstes, die Einrichtung der Datenbank "
-"und alle zugehörigen Netzwerkfunktionen, die SDN bereitstellt, übernimmt."
-
-msgid ""
-"To that end, all charts provide an ``images:`` section that allows operators "
-"to override images. Also, all default image references should be fully "
-"spelled out, even those hosted by Docker or Quay. Further, no default image "
-"reference should use ``:latest`` but rather should be pinned to a specific "
-"version to ensure consistent behavior for deployments over time."
-msgstr ""
-"Zu diesem Zweck enthalten alle Charts einen Abschnitt ``images:``, mit dem "
-"Operatoren Abbilder überschreiben können. Außerdem sollten alle Standard-"
-"Abbildreferenzen vollständig angegeben werden, selbst wenn sie von Docker "
-"oder Quay gehostet werden. Darüber hinaus sollte keine "
-"Standardabbildreferenz ``:latest`` verwenden, sondern sollte an eine "
-"bestimmte Version angeheftet werden, um ein konsistentes Verhalten für "
-"Bereitstellungen im Zeitverlauf sicherzustellen."
-
-msgid ""
-"To use other Neutron reference architecture types of SDN, these options "
-"should be configured in :code:`neutron.conf`:"
-msgstr ""
-"Um andere Neutron-Referenzarchitekturtypen von SDN zu verwenden, sollten "
-"diese Optionen in folgendem Code konfiguriert werden :code:`neutron.conf`:"
-
-msgid ""
-"Today, the ``images:`` section has several common conventions. Most "
-"OpenStack services require a database initialization function, a database "
-"synchronization function, and a series of steps for Keystone registration "
-"and integration. Each component may also have a specific image that composes "
-"an OpenStack service. The images may or may not differ, but regardless, "
-"should all be defined in ``images``."
-msgstr ""
-"Heute hat der Abschnitt ``images:`` einige allgemeine Konventionen. Die "
-"meisten OpenStack-Dienste erfordern eine Datenbankinitialisierungsfunktion, "
-"eine Datenbanksynchronisierungsfunktion und eine Reihe von Schritten für die "
-"Keystone-Registrierung und -Integration. Jede Komponente kann auch ein "
-"bestimmtes Abbild haben, aus dem ein OpenStack-Service besteht. Die Abbilder "
-"können sich unterscheiden oder nicht, aber unabhängig davon sollten alle in "
-"``images`` definiert sein."
-
-msgid "Typical networking API request is an operation of create/update/delete:"
-msgstr ""
-"Eine typische Netzwerk-API-Anfrage ist eine Operation von create / update / "
-"delete:"
-
-msgid "Upgrades and Reconfiguration"
-msgstr "Upgrades und Neukonfigurationen"
-
-msgid ""
-"``host1.fqdn`` with labels ``compute-type: dpdk, sriov`` and ``another-"
-"label: another-value``:"
-msgstr ""
-"``host1.fqdn`` mit den Labels ``compute-type: dpdk, sriov`` und ``another-"
-"label: another-value``:"
-
-msgid ""
-"``host2.fqdn`` with labels ``compute-type: dpdk, sriov`` and ``another-"
-"label: another-value``:"
-msgstr ""
-"``host2.fqdn`` mit den Labels ``compute-type: dpdk, sriov`` und ``another-"
-"label: another-value``:"
-
-msgid ""
-"``host3.fqdn`` with labels ``compute-type: dpdk, sriov`` and ``another-"
-"label: another-value``:"
-msgstr ""
-"``host3.fqdn`` mit den Labels ``compute-type: dpdk, sriov`` und ``another-"
-"label: another-value``:"
-
-msgid "``host4.fqdn`` with labels ``compute-type: dpdk, sriov``:"
-msgstr "``host4.fqdn`` mit Label ``compute-type: dpdk, sriov``:"
-
-msgid "``host5.fqdn`` with no labels:"
-msgstr "``host5.fqdn`` ohne Label:"
-
-msgid ""
-"db\\_drop: The image that will perform database deletion operations for the "
-"OpenStack service."
-msgstr ""
-"db \\ _drop: Das Abbild, das Datenbanklöschvorgänge für den OpenStack-"
-"Service ausführt."
-
-msgid ""
-"db\\_init: The image that will perform database creation operations for the "
-"OpenStack service."
-msgstr ""
-"db \\ _init: Das Abbild, das Datenbankerstellungsvorgänge für den OpenStack-"
-"Service ausführt."
-
-msgid ""
-"db\\_sync: The image that will perform database sync (schema initialization "
-"and migration) for the OpenStack service."
-msgstr ""
-"db \\ _sync: Das Abbild, das die Datenbanksynchronisierung "
-"(Schemainitialisierung und -migration) für den OpenStack-Service durchführt."
-
-msgid ""
-"dep\\_check: The image that will perform dependency checking in an init-"
-"container."
-msgstr ""
-"dep \\ _check: Das Abbild, das die Abhängigkeitsprüfung in einem init-"
-"Container durchführt."
-
-msgid ""
-"image: This is the OpenStack service that the endpoint is being built for. "
-"This will be mapped to ``glance`` which is the image service for OpenStack."
-msgstr ""
-"image: Dies ist der OpenStack-Dienst, für den der Endpunkt erstellt wird. "
-"Dies wird auf ``glance`` abgebildet, was der Abbild-Dienst für OpenStack ist."
-
-msgid ""
-"internal: This is the OpenStack endpoint type we are looking for - valid "
-"values would be ``internal``, ``admin``, and ``public``"
-msgstr ""
-"internal: Dies ist der OpenStack-Endpunkttyp, nach dem wir suchen - gültige "
-"Werte wären ``internal``, `admin`` und` public``"
-
-msgid ""
-"ks\\_endpoints: The image that will perform keystone endpoint registration "
-"for the service."
-msgstr ""
-"ks \\ _endpoints: Das Abbild, das die Keystone-Endpunktregistrierung für den "
-"Service durchführt."
-
-msgid ""
-"ks\\_service: The image that will perform keystone service registration for "
-"the service."
-msgstr ""
-"ks \\ _service: Das Abbild, das die Registrierung des Keystone-Service für "
-"den Service durchführt."
-
-msgid ""
-"ks\\_user: The image that will perform keystone user creation for the "
-"service."
-msgstr ""
-"ks \\ _user: Das Abbild, das die Keystone-Nutzererstellung für den Service "
-"durchführt."
-
-msgid "network"
-msgstr "Netzwerk"
-
-msgid "neutron-dhcp-agent"
-msgstr "Neutron-dhcp-Agent"
-
-msgid ""
-"neutron-dhcp-agent service is scheduled to run on nodes with the label "
-"`openstack-control-plane=enabled`."
-msgstr ""
-"Der Neutron-dhcp-Agent-Dienst wird auf Knoten mit der Bezeichnung openstack-"
-"control-plane = enabled ausgeführt."
-
-msgid "neutron-l3-agent"
-msgstr "Neutron-I3-agent"
-
-msgid ""
-"neutron-l3-agent service is scheduled to run on nodes with the label "
-"`openstack-control-plane=enabled`."
-msgstr ""
-"Der Dienst von neutron-l3-agent soll auf Knoten mit der Bezeichnung "
-"openstack-control-plane = enabled ausgeführt werden."
-
-msgid "neutron-lb-agent"
-msgstr "Neutron-lb-agent"
-
-msgid "neutron-metadata-agent"
-msgstr "Neutron-metadata-agent"
-
-msgid ""
-"neutron-metadata-agent service is scheduled to run on nodes with the label "
-"`openstack-control-plane=enabled`."
-msgstr ""
-"Der Neutron-Metadaten-Agent-Dienst soll auf Knoten mit der Bezeichnung "
-"openstack-control-plane = enabled ausgeführt werden."
-
-msgid "neutron-ovs-agent"
-msgstr "Neutron-ovs-agent"
-
-msgid "neutron-server"
-msgstr "Neutron-Server"
-
-msgid ""
-"neutron-server is serving the networking REST API for operator and other "
-"OpenStack services usage. The internals of Neutron are highly flexible, "
-"providing plugin mechanisms for all networking services exposed. The "
-"consistent API is exposed to the user, but the internal implementation is up "
-"to the chosen SDN."
-msgstr ""
-"Neutron-Server bedient die Netzwerk-REST-API für die Nutzung von Betreibern "
-"und anderen OpenStack-Diensten. Die Interna von Neutron sind sehr flexibel "
-"und bieten Plug-in-Mechanismen für alle verfügbaren Netzwerkdienste. Die "
-"konsistente API wird dem Benutzer zur Verfügung gestellt, die interne "
-"Implementierung unterliegt jedoch dem ausgewählten SDN."
-
-msgid "openvswitch-db and openvswitch-vswitchd"
-msgstr "openvswitch-db und openvswitch-vswitchd"
-
-msgid "port"
-msgstr "port"
-
-msgid ""
-"pull\\_policy: The image pull policy, one of \"Always\", \"IfNotPresent\", "
-"and \"Never\" which will be used by all containers in the chart."
-msgstr ""
-"pull \\ _policy: Die Image-Pull-Richtlinie, eine der Optionen ``Always``, "
-"``IfNotPresent`` und ``Never``, die von allen Containern im Chart verwendet "
-"wird."
-
-msgid "subnet"
-msgstr "Teilnetz"
diff --git a/doc/source/locale/de/LC_MESSAGES/doc-install.po b/doc/source/locale/de/LC_MESSAGES/doc-install.po
deleted file mode 100644
index f9f3bdc1d1..0000000000
--- a/doc/source/locale/de/LC_MESSAGES/doc-install.po
+++ /dev/null
@@ -1,968 +0,0 @@
-# Frank Kloeker <eumel@arcor.de>, 2018. #zanata
-# Robert Simai <robert.simai@suse.com>, 2018. #zanata
-msgid ""
-msgstr ""
-"Project-Id-Version: openstack-helm 0.1.1.dev3685\n"
-"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2022-04-06 21:47+0000\n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-"PO-Revision-Date: 2018-10-25 10:34+0000\n"
-"Last-Translator: Robert Simai <robert.simai@suse.com>\n"
-"Language-Team: German\n"
-"Language: de\n"
-"Plural-Forms: nplurals=2; plural=(n != 1)\n"
-"X-Generator: Zanata 4.3.3\n"
-
-msgid "**Check Chart Status**"
-msgstr "**Chart Status überprüfen**"
-
-msgid ""
-"**First**, edit the ``values.yaml`` for Neutron, Glance, Horizon, Keystone, "
-"and Nova."
-msgstr ""
-"**Zuerst**, editieren Sie die ``values.yaml`` für Neutron, Glance, Horizon, "
-"Keystone und Nova."
-
-msgid "**Review the Ingress configuration.**"
-msgstr "**Überprüfen Sie die Ingress-Konfiguration.**"
-
-msgid ""
-"**Second** option would be as ``--set`` flags when calling ``helm install``"
-msgstr ""
-"**Zweiten** Option wäre als ``set`` Flags beim Aufruf von` `helm install``"
-
-msgid "16GB of RAM"
-msgstr "16 GB RAM"
-
-msgid "4 Cores"
-msgstr "4 Kerne"
-
-msgid "48GB HDD"
-msgstr "48 GB HDD"
-
-msgid "8 Cores"
-msgstr "8 Kerne"
-
-msgid "8GB of RAM"
-msgstr "8 GB RAM"
-
-msgid "Activate the OpenStack namespace to be able to use Ceph"
-msgstr "Aktivieren Sie den OpenStack-Namespace, um Ceph verwenden zu können"
-
-msgid "Activate the openstack namespace to be able to use Ceph"
-msgstr "Aktivieren Sie den Openstack-Namespace, um Ceph verwenden zu können"
-
-msgid ""
-"Add the address of the Kubernetes API, ``172.17.0.1``, and ``.svc.cluster."
-"local`` to your ``no_proxy`` and ``NO_PROXY`` environment variables."
-msgstr ""
-"Fügen Sie die Adresse der Kubernetes-API ``172.17.0.1`` und ``.svc.cluster."
-"local`` zu Ihren Umgebungsvariablen ``no_proxy`` und ``NO_PROXY`` hinzu."
-
-msgid ""
-"Add to the Install steps these flags - also adding a shell environment "
-"variable to save on repeat code."
-msgstr ""
-"Fügen Sie zu den Installationsschritten diese Flags hinzu, und fügen Sie "
-"außerdem eine Shell-Umgebungsvariable hinzu, um den Wiederholungscode zu "
-"speichern."
-
-msgid ""
-"Additional configuration variables can be found `here <https://github.com/"
-"openstack/openstack-helm-infra/blob/master/roles/deploy-kubeadm-aio-common/"
-"defaults/main.yml>`_. In particular, ``kubernetes_cluster_pod_subnet`` can "
-"be used to override the pod subnet set up by Calico (the default container "
-"SDN), if you have a preexisting network that conflicts with the default pod "
-"subnet of 192.168.0.0/16."
-msgstr ""
-"Zusätzliche Konfigurationsvariablen finden Sie `hier <https://github.com/"
-"openstack/openstack-helm-infra/blob/master/roles/deploy-kubeadm-aio-common/"
-"defaults/main.yml>`_. Insbesondere kann ``kubernetes_cluster_pod_subnet`` "
-"verwendet werden, um das von Calico (dem Standard-Container SDN) "
-"eingerichtete Pod-Subnetz zu überschreiben, wenn ein bereits bestehendes "
-"Netzwerk mit dem Standard-Pod-Subnetz von 192.168.0.0/16 in Konflikt steht."
-
-msgid ""
-"Additional information on Kubernetes Ceph-based integration can be found in "
-"the documentation for the `CephFS <https://github.com/kubernetes-incubator/"
-"external-storage/blob/master/ceph/cephfs/README.md>`_ and `RBD <https://"
-"github.com/kubernetes-incubator/external-storage/blob/master/ceph/rbd/README."
-"md>`_ storage provisioners, as well as for the alternative `NFS <https://"
-"github.com/kubernetes-incubator/external-storage/blob/master/nfs/README."
-"md>`_ provisioner."
-msgstr ""
-"Weitere Informationen zur Kubernetes Ceph-basierten Integration finden Sie "
-"in der Dokumentation zum `CephFS <https://github.com/kubernetes-incubator/"
-"external-storage/blob/master/ceph/cephfs/README.md>`_ und` RBD <https://"
-"github.com/kubernetes-incubator/external-storage/blob/master/ceph/rbd/README."
-"md>`_ Speicher-Provisioner, sowie für die Alternative `NFS <https://github."
-"com/kubernetes-incubator/external-storage/blob/master/nfs/README.md>`_ "
-"Bereitsteller."
-
-msgid ""
-"After making the configuration changes, run a ``make`` and then install as "
-"you would from AIO or MultiNode instructions."
-msgstr ""
-"Nachdem Sie die Konfigurationsänderungen vorgenommen haben, führen Sie ein "
-"``make`` aus und installieren Sie dann wie von AIO- oder MultiNode-"
-"Anweisungen."
-
-msgid ""
-"All commands below should be run as a normal user, not as root. Appropriate "
-"versions of Docker, Kubernetes, and Helm will be installed by the playbooks "
-"used below, so there's no need to install them ahead of time."
-msgstr ""
-"Alle folgenden Befehle sollten als normaler Benutzer und nicht als root "
-"ausgeführt werden. Entsprechende Versionen von Docker, Kubernetes und Helm "
-"werden von den unten verwendeten Playbooks installiert, so dass es nicht "
-"notwendig ist, sie vorher zu installieren."
-
-msgid ""
-"Alternatively, this step can be performed by running the script directly:"
-msgstr ""
-"Alternativ kann dieser Schritt ausgeführt werden, indem das Skript direkt "
-"ausgeführt wird:"
-
-msgid ""
-"An Ingress is a collection of rules that allow inbound connections to reach "
-"the cluster services."
-msgstr ""
-"Ein Ingress ist eine Sammlung von Regeln, die es eingehenden Verbindungen "
-"erlauben, die Cluster-Dienste zu erreichen."
-
-msgid ""
-"By default the Calico CNI will use ``192.168.0.0/16`` and Kubernetes "
-"services will use ``10.96.0.0/16`` as the CIDR for services. Check that "
-"these CIDRs are not in use on the development node before proceeding, or "
-"adjust as required."
-msgstr ""
-"Standardmäßig verwendet der Calico CNI `192.168.0.0/16`` und Kubernetes "
-"Dienste` `10.96.0.0/16`` als CIDR für Dienste. Stellen Sie sicher, dass "
-"diese CIDRs nicht auf dem Entwicklungsknoten verwendet werden, bevor Sie "
-"fortfahren, oder passen Sie sie wie erforderlich an."
-
-msgid "Cleaning the Deployment"
-msgstr "Reinigung der Bereitstellung"
-
-msgid "Clone the OpenStack-Helm Repos"
-msgstr "Klonen Sie die OpenStack-Helm Repos"
-
-msgid "Code examples below."
-msgstr "Codebeispiele unten."
-
-msgid "Common Deployment Requirements"
-msgstr "Allgemeine Bereitstellungsanforderungen"
-
-msgid "Configure OpenStack"
-msgstr "Konfigurieren Sie OpenStack"
-
-msgid ""
-"Configuring OpenStack for a particular production use-case is beyond the "
-"scope of this guide. Please refer to the OpenStack `Configuration <https://"
-"docs.openstack.org/latest/configuration/>`_ documentation for your selected "
-"version of OpenStack to determine what additional values overrides should be "
-"provided to the OpenStack-Helm charts to ensure appropriate networking, "
-"security, etc. is in place."
-msgstr ""
-"Die Konfiguration von OpenStack für einen bestimmten Produktions-"
-"Anwendungsfall würde den Rahmen dieses Handbuchs sprengen. Bitte beachten "
-"Sie die OpenStack `Konfiguration <https://docs.openstack.org/latest/"
-"configuration/>`_ Dokumentation für Ihre Version von OpenStack, um zu "
-"ermitteln, welche zusätzlichen Werte den OpenStack-Helm-Charts hinzugefügt "
-"werden sollten, um eine angemessene Vernetzung, Sicherheit usw. "
-"sicherzustellen."
-
-msgid "Contents:"
-msgstr "Inhalt:"
-
-msgid ""
-"Copy the key: ``sudo cp ~/.ssh/id_rsa /etc/openstack-helm/deploy-key.pem``"
-msgstr ""
-"Kopieren Sie den Schlüssel: ``sudo cp ~/.ssh/id_rsa /etc/openstack-helm/"
-"deploy-key.pem``"
-
-msgid "Create an environment file"
-msgstr "Erstellen Sie eine Umgebungsdatei"
-
-msgid "Create an inventory file"
-msgstr "Erstellen Sie eine Inventardatei"
-
-msgid ""
-"Create an ssh-key on the master node, and add the public key to each node "
-"that you intend to join the cluster."
-msgstr ""
-"Erstellen Sie auf dem Master-Knoten einen SSH-Schlüssel, und fügen Sie jedem "
-"Knoten, dem Sie den Cluster beitreten möchten, den öffentlichen Schlüssel "
-"hinzu."
-
-msgid "Deploy Barbican"
-msgstr "Bereitstellen von Barbican"
-
-msgid "Deploy Ceph"
-msgstr "Stellen Sie Ceph bereit"
-
-msgid "Deploy Cinder"
-msgstr "Bereitstellen von Cinder"
-
-msgid "Deploy Compute Kit (Nova and Neutron)"
-msgstr "Bereitstellen eines Compute Kit (Nova und Neutron)"
-
-msgid "Deploy Glance"
-msgstr "Bereitstellen von Glance"
-
-msgid "Deploy Heat"
-msgstr "Bereitstellen von Heat"
-
-msgid "Deploy Horizon"
-msgstr "Bereitstellen von Horizont"
-
-msgid "Deploy Keystone"
-msgstr "Stellen Sie Keystone bereit"
-
-msgid "Deploy Kubernetes & Helm"
-msgstr "Stellen Sie Kubernetes & Helm bereit"
-
-msgid "Deploy Libvirt"
-msgstr "Stellen Sie Libvirt bereit"
-
-msgid "Deploy MariaDB"
-msgstr "Stellen Sie MariaDB bereit"
-
-msgid "Deploy Memcached"
-msgstr "Bereitstellen von Memcached"
-
-msgid "Deploy NFS Provisioner"
-msgstr "Bereitstellen von NFS-Provisioner"
-
-msgid "Deploy OpenStack-Helm"
-msgstr "Stellen Sie OpenStack-Helm bereit"
-
-msgid "Deploy OpenvSwitch"
-msgstr "Stellen Sie OpenvSwitch bereit"
-
-msgid "Deploy RabbitMQ"
-msgstr "Stellen Sie RabbitMQ bereit"
-
-msgid "Deploy Rados Gateway for object store"
-msgstr "Stellen Sie Rados Gateway für den Objektspeicher bereit"
-
-msgid "Deploy the ingress controller"
-msgstr "Stellen Sie den Ingress-Controller bereit"
-
-msgid "Deployment With Ceph"
-msgstr "Einsatz mit Ceph"
-
-msgid "Deployment With NFS"
-msgstr "Bereitstellung mit NFS"
-
-msgid "Development"
-msgstr "Entwicklung"
-
-msgid "Environment tear-down"
-msgstr "Environment-Abbau"
-
-msgid ""
-"Essentially the use of Ingress for OpenStack-Helm is an Nginx proxy service. "
-"Ingress (Nginx) is accessible by your cluster public IP - e.g. the IP "
-"associated with ``kubectl get pods -o wide --all-namespaces | grep ingress-"
-"api`` Ingress/Nginx will be listening for server name requests of \"keystone"
-"\" or \"keystone.openstack\" and will route those requests to the proper "
-"internal K8s Services. These public listeners in Ingress must match the "
-"external DNS that you will set up to access your OpenStack deployment. Note "
-"each rule also has a Service that directs Ingress Controllers allow access "
-"to the endpoints from within the cluster."
-msgstr ""
-"Im Wesentlichen ist die Verwendung von Ingress für OpenStack-Helm ein Nginx-"
-"Proxy-Dienst. Auf Ingress (Nginx) kann über die öffentliche IP-Adresse des "
-"Clusters zugegriffen werden - z.B. die mit ``kubectl get pods -o wide --all-"
-"namespaces |`` verbundene IP grep ingress-api`` Ingress / Nginx wird auf die "
-"Server-Namensanforderungen ``keystone`` oder ``keystone.openstack`` warten "
-"und diese Anfragen an die richtigen internen K8s-Dienste weiterleiten. Diese "
-"öffentlichen Listener in Ingress müssen mit dem externen DNS übereinstimmen, "
-"den Sie für den Zugriff auf Ihre OpenStack-Bereitstellung einrichten. "
-"Beachten Sie, dass jede Regel auch über einen Dienst verfügt, der Ingress-"
-"Controllern den Zugriff auf die Endpunkte innerhalb des Clusters ermöglicht."
-
-msgid "Examples"
-msgstr "Beispiele"
-
-msgid "Exercise the Cloud"
-msgstr "Trainieren der Cloud"
-
-msgid "External DNS and FQDN"
-msgstr "Externer DNS und FQDN"
-
-msgid "External DNS to FQDN/Ingress"
-msgstr "Externer DNS zu FQDN/Ingress"
-
-msgid ""
-"For ``identity`` and ``dashboard`` at ``host_fdqn_override.public`` replace "
-"``null`` with the value as ``keystone.os.foo.org`` and ``horizon.os.foo.org``"
-msgstr ""
-"Für ``identity`` und ``dashboard`` bei ``host_fdqn_override.public`` "
-"ersetzen Sie ``null`` durch den Wert ``keystone.os.foo.org`` und ``horizon."
-"os.foo. org``"
-
-msgid ""
-"For a deployment without cinder and horizon the system requirements are:"
-msgstr ""
-"Für eine Bereitstellung ohne Cinder und Horizon sind die Systemanforderungen:"
-
-msgid ""
-"For a lab or proof-of-concept environment, the OpenStack-Helm gate scripts "
-"can be used to quickly deploy a multinode Kubernetes cluster using KubeADM "
-"and Ansible. Please refer to the deployment guide `here <./kubernetes-gate."
-"html>`__."
-msgstr ""
-"Für eine Labor- oder Proof-of-Concept-Umgebung können die OpenStack-Helm-"
-"Gate-Scripts verwendet werden, um einen Multinode-Kubernetes-Cluster "
-"mithilfe von KubeADM und Ansible schnell bereitzustellen. Weitere "
-"Informationen finden Sie im Bereitstellungshandbuch `hier <./kubernetes-gate."
-"html>`__."
-
-msgid ""
-"For other deployment options, select appropriate ``Deployment with ...`` "
-"option from `Index <../developer/index.html>`__ page."
-msgstr ""
-"Wählen Sie für andere Bereitstellungsoptionen die entsprechende Option `` "
-"Deployment with ... `` von der Seite `Index <../developer/index.html>`__."
-
-msgid "Gate-Based Kubernetes"
-msgstr "Gate-Based Kubernetes"
-
-msgid "Get the Nginx configuration from the Ingress Pod:"
-msgstr "Holen Sie sich die Nginx-Konfiguration vom Ingress Pod:"
-
-msgid "Get the ``helm status`` of your chart."
-msgstr "Erhalten Sie den ``Helm Status`` Ihres Charts."
-
-msgid "Helm Chart Installation"
-msgstr "Helm Chart Installation"
-
-msgid "Host Configuration"
-msgstr "Hostkonfiguration"
-
-msgid ""
-"If doing an `AIO install <https://docs.openstack.org/openstack-helm/latest/"
-"install/developer/index.html>`__, all the ``--set`` flags"
-msgstr ""
-"Wenn Sie eine `AIO-Installation durchführen <https://docs.openstack.org/"
-"openstack-helm/latest/install/developer/index.html>`__, alle ``set`` Flags"
-
-msgid ""
-"Implementing the FQDN overrides **must** be done at install time. If you run "
-"these as helm upgrades, Ingress will notice the updates though none of the "
-"endpoint build-out jobs will run again, unless they are cleaned up manually "
-"or using a tool like Armada."
-msgstr ""
-"Die Implementierung der FQDN-Überschreibungen **muss** zur Installationszeit "
-"erfolgen. Wenn Sie diese als Helm-Upgrades ausführen, wird Ingress die "
-"Updates bemerken, aber keiner der Endpoint-Build-Out-Jobs wird erneut "
-"ausgeführt, es sei denn, sie werden manuell bereinigt oder mit einem Tool "
-"wie Armada."
-
-msgid ""
-"In order to access your OpenStack deployment on Kubernetes we can use the "
-"Ingress Controller or NodePorts to provide a pathway in. A background on "
-"Ingress, OpenStack-Helm fully qualified domain name (FQDN) overrides, "
-"installation, examples, and troubleshooting will be discussed here."
-msgstr ""
-"Um auf Ihre OpenStack-Implementierung auf Kubernetes zuzugreifen, können wir "
-"den Ingress-Controller oder die NodePorts verwenden, um einen Pfad "
-"anzugeben. Ein Hintergrund zu Ingress, OpenStack-Helm vollständig "
-"qualifizierten Domänennamen (FQDN), Installation, Beispielen und "
-"Fehlerbehebung wird hier besprochen ."
-
-msgid ""
-"In order to deploy OpenStack-Helm behind corporate proxy servers, add the "
-"following entries to ``openstack-helm-infra/tools/gate/devel/local-vars."
-"yaml``."
-msgstr ""
-"Um OpenStack-Helm hinter Corporate Proxy Servern zu deployen, fügen Sie "
-"folgende Einträge zu ``openstack-helm-infra/tools/gate/devel/local-vars."
-"yaml`` hinzu."
-
-msgid ""
-"In order to drive towards a production-ready OpenStack solution, our goal is "
-"to provide containerized, yet stable `persistent volumes <https://kubernetes."
-"io/docs/concepts/storage/persistent-volumes/>`_ that Kubernetes can use to "
-"schedule applications that require state, such as MariaDB (Galera). Although "
-"we assume that the project should provide a \"batteries included\" approach "
-"towards persistent storage, we want to allow operators to define their own "
-"solution as well. Examples of this work will be documented in another "
-"section, however evidence of this is found throughout the project. If you "
-"find any issues or gaps, please create a `story <https://storyboard."
-"openstack.org/#!/project/886>`_ to track what can be done to improve our "
-"documentation."
-msgstr ""
-"Um zu einer produktionsfertigen OpenStack-Lösung zu gelangen, ist es unser "
-"Ziel, containerisierte und dennoch stabile `persistente Datenträger "
-"bereitzustellen <https://kubernetes.io/docs/concepts/storage/persistent-"
-"volumes/>`_, die Kubernetes verwenden kann, um Anwendungen zu planen, die "
-"einen Zustand benötigen, wie MariaDB (Galera). Obwohl wir davon ausgehen, "
-"dass das Projekt einen ``Batteries included``-Ansatz für persistenten "
-"Speicher bereitstellen sollte, wollen wir es den Betreibern ermöglichen, "
-"auch ihre eigene Lösung zu definieren. Beispiele für diese Arbeit werden in "
-"einem anderen Abschnitt dokumentiert, der Nachweis dafür findet sich jedoch "
-"im gesamten Projekt. Wenn Sie Probleme oder Lücken finden, erstellen Sie "
-"bitte eine Story <https://storyboard.openstack.org/#!/project/886>`_ um zu "
-"verfolgen, was getan werden kann, um unsere Dokumentation zu verbessern."
-
-msgid "Ingress"
-msgstr "Ingress"
-
-msgid "Install OpenStack-Helm"
-msgstr "Installiere OpenStack-Helm"
-
-msgid "Installation"
-msgstr "Installation"
-
-msgid ""
-"It can be configured to give services externally-reachable URLs, load "
-"balance traffic, terminate SSL, offer name based virtual hosting, and more."
-msgstr ""
-"Es kann so konfiguriert werden, dass es extern erreichbare URLs "
-"bereitstellt, Last-Balance-Verkehr aufteilt, SSL beendet, namensbasiertes "
-"virtuelles Hosting anbietet und vieles mehr."
-
-msgid "Kubernetes Preparation"
-msgstr "Kubernetes Vorbereitung"
-
-msgid "Kubernetes and Common Setup"
-msgstr "Kubernetes und gemeinsames Setup"
-
-msgid "Latest Version Installs"
-msgstr "Neueste Version installiert"
-
-msgid ""
-"Look for *server* configuration with a *server_name* matching your desired "
-"FQDN"
-msgstr ""
-"Suchen Sie nach *server* configuration mit einem *server_name*, der Ihrem "
-"gewünschten FQDN entspricht"
-
-msgid ""
-"Managing and configuring a Kubernetes cluster is beyond the scope of "
-"OpenStack-Helm and this guide."
-msgstr ""
-"Das Verwalten und Konfigurieren eines Kubernetes-Clusters geht über den "
-"Umfang von OpenStack-Helm und diesem Handbuch hinaus."
-
-msgid ""
-"Many of the default container images that are referenced across OpenStack-"
-"Helm charts are not intended for production use; for example, while LOCI and "
-"Kolla can be used to produce production-grade images, their public reference "
-"images are not prod-grade.  In addition, some of the default images use "
-"``latest`` or ``master`` tags, which are moving targets and can lead to "
-"unpredictable behavior.  For production-like deployments, we recommend "
-"building custom images, or at minimum caching a set of known images, and "
-"incorporating them into OpenStack-Helm via values overrides."
-msgstr ""
-"Viele der Standard-Containerabbilder, auf die in den OpenStack-Helmet-Charts "
-"verwiesen wird, sind nicht für den produktiven Einsatz vorgesehen. Während "
-"beispielsweise LOCI und Kolla für die Produktion von Abbildern in "
-"Produktionsqualität verwendet werden können, sind ihre öffentlichen "
-"Referenzabbilder keine Produktqualität. Darüber hinaus verwenden einige der "
-"Standardabbilder ``latest`` oder ``master``-Tags, bei denen es sich um "
-"bewegte Ziele handelt, die zu unvorhersehbarem Verhalten führen können. Für "
-"produktionsähnliche Bereitstellungen empfehlen wir, benutzerdefinierte "
-"Abbiler zu erstellen oder mindestens eine Reihe bekannter Abbildern "
-"zwischenzuspeichern und sie über Werteüberschreibungen in OpenStack-Helm zu "
-"integrieren."
-
-msgid "Multinode"
-msgstr "Multinode"
-
-msgid ""
-"Note if you need to make a DNS change, you will have to do uninstall (``helm "
-"delete <chart>``) and install again."
-msgstr ""
-"Hinweis: Wenn Sie eine DNS-Änderung vornehmen, müssen Sie eine "
-"Deinstallation durchführen (``helm delete <chart> ``) und erneut "
-"installieren."
-
-msgid ""
-"Note that this command will only enable you to auth successfully using the "
-"``python-openstackclient`` CLI. To use legacy clients like the ``python-"
-"novaclient`` from the CLI, reference the auth values in ``/etc/openstack/"
-"clouds.yaml`` and run::"
-msgstr ""
-"Beachten Sie, dass Sie mit diesem Befehl nur autorisieren können, wenn Sie "
-"die CLI ``python-openstackclient`` verwenden. Um Legacy-Clients wie den `` "
-"python-novaclient`` aus der CLI zu verwenden, referenzieren Sie die Auth-"
-"Werte in ``/etc/openstack/clouds.yaml`` und führen Sie folgendes aus:"
-
-msgid ""
-"On the host or master node, install the latest versions of Git, CA Certs & "
-"Make if necessary"
-msgstr ""
-"Installieren Sie auf dem Host- oder Master-Knoten die neuesten Versionen von "
-"Git, CA Certs & Make, falls erforderlich"
-
-msgid "On the master node create an environment file for the cluster:"
-msgstr ""
-"Erstellen Sie auf dem Master-Knoten eine Umgebungsdatei für den Cluster:"
-
-msgid "On the master node create an inventory file for the cluster:"
-msgstr ""
-"Erstellen Sie auf dem Master-Knoten eine Inventardatei für den Cluster:"
-
-msgid "On the master node run the playbooks:"
-msgstr "Führen Sie auf dem Master-Knoten die Playbooks aus:"
-
-msgid "On the worker nodes:"
-msgstr "Auf den Worker-Knoten:"
-
-msgid ""
-"Once OpenStack-Helm has been deployed, the cloud can be exercised either "
-"with the OpenStack client, or the same heat templates that are used in the "
-"validation gates."
-msgstr ""
-"Sobald OpenStack-Helm implementiert wurde, kann die Cloud entweder mit dem "
-"OpenStack-Client oder mit den gleichen Heat-Vorlagen, die in den "
-"Validierungsgates verwendet werden, ausgeführt werden."
-
-msgid ""
-"Once installed, access the API's or Dashboard at `http://horizon.os.foo.org`"
-msgstr ""
-"Nach der Installation greifen Sie auf die APIs oder das Dashboard unter "
-"``http://horizon.os.foo.org`` zu"
-
-msgid ""
-"Once the host has been configured the repos containing the OpenStack-Helm "
-"charts should be cloned onto each node in the cluster:"
-msgstr ""
-"Sobald der Host konfiguriert wurde, sollten die Repos, die die OpenStack-"
-"Helm-Charts enthalten, auf jeden Knoten im Cluster geklont werden:"
-
-msgid ""
-"Once the host has been configured the repos containing the OpenStack-Helm "
-"charts should be cloned:"
-msgstr ""
-"Sobald der Host konfiguriert wurde, sollten die Repos mit den OpenStack-Helm "
-"Charts geklont werden:"
-
-msgid ""
-"OpenStack-Helm uses the hosts networking namespace for many pods including, "
-"Ceph, Neutron and Nova components. For this, to function, as expected pods "
-"need to be able to resolve DNS requests correctly. Ubuntu Desktop and some "
-"other distributions make use of ``mdns4_minimal`` which does not operate as "
-"Kubernetes expects with its default TLD of ``.local``. To operate at "
-"expected either change the ``hosts`` line in the ``/etc/nsswitch.conf``, or "
-"confirm that it matches:"
-msgstr ""
-"OpenStack-Helm verwendet den Namensraum des Hosts für viele Pods, "
-"einschließlich Ceph-, Neutron- und Nova-Komponenten. Damit dies "
-"funktioniert, müssen Pods in der Lage sein, DNS-Anfragen korrekt aufzulösen. "
-"Ubuntu Desktop und einige andere Distributionen benutzen `` mdns4_minimal``, "
-"was nicht funktioniert, wie es Kubernetes mit seiner Standard-TLD `` ."
-"local`` erwartet. Um bei erwartet zu arbeiten, ändern Sie entweder die `` "
-"hosts`` Zeile in der ``/etc/nsswitch.conf``, oder bestätigen Sie, dass sie "
-"übereinstimmt:"
-
-msgid ""
-"OpenStack-Helm utilizes the `Kubernetes Ingress Controller <https://"
-"kubernetes.io/docs/concepts/services-networking/ingress/>`__"
-msgstr ""
-"OpenStack-Helm verwendet den `Kubernetes Ingress Controller <https://"
-"kubernetes.io/docs/concepts/services-networking/ingress/>`__"
-
-msgid "OpenStack-Helm-Infra KubeADM deployment"
-msgstr "OpenStack-Helm-Infra KubeADM-Bereitstellung"
-
-msgid ""
-"Other versions and considerations (such as other CNI SDN providers), config "
-"map data, and value overrides will be included in other documentation as we "
-"explore these options further."
-msgstr ""
-"Andere Versionen und Überlegungen (wie z.B. andere CNI-SDN-Anbieter), "
-"Konfigurationskartendaten und Wertüberschreibungen werden in der weiteren "
-"Dokumentation enthalten sein, wenn wir diese Optionen weiter untersuchen."
-
-msgid "Overview"
-msgstr "Überblick"
-
-msgid "Passwordless Sudo"
-msgstr "Passwortloses Sudo"
-
-msgid ""
-"Please see the supported application versions outlined in the `source "
-"variable file <https://github.com/openstack/openstack-helm-infra/blob/master/"
-"roles/build-images/defaults/main.yml>`_."
-msgstr ""
-"Bitte beachten Sie die unterstützten Anwendungsversionen, die in der "
-"`Quellvariablendatei beschrieben sind <https://github.com/openstack/"
-"openstack-helm-infra/blob/master/roles/build-images/defaults/main.yml>`_."
-
-msgid ""
-"Prepare ahead of time your FQDN and DNS layouts. There are a handful of "
-"OpenStack endpoints you will want to expose for API and Dashboard access."
-msgstr ""
-"Bereiten Sie Ihre FQDN- und DNS-Layouts im Voraus vor. Es gibt eine Handvoll "
-"OpenStack-Endpunkte, die für API- und Dashboard-Zugriff verfügbar sein "
-"sollen."
-
-msgid "Proxy Configuration"
-msgstr "Proxy-Konfiguration"
-
-msgid "Removing Helm Charts"
-msgstr "Helm-Charts entfernen"
-
-msgid "Requirements"
-msgstr "Anforderungen"
-
-msgid "Requirements and Host Configuration"
-msgstr "Anforderungen und Hostkonfiguration"
-
-msgid "Run the playbooks"
-msgstr "Führen Sie die Playbooks aus"
-
-msgid "SSH-Key preparation"
-msgstr "SSH-Schlüssel Vorbereitung"
-
-msgid ""
-"Set correct ownership: ``sudo chown ubuntu /etc/openstack-helm/deploy-key."
-"pem``"
-msgstr ""
-"Setzen Sie die korrekten Dateirechte: ``sudo chown ubuntu /etc/openstack-"
-"helm/deploy-key.pem``"
-
-msgid "Setup Clients on the host and assemble the charts"
-msgstr ""
-"Richten Sie Clients auf dem Host ein und stellen Sie die Charts zusammen"
-
-msgid "Setup the gateway to the public network"
-msgstr "Richten Sie das Gateway zum öffentlichen Netzwerk ein"
-
-msgid "System Requirements"
-msgstr "System Anforderungen"
-
-msgid ""
-"Test this by ssh'ing to a node and then executing a command with 'sudo'. "
-"Neither operation should require a password."
-msgstr ""
-"Testen Sie dies, indem Sie einen ssh-Befehl an einen Knoten senden und dann "
-"einen Befehl mit 'sudo' ausführen. Keine Operation sollte ein Passwort "
-"erfordern."
-
-msgid ""
-"The OpenStack clients and Kubernetes RBAC rules, along with assembly of the "
-"charts can be performed by running the following commands:"
-msgstr ""
-"Die OpenStack-Clients und Kubernetes-RBAC-Regeln können zusammen mit dem "
-"Zusammenstellen der Charts ausgeführt werden, indem Sie die folgenden "
-"Befehle ausführen:"
-
-msgid ""
-"The `./tools/deployment/multinode/kube-node-subnet.sh` script requires "
-"docker to run."
-msgstr ""
-"Das Skript ``./tools/deployment/multinode/kube-node-subnet.sh`` erfordert "
-"das Ausführen von docker."
-
-msgid ""
-"The ``.svc.cluster.local`` address is required to allow the OpenStack client "
-"to communicate without being routed through proxy servers. The IP address "
-"``172.17.0.1`` is the advertised IP address for the Kubernetes API server. "
-"Replace the addresses if your configuration does not match the one defined "
-"above."
-msgstr ""
-"Die ``.svc.cluster.local``-Adresse ist erforderlich, damit der OpenStack-"
-"Client kommunizieren kann, ohne über Proxy-Server weitergeleitet zu werden. "
-"Die IP-Adresse ``172.17.0.1`` ist die angekündigte IP-Adresse für den "
-"Kubernetes-API-Server. Ersetzen Sie die Adressen, wenn Ihre Konfiguration "
-"nicht mit der oben definierten Konfiguration übereinstimmt."
-
-msgid "The default FQDN's for OpenStack-Helm are"
-msgstr "Die Standard-FQDNs für OpenStack-Helm sind"
-
-msgid ""
-"The example above uses the default values used by ``openstack-helm-infra``."
-msgstr ""
-"Das obige Beispiel verwendet die Standardwerte von ``openstack-helm-infra``."
-
-msgid ""
-"The following commands all assume that they are run from the ``/opt/"
-"openstack-helm`` directory."
-msgstr ""
-"Die folgenden Befehle gehen alle davon aus, dass sie vom Verzeichnis ``/opt/"
-"openstack-helm`` ausgeführt werden."
-
-msgid ""
-"The following commands all assume that they are run from the ``openstack-"
-"helm`` directory and the repos have been cloned as above."
-msgstr ""
-"Die folgenden Befehle gehen alle davon aus, dass sie vom Verzeichnis "
-"``openstack-helm`` ausgeführt werden und die Repos wie oben geklont wurden."
-
-msgid ""
-"The installation procedures below, will take an administrator from a new "
-"``kubeadm`` installation to OpenStack-Helm deployment."
-msgstr ""
-"Die folgenden Installationsverfahren führen einen Administrator von einer "
-"neuen ``kubeadm``-Installation zur OpenStack-Helm-Bereitstellung."
-
-msgid "The recommended minimum system requirements for a full deployment are:"
-msgstr ""
-"Die empfohlenen Mindestsystemanforderungen für eine vollständige "
-"Bereitstellung sind:"
-
-msgid ""
-"The upstream Ceph image repository does not currently pin tags to specific "
-"Ceph point releases.  This can lead to unpredictable results in long-lived "
-"deployments.  In production scenarios, we strongly recommend overriding the "
-"Ceph images to use either custom built images or controlled, cached images."
-msgstr ""
-"Das vorgelagerte Ceph-Bild-Repository bindet derzeit keine Tags an bestimmte "
-"Ceph-Point-Releases. Dies kann zu unvorhersehbaren Ergebnissen in "
-"langlebigen Bereitstellungen führen. In Produktionsszenarien empfehlen wir "
-"dringend, die Ceph-Abbilder zu überschreiben, um entweder benutzerdefinierte "
-"Abbilder oder gesteuerte, zwischengespeicherte Abbilder zu verwenden."
-
-msgid ""
-"These commands will restore the environment back to a clean Kubernetes "
-"deployment, that can either be manually removed or over-written by "
-"restarting the deployment process. It is recommended to restart the host "
-"before doing so to ensure any residual state, eg. Network interfaces are "
-"removed."
-msgstr ""
-"Mit diesen Befehlen wird die Umgebung wieder in einer sauberen Kubernetes-"
-"Bereitstellung wiederhergestellt, die entweder manuell entfernt oder "
-"überschrieben werden kann, indem der Bereitstellungsprozess neu gestartet "
-"wird. Es wird empfohlen, den Host vorher neu zu starten, um einen Reststatus "
-"sicherzustellen, z.B. Netzwerkschnittstellen werden entfernt."
-
-msgid ""
-"This guide assumes that users wishing to deploy behind a proxy have already "
-"defined the conventional proxy environment variables ``http_proxy``, "
-"``https_proxy``, and ``no_proxy``."
-msgstr ""
-"In diesem Handbuch wird davon ausgegangen, dass Benutzer, die hinter einem "
-"Proxy-Server installieren möchten, bereits die herkömmlichen Proxy-"
-"Umgebungsvariablen ``http_proxy``, ``https_proxy`` und ``no_proxy`` "
-"definiert haben."
-
-msgid "This guide covers the minimum number of requirements to get started."
-msgstr ""
-"In diesem Handbuch wird die Mindestanzahl von Anforderungen für den Start "
-"beschrieben."
-
-msgid ""
-"This installation, by default will use Google DNS servers, 8.8.8.8 or "
-"8.8.4.4 and updates resolv.conf. These DNS nameserver entries can be changed "
-"by updating file ``/opt/openstack-helm-infra/tools/images/kubeadm-aio/assets/"
-"opt/playbooks/vars.yaml`` under section ``external_dns_nameservers``. This "
-"change must be done on each node in your cluster."
-msgstr ""
-"Diese Installation verwendet standardmäßig die Google DNS-Server 8.8.8.8 "
-"oder 8.8.4.4 und aktualisiert resolv.conf. Diese DNS-Nameserver-Einträge "
-"können geändert werden, indem die Datei ``/opt/openstack-helm-infra/tools/"
-"images/kubeadm-aio/assets/opt/playbooks/vars.yaml`` im Abschnitt "
-"``external_dns_nameservers`` aktualisiert wird. Diese Änderung muss für "
-"jeden Knoten in Ihrem Cluster durchgeführt werden."
-
-msgid ""
-"This will delete all Kubernetes resources generated when the chart was "
-"instantiated. However for OpenStack charts, by default, this will not delete "
-"the database and database users that were created when the chart was "
-"installed. All OpenStack projects can be configured such that upon deletion, "
-"their database will also be removed. To delete the database when the chart "
-"is deleted the database drop job must be enabled before installing the "
-"chart. There are two ways to enable the job, set the job_db_drop value to "
-"true in the chart's ``values.yaml`` file, or override the value using the "
-"helm install command as follows:"
-msgstr ""
-"Dadurch werden alle Kubernetes-Ressourcen gelöscht, die beim Instanziieren "
-"des Charts generiert wurden. Bei OpenStack-Charts werden jedoch "
-"standardmäßig nicht die Datenbank- und Datenbankbenutzer gelöscht, die bei "
-"der Installation des Charts erstellt wurden. Alle OpenStack-Projekte können "
-"so konfiguriert werden, dass ihre Datenbank beim Löschen ebenfalls entfernt "
-"wird. Um die Datenbank zu löschen, wenn das Chart gelöscht wird, muss der "
-"Datenbank-Drop-Job vor der Installation des Charts aktiviert werden. Es gibt "
-"zwei Möglichkeiten, den Job zu aktivieren, den Wert job_db_drop in der Datei "
-"``values.yaml`` des Charts auf true zu setzen oder den Wert mithilfe des "
-"Befehls helm install wie folgt zu überschreiben:"
-
-msgid ""
-"Throughout this guide the assumption is that the user is: ``ubuntu``. "
-"Because this user has to execute root level commands remotely to other "
-"nodes, it is advised to add the following lines to ``/etc/sudoers`` for each "
-"node:"
-msgstr ""
-"In diesem Handbuch wird angenommen, dass der Benutzer ``ubuntu`` ist. Da "
-"dieser Benutzer Befehle auf root-Ebene remote an andere Knoten ausführen "
-"muss, wird empfohlen, die folgenden Zeilen für jeden Knoten zu ``/etc/"
-"sudoers`` hinzuzufügen:"
-
-msgid ""
-"To copy the ssh key to each node, this can be accomplished with the ``ssh-"
-"copy-id`` command, for example: *ssh-copy-id ubuntu@192.168.122.178*"
-msgstr ""
-"Um den ssh-Schlüssel auf jeden Knoten zu kopieren, kann dies mit dem Befehl "
-"``ssh-copy-id`` durchgeführt werden, zum Beispiel: *ssh-copy-id "
-"ubuntu@192.168.122.178*"
-
-msgid "To delete an installed helm chart, use the following command:"
-msgstr ""
-"Verwenden Sie den folgenden Befehl, um ein installiertes Helm-Chart zu "
-"löschen:"
-
-msgid "To generate the key you can use ``ssh-keygen -t rsa``"
-msgstr ""
-"Um den Schlüssel zu generieren, können Sie ``ssh-keygen -t rsa`` benutzen"
-
-msgid ""
-"To run further commands from the CLI manually, execute the following to set "
-"up authentication credentials::"
-msgstr ""
-"Um weitere Befehle von der CLI manuell auszuführen, führen Sie Folgendes "
-"aus, um die Anmeldedaten für die Authentifizierung einzurichten:"
-
-msgid ""
-"To tear-down, the development environment charts should be removed first "
-"from the 'openstack' namespace and then the 'ceph' namespace using the "
-"commands from the `Removing Helm Charts` section. Additionally charts should "
-"be removed from the 'nfs' and 'libvirt' namespaces if deploying with NFS "
-"backing or bare metal development support. You can run the following "
-"commands to loop through and delete the charts, then stop the kubelet "
-"systemd unit and remove all the containers before removing the directories "
-"used on the host by pods."
-msgstr ""
-"Zum Abbau sollten die Entwicklungsumgebungsdiagramme zuerst aus dem "
-"Namespace ``openstack`` und dann aus dem Namespace ``ceph`` mit den Befehlen "
-"aus dem Abschnitt ``Entfernen der Helm-Charts`` entfernt werden. Außerdem "
-"sollten Charts aus den Namespaces 'nfs' und 'libvirt' entfernt werden, wenn "
-"sie mit Unterstützung für NFS-Unterstützung oder Bare-Metal-Entwicklung "
-"bereitgestellt werden. Sie können die folgenden Befehle ausführen, um die "
-"Charts zu durchlaufen und zu löschen. Stoppen Sie dann die Kubelet-"
-"Systemeinheit und entfernen Sie alle Container, bevor Sie die auf dem Host "
-"verwendeten Verzeichnisse durch Pods entfernen."
-
-msgid "Troubleshooting"
-msgstr "Fehlerbehebung"
-
-msgid ""
-"Two similar options exist to set the FQDN overrides for External DNS mapping."
-msgstr ""
-"Es gibt zwei ähnliche Optionen, um die FQDN-Überschreibungen für die externe "
-"DNS-Zuordnung festzulegen."
-
-msgid ""
-"Until the Ubuntu kernel shipped with 16.04 supports CephFS subvolume mounts "
-"by default the `HWE Kernel <../troubleshooting/ubuntu-hwe-kernel.html>`__ is "
-"required to use CephFS."
-msgstr ""
-"Bis der Ubuntu-Kernel, der mit 16.04 ausgeliefert wird, standardmäßig CephFS-"
-"Subvolume-Mounts unterstützt, ist der `HWE-Kernel <../troubleshooting/ubuntu-"
-"hwe-kernel.html>`__ erforderlich, um CephFS zu verwenden."
-
-msgid ""
-"Update your lab/environment DNS server with your appropriate host values "
-"creating A Records for the edge node IP's and various FQDN's. Alternatively "
-"you can test these settings locally by editing your ``/etc/hosts``. Below is "
-"an example with a dummy domain ``os.foo.org`` and dummy Ingress IP "
-"``1.2.3.4``."
-msgstr ""
-"Aktualisieren Sie Ihren Labor-/Umgebungs-DNS-Server mit Ihren entsprechenden "
-"Host-Werten, indem Sie A-Datensätze für die IP-Adressen des Randknotens und "
-"verschiedene FQDNs erstellen. Alternativ können Sie diese Einstellungen "
-"lokal testen, indem Sie Ihre ``/etc/hosts`` bearbeiten. Unten ist ein "
-"Beispiel mit einer Dummy-Domain ``os.foo.org`` und einer Dummy-Ingress-IP "
-"``1.2.3.4``."
-
-msgid "Using Horizon as an example, find the ``endpoints`` config."
-msgstr "Am Beispiel von Horizon finden Sie die Konfiguration ``endpoints``."
-
-msgid ""
-"Using the Helm packages previously pushed to the local Helm repository, run "
-"the following commands to instruct tiller to create an instance of the given "
-"chart. During installation, the helm client will print useful information "
-"about resources created, the state of the Helm releases, and whether any "
-"additional configuration steps are necessary."
-msgstr ""
-"Führen Sie mithilfe der Helm-Pakete, die zuvor in das lokale Helm-Repository "
-"gepusht wurden, die folgenden Befehle aus, um Tiller anzuweisen, eine "
-"Instanz des angegebenen Charts zu erstellen. Während der Installation wird "
-"der Helm-Client nützliche Informationen über die erstellten Ressourcen, den "
-"Status der Helm-Versionen und darüber, ob zusätzliche Konfigurationsschritte "
-"erforderlich sind, drucken."
-
-msgid "Verify the *v1beta1/Ingress* resource has a Host with your FQDN value"
-msgstr ""
-"Überprüfen Sie, ob die Ressource *v1beta1/Ingress* über einen Host mit Ihrem "
-"FQDN-Wert verfügt"
-
-msgid ""
-"We want to change the **public** configurations to match our DNS layouts "
-"above. In each Chart ``values.yaml`` is a ``endpoints`` configuration that "
-"has ``host_fqdn_override``'s for each API that the Chart either produces or "
-"is dependent on. `Read more about how Endpoints are developed <https://docs."
-"openstack.org/openstack-helm/latest/devref/endpoints.html>`__. Note while "
-"Glance Registry is listening on a Ingress http endpoint, you will not need "
-"to expose the registry for external services."
-msgstr ""
-"Wir möchten die **public** Konfigurationen so ändern, dass sie unseren "
-"obigen DNS-Layouts entsprechen. In jedem Chart ist `values.yaml`` eine `` "
-"endpoints`` Konfiguration, die ``host_fqdn_override``s für jede API hat, die "
-"das Chart entweder erzeugt oder von der es abhängig ist. `Lesen Sie mehr "
-"darüber, wie Endpunkte entwickelt werden <https://docs.openstack.org/"
-"openstack-helm/latest/devref/endpoints.html>`__ . Hinweis: Während Glance "
-"Registry einen Ingress-HTTP-Endpunkt überwacht, müssen Sie die Registrierung "
-"für externe Dienste nicht verfügbar machen."
-
-msgid ""
-"You can use any Kubernetes deployment tool to bring up a working Kubernetes "
-"cluster for use with OpenStack-Helm. For production deployments, please "
-"choose (and tune appropriately) a highly-resilient Kubernetes distribution, "
-"e.g.:"
-msgstr ""
-"Sie können ein beliebiges Kubernetes-Bereitstellungstool verwenden, um einen "
-"funktionierenden Kubernetes-Cluster zur Verwendung mit OpenStack-Helm "
-"aufzurufen. Bei Produktionsbereitstellungen wählen Sie bitte eine hoch "
-"belastbare Kubernetes-Distribution aus, z.B.:"
-
-msgid ""
-"You can use any Kubernetes deployment tool to bring up a working Kubernetes "
-"cluster for use with OpenStack-Helm. This guide describes how to simply "
-"stand up a multinode Kubernetes cluster via the OpenStack-Helm gate scripts, "
-"which use KubeADM and Ansible. Although this cluster won't be production-"
-"grade, it will serve as a quick starting point in a lab or proof-of-concept "
-"environment."
-msgstr ""
-"Sie können ein beliebiges Kubernetes-Bereitstellungstool verwenden, um einen "
-"funktionierenden Kubernetes-Cluster zur Verwendung mit OpenStack-Helm "
-"aufzurufen. Dieser Leitfaden beschreibt, wie man einen Multinode-Kubernetes-"
-"Cluster einfach über die OpenStack-Helm-Gate-Skripte, die KubeADM und "
-"Ansible verwenden, aufstellt. Obwohl dieser Cluster keine "
-"Produktionsqualität hat, wird er als ein schneller Ausgangspunkt in einer "
-"Labor- oder Proof-of-Concept-Umgebung dienen."
-
-msgid ""
-"You may now deploy kubernetes, and helm onto your machine, first move into "
-"the ``openstack-helm`` directory and then run the following:"
-msgstr ""
-"Sie können nun kubernetes und helm auf Ihrem Rechner installieren, zuerst in "
-"das Verzeichnis ``openstack-helm`` wechseln und dann folgendes ausführen:"
-
-msgid ""
-"`Airship <https://airshipit.org/>`_, a declarative open cloud infrastructure "
-"platform"
-msgstr ""
-"`Airship <https://airshipit.org/>`_, eine deklarative Open-Cloud-"
-"Infrastrukturplattform"
-
-msgid ""
-"`KubeADM <https://kubernetes.io/docs/setup/independent/high-availability/"
-">`_, the foundation of a number of Kubernetes installation solutions"
-msgstr ""
-"`KubeADM <https://kubernetes.io/docs/setup/independent/high-availability/> "
-"`_, die Grundlage für eine Reihe von Kubernetes Installationslösungen"
-
-msgid ""
-"node_one, node_two and node_three below are all worker nodes, children of "
-"the master node that the commands below are executed on."
-msgstr ""
-"node_one, node_two und node_three unten sind alle Worker-Knoten, Kinder des "
-"Master-Knotens, auf dem die folgenden Befehle ausgeführt werden."
diff --git a/doc/source/locale/de/LC_MESSAGES/doc-testing.po b/doc/source/locale/de/LC_MESSAGES/doc-testing.po
deleted file mode 100644
index 0b59e0ea51..0000000000
--- a/doc/source/locale/de/LC_MESSAGES/doc-testing.po
+++ /dev/null
@@ -1,757 +0,0 @@
-# Andreas Jaeger <jaegerandi@gmail.com>, 2018. #zanata
-# Frank Kloeker <eumel@arcor.de>, 2018. #zanata
-msgid ""
-msgstr ""
-"Project-Id-Version: openstack-helm\n"
-"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2019-03-23 00:21+0000\n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-"PO-Revision-Date: 2018-10-25 07:45+0000\n"
-"Last-Translator: Andreas Jaeger <jaegerandi@gmail.com>\n"
-"Language-Team: German\n"
-"Language: de\n"
-"Plural-Forms: nplurals=2; plural=(n != 1)\n"
-"X-Generator: Zanata 4.3.3\n"
-
-msgid "3 Node (VM based) env."
-msgstr "3 Knoten (VM-basiert) env."
-
-msgid "6 Nodes (VM based) env"
-msgstr "6 Knoten (VM-basiert) Env."
-
-msgid ""
-"A Ceph Monitor running on voyager3 (whose Monitor database is destroyed) "
-"becomes out of quorum, and the mon-pod's status stays in ``Running`` -> "
-"``Error`` -> ``CrashLoopBackOff`` while keeps restarting."
-msgstr ""
-"Ein Ceph-Monitor, der auf voyager3 läuft (dessen Monitor-Datenbank zerstört "
-"ist), wird aus dem Quorum und der Status des Mon-Pods bleibt in ``Running`` -"
-"> ``Error`` -> ``CrashLoopBackOff``, während der Neustart fortgesetzt wird."
-
-msgid "Adding Tests"
-msgstr "Hinzufügen von Tests"
-
-msgid ""
-"Additional information on Helm tests for OpenStack-Helm and how to execute "
-"these tests locally via the scripts used in the gate can be found in the "
-"gates_ directory."
-msgstr ""
-"Weitere Informationen zu Helm-Tests für OpenStack-Helm und wie diese Tests "
-"lokal über die im Gate verwendeten Skripte ausgeführt werden, finden Sie im "
-"Verzeichnis gates_."
-
-msgid ""
-"After 10+ miniutes, Ceph starts rebalancing with one node lost (i.e., 6 osds "
-"down) and the status stablizes with 18 osds."
-msgstr ""
-"Nach 10+ Minuten beginnt Ceph mit einem verlorenen Knoten (d.h. 6 OSDs nach "
-"unten) und der Status stabilisiert sich mit 18 OSDs."
-
-msgid "After reboot (node voyager3), the node status changes to ``NotReady``."
-msgstr ""
-"Nach dem Neustart (Knoten voyager3) ändert sich der Knotenstatus in "
-"``NotReady``."
-
-msgid ""
-"After the host is down (node voyager3), the node status changes to "
-"``NotReady``."
-msgstr ""
-"Nachdem der Host ausgefallen ist (Knoten voyager3), ändert sich der "
-"Knotenstatus in ``NotReady``."
-
-msgid ""
-"All tests should be added to the gates during development, and are required "
-"for any new service charts prior to merging.  All Helm tests should be "
-"included as part of the deployment script.  An example of this can be seen "
-"in this script_."
-msgstr ""
-"Alle Tests sollten während der Entwicklung zu den Gates hinzugefügt werden "
-"und sind für alle neuen Dienst-Charts vor dem Zusammenführen erforderlich. "
-"Alle Helm-Tests sollten als Teil des Bereitstellungsskripts enthalten sein. "
-"Ein Beispiel dafür ist in diesem Skript zu sehen."
-
-msgid ""
-"Also, the pod status of ceph-mon and ceph-osd changes from ``NodeLost`` back "
-"to ``Running``."
-msgstr ""
-"Außerdem ändert sich der Pod-Status von ceph-mon und ceph-osd von "
-"``NodeLost`` zurück zu ``Running``."
-
-msgid "Any Helm tests associated with a chart can be run by executing:"
-msgstr ""
-"Alle Helm-Tests, die mit einem Chart verknüpft sind, können ausgeführt "
-"werden, indem Sie Folgendes ausführen:"
-
-msgid ""
-"Any templates for Helm tests submitted should follow the philosophies "
-"applied in the other templates.  These include: use of overrides where "
-"appropriate, use of endpoint lookups and other common functionality in helm-"
-"toolkit, and mounting any required scripting templates via the configmap-bin "
-"template for the service chart.  If Rally tests are not appropriate or "
-"adequate for a service chart, any additional tests should be documented "
-"appropriately and adhere to the same expectations."
-msgstr ""
-"Alle Vorlagen für Helm-Tests sollten den Philosophien folgen, die in den "
-"anderen Vorlagen angewendet wurden. Dazu gehören: gegebenenfalls die "
-"Verwendung von Überschreibungen, die Verwendung von Endpunkt-Suchvorgängen "
-"und anderen allgemeinen Funktionen in helm-toolkit sowie das Bereitstellen "
-"aller erforderlichen Skriptvorlagen über die Vorlage configmap-bin für das "
-"Dienstdiagramm. Wenn Rally-Tests für ein Dienst-Chart nicht angemessen oder "
-"angemessen sind, sollten alle zusätzlichen Tests angemessen dokumentiert "
-"werden und den gleichen Erwartungen entsprechen."
-
-msgid "Capture Ceph pods statuses."
-msgstr "Capture Ceph Pods Status."
-
-msgid "Capture Openstack pods statuses."
-msgstr "Capture Openstack Pods Status."
-
-msgid "Capture final Ceph pod statuses:"
-msgstr "Erfassen Sie die endgültigen Ceph-Pod-Status:"
-
-msgid "Capture final Openstack pod statuses:"
-msgstr "Erfassen Sie die letzten Openstack-Pod-Status:"
-
-msgid "Case: 1 out of 3 Monitor Processes is Down"
-msgstr "Fall: 1 von 3 Überwachungsprozesse ist inaktiv"
-
-msgid "Case: 2 out of 3 Monitor Processes are Down"
-msgstr "Fall: 2 von 3 Monitor-Prozesse sind inaktiv"
-
-msgid "Case: 3 out of 3 Monitor Processes are Down"
-msgstr "Fall: 3 von 3 Monitor-Prozesse sind inaktiv"
-
-msgid "Case: A OSD pod is deleted"
-msgstr "Fall: Ein OSD-Pod wurde gelöscht"
-
-msgid "Case: A disk fails"
-msgstr "Fall: Eine Festplatte geht kaputt"
-
-msgid "Case: A host machine where ceph-mon is running is down"
-msgstr "Fall: Ein Host-Computer, auf dem ceph-mon läuft, ist inaktiv"
-
-msgid "Case: Monitor database is destroyed"
-msgstr "Fall: Die Monitor-Datenbank ist zerstört"
-
-msgid "Case: OSD processes are killed"
-msgstr "Fall: OSD-Prozesse werden abgebrochen"
-
-msgid "Case: One host machine where ceph-mon is running is rebooted"
-msgstr "Fall: Ein Host-Rechner, auf dem ceph-mon läuft, wird neu gestartet"
-
-msgid "Caveats:"
-msgstr "Vorbehalte:"
-
-msgid "Ceph Cephfs provisioner docker images."
-msgstr "Ceph Cephfs Provisioner Docker Abbilder."
-
-msgid "Ceph Luminous point release images for Ceph components"
-msgstr "Ceph Luminous Point Release Abbilder für Ceph-Komponenten"
-
-msgid "Ceph RBD provisioner docker images."
-msgstr "Ceph-RBD-Provisioner-Docker-Abbilder."
-
-msgid "Ceph Resiliency"
-msgstr "Ceph-Ausfallsicherheit"
-
-msgid "Ceph Upgrade"
-msgstr "Ceph Upgrade"
-
-msgid ""
-"Ceph status shows that ceph-mon running on ``voyager3`` becomes out of "
-"quorum. Also, 6 osds running on ``voyager3`` are down (i.e., 18 out of 24 "
-"osds are up). Some placement groups become degraded and undersized."
-msgstr ""
-"Der Ceph-Status zeigt, dass Ceph-mon, das auf ``voyager3`` läuft, das Quorum "
-"verlässt. Außerdem sind 6 osds, die auf ``voyager3`` laufen, "
-"heruntergefahren (d.h. 18 von 24 ods sind oben). Einige Placement-Gruppen "
-"werden degradiert und zu klein."
-
-msgid ""
-"Ceph status shows that ceph-mon running on ``voyager3`` becomes out of "
-"quorum. Also, six osds running on ``voyager3`` are down; i.e., 18 osds are "
-"up out of 24 osds."
-msgstr ""
-"Der Ceph-Status zeigt, dass Ceph-mon, das auf ``voyager3`` läuft, das Quorum "
-"verlässt. Sechs osds, die auf `` voyager3`` laufen, sind ebenfalls nicht "
-"erreichbar. Das heißt, 18 Osts sind aus 24 Osts heraus."
-
-msgid "Ceph version: 12.2.3"
-msgstr "Ceph-Version: 12.2.3"
-
-msgid "Check Ceph Pods"
-msgstr "Überprüfen Sie Ceph Pods"
-
-msgid "Check version of each Ceph components."
-msgstr "Überprüfen Sie die Version der einzelnen Ceph-Komponenten."
-
-msgid "Check which images Provisionors and Mon-Check PODs are using"
-msgstr ""
-"Überprüfen Sie, welche Abbilder Provisioner und Mon-Check-PODs verwenden"
-
-msgid "Cluster size: 4 host machines"
-msgstr "Clustergröße: 4 Host-Maschinen"
-
-msgid "Conclusion:"
-msgstr "Fazit:"
-
-msgid "Confirm Ceph component's version."
-msgstr "Bestätigen Sie die Version der Ceph-Komponente."
-
-msgid "Continue with OSH multinode guide to install other Openstack charts."
-msgstr ""
-"Fahren Sie mit OSH multinode guide fort, um weitere Openstack-Charts zu "
-"installieren."
-
-msgid "Deploy and Validate Ceph"
-msgstr "Bereitstellen und Validieren von Ceph"
-
-msgid "Disk Failure"
-msgstr "Festplattenfehler"
-
-msgid "Docker Images:"
-msgstr "Docker Abbilder:"
-
-msgid ""
-"Every OpenStack-Helm chart should include any required Helm tests necessary "
-"to provide a sanity check for the OpenStack service.  Information on using "
-"the Helm testing framework can be found in the Helm repository_.  Currently, "
-"the Rally testing framework is used to provide these checks for the core "
-"services.  The Keystone Helm test template can be used as a reference, and "
-"can be found here_."
-msgstr ""
-"Jedes OpenStack-Helm-Chart sollte alle erforderlichen Helm-Tests enthalten, "
-"die für eine Plausibilitätsprüfung des OpenStack-Dienstes erforderlich sind. "
-"Informationen zur Verwendung des Helm-Test-Frameworks finden Sie im Helm-"
-"Repository. Momentan wird das Rallyetest-Framework verwendet, um diese "
-"Überprüfungen für die Kerndienste bereitzustellen. Die Keystone Helm "
-"Testvorlage kann als Referenz verwendet werden und kann hier gefunden werden."
-
-msgid "Find that Ceph is healthy with a lost OSD (i.e., a total of 23 OSDs):"
-msgstr ""
-"Finde heraus, dass Ceph gesund ist mit einem verlorenen OSD (d.h. insgesamt "
-"23 OSDs):"
-
-msgid "Follow all steps from OSH multinode guide with below changes."
-msgstr ""
-"Befolgen Sie alle Schritte des OSH-Multinode-Handbuchs mit den folgenden "
-"Änderungen."
-
-msgid ""
-"Followed OSH multinode guide steps to setup nodes and install K8s cluster"
-msgstr ""
-"Gefolgt OSH Multinode Guide Schritte zum Einrichten von Knoten und "
-"installieren K8s-Cluster"
-
-msgid "Followed OSH multinode guide steps upto Ceph install"
-msgstr "Gefolgt OSH Multinode Guide Schritte bis Ceph Installation"
-
-msgid "Following is a partial part from script to show changes."
-msgstr "Es folgt ein Teil des Skripts, um Änderungen anzuzeigen."
-
-msgid ""
-"From the Kubernetes cluster, remove the failed OSD pod, which is running on "
-"``voyager4``:"
-msgstr ""
-"Entfernen Sie im Kubernetes-Cluster den fehlerhaften OSD-Pod, der auf "
-"``voyager4`` läuft:"
-
-msgid "Hardware Failure"
-msgstr "Hardwarefehler"
-
-msgid "Helm Tests"
-msgstr "Helm-Tests"
-
-msgid "Host Failure"
-msgstr "Hostfehler"
-
-msgid ""
-"In the mean time, we monitor the status of Ceph and noted that it takes "
-"about 30 seconds for the 6 OSDs to recover from ``down`` to ``up``. The "
-"reason is that Kubernetes automatically restarts OSD pods whenever they are "
-"killed."
-msgstr ""
-"In der Zwischenzeit überwachen wir den Status von Ceph und stellen fest, "
-"dass es etwa 30 Sekunden dauert, bis die 6 OSDs von ``down`` nach ``up`` "
-"zurückkehren. Der Grund dafür ist, dass Kubernetes OSD-Pods automatisch neu "
-"startet, wenn sie getötet werden."
-
-msgid ""
-"In the mean time, we monitored the status of Ceph and noted that it takes "
-"about 24 seconds for the killed Monitor process to recover from ``down`` to "
-"``up``. The reason is that Kubernetes automatically restarts pods whenever "
-"they are killed."
-msgstr ""
-"In der Zwischenzeit haben wir den Status von Ceph überwacht und "
-"festgestellt, dass es etwa 24 Sekunden dauert, bis sich der getötete Monitor-"
-"Prozess von ``down`` nach ``up`` zurückholt. Der Grund ist, dass Kubernetes "
-"automatisch Pods neu startet, wenn sie getötet werden."
-
-msgid "Install Ceph charts (12.2.4) by updating Docker images in overrides."
-msgstr ""
-"Installieren Sie Ceph-Diagramme (12.2.4), indem Sie Docker-Abbilder in "
-"Overrides aktualisieren."
-
-msgid "Install Ceph charts (version 12.2.4)"
-msgstr "Installieren Sie Ceph-Diagramme (Version 12.2.4)"
-
-msgid "Install OSH components as per OSH multinode guide."
-msgstr ""
-"Installieren Sie die Arbeitsschutzkomponenten gemäß dem OSH multinode guide."
-
-msgid "Install Openstack charts"
-msgstr "Installieren Sie Openstack-Charts"
-
-msgid ""
-"It takes longer (about 1 minute) for the killed Monitor processes to recover "
-"from ``down`` to ``up``."
-msgstr ""
-"Es dauert länger (etwa 1 Minute), bis die getöteten Monitor-Prozesse von "
-"``down`` nach ``up`` zurückkehren."
-
-msgid "Kubernetes version: 1.10.5"
-msgstr "Kubernetes Version: 1.10.5"
-
-msgid "Kubernetes version: 1.9.3"
-msgstr "Kubernetes Version: 1.9.3"
-
-msgid "Mission"
-msgstr "Mission"
-
-msgid "Monitor Failure"
-msgstr "Fehler beim Überwachen"
-
-msgid ""
-"Note: To find the daemonset associated with a failed OSD, check out the "
-"followings:"
-msgstr ""
-"Hinweis: Um den mit einem fehlgeschlagenen OSD verbundenen Daemonset zu "
-"finden, überprüfen Sie Folgendes:"
-
-msgid "Number of disks: 24 (= 6 disks per host * 4 hosts)"
-msgstr "Anzahl der Festplatten: 24 (= 6 Festplatten pro Host * 4 Hosts)"
-
-msgid "OSD Failure"
-msgstr "OSD-Fehler"
-
-msgid "OSD count is set to 3 based on env setup."
-msgstr "Die OSD-Anzahl wird basierend auf dem env-Setup auf 3 festgelegt."
-
-msgid "OpenStack-Helm commit: 25e50a34c66d5db7604746f4d2e12acbdd6c1459"
-msgstr "OpenStack-Helm commit: 25e50a34c66d5db7604746f4d2e12acbdd6c1459"
-
-msgid "OpenStack-Helm commit: 28734352741bae228a4ea4f40bcacc33764221eb"
-msgstr "OpenStack-Helm commit: 28734352741bae228a4ea4f40bcacc33764221eb"
-
-msgid ""
-"Our focus lies on resiliency for various failure scenarios but not on "
-"performance or stress testing."
-msgstr ""
-"Unser Fokus liegt auf der Ausfallsicherheit für verschiedene "
-"Fehlerszenarien, jedoch nicht auf der Leistung oder dem Stresstest."
-
-msgid "Plan:"
-msgstr "Planen:"
-
-msgid "Recovery:"
-msgstr "Wiederherstellung:"
-
-msgid ""
-"Remove the entire ceph-mon directory on voyager3, and then Ceph will "
-"automatically recreate the database by using the other ceph-mons' database."
-msgstr ""
-"Entfernen Sie das gesamte Verzeichnis ceph-mon auf voyager3, und Ceph "
-"erstellt dann automatisch die Datenbank neu, indem es die Datenbank der "
-"anderen ceph-mons verwendet."
-
-msgid ""
-"Remove the failed OSD (OSD ID = 2 in this example) from the Ceph cluster:"
-msgstr ""
-"Entfernen Sie das fehlerhafte OSD (OSD ID = 2 in diesem Beispiel) vom Ceph-"
-"Cluster:"
-
-msgid "Resiliency Tests for OpenStack-Helm/Ceph"
-msgstr "Resiliency Tests für OpenStack-Helm/Ceph"
-
-msgid "Running Tests"
-msgstr "Tests ausführen"
-
-msgid "Setup:"
-msgstr "Konfiguration:"
-
-msgid ""
-"Showing partial output from kubectl describe command to show which image is "
-"Docker container is using"
-msgstr ""
-"Teilausgabe von kubectl anzeigen Befehl beschreiben, welches Abbild der "
-"Docker-Container verwendet"
-
-msgid "Software Failure"
-msgstr "Softwarefehler"
-
-msgid "Solution:"
-msgstr "Lösung:"
-
-msgid "Start a new OSD pod on ``voyager4``:"
-msgstr "Starten Sie einen neuen OSD-Pod auf ``voyager4``:"
-
-msgid "Step 1: Initial Ceph and OpenStack deployment"
-msgstr "Schritt 1: Initiales Ceph und OpenStack Deployment"
-
-msgid "Steps:"
-msgstr "Schritte:"
-
-msgid "Symptom:"
-msgstr "Symptom:"
-
-msgid "Test Environment"
-msgstr "Testumgebung"
-
-msgid "Test Scenario:"
-msgstr "Testszenario:"
-
-msgid "Test Scenarios:"
-msgstr "Testszenarien:"
-
-msgid "Testing"
-msgstr "Testen"
-
-msgid "Testing Expectations"
-msgstr "Erwartungen testen"
-
-msgid ""
-"The goal of our resiliency tests for `OpenStack-Helm/Ceph <https://github."
-"com/openstack/openstack-helm/tree/master/ceph>`_ is to show symptoms of "
-"software/hardware failure and provide the solutions."
-msgstr ""
-"Das Ziel unserer Elastizitätstests für `OpenStack-Helm/Ceph <https://github."
-"com/openstack/openstack-helm/tree/master/ceph>`_ soll Symptome von Software/"
-"Hardware-Versagen zeigen und die Lösungen bereitstellen."
-
-msgid ""
-"The logs of the failed mon-pod shows the ceph-mon process cannot run as ``/"
-"var/lib/ceph/mon/ceph-voyager3/store.db`` does not exist."
-msgstr ""
-"Die Protokolle des fehlgeschlagenen Mon-Pods zeigen, dass der Ceph-Mon-"
-"Prozess nicht ausgeführt werden kann, da ``/var/lib/ceph/mon/ceph-voyager3/"
-"store.db``` nicht existiert."
-
-msgid ""
-"The node status of ``voyager3`` changes to ``Ready`` after the node is up "
-"again. Also, Ceph pods are restarted automatically. Ceph status shows that "
-"the monitor running on ``voyager3`` is now in quorum."
-msgstr ""
-"Der Knotenstatus von ``voyager3`` ändert sich in ``Ready``, nachdem der "
-"Knoten wieder geöffnet wurde. Außerdem werden Ceph-Pods automatisch neu "
-"gestartet. Der Ceph-Status zeigt an, dass der Monitor, der auf ``voyager3`` "
-"läuft, jetzt im Quorum ist."
-
-msgid ""
-"The node status of ``voyager3`` changes to ``Ready`` after the node is up "
-"again. Also, Ceph pods are restarted automatically. The Ceph status shows "
-"that the monitor running on ``voyager3`` is now in quorum and 6 osds gets "
-"back up (i.e., a total of 24 osds are up)."
-msgstr ""
-"Der Knotenstatus von ``voyager3`` ändert sich in ``Ready``, nachdem der "
-"Knoten wieder geöffnet wurde. Außerdem werden Ceph-Pods automatisch neu "
-"gestartet. Der Ceph-Status zeigt an, dass der Monitor, der auf ``voyager3`` "
-"läuft, jetzt im Quorum ist und 6 ods zurück geht (d.h. insgesamt 24 ods sind "
-"aktiv)."
-
-msgid ""
-"The output of the Helm tests can be seen by looking at the logs of the pod "
-"created by the Helm tests.  These logs can be viewed with:"
-msgstr ""
-"Die Ergebnisse der Helm-Tests können Sie sehen, wenn Sie sich die Logs des "
-"Pods ansehen, die mit den Helm-Tests erstellt wurden. Diese Protokolle "
-"können angezeigt werden mit:"
-
-msgid "The pod status of ceph-mon and ceph-osd shows as ``NodeLost``."
-msgstr ""
-"Der Pod-Status von ceph-mon und ceph-osd wird als ``NodeLost`` angezeigt."
-
-msgid ""
-"The status of the pods (where the three Monitor processes are killed) "
-"changed as follows: ``Running`` -> ``Error`` -> ``CrashLoopBackOff`` -> "
-"``Running`` and this recovery process takes about 1 minute."
-msgstr ""
-"Der Status der Pods (wo die drei Monitor-Prozesse beendet werden) hat sich "
-"wie folgt geändert: ``Running`` -> ``Error`` -> ``CrashLoopBackOff`` -> "
-"``Running`` und dieser Wiederherstellungsprozess dauert ungefähr 1 Minute."
-
-msgid ""
-"The status of the pods (where the two Monitor processes are killed) changed "
-"as follows: ``Running`` -> ``Error`` -> ``CrashLoopBackOff`` -> ``Running`` "
-"and this recovery process takes about 1 minute."
-msgstr ""
-"Der Status der Pods (wo die beiden Monitor-Prozesse beendet sind) hat sich "
-"wie folgt geändert: ``Running`` -> ``Error`` -> ``CrashLoopBackOff`` -> "
-"``Running`` und dieser Wiederherstellungsprozess dauert ungefähr 1 Minute."
-
-msgid ""
-"This guide documents steps showing Ceph version upgrade. The main goal of "
-"this document is to demostrate Ceph chart update without downtime for OSH "
-"components."
-msgstr ""
-"Dieser Leitfaden dokumentiert Schritte, die das Upgrade der Ceph-Version "
-"zeigen. Das Hauptziel dieses Dokuments besteht darin, das Ceph-Diagramm-"
-"Update ohne Ausfallzeiten für Arbeitsschutzkomponenten zu demonstrieren."
-
-msgid ""
-"This is for the case when a host machine (where ceph-mon is running) is down."
-msgstr ""
-"Dies ist der Fall, wenn eine Host-Maschine (auf der ceph-mon läuft) nicht "
-"läuft."
-
-msgid "This is to test a scenario when 1 out of 3 Monitor processes is down."
-msgstr ""
-"Dies dient zum Testen eines Szenarios, wenn 1 von 3 Überwachungsprozessen "
-"ausfällt."
-
-msgid ""
-"This is to test a scenario when 2 out of 3 Monitor processes are down. To "
-"bring down 2 Monitor processes (out of 3), we identify two Monitor processes "
-"and kill them from the 2 monitor hosts (not a pod)."
-msgstr ""
-"Dies dient dazu, ein Szenario zu testen, wenn 2 von 3 Monitor-Prozessen "
-"ausgefallen sind. Um 2 Monitor-Prozesse (von 3) zu reduzieren, "
-"identifizieren wir zwei Monitor-Prozesse und töten sie von den 2 Monitor-"
-"Hosts (kein Pod)."
-
-msgid ""
-"This is to test a scenario when 3 out of 3 Monitor processes are down. To "
-"bring down 3 Monitor processes (out of 3), we identify all 3 Monitor "
-"processes and kill them from the 3 monitor hosts (not pods)."
-msgstr ""
-"Dies dient zum Testen eines Szenarios, wenn 3 von 3 Monitor-Prozessen nicht "
-"verfügbar sind. Um 3 Monitor-Prozesse (von 3) zu reduzieren, identifizieren "
-"wir alle 3 Monitor-Prozesse und töten sie von den 3 Monitor-Hosts (nicht "
-"Pods)."
-
-msgid ""
-"This is to test a scenario when a disk failure happens. We monitor the ceph "
-"status and notice one OSD (osd.2) on voyager4 which has ``/dev/sdh`` as a "
-"backend is down."
-msgstr ""
-"Dies dient zum Testen eines Szenarios, wenn ein Festplattenfehler auftritt. "
-"Wir überwachen den Ceph-Status und bemerken ein OSD (osd.2) auf voyager4, "
-"das ``/dev/sdh`` hat, da ein Backend nicht läuft."
-
-msgid "This is to test a scenario when some of the OSDs are down."
-msgstr ""
-"Dies dient dazu, ein Szenario zu testen, wenn einige der OSDs nicht "
-"verfügbar sind."
-
-msgid ""
-"To bring down 1 Monitor process (out of 3), we identify a Monitor process "
-"and kill it from the monitor host (not a pod)."
-msgstr ""
-"Um einen Monitor-Prozess (von 3) zu reduzieren, identifizieren wir einen "
-"Monitor-Prozess und töten ihn vom Monitor-Host (kein Pod)."
-
-msgid ""
-"To bring down 6 OSDs (out of 24), we identify the OSD processes and kill "
-"them from a storage host (not a pod)."
-msgstr ""
-"Um 6 OSDs (von 24) zu reduzieren, identifizieren wir die OSD-Prozesse und "
-"löschen sie von einem Storage-Host (nicht einem Pod)."
-
-msgid "Update Ceph Client chart with new overrides:"
-msgstr "Aktualisieren Sie das Ceph-Client-Diagramm mit neuen Überschreibungen:"
-
-msgid "Update Ceph Mon chart with new overrides"
-msgstr "Aktualisieren Sie das Ceph Mon-Chart mit neuen Überschreibungen"
-
-msgid "Update Ceph OSD chart with new overrides:"
-msgstr "Aktualisieren Sie das Ceph-OSD-Diagramm mit neuen Überschreibungen:"
-
-msgid "Update Ceph Provisioners chart with new overrides:"
-msgstr ""
-"Aktualisieren Sie das Ceph Provisioners-Chart mit neuen Überschreibungen:"
-
-msgid ""
-"Update ceph install script ``./tools/deployment/multinode/030-ceph.sh`` to "
-"add ``images:`` section in overrides as shown below."
-msgstr ""
-"Aktualisieren Sie ceph install script ``./tools/deployment/multinode/ 030-"
-"ceph.sh``, um ``images:`` in Überschreibungen hinzuzufügen, wie unten "
-"gezeigt."
-
-msgid ""
-"Update, image section in new overrides ``ceph-update.yaml`` as shown below"
-msgstr ""
-"Update, Abbildausschnitt in neuen überschreibt ``ceph-update.yaml`` wie "
-"unten gezeigt"
-
-msgid "Upgrade Ceph charts to update version"
-msgstr "Aktualisieren Sie Ceph-Charts, um die Version zu aktualisieren"
-
-msgid ""
-"Upgrade Ceph charts to version 12.2.5 by updating docker images in overrides."
-msgstr ""
-"Aktualisieren Sie Ceph-Diagramme auf Version 12.2.5, indem Sie Docker-"
-"Abbilder in Overrides aktualisieren."
-
-msgid ""
-"Upgrade Ceph component version from ``12.2.4`` to ``12.2.5`` without "
-"downtime to OSH components."
-msgstr ""
-"Aktualisieren Sie die Ceph-Komponentenversion von ``12.2.4`` nach ``12.2.5`` "
-"ohne Ausfallzeiten für die OSH Komponenten."
-
-msgid ""
-"Use Ceph override file ``ceph.yaml`` that was generated previously and "
-"update images section as below"
-msgstr ""
-"Verwenden Sie die zuvor generierte Ceph Override-Datei ``ceph.yaml`` und "
-"aktualisieren Sie den Abbildbereich wie folgt"
-
-msgid ""
-"Validate the Ceph status (i.e., one OSD is added, so the total number of "
-"OSDs becomes 24):"
-msgstr ""
-"Überprüfen Sie den Ceph-Status (d.h., ein OSD wird hinzugefügt, so dass die "
-"Gesamtzahl der OSDs 24 wird):"
-
-msgid ""
-"We also monitored the status of the Monitor pod through ``kubectl get pods -"
-"n ceph``, and the status of the pod (where a Monitor process is killed) "
-"changed as follows: ``Running`` -> ``Error`` -> ``Running`` and this "
-"recovery process takes about 24 seconds."
-msgstr ""
-"Wir haben auch den Status des Monitor-Pods über ``kubectl get pods -n ceph`` "
-"überwacht, und der Status des Pods (wo ein Monitor-Prozess beendet wird) hat "
-"sich wie folgt geändert: ``Running`` -> ``Error`` -> ``Running`` und dieser "
-"Wiederherstellungsprozess dauert ungefähr 24 Sekunden."
-
-msgid ""
-"We have 3 Monitors in this Ceph cluster, one on each of the 3 Monitor hosts."
-msgstr ""
-"Wir haben 3 Monitore in diesem Ceph-Cluster, einen auf jedem der 3 Monitor-"
-"Hosts."
-
-msgid ""
-"We intentionlly destroy a Monitor database by removing ``/var/lib/openstack-"
-"helm/ceph/mon/mon/ceph-voyager3/store.db``."
-msgstr ""
-"Wir zerstören absichtlich eine Monitor-Datenbank, indem wir ``/var/lib/"
-"openstack-helm/ceph/mon/mon/ceph-voyager3/store.db`` entfernen."
-
-msgid ""
-"We monitored the status of Ceph Monitor pods and noted that the symptoms are "
-"similar to when 1 or 2 Monitor processes are killed:"
-msgstr ""
-"Wir haben den Status von Ceph Monitor-Pods überwacht und festgestellt, dass "
-"die Symptome ähnlich sind, wenn 1 oder 2 Monitor-Prozesse beendet werden:"
-
-msgid ""
-"We monitored the status of Ceph when the Monitor processes are killed and "
-"noted that the symptoms are similar to when 1 Monitor process is killed:"
-msgstr ""
-"Wir haben den Status von Ceph überwacht, als die Überwachungsprozesse "
-"beendet wurden, und festgestellt, dass die Symptome ähnlich sind, wenn 1 "
-"Überwachungsprozess beendet wird:"
-
-msgid "`Disk failure <./disk-failure.html>`_"
-msgstr "`Festplattenfehler <./disk-failure.html>`_"
-
-msgid "`Host failure <./host-failure.html>`_"
-msgstr "`Hostfehler <./host-failure.html>`_"
-
-msgid "`Monitor failure <./monitor-failure.html>`_"
-msgstr "`Monitorfehler <./monitor-failure.html>`_"
-
-msgid "`OSD failure <./osd-failure.html>`_"
-msgstr "`OSD Fehler <./osd-failure.html>`_"
-
-msgid "``Ceph MON Status:``"
-msgstr "``Ceph MON Status:``"
-
-msgid "``Ceph PODs:``"
-msgstr "``Ceph PODs:``"
-
-msgid "``Ceph PODs``"
-msgstr "``Ceph PODs``"
-
-msgid "``Ceph Status:``"
-msgstr "``Ceph Status:``"
-
-msgid "``Ceph quorum status:``"
-msgstr "``Ceph Quorum Status:``"
-
-msgid "``Ceph quorum status``"
-msgstr "``Ceph Quorum Status``"
-
-msgid "``Ceph status:``"
-msgstr "``Ceph Status:``"
-
-msgid "``Ceph status``"
-msgstr "``Ceph Status``"
-
-msgid "``OpenStack PODs:``"
-msgstr "``OpenStack PODs:``"
-
-msgid "``OpenStack PODs``"
-msgstr "``OpenStack PODs``"
-
-msgid "``Result/Observation:``"
-msgstr "``Resultat/Observation:``"
-
-msgid ""
-"``Results:`` All provisioner pods got terminated at once (same time). Other "
-"ceph pods are running. No interruption to OSH pods."
-msgstr ""
-"``Results: ``Alle Provisioner-Pods wurden gleichzeitig beendet (gleiche "
-"Zeit). Andere Ceph-Kapseln laufen. Keine Unterbrechung der OSH-Pods."
-
-msgid ""
-"``Results:`` Mon pods got updated one by one (rolling updates). Each Mon pod "
-"got respawn and was in 1/1 running state before next Mon pod got updated. "
-"Each Mon pod got restarted. Other ceph pods were not affected with this "
-"update. No interruption to OSH pods."
-msgstr ""
-"`` Ergebnisse: ``Mon-Pods wurden nacheinander aktualisiert (rollende "
-"Updates). Jeder Mon-Pod wurde respawn und war im 1/1 Laufstatus, bevor der "
-"nächste Mon-Pod aktualisiert wurde. Jeder Mon-Pod wurde neu gestartet. "
-"Andere Ceph-Pods waren von diesem Update nicht betroffen. Keine "
-"Unterbrechung der OSH-Pods."
-
-msgid ""
-"``Results:`` Rolling updates (one pod at a time). Other ceph pods are "
-"running. No interruption to OSH pods."
-msgstr ""
-"`` Ergebnisse: ``Rollende Updates (jeweils ein Pod). Andere Ceph-Kapseln "
-"laufen. Keine Unterbrechung der OSH-Pods."
-
-msgid ""
-"``ceph_bootstrap``, ``ceph-config_helper`` and ``ceph_rbs_pool`` images are "
-"used for jobs. ``ceph_mon_check`` has one script that is stable so no need "
-"to upgrade."
-msgstr ""
-"`ceph_bootstrap``, ``ceph-config_helper`` und ``ceph_rbs_pool`` Abbilder "
-"werden für Jobs verwendet. ``ceph_mon_check`` hat ein Skript, das stabil "
-"ist, also kein Upgrade nötig ist."
-
-msgid "``cp /tmp/ceph.yaml ceph-update.yaml``"
-msgstr "``cp /tmp/ceph.yaml ceph-update.yaml``"
-
-msgid "``helm upgrade ceph-client ./ceph-client --values=ceph-update.yaml``"
-msgstr "``helm upgrade ceph-client ./ceph-client --values=ceph-update.yaml``"
-
-msgid "``helm upgrade ceph-mon ./ceph-mon --values=ceph-update.yaml``"
-msgstr "`` helm upgrade ceph-mon ./ceph-mon --values=ceph-update.yaml``"
-
-msgid "``helm upgrade ceph-osd ./ceph-osd --values=ceph-update.yaml``"
-msgstr "``helm upgrade ceph-osd ./ceph-osd --values=ceph-update.yaml``"
-
-msgid ""
-"``helm upgrade ceph-provisioners ./ceph-provisioners --values=ceph-update."
-"yaml``"
-msgstr ""
-"``helm upgrade ceph-provisioners ./ceph-provisioners --values=ceph-update."
-"yaml``"
-
-msgid "``series of console outputs:``"
-msgstr "``Reihe der Konsolenausgaben:``"
diff --git a/doc/source/locale/de/LC_MESSAGES/doc-troubleshooting.po b/doc/source/locale/de/LC_MESSAGES/doc-troubleshooting.po
deleted file mode 100644
index 044b936882..0000000000
--- a/doc/source/locale/de/LC_MESSAGES/doc-troubleshooting.po
+++ /dev/null
@@ -1,210 +0,0 @@
-# Frank Kloeker <eumel@arcor.de>, 2018. #zanata
-# Andreas Jaeger <jaegerandi@gmail.com>, 2021. #zanata
-msgid ""
-msgstr ""
-"Project-Id-Version: openstack-helm 0.1.1.dev3462\n"
-"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2021-06-22 20:22+0000\n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-"PO-Revision-Date: 2021-04-16 08:41+0000\n"
-"Last-Translator: Andreas Jaeger <jaegerandi@gmail.com>\n"
-"Language-Team: German\n"
-"Language: de\n"
-"Plural-Forms: nplurals=2; plural=(n != 1)\n"
-"X-Generator: Zanata 4.3.3\n"
-
-msgid "Backing up a PVC"
-msgstr "Ein PVC sichern"
-
-msgid ""
-"Backing up a PVC stored in Ceph, is fairly straigthforward, in this example "
-"we use the PVC ``mysql-data-mariadb-server-0`` as an example, but this will "
-"also apply to any other services using PVCs eg. RabbitMQ, Postgres."
-msgstr ""
-"Die Sicherung eines in Ceph gespeicherten PVCs ist ziemlich geradlinig, in "
-"diesem Beispiel verwenden wir als Beispiel den PVC-Server ``mysql-data-"
-"mariab-server-0``, aber dies gilt auch für alle anderen Dienste, die PVCs "
-"verwenden, z. RabbitMQ, Postgres."
-
-msgid ""
-"Before proceeding, it is important to ensure that you have deployed a client "
-"key in the namespace you wish to fulfill ``PersistentVolumeClaims``. To "
-"verify that your deployment namespace has a client key:"
-msgstr ""
-"Bevor Sie fortfahren, müssen Sie sicherstellen, dass Sie einen "
-"Clientschlüssel in dem Namespace implementiert haben, den Sie mit "
-"``PersistentVolumeClaims`` erfüllen möchten. So überprüfen Sie, ob Ihr "
-"Implementierungsnamespace über einen Clientschlüssel verfügt:"
-
-msgid "Bugs and Feature requests"
-msgstr "Bugs und Feature Anfragen"
-
-msgid "Ceph"
-msgstr "Ceph"
-
-msgid "Ceph Deployment Status"
-msgstr "Ceph-Bereitstellungsstatus"
-
-msgid "Ceph Validating PVC Operation"
-msgstr "Ceph Validierung des PVC-Betriebs"
-
-msgid "Ceph Validating StorageClass"
-msgstr "Ceph Validierung von StorageClass"
-
-msgid "Channels"
-msgstr "Kanäle"
-
-msgid "Database Deployments"
-msgstr "Datenbankbereitstellungen"
-
-msgid ""
-"First, we want to validate that Ceph is working correctly. This can be done "
-"with the following Ceph command:"
-msgstr ""
-"Zuerst wollen wir bestätigen, dass Ceph korrekt funktioniert. Dies kann mit "
-"dem folgenden Ceph-Befehl geschehen:"
-
-msgid "Galera Cluster"
-msgstr "Galera-Cluster"
-
-msgid "Getting help"
-msgstr "Hilfe bekommen"
-
-msgid "Installation"
-msgstr "Installation"
-
-msgid "Join us on `Slack <http://slack.k8s.io/>`_ - #openstack-helm"
-msgstr ""
-"Begleiten Sie uns auf `Slack <http://slack.k8s.io/>`_ - #openstack-helm"
-
-msgid ""
-"Next we can look at the storage class, to make sure that it was created "
-"correctly:"
-msgstr ""
-"Als nächstes können wir uns die Speicherklasse ansehen, um sicherzustellen, "
-"dass sie korrekt erstellt wurde:"
-
-msgid ""
-"Note: This step is not relevant for PVCs within the same namespace Ceph was "
-"deployed."
-msgstr ""
-"Hinweis: Dieser Schritt ist nicht relevant für PVCs in demselben Namespace, "
-"in dem Ceph implementiert wurde."
-
-msgid "Once this has been done the workload can be restarted."
-msgstr "Sobald dies erledigt ist, kann die Arbeitslast neu gestartet werden."
-
-msgid "PVC Preliminary Validation"
-msgstr "PVC-Vorprüfung"
-
-msgid "Persistent Storage"
-msgstr "Dauerspeicher"
-
-msgid ""
-"Please, refer to `Contribution guidelines <../contributor/contributing."
-"html>`_."
-msgstr ""
-"Lesen Sie die `Richtlinien für Mitwirkende  <../contributor/contributing."
-"html>`_."
-
-msgid ""
-"Restoring is just as straightforward. Once the workload consuming the device "
-"has been stopped, and the raw RBD device removed the following will import "
-"the back up and create a device:"
-msgstr ""
-"Das Wiederherstellen ist genauso einfach. Sobald die Arbeitslast, die das "
-"Gerät verbraucht, beendet wurde und das RBD-Gerät entfernt wurde, wird das "
-"Folgende in die Sicherung importiert und ein Gerät erstellt:"
-
-msgid ""
-"Sometimes things go wrong. These guides will help you solve many common "
-"issues with the following:"
-msgstr ""
-"Manchmal gehen Dinge schief. Diese Handbücher helfen Ihnen bei der Lösung "
-"vieler häufig auftretender Probleme:"
-
-msgid ""
-"The parameters are what we're looking for here. If we see parameters passed "
-"to the StorageClass correctly, we will see the ``ceph-mon.ceph.svc.cluster."
-"local:6789`` hostname/port, things like ``userid``, and appropriate secrets "
-"used for volume claims."
-msgstr ""
-"Nach den Parametern suchen wir hier. Wenn wir sehen, dass die Parameter "
-"korrekt an die StorageClass übergeben werden, sehen wir den ``ceph-mon.ceph."
-"svc.cluster.local:6789`` Hostnamen/Port, Dinge wie ``userid`` und "
-"entsprechende Secrets, die für Volume Claims verwendet werden ."
-
-msgid ""
-"This guide is to help users debug any general storage issues when deploying "
-"Charts in this repository."
-msgstr ""
-"Dieser Leitfaden soll Benutzern helfen, allgemeine Speicherprobleme beim "
-"Bereitstellen von Charts in diesem Repository zu beheben."
-
-msgid ""
-"This guide is to help users debug any general storage issues when deploying "
-"charts in this repository."
-msgstr ""
-"Dieses Handbuch soll Benutzern helfen, allgemeine Speicherprobleme beim "
-"Bereitstellen von Diagrammen in diesem Repository zu beheben."
-
-msgid ""
-"To deploy the HWE kernel, prior to deploying Kubernetes and OpenStack-Helm "
-"the following commands should be run on each node:"
-msgstr ""
-"Zur Bereitstellung des HWE-Kernels sollten vor der Bereitstellung von "
-"Kubernetes und OpenStack-Helm die folgenden Befehle auf jedem Knoten "
-"ausgeführt werden:"
-
-msgid ""
-"To make use of CephFS in Ubuntu the HWE Kernel is required, until the issue "
-"described `here <https://github.com/kubernetes-incubator/external-storage/"
-"issues/345>`_ is fixed."
-msgstr ""
-"Um CephFS in Ubuntu nutzen zu können, wird der HWE-Kernel benötigt, bis das "
-"Problem hier beschrieben wird <https://github.com/kubernetes-incubator/"
-"external-storage/issues/345>`_ ist behoben."
-
-msgid "To test MariaDB, do the following:"
-msgstr "Um MariaDB zu testen, machen Sie folgendes:"
-
-msgid ""
-"To validate persistent volume claim (PVC) creation, we've placed a test "
-"manifest `here <https://raw.githubusercontent.com/openstack/openstack-helm/"
-"master/tests/pvc-test.yaml>`_. Deploy this manifest and verify the job "
-"completes successfully."
-msgstr ""
-"Um die Erstellung eines persistenten Volumenanspruchs (PVC) zu validieren, "
-"haben wir ein Testmanifest `hier platziert <https://raw.githubusercontent."
-"com/openstack/openstack-helm/master/tests/pvc-test.yaml>`_. Stellen Sie "
-"dieses Manifest bereit und überprüfen Sie, ob der Job erfolgreich "
-"abgeschlossen wurde."
-
-msgid "Troubleshooting"
-msgstr "Fehlerbehebung"
-
-msgid "Ubuntu HWE Kernel"
-msgstr "Ubuntu HWE Kernel"
-
-msgid ""
-"Use one of your Ceph Monitors to check the status of the cluster. A couple "
-"of things to note above; our health is `HEALTH\\_OK`, we have 3 mons, we've "
-"established a quorum, and we can see that all of our OSDs are up and in the "
-"OSD map."
-msgstr ""
-"Verwenden Sie einen Ihrer Ceph-Monitore, um den Status des Clusters zu "
-"überprüfen. Ein paar Dinge zu beachten; unser Gesundheitszustand ist HEALTH "
-"\\_OK`, wir haben 3 Mons, wir haben ein Quorum eingerichtet, und wir können "
-"sehen, dass alle unsere OSDs in der OSD-Karte aufgeführt sind."
-
-msgid ""
-"Without this, your RBD-backed PVCs will never reach the ``Bound`` state.  "
-"For more information, see how to `activate namespace for ceph <../install/"
-"multinode.html#activating-control-plane-namespace-for-ceph>`_."
-msgstr ""
-"Ohne dies werden Ihre RBD-unterstützten PVCs niemals den ``Bound`` -Zustand "
-"erreichen. Weitere Informationen finden Sie unter `namespace für ceph "
-"aktivieren <../install/multinode.html#activating-control-plane-namespace-for-"
-"ceph>`_."
diff --git a/doc/source/locale/de/LC_MESSAGES/doc.po b/doc/source/locale/de/LC_MESSAGES/doc.po
deleted file mode 100644
index 04024c3083..0000000000
--- a/doc/source/locale/de/LC_MESSAGES/doc.po
+++ /dev/null
@@ -1,403 +0,0 @@
-# Andreas Jaeger <jaegerandi@gmail.com>, 2018. #zanata
-# Frank Kloeker <eumel@arcor.de>, 2018. #zanata
-# Robert Simai <robert.simai@suse.com>, 2019. #zanata
-# Andreas Jaeger <jaegerandi@gmail.com>, 2021. #zanata
-msgid ""
-msgstr ""
-"Project-Id-Version: openstack-helm 0.1.1.dev3879\n"
-"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2022-10-24 20:45+0000\n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-"PO-Revision-Date: 2021-04-16 08:40+0000\n"
-"Last-Translator: Andreas Jaeger <jaegerandi@gmail.com>\n"
-"Language-Team: German\n"
-"Language: de\n"
-"Plural-Forms: nplurals=2; plural=(n != 1)\n"
-"X-Generator: Zanata 4.3.3\n"
-
-msgid ":ref:`genindex`"
-msgstr ":ref: `genindex`"
-
-msgid ":ref:`search`"
-msgstr ":ref: `suchen`"
-
-msgid "Adding Services"
-msgstr "Hinzufügen von Diensten"
-
-msgid "Adding Tests"
-msgstr "Hinzufügen von Tests"
-
-msgid ""
-"Any additional functions required for testing new charts or improving the "
-"gate workflow should be placed in the appropriate location."
-msgstr ""
-"Alle zusätzlichen Funktionen, die zum Testen neuer Diagramme oder zum "
-"Verbessern des Gate-Workflows erforderlich sind, sollten an der "
-"entsprechenden Stelle platziert werden."
-
-msgid ""
-"Any tests that do not use the Rally testing framework would need to be "
-"handled in the appropriate manner in launch script. This would ideally "
-"result in new functions that could be reused, or expansion of the gate "
-"scripts to include scenarios beyond basic service launches."
-msgstr ""
-"Alle Tests, die das Rally-Test-Framework nicht verwenden, müssen im Start-"
-"Skript entsprechend behandelt werden. Dies würde idealerweise zu neuen "
-"Funktionen führen, die wiederverwendet werden könnten, oder eine Erweiterung "
-"der Gate-Scripts um Szenarien, die über die Einführung von Basisdiensten "
-"hinausgehen."
-
-msgid ""
-"As charts for additional services are added to OpenStack-Helm, they should "
-"be included in the gates.  Adding new services to the gates allows a chart "
-"developer and the review team to identify any potential issues associated "
-"with a new service. All services are currently launched in the gate via a "
-"series of launch scripts of the format ``NNN-service-name.sh`` where ``NNN`` "
-"dictates the order these scripts are launched. The script should contain an "
-"installation command like:"
-msgstr ""
-"Da Charts für zusätzliche Dienste zu OpenStack-Helm hinzugefügt werden, "
-"sollten sie in den Gates enthalten sein. Durch Hinzufügen neuer Dienste zu "
-"den Gates können ein Charts-Entwickler und das Überprüfungsteam potenzielle "
-"Probleme identifizieren, die mit einem neuen Dienst verbunden sind. Alle "
-"Dienste werden derzeit über eine Reihe von Start-Skripts im Format ``NNN-"
-"service-name.sh``  gestartet, wobei ``NNN`` die Reihenfolge angibt, in der "
-"diese Skripte gestartet werden. Das Skript sollte einen Installationsbefehl "
-"enthalten wie:"
-
-msgid ""
-"As new charts are developed and the services are added to the gate, an "
-"associated Helm test should be introduced to the gates.  The appropriate "
-"place for executing these tests is in the respective service's launch "
-"script, and must be placed after the entry for installing the service and "
-"any associated overrides.  Any tests that use the Rally testing framework "
-"should leverage the helm_test_deployment function in the aforementioned "
-"funcs/helm.sh file. For example, a Helm test for Mistral might look like:"
-msgstr ""
-"Wenn neue Charts entwickelt werden und die Dienste dem gate hinzugefügt "
-"werden, sollte ein zugehöriger Helm-Test zu den Gates eingeführt werden. Der "
-"entsprechende Ort zum Ausführen dieser Tests befindet sich im Startskript "
-"des jeweiligen Diensts und muss nach dem Eintrag für die Installation des "
-"Diensts und den zugehörigen Überschreibungen platziert werden. Alle Tests, "
-"die das Rally-Test-Framework verwenden, sollten die Funktion "
-"helm_test_deployment in der oben genannten Datei funcs/helm.sh nutzen. Zum "
-"Beispiel könnte ein Helm-Test für Mistral wie folgt aussehen:"
-
-msgid ""
-"Bugs and enhancements are tracked via OpenStack-Helm's `Storyboard <https://"
-"storyboard.openstack.org/#!/project_group/64>`_."
-msgstr ""
-"Bugs und Verbesserungen werden über das Storyboard von OpenStack-Helm "
-"verfolgt <https://storyboard.openstack.org/#!/project_group/64>`_."
-
-msgid "Communication"
-msgstr "Kommunikation"
-
-msgid "Contents:"
-msgstr "Inhalt:"
-
-msgid "Contributing"
-msgstr "Beitragend"
-
-msgid ""
-"Developers wishing to work on the OpenStack-Helm project should always base "
-"their work on the latest code, available from the OpenStack-Helm git "
-"repository."
-msgstr ""
-"Entwickler, welche am OpenStack-Helm Projekt mitarbeiten wollen, sollen "
-"immer ihre Arbeit auf den aktuellen Code basieren, welcher im OpenStack-Helm "
-"Git Repository verfügbar ist."
-
-msgid ""
-"Functions for Helm specific operations, found in helm.sh.  These functions "
-"include: installing Helm, serving a Helm repository locally, linting and "
-"building all Helm charts, running Helm tests on a release, installing the "
-"helm template plugin, and running the helm template plugin against a chart."
-msgstr ""
-"Funktionen für helmspezifische Operationen, gefunden in helm.sh. Zu diesen "
-"Funktionen gehören: Helm installieren, ein Helm-Repository lokal "
-"bereitstellen, alle Helm-Diagramme filtern und erstellen, Helm-Tests für ein "
-"Release ausführen, das Helm-Vorlagen-Plugin installieren und das Helm-"
-"Vorlagen-Plugin gegen ein Diagramm ausführen."
-
-msgid ""
-"Functions for Kubernetes specific operations, found in kube.sh.  These "
-"functions include: waiting for pods in a specific namespace to register as "
-"ready, waiting for all nodes to register as ready, install the requirements "
-"for the kubeadm-aio container used in the gates, building the kubeadm-aio "
-"container, launching the kubeadm-aio container, and replacing the kube-"
-"controller-manager with a specific image necessary for ceph functionality."
-msgstr ""
-"Funktionen für Kubernetes-spezifische Operationen, gefunden in kube.sh. Zu "
-"diesen Funktionen gehören: Warten auf Pods in einem bestimmten Namespace, um "
-"sich als bereit zu registrieren, Warten auf die Registrierung aller Knoten "
-"als bereit, Installieren der Anforderungen für den in den Gates verwendeten "
-"kubeadm-aio-Container, Erstellen des kubeadm-aio-Containers, Starten des "
-"kubeadm-aio-Containers aio container, und ersetzen Sie den kube-controller-"
-"manager durch ein spezielles Abbild, das für die ceph-Funktionalität "
-"benötigt wird."
-
-msgid ""
-"Functions for OpenStack specific operations, found in openstack.sh.  These "
-"functions include: waiting for a successful ping, and waiting for a booted "
-"virtual machine's status to return as ACTIVE."
-msgstr ""
-"Funktionen für OpenStack-spezifische Operationen, die in openstack.sh "
-"enthalten sind. Zu diesen Funktionen gehören: Warten auf einen erfolgreichen "
-"Ping und Warten auf den Status einer gestarteten virtuellen Maschine als "
-"ACTIVE."
-
-msgid "Functions for common host preparation operations, found in common.sh"
-msgstr ""
-"Funktionen für allgemeine Hostvorbereitungsoperationen, die unter common.sh "
-"zu finden sind"
-
-msgid ""
-"Functions for network specific operations, found in network.sh.  These "
-"functions include: creating a backup of the host's resolv.conf file before "
-"deploying the kubeadm environments, restoring the original resolv.conf "
-"settings, creating a backup of the host's /etc/hosts file before adding the "
-"hosts interface and address, and restoring the original /etc/hosts file."
-msgstr ""
-"Funktionen für netzwerkspezifische Operationen, gefunden in network.sh. Zu "
-"diesen Funktionen gehören: Erstellen einer Sicherungskopie der resolv.conf-"
-"Datei des Hosts vor dem Bereitstellen der kubeadm-Umgebungen, "
-"Wiederherstellen der ursprünglichen resolv.conf-Einstellungen, Erstellen "
-"einer Sicherungskopie der Datei /etc/hosts des Hosts vor dem Hinzufügen der "
-"Hostschnittstelle und -adresse und Wiederherstellen der Original /etc/hosts "
-"Datei."
-
-msgid "Gate Checks"
-msgstr "Gate Checks"
-
-msgid "Gate Functions"
-msgstr "Gate-Funktionen"
-
-msgid "Gate Output"
-msgstr "Gate-Ausgang"
-
-msgid "Indices and Tables"
-msgstr "Indizes und Tabellen"
-
-msgid "Installation and Development"
-msgstr "Installation und Entwicklung"
-
-msgid ""
-"Join us on `Slack <https://kubernetes.slack.com/messages/C3WERB7DE/>`_ - "
-"#openstack-helm"
-msgstr ""
-"Begleiten Sie uns auf `Slack <https://kubernetes.slack.com/messages/"
-"C3WERB7DE/>`_ - #openstack-helm"
-
-msgid ""
-"Meeting Agenda Items: `Agenda <https://etherpad.openstack.org/p/openstack-"
-"helm-meeting-agenda>`_"
-msgstr ""
-"Tagesordnungspunkte: `Agenda <https://etherpad.openstack.org/p/openstack-"
-"helm-meeting-agenda>`_"
-
-msgid "Mission"
-msgstr "Mission"
-
-msgid "OpenStack-Helm"
-msgstr "OpenStack-Helm"
-
-msgid "OpenStack-Helm Gates"
-msgstr "OpenStack-Helm Gates"
-
-msgid "OpenStack-Helm currently checks the following scenarios:"
-msgstr "OpenStack-Helm überprüft derzeit die folgenden Szenarien:"
-
-msgid ""
-"OpenStack-Helm's single node and multinode gates leverage the kubeadm-aio "
-"environment created and maintained for use as a development environment.  "
-"All information regarding the kubeadm-aio environment can be found here_."
-msgstr ""
-"Die Single-Node- und Multinode-Gates von OpenStack-Helm nutzen die kubeadm-"
-"aio-Umgebung, die zur Verwendung als Entwicklungsumgebung erstellt und "
-"verwaltet wird. Alle Informationen zur kubeadm-aio-Umgebung finden Sie hier."
-
-msgid ""
-"Provisioning a multi-node Ubuntu-1604 cluster and deploying the OpenStack "
-"services. This check is provided for both a two node cluster and a three "
-"node cluster."
-msgstr ""
-"Bereitstellung eines Ubuntu-1604-Clusters mit mehreren Knoten und "
-"Bereitstellung der OpenStack-Dienste. Diese Überprüfung wird sowohl für "
-"einen Cluster mit zwei Knoten als auch für einen Cluster mit drei Knoten "
-"bereitgestellt."
-
-msgid ""
-"Provisioning a single node cluster and deploying the OpenStack services.  "
-"This check is provided for: Ubuntu-1604, CentOS-7, and Fedora-25."
-msgstr ""
-"Bereitstellen eines einzelnen Knotenclusters und Bereitstellen der OpenStack-"
-"Dienste. Dieser Check ist vorgesehen für: Ubuntu-1604, CentOS-7 und "
-"Fedora-25."
-
-msgid "Repository"
-msgstr "Repository"
-
-msgid ""
-"Running Make on each chart, which lints and packages the charts.  This gate "
-"does not stand up a Kubernetes cluster."
-msgstr ""
-"Starte Make für jedes Chart, welches Charts mit Lint überprüft und packt. "
-"Dieses Gate startet keinen Kubernetes-Cluster."
-
-msgid ""
-"Some services in the gate require specific overrides to the default values "
-"in the chart's values.yaml file.  If a service requires multiple overrides "
-"to function in the gate, the service should include a separate values.yaml "
-"file placed in the tools/overrides/mvp directory.  The <service>.yaml MVP "
-"files provide a configuration file to use for overriding default "
-"configuration values in the chart's values.yaml as an alternative to "
-"overriding individual values during installation.  A chart that requires a "
-"MVP overrides file requires the following format:"
-msgstr ""
-"Einige Dienste im Gate erfordern bestimmte Überschreibungen zu den "
-"Standardwerten in der values.yaml-Datei des Charts. Wenn ein Dienst mehrere "
-"Überschreibungen benötigt, um im Gate zu funktionieren, sollte der Dienst "
-"eine separate Datei values.yaml enthalten, die im Verzeichnis tools/"
-"overrides/mvp abgelegt ist. Die <service>.yaml MVP-Dateien bieten eine "
-"Konfigurationsdatei, die zum Überschreiben von Standardkonfigurationswerten "
-"in den values.yaml des Diagramms als Alternative zum Überschreiben einzelner "
-"Werte während der Installation verwendet werden kann. Ein Diagramm, für das "
-"eine MVP-Überschreibungsdatei erforderlich ist, muss das folgende Format "
-"aufweisen:"
-
-msgid "Storyboard"
-msgstr "Storyboard"
-
-msgid "Testing any documentation changes and impacts."
-msgstr "Testen von Änderungen und Auswirkungen der Dokumentation"
-
-msgid ""
-"The K8s directory contains the logs and output of the Kubernetes objects.  "
-"It includes: pods, nodes, secrets, services, namespaces, configmaps, "
-"deployments, daemonsets, and statefulsets.  Descriptions for the state of "
-"all resources during execution are found here, and this information can "
-"prove valuable when debugging issues raised during a check.  When a single "
-"node or multi-node check fails, this is the first place to look.  The logs "
-"found here are helpful when the templates render correctly, but the services "
-"are not functioning correctly, whether due to service configuration issues "
-"or issues with the pods themselves."
-msgstr ""
-"Das Verzeichnis K8s enthält die Protokolle und die Ausgabe der Kubernetes-"
-"Objekte. Dazu gehören: Pods, Knoten, Secrets, Services, Namespaces, "
-"Configmaps, Bereitstellungen, Daemonsets und Statefulsets. Beschreibungen "
-"für den Status aller Ressourcen während der Ausführung finden Sie hier. "
-"Diese Informationen können sich beim Debuggen von Problemen während einer "
-"Prüfung als nützlich erweisen. Wenn eine Prüfung mit einem einzelnen Knoten "
-"oder mehreren Knoten fehlschlägt, sollten Sie zuerst nachsehen. Die hier "
-"gefundenen Protokolle sind hilfreich, wenn die Vorlagen korrekt gerendert "
-"werden, die Dienste jedoch nicht ordnungsgemäß funktionieren, unabhängig "
-"davon, ob Probleme mit der Dienstkonfiguration oder Probleme mit den Pods "
-"auftreten."
-
-msgid ""
-"The dry-runs directory contains the rendered output of Helm dry-run installs "
-"on each of the OpenStack service charts.  This gives visibility into the "
-"manifests created by the templates with the supplied values.  When the dry-"
-"run gate fails, the reason should be apparent in the dry-runs output.  The "
-"logs found here are helpful in identifying issues resulting from using helm-"
-"toolkit functions incorrectly or other rendering issues with gotpl."
-msgstr ""
-"Das Dry-runs-Verzeichnis enthält die gerenderte Ausgabe von Helm-Dry-Run-"
-"Installationen auf jedem der OpenStack-Dienstchart. Dadurch erhalten Sie "
-"Einblick in die Manifeste, die von den Vorlagen mit den angegebenen Werten "
-"erstellt wurden. Wenn das Dry-run-Gate versagt, sollte der Grund in der Dry-"
-"Run-Ausgabe offensichtlich sein. Die hier gefundenen Logs sind hilfreich, um "
-"Probleme zu identifizieren, die sich aus der falschen Verwendung von Helm-"
-"Toolkit-Funktionen oder anderen Rendering-Problemen mit gotpl ergeben."
-
-msgid ""
-"The goal of OpenStack-Helm is to provide a collection of Helm charts that "
-"simply, resiliently, and flexibly deploy OpenStack and related services on "
-"Kubernetes."
-msgstr ""
-"Das Ziel von OpenStack-Helm ist es, eine Sammlung von Helm-Charts zur "
-"Verfügung zu stellen, die OpenStack und zugehörige Dienste auf Kubernetes "
-"einfach, flexibel und flexibel bereitstellen."
-
-msgid ""
-"The nodes directory contains information about the node the gate tests are "
-"running on in openstack-infra.  This includes: the network interfaces, the "
-"contents of iptables, the host's resolv.conf, and the kernel IP routing "
-"table. These logs can be helpful when trying to identify issues with host "
-"networking or other issues at the node level."
-msgstr ""
-"Das Knotenverzeichnis enthält Informationen zu dem Knoten, auf dem die Gate-"
-"Tests in openstack-infra ausgeführt werden. Dazu gehören: die "
-"Netzwerkschnittstellen, der Inhalt von iptables, die resolv.conf des Hosts "
-"und die Kernel-IP-Routingtabelle. Diese Protokolle können hilfreich sein, "
-"wenn Sie versuchen, Probleme mit dem Hostnetzwerk oder andere Probleme auf "
-"Knotenebene zu identifizieren."
-
-msgid ""
-"This project is under active development. We encourage anyone interested in "
-"OpenStack-Helm to review our `Installation <https://docs.openstack.org/"
-"openstack-helm/latest/install/index.html>`_ documentation. Feel free to ask "
-"questions or check out our current `Storyboard backlog <https://storyboard."
-"openstack.org/#!/project_group/64>`_."
-msgstr ""
-"Dieses Projekt wird aktiv weiterentwickelt. Wir empfehlen jedem, der an "
-"OpenStack-Helm interessiert ist, unsere `Installation` zu überprüfen "
-"<https://docs.openstack.org/openstack-helm/latest/install/index.html>`_ "
-"Dokumentation. Sie können Fragen stellen oder unseren aktuellen Storyboard-"
-"Backlog lesen <https://storyboard.openstack.org/#!/project_group/64>`_."
-
-msgid "This results in the gate running the following:"
-msgstr "Dies führt dazu, dass das Gate folgendes ausführt:"
-
-msgid ""
-"To evaluate a multinode installation, follow the `Bare Metal <https://docs."
-"openstack.org/openstack-helm/latest/install/multinode.html>`_ install guide."
-msgstr ""
-"Um eine Multinode-Installation zu evaluieren, folgen Sie dem Bare Metal "
-"<https://docs.openstack.org/openstack-helm/latest/install/multinode.html>`_ "
-"Installationsanleitung."
-
-msgid ""
-"To facilitate ease of testing and debugging, information regarding gates and "
-"their functionality can be found here."
-msgstr ""
-"Um das Testen und Debuggen zu erleichtern, finden Sie hier Informationen zu "
-"Gates und deren Funktionalität."
-
-msgid ""
-"To provide meaningful output from the gates, all information pertaining to "
-"the components of the cluster and workflow are output to the logs directory "
-"inside each gate.  The contents of the log directory are as follows:"
-msgstr ""
-"Um eine sinnvolle Ausgabe von den Gates bereitzustellen, werden alle "
-"Informationen bezüglich der Komponenten des Clusters und des Arbeitsablaufs "
-"in das Protokollverzeichnis innerhalb jedes Gates ausgegeben. Der Inhalt des "
-"Protokollverzeichnisses ist wie folgt:"
-
-msgid ""
-"To provide reusable components for gate functionality, functions have been "
-"provided in the gates/funcs directory. These functions include:"
-msgstr ""
-"Um wiederverwendbare Komponenten für die Gate-Funktionalität "
-"bereitzustellen, wurden Funktionen im Verzeichnis gates/funcs "
-"bereitgestellt. Diese Funktionen umfassen:"
-
-msgid ""
-"We welcome contributions. Check out `this <CONTRIBUTING.rst>`_ document if "
-"you would like to get involved."
-msgstr ""
-"Wir freuen uns über Beiträge. Schauen Sie sich `dieses <CONTRIBUTING.rst>`_ "
-"Dokument um, falls Sie mitmachen wollen."
-
-msgid "Welcome to OpenStack-Helm's documentation!"
-msgstr "Willkommen zur Dokumentation von OpenStack-Helm!"
-
-msgid ""
-"`OpenStack-Helm git repository <https://opendev.org/openstack/openstack-helm/"
-">`_"
-msgstr ""
-"`OpenStack-Helm git Repository <https://opendev.org/openstack/openstack-helm/"
-">`_"
diff --git a/doc/source/locale/en_GB/LC_MESSAGES/doc-contributor.po b/doc/source/locale/en_GB/LC_MESSAGES/doc-contributor.po
deleted file mode 100644
index 1bbf957a46..0000000000
--- a/doc/source/locale/en_GB/LC_MESSAGES/doc-contributor.po
+++ /dev/null
@@ -1,175 +0,0 @@
-# Andi Chandler <andi@gowling.com>, 2020. #zanata
-# Andi Chandler <andi@gowling.com>, 2021. #zanata
-msgid ""
-msgstr ""
-"Project-Id-Version: openstack-helm 0.1.1.dev3462\n"
-"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2021-06-22 20:22+0000\n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-"PO-Revision-Date: 2021-06-24 03:48+0000\n"
-"Last-Translator: Andi Chandler <andi@gowling.com>\n"
-"Language-Team: English (United Kingdom)\n"
-"Language: en_GB\n"
-"X-Generator: Zanata 4.3.3\n"
-"Plural-Forms: nplurals=2; plural=(n != 1)\n"
-
-msgid ""
-"Additional information could be found in `OpenDev Developer's Guide <https://"
-"docs.opendev.org/opendev/infra-manual/latest/developers.html>`_."
-msgstr ""
-"Additional information could be found in `OpenDev Developer's Guide <https://"
-"docs.opendev.org/opendev/infra-manual/latest/developers.html>`_."
-
-msgid ""
-"All common PTL duties are enumerated in the `PTL guide <https://docs."
-"openstack.org/project-team-guide/ptl.html>`_."
-msgstr ""
-"All common PTL duties are enumerated in the `PTL guide <https://docs."
-"openstack.org/project-team-guide/ptl.html>`_."
-
-msgid ""
-"Below will cover the more project specific information you need to get "
-"started with OpenStack-Helm."
-msgstr ""
-"Below will cover the more project specific information you need to get "
-"started with OpenStack-Helm."
-
-msgid "Bugs should be filed as stories in Storyboard, not GitHub."
-msgstr "Bugs should be filed as stories in Storyboard, not GitHub."
-
-msgid ""
-"Changes affecting code base often require CI tests and documentation to be "
-"added in the same patch set."
-msgstr ""
-"Changes affecting code base often require CI tests and documentation to be "
-"added in the same patch set."
-
-msgid "Communication"
-msgstr "Communication"
-
-msgid ""
-"Community `IRC Meetings <http://eavesdrop.openstack.org/#OpenStack-"
-"Helm_Team_Meeting>`_: [Every Tuesday @ 3PM UTC], #openstack-meeting-alt on "
-"oftc"
-msgstr ""
-"Community `IRC Meetings <http://eavesdrop.openstack.org/#OpenStack-"
-"Helm_Team_Meeting>`_: [Every Tuesday @ 3PM UTC], #openstack-meeting-alt on "
-"oftc"
-
-msgid "Contacting the Core Team"
-msgstr "Contacting the Core Team"
-
-msgid ""
-"For general information on contributing to OpenStack, please check out the "
-"`contributor guide <https://docs.openstack.org/contributors/>`_ to get "
-"started. It covers all the basics that are common to all OpenStack projects: "
-"the accounts you need, the basics of interacting with our Gerrit review "
-"system, how we communicate as a community, etc."
-msgstr ""
-"For general information on contributing to OpenStack, please check out the "
-"`contributor guide <https://docs.openstack.org/contributors/>`_ to get "
-"started. It covers all the basics that are common to all OpenStack projects: "
-"the accounts you need, the basics of interacting with our Gerrit review "
-"system, how we communicate as a community, etc."
-
-msgid "Getting Your Patch Merged"
-msgstr "Getting Your Patch Merged"
-
-msgid ""
-"If issue is on one of other OpenStack-Helm components, report it to the "
-"appropriate `group Storyboard`_."
-msgstr ""
-"If issue is on one of other OpenStack-Helm components, report it to the "
-"appropriate `group Storyboard`_."
-
-msgid ""
-"If you're looking for some smaller, easier work item to pick up and get "
-"started on, search for the 'low-hanging-fruit' tag."
-msgstr ""
-"If you're looking for some smaller, easier work item to pick up and get "
-"started on, search for the 'low-hanging-fruit' tag."
-
-msgid ""
-"Join us on `IRC <irc://chat.oftc.net/openstack-helm>`_: #openstack-helm on "
-"oftc"
-msgstr ""
-"Join us on `IRC <irc://chat.oftc.net/openstack-helm>`_: #openstack-helm on "
-"oftc"
-
-msgid ""
-"Join us on `Slack <https://kubernetes.slack.com/messages/C3WERB7DE/>`_ - "
-"#openstack-helm"
-msgstr ""
-"Join us on `Slack <https://kubernetes.slack.com/messages/C3WERB7DE/>`_ - "
-"#openstack-helm"
-
-msgid ""
-"Meeting Agenda Items: `Agenda <https://etherpad.openstack.org/p/openstack-"
-"helm-meeting-agenda>`_"
-msgstr ""
-"Meeting Agenda Items: `Agenda <https://etherpad.openstack.org/p/openstack-"
-"helm-meeting-agenda>`_"
-
-msgid "New Feature Planning"
-msgstr "New Feature Planning"
-
-msgid ""
-"New features are planned and implemented trough the process described in "
-"`Project Specifications <../specs/index.html>`_ section of this document."
-msgstr ""
-"New features are planned and implemented trough the process described in "
-"`Project Specifications <../specs/index.html>`_ section of this document."
-
-msgid ""
-"Other OpenStack-Helm component's tasks could be found on the `group "
-"Storyboard`_."
-msgstr ""
-"Other OpenStack-Helm component's tasks could be found on the `group "
-"Storyboard`_."
-
-msgid "Project Team Lead Duties"
-msgstr "Project Team Lead Duties"
-
-msgid ""
-"Project's Core Team could be contacted via IRC or Slack, usually during "
-"weekly meetings. List of current Cores could be found on a Members tab of "
-"`openstack-helm-core <https://review.opendev.org/#/admin/groups/1749,info>`_ "
-"Gerrit group."
-msgstr ""
-"Project's Core Team could be contacted via IRC or Slack, usually during "
-"weekly meetings. List of current Cores could be found on a Members tab of "
-"`openstack-helm-core <https://review.opendev.org/#/admin/groups/1749,info>`_ "
-"Gerrit group."
-
-msgid "Pull requests submitted through GitHub will be ignored."
-msgstr "Pull requests submitted through GitHub will be ignored."
-
-msgid "Reporting a Bug"
-msgstr "Reporting a Bug"
-
-msgid "So You Want to Contribute..."
-msgstr "So You Want to Contribute..."
-
-msgid "Task Tracking"
-msgstr "Task Tracking"
-
-msgid ""
-"We require two Code-Review +2's from reviewers, before getting your patch "
-"merged with giving Workforce +1. Trivial patches (e.g. typos) could be "
-"merged with one Code-Review +2."
-msgstr ""
-"We require two Code-Review +2's from reviewers, before getting your patch "
-"merged with giving Workforce +1. Trivial patches (e.g. typos) could be "
-"merged with one Code-Review +2."
-
-msgid "We track our tasks on our StoryBoard_."
-msgstr "We track our tasks on our StoryBoard_."
-
-msgid ""
-"You found an issue and want to make sure we are aware of it? You can do so "
-"on our Storyboard_."
-msgstr ""
-"You found an issue and want to make sure we are aware of it? You can do so "
-"on our Storyboard_."
diff --git a/doc/source/locale/en_GB/LC_MESSAGES/doc-devref.po b/doc/source/locale/en_GB/LC_MESSAGES/doc-devref.po
deleted file mode 100644
index b84012a0cc..0000000000
--- a/doc/source/locale/en_GB/LC_MESSAGES/doc-devref.po
+++ /dev/null
@@ -1,1174 +0,0 @@
-# Andi Chandler <andi@gowling.com>, 2019. #zanata
-# Andi Chandler <andi@gowling.com>, 2020. #zanata
-# Andi Chandler <andi@gowling.com>, 2021. #zanata
-# Andi Chandler <andi@gowling.com>, 2022. #zanata
-msgid ""
-msgstr ""
-"Project-Id-Version: openstack-helm 0.1.1.dev3755\n"
-"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2022-05-25 23:10+0000\n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-"PO-Revision-Date: 2022-06-01 06:47+0000\n"
-"Last-Translator: Andi Chandler <andi@gowling.com>\n"
-"Language-Team: English (United Kingdom)\n"
-"Language: en_GB\n"
-"X-Generator: Zanata 4.3.3\n"
-"Plural-Forms: nplurals=2; plural=(n != 1)\n"
-
-msgid ""
-"**Note:** The values defined in a PodDisruptionBudget may conflict with "
-"other values that have been provided if an operator chooses to leverage "
-"Rolling Updates for deployments.  In the case where an operator defines a "
-"``maxUnavailable`` and ``maxSurge`` within an update strategy that is higher "
-"than a ``minAvailable`` within a pod disruption budget, a scenario may occur "
-"where pods fail to be evicted from a deployment."
-msgstr ""
-"**Note:** The values defined in a PodDisruptionBudget may conflict with "
-"other values that have been provided if an operator chooses to leverage "
-"Rolling Updates for deployments.  In the case where an operator defines a "
-"``maxUnavailable`` and ``maxSurge`` within an update strategy that is higher "
-"than a ``minAvailable`` within a pod disruption budget, a scenario may occur "
-"where pods fail to be evicted from a deployment."
-
-msgid ""
-":code:`neutron/templates/bin/_neutron-linuxbridge-agent-init.sh.tpl` is "
-"configuring the tunnel IP, external bridge and all bridge mappings defined "
-"in config. It is done in init container, and the IP for tunneling is shared "
-"using file :code:`/tmp/pod-shared/ml2-local-ip.ini` with main linuxbridge "
-"container."
-msgstr ""
-":code:`neutron/templates/bin/_neutron-linuxbridge-agent-init.sh.tpl` is "
-"configuring the tunnel IP, external bridge and all bridge mappings defined "
-"in config. It is done in init container, and the IP for tunnelling is shared "
-"using file :code:`/tmp/pod-shared/ml2-local-ip.ini` with main linuxbridge "
-"container."
-
-msgid ""
-"A detail worth mentioning is that ovs is configured to use sockets, rather "
-"than the default loopback mechanism."
-msgstr ""
-"A detail worth mentioning is that OVS is configured to use sockets, rather "
-"than the default loopback mechanism."
-
-msgid ""
-"A long-term goal, besides being image agnostic, is to also be able to "
-"support any of the container runtimes that Kubernetes supports, even those "
-"that might not use Docker's own packaging format. This will allow the "
-"project to continue to offer maximum flexibility with regard to operator "
-"choice."
-msgstr ""
-"A long-term goal, besides being image agnostic, is to also be able to "
-"support any of the container runtimes that Kubernetes supports, even those "
-"that might not use Docker's own packaging format. This will allow the "
-"project to continue to offer maximum flexibility with regard to operator "
-"choice."
-
-msgid ""
-"A typical Helm daemonset may leverage a secret to store configuration data. "
-"However, there are cases where the same secret document can't be used for "
-"the entire daemonset, because there are node-specific differences."
-msgstr ""
-"A typical Helm daemonset may leverage a secret to store configuration data. "
-"However, there are cases where the same secret document can't be used for "
-"the entire daemonset, because there are node-specific differences."
-
-msgid "Adapting your daemonset to support node/nodelabel overrides"
-msgstr "Adapting your daemonset to support node/nodelabel overrides"
-
-msgid ""
-"All ``Deployment`` chart components are outfitted by default with rolling "
-"update strategies:"
-msgstr ""
-"All ``Deployment`` chart components are outfitted by default with rolling "
-"update strategies:"
-
-msgid "All dependencies described in neutron-dhcp-agent are valid here."
-msgstr "All dependencies described in neutron-dhcp-agent are valid here."
-
-msgid ""
-"All of the above configs are endpoints or path to the specific class "
-"implementing the interface. You can see the endpoints to class mapping in "
-"`setup.cfg <https://github.com/openstack/neutron/"
-"blob/412c49b3930ce8aecb0a07aec50a9607058e5bc7/setup.cfg#L69>`_."
-msgstr ""
-"All of the above configs are endpoints or path to the specific class "
-"implementing the interface. You can see the endpoints to class mapping in "
-"`setup.cfg <https://github.com/openstack/neutron/"
-"blob/412c49b3930ce8aecb0a07aec50a9607058e5bc7/setup.cfg#L69>`_."
-
-msgid ""
-"Also note that other non-overridden values are inherited by hosts and labels "
-"with overrides. The following shows a set of example hosts and the values "
-"fed into each:"
-msgstr ""
-"Also note that other non-overridden values are inherited by hosts and labels "
-"with overrides. The following shows a set of example hosts and the values "
-"fed into each:"
-
-msgid ""
-"An illustrative example of an ``images:`` section taken from the heat chart:"
-msgstr ""
-"An illustrative example of an ``images:`` section taken from the heat chart:"
-
-msgid ""
-"Another place where the DHCP agent is dependent on L2 agent is the "
-"dependency for the L2 agent daemonset:"
-msgstr ""
-"Another place where the DHCP agent is dependent on L2 agent is the "
-"dependency for the L2 agent daemonset:"
-
-msgid ""
-"As Helm stands today, several issues exist when you update images within "
-"charts that might have been used by jobs that already ran to completion or "
-"are still in flight. An example of where this behavior would be desirable is "
-"when an updated db\\_sync image has updated to point from one openstack "
-"release to another. In this case, the operator will likely want a db\\_sync "
-"job, which was already run and completed during site installation, to run "
-"again with the updated image to bring the schema inline with the Newton "
-"release."
-msgstr ""
-"As Helm stands today, several issues exist when you update images within "
-"charts that might have been used by jobs that already ran to completion or "
-"are still in flight. An example of where this behaviour would be desirable "
-"is when an updated db\\_sync image has updated to point from one OpenStack "
-"release to another. In this case, the operator will likely want a db\\_sync "
-"job, which was already run and completed during site installation, to run "
-"again with the updated image to bring the schema inline with the Newton "
-"release."
-
-msgid ""
-"As an example, this line uses the ``endpoints.keystone_endpoint_uri_lookup`` "
-"macro in the ``helm-toolkit`` chart (since it is used by all charts). Note "
-"that there is a second convention here. All ``{{ define }}`` macros in "
-"charts should be pre-fixed with the chart that is defining them. This allows "
-"developers to easily identify the source of a Helm macro and also avoid "
-"namespace collisions. In the example above, the macro ``endpoints."
-"keystone_endpoint_uri_lookup`` is defined in the ``helm-toolkit`` chart. "
-"This macro is passing three parameters (aided by the ``tuple`` method built "
-"into the go/sprig templating library used by Helm):"
-msgstr ""
-"As an example, this line uses the ``endpoints.keystone_endpoint_uri_lookup`` "
-"macro in the ``helm-toolkit`` chart (since it is used by all charts). Note "
-"that there is a second convention here. All ``{{ define }}`` macros in "
-"charts should be pre-fixed with the chart that is defining them. This allows "
-"developers to easily identify the source of a Helm macro and also avoid "
-"namespace collisions. In the example above, the macro ``endpoints."
-"keystone_endpoint_uri_lookup`` is defined in the ``helm-toolkit`` chart. "
-"This macro is passing three parameters (aided by the ``tuple`` method built "
-"into the go/sprig templating library used by Helm):"
-
-msgid ""
-"As part of Neutron chart, this daemonset is running Neutron OVS agent. It is "
-"dependent on having :code:`openvswitch-db` and :code:`openvswitch-vswitchd` "
-"deployed and ready. Since its the default choice of the networking backend, "
-"all configuration is in place in `neutron/values.yaml`. :code:`neutron-ovs-"
-"agent` should not be deployed when another SDN is used in `network.backend`."
-msgstr ""
-"As part of Neutron chart, this daemonset is running Neutron OVS agent. It is "
-"dependent on having :code:`openvswitch-db` and :code:`openvswitch-vswitchd` "
-"deployed and ready. Since its the default choice of the networking backend, "
-"all configuration is in place in `neutron/values.yaml`. :code:`neutron-ovs-"
-"agent` should not be deployed when another SDN is used in `network.backend`."
-
-msgid "Assume the chart name is ``mychart``."
-msgstr "Assume the chart name is ``mychart``."
-
-msgid ""
-"By default, each endpoint is located in the same namespace as the current "
-"service's helm chart. To connect to a service which is running in a "
-"different Kubernetes namespace, a ``namespace`` can be provided for each "
-"individual endpoint."
-msgstr ""
-"By default, each endpoint is located in the same namespace as the current "
-"service's helm chart. To connect to a service which is running in a "
-"different Kubernetes namespace, a ``namespace`` can be provided for each "
-"individual endpoint."
-
-msgid ""
-"Charts should not use hard coded values such as ``http://keystone-api:5000`` "
-"because these are not compatible with operator overrides and do not support "
-"spreading components out over various namespaces."
-msgstr ""
-"Charts should not use hard coded values such as ``http://keystone-api:5000`` "
-"because these are not compatible with operator overrides and do not support "
-"spreading components out over various namespaces."
-
-msgid ""
-"Configuration of OVS bridges can be done via `neutron/templates/bin/_neutron-"
-"openvswitch-agent-init.sh.tpl`. The script is configuring the external "
-"network bridge and sets up any bridge mappings defined in :code:`conf."
-"auto_bridge_add`.  These values should align with :code:`conf.plugins."
-"openvswitch_agent.ovs.bridge_mappings`."
-msgstr ""
-"Configuration of OVS bridges can be done via `neutron/templates/bin/_neutron-"
-"openvswitch-agent-init.sh.tpl`. The script is configuring the external "
-"network bridge and sets up any bridge mappings defined in :code:`conf."
-"auto_bridge_add`.  These values should align with :code:`conf.plugins."
-"openvswitch_agent.ovs.bridge_mappings`."
-
-msgid ""
-"Configure neutron-server with SDN specific core_plugin/mechanism_drivers."
-msgstr ""
-"Configure neutron-server with SDN specific core_plugin/mechanism_drivers."
-
-msgid "Configuring network plugin"
-msgstr "Configuring network plugin"
-
-msgid ""
-"Consider the following (simplified) secret and daemonset pairing example:"
-msgstr ""
-"Consider the following (simplified) secret and daemonset pairing example:"
-
-msgid "Contents:"
-msgstr "Contents:"
-
-msgid "Create separate chart with new SDN deployment method."
-msgstr "Create separate chart with new SDN deployment method."
-
-msgid ""
-"Currently OpenStack-Helm supports OpenVSwitch and LinuxBridge as a network "
-"virtualization engines. In order to support many possible backends (SDNs), "
-"modular architecture of Neutron chart was developed. OpenStack-Helm can "
-"support every SDN solution that has Neutron plugin, either core_plugin or "
-"mechanism_driver."
-msgstr ""
-"Currently OpenStack-Helm supports OpenVSwitch and LinuxBridge as a network "
-"virtualisation engines. In order to support many possible backends (SDNs), "
-"modular architecture of Neutron chart was developed. OpenStack-Helm can "
-"support every SDN solution that has Neutron plugin, either core_plugin or "
-"mechanism_driver."
-
-msgid "DHCP - auto-assign IP address and DNS info"
-msgstr "DHCP - auto-assign IP address and DNS info"
-
-msgid ""
-"DHCP agent is running dnsmasq process which is serving the IP assignment and "
-"DNS info. DHCP agent is dependent on the L2 agent wiring the interface. So "
-"one should be aware that when changing the L2 agent, it also needs to be "
-"changed in the DHCP agent. The configuration of the DHCP agent includes "
-"option `interface_driver`, which will instruct how the tap interface created "
-"for serving the request should be wired."
-msgstr ""
-"DHCP agent is running dnsmasq process which is serving the IP assignment and "
-"DNS info. DHCP agent is dependent on the L2 agent wiring the interface. So "
-"one should be aware that when changing the L2 agent, it also needs to be "
-"changed in the DHCP agent. The configuration of the DHCP agent includes "
-"option `interface_driver`, which will instruct how the tap interface created "
-"for serving the request should be wired."
-
-msgid "Developer References"
-msgstr "Developer References"
-
-msgid ""
-"EFK (Elasticsearch, Fluent-bit & Fluentd, Kibana) based Logging Mechanism"
-msgstr ""
-"EFK (Elasticsearch, Fluent-bit & Fluentd, Kibana) based Logging Mechanism"
-
-msgid "Endpoints"
-msgstr "Endpoints"
-
-msgid "Exercising node/nodelabel overrides"
-msgstr "Exercising node/nodelabel overrides"
-
-msgid ""
-"Fluent-bit, Fluentd meet OpenStack-Helm's logging requirements for "
-"gathering, aggregating, and delivering of logged events. Fluent-bit runs as "
-"a daemonset on each node and mounts the `/var/lib/docker/containers` "
-"directory. The Docker container runtime engine directs events posted to "
-"stdout and stderr to this directory on the host. Fluent-bit then forward the "
-"contents of that directory to Fluentd. Fluentd runs as deployment at the "
-"designated nodes and expose service for Fluent-bit to forward logs. Fluentd "
-"should then apply the Logstash format to the logs. Fluentd can also write "
-"kubernetes and OpenStack metadata to the logs. Fluentd will then forward the "
-"results to Elasticsearch and to optionally Kafka. Elasticsearch indexes the "
-"logs in a logstash-* index by default. Kafka stores the logs in a ``logs`` "
-"topic by default. Any external tool can then consume the ``logs`` topic."
-msgstr ""
-"Fluent-bit, Fluentd meet OpenStack-Helm's logging requirements for "
-"gathering, aggregating, and delivering of logged events. Fluent-bit runs as "
-"a daemonset on each node and mounts the `/var/lib/docker/containers` "
-"directory. The Docker container runtime engine directs events posted to "
-"stdout and stderr to this directory on the host. Fluent-bit then forward the "
-"contents of that directory to Fluentd. Fluentd runs as deployment at the "
-"designated nodes and expose service for Fluent-bit to forward logs. Fluentd "
-"should then apply the Logstash format to the logs. Fluentd can also write "
-"kubernetes and OpenStack metadata to the logs. Fluentd will then forward the "
-"results to Elasticsearch and to optionally Kafka. Elasticsearch indexes the "
-"logs in a logstash-* index by default. Kafka stores the logs in a ``logs`` "
-"topic by default. Any external tool can then consume the ``logs`` topic."
-
-msgid ""
-"For example, if you have some special conf setting that should be applied to "
-"``host1.fqdn``, and another special conf setting that should be applied to "
-"nodes labeled with ``someNodeLabel``, then three secret/daemonset pairs will "
-"be generated and registered with kubernetes: one for ``host1.fqdn``, one for "
-"``someNodeLabel``, and one for ``default``."
-msgstr ""
-"For example, if you have some special conf setting that should be applied to "
-"``host1.fqdn``, and another special conf setting that should be applied to "
-"nodes labeled with ``someNodeLabel``, then three secret/daemonset pairs will "
-"be generated and registered with Kubernetes: one for ``host1.fqdn``, one for "
-"``someNodeLabel``, and one for ``default``."
-
-msgid ""
-"For instance, in the Neutron chart ``values.yaml`` the following endpoints "
-"are defined:"
-msgstr ""
-"For instance, in the Neutron chart ``values.yaml`` the following endpoints "
-"are defined:"
-
-msgid "Host overrides supercede label overrides"
-msgstr "Host overrides supersede label overrides"
-
-msgid ""
-"If :code:`.Values.manifests.daemonset_ovs_agent` will be set to false, "
-"neutron ovs agent would not be launched. In that matter, other type of L2 or "
-"L3 agent on compute node can be run."
-msgstr ""
-"If :code:`.Values.manifests.daemonset_ovs_agent` will be set to false, "
-"Neutron OVS agent would not be launched. In that matter, other type of L2 or "
-"L3 agent on compute node can be run."
-
-msgid ""
-"If a node matches more than one nodelabel, only the last matching nodelabel "
-"will apply (last in terms of the order the overrides are defined in the "
-"YAML)."
-msgstr ""
-"If a node matches more than one nodelabel, only the last matching nodelabel "
-"will apply (last in terms of the order the overrides are defined in the "
-"YAML)."
-
-msgid "If required, add new networking agent label type."
-msgstr "If required, add new networking agent label type."
-
-msgid ""
-"If the SDN implements its own version of L3 networking, neutron-l3-agent "
-"should not be started."
-msgstr ""
-"If the SDN implements its own version of L3 networking, neutron-l3-agent "
-"should not be started."
-
-msgid ""
-"If the SDN of your choice is using the ML2 core plugin, then the extra "
-"options in `neutron/ml2/plugins/ml2_conf.ini` should be configured:"
-msgstr ""
-"If the SDN of your choice is using the ML2 core plugin, then the extra "
-"options in `neutron/ml2/plugins/ml2_conf.ini` should be configured:"
-
-msgid ""
-"If there is no matching FQDN and no matching nodelabel, then the default "
-"daemonset/secret (with no overrides applied) is used."
-msgstr ""
-"If there is no matching FQDN and no matching nodelabel, then the default "
-"daemonset/secret (with no overrides applied) is used."
-
-msgid "Images"
-msgstr "Images"
-
-msgid "Implementation details of node/nodelabel overrides"
-msgstr "Implementation details of node/nodelabel overrides"
-
-msgid ""
-"In ``values.yaml`` in each chart, the same defaults are supplied in every "
-"chart, which allows the operator to override at upgrade or deployment time."
-msgstr ""
-"In ``values.yaml`` in each chart, the same defaults are supplied in every "
-"chart, which allows the operator to override at upgrade or deployment time."
-
-msgid ""
-"In order to add support for more SDNs, these steps need to be performed:"
-msgstr ""
-"In order to add support for more SDNs, these steps need to be performed:"
-
-msgid ""
-"In order to meet modularity criteria of Neutron chart, section `manifests` "
-"in :code:`neutron/values.yaml` contains boolean values describing which "
-"Neutron's Kubernetes resources should be deployed:"
-msgstr ""
-"In order to meet modularity criteria of Neutron chart, section `manifests` "
-"in :code:`neutron/values.yaml` contains boolean values describing which "
-"Neutron's Kubernetes resources should be deployed:"
-
-msgid ""
-"In order to use linuxbridge in your OpenStack-Helm deployment, you need to "
-"label the compute and controller/network nodes with `linuxbridge=enabled` "
-"and use this `neutron/values.yaml` override:"
-msgstr ""
-"In order to use linuxbridge in your OpenStack-Helm deployment, you need to "
-"label the compute and controller/network nodes with `linuxbridge=enabled` "
-"and use this `neutron/values.yaml` override:"
-
-msgid ""
-"Instead of having one daemonset with one monolithic secret, this helm-"
-"toolkit feature permits a common daemonset and secret template, from which "
-"daemonset and secret pairings are auto-generated. It supports establishing "
-"value overrides for nodes with specific label value pairs and for targeting "
-"nodes with specific hostnames and hostlabels. The overridden configuration "
-"is merged with the normal config data, with the override data taking "
-"precedence."
-msgstr ""
-"Instead of having one daemonset with one monolithic secret, this helm-"
-"toolkit feature permits a common daemonset and secret template, from which "
-"daemonset and secret pairings are auto-generated. It supports establishing "
-"value overrides for nodes with specific label value pairs and for targeting "
-"nodes with specific hostnames and hostlabels. The overridden configuration "
-"is merged with the normal config data, with the override data taking "
-"precedence."
-
-msgid ""
-"Introducing a new SDN solution should consider how the above services are "
-"provided. It maybe required to disable built-in Neutron functionality."
-msgstr ""
-"Introducing a new SDN solution should consider how the above services are "
-"provided. It maybe required to disable built-in Neutron functionality."
-
-msgid ""
-"L3 agent is serving the routing capabilities for Neutron networks. It is "
-"also dependent on the L2 agent wiring the tap interface for the routers."
-msgstr ""
-"L3 agent is serving the routing capabilities for Neutron networks. It is "
-"also dependent on the L2 agent wiring the tap interface for the routers."
-
-msgid "L3 routing - creation of routers"
-msgstr "L3 routing - creation of routers"
-
-msgid "Linuxbridge"
-msgstr "Linuxbridge"
-
-msgid ""
-"Linuxbridge is the second type of Neutron reference architecture L2 agent. "
-"It is running on nodes labeled `linuxbridge=enabled`. As mentioned before, "
-"all nodes that are requiring the L2 services need to be labeled with "
-"linuxbridge. This includes both the compute and controller/network nodes. It "
-"is not possible to label the same node with both openvswitch and linuxbridge "
-"(or any other network virtualization technology) at the same time."
-msgstr ""
-"Linuxbridge is the second type of Neutron reference architecture L2 agent. "
-"It is running on nodes labeled `linuxbridge=enabled`. As mentioned before, "
-"all nodes that are requiring the L2 services need to be labelled with "
-"linuxbridge. This includes both the compute and controller/network nodes. It "
-"is not possible to label the same node with both openvswitch and linuxbridge "
-"(or any other network virtualisation technology) at the same time."
-
-msgid "Logging Mechanism"
-msgstr "Logging Mechanism"
-
-msgid "Logging Requirements"
-msgstr "Logging Requirements"
-
-msgid "Metadata - Provide proxy for Nova metadata service"
-msgstr "Metadata - Provide proxy for Nova metadata service"
-
-msgid ""
-"Metadata-agent is a proxy to nova-metadata service. This one provides "
-"information about public IP, hostname, ssh keys, and any tenant specific "
-"information. The same dependencies apply for metadata as it is for DHCP and "
-"L3 agents. Other SDNs may require to force the config driver in nova, since "
-"the metadata service is not exposed by it."
-msgstr ""
-"Metadata-agent is a proxy to nova-metadata service. This one provides "
-"information about public IP, hostname, ssh keys, and any tenant specific "
-"information. The same dependencies apply for metadata as it is for DHCP and "
-"L3 agents. Other SDNs may require to force the config driver in Nova, since "
-"the metadata service is not exposed by it."
-
-msgid "Networking"
-msgstr "Networking"
-
-msgid "Neutron architecture"
-msgstr "Neutron architecture"
-
-msgid "Neutron chart includes the following services:"
-msgstr "Neutron chart includes the following services:"
-
-msgid ""
-"Neutron-server service is scheduled on nodes with `openstack-control-"
-"plane=enabled` label."
-msgstr ""
-"Neutron-server service is scheduled on nodes with `openstack-control-"
-"plane=enabled` label."
-
-msgid "Node and node label specific daemonset configurations"
-msgstr "Node and node label specific daemonset configurations"
-
-msgid "Note that only one set of overrides is applied per node, such that:"
-msgstr "Note that only one set of overrides is applied per node, such that:"
-
-msgid ""
-"Note that some additional values have been injected into the config file, "
-"this is performed via statements in the configmap template, which also calls "
-"the ``helm-toolkit.utils.to_oslo_conf`` to convert the yaml to the required "
-"layout:"
-msgstr ""
-"Note that some additional values have been injected into the config file, "
-"this is performed via statements in the configmap template, which also calls "
-"the ``helm-toolkit.utils.to_oslo_conf`` to convert the yaml to the required "
-"layout:"
-
-msgid ""
-"Note: Rolling update values can conflict with values defined in each "
-"service's PodDisruptionBudget.  See `here <https://docs.openstack.org/"
-"openstack-helm/latest/devref/pod-disruption-budgets.html>`_ for more "
-"information."
-msgstr ""
-"Note: Rolling update values can conflict with values defined in each "
-"service's PodDisruptionBudget.  See `here <https://docs.openstack.org/"
-"openstack-helm/latest/devref/pod-disruption-budgets.html>`_ for more "
-"information."
-
-msgid "Nova config dependency"
-msgstr "Nova config dependency"
-
-msgid "Nova vcpu example"
-msgstr "Nova vCPU example"
-
-msgid ""
-"Now we can wrap the existing YAML to make it support node and nodelabel "
-"overrides, with minimal changes to the existing YAML (note where $secretName "
-"has been substituted):"
-msgstr ""
-"Now we can wrap the existing YAML to make it support node and nodelabel "
-"overrides, with minimal changes to the existing YAML (note where $secretName "
-"has been substituted):"
-
-msgid "OSLO-Config Values"
-msgstr "OSLO-Config Values"
-
-msgid ""
-"OpenStack-Helm defines a centralized logging mechanism to provide insight "
-"into the state of the OpenStack services and infrastructure components as "
-"well as underlying Kubernetes platform. Among the requirements for a logging "
-"platform, where log data can come from and where log data need to be "
-"delivered are very variable. To support various logging scenarios, OpenStack-"
-"Helm should provide a flexible mechanism to meet with certain operation "
-"needs."
-msgstr ""
-"OpenStack-Helm defines a centralized logging mechanism to provide insight "
-"into the state of the OpenStack services and infrastructure components as "
-"well as underlying Kubernetes platform. Among the requirements for a logging "
-"platform, where log data can come from and where log data need to be "
-"delivered are very variable. To support various logging scenarios, OpenStack-"
-"Helm should provide a flexible mechanism to meet with certain operation "
-"needs."
-
-msgid ""
-"OpenStack-Helm generates oslo-config compatible formatted configuration "
-"files for services dynamically from values specified in a yaml tree. This "
-"allows operators to control any and all aspects of an OpenStack services "
-"configuration. An example snippet for an imaginary Keystone configuration is "
-"described here:"
-msgstr ""
-"OpenStack-Helm generates oslo-config compatible formatted configuration "
-"files for services dynamically from values specified in a yaml tree. This "
-"allows operators to control any and all aspects of an OpenStack services "
-"configuration. An example snippet for an imaginary Keystone configuration is "
-"described here:"
-
-msgid ""
-"OpenStack-Helm leverages PodDisruptionBudgets to enforce quotas that ensure "
-"that a certain number of replicas of a pod are available at any given time.  "
-"This is particularly important in the case when a Kubernetes node needs to "
-"be drained."
-msgstr ""
-"OpenStack-Helm leverages PodDisruptionBudgets to enforce quotas that ensure "
-"that a certain number of replicas of a pod are available at any given time.  "
-"This is particularly important in the case when a Kubernetes node needs to "
-"be drained."
-
-msgid ""
-"OpenStack-Helm provides fast and lightweight log forwarder and full featured "
-"log aggregator complementing each other providing a flexible and reliable "
-"solution. Especially, Fluent-bit is used as a log forwarder and Fluentd is "
-"used as a main log aggregator and processor."
-msgstr ""
-"OpenStack-Helm provides fast and lightweight log forwarder and full featured "
-"log aggregator complementing each other providing a flexible and reliable "
-"solution. Especially, Fluent-bit is used as a log forwarder and Fluentd is "
-"used as a main log aggregator and processor."
-
-msgid "OpenVSwitch"
-msgstr "OpenVSwitch"
-
-msgid "Other SDNs"
-msgstr "Other SDNs"
-
-msgid "Other networking services provided by Neutron are:"
-msgstr "Other networking services provided by Neutron are:"
-
-msgid "Pod Disruption Budgets"
-msgstr "Pod Disruption Budgets"
-
-msgid ""
-"SDNs implementing ML2 driver can add extra/plugin-specific configuration "
-"options in `neutron/ml2/plugins/ml2_conf.ini`. Or define its own "
-"`ml2_conf_<name>.ini` file where configs specific to the SDN would be placed."
-msgstr ""
-"SDNs implementing ML2 driver can add extra/plugin-specific configuration "
-"options in `neutron/ml2/plugins/ml2_conf.ini`. Or define its own "
-"`ml2_conf_<name>.ini` file where configs specific to the SDN would be placed."
-
-msgid ""
-"Script in :code:`neutron/templates/bin/_neutron-openvswitch-agent-init.sh."
-"tpl` is responsible for determining the tunnel interface and its IP for "
-"later usage by :code:`neutron-ovs-agent`. The IP is set in init container "
-"and shared between init container and main container with :code:`neutron-ovs-"
-"agent` via file :code:`/tmp/pod-shared/ml2-local-ip.ini`."
-msgstr ""
-"Script in :code:`neutron/templates/bin/_neutron-openvswitch-agent-init.sh."
-"tpl` is responsible for determining the tunnel interface and its IP for "
-"later usage by :code:`neutron-ovs-agent`. The IP is set in init container "
-"and shared between init container and main container with :code:`neutron-ovs-"
-"agent` via file :code:`/tmp/pod-shared/ml2-local-ip.ini`."
-
-msgid ""
-"Some nodes may have a different vcpu_pin_set in nova.conf due to differences "
-"in CPU hardware."
-msgstr ""
-"Some nodes may have a different vcpu_pin_set in nova.conf due to differences "
-"in CPU hardware."
-
-msgid ""
-"Specify if new SDN would like to use existing services from Neutron: L3, "
-"DHCP, metadata."
-msgstr ""
-"Specify if new SDN would like to use existing services from Neutron: L3, "
-"DHCP, metadata."
-
-msgid ""
-"The Neutron reference architecture provides mechanism_drivers :code:"
-"`OpenVSwitch` (OVS) and :code:`linuxbridge` (LB) with ML2 :code:"
-"`core_plugin` framework."
-msgstr ""
-"The Neutron reference architecture provides mechanism_drivers :code:"
-"`OpenVSwitch` (OVS) and :code:`linuxbridge` (LB) with ML2 :code:"
-"`core_plugin` framework."
-
-msgid ""
-"The OpenStack-Helm project also implements annotations across all chart "
-"configmaps so that changing resources inside containers, such as "
-"configuration files, triggers a Kubernetes rolling update. This means that "
-"those resources can be updated without deleting and redeploying the service "
-"and can be treated like any other upgrade, such as a container image change."
-msgstr ""
-"The OpenStack-Helm project also implements annotations across all chart "
-"configmaps so that changing resources inside containers, such as "
-"configuration files, triggers a Kubernetes rolling update. This means that "
-"those resources can be updated without deleting and redeploying the service "
-"and can be treated like any other upgrade, such as a container image change."
-
-msgid ""
-"The OpenStack-Helm project assumes all upgrades will be done through Helm. "
-"This includes handling several different resource types. First, changes to "
-"the Helm chart templates themselves are handled. Second, all of the "
-"resources layered on top of the container image, such as ``ConfigMaps`` "
-"which includes both scripts and configuration files, are updated during an "
-"upgrade. Finally, any image references will result in rolling updates of "
-"containers, replacing them with the updating image."
-msgstr ""
-"The OpenStack-Helm project assumes all upgrades will be done through Helm. "
-"This includes handling several different resource types. First, changes to "
-"the Helm chart templates themselves are handled. Second, all of the "
-"resources layered on top of the container image, such as ``ConfigMaps`` "
-"which includes both scripts and configuration files, are updated during an "
-"upgrade. Finally, any image references will result in rolling updates of "
-"containers, replacing them with the updating image."
-
-msgid ""
-"The OpenStack-Helm project today uses a mix of Docker images from "
-"Stackanetes and Kolla, but will likely standardize on a default set of "
-"images for all charts without any reliance on image-specific utilities."
-msgstr ""
-"The OpenStack-Helm project today uses a mix of Docker images from "
-"Stackanetes and Kolla, but will likely standardise on a default set of "
-"images for all charts without any reliance on image-specific utilities."
-
-msgid ""
-"The ``hash`` function defined in the ``helm-toolkit`` chart ensures that any "
-"change to any file referenced by configmap-bin.yaml or configmap-etc.yaml "
-"results in a new hash, which will then trigger a rolling update."
-msgstr ""
-"The ``hash`` function defined in the ``helm-toolkit`` chart ensures that any "
-"change to any file referenced by configmap-bin.yaml or configmap-etc.yaml "
-"results in a new hash, which will then trigger a rolling update."
-
-msgid "The above configuration options are handled by `neutron/values.yaml`:"
-msgstr "The above configuration options are handled by `neutron/values.yaml`:"
-
-msgid ""
-"The chart will then generate one daemonset for each host and label override, "
-"in addition to a default daemonset for which no overrides are applied. Each "
-"daemonset generated will also exclude from its scheduling criteria all other "
-"hosts and labels defined in other overrides for the same daemonset, to "
-"ensure that there is no overlap of daemonsets (i.e., one and only one "
-"daemonset of a given type for each node)."
-msgstr ""
-"The chart will then generate one daemonset for each host and label override, "
-"in addition to a default daemonset for which no overrides are applied. Each "
-"daemonset generated will also exclude from its scheduling criteria all other "
-"hosts and labels defined in other overrides for the same daemonset, to "
-"ensure that there is no overlap of daemonsets (i.e., one and only one "
-"daemonset of a given type for each node)."
-
-msgid ""
-"The farther down the list the label appears, the greater precedence it has. "
-"e.g., \"another-label\" overrides will apply to a node containing both "
-"labels."
-msgstr ""
-"The farther down the list the label appears, the greater precedence it has. "
-"e.g., \"another-label\" overrides will apply to a node containing both "
-"labels."
-
-msgid ""
-"The following example demonstrates how to exercise the node/nodelabel "
-"overrides:"
-msgstr ""
-"The following example demonstrates how to exercise the node/nodelabel "
-"overrides:"
-
-msgid ""
-"The following standards are in use today, in addition to any components "
-"defined by the service itself:"
-msgstr ""
-"The following standards are in use today, in addition to any components "
-"defined by the service itself:"
-
-msgid ""
-"The macros that help translate these into the actual URLs necessary are "
-"defined in the ``helm-toolkit`` chart. For instance, the cinder chart "
-"defines a ``glance_api_servers`` definition in the ``cinder.conf`` template:"
-msgstr ""
-"The macros that help translate these into the actual URLs necessary are "
-"defined in the ``helm-toolkit`` chart. For instance, the Cinder chart "
-"defines a ``glance_api_servers`` definition in the ``cinder.conf`` template:"
-
-msgid ""
-"The order of precedence for matches is FQDN, node label, and then default. "
-"If a node matches both a FQDN and a nodelabel, then only the FQDN override "
-"is applied. Pay special attention to adding FQDN overrides for nodes that "
-"match a nodelabel override, as you would need to duplicate the nodelabel "
-"overrides for that node in the FQDN overrides for them to still apply."
-msgstr ""
-"The order of precedence for matches is FQDN, node label, and then default. "
-"If a node matches both a FQDN and a nodelabel, then only the FQDN override "
-"is applied. Pay special attention to adding FQDN overrides for nodes that "
-"match a nodelabel override, as you would need to duplicate the nodelabel "
-"overrides for that node in the FQDN overrides for them to still apply."
-
-msgid ""
-"The ovs set of daemonsets are running on the node labeled "
-"`openvswitch=enabled`. This includes the compute and controller/network "
-"nodes. For more flexibility, OpenVSwitch as a tool was split out of Neutron "
-"chart, and put in separate chart dedicated OpenVSwitch. Neutron OVS agent "
-"remains in Neutron chart. Splitting out the OpenVSwitch creates "
-"possibilities to use it with different SDNs, adjusting the configuration "
-"accordingly."
-msgstr ""
-"The OVS set of daemonsets are running on the node labeled "
-"`openvswitch=enabled`. This includes the compute and controller/network "
-"nodes. For more flexibility, OpenVSwitch as a tool was split out of Neutron "
-"chart, and put in separate chart dedicated OpenVSwitch. Neutron OVS agent "
-"remains in Neutron chart. Splitting out the OpenVSwitch creates "
-"possibilities to use it with different SDNs, adjusting the configuration "
-"accordingly."
-
-msgid ""
-"The project's core philosophy regarding images is that the toolsets required "
-"to enable the OpenStack services should be applied by Kubernetes itself. "
-"This requires OpenStack-Helm to develop common and simple scripts with "
-"minimal dependencies that can be overlaid on any image that meets the "
-"OpenStack core library requirements. The advantage of this is that the "
-"project can be image agnostic, allowing operators to use Stackanetes, Kolla, "
-"LOCI, or any image flavor and format they choose and they will all function "
-"the same."
-msgstr ""
-"The project's core philosophy regarding images is that the toolsets required "
-"to enable the OpenStack services should be applied by Kubernetes itself. "
-"This requires OpenStack-Helm to develop common and simple scripts with "
-"minimal dependencies that can be overlaid on any image that meets the "
-"OpenStack core library requirements. The advantage of this is that the "
-"project can be image agnostic, allowing operators to use Stackanetes, Kolla, "
-"LOCI, or any image flavour and format they choose and they will all function "
-"the same."
-
-msgid ""
-"The project's goal is to provide a consistent mechanism for endpoints. "
-"OpenStack is a highly interconnected application, with various components "
-"requiring connectivity details to numerous services, including other "
-"OpenStack components and infrastructure elements such as databases, queues, "
-"and memcached infrastructure. The project's goal is to ensure that it can "
-"provide a consistent mechanism for defining these \"endpoints\" across all "
-"charts and provide the macros necessary to convert those definitions into "
-"usable endpoints. The charts should consistently default to building "
-"endpoints that assume the operator is leveraging all charts to build their "
-"OpenStack cloud. Endpoints should be configurable if an operator would like "
-"a chart to work with their existing infrastructure or run elements in "
-"different namespaces."
-msgstr ""
-"The project's goal is to provide a consistent mechanism for endpoints. "
-"OpenStack is a highly interconnected application, with various components "
-"requiring connectivity details to numerous services, including other "
-"OpenStack components and infrastructure elements such as databases, queues, "
-"and memcached infrastructure. The project's goal is to ensure that it can "
-"provide a consistent mechanism for defining these \"endpoints\" across all "
-"charts and provide the macros necessary to convert those definitions into "
-"usable endpoints. The charts should consistently default to building "
-"endpoints that assume the operator is leveraging all charts to build their "
-"OpenStack cloud. Endpoints should be configurable if an operator would like "
-"a chart to work with their existing infrastructure or run elements in "
-"different namespaces."
-
-msgid ""
-"The resulting logs can then be queried directly through Elasticsearch, or "
-"they can be viewed via Kibana. Kibana offers a dashboard that can create "
-"custom views on logged events, and Kibana integrates well with Elasticsearch "
-"by default."
-msgstr ""
-"The resulting logs can then be queried directly through Elasticsearch, or "
-"they can be viewed via Kibana. Kibana offers a dashboard that can create "
-"custom views on logged events, and Kibana integrates well with Elasticsearch "
-"by default."
-
-msgid ""
-"There is also a need for DHCP agent to pass ovs agent config file (in :code:"
-"`neutron/templates/bin/_neutron-dhcp-agent.sh.tpl`):"
-msgstr ""
-"There is also a need for DHCP agent to pass OVS agent config file (in :code:"
-"`neutron/templates/bin/_neutron-dhcp-agent.sh.tpl`):"
-
-msgid ""
-"These quotas are configurable by modifying the ``minAvailable`` field within "
-"each PodDisruptionBudget manifest, which is conveniently mapped to a "
-"templated variable inside the ``values.yaml`` file. The ``min_available`` "
-"within each service's ``values.yaml`` file can be represented by either a "
-"whole number, such as ``1``, or a percentage, such as ``80%``.  For example, "
-"when deploying 5 replicas of a pod (such as keystone-api), using "
-"``min_available: 3`` would enforce policy to ensure at least 3 replicas were "
-"running, whereas using ``min_available: 80%`` would ensure that 4 replicas "
-"of that pod are running."
-msgstr ""
-"These quotas are configurable by modifying the ``minAvailable`` field within "
-"each PodDisruptionBudget manifest, which is conveniently mapped to a "
-"templated variable inside the ``values.yaml`` file. The ``min_available`` "
-"within each service's ``values.yaml`` file can be represented by either a "
-"whole number, such as ``1``, or a percentage, such as ``80%``.  For example, "
-"when deploying 5 replicas of a pod (such as keystone-api), using "
-"``min_available: 3`` would enforce policy to ensure at least 3 replicas were "
-"running, whereas using ``min_available: 80%`` would ensure that 4 replicas "
-"of that pod are running."
-
-msgid ""
-"These values define all the endpoints that the Neutron chart may need in "
-"order to build full URL compatible endpoints to various services. Long-term, "
-"these will also include database, memcached, and rabbitmq elements in one "
-"place. Essentially, all external connectivity can be defined centrally."
-msgstr ""
-"These values define all the endpoints that the Neutron chart may need in "
-"order to build full URL compatible endpoints to various services. Long-term, "
-"these will also include database, memcached, and rabbitmq elements in one "
-"place. Essentially, all external connectivity can be defined centrally."
-
-msgid ""
-"This daemonset includes the linuxbridge Neutron agent with bridge-utils and "
-"ebtables utilities installed. This is all that is needed, since linuxbridge "
-"uses native kernel libraries."
-msgstr ""
-"This daemonset includes the linuxbridge Neutron agent with bridge-utils and "
-"ebtables utilities installed. This is all that is needed, since linuxbridge "
-"uses native kernel libraries."
-
-msgid "This is accomplished with the following annotation:"
-msgstr "This is accomplished with the following annotation:"
-
-msgid ""
-"This option will allow to configure the Neutron services in proper way, by "
-"checking what is the actual backed set in :code:`neutron/values.yaml`."
-msgstr ""
-"This option will allow to configure the Neutron services in proper way, by "
-"checking what is the actual backed set in :code:`neutron/values.yaml`."
-
-msgid ""
-"This requirement is OVS specific, the `ovsdb_connection` string is defined "
-"in `openvswitch_agent.ini` file, specifying how DHCP agent can connect to "
-"ovs. When using other SDNs, running the DHCP agent may not be required. When "
-"the SDN solution is addressing the IP assignments in another way, neutron's "
-"DHCP agent should be disabled."
-msgstr ""
-"This requirement is OVS specific, the `ovsdb_connection` string is defined "
-"in `openvswitch_agent.ini` file, specifying how DHCP agent can connect to "
-"ovs. When using other SDNs, running the DHCP agent may not be required. When "
-"the SDN solution is addressing the IP assignments in another way, neutron's "
-"DHCP agent should be disabled."
-
-msgid ""
-"This runs the OVS tool and database. OpenVSwitch chart is not Neutron "
-"specific, it may be used with other technologies that are leveraging the OVS "
-"technology, such as OVN or ODL."
-msgstr ""
-"This runs the OVS tool and database. OpenVSwitch chart is not Neutron "
-"specific, it may be used with other technologies that are leveraging the OVS "
-"technology, such as OVN or ODL."
-
-msgid ""
-"This will be consumed by the templated ``configmap-etc.yaml`` manifest to "
-"produce the following config file:"
-msgstr ""
-"This will be consumed by the templated ``configmap-etc.yaml`` manifest to "
-"produce the following config file:"
-
-msgid ""
-"To address this use-case, the ``helm-toolkit.utils.daemonset_overrides`` "
-"template was added in helm-toolkit. This was created with the intention that "
-"it should be straightforward to convert (wrap) a pre-existing daemonset with "
-"the functionality to override secret parameters on a per-node or per-"
-"nodelabel basis."
-msgstr ""
-"To address this use-case, the ``helm-toolkit.utils.daemonset_overrides`` "
-"template was added in helm-toolkit. This was created with the intention that "
-"it should be straightforward to convert (wrap) a pre-existing daemonset with "
-"the functionality to override secret parameters on a per-node or per-"
-"nodelabel basis."
-
-msgid ""
-"To address this, we can specify overrides in the values fed to the chart. Ex:"
-msgstr ""
-"To address this, we can specify overrides in the values fed to the chart. Ex:"
-
-msgid ""
-"To be able to configure multiple networking plugins inside of OpenStack-"
-"Helm, a new configuration option is added:"
-msgstr ""
-"To be able to configure multiple networking plugins inside of OpenStack-"
-"Helm, a new configuration option is added:"
-
-msgid ""
-"To enable new SDN solution, there should be separate chart created, which "
-"would handle the deployment of service, setting up the database and any "
-"related networking functionality that SDN is providing."
-msgstr ""
-"To enable new SDN solution, there should be separate chart created, which "
-"would handle the deployment of service, setting up the database and any "
-"related networking functionality that SDN is providing."
-
-msgid ""
-"To that end, all charts provide an ``images:`` section that allows operators "
-"to override images. Also, all default image references should be fully "
-"spelled out, even those hosted by Docker or Quay. Further, no default image "
-"reference should use ``:latest`` but rather should be pinned to a specific "
-"version to ensure consistent behavior for deployments over time."
-msgstr ""
-"To that end, all charts provide an ``images:`` section that allows operators "
-"to override images. Also, all default image references should be fully "
-"spelled out, even those hosted by Docker or Quay. Further, no default image "
-"reference should use ``:latest`` but rather should be pinned to a specific "
-"version to ensure consistent behaviour for deployments over time."
-
-msgid ""
-"To use other Neutron reference architecture types of SDN, these options "
-"should be configured in :code:`neutron.conf`:"
-msgstr ""
-"To use other Neutron reference architecture types of SDN, these options "
-"should be configured in :code:`neutron.conf`:"
-
-msgid ""
-"Today, the ``images:`` section has several common conventions. Most "
-"OpenStack services require a database initialization function, a database "
-"synchronization function, and a series of steps for Keystone registration "
-"and integration. Each component may also have a specific image that composes "
-"an OpenStack service. The images may or may not differ, but regardless, "
-"should all be defined in ``images``."
-msgstr ""
-"Today, the ``images:`` section has several common conventions. Most "
-"OpenStack services require a database initialization function, a database "
-"synchronization function, and a series of steps for Keystone registration "
-"and integration. Each component may also have a specific image that composes "
-"an OpenStack service. The images may or may not differ, but regardless, "
-"should all be defined in ``images``."
-
-msgid "Typical networking API request is an operation of create/update/delete:"
-msgstr ""
-"Typical networking API request is an operation of create/update/delete:"
-
-msgid "Upgrades and Reconfiguration"
-msgstr "Upgrades and Reconfiguration"
-
-msgid ""
-"Whenever we change the L2 agent, it should be reflected in ``nova/values."
-"yaml`` in dependency resolution for nova-compute."
-msgstr ""
-"Whenever we change the L2 agent, it should be reflected in ``nova/values."
-"yaml`` in dependency resolution for nova-compute."
-
-msgid ""
-"Your daemonset should now support node and nodelabl level overrides. (Note "
-"that you will also need your chart to have helm-toolkit listed as a "
-"dependency.)"
-msgstr ""
-"Your daemonset should now support node and nodelabel level overrides. (Note "
-"that you will also need your chart to have helm-toolkit listed as a "
-"dependency.)"
-
-msgid ""
-"``host1.fqdn`` with labels ``compute-type: dpdk, sriov`` and ``another-"
-"label: another-value``:"
-msgstr ""
-"``host1.fqdn`` with labels ``compute-type: dpdk, sriov`` and ``another-"
-"label: another-value``:"
-
-msgid ""
-"``host2.fqdn`` with labels ``compute-type: dpdk, sriov`` and ``another-"
-"label: another-value``:"
-msgstr ""
-"``host2.fqdn`` with labels ``compute-type: dpdk, sriov`` and ``another-"
-"label: another-value``:"
-
-msgid ""
-"``host3.fqdn`` with labels ``compute-type: dpdk, sriov`` and ``another-"
-"label: another-value``:"
-msgstr ""
-"``host3.fqdn`` with labels ``compute-type: dpdk, sriov`` and ``another-"
-"label: another-value``:"
-
-msgid "``host4.fqdn`` with labels ``compute-type: dpdk, sriov``:"
-msgstr "``host4.fqdn`` with labels ``compute-type: dpdk, sriov``:"
-
-msgid "``host5.fqdn`` with no labels:"
-msgstr "``host5.fqdn`` with no labels:"
-
-msgid "api: This is the port to map to for the service."
-msgstr "api: This is the port to map to for the service."
-
-msgid ""
-"db\\_drop: The image that will perform database deletion operations for the "
-"OpenStack service."
-msgstr ""
-"db\\_drop: The image that will perform database deletion operations for the "
-"OpenStack service."
-
-msgid ""
-"db\\_init: The image that will perform database creation operations for the "
-"OpenStack service."
-msgstr ""
-"db\\_init: The image that will perform database creation operations for the "
-"OpenStack service."
-
-msgid ""
-"db\\_sync: The image that will perform database sync (schema initialization "
-"and migration) for the OpenStack service."
-msgstr ""
-"db\\_sync: The image that will perform database sync (schema initialisation "
-"and migration) for the OpenStack service."
-
-msgid ""
-"dep\\_check: The image that will perform dependency checking in an init-"
-"container."
-msgstr ""
-"dep\\_check: The image that will perform dependency checking in an init-"
-"container."
-
-msgid ""
-"image: This is the OpenStack service that the endpoint is being built for. "
-"This will be mapped to ``glance`` which is the image service for OpenStack."
-msgstr ""
-"image: This is the OpenStack service that the endpoint is being built for. "
-"This will be mapped to ``glance`` which is the image service for OpenStack."
-
-msgid ""
-"internal: This is the OpenStack endpoint type we are looking for - valid "
-"values would be ``internal``, ``admin``, and ``public``"
-msgstr ""
-"internal: This is the OpenStack endpoint type we are looking for - valid "
-"values would be ``internal``, ``admin``, and ``public``"
-
-msgid ""
-"ks\\_endpoints: The image that will perform keystone endpoint registration "
-"for the service."
-msgstr ""
-"ks\\_endpoints: The image that will perform Keystone endpoint registration "
-"for the service."
-
-msgid ""
-"ks\\_service: The image that will perform keystone service registration for "
-"the service."
-msgstr ""
-"ks\\_service: The image that will perform Keystone service registration for "
-"the service."
-
-msgid ""
-"ks\\_user: The image that will perform keystone user creation for the "
-"service."
-msgstr ""
-"ks\\_user: The image that will perform Keystone user creation for the "
-"service."
-
-msgid "network"
-msgstr "network"
-
-msgid "neutron-dhcp-agent"
-msgstr "neutron-dhcp-agent"
-
-msgid ""
-"neutron-dhcp-agent service is scheduled to run on nodes with the label "
-"`openstack-control-plane=enabled`."
-msgstr ""
-"neutron-dhcp-agent service is scheduled to run on nodes with the label "
-"`openstack-control-plane=enabled`."
-
-msgid "neutron-l3-agent"
-msgstr "neutron-l3-agent"
-
-msgid ""
-"neutron-l3-agent service is scheduled to run on nodes with the label "
-"`openstack-control-plane=enabled`."
-msgstr ""
-"neutron-l3-agent service is scheduled to run on nodes with the label "
-"`openstack-control-plane=enabled`."
-
-msgid "neutron-lb-agent"
-msgstr "neutron-lb-agent"
-
-msgid "neutron-metadata-agent"
-msgstr "neutron-metadata-agent"
-
-msgid ""
-"neutron-metadata-agent service is scheduled to run on nodes with the label "
-"`openstack-control-plane=enabled`."
-msgstr ""
-"neutron-metadata-agent service is scheduled to run on nodes with the label "
-"`openstack-control-plane=enabled`."
-
-msgid "neutron-ovs-agent"
-msgstr "neutron-ovs-agent"
-
-msgid "neutron-server"
-msgstr "neutron-server"
-
-msgid ""
-"neutron-server is serving the networking REST API for operator and other "
-"OpenStack services usage. The internals of Neutron are highly flexible, "
-"providing plugin mechanisms for all networking services exposed. The "
-"consistent API is exposed to the user, but the internal implementation is up "
-"to the chosen SDN."
-msgstr ""
-"neutron-server is serving the networking REST API for operator and other "
-"OpenStack services usage. The internals of Neutron are highly flexible, "
-"providing plugin mechanisms for all networking services exposed. The "
-"consistent API is exposed to the user, but the internal implementation is up "
-"to the chosen SDN."
-
-msgid "openvswitch-db and openvswitch-vswitchd"
-msgstr "openvswitch-db and openvswitch-vswitchd"
-
-msgid "port"
-msgstr "port"
-
-msgid ""
-"pull\\_policy: The image pull policy, one of \"Always\", \"IfNotPresent\", "
-"and \"Never\" which will be used by all containers in the chart."
-msgstr ""
-"pull\\_policy: The image pull policy, one of \"Always\", \"IfNotPresent\", "
-"and \"Never\" which will be used by all containers in the chart."
-
-msgid "subnet"
-msgstr "subnet"
diff --git a/doc/source/locale/en_GB/LC_MESSAGES/doc-install.po b/doc/source/locale/en_GB/LC_MESSAGES/doc-install.po
deleted file mode 100644
index d1ac717c2b..0000000000
--- a/doc/source/locale/en_GB/LC_MESSAGES/doc-install.po
+++ /dev/null
@@ -1,1679 +0,0 @@
-# Andi Chandler <andi@gowling.com>, 2018. #zanata
-# Andi Chandler <andi@gowling.com>, 2020. #zanata
-# Andi Chandler <andi@gowling.com>, 2021. #zanata
-# Andi Chandler <andi@gowling.com>, 2022. #zanata
-msgid ""
-msgstr ""
-"Project-Id-Version: openstack-helm 0.1.1.dev3755\n"
-"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2022-05-25 23:10+0000\n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-"PO-Revision-Date: 2022-06-01 06:48+0000\n"
-"Last-Translator: Andi Chandler <andi@gowling.com>\n"
-"Language-Team: English (United Kingdom)\n"
-"Language: en_GB\n"
-"X-Generator: Zanata 4.3.3\n"
-"Plural-Forms: nplurals=2; plural=(n != 1)\n"
-
-msgid "**Check Chart Status**"
-msgstr "**Check Chart Status**"
-
-msgid ""
-"**First**, edit the ``values.yaml`` for Neutron, Glance, Horizon, Keystone, "
-"and Nova."
-msgstr ""
-"**First**, edit the ``values.yaml`` for Neutron, Glance, Horizon, Keystone, "
-"and Nova."
-
-msgid "**Review the Ingress configuration.**"
-msgstr "**Review the Ingress configuration.**"
-
-msgid ""
-"**Second** option would be as ``--set`` flags when calling ``helm install``"
-msgstr ""
-"**Second** option would be as ``--set`` flags when calling ``helm install``"
-
-msgid ""
-"**TaaS Agent, TaaS OVS Driver and TaaS SR-IOV Driver**: This forms the back-"
-"end of TaaS which runs as a ML2 agent extension on compute nodes. It handles "
-"the RPC calls made by TaaS Plugin and configures the mechanism driver, i.e. "
-"OpenVSwitch or SR-IOV Nic Switch."
-msgstr ""
-"**TaaS Agent, TaaS OVS Driver and TaaS SR-IOV Driver**: This forms the back-"
-"end of TaaS which runs as a ML2 agent extension on compute nodes. It handles "
-"the RPC calls made by TaaS Plugin and configures the mechanism driver, i.e. "
-"OpenVSwitch or SR-IOV Nic Switch."
-
-msgid ""
-"**TaaS Dashboard Plugin**: Horizon Plugin which adds GUI panels for TaaS "
-"resources in the Horizon Dashboard."
-msgstr ""
-"**TaaS Dashboard Plugin**: Horizon Plugin which adds GUI panels for TaaS "
-"resources in the Horizon Dashboard."
-
-msgid ""
-"**TaaS Plugin**: This is the front-end of TaaS which runs on controller node "
-"(Neutron server). This serves TaaS APIs and stores/retrieves TaaS "
-"configuration state to/from Neutron TaaS DB."
-msgstr ""
-"**TaaS Plugin**: This is the front-end of TaaS which runs on controller node "
-"(Neutron server). This serves TaaS APIs and stores/retrieves TaaS "
-"configuration state to/from Neutron TaaS DB."
-
-msgid "16GB of RAM"
-msgstr "16GB of RAM"
-
-msgid "4 Cores"
-msgstr "4 Cores"
-
-msgid "48GB HDD"
-msgstr "48GB HDD"
-
-msgid "8 Cores"
-msgstr "8 Cores"
-
-msgid "8GB of RAM"
-msgstr "8GB of RAM"
-
-msgid ""
-"A correct DPDK configuration depends heavily on the specific hardware "
-"resources and its configuration. Before deploying Openvswitch with DPDK, "
-"check the amount and type of available hugepages on the host OS."
-msgstr ""
-"A correct DPDK configuration depends heavily on the specific hardware "
-"resources and its configuration. Before deploying Openvswitch with DPDK, "
-"check the amount and type of available hugepages on the host OS."
-
-msgid "Activate the OpenStack namespace to be able to use Ceph"
-msgstr "Activate the OpenStack namespace to be able to use Ceph"
-
-msgid "Activate the openstack namespace to be able to use Ceph"
-msgstr "Activate the OpenStack namespace to be able to use Ceph"
-
-msgid ""
-"Add TaaS Dashboard dependency in ``requirements.txt`` file in ``openstack/"
-"horizon`` repo, i.e. https://opendev.org/openstack/horizon"
-msgstr ""
-"Add TaaS Dashboard dependency in ``requirements.txt`` file in ``openstack/"
-"horizon`` repo, i.e. https://opendev.org/openstack/horizon"
-
-msgid ""
-"Add TaaS and TaaS dashboard dependencies in :code:`upper-constraints.txt` "
-"file in :code:`openstack/requirements` repo, i.e. https://opendev.org/"
-"openstack/requirements"
-msgstr ""
-"Add TaaS and TaaS dashboard dependencies in :code:`upper-constraints.txt` "
-"file in :code:`openstack/requirements` repo, i.e. https://opendev.org/"
-"openstack/requirements"
-
-msgid ""
-"Add TaaS dependency in ``requirements.txt`` file in ``openstack/neutron`` "
-"repo, i.e. https://opendev.org/openstack/neutron"
-msgstr ""
-"Add TaaS dependency in ``requirements.txt`` file in ``openstack/neutron`` "
-"repo, i.e. https://opendev.org/openstack/neutron"
-
-msgid "Add TaaS panel to Horizon Dashboard:"
-msgstr "Add TaaS panel to Horizon Dashboard:"
-
-msgid ""
-"Add the address of the Kubernetes API, ``172.17.0.1``, and ``.svc.cluster."
-"local`` to your ``no_proxy`` and ``NO_PROXY`` environment variables."
-msgstr ""
-"Add the address of the Kubernetes API, ``172.17.0.1``, and ``.svc.cluster."
-"local`` to your ``no_proxy`` and ``NO_PROXY`` environment variables."
-
-msgid ""
-"Add to the Install steps these flags - also adding a shell environment "
-"variable to save on repeat code."
-msgstr ""
-"Add to the Install steps these flags - also adding a shell environment "
-"variable to save on repeat code."
-
-msgid "Adding a DPDK port to Openvswitch fails"
-msgstr "Adding a DPDK port to Openvswitch fails"
-
-msgid ""
-"Additional configuration variables can be found `here <https://github.com/"
-"openstack/openstack-helm-infra/blob/master/roles/deploy-kubeadm-aio-common/"
-"defaults/main.yml>`_. In particular, ``kubernetes_cluster_pod_subnet`` can "
-"be used to override the pod subnet set up by Calico (the default container "
-"SDN), if you have a preexisting network that conflicts with the default pod "
-"subnet of 192.168.0.0/16."
-msgstr ""
-"Additional configuration variables can be found `here <https://github.com/"
-"openstack/openstack-helm-infra/blob/master/roles/deploy-kubeadm-aio-common/"
-"defaults/main.yml>`_. In particular, ``kubernetes_cluster_pod_subnet`` can "
-"be used to override the pod subnet set up by Calico (the default container "
-"SDN), if you have a preexisting network that conflicts with the default pod "
-"subnet of 192.168.0.0/16."
-
-msgid ""
-"Additional information on Kubernetes Ceph-based integration can be found in "
-"the documentation for the `CephFS <https://github.com/kubernetes-incubator/"
-"external-storage/blob/master/ceph/cephfs/README.md>`_ and `RBD <https://"
-"github.com/kubernetes-incubator/external-storage/blob/master/ceph/rbd/README."
-"md>`_ storage provisioners, as well as for the alternative `NFS <https://"
-"github.com/kubernetes-incubator/external-storage/blob/master/nfs/README."
-"md>`_ provisioner."
-msgstr ""
-"Additional information on Kubernetes Ceph-based integration can be found in "
-"the documentation for the `CephFS <https://github.com/kubernetes-incubator/"
-"external-storage/blob/master/ceph/cephfs/README.md>`_ and `RBD <https://"
-"github.com/kubernetes-incubator/external-storage/blob/master/ceph/rbd/README."
-"md>`_ storage provisioners, as well as for the alternative `NFS <https://"
-"github.com/kubernetes-incubator/external-storage/blob/master/nfs/README."
-"md>`_ provisioner."
-
-msgid ""
-"Additionally, the default configuration of the neutron chart must be adapted "
-"according to the underlying hardware. The corresponding configuration "
-"parameter is labeled with \"CHANGE-ME\" in the script \"values_overrides/"
-"dpdk.yaml\". Specifically, the \"ovs_dpdk\" configuration section should "
-"list all NICs which should be bound to DPDK with their corresponding PCI-"
-"IDs. Moreover, the name of each NIC needs to be unique, e.g., dpdk0, dpdk1, "
-"etc."
-msgstr ""
-"Additionally, the default configuration of the neutron chart must be adapted "
-"according to the underlying hardware. The corresponding configuration "
-"parameter is labeled with \"CHANGE-ME\" in the script \"values_overrides/"
-"dpdk.yaml\". Specifically, the \"ovs_dpdk\" configuration section should "
-"list all NICs which should be bound to DPDK with their corresponding PCI-"
-"IDs. Moreover, the name of each NIC needs to be unique, e.g., dpdk0, dpdk1, "
-"etc."
-
-msgid ""
-"After making the configuration changes, run a ``make`` and then install as "
-"you would from AIO or MultiNode instructions."
-msgstr ""
-"After making the configuration changes, run a ``make`` and then install as "
-"you would from AIO or MultiNode instructions."
-
-msgid ""
-"All commands below should be run as a normal user, not as root. Appropriate "
-"versions of Docker, Kubernetes, and Helm will be installed by the playbooks "
-"used below, so there's no need to install them ahead of time."
-msgstr ""
-"All commands below should be run as a normal user, not as root. Appropriate "
-"versions of Docker, Kubernetes, and Helm will be installed by the playbooks "
-"used below, so there's no need to install them ahead of time."
-
-msgid ""
-"Alternatively, these steps can be performed by running the script directly::"
-msgstr ""
-"Alternatively, these steps can be performed by running the script directly::"
-
-msgid ""
-"Alternatively, this step can be performed by running the script directly:"
-msgstr ""
-"Alternatively, this step can be performed by running the script directly:"
-
-msgid ""
-"An Ingress is a collection of rules that allow inbound connections to reach "
-"the cluster services."
-msgstr ""
-"An Ingress is a collection of rules that allow inbound connections to reach "
-"the cluster services."
-
-msgid ""
-"Apart from the variables above with gerrit refspec values, additionally "
-"export following environment variables with values as applicable:"
-msgstr ""
-"Apart from the variables above with gerrit refspec values, additionally "
-"export following environment variables with values as applicable:"
-
-msgid ""
-"As a final validation step, re-run the **openstack helm stack list** and "
-"**openstack helm keypair list** commands and confirm the returned results "
-"are shown as empty.::"
-msgstr ""
-"As a final validation step, re-run the **openstack helm stack list** and "
-"**openstack helm keypair list** commands and confirm the returned results "
-"are shown as empty.::"
-
-msgid ""
-"As any other Neutron plugin, TaaS neutron plugin functionality consists of "
-"following modules:"
-msgstr ""
-"As any other Neutron plugin, TaaS neutron plugin functionality consists of "
-"following modules:"
-
-msgid ""
-"Before deploying TaaS and/or TaaS Dashboard, it needs to be added in Neutron "
-"and/or Horizon LOCI images."
-msgstr ""
-"Before deploying TaaS and/or TaaS Dashboard, it needs to be added in Neutron "
-"and/or Horizon LOCI images."
-
-msgid ""
-"Below are some instructions and suggestions to help you get started with a "
-"Kubeadm All-in-One environment on Ubuntu 18.04. Other supported versions of "
-"Linux can also be used, with the appropriate changes to package installation."
-msgstr ""
-"Below are some instructions and suggestions to help you get started with a "
-"Kubeadm All-in-One environment on Ubuntu 18.04. Other supported versions of "
-"Linux can also be used, with the appropriate changes to package installation."
-
-msgid "Build the requirements LOCI image using above commit"
-msgstr "Build the requirements LOCI image using above commit"
-
-msgid ""
-"By default OSH will use Google DNS Server IPs (8.8.8.8, 8.8.4.4) and will "
-"update resolv.conf as a result. If those IPs are blocked by your proxy, "
-"running the OSH scripts will result in the inability to connect to anything "
-"on the network. These DNS nameserver entries can be changed by updating the "
-"external_dns_nameservers entry in the file ``openstack-helm-infra/tools/"
-"images/kubeadm-aio/assets/opt/playbooks/vars.yaml``."
-msgstr ""
-"By default OSH will use Google DNS Server IPs (8.8.8.8, 8.8.4.4) and will "
-"update resolv.conf as a result. If those IPs are blocked by your proxy, "
-"running the OSH scripts will result in the inability to connect to anything "
-"on the network. These DNS nameserver entries can be changed by updating the "
-"external_dns_nameservers entry in the file ``openstack-helm-infra/tools/"
-"images/kubeadm-aio/assets/opt/playbooks/vars.yaml``."
-
-msgid ""
-"By default the Calico CNI will use ``192.168.0.0/16`` and Kubernetes "
-"services will use ``10.96.0.0/16`` as the CIDR for services. Check that "
-"these CIDRs are not in use on the development node before proceeding, or "
-"adjust as required."
-msgstr ""
-"By default the Calico CNI will use ``192.168.0.0/16`` and Kubernetes "
-"services will use ``10.96.0.0/16`` as the CIDR for services. Check that "
-"these CIDRs are not in use on the development node before proceeding, or "
-"adjust as required."
-
-msgid ""
-"By default, this installation will use Google DNS Server IPs (8.8.8.8, "
-"8.8.4.4) and will update resolv.conf as a result. If those IPs are blocked "
-"by the proxy, this will overwrite the original DNS entries and result in the "
-"inability to connect to anything on the network behind the proxy. These DNS "
-"nameserver entries can be changed by updating the "
-"``external_dns_nameservers`` entry in this file:"
-msgstr ""
-"By default, this installation will use Google DNS Server IPs (8.8.8.8, "
-"8.8.4.4) and will update resolv.conf as a result. If those IPs are blocked "
-"by the proxy, this will overwrite the original DNS entries and result in the "
-"inability to connect to anything on the network behind the proxy. These DNS "
-"nameserver entries can be changed by updating the "
-"``external_dns_nameservers`` entry in this file:"
-
-msgid "Cleaning the Deployment"
-msgstr "Cleaning the Deployment"
-
-msgid "Clone the OpenStack-Helm Repos"
-msgstr "Clone the OpenStack-Helm Repos"
-
-msgid "Code examples below."
-msgstr "Code examples below."
-
-msgid "Common Deployment Requirements"
-msgstr "Common Deployment Requirements"
-
-msgid "Configure OpenStack"
-msgstr "Configure OpenStack"
-
-msgid "Configure TaaS in Neutron chart"
-msgstr "Configure TaaS in Neutron chart"
-
-msgid ""
-"Configuring OpenStack for a particular production use-case is beyond the "
-"scope of this guide. Please refer to the OpenStack `Configuration <https://"
-"docs.openstack.org/latest/configuration/>`_ documentation for your selected "
-"version of OpenStack to determine what additional values overrides should be "
-"provided to the OpenStack-Helm charts to ensure appropriate networking, "
-"security, etc. is in place."
-msgstr ""
-"Configuring OpenStack for a particular production use-case is beyond the "
-"scope of this guide. Please refer to the OpenStack `Configuration <https://"
-"docs.openstack.org/latest/configuration/>`_ documentation for your selected "
-"version of OpenStack to determine what additional values overrides should be "
-"provided to the OpenStack-Helm charts to ensure appropriate networking, "
-"security, etc. is in place."
-
-msgid "Contents:"
-msgstr "Contents:"
-
-msgid ""
-"Copy the key: ``sudo cp ~/.ssh/id_rsa /etc/openstack-helm/deploy-key.pem``"
-msgstr ""
-"Copy the key: ``sudo cp ~/.ssh/id_rsa /etc/openstack-helm/deploy-key.pem``"
-
-msgid "Create a patchset for ``openstack/horizon`` repo"
-msgstr "Create a patchset for ``openstack/horizon`` repo"
-
-msgid "Create a patchset for ``openstack/neutron`` repo"
-msgstr "Create a patchset for ``openstack/neutron`` repo"
-
-msgid "Create a patchset for ``openstack/requirements`` repo"
-msgstr "Create a patchset for ``openstack/requirements`` repo"
-
-msgid "Create an environment file"
-msgstr "Create an environment file"
-
-msgid "Create an inventory file"
-msgstr "Create an inventory file"
-
-msgid ""
-"Create an ssh-key on the master node, and add the public key to each node "
-"that you intend to join the cluster."
-msgstr ""
-"Create an ssh-key on the master node, and add the public key to each node "
-"that you intend to join the cluster."
-
-msgid "Create loopback devices for CEPH"
-msgstr "Create loopback devices for CEPH"
-
-msgid ""
-"Create two loopback devices for ceph as one disk for OSD data and other disk "
-"for block DB and block WAL. If loop0 and loop1  devices are busy in your "
-"case , feel free to change them in parameters by using --ceph-osd-data and --"
-"ceph-osd-dbwal options."
-msgstr ""
-"Create two loopback devices for Ceph as one disk for OSD data and other disk "
-"for block DB and block WAL. If loop0 and loop1  devices are busy in your "
-"case , feel free to change them in parameters by using --ceph-osd-data and --"
-"ceph-osd-dbwal options."
-
-msgid ""
-"Default log level for Neutron TaaS is :code:`INFO`. For changing it, "
-"override following parameter:"
-msgstr ""
-"Default log level for Neutron TaaS is :code:`INFO`. For changing it, "
-"override following parameter:"
-
-msgid "Delete the keypair(s) returned from the list command above::"
-msgstr "Delete the keypair(s) returned from the list command above::"
-
-msgid ""
-"Delete the stacks returned from the *openstack helm stack list* command "
-"above::"
-msgstr ""
-"Delete the stacks returned from the *openstack helm stack list* command "
-"above::"
-
-msgid ""
-"Depending on your specific proxy, https_proxy may be the same as http_proxy. "
-"Refer to your specific proxy documentation."
-msgstr ""
-"Depending on your specific proxy, https_proxy may be the same as http_proxy. "
-"Refer to your specific proxy documentation."
-
-msgid "Deploy Barbican"
-msgstr "Deploy Barbican"
-
-msgid "Deploy Ceph"
-msgstr "Deploy Ceph"
-
-msgid "Deploy Cinder"
-msgstr "Deploy Cinder"
-
-msgid "Deploy Compute Kit (Nova and Neutron)"
-msgstr "Deploy Compute Kit (Nova and Neutron)"
-
-msgid "Deploy Glance"
-msgstr "Deploy Glance"
-
-msgid "Deploy Heat"
-msgstr "Deploy Heat"
-
-msgid "Deploy Horizon"
-msgstr "Deploy Horizon"
-
-msgid "Deploy Keystone"
-msgstr "Deploy Keystone"
-
-msgid "Deploy Kubernetes & Helm"
-msgstr "Deploy Kubernetes & Helm"
-
-msgid "Deploy Libvirt"
-msgstr "Deploy Libvirt"
-
-msgid "Deploy MariaDB"
-msgstr "Deploy MariaDB"
-
-msgid "Deploy Memcached"
-msgstr "Deploy Memcached"
-
-msgid "Deploy NFS Provisioner"
-msgstr "Deploy NFS Provisioner"
-
-msgid "Deploy OVS-DPDK"
-msgstr "Deploy OVS-DPDK"
-
-msgid "Deploy OpenStack-Helm"
-msgstr "Deploy OpenStack-Helm"
-
-msgid "Deploy OpenvSwitch"
-msgstr "Deploy OpenvSwitch"
-
-msgid "Deploy RabbitMQ"
-msgstr "Deploy RabbitMQ"
-
-msgid "Deploy Rados Gateway for object store"
-msgstr "Deploy Rados Gateway for object store"
-
-msgid "Deploy TaaS Dashboard Plugin"
-msgstr "Deploy TaaS Dashboard Plugin"
-
-msgid "Deploy TaaS Plugin"
-msgstr "Deploy TaaS Plugin"
-
-msgid "Deploy tap-as-a-service (TaaS) Neutron / Dashboard plugin"
-msgstr "Deploy tap-as-a-service (TaaS) Neutron / Dashboard plugin"
-
-msgid "Deploy the ingress controller"
-msgstr "Deploy the ingress controller"
-
-msgid "Deployment"
-msgstr "Deployment"
-
-msgid "Deployment With Ceph"
-msgstr "Deployment With Ceph"
-
-msgid "Deployment With NFS"
-msgstr "Deployment With NFS"
-
-msgid "Deployment with Tungsten Fabric"
-msgstr "Deployment with Tungsten Fabric"
-
-msgid "Development"
-msgstr "Development"
-
-msgid "Environment tear-down"
-msgstr "Environment tear-down"
-
-msgid ""
-"Essentially the use of Ingress for OpenStack-Helm is an Nginx proxy service. "
-"Ingress (Nginx) is accessible by your cluster public IP - e.g. the IP "
-"associated with ``kubectl get pods -o wide --all-namespaces | grep ingress-"
-"api`` Ingress/Nginx will be listening for server name requests of \"keystone"
-"\" or \"keystone.openstack\" and will route those requests to the proper "
-"internal K8s Services. These public listeners in Ingress must match the "
-"external DNS that you will set up to access your OpenStack deployment. Note "
-"each rule also has a Service that directs Ingress Controllers allow access "
-"to the endpoints from within the cluster."
-msgstr ""
-"Essentially the use of Ingress for OpenStack-Helm is an Nginx proxy service. "
-"Ingress (Nginx) is accessible by your cluster public IP - e.g. the IP "
-"associated with ``kubectl get pods -o wide --all-namespaces | grep ingress-"
-"api`` Ingress/Nginx will be listening for server name requests of \"keystone"
-"\" or \"keystone.openstack\" and will route those requests to the proper "
-"internal K8s Services. These public listeners in Ingress must match the "
-"external DNS that you will set up to access your OpenStack deployment. Note "
-"each rule also has a Service that directs Ingress Controllers allow access "
-"to the endpoints from within the cluster."
-
-msgid "Examples"
-msgstr "Examples"
-
-msgid ""
-"Execution of the **900-use-it.sh** script results in the creation of 4 heat "
-"stacks and a unique keypair enabling access to a newly created VM.  "
-"Subsequent runs of the **900-use-it.sh** script requires deletion of the "
-"stacks, a keypair, and key files, generated during the initial script "
-"execution."
-msgstr ""
-"Execution of the **900-use-it.sh** script results in the creation of 4 heat "
-"stacks and a unique keypair enabling access to a newly created VM.  "
-"Subsequent runs of the **900-use-it.sh** script requires deletion of the "
-"stacks, a keypair, and key files, generated during the initial script "
-"execution."
-
-msgid "Exercise the Cloud"
-msgstr "Exercise the Cloud"
-
-msgid "External DNS and FQDN"
-msgstr "External DNS and FQDN"
-
-msgid "External DNS to FQDN/Ingress"
-msgstr "External DNS to FQDN/Ingress"
-
-msgid ""
-"First you have to set up OpenStack and Linux versions and install needed "
-"packages"
-msgstr ""
-"First you have to set up OpenStack and Linux versions and install needed "
-"packages"
-
-msgid ""
-"For ``identity`` and ``dashboard`` at ``host_fdqn_override.public`` replace "
-"``null`` with the value as ``keystone.os.foo.org`` and ``horizon.os.foo.org``"
-msgstr ""
-"For ``identity`` and ``dashboard`` at ``host_fdqn_override.public`` replace "
-"``null`` with the value as ``keystone.os.foo.org`` and ``horizon.os.foo.org``"
-
-msgid ""
-"For a deployment without cinder and horizon the system requirements are:"
-msgstr ""
-"For a deployment without Cinder and Horizon the system requirements are:"
-
-msgid ""
-"For a lab or proof-of-concept environment, the OpenStack-Helm gate scripts "
-"can be used to quickly deploy a multinode Kubernetes cluster using KubeADM "
-"and Ansible. Please refer to the deployment guide `here <./kubernetes-gate."
-"html>`__."
-msgstr ""
-"For a lab or proof-of-concept environment, the OpenStack-Helm gate scripts "
-"can be used to quickly deploy a multinode Kubernetes cluster using KubeADM "
-"and Ansible. Please refer to the deployment guide `here <./kubernetes-gate."
-"html>`__."
-
-msgid ""
-"For example if gerrit refspec for this commit is \"refs/changes/xx/xxxxxx/x"
-"\", so export the :code:`REQUIREMENTS_REF_SPEC` variable as follows:"
-msgstr ""
-"For example if gerrit refspec for this commit is \"refs/changes/xx/xxxxxx/x"
-"\", so export the :code:`REQUIREMENTS_REF_SPEC` variable as follows:"
-
-msgid ""
-"For example if gerrit refspec for this commit is \"refs/changes/xx/xxxxxx/x"
-"\"; so export the :code:`HORIZON_REF_SPEC` variable as follows:"
-msgstr ""
-"For example if gerrit refspec for this commit is \"refs/changes/xx/xxxxxx/x"
-"\"; so export the :code:`HORIZON_REF_SPEC` variable as follows:"
-
-msgid ""
-"For example if gerrit refspec for this commit is \"refs/changes/xx/xxxxxx/x"
-"\"; so export the :code:`NEUTRON_REF_SPEC` variable as follows:"
-msgstr ""
-"For example if gerrit refspec for this commit is \"refs/changes/xx/xxxxxx/x"
-"\"; so export the :code:`NEUTRON_REF_SPEC` variable as follows:"
-
-msgid "For more details, refer to TaaS specification: Tap-as-a-service_."
-msgstr "For more details, refer to TaaS specification: Tap-as-a-service_."
-
-msgid ""
-"For other deployment options, select appropriate ``Deployment with ...`` "
-"option from `Index <../developer/index.html>`__ page."
-msgstr ""
-"For other deployment options, select appropriate ``Deployment with ...`` "
-"option from `Index <../developer/index.html>`__ page."
-
-msgid "Gate-Based Kubernetes"
-msgstr "Gate-Based Kubernetes"
-
-msgid "Get the Nginx configuration from the Ingress Pod:"
-msgstr "Get the Nginx configuration from the Ingress Pod:"
-
-msgid "Get the ``helm status`` of your chart."
-msgstr "Get the ``helm status`` of your chart."
-
-msgid "Helm Chart Installation"
-msgstr "Helm Chart Installation"
-
-msgid "Host Configuration"
-msgstr "Host Configuration"
-
-msgid "Host Proxy & DNS Configuration"
-msgstr "Host Proxy & DNS Configuration"
-
-msgid ""
-"If OVS fails to start up because of no hugepages are available, check the "
-"configuration of the OVS daemonset. Older versions of helm-toolkit were not "
-"able to render hugepage configuration into the Kubernetes manifest and just "
-"removed the hugepage attributes. If no hugepage configuration is defined for "
-"the OVS daemonset, consider using a newer version of helm-toolkit."
-msgstr ""
-"If OVS fails to start up because of no hugepages are available, check the "
-"configuration of the OVS daemonset. Older versions of helm-toolkit were not "
-"able to render hugepage configuration into the Kubernetes manifest and just "
-"removed the hugepage attributes. If no hugepage configuration is defined for "
-"the OVS daemonset, consider using a newer version of helm-toolkit."
-
-msgid ""
-"If doing an `AIO install <https://docs.openstack.org/openstack-helm/latest/"
-"install/developer/index.html>`__, all the ``--set`` flags"
-msgstr ""
-"If doing an `AIO install <https://docs.openstack.org/openstack-helm/latest/"
-"install/developer/index.html>`__, all the ``--set`` flags"
-
-msgid ""
-"If you are not deploying OSH behind a proxy, skip this step and continue "
-"with \"Deploy Kubernetes & Helm\"."
-msgstr ""
-"If you are not deploying OSH behind a proxy, skip this step and continue "
-"with \"Deploy Kubernetes & Helm\"."
-
-msgid "If you are not deploying OSH behind a proxy, skip this step."
-msgstr "If you are not deploying OSH behind a proxy, skip this step."
-
-msgid ""
-"Implementing the FQDN overrides **must** be done at install time. If you run "
-"these as helm upgrades, Ingress will notice the updates though none of the "
-"endpoint build-out jobs will run again, unless they are cleaned up manually "
-"or using a tool like Armada."
-msgstr ""
-"Implementing the FQDN overrides **must** be done at install time. If you run "
-"these as helm upgrades, Ingress will notice the updates though none of the "
-"endpoint build-out jobs will run again, unless they are cleaned up manually "
-"or using a tool like Armada."
-
-msgid ""
-"In order to access your OpenStack deployment on Kubernetes we can use the "
-"Ingress Controller or NodePorts to provide a pathway in. A background on "
-"Ingress, OpenStack-Helm fully qualified domain name (FQDN) overrides, "
-"installation, examples, and troubleshooting will be discussed here."
-msgstr ""
-"In order to access your OpenStack deployment on Kubernetes we can use the "
-"Ingress Controller or NodePorts to provide a pathway in. A background on "
-"Ingress, OpenStack-Helm fully qualified domain name (FQDN) overrides, "
-"installation, examples, and troubleshooting will be discussed here."
-
-msgid ""
-"In order to allow OVS inside a pod to make use of hugepages, the "
-"corresponding type and amount of hugepages must be specified in the resource "
-"section of the OVS chart's values.yaml:"
-msgstr ""
-"In order to allow OVS inside a pod to make use of hugepages, the "
-"corresponding type and amount of hugepages must be specified in the resource "
-"section of the OVS chart's values.yaml:"
-
-msgid ""
-"In order to deploy OSH behind a proxy, add the following entries to "
-"``openstack-helm-infra/tools/gate/devel/local-vars.yaml``:"
-msgstr ""
-"In order to deploy OSH behind a proxy, add the following entries to "
-"``openstack-helm-infra/tools/gate/devel/local-vars.yaml``:"
-
-msgid ""
-"In order to deploy OpenStack-Helm behind corporate proxy servers, add the "
-"following entries to ``openstack-helm-infra/tools/gate/devel/local-vars."
-"yaml``."
-msgstr ""
-"In order to deploy OpenStack-Helm behind corporate proxy servers, add the "
-"following entries to ``openstack-helm-infra/tools/gate/devel/local-vars."
-"yaml``."
-
-msgid ""
-"In order to drive towards a production-ready OpenStack solution, our goal is "
-"to provide containerized, yet stable `persistent volumes <https://kubernetes."
-"io/docs/concepts/storage/persistent-volumes/>`_ that Kubernetes can use to "
-"schedule applications that require state, such as MariaDB (Galera). Although "
-"we assume that the project should provide a \"batteries included\" approach "
-"towards persistent storage, we want to allow operators to define their own "
-"solution as well. Examples of this work will be documented in another "
-"section, however evidence of this is found throughout the project. If you "
-"find any issues or gaps, please create a `story <https://storyboard."
-"openstack.org/#!/project/886>`_ to track what can be done to improve our "
-"documentation."
-msgstr ""
-"In order to drive towards a production-ready OpenStack solution, our goal is "
-"to provide containerized, yet stable `persistent volumes <https://kubernetes."
-"io/docs/concepts/storage/persistent-volumes/>`_ that Kubernetes can use to "
-"schedule applications that require state, such as MariaDB (Galera). Although "
-"we assume that the project should provide a \"batteries included\" approach "
-"towards persistent storage, we want to allow operators to define their own "
-"solution as well. Examples of this work will be documented in another "
-"section, however evidence of this is found throughout the project. If you "
-"find any issues or gaps, please create a `story <https://storyboard."
-"openstack.org/#!/project/886>`_ to track what can be done to improve our "
-"documentation."
-
-msgid ""
-"In the example above, bonding isn't used and hence an empty list is passed "
-"in the \"bonds\" section."
-msgstr ""
-"In the example above, bonding isn't used and hence an empty list is passed "
-"in the \"bonds\" section."
-
-msgid ""
-"In this example, 8 hugepages of 1G size have been allocated. 2 of those are "
-"being used and 6 are still available."
-msgstr ""
-"In this example, 8 hugepages of 1G size have been allocated. 2 of those are "
-"being used and 6 are still available."
-
-msgid ""
-"In this example, the NIC with PCI-ID 0000:00:04.0 is connected to NUMA "
-"socket 1. As a result, this NIC can only be used by OVS if"
-msgstr ""
-"In this example, the NIC with PCI-ID 0000:00:04.0 is connected to NUMA "
-"socket 1. As a result, this NIC can only be used by OVS if"
-
-msgid "Ingress"
-msgstr "Ingress"
-
-msgid "Install Basic Utilities"
-msgstr "Install Basic Utilities"
-
-msgid "Install OpenStack packages"
-msgstr "Install OpenStack packages"
-
-msgid "Install OpenStack-Helm"
-msgstr "Install OpenStack-Helm"
-
-msgid "Install k8s Minikube"
-msgstr "Install k8s Minikube"
-
-msgid "Installation"
-msgstr "Installation"
-
-msgid "Intro"
-msgstr "Intro"
-
-msgid ""
-"It can be configured to give services externally-reachable URLs, load "
-"balance traffic, terminate SSL, offer name based virtual hosting, and more."
-msgstr ""
-"It can be configured to give services externally-reachable URLs, load "
-"balance traffic, terminate SSL, offer name based virtual hosting, and more."
-
-msgid ""
-"It is recommended to add your own existing DNS nameserver entries to avoid "
-"losing connection."
-msgstr ""
-"It is recommended to add your own existing DNS nameserver entries to avoid "
-"losing connection."
-
-msgid "Kubernetes Preparation"
-msgstr "Kubernetes Preparation"
-
-msgid "Kubernetes and Common Setup"
-msgstr "Kubernetes and Common Setup"
-
-msgid "Latest Version Installs"
-msgstr "Latest Version Installs"
-
-msgid "List the keypair(s) generated during the script execution::"
-msgstr "List the keypair(s) generated during the script execution::"
-
-msgid ""
-"List the stacks created during script execution which will need to be "
-"deleted::"
-msgstr ""
-"List the stacks created during script execution which will need to be "
-"deleted::"
-
-msgid ""
-"Look for *server* configuration with a *server_name* matching your desired "
-"FQDN"
-msgstr ""
-"Look for *server* configuration with a *server_name* matching your desired "
-"FQDN"
-
-msgid ""
-"Managing and configuring a Kubernetes cluster is beyond the scope of "
-"OpenStack-Helm and this guide."
-msgstr ""
-"Managing and configuring a Kubernetes cluster is beyond the scope of "
-"OpenStack-Helm and this guide."
-
-msgid ""
-"Manually remove the keypair directories created from the script in the ~/."
-"ssh directory::"
-msgstr ""
-"Manually remove the keypair directories created from the script in the ~/."
-"ssh directory::"
-
-msgid ""
-"Many of the default container images that are referenced across OpenStack-"
-"Helm charts are not intended for production use; for example, while LOCI and "
-"Kolla can be used to produce production-grade images, their public reference "
-"images are not prod-grade.  In addition, some of the default images use "
-"``latest`` or ``master`` tags, which are moving targets and can lead to "
-"unpredictable behavior.  For production-like deployments, we recommend "
-"building custom images, or at minimum caching a set of known images, and "
-"incorporating them into OpenStack-Helm via values overrides."
-msgstr ""
-"Many of the default container images that are referenced across OpenStack-"
-"Helm charts are not intended for production use; for example, while LOCI and "
-"Kolla can be used to produce production-grade images, their public reference "
-"images are not prod-grade.  In addition, some of the default images use "
-"``latest`` or ``master`` tags, which are moving targets and can lead to "
-"unpredictable behavior.  For production-like deployments, we recommend "
-"building custom images, or at minimum caching a set of known images, and "
-"incorporating them into OpenStack-Helm via values overrides."
-
-msgid ""
-"More information can be found in the `Openvswitch documentation <http://docs."
-"openvswitch.org/en/latest/intro/install/dpdk/>`_."
-msgstr ""
-"More information can be found in the `Openvswitch documentation <http://docs."
-"openvswitch.org/en/latest/intro/install/dpdk/>`_."
-
-msgid ""
-"More information on how to allocate and configure hugepages on the host OS "
-"can be found in the `Openvswitch documentation <http://docs.openvswitch.org/"
-"en/latest/intro/install/dpdk/>`_."
-msgstr ""
-"More information on how to allocate and configure hugepages on the host OS "
-"can be found in the `Openvswitch documentation <http://docs.openvswitch.org/"
-"en/latest/intro/install/dpdk/>`_."
-
-msgid "Multinode"
-msgstr "Multinode"
-
-msgid "Neutron TaaS Architecture"
-msgstr "Neutron TaaS Architecture"
-
-msgid "Neutron TaaS support in Openstack-Helm commits:"
-msgstr "Neutron TaaS support in Openstack-Helm commits:"
-
-msgid "Neutron and Horizon LOCI images"
-msgstr "Neutron and Horizon LOCI images"
-
-msgid ""
-"Note if you need to make a DNS change, you will have to do uninstall (``helm "
-"delete <chart>``) and install again."
-msgstr ""
-"Note if you need to make a DNS change, you will have to do uninstall (``helm "
-"delete <chart>``) and install again."
-
-msgid ""
-"Note that this command will only enable you to auth successfully using the "
-"``python-openstackclient`` CLI. To use legacy clients like the ``python-"
-"novaclient`` from the CLI, reference the auth values in ``/etc/openstack/"
-"clouds.yaml`` and run::"
-msgstr ""
-"Note that this command will only enable you to auth successfully using the "
-"``python-openstackclient`` CLI. To use legacy clients like the ``python-"
-"novaclient`` from the CLI, reference the auth values in ``/etc/openstack/"
-"clouds.yaml`` and run::"
-
-msgid "OSH Proxy & DNS Configuration"
-msgstr "OSH Proxy & DNS Configuration"
-
-msgid ""
-"OSH runs updates for local apt packages, so we will need to set the proxy "
-"for apt as well by adding these lines to `/etc/apt/apt.conf`:"
-msgstr ""
-"OSH runs updates for local apt packages, so we will need to set the proxy "
-"for apt as well by adding these lines to `/etc/apt/apt.conf`:"
-
-msgid "OVS startup failure"
-msgstr "OVS startup failure"
-
-msgid ""
-"On the host or master node, install the latest versions of Git, CA Certs & "
-"Make if necessary"
-msgstr ""
-"On the host or master node, install the latest versions of Git, CA Certs & "
-"Make if necessary"
-
-msgid "On the master node create an environment file for the cluster:"
-msgstr "On the master node create an environment file for the cluster:"
-
-msgid "On the master node create an inventory file for the cluster:"
-msgstr "On the master node create an inventory file for the cluster:"
-
-msgid "On the master node run the playbooks:"
-msgstr "On the master node run the playbooks:"
-
-msgid "On the worker nodes:"
-msgstr "On the worker nodes:"
-
-msgid ""
-"Once OpenStack-Helm has been deployed, the cloud can be exercised either "
-"with the OpenStack client, or the same heat templates that are used in the "
-"validation gates."
-msgstr ""
-"Once OpenStack-Helm has been deployed, the cloud can be exercised either "
-"with the OpenStack client, or the same Heat templates that are used in the "
-"validation gates."
-
-msgid ""
-"Once installed, access the API's or Dashboard at `http://horizon.os.foo.org`"
-msgstr ""
-"Once installed, access the API's or Dashboard at `http://horizon.os.foo.org`"
-
-msgid ""
-"Once the above requirements are met, start deploying Openstack Helm using "
-"the deployment scripts under the dpdk directory in an increasing order"
-msgstr ""
-"Once the above requirements are met, start deploying Openstack Helm using "
-"the deployment scripts under the dpdk directory in an increasing order"
-
-msgid ""
-"Once the host has been configured the repos containing the OpenStack-Helm "
-"charts should be cloned onto each node in the cluster:"
-msgstr ""
-"Once the host has been configured the repos containing the OpenStack-Helm "
-"charts should be cloned onto each node in the cluster:"
-
-msgid ""
-"Once the host has been configured the repos containing the OpenStack-Helm "
-"charts should be cloned:"
-msgstr ""
-"Once the host has been configured the repos containing the OpenStack-Helm "
-"charts should be cloned:"
-
-msgid ""
-"One can also specify the name of Openstack release and container OS "
-"distribution as overrides before running the deployment scripts, for "
-"instance,"
-msgstr ""
-"One can also specify the name of Openstack release and container OS "
-"distribution as overrides before running the deployment scripts, for "
-"instance,"
-
-msgid ""
-"OpenStack-Helm uses the hosts networking namespace for many pods including, "
-"Ceph, Neutron and Nova components. For this, to function, as expected pods "
-"need to be able to resolve DNS requests correctly. Ubuntu Desktop and some "
-"other distributions make use of ``mdns4_minimal`` which does not operate as "
-"Kubernetes expects with its default TLD of ``.local``. To operate at "
-"expected either change the ``hosts`` line in the ``/etc/nsswitch.conf``, or "
-"confirm that it matches:"
-msgstr ""
-"OpenStack-Helm uses the hosts networking namespace for many pods including, "
-"Ceph, Neutron and Nova components. For this, to function, as expected pods "
-"need to be able to resolve DNS requests correctly. Ubuntu Desktop and some "
-"other distributions make use of ``mdns4_minimal`` which does not operate as "
-"Kubernetes expects with its default TLD of ``.local``. To operate at "
-"expected either change the ``hosts`` line in the ``/etc/nsswitch.conf``, or "
-"confirm that it matches:"
-
-msgid ""
-"OpenStack-Helm utilizes the `Kubernetes Ingress Controller <https://"
-"kubernetes.io/docs/concepts/services-networking/ingress/>`__"
-msgstr ""
-"OpenStack-Helm utilises the `Kubernetes Ingress Controller <https://"
-"kubernetes.io/docs/concepts/services-networking/ingress/>`__"
-
-msgid "OpenStack-Helm-Infra KubeADM deployment"
-msgstr "OpenStack-Helm-Infra KubeADM deployment"
-
-msgid ""
-"Other versions and considerations (such as other CNI SDN providers), config "
-"map data, and value overrides will be included in other documentation as we "
-"explore these options further."
-msgstr ""
-"Other versions and considerations (such as other CNI SDN providers), config "
-"map data, and value overrides will be included in other documentation as we "
-"explore these options further."
-
-msgid "Override images in Neutron chart"
-msgstr "Override images in Neutron chart"
-
-msgid ""
-"Override the :code:`images` section parameters for Neutron chart with the "
-"custom LOCI image's tag, prepared as explained in above sections."
-msgstr ""
-"Override the :code:`images` section parameters for Neutron chart with the "
-"custom LOCI image's tag, prepared as explained in above sections."
-
-msgid "Overview"
-msgstr "Overview"
-
-msgid "PMD threads have been assigned to NUMA socket 1."
-msgstr "PMD threads have been assigned to NUMA socket 1."
-
-msgid "Passwordless Sudo"
-msgstr "Passwordless Sudo"
-
-msgid ""
-"Please see the supported application versions outlined in the `source "
-"variable file <https://github.com/openstack/openstack-helm-infra/blob/master/"
-"roles/build-images/defaults/main.yml>`_."
-msgstr ""
-"Please see the supported application versions outlined in the `source "
-"variable file <https://github.com/openstack/openstack-helm-infra/blob/master/"
-"roles/build-images/defaults/main.yml>`_."
-
-msgid "Plugins"
-msgstr "Plugins"
-
-msgid "Prepare LOCI images"
-msgstr "Prepare LOCI images"
-
-msgid ""
-"Prepare Neutron or Horizon LOCI image using this requirements image as :code:"
-"`docker build --build-arg WHEELS` command argument."
-msgstr ""
-"Prepare Neutron or Horizon LOCI image using this requirements image as :code:"
-"`docker build --build-arg WHEELS` command argument."
-
-msgid ""
-"Prepare a requirements LOCI image with Neutron TaaS and TaaS Dashboard code "
-"installed."
-msgstr ""
-"Prepare a requirements LOCI image with Neutron TaaS and TaaS Dashboard code "
-"installed."
-
-msgid ""
-"Prepare ahead of time your FQDN and DNS layouts. There are a handful of "
-"OpenStack endpoints you will want to expose for API and Dashboard access."
-msgstr ""
-"Prepare ahead of time your FQDN and DNS layouts. There are a handful of "
-"OpenStack endpoints you will want to expose for API and Dashboard access."
-
-msgid "Prepare host"
-msgstr "Prepare host"
-
-msgid "Prepare host and openstack helm for tf"
-msgstr "Prepare host and OpenStack Helm for tf"
-
-msgid "Proxy Configuration"
-msgstr "Proxy Configuration"
-
-msgid "Putting it all together"
-msgstr "Putting it all together"
-
-msgid "References"
-msgstr "References"
-
-msgid "Removing Helm Charts"
-msgstr "Removing Helm Charts"
-
-msgid "Requirements"
-msgstr "Requirements"
-
-msgid "Requirements LOCI image"
-msgstr "Requirements LOCI image"
-
-msgid "Requirements and Host Configuration"
-msgstr "Requirements and Host Configuration"
-
-msgid "Run the playbooks"
-msgstr "Run the playbooks"
-
-msgid "SSH-Key preparation"
-msgstr "SSH-Key preparation"
-
-msgid ""
-"Set correct ownership: ``sudo chown ubuntu /etc/openstack-helm/deploy-key."
-"pem``"
-msgstr ""
-"Set correct ownership: ``sudo chown ubuntu /etc/openstack-helm/deploy-key."
-"pem``"
-
-msgid "Set log level for TaaS"
-msgstr "Set log level for TaaS"
-
-msgid ""
-"Set your local environment variables to use the proxy information. This "
-"involves adding or setting the following values in ``/etc/environment``:"
-msgstr ""
-"Set your local environment variables to use the proxy information. This "
-"involves adding or setting the following values in ``/etc/environment``:"
-
-msgid "Setup Clients on the host and assemble the charts"
-msgstr "Setup Clients on the host and assemble the charts"
-
-msgid "Setup DNS for use cluster DNS"
-msgstr "Setup DNS for use cluster DNS"
-
-msgid "Setup Glance"
-msgstr "Setup Glance"
-
-msgid "Setup Heat"
-msgstr "Setup Heat"
-
-msgid "Setup Ingress"
-msgstr "Setup Ingress"
-
-msgid "Setup Keystone"
-msgstr "Setup Keystone"
-
-msgid "Setup MariaDB"
-msgstr "Setup MariaDB"
-
-msgid "Setup Memcached"
-msgstr "Setup Memcached"
-
-msgid "Setup NFS"
-msgstr "Setup NFS"
-
-msgid "Setup Neutron and Nova"
-msgstr "Setup Neutron and Nova"
-
-msgid "Setup OpenStack client"
-msgstr "Setup OpenStack client"
-
-msgid "Setup RabbitMQ"
-msgstr "Setup RabbitMQ"
-
-msgid "Setup Tungsten Fabric"
-msgstr "Setup Tungsten Fabric"
-
-msgid "Setup env for apply values_overrides"
-msgstr "Setup env for apply values_overrides"
-
-msgid "Setup libvirt"
-msgstr "Setup libvirt"
-
-msgid "Setup the gateway to the public network"
-msgstr "Setup the gateway to the public network"
-
-msgid "Subsequent Runs & Post Clean-up"
-msgstr "Subsequent Runs & Post Clean-up"
-
-msgid "System Requirements"
-msgstr "System Requirements"
-
-msgid "TaaS Architecture"
-msgstr "TaaS Architecture"
-
-msgid ""
-"TaaS dashboard plugin can be deployed simply by using custom LOCI images "
-"having TaaS Dashboard code installed (as explained in above sections), i.e. "
-"override the :code:`images` section parameters for Horizon charts:"
-msgstr ""
-"TaaS dashboard plugin can be deployed simply by using custom LOCI images "
-"having TaaS Dashboard code installed (as explained in above sections), i.e. "
-"override the :code:`images` section parameters for Horizon charts:"
-
-msgid ""
-"TaaS plugin provides a mechanism to mirror certain traffic (for example "
-"tagged with specific VLANs) from a source VM to any traffic analyzer VM. "
-"When packet will be forwarded, the original value of source and target ip/"
-"ports information will not be altered and the system administrator will be "
-"able to run, for ex. tcpdump, on the target VM to trace these packets."
-msgstr ""
-"TaaS plugin provides a mechanism to mirror certain traffic (for example "
-"tagged with specific VLANs) from a source VM to any traffic analyser VM. "
-"When packet will be forwarded, the original value of source and target ip/"
-"ports information will not be altered and the system administrator will be "
-"able to run, for ex. tcpdump, on the target VM to trace these packets."
-
-msgid ""
-"Test this by ssh'ing to a node and then executing a command with 'sudo'. "
-"Neither operation should require a password."
-msgstr ""
-"Test this by ssh'ing to a node and then executing a command with 'sudo'. "
-"Neither operation should require a password."
-
-msgid ""
-"The NUMA socket a given NIC is connected to can be found in the ovs-vswitchd "
-"log:"
-msgstr ""
-"The NUMA socket a given NIC is connected to can be found in the ovs-vswitchd "
-"log:"
-
-msgid ""
-"The OpenStack clients and Kubernetes RBAC rules, along with assembly of the "
-"charts can be performed by running the following commands:"
-msgstr ""
-"The OpenStack clients and Kubernetes RBAC rules, along with assembly of the "
-"charts can be performed by running the following commands:"
-
-msgid ""
-"The `./tools/deployment/multinode/kube-node-subnet.sh` script requires "
-"docker to run."
-msgstr ""
-"The `./tools/deployment/multinode/kube-node-subnet.sh` script requires "
-"docker to run."
-
-msgid ""
-"The ``.svc.cluster.local`` address is required to allow the OpenStack client "
-"to communicate without being routed through proxy servers. The IP address "
-"``172.17.0.1`` is the advertised IP address for the Kubernetes API server. "
-"Replace the addresses if your configuration does not match the one defined "
-"above."
-msgstr ""
-"The ``.svc.cluster.local`` address is required to allow the OpenStack client "
-"to communicate without being routed through proxy servers. The IP address "
-"``172.17.0.1`` is the advertised IP address for the Kubernetes API server. "
-"Replace the addresses if your configuration does not match the one defined "
-"above."
-
-msgid "The default FQDN's for OpenStack-Helm are"
-msgstr "The default FQDN's for OpenStack-Helm are"
-
-msgid ""
-"The example above uses the default values used by ``openstack-helm-infra``."
-msgstr ""
-"The example above uses the default values used by ``openstack-helm-infra``."
-
-msgid ""
-"The following commands all assume that they are run from the ``/opt/"
-"openstack-helm`` directory."
-msgstr ""
-"The following commands all assume that they are run from the ``/opt/"
-"openstack-helm`` directory."
-
-msgid ""
-"The following commands all assume that they are run from the ``openstack-"
-"helm`` directory and the repos have been cloned as above."
-msgstr ""
-"The following commands all assume that they are run from the ``openstack-"
-"helm`` directory and the repos have been cloned as above."
-
-msgid ""
-"The following steps serve as a guide to clean-up the client environment by "
-"deleting stacks and respective artifacts created during the **900-use-it."
-"sh** script:"
-msgstr ""
-"The following steps serve as a guide to clean-up the client environment by "
-"deleting stacks and respective artefacts created during the **900-use-it."
-"sh** script:"
-
-msgid ""
-"The installation procedures below, will take an administrator from a new "
-"``kubeadm`` installation to OpenStack-Helm deployment."
-msgstr ""
-"The installation procedures below, will take an administrator from a new "
-"``kubeadm`` installation to OpenStack-Helm deployment."
-
-msgid ""
-"The mapping of CPU cores to NUMA sockets can be determined by means of "
-"``lspci``, for instance:"
-msgstr ""
-"The mapping of CPU cores to NUMA sockets can be determined by means of "
-"``lspci``, for instance:"
-
-msgid "The recommended minimum system requirements for a full deployment are:"
-msgstr "The recommended minimum system requirements for a full deployment are:"
-
-msgid ""
-"The script below configures Ceph to use loopback devices created in previous "
-"step as backend for ceph osds. To configure a custom block device-based "
-"backend, please refer to the ``ceph-osd`` `values.yaml <https://github.com/"
-"openstack/openstack-helm/blob/master/ceph-osd/values.yaml>`_."
-msgstr ""
-"The script below configures Ceph to use loopback devices created in previous "
-"step as backend for ceph osds. To configure a custom block device-based "
-"backend, please refer to the ``ceph-osd`` `values.yaml <https://github.com/"
-"openstack/openstack-helm/blob/master/ceph-osd/values.yaml>`_."
-
-msgid ""
-"The upstream Ceph image repository does not currently pin tags to specific "
-"Ceph point releases.  This can lead to unpredictable results in long-lived "
-"deployments.  In production scenarios, we strongly recommend overriding the "
-"Ceph images to use either custom built images or controlled, cached images."
-msgstr ""
-"The upstream Ceph image repository does not currently pin tags to specific "
-"Ceph point releases.  This can lead to unpredictable results in long-lived "
-"deployments.  In production scenarios, we strongly recommend overriding the "
-"Ceph images to use either custom built images or controlled, cached images."
-
-msgid ""
-"These commands will restore the environment back to a clean Kubernetes "
-"deployment, that can either be manually removed or over-written by "
-"restarting the deployment process. It is recommended to restart the host "
-"before doing so to ensure any residual state, eg. Network interfaces are "
-"removed."
-msgstr ""
-"These commands will restore the environment back to a clean Kubernetes "
-"deployment, that can either be manually removed or over-written by "
-"restarting the deployment process. It is recommended to restart the host "
-"before doing so to ensure any residual state, eg. Network interfaces are "
-"removed."
-
-msgid "These values can be retrieved by running:"
-msgstr "These values can be retrieved by running:"
-
-msgid ""
-"This command will deploy a single node minikube cluster. This will use the "
-"parameters in ``${OSH_INFRA_PATH}/playbooks/vars.yaml`` to control the "
-"deployment, which can be over-ridden by adding entries to ``"
-"${OSH_INFRA_PATH}/tools/gate/devel/local-vars.yaml``."
-msgstr ""
-"This command will deploy a single node minikube cluster. This will use the "
-"parameters in ``${OSH_INFRA_PATH}/playbooks/vars.yaml`` to control the "
-"deployment, which can be over-ridden by adding entries to ``"
-"${OSH_INFRA_PATH}/tools/gate/devel/local-vars.yaml``."
-
-msgid ""
-"This guide assumes that users wishing to deploy behind a proxy have already "
-"defined the conventional proxy environment variables ``http_proxy``, "
-"``https_proxy``, and ``no_proxy``."
-msgstr ""
-"This guide assumes that users wishing to deploy behind a proxy have already "
-"defined the conventional proxy environment variables ``http_proxy``, "
-"``https_proxy``, and ``no_proxy``."
-
-msgid "This guide covers the minimum number of requirements to get started."
-msgstr "This guide covers the minimum number of requirements to get started."
-
-msgid ""
-"This guide explains how to deploy tap-as-a-service (TaaS) Neutron plugin and "
-"TaaS Dashboard plugin in Neutron and Horizon charts respectively."
-msgstr ""
-"This guide explains how to deploy tap-as-a-service (TaaS) Neutron plugin and "
-"TaaS Dashboard plugin in Neutron and Horizon charts respectively."
-
-msgid ""
-"This installation, by default will use Google DNS servers, 8.8.8.8 or "
-"8.8.4.4 and updates resolv.conf. These DNS nameserver entries can be changed "
-"by updating file ``/opt/openstack-helm-infra/tools/images/kubeadm-aio/assets/"
-"opt/playbooks/vars.yaml`` under section ``external_dns_nameservers``. This "
-"change must be done on each node in your cluster."
-msgstr ""
-"This installation, by default will use Google DNS servers, 8.8.8.8 or "
-"8.8.4.4 and updates resolv.conf. These DNS nameserver entries can be changed "
-"by updating file ``/opt/openstack-helm-infra/tools/images/kubeadm-aio/assets/"
-"opt/playbooks/vars.yaml`` under section ``external_dns_nameservers``. This "
-"change must be done on each node in your cluster."
-
-msgid "This is a two step process, i.e."
-msgstr "This is a two step process, i.e."
-
-msgid ""
-"This script will create two loopback devices for Ceph as one disk for OSD "
-"data and other disk for block DB and block WAL. If default devices (loop0 "
-"and loop1) are busy in your case, feel free to change them by exporting "
-"environment variables(CEPH_OSD_DATA_DEVICE and CEPH_OSD_DB_WAL_DEVICE)."
-msgstr ""
-"This script will create two loopback devices for Ceph as one disk for OSD "
-"data and other disk for block DB and block WAL. If default devices (loop0 "
-"and loop1) are busy in your case, feel free to change them by exporting "
-"environment variables(CEPH_OSD_DATA_DEVICE and CEPH_OSD_DB_WAL_DEVICE)."
-
-msgid ""
-"This will delete all Kubernetes resources generated when the chart was "
-"instantiated. However for OpenStack charts, by default, this will not delete "
-"the database and database users that were created when the chart was "
-"installed. All OpenStack projects can be configured such that upon deletion, "
-"their database will also be removed. To delete the database when the chart "
-"is deleted the database drop job must be enabled before installing the "
-"chart. There are two ways to enable the job, set the job_db_drop value to "
-"true in the chart's ``values.yaml`` file, or override the value using the "
-"helm install command as follows:"
-msgstr ""
-"This will delete all Kubernetes resources generated when the chart was "
-"instantiated. However for OpenStack charts, by default, this will not delete "
-"the database and database users that were created when the chart was "
-"installed. All OpenStack projects can be configured such that upon deletion, "
-"their database will also be removed. To delete the database when the chart "
-"is deleted the database drop job must be enabled before installing the "
-"chart. There are two ways to enable the job, set the job_db_drop value to "
-"true in the chart's ``values.yaml`` file, or override the value using the "
-"helm install command as follows:"
-
-msgid ""
-"Throughout this guide the assumption is that the user is: ``ubuntu``. "
-"Because this user has to execute root level commands remotely to other "
-"nodes, it is advised to add the following lines to ``/etc/sudoers`` for each "
-"node:"
-msgstr ""
-"Throughout this guide the assumption is that the user is: ``ubuntu``. "
-"Because this user has to execute root level commands remotely to other "
-"nodes, it is advised to add the following lines to ``/etc/sudoers`` for each "
-"node:"
-
-msgid ""
-"To allocate PMD threads to NUMA sockets in OVS, ensure that the "
-"``pmd_cpu_mask`` attribute in values.yaml includes CPU sockets on the "
-"corresponding NUMA socket. In the example below, the mask of 0xf covers the "
-"first 4 CPU cores which are distributed across NUMA sockets 0 and 1."
-msgstr ""
-"To allocate PMD threads to NUMA sockets in OVS, ensure that the "
-"``pmd_cpu_mask`` attribute in values.yaml includes CPU sockets on the "
-"corresponding NUMA socket. In the example below, the mask of 0xf covers the "
-"first 4 CPU cores which are distributed across NUMA sockets 0 and 1."
-
-msgid ""
-"To allocate hugepages to NUMA sockets in OVS, ensure that the "
-"``socket_memory`` attribute in values.yaml specifies a value for the "
-"corresponding NUMA socket. In the following example, OVS will use one 1G "
-"hugepage for NUMA socket 0 and socket 1."
-msgstr ""
-"To allocate hugepages to NUMA sockets in OVS, ensure that the "
-"``socket_memory`` attribute in values.yaml specifies a value for the "
-"corresponding NUMA socket. In the following example, OVS will use one 1G "
-"hugepage for NUMA socket 0 and socket 1."
-
-msgid ""
-"To continue to deploy OpenStack on Kubernetes via OSH, see :doc:`Deploy "
-"NFS<./deploy-with-nfs>` or :doc:`Deploy Ceph<./deploy-with-ceph>`."
-msgstr ""
-"To continue to deploy OpenStack on Kubernetes via OSH, see :doc:`Deploy "
-"NFS<./deploy-with-nfs>` or :doc:`Deploy Ceph<./deploy-with-ceph>`."
-
-msgid ""
-"To copy the ssh key to each node, this can be accomplished with the ``ssh-"
-"copy-id`` command, for example: *ssh-copy-id ubuntu@192.168.122.178*"
-msgstr ""
-"To copy the ssh key to each node, this can be accomplished with the ``ssh-"
-"copy-id`` command, for example: *ssh-copy-id ubuntu@192.168.122.178*"
-
-msgid "To delete an installed helm chart, use the following command:"
-msgstr "To delete an installed helm chart, use the following command:"
-
-msgid "To generate the key you can use ``ssh-keygen -t rsa``"
-msgstr "To generate the key you can use ``ssh-keygen -t rsa``"
-
-msgid "To get started with OSH, we will need  ``git``,  ``curl`` and ``make``."
-msgstr ""
-"To get started with OSH, we will need  ``git``,  ``curl`` and ``make``."
-
-msgid ""
-"To run further commands from the CLI manually, execute the following to set "
-"up authentication credentials::"
-msgstr ""
-"To run further commands from the CLI manually, execute the following to set "
-"up authentication credentials::"
-
-msgid ""
-"To tear-down, the development environment charts should be removed first "
-"from the 'openstack' namespace and then the 'ceph' namespace using the "
-"commands from the `Removing Helm Charts` section. Additionally charts should "
-"be removed from the 'nfs' and 'libvirt' namespaces if deploying with NFS "
-"backing or bare metal development support. You can run the following "
-"commands to loop through and delete the charts, then stop the kubelet "
-"systemd unit and remove all the containers before removing the directories "
-"used on the host by pods."
-msgstr ""
-"To tear-down, the development environment charts should be removed first "
-"from the 'openstack' namespace and then the 'ceph' namespace using the "
-"commands from the `Removing Helm Charts` section. Additionally charts should "
-"be removed from the 'nfs' and 'libvirt' namespaces if deploying with NFS "
-"backing or bare metal development support. You can run the following "
-"commands to loop through and delete the charts, then stop the kubelet "
-"systemd unit and remove all the containers before removing the directories "
-"used on the host by pods."
-
-msgid "Troubleshooting"
-msgstr "Troubleshooting"
-
-msgid ""
-"Tungsten Fabric is the multicloud and multistack network solution which you "
-"can use for your OpenStack as a network plugin. This document decribes how "
-"you can deploy a single node Open Stack based on Tungsten Fabric using "
-"openstack helm for development purpose."
-msgstr ""
-"Tungsten Fabric is the multicloud and multistack network solution which you "
-"can use for your OpenStack as a network plugin. This document describes how "
-"you can deploy a single node Open Stack based on Tungsten Fabric using "
-"OpenStack helm for development purpose."
-
-msgid ""
-"Two similar options exist to set the FQDN overrides for External DNS mapping."
-msgstr ""
-"Two similar options exist to set the FQDN overrides for External DNS mapping."
-
-msgid ""
-"Until the Ubuntu kernel shipped with 16.04 supports CephFS subvolume mounts "
-"by default the `HWE Kernel <../troubleshooting/ubuntu-hwe-kernel.html>`__ is "
-"required to use CephFS."
-msgstr ""
-"Until the Ubuntu kernel shipped with 16.04 supports CephFS subvolume mounts "
-"by default the `HWE Kernel <../troubleshooting/ubuntu-hwe-kernel.html>`__ is "
-"required to use CephFS."
-
-msgid ""
-"Update your lab/environment DNS server with your appropriate host values "
-"creating A Records for the edge node IP's and various FQDN's. Alternatively "
-"you can test these settings locally by editing your ``/etc/hosts``. Below is "
-"an example with a dummy domain ``os.foo.org`` and dummy Ingress IP "
-"``1.2.3.4``."
-msgstr ""
-"Update your lab/environment DNS server with your appropriate host values "
-"creating A Records for the edge node IP's and various FQDN's. Alternatively "
-"you can test these settings locally by editing your ``/etc/hosts``. Below is "
-"an example with a dummy domain ``os.foo.org`` and dummy Ingress IP "
-"``1.2.3.4``."
-
-msgid ""
-"Use above gerrit commits to prepare the LOCI images using following script:"
-msgstr ""
-"Use above gerrit commits to prepare the LOCI images using following script:"
-
-msgid ""
-"Use it as ``docker build --build-arg PROJECT_REF=${REQUIREMENTS_REF_SPEC}`` "
-"command argument to build the requirements LOCI image."
-msgstr ""
-"Use it as ``docker build --build-arg PROJECT_REF=${REQUIREMENTS_REF_SPEC}`` "
-"command argument to build the requirements LOCI image."
-
-msgid "Using Horizon as an example, find the ``endpoints`` config."
-msgstr "Using Horizon as an example, find the ``endpoints`` config."
-
-msgid ""
-"Using the Helm packages previously pushed to the local Helm repository, run "
-"the following commands to instruct tiller to create an instance of the given "
-"chart. During installation, the helm client will print useful information "
-"about resources created, the state of the Helm releases, and whether any "
-"additional configuration steps are necessary."
-msgstr ""
-"Using the Helm packages previously pushed to the local Helm repository, run "
-"the following commands to instruct tiller to create an instance of the given "
-"chart. During installation, the helm client will print useful information "
-"about resources created, the state of the Helm releases, and whether any "
-"additional configuration steps are necessary."
-
-msgid "Verify the *v1beta1/Ingress* resource has a Host with your FQDN value"
-msgstr "Verify the *v1beta1/Ingress* resource has a Host with your FQDN value"
-
-msgid ""
-"We are also going to separate Ceph metadata and data onto a different "
-"devices to replicate the ideal scenario of fast disks for metadata and slow "
-"disks to store data. You can change this as per your design by referring to "
-"the documentation explained in ../openstack-helm-infra/ceph-osd/values.yaml"
-msgstr ""
-"We are also going to separate Ceph metadata and data onto a different "
-"devices to replicate the ideal scenario of fast disks for metadata and slow "
-"disks to store data. You can change this as per your design by referring to "
-"the documentation explained in ../openstack-helm-infra/ceph-osd/values.yaml"
-
-msgid ""
-"We are going to install Ceph OSDs backed by loopback devices as this will "
-"help us not to attach extra disks, in case if you have enough disks on the "
-"node then feel free to skip creating loopback devices by exporting "
-"CREATE_LOOPBACK_DEVICES_FOR_CEPH to false and export the  block devices "
-"names as environment variables(CEPH_OSD_DATA_DEVICE and "
-"CEPH_OSD_DB_WAL_DEVICE)."
-msgstr ""
-"We are going to install Ceph OSDs backed by loopback devices as this will "
-"help us not to attach extra disks, in case if you have enough disks on the "
-"node then feel free to skip creating loopback devices by exporting "
-"CREATE_LOOPBACK_DEVICES_FOR_CEPH to false and export the  block devices "
-"names as environment variables(CEPH_OSD_DATA_DEVICE and "
-"CEPH_OSD_DB_WAL_DEVICE)."
-
-msgid ""
-"We want to change the **public** configurations to match our DNS layouts "
-"above. In each Chart ``values.yaml`` is a ``endpoints`` configuration that "
-"has ``host_fqdn_override``'s for each API that the Chart either produces or "
-"is dependent on. `Read more about how Endpoints are developed <https://docs."
-"openstack.org/openstack-helm/latest/devref/endpoints.html>`__. Note while "
-"Glance Registry is listening on a Ingress http endpoint, you will not need "
-"to expose the registry for external services."
-msgstr ""
-"We want to change the **public** configurations to match our DNS layouts "
-"above. In each Chart ``values.yaml`` is a ``endpoints`` configuration that "
-"has ``host_fqdn_override``'s for each API that the Chart either produces or "
-"is dependent on. `Read more about how Endpoints are developed <https://docs."
-"openstack.org/openstack-helm/latest/devref/endpoints.html>`__. Note while "
-"Glance Registry is listening on a Ingress http endpoint, you will not need "
-"to expose the registry for external services."
-
-msgid ""
-"When adding a DPDK port (a NIC bound to DPDK) to OVS fails, one source of "
-"error is related to an incorrect configuration with regards to the NUMA "
-"topology of the underlying hardware. Every NIC is connected to one specific "
-"NUMA socket. In order to use a NIC as DPDK port in OVS, the OVS "
-"configurations regarding hugepage(s) and PMD thread(s) need to match the "
-"NUMA topology."
-msgstr ""
-"When adding a DPDK port (a NIC bound to DPDK) to OVS fails, one source of "
-"error is related to an incorrect configuration with regards to the NUMA "
-"topology of the underlying hardware. Every NIC is connected to one specific "
-"NUMA socket. In order to use a NIC as DPDK port in OVS, the OVS "
-"configurations regarding hugepage(s) and PMD thread(s) need to match the "
-"NUMA topology."
-
-msgid ""
-"While deploying neutron-server and L2 agents, TaaS should be enabled in "
-"``conf: neutron`` section to add TaaS as a service plugin; in ``conf: "
-"plugins`` section to add TaaS as a L2 agent extension; in ``conf: "
-"taas_plugin`` section to configure the ``service_provider`` endpoint used by "
-"Neutron TaaS plugin:"
-msgstr ""
-"While deploying neutron-server and L2 agents, TaaS should be enabled in "
-"``conf: neutron`` section to add TaaS as a service plugin; in ``conf: "
-"plugins`` section to add TaaS as a L2 agent extension; in ``conf: "
-"taas_plugin`` section to configure the ``service_provider`` endpoint used by "
-"Neutron TaaS plugin:"
-
-msgid ""
-"You can use any Kubernetes deployment tool to bring up a working Kubernetes "
-"cluster for use with OpenStack-Helm. For production deployments, please "
-"choose (and tune appropriately) a highly-resilient Kubernetes distribution, "
-"e.g.:"
-msgstr ""
-"You can use any Kubernetes deployment tool to bring up a working Kubernetes "
-"cluster for use with OpenStack-Helm. For production deployments, please "
-"choose (and tune appropriately) a highly-resilient Kubernetes distribution, "
-"e.g.:"
-
-msgid ""
-"You can use any Kubernetes deployment tool to bring up a working Kubernetes "
-"cluster for use with OpenStack-Helm. This guide describes how to simply "
-"stand up a multinode Kubernetes cluster via the OpenStack-Helm gate scripts, "
-"which use KubeADM and Ansible. Although this cluster won't be production-"
-"grade, it will serve as a quick starting point in a lab or proof-of-concept "
-"environment."
-msgstr ""
-"You can use any Kubernetes deployment tool to bring up a working Kubernetes "
-"cluster for use with OpenStack-Helm. This guide describes how to simply "
-"stand up a multinode Kubernetes cluster via the OpenStack-Helm gate scripts, "
-"which use KubeADM and Ansible. Although this cluster won't be production-"
-"grade, it will serve as a quick starting point in a lab or proof-of-concept "
-"environment."
-
-msgid ""
-"You may now deploy kubernetes, and helm onto your machine, first move into "
-"the ``openstack-helm`` directory and then run the following:"
-msgstr ""
-"You may now deploy kubernetes, and helm onto your machine, first move into "
-"the ``openstack-helm`` directory and then run the following:"
-
-msgid ""
-"Your changes to `/etc/environment` will not be applied until you source them:"
-msgstr ""
-"Your changes to `/etc/environment` will not be applied until you source them:"
-
-msgid ""
-"`Airship <https://airshipit.org/>`_, a declarative open cloud infrastructure "
-"platform"
-msgstr ""
-"`Airship <https://airshipit.org/>`_, a declarative open cloud infrastructure "
-"platform"
-
-msgid ""
-"`KubeADM <https://kubernetes.io/docs/setup/independent/high-availability/"
-">`_, the foundation of a number of Kubernetes installation solutions"
-msgstr ""
-"`KubeADM <https://kubernetes.io/docs/setup/independent/high-availability/"
-">`_, the foundation of a number of Kubernetes installation solutions"
-
-msgid "https://review.openstack.org/#/c/597200/"
-msgstr "https://review.openstack.org/#/c/597200/"
-
-msgid "https://review.openstack.org/#/c/607392/"
-msgstr "https://review.openstack.org/#/c/607392/"
-
-msgid "https://review.openstack.org/#/c/621606/"
-msgstr "https://review.openstack.org/#/c/621606/"
-
-msgid "hugepages have been allocated on NUMA socket 1 by OVS, and"
-msgstr "hugepages have been allocated on NUMA socket 1 by OVS, and"
-
-msgid ""
-"if you are rerunning the below script then make sure to skip the loopback "
-"device creation by exporting CREATE_LOOPBACK_DEVICES_FOR_CEPH to false."
-msgstr ""
-"if you are rerunning the below script then make sure to skip the loopback "
-"device creation by exporting CREATE_LOOPBACK_DEVICES_FOR_CEPH to false."
-
-msgid ""
-"node_one, node_two and node_three below are all worker nodes, children of "
-"the master node that the commands below are executed on."
-msgstr ""
-"node_one, node_two and node_three below are all worker nodes, children of "
-"the master node that the commands below are executed on."
diff --git a/doc/source/locale/en_GB/LC_MESSAGES/doc-specs.po b/doc/source/locale/en_GB/LC_MESSAGES/doc-specs.po
deleted file mode 100644
index b550133036..0000000000
--- a/doc/source/locale/en_GB/LC_MESSAGES/doc-specs.po
+++ /dev/null
@@ -1,2800 +0,0 @@
-# Andi Chandler <andi@gowling.com>, 2020. #zanata
-# Andi Chandler <andi@gowling.com>, 2021. #zanata
-msgid ""
-msgstr ""
-"Project-Id-Version: openstack-helm 0.1.1.dev3462\n"
-"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2021-06-22 20:22+0000\n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-"PO-Revision-Date: 2021-06-24 03:47+0000\n"
-"Last-Translator: Andi Chandler <andi@gowling.com>\n"
-"Language-Team: English (United Kingdom)\n"
-"Language: en_GB\n"
-"X-Generator: Zanata 4.3.3\n"
-"Plural-Forms: nplurals=2; plural=(n != 1)\n"
-
-msgid "**Charts in the appropriate project**"
-msgstr "**Charts in the appropriate project**"
-
-msgid "**Combined helm-toolkit**"
-msgstr "**Combined helm-toolkit**"
-
-msgid "**Document Kubernetes requirements**"
-msgstr "**Document Kubernetes requirements**"
-
-msgid "**Document version requirements**"
-msgstr "**Document version requirements**"
-
-msgid "**Helm test for all charts**"
-msgstr "**Helm test for all charts**"
-
-msgid "**Inclusion of all core services**"
-msgstr "**Inclusion of all core services**"
-
-msgid "**LMA Operations Guide**"
-msgstr "**LMA Operations Guide**"
-
-msgid "**OpenStack-Helm release process**"
-msgstr "**OpenStack-Helm release process**"
-
-msgid "**Release notes**"
-msgstr "**Release notes**"
-
-msgid "**Resiliency across reboots**"
-msgstr "**Resiliency across reboots**"
-
-msgid "**Split Ceph chart**"
-msgstr "**Split Ceph chart**"
-
-msgid "**Standardization of manifests**"
-msgstr "**Standardisation of manifests**"
-
-msgid "**Standardization of values**"
-msgstr "**Standardisation of values**"
-
-msgid "**Upgrades**"
-msgstr "**Upgrades**"
-
-msgid "**Values-driven config files**"
-msgstr "**Values-driven config files**"
-
-msgid "1) Prepare scripts:"
-msgstr "1) Prepare scripts:"
-
-msgid ""
-"1. For each chart, add a new entry ``oci_image_registry:`` under ``endpoints:"
-"`` in ``values.yaml``. The entry ``oci_image_registry:`` has the ``auth:`` "
-"section which provides the credentials for accessing registry images and an "
-"option ``enabled:`` to determine whether images authentication is required "
-"or not. The registry basic information would also be included for generating "
-"the registry URL by the endpoint lookup functions. Also add a new entry "
-"``oci_image_registry:`` under ``secrets:`` to indicate the secret name. In "
-"order to create the secret that holds the provided credentials, add a new "
-"component ``secret_registry`` in ``manifests:`` section. For example:"
-msgstr ""
-"1. For each chart, add a new entry ``oci_image_registry:`` under ``endpoints:"
-"`` in ``values.yaml``. The entry ``oci_image_registry:`` has the ``auth:`` "
-"section which provides the credentials for accessing registry images and an "
-"option ``enabled:`` to determine whether images authentication is required "
-"or not. The registry basic information would also be included for generating "
-"the registry URL by the endpoint lookup functions. Also add a new entry "
-"``oci_image_registry:`` under ``secrets:`` to indicate the secret name. In "
-"order to create the secret that holds the provided credentials, add a new "
-"component ``secret_registry`` in ``manifests:`` section. For example:"
-
-msgid "2 Replace occurrence of ``ceph.yaml`` with ``tenant-ceph.yaml``"
-msgstr "2 Replace occurrence of ``ceph.yaml`` with ``tenant-ceph.yaml``"
-
-msgid "2) Deploy ingress chart:"
-msgstr "2) Deploy ingress chart:"
-
-msgid ""
-"3 For tenant Ceph, no need to deploy ceph-provisioners. Update script to "
-"``for CHART in ceph-mon ceph-osd ceph-client; do``"
-msgstr ""
-"3 For tenant Ceph, no need to deploy ceph-provisioners. Update script to "
-"``for CHART in ceph-mon ceph-osd ceph-client; do``"
-
-msgid "3) Deploy Ceph for RBD:"
-msgstr "3) Deploy Ceph for RBD:"
-
-msgid "4) Deploy MariaDB, RabbitMQ, Memcached and Keystone:"
-msgstr "4) Deploy MariaDB, RabbitMQ, Memcached and Keystone:"
-
-msgid "5) Deploy Ceph for Tenant:"
-msgstr "5) Deploy Ceph for Tenant:"
-
-msgid "6 VM based hosts (node1, node2, node3, node4, node5, node6)"
-msgstr "6 VM based hosts (node1, node2, node3, node4, node5, node6)"
-
-msgid "6) Enable Openstack namespace to use Tenant Ceph:"
-msgstr "6) Enable OpenStack namespace to use Tenant Ceph:"
-
-msgid "7) Tenant Ceph: Deploy Rados Gateway:"
-msgstr "7) Tenant Ceph: Deploy RADOS Gateway:"
-
-msgid "8) Deploy Glance:"
-msgstr "8) Deploy Glance:"
-
-msgid "9) Deploy Cinder:"
-msgstr "9) Deploy Cinder:"
-
-msgid ""
-"A basic Logging, Monitoring, and Alerting-oriented operations guide must be "
-"in place, illustrating for operators (and developers) how to set up and use "
-"an example LMA setup for OpenStack and supporting services.  It will include "
-"instructions on how to perform basic configuration and how to access and use "
-"the user interfaces at a high level.  It will also link out to more detailed "
-"documentation for the LMA tooling itself."
-msgstr ""
-"A basic Logging, Monitoring, and Alerting-oriented operations guide must be "
-"in place, illustrating for operators (and developers) how to set up and use "
-"an example LMA setup for OpenStack and supporting services.  It will include "
-"instructions on how to perform basic configuration and how to access and use "
-"the user interfaces at a high level.  It will also link out to more detailed "
-"documentation for the LMA tooling itself."
-
-msgid ""
-"A few areas have been identified on changes required. Each of them will be a "
-"work item."
-msgstr ""
-"A few areas have been identified on changes required. Each of them will be a "
-"work item."
-
-msgid ""
-"A foundational requirement of 1.0 readiness is the presence of robust gating "
-"that will ensure functionality, backward compatibility, and upgradeability. "
-"This will allow development to continue and for support for new versions of "
-"OpenStack to be added post-1.0. The following gating requirements must be "
-"met:"
-msgstr ""
-"A foundational requirement of 1.0 readiness is the presence of robust gating "
-"that will ensure functionality, backward compatibility, and upgradeability. "
-"This will allow development to continue and for support for new versions of "
-"OpenStack to be added post-1.0. The following gating requirements must be "
-"met:"
-
-msgid ""
-"A gate will be added to OpenStack-Helm that runs through the developer "
-"environment deployment process."
-msgstr ""
-"A gate will be added to OpenStack-Helm that runs through the developer "
-"environment deployment process."
-
-msgid ""
-"A number of in-progress and planned development efforts must be completed "
-"prior to 1.0, to ensure a stable OpenStack-Helm interface thereafter."
-msgstr ""
-"A number of in-progress and planned development efforts must be completed "
-"prior to 1.0, to ensure a stable OpenStack-Helm interface thereafter."
-
-msgid ""
-"A set of scripts will be provided to exercise the deployed environment that "
-"checks the basic functionality of the deployed cloud, driven where possible "
-"via OpenStack heat:"
-msgstr ""
-"A set of scripts will be provided to exercise the deployed environment that "
-"checks the basic functionality of the deployed cloud, driven where possible "
-"via OpenStack heat:"
-
-msgid ""
-"A specification should precede any broad-reaching technical changes or "
-"proposals to OpenStack-Helm.  Examples of changes requiring a specification "
-"include:  a standard format to the values.yaml files, multiple backend "
-"support for neutron, and the approach for logging and monitoring in "
-"OpenStack-Helm.  Some additional features will not need an accompanying "
-"specification, but may be tied back to an existing specification.  An "
-"example of this would be introducing a service in OpenStack-Helm that could "
-"be included under the scope of a specification already drafted and approved."
-msgstr ""
-"A specification should precede any broad-reaching technical changes or "
-"proposals to OpenStack-Helm.  Examples of changes requiring a specification "
-"include:  a standard format to the values.yaml files, multiple backend "
-"support for neutron, and the approach for logging and monitoring in "
-"OpenStack-Helm.  Some additional features will not need an accompanying "
-"specification, but may be tied back to an existing specification.  An "
-"example of this would be introducing a service in OpenStack-Helm that could "
-"be included under the scope of a specification already drafted and approved."
-
-msgid "API Deployments"
-msgstr "API Deployments"
-
-msgid "Ability to apply custom metadata and uniform format to logs"
-msgstr "Ability to apply custom metadata and uniform format to logs"
-
-msgid "Ability to perform custom queries against metrics collected"
-msgstr "Ability to perform custom queries against metrics collected"
-
-msgid "Ability to perform custom queries against stored logs"
-msgstr "Ability to perform custom queries against stored logs"
-
-msgid ""
-"Above output shows ``http://ceph-rgw.openstack.svc.cluster.local`` which "
-"shows that swift is pointing to tenant-ceph."
-msgstr ""
-"Above output shows ``http://ceph-rgw.openstack.svc.cluster.local`` which "
-"shows that swift is pointing to tenant-ceph."
-
-msgid ""
-"Above output shows that tenant ceph now has 19 pools including one for "
-"Cinder."
-msgstr ""
-"Above output shows that tenant Ceph now has 19 pools including one for "
-"Cinder."
-
-msgid "Add Linux Bridge as first alternative for OVS - separate spec needed."
-msgstr "Add Linux Bridge as first alternative for OVS - separate spec needed."
-
-msgid "Add LinuxBridge daemonset"
-msgstr "Add LinuxBridge daemonset"
-
-msgid ""
-"Add a helm-toolkit function ``helm-toolkit.manifests.secret_registry`` to "
-"create a manifest for secret generation. For example:"
-msgstr ""
-"Add a helm-toolkit function ``helm-toolkit.manifests.secret_registry`` to "
-"create a manifest for secret generation. For example:"
-
-msgid ""
-"Add a template highlighting the updated values ordering for use in chart "
-"development"
-msgstr ""
-"Add a template highlighting the updated values ordering for use in chart "
-"development"
-
-msgid "Add documentation on how to use LinuxBridge"
-msgstr "Add documentation on how to use LinuxBridge"
-
-msgid "Add gate for developer environment"
-msgstr "Add gate for developer environment"
-
-msgid "Add gate job testing VM network connectivity"
-msgstr "Add gate job testing VM network connectivity"
-
-msgid ""
-"Add one SDN to see if proposed change is working OK - separate spec needed."
-msgstr ""
-"Add one SDN to see if proposed change is working OK - separate spec needed."
-
-msgid "Add or remove nodes depending on utilization"
-msgstr "Add or remove nodes depending on utilisation"
-
-msgid "Additional assignees TBD"
-msgstr "Additional assignees TBD"
-
-msgid ""
-"Aggregator also send aggregated logs to Kafka for external tools to consume"
-msgstr ""
-"Aggregator also send aggregated logs to Kafka for external tools to consume"
-
-msgid "Alerting capabilities to notify operators when thresholds exceeded"
-msgstr "Alerting capabilities to notify operators when thresholds exceeded"
-
-msgid "Alertmanager chart"
-msgstr "Alertmanager chart"
-
-msgid ""
-"All charts must include sensible configuration values to make the monitoring "
-"platform usable by default.  These include:  static Prometheus "
-"configurations for the included exporters, static dashboards for Grafana "
-"mounted via configMaps and configurations for Alertmanager out of the box."
-msgstr ""
-"All charts must include sensible configuration values to make the monitoring "
-"platform usable by default.  These include:  static Prometheus "
-"configurations for the included exporters, static dashboards for Grafana "
-"mounted via configMaps and configurations for Alertmanager out of the box."
-
-msgid ""
-"All charts require valid and sensible default values to provide operational "
-"value out of the box."
-msgstr ""
-"All charts require valid and sensible default values to provide operational "
-"value out of the box."
-
-msgid ""
-"All charts should follow design approaches applied to all other OpenStack-"
-"Helm charts, including the use of helm-toolkit."
-msgstr ""
-"All charts should follow design approaches applied to all other OpenStack-"
-"Helm charts, including the use of helm-toolkit."
-
-msgid "All charts should migrate to their appropriate home project as follows:"
-msgstr ""
-"All charts should migrate to their appropriate home project as follows:"
-
-msgid ""
-"All keys under top-level keys are listed in alphabetical order, with the "
-"exception of the conf key.  As some configuration files require a strict "
-"ordering of their content, excluding this key from any alphabetical "
-"organization is required."
-msgstr ""
-"All keys under top-level keys are listed in alphabetical order, with the "
-"exception of the conf key.  As some configuration files require a strict "
-"ordering of their content, excluding this key from any alphabetical "
-"organisation is required."
-
-msgid "All services in OpenStack-Helm log to stdout and stderr by default"
-msgstr "All services in OpenStack-Helm log to stdout and stderr by default"
-
-msgid ""
-"All services running within the platform should be subject to the security "
-"practices applied to the other OpenStack-Helm charts."
-msgstr ""
-"All services running within the platform should be subject to the security "
-"practices applied to the other OpenStack-Helm charts."
-
-msgid ""
-"All services should survive node reboots, and their functionality validated "
-"following a reboot by a gate."
-msgstr ""
-"All services should survive node reboots, and their functionality validated "
-"following a reboot by a gate."
-
-msgid ""
-"All three charts must include sensible configuration values to make the "
-"logging platform usable by default.  These include: proper input "
-"configurations for Fluentd, proper metadata and formats applied to the logs "
-"via Fluentd, sensible indexes created for Elasticsearch, and proper "
-"configuration values for Kibana to query the Elasticsearch indexes "
-"previously created."
-msgstr ""
-"All three charts must include sensible configuration values to make the "
-"logging platform usable by default.  These include: proper input "
-"configurations for Fluentd, proper metadata and formats applied to the logs "
-"via Fluentd, sensible indexes created for Elasticsearch, and proper "
-"configuration values for Kibana to query the Elasticsearch indexes "
-"previously created."
-
-msgid "Allow the usage of multiple base images in OSH."
-msgstr "Allow the usage of multiple base images in OSH."
-
-msgid ""
-"Allows different profiles of apache, should some charts require different "
-"args for example for the same kind of images, by using yaml dict merges "
-"features."
-msgstr ""
-"Allows different profiles of Apache, should some charts require different "
-"args for example for the same kind of images, by using yaml dict merges "
-"features."
-
-msgid ""
-"Alter webserver configuration per distro. Different distros have different "
-"expectations in terms of path (including a different series of files "
-"required), and it would make the operators' life easier by using their "
-"expected distro paths."
-msgstr ""
-"Alter webserver configuration per distro. Different distros have different "
-"expectations in terms of path (including a different series of files "
-"required), and it would make the operators' life easier by using their "
-"expected distro paths."
-
-msgid "Alternatives"
-msgstr "Alternatives"
-
-msgid ""
-"Alternatives to decomposable Neutron chart would be to copy whole Neutron "
-"chart and create spin-offs with new SDN enabled. This approach has drawbacks "
-"of maintaining the whole neutron chart in many places, and copies of "
-"standard services may be out of sync with OSH improvements. This implies "
-"constant maintenance effort to up to date."
-msgstr ""
-"Alternatives to decomposable Neutron chart would be to copy whole Neutron "
-"chart and create spin-offs with new SDN enabled. This approach has drawbacks "
-"of maintaining the whole neutron chart in many places, and copies of "
-"standard services may be out of sync with OSH improvements. This implies "
-"constant maintenance effort to up to date."
-
-msgid "Angie Wang (angiewang)"
-msgstr "Angie Wang (angiewang)"
-
-msgid ""
-"Another place where Neutron L2 agent should be pointed is dependencies list "
-"in other OpenStack projects. Currently, :code:`nova-compute` has dependency "
-"for :code:`ovs-agent` in :code:`nova/values.yaml`, it should be changed to:"
-msgstr ""
-"Another place where Neutron L2 agent should be pointed is dependencies list "
-"in other OpenStack projects. Currently, :code:`nova-compute` has dependency "
-"for :code:`ovs-agent` in :code:`nova/values.yaml`, it should be changed to:"
-
-msgid "Any other changes to the external interface of OpenStack-Helm"
-msgstr "Any other changes to the external interface of OpenStack-Helm"
-
-msgid ""
-"As mentioned before, configuration of L3/DHCP/metadata agent should be "
-"adjusted to use LinuxBridge, sample configuration override:"
-msgstr ""
-"As mentioned before, configuration of L3/DHCP/metadata agent should be "
-"adjusted to use LinuxBridge, sample configuration override:"
-
-msgid "Assign Floating IP to VM"
-msgstr "Assign Floating IP to VM"
-
-msgid "Assignee(s)"
-msgstr "Assignee(s)"
-
-msgid ""
-"At this point, curated scripts will be used to deploy OpenStack-Helm "
-"services on demand as desired, with documentation provided to allow a new "
-"developer to quickly set up either a single or multimode deployment of a "
-"reference `OpenStack Compute Kit <https://governance.openstack.org/tc/"
-"reference/tags/starter-kit_compute.html>`_ environment with the addition of:"
-msgstr ""
-"At this point, curated scripts will be used to deploy OpenStack-Helm "
-"services on demand as desired, with documentation provided to allow a new "
-"developer to quickly set up either a single or multimode deployment of a "
-"reference `OpenStack Compute Kit <https://governance.openstack.org/tc/"
-"reference/tags/starter-kit_compute.html>`_ environment with the addition of:"
-
-msgid ""
-"Authentication should be enabled for normal users to access Kube API server "
-"via either kubectl command or kube REST API call."
-msgstr ""
-"Authentication should be enabled for normal users to access Kube API server "
-"via either kubectl command or kube REST API call."
-
-msgid "Backed by highly available storage"
-msgstr "Backed by highly available storage"
-
-msgid ""
-"Before drafting a specification, a blueprint should be filed in Storyboard_ "
-"along with any dependencies the blueprint requires.  Once the blueprint has "
-"been registered, submit the specification as a patch set to the specs/ "
-"directory using the supplied template."
-msgstr ""
-"Before drafting a specification, a blueprint should be filed in Storyboard_ "
-"along with any dependencies the blueprint requires.  Once the blueprint has "
-"been registered, submit the specification as a patch set to the specs/ "
-"directory using the supplied template."
-
-msgid "Before using Openstack-Helm to deploy openstack services,"
-msgstr "Before using Openstack-Helm to deploy OpenStack services,"
-
-msgid "Bin ConfigMaps"
-msgstr "Bin ConfigMaps"
-
-msgid ""
-"Blueprint: https://blueprints.launchpad.net/openstack-helm/+spec/nginx-"
-"sidecar"
-msgstr ""
-"Blueprint: https://blueprints.launchpad.net/openstack-helm/+spec/nginx-"
-"sidecar"
-
-msgid "Blueprint: neutron-multiple-sdns_"
-msgstr "Blueprint: neutron-multiple-sdns_"
-
-msgid "Blueprint: support-linux-bridge-on-neutron_"
-msgstr "Blueprint: support-linux-bridge-on-neutron_"
-
-msgid "Blueprint: support-oci-image-registry-with-authentication-turned-on_"
-msgstr "Blueprint: support-oci-image-registry-with-authentication-turned-on_"
-
-msgid "Blueprints: 1. osh-logging-framework_"
-msgstr "Blueprints: 1. osh-logging-framework_"
-
-msgid "Blueprints: 1. osh-monitoring_ 2. osh-logging-framework_"
-msgstr "Blueprints: 1. osh-monitoring_ 2. osh-logging-framework_"
-
-msgid ""
-"But above alternatives have limitations and security impact. i.e...require "
-"root access to configure on all nodes, all pods can read any configured "
-"private registries, all pods can use any images cached on a node [1]_"
-msgstr ""
-"But above alternatives have limitations and security impact. i.e...require "
-"root access to configure on all nodes, all pods can read any configured "
-"private registries, all pods can use any images cached on a node [1]_"
-
-msgid ""
-"By default, :code:`daemonset_lb_agent` will be set to false to remain "
-"default behaviour of installing OVS as networking agent."
-msgstr ""
-"By default, :code:`daemonset_lb_agent` will be set to false to remain "
-"default behaviour of installing OVS as networking agent."
-
-msgid "Ceph Clusters:"
-msgstr "Ceph Clusters:"
-
-msgid "Ceph backed Block Storage (cinder)"
-msgstr "Ceph backed Block Storage (Cinder)"
-
-msgid "Ceph backed Object Storage"
-msgstr "Ceph backed Object Storage"
-
-msgid "Ceph for RBD:"
-msgstr "Ceph for RBD:"
-
-msgid "Ceph for Tenant:"
-msgstr "Ceph for Tenant:"
-
-msgid "Ceph metrics: total pool usage, latency, health, etc"
-msgstr "Ceph metrics: total pool usage, latency, health, etc"
-
-msgid ""
-"Change ordering of keys across all charts in openstack-helm, openstack-helm-"
-"infra, and openstack-helm-addons"
-msgstr ""
-"Change ordering of keys across all charts in openstack-helm, openstack-helm-"
-"infra, and openstack-helm-addons"
-
-msgid ""
-"Charts for all core OpenStack services must be present to achieve 1.0 "
-"releasability.  The only core service outstanding at this time is Swift."
-msgstr ""
-"Charts for all core OpenStack services must be present to achieve 1.0 "
-"releasability.  The only core service outstanding at this time is Swift."
-
-msgid ""
-"Charts for exporters: kube-state-metrics, ceph-exporter, openstack-exporter?"
-msgstr ""
-"Charts for exporters: kube-state-metrics, ceph-exporter, openstack-exporter?"
-
-msgid "Code Completion and Refactoring"
-msgstr "Code Completion and Refactoring"
-
-msgid "Collect logs from the node by Fluentbit"
-msgstr "Collect logs from the node by Fluentbit"
-
-msgid "Common method to configure all monitoring targets"
-msgstr "Common method to configure all monitoring targets"
-
-msgid ""
-"Comprehensive documentation is key to the ability for real-world operators "
-"to benefit from OpenStack-Helm, and so it is a requirement for 1.0 "
-"releasability. The following outstanding items must be completed from a "
-"documentation perspective:"
-msgstr ""
-"Comprehensive documentation is key to the ability for real-world operators "
-"to benefit from OpenStack-Helm, and so it is a requirement for 1.0 "
-"releasability. The following outstanding items must be completed from a "
-"documentation perspective:"
-
-msgid "Configurable log rotation mechanism"
-msgstr "Configurable log rotation mechanism"
-
-msgid "Configuration in :code:`neutron.conf` and :code:`ml2_conf.ini`"
-msgstr "Configuration in :code:`neutron.conf` and :code:`ml2_conf.ini`"
-
-msgid ""
-"Cover the following logging use cases https://review.openstack.org/#/"
-"c/482687/"
-msgstr ""
-"Cover the following logging use cases https://review.openstack.org/#/"
-"c/482687/"
-
-msgid "Create SSH Key in nova"
-msgstr "Create SSH Key in Nova"
-
-msgid "Create VM on tenant network"
-msgstr "Create VM on tenant network"
-
-msgid ""
-"Create conditionals in the helm charts. This is problematic, as the amount "
-"of conditionals will increase and will be harder to maintain. Overrides "
-"files are easy to sync between charts."
-msgstr ""
-"Create conditionals in the Helm charts. This is problematic, as the amount "
-"of conditionals will increase and will be harder to maintain. Overrides "
-"files are easy to sync between charts."
-
-msgid "Create external network"
-msgstr "Create external network"
-
-msgid "Create tenant network"
-msgstr "Create tenant network"
-
-msgid "Create tenant router to link tenant network and external"
-msgstr "Create tenant router to link tenant network and external"
-
-msgid "CronJobs"
-msgstr "CronJobs"
-
-msgid ""
-"Currently OpenStack-Helm supports OpenVSwitch as a network virtualization "
-"engine. In order to support many possible backends (SDNs), changes are "
-"required in neutron chart and in deployment techniques. OpenStack-Helm can "
-"support every SDN solution that has Neutron plugin, either core_plugin or "
-"mechanism_driver."
-msgstr ""
-"Currently OpenStack-Helm supports OpenVSwitch as a network virtualization "
-"engine. In order to support many possible backends (SDNs), changes are "
-"required in Neutron chart and in deployment techniques. OpenStack-Helm can "
-"support every SDN solution that has Neutron plugin, either core_plugin or "
-"mechanism_driver."
-
-msgid ""
-"Currently both OpenStack-Helm and OpenStack-Helm-Infra have their own "
-"parallel versions of the Helm-Toolkit library chart.  They must be combined "
-"into a single chart in OpenStack-Helm-Infra prior to 1.0."
-msgstr ""
-"Currently both OpenStack-Helm and OpenStack-Helm-Infra have their own "
-"parallel versions of the Helm-Toolkit library chart.  They must be combined "
-"into a single chart in OpenStack-Helm-Infra prior to 1.0."
-
-msgid "DHCP - auto-assign IP address and DNS info"
-msgstr "DHCP - auto-assign IP address and DNS info"
-
-msgid "Database drop Job"
-msgstr "Database drop Job"
-
-msgid "Deploy Kubernetes via KubeADM, with charts for CNI and DNS services"
-msgstr "Deploy Kubernetes via KubeADM, with charts for CNI and DNS services"
-
-msgid "Deploying multuple Ceph clusters"
-msgstr "Deploying multiple Ceph clusters"
-
-msgid ""
-"Develop scripts for bringing up OpenStack-Helm Charts and perform basic "
-"interactive tests"
-msgstr ""
-"Develop scripts for bringing up OpenStack-Helm Charts and perform basic "
-"interactive tests"
-
-msgid "Developer Environment"
-msgstr "Developer Environment"
-
-msgid ""
-"Developers require a simple way of instantiating a working environment for "
-"OpenStack-Helm, that allows them to quickly begin development of the "
-"project. This is more complex to achieve than many OpenStack Projects that "
-"can simply rely upon a devstack plugin to achieve this. This is as OpenStack-"
-"Helm is focused on the deployment of OpenStack (and associated) Projects, "
-"rather than the development of the projects themselves, and also requires "
-"additional supporting infrastructure, e.g. Kubernetes and a CNI."
-msgstr ""
-"Developers require a simple way of instantiating a working environment for "
-"OpenStack-Helm, that allows them to quickly begin development of the "
-"project. This is more complex to achieve than many OpenStack Projects that "
-"can simply rely upon a devstack plugin to achieve this. This is as OpenStack-"
-"Helm is focused on the deployment of OpenStack (and associated) Projects, "
-"rather than the development of the projects themselves, and also requires "
-"additional supporting infrastructure, e.g. Kubernetes and a CNI."
-
-msgid "Development of OpenStack-Helm"
-msgstr "Development of OpenStack-Helm"
-
-msgid "Documentation"
-msgstr "Documentation"
-
-msgid "Documentation Impact"
-msgstr "Documentation Impact"
-
-msgid ""
-"Documentation of how new SDN can be enabled, how Neutron should be "
-"configured. Also, for each new SDN that would be incorporated, the "
-"architecture overview should be provided."
-msgstr ""
-"Documentation of how new SDN can be enabled, how Neutron should be "
-"configured. Also, for each new SDN that would be incorporated, the "
-"architecture overview should be provided."
-
-msgid "Documentation of how to enable the registry secret generation"
-msgstr "Documentation of how to enable the registry secret generation"
-
-msgid "Documentation on how to use LinuxBridge with Neutron chart."
-msgstr "Documentation on how to use LinuxBridge with Neutron chart."
-
-msgid ""
-"Documentation should be included for each of the included charts as well as "
-"documentation detailing the requirements for a usable monitoring platform, "
-"preferably with sane default values out of the box."
-msgstr ""
-"Documentation should be included for each of the included charts as well as "
-"documentation detailing the requirements for a usable monitoring platform, "
-"preferably with sane default values out of the box."
-
-msgid "Duplicate scripts as shows below for later use."
-msgstr "Duplicate scripts as shows below for later use."
-
-msgid ""
-"Dynamically alter webserver environment conditionally in the helm chart. For "
-"example, for apache, ensure the necessary modules to run openstack are "
-"available and loaded at helm chart deploy time. This will leverage the "
-"binaries listed in ``values.yaml``. These series of commands are "
-"distribution/image dependent, as commands to list modules to load might "
-"differ. However with a few parameters, we can get a very distro independent "
-"process which would allow us to load all the required apache modules."
-msgstr ""
-"Dynamically alter webserver environment conditionally in the helm chart. For "
-"example, for Apache, ensure the necessary modules to run OpenStack are "
-"available and loaded at helm chart deploy time. This will leverage the "
-"binaries listed in ``values.yaml``. These series of commands are "
-"distribution/image dependent, as commands to list modules to load might "
-"differ. However with a few parameters, we can get a very distro independent "
-"process which would allow us to load all the required Apache modules."
-
-msgid ""
-"Each chart's values.yaml file contains various settings such as docker image "
-"definition, chart structure setting, form of the resources being "
-"distributed, and process configuration.  Currently, the structure of the "
-"yaml file is complicated, and finding keys between charts proves difficult "
-"due to the lack of uniform values organization across charts."
-msgstr ""
-"Each chart's values.yaml file contains various settings such as docker image "
-"definition, chart structure setting, form of the resources being "
-"distributed, and process configuration.  Currently, the structure of the "
-"yaml file is complicated, and finding keys between charts proves difficult "
-"due to the lack of uniform values organisation across charts."
-
-msgid ""
-"Edit all helm charts to remove possible references to image specific "
-"elements, replacing them with values overrides or conditionals."
-msgstr ""
-"Edit all helm charts to remove possible references to image specific "
-"elements, replacing them with values overrides or conditionals."
-
-msgid "Elasticsearch chart"
-msgstr "Elasticsearch chart"
-
-msgid ""
-"Elasticsearch configured in a highly available manner with sane defaults"
-msgstr ""
-"Elasticsearch configured in a highly available manner with sane defaults"
-
-msgid "Elasticsearch configured to prevent memory swapping to disk"
-msgstr "Elasticsearch configured to prevent memory swapping to disk"
-
-msgid "Env Setup:"
-msgstr "Env Setup:"
-
-msgid "Etc ConfigMaps"
-msgstr "Etc ConfigMaps"
-
-msgid "Every Fluentbit send logs to Fluentd with Kubernetes metadata attached"
-msgstr "Every Fluentbit send logs to Fluentd with Kubernetes metadata attached"
-
-msgid ""
-"Every Kubernetes manifest inside Neutron chart can be enabled or disabled. "
-"That would provide flexibility to the operator, to choose which Neutron "
-"components are reusable with different type of SDNs. For example, neutron-"
-"server which is serving the API and configuring the database can be used "
-"with different types of SDN plugin, and provider of that SDN chart would not "
-"need to copy all logic from Neutron base chart to manage the API and "
-"database."
-msgstr ""
-"Every Kubernetes manifest inside Neutron chart can be enabled or disabled. "
-"That would provide flexibility to the operator, to choose which Neutron "
-"components are reusable with different type of SDNs. For example, neutron-"
-"server which is serving the API and configuring the database can be used "
-"with different types of SDN plugin, and provider of that SDN chart would not "
-"need to copy all logic from Neutron base chart to manage the API and "
-"database."
-
-msgid "Example OpenStack-Helm metrics requiring monitoring include:"
-msgstr "Example OpenStack-Helm metrics requiring monitoring include:"
-
-msgid "Example uses for centralized logging include:"
-msgstr "Example uses for centralised logging include:"
-
-msgid ""
-"Example uses for centralized logging with Fluentbit and Fluentd include:"
-msgstr ""
-"Example uses for centralised logging with Fluentbit and Fluentd include:"
-
-msgid "Examples of how these metrics can be used include:"
-msgstr "Examples of how these metrics can be used include:"
-
-msgid ""
-"Examples of how to set up the above under KubeADM and KubeSpray-based "
-"clusters must be documented as well."
-msgstr ""
-"Examples of how to set up the above under KubeADM and KubeSpray-based "
-"clusters must be documented as well."
-
-msgid "Execute script"
-msgstr "Execute script"
-
-msgid "Execute script."
-msgstr "Execute script."
-
-msgid ""
-"Exposes security/configuration features of software, allowing deployers to "
-"configure software to their needs."
-msgstr ""
-"Exposes security/configuration features of software, allowing deployers to "
-"configure software to their needs."
-
-msgid "External charts (Calico)"
-msgstr "External charts (Calico)"
-
-msgid "Find all backtraces for a tenant id's uuid"
-msgstr "Find all backtraces for a tenant id's UUID"
-
-msgid ""
-"Find all logged events that match a pattern (service, pod, behavior, etc)"
-msgstr ""
-"Find all logged events that match a pattern (service, pod, behaviour, etc)"
-
-msgid ""
-"First reasonable testing in gates would be to setup Linux Bridge and check "
-"if VM network connectivity is working."
-msgstr ""
-"First reasonable testing in gates would be to setup Linux Bridge and check "
-"if VM network connectivity is working."
-
-msgid ""
-"Fluentbit, Fluentd meet OpenStack-Helm's logging requirements for gathering, "
-"aggregating, and delivering of logged events. Fluntbit runs as a daemonset "
-"on each node and mounts the /var/lib/docker/containers directory. The Docker "
-"container runtime engine directs events posted to stdout and stderr to this "
-"directory on the host. Fluentbit then forward the contents of that directory "
-"to Fluentd. Fluentd runs as deployment at the designated nodes and expose "
-"service for Fluentbit to forward logs. Fluentd should then apply the "
-"Logstash format to the logs. Fluentd can also write Kubernetes and OpenStack "
-"metadata to the logs. Fluentd will then forward the results to Elasticsearch "
-"and to optionally Kafka. Elasticsearch indexes the logs in a logstash-* "
-"index by default. Kafka stores the logs in a 'logs' topic by default. Any "
-"external tool can then consume the 'logs' topic."
-msgstr ""
-"Fluentbit, Fluentd meet OpenStack-Helm's logging requirements for gathering, "
-"aggregating, and delivering of logged events. Fluntbit runs as a daemonset "
-"on each node and mounts the /var/lib/docker/containers directory. The Docker "
-"container runtime engine directs events posted to stdout and stderr to this "
-"directory on the host. Fluentbit then forward the contents of that directory "
-"to Fluentd. Fluentd runs as deployment at the designated nodes and expose "
-"service for Fluentbit to forward logs. Fluentd should then apply the "
-"Logstash format to the logs. Fluentd can also write Kubernetes and OpenStack "
-"metadata to the logs. Fluentd will then forward the results to Elasticsearch "
-"and to optionally Kafka. Elasticsearch indexes the logs in a logstash-* "
-"index by default. Kafka stores the logs in a 'logs' topic by default. Any "
-"external tool can then consume the 'logs' topic."
-
-msgid "Fluentbit-Fluentd logging chart"
-msgstr "Fluentbit-Fluentd logging chart"
-
-msgid "Fluentd chart"
-msgstr "Fluentd chart"
-
-msgid "Fluentd properly filters and categorizes logs"
-msgstr "Fluentd properly filters and categorises logs"
-
-msgid ""
-"Fluentd send aggregated logs to Elasticsearch for the internal use cases"
-msgstr ""
-"Fluentd send aggregated logs to Elasticsearch for the internal use cases"
-
-msgid "Fluentd then attaches Kubernetes and/or OpenStack metadata"
-msgstr "Fluentd then attaches Kubernetes and/or OpenStack metadata"
-
-msgid ""
-"Fluentd, Elasticsearch, and Kibana meet OpenStack-Helm's logging "
-"requirements for capture, storage and visualization of logged events.  "
-"Fluentd runs as a daemonset on each node and mounts the /var/lib/docker/"
-"containers directory. The Docker container runtime engine directs events "
-"posted to stdout and stderr to this directory on the host.  Fluentd should "
-"then declare the contents of that directory as an input stream, and use the "
-"fluent-plugin-elasticsearch plugin to apply the Logstash format to the "
-"logs.  Fluentd will also use the fluentd-plugin-kubernetes-metadata plugin "
-"to write Kubernetes metadata to the log record.  Fluentd will then forward "
-"the results to Elasticsearch, which indexes the logs in a logstash-* index "
-"by default.  The resulting logs can then be queried directly through "
-"Elasticsearch, or they can be viewed via Kibana. Kibana offers a dashboard "
-"that can create custom views on logged events, and Kibana integrates well "
-"with Elasticsearch by default."
-msgstr ""
-"Fluentd, Elasticsearch, and Kibana meet OpenStack-Helm's logging "
-"requirements for capture, storage and visualization of logged events.  "
-"Fluentd runs as a daemonset on each node and mounts the /var/lib/docker/"
-"containers directory. The Docker container runtime engine directs events "
-"posted to stdout and stderr to this directory on the host.  Fluentd should "
-"then declare the contents of that directory as an input stream, and use the "
-"fluent-plugin-elasticsearch plugin to apply the Logstash format to the "
-"logs.  Fluentd will also use the fluentd-plugin-kubernetes-metadata plugin "
-"to write Kubernetes metadata to the log record.  Fluentd will then forward "
-"the results to Elasticsearch, which indexes the logs in a logstash-* index "
-"by default.  The resulting logs can then be queried directly through "
-"Elasticsearch, or they can be viewed via Kibana. Kibana offers a dashboard "
-"that can create custom views on logged events, and Kibana integrates well "
-"with Elasticsearch by default."
-
-msgid ""
-"For Tenant Ceph, we will not be provisioning storage classes therefor, "
-"update script to not install ceph-provisioners chart as following."
-msgstr ""
-"For Tenant Ceph, we will not be provisioning storage classes therefore, "
-"update script to not install ceph-provisioners chart as following."
-
-msgid ""
-"For the ``Category B`` helm charts, an informal testing has been done in the "
-"past to ensure image independence. However, there is nothing exercising this "
-"independence in gates. Due to that, code of the helm charts might or might "
-"not require adapting."
-msgstr ""
-"For the ``Category B`` helm charts, an informal testing has been done in the "
-"past to ensure image independence. However, there is nothing exercising this "
-"independence in gates. Due to that, code of the helm charts might or might "
-"not require adapting."
-
-msgid ""
-"For this spec, we assume ``imagename1`` and ``imagename2`` are similarly "
-"built. This means we do not require any override per image. Instead we "
-"require a generic kind of override, per application, usable by all charts."
-msgstr ""
-"For this spec, we assume ``imagename1`` and ``imagename2`` are similarly "
-"built. This means we do not require any override per image. Instead we "
-"require a generic kind of override, per application, usable by all charts."
-
-msgid "Gate job testing VM network connectivity."
-msgstr "Gate job testing VM network connectivity."
-
-msgid "Gating"
-msgstr "Gating"
-
-msgid ""
-"Gating must prove that upgrades from each supported OpenStack version to the "
-"next operate flawlessly, using the default image set (LOCI).  Specifically, "
-"each OpenStack chart should be upgraded from one release to the next, and "
-"each infrastructure service from one minor version to the next.  Both the "
-"container image and configuration must be modified as part of this upgrade. "
-"At minimum, Newton to Ocata upgrade must be validated for the 1.0 release."
-msgstr ""
-"Gating must prove that upgrades from each supported OpenStack version to the "
-"next operate flawlessly, using the default image set (LOCI).  Specifically, "
-"each OpenStack chart should be upgraded from one release to the next, and "
-"each infrastructure service from one minor version to the next.  Both the "
-"container image and configuration must be modified as part of this upgrade. "
-"At minimum, Newton to Ocata upgrade must be validated for the 1.0 release."
-
-msgid "Grafana chart"
-msgstr "Grafana chart"
-
-msgid ""
-"Having services configured, also the services pod dependencies should be "
-"updated to reflect the new kind on L2 agent:"
-msgstr ""
-"Having services configured, also the services pod dependencies should be "
-"updated to reflect the new kind on L2 agent:"
-
-msgid "Helm"
-msgstr "Helm"
-
-msgid "Helm chart for Alertmanager"
-msgstr "Helm chart for Alertmanager"
-
-msgid "Helm chart for Elasticsearch"
-msgstr "Helm chart for Elasticsearch"
-
-msgid "Helm chart for Fluentbit-Fluentd Combination"
-msgstr "Helm chart for Fluentbit-Fluentd Combination"
-
-msgid "Helm chart for Fluentd"
-msgstr "Helm chart for Fluentd"
-
-msgid "Helm chart for Grafana"
-msgstr "Helm chart for Grafana"
-
-msgid "Helm chart for Kibana"
-msgstr "Helm chart for Kibana"
-
-msgid "Helm chart for Prometheus"
-msgstr "Helm chart for Prometheus"
-
-msgid "Helm charts for any appropriate Prometheus exporters"
-msgstr "Helm charts for any appropriate Prometheus exporters"
-
-msgid ""
-"Helm charts for which we are building images in osh-images. (Called further "
-"``Category B`` helm charts)"
-msgstr ""
-"Helm charts for which we are building images in osh-images. (Called further "
-"``Category B`` helm charts)"
-
-msgid ""
-"Helm charts for which we use official upstream images. (Called further "
-"``Category A`` helm charts)"
-msgstr ""
-"Helm charts for which we use official upstream images. (Called further "
-"``Category A`` helm charts)"
-
-msgid "Helm must be installed"
-msgstr "Helm must be installed"
-
-msgid ""
-"Helm test is the building block for all gating.  Each chart must integrate a "
-"helm-test script which validates proper functionality.  This is already a "
-"merge criterion for new charts, but a handful of older charts still need for "
-"helm test functionality to be added.  No additional charts will be merged "
-"prior to 1.0 unless they meet this requirement (and others in this document)."
-msgstr ""
-"Helm test is the building block for all gating.  Each chart must integrate a "
-"helm-test script which validates proper functionality.  This is already a "
-"merge criterion for new charts, but a handful of older charts still need for "
-"helm test functionality to be added.  No additional charts will be merged "
-"prior to 1.0 unless they meet this requirement (and others in this document)."
-
-msgid "Here is a list of the current specs:"
-msgstr "Here is a list of the current specs:"
-
-msgid "Host utilization: memory usage, CPU usage, disk I/O, network I/O, etc"
-msgstr "Host utilisation: memory usage, CPU usage, disk I/O, network I/O, etc"
-
-msgid "Hosts must use KubeDNS / CoreDNS for resolution"
-msgstr "Hosts must use KubeDNS / CoreDNS for resolution"
-
-msgid ""
-"I propose to extend the conf schema with generic software information. For "
-"example, for apache2:"
-msgstr ""
-"I propose to extend the conf schema with generic software information. For "
-"example, for apache2:"
-
-msgid "Identify etcd performance that could lead to cluster instability"
-msgstr "Identify etcd performance that could lead to cluster instability"
-
-msgid ""
-"Identify issues with Kubernetes components, such as: etcd, CNI, scheduler, "
-"etc"
-msgstr ""
-"Identify issues with Kubernetes components, such as: etcd, CNI, scheduler, "
-"etc"
-
-msgid ""
-"Identify issues with infrastructure components, such as RabbitMQ, mariadb, "
-"etc"
-msgstr ""
-"Identify issues with infrastructure components, such as RabbitMQ, Mariadb, "
-"etc"
-
-msgid "Identify opportunities for improving Prometheus's operation over time"
-msgstr "Identify opportunities for improving Prometheus's operation over time"
-
-msgid ""
-"If .Values.endpoints.oci_image_registry.auth.enabled will be set to true, "
-"then any containers created with the current service account will have the "
-"``imagePullSecrets`` automatically added to their spec and the secret will "
-"be passed to kubelet to be used for pulling images."
-msgstr ""
-"If .Values.endpoints.oci_image_registry.auth.enabled will be set to true, "
-"then any containers created with the current service account will have the "
-"``imagePullSecrets`` automatically added to their spec and the secret will "
-"be passed to kubelet to be used for pulling images."
-
-msgid ""
-"If :code:`.Values.manifests.daemonset_ovs_agent` will be set to false, "
-"neutron ovs agent would not be launched. In that matter, other type of L2 or "
-"L3 agent on compute node can be run."
-msgstr ""
-"If :code:`.Values.manifests.daemonset_ovs_agent` will be set to false, "
-"neutron ovs agent would not be launched. In that matter, other type of L2 or "
-"L3 agent on compute node can be run."
-
-msgid "Implement decomposable Neutron chart"
-msgstr "Implement decomposable Neutron chart"
-
-msgid "Implementation"
-msgstr "Implementation"
-
-msgid ""
-"In a secured deployment, TLS certificates are used to protect the transports "
-"amongst the various components.  In some cases, this requires additional "
-"mechanism to handle TLS offloading and to terminate the connection "
-"gracefully:"
-msgstr ""
-"In a secured deployment, TLS certificates are used to protect the transports "
-"amongst the various components.  In some cases, this requires additional "
-"mechanism to handle TLS offloading and to terminate the connection "
-"gracefully:"
-
-msgid "In above example OVS and Neutron OVS agent are disabled."
-msgstr "In above example OVS and Neutron OVS agent are disabled."
-
-msgid ""
-"In all cases, we will need to provide different ``profiles`` (in other "
-"words, overrides), to test different image providers use cases in CI."
-msgstr ""
-"In all cases, we will need to provide different ``profiles`` (in other "
-"words, overrides), to test different image providers use cases in CI."
-
-msgid ""
-"In order to maximize flexibility for operators, and to help facilitate "
-"upgrades to newer versions of containerized software without editing the "
-"chart itself, all configuration files will be specified dynamically based on "
-"`values.yaml` and overrides.  In most cases the config files will be "
-"generated based on the YAML values tree itself, and in some cases the config "
-"file content will be specified in `values.yaml` as a string literal."
-msgstr ""
-"In order to maximise flexibility for operators, and to help facilitate "
-"upgrades to newer versions of containerised software without editing the "
-"chart itself, all configuration files will be specified dynamically based on "
-"`values.yaml` and overrides.  In most cases the config files will be "
-"generated based on the YAML values tree itself, and in some cases the config "
-"file content will be specified in `values.yaml` as a string literal."
-
-msgid "In particular, these charts must move to OpenStack-Helm-Infra:"
-msgstr "In particular, these charts must move to OpenStack-Helm-Infra:"
-
-msgid ""
-"In the current openstack-helm, all charts provide an ``images:`` section in "
-"their ``values.yaml`` that have the container images references. By default, "
-"the container images are all downloaded from a registry hosted by Docker or "
-"Quay. However, the image references can be overridden by operators to "
-"download images from any OCI image registry. In the case that the OCI image "
-"registry has authentication turned on, kubelet would fail to download the "
-"images because the current Openstack-Helm does not provide a way to pass the "
-"OCI image registry credentials to kubernetes when pulling images."
-msgstr ""
-"In the current openstack-helm, all charts provide an ``images:`` section in "
-"their ``values.yaml`` that have the container images references. By default, "
-"the container images are all downloaded from a registry hosted by Docker or "
-"Quay. However, the image references can be overridden by operators to "
-"download images from any OCI image registry. In the case that the OCI image "
-"registry has authentication turned on, kubelet would fail to download the "
-"images because the current Openstack-Helm does not provide a way to pass the "
-"OCI image registry credentials to Kubernetes when pulling images."
-
-msgid "Include the URL of your Storyboard RFE:"
-msgstr "Include the URL of your Storyboard RFE:"
-
-msgid ""
-"Installing OVS requires Kubernetes worker node labeling with tag :code:"
-"`openvswitch=enabled`. To mark nodes where LB should be used, new tag will "
-"be introduced: :code:`linuxbridge=enabled`."
-msgstr ""
-"Installing OVS requires Kubernetes worker node labelling with tag :code:"
-"`openvswitch=enabled`. To mark nodes where LB should be used, new tag will "
-"be introduced: :code:`linuxbridge=enabled`."
-
-msgid "Instead of using nginx, haproxy can be used instead."
-msgstr "Instead of using Nginx, HAProxy can be used instead."
-
-msgid ""
-"Introducing a new SDN solution should consider how the above services are "
-"provided. It may be required to disable the built-in Neutron functionality."
-msgstr ""
-"Introducing a new SDN solution should consider how the above services are "
-"provided. It may be required to disable the built-in Neutron functionality."
-
-msgid ""
-"It is important to notice that the helm charts can be split in two "
-"categories for now:"
-msgstr ""
-"It is important to notice that the helm charts can be split in two "
-"categories for now:"
-
-msgid "Kibana chart"
-msgstr "Kibana chart"
-
-msgid "Kubernetes"
-msgstr "Kubernetes"
-
-msgid "Kubernetes metrics: pod status, replica availability, job status, etc"
-msgstr "Kubernetes metrics: pod status, replica availability, job status, etc"
-
-msgid ""
-"Kubernetes must enable mount propagation (until it is enabled by default)"
-msgstr ""
-"Kubernetes must enable mount propagation (until it is enabled by default)"
-
-msgid "L3 routing - creation of routers"
-msgstr "L3 routing - creation of routers"
-
-msgid "Labels assigned to nodes: node1, node2, node3:"
-msgstr "Labels assigned to nodes: node1, node2, node3:"
-
-msgid "Labels assigned to nodes: node4, node5, node6:"
-msgstr "Labels assigned to nodes: node4, node5, node6:"
-
-msgid ""
-"Labels for mon, osd, rgw, mgr and job have been updated for tenant Ceph."
-msgstr ""
-"Labels for mon, osd, rgw, mgr and job have been updated for tenant Ceph."
-
-msgid ""
-"Let's consider how new SDN can take advantage of disaggregated Neutron "
-"services architecture. First assumption is that neutron-server functionality "
-"would be common for all SDNs, as it provides networking API, database "
-"management and Keystone interaction. Required modifications are:"
-msgstr ""
-"Let's consider how new SDN can take advantage of disaggregated Neutron "
-"services architecture. First assumption is that neutron-server functionality "
-"would be common for all SDNs, as it provides networking API, database "
-"management and Keystone interaction. Required modifications are:"
-
-msgid ""
-"LinuxBridge installation with neutron chart takes advantaged of decomposable "
-"neutron chart in OSH. LinuxBridge agent will be added as daemonset, "
-"similarly how OVS is implemented. New value :code:`daemonset_lb_agent` "
-"should be added in :code:`neutron/values.yaml` in :code:`manifests` section:"
-msgstr ""
-"LinuxBridge installation with Neutron chart takes advantaged of decomposable "
-"Neutron chart in OSH. LinuxBridge agent will be added as daemonset, "
-"similarly how OVS is implemented. New value :code:`daemonset_lb_agent` "
-"should be added in :code:`neutron/values.yaml` in :code:`manifests` section:"
-
-msgid "LinuxBridge should be also enabled in :code:`manifests` section:"
-msgstr "LinuxBridge should be also enabled in :code:`manifests` section:"
-
-msgid ""
-"LinuxBridge should support external bridge configuration, as well as auto "
-"bridge add mechanism implemented for OVS."
-msgstr ""
-"LinuxBridge should support external bridge configuration, as well as auto "
-"bridge add mechanism implemented for OVS."
-
-msgid "Log aggregator deployment runs on a selected node as deployment"
-msgstr "Log aggregator deployment runs on a selected node as deployment"
-
-msgid "Log aggregator is able to send data to Elasticsearch and Kafka"
-msgstr "Log aggregator is able to send data to Elasticsearch and Kafka"
-
-msgid "Log aggregator should be scalable"
-msgstr "Log aggregator should be scalable"
-
-msgid "Log aggregator should have HA capability"
-msgstr "Log aggregator should have HA capability"
-
-msgid "Log aggregator should have a flexible output capability to choose from"
-msgstr "Log aggregator should have a flexible output capability to choose from"
-
-msgid "Log collection daemon runs on each node to forward logs to aggregator"
-msgstr "Log collection daemon runs on each node to forward logs to aggregator"
-
-msgid "Log collection daemon runs on each node to forward logs to storage"
-msgstr "Log collection daemon runs on each node to forward logs to storage"
-
-msgid "Log collection daemon should have a minimal server footprint"
-msgstr "Log collection daemon should have a minimal server footprint"
-
-msgid "Logging"
-msgstr "Logging"
-
-msgid "Logging Requirements"
-msgstr "Logging Requirements"
-
-msgid "Logging Use Cases"
-msgstr "Logging Use Cases"
-
-msgid "Logical Diagram"
-msgstr "Logical Diagram"
-
-msgid ""
-"Make following changes to script: 1 Replace occurrence of ``ceph-fs-uuid."
-"txt`` with ``tenant-ceph-fs-uuid.txt``"
-msgstr ""
-"Make following changes to script: 1 Replace occurrence of ``ceph-fs-uuid."
-"txt`` with ``tenant-ceph-fs-uuid.txt``"
-
-msgid ""
-"Make webserver binary path/arguments templated using ``values.yaml``. As "
-"expressed above, this allows us to provide different overrides per image/"
-"distribution to automatically wire things."
-msgstr ""
-"Make webserver binary path/arguments templated using ``values.yaml``. As "
-"expressed above, this allows us to provide different overrides per image/"
-"distribution to automatically wire things."
-
-msgid "Metadata- Provide proxy for Nova metadata service"
-msgstr "Metadata- Provide proxy for Nova metadata service"
-
-msgid "Monitoring"
-msgstr "Monitoring"
-
-msgid "Monitoring Requirements"
-msgstr "Monitoring Requirements"
-
-msgid "Monitoring Use Cases"
-msgstr "Monitoring Use Cases"
-
-msgid ""
-"More information about the blueprint + specification lifecycle can be found "
-"here_."
-msgstr ""
-"More information about the blueprint + specification lifecycle can be found "
-"here_."
-
-msgid "Multi-OS Support"
-msgstr "Multi-OS Support"
-
-msgid "Neutron multiple SDNs"
-msgstr "Neutron multiple SDNs"
-
-msgid "New charts"
-msgstr "New charts"
-
-msgid ""
-"Next, Neutron services like L3 routing, DHCP and metadata serving should be "
-"considered. If SDN provides its own implementation, the Neutron's default "
-"one should be disabled:"
-msgstr ""
-"Next, Neutron services like L3 routing, DHCP and metadata serving should be "
-"considered. If SDN provides its own implementation, the Neutron's default "
-"one should be disabled:"
-
-msgid "Nginx Sidecar"
-msgstr "Nginx Sidecar"
-
-msgid "No benchmark was done to evaluate:"
-msgstr "No benchmark was done to evaluate:"
-
-msgid ""
-"No change in testing is required, *per se*. It is expected the new software "
-"configuration would be tested with the current practices."
-msgstr ""
-"No change in testing is required, *per se*. It is expected the new software "
-"configuration would be tested with the current practices."
-
-msgid ""
-"No direct impact, as there is no change in the current software/"
-"configuration location, merely a templating change."
-msgstr ""
-"No direct impact, as there is no change in the current software/"
-"configuration location, merely a templating change."
-
-msgid "No impact"
-msgstr "No impact"
-
-msgid "No performance impact"
-msgstr "No performance impact"
-
-msgid "No security impact."
-msgstr "No security impact."
-
-msgid "None"
-msgstr "None"
-
-msgid ""
-"None more than this spec, as it should be relatively transparent for the "
-"user. However, extra documentation to explain the usage of "
-"``value_overrides`` would be welcomed."
-msgstr ""
-"None more than this spec, as it should be relatively transparent for the "
-"user. However, extra documentation to explain the usage of "
-"``value_overrides`` would be welcomed."
-
-msgid ""
-"Not providing a support of multiple images. This leads to ease of "
-"maintainance and reduced gate impact, with the risk of having less "
-"contributors. For available overrides, users would have to provide many "
-"overrides themselves, while this spec proposes a common community approach."
-msgstr ""
-"Not providing a support of multiple images. This leads to ease of "
-"maintenance and reduced gate impact, with the risk of having less "
-"contributors. For available overrides, users would have to provide many "
-"overrides themselves, while this spec proposes a common community approach."
-
-msgid "Note that mon_addr and mon_host have default mon port 6789."
-msgstr "Note that mon_addr and mon_host have default mon port 6789."
-
-msgid "OSH Logging, Monitoring, and Alerting"
-msgstr "OSH Logging, Monitoring, and Alerting"
-
-msgid ""
-"OVS is an alternative in Neutron reference architecture. It is already in "
-"tree."
-msgstr ""
-"OVS is an alternative in Neutron reference architecture. It is already in "
-"tree."
-
-msgid ""
-"On top of that, the newly provided `example_values/` must aim for being "
-"tested **as soon as possible upon delivery**. Without tests, those examples "
-"will decrepit. The changes in CI pipelines for making use of "
-"`example_values` is outside the scope of this spec."
-msgstr ""
-"On top of that, the newly provided `example_values/` must aim for being "
-"tested **as soon as possible upon delivery**. Without tests, those examples "
-"will decrepit. The changes in CI pipelines for making use of "
-"`example_values` is outside the scope of this spec."
-
-msgid ""
-"Only provide one way to configure software, and expect to always have the "
-"same versions. This is further away from the \"image independent\" contract, "
-"with extra burden: We will need to maintain a curated list of versions, deal "
-"with the differences of the defaults (selinux/apparmor profiles come to mind "
-"as path sensitive for example), and different expectations for operational "
-"teams (\"The code is not where I expect it to be in the image\"). Embracing "
-"difference could even allow deployers to have different expectations for "
-"images, for example: apache+mod_wsgi vs uwsgi standalone or uwsgi + nginx."
-msgstr ""
-"Only provide one way to configure software, and expect to always have the "
-"same versions. This is further away from the \"image independent\" contract, "
-"with extra burden: We will need to maintain a curated list of versions, deal "
-"with the differences of the defaults (selinux/apparmor profiles come to mind "
-"as path sensitive for example), and different expectations for operational "
-"teams (\"The code is not where I expect it to be in the image\"). Embracing "
-"difference could even allow deployers to have different expectations for "
-"images, for example: apache+mod_wsgi vs uwsgi standalone or uwsgi + nginx."
-
-msgid ""
-"OpenStack metrics: tenants, networks, flavors, floating IPs, quotas, etc"
-msgstr ""
-"OpenStack metrics: tenants, networks, flavours, floating IPs, quotas, etc"
-
-msgid "OpenStack-Helm 1.0 Requirements"
-msgstr "OpenStack-Helm 1.0 Requirements"
-
-msgid ""
-"OpenStack-Helm currently lacks a centralized mechanism for providing insight "
-"into the performance of the OpenStack services and infrastructure "
-"components. The log formats of the different components in OpenStack-Helm "
-"vary, which makes identifying causes for issues difficult across services.  "
-"To support operational readiness by default, OpenStack-Helm should include "
-"components for logging events in a common format, monitoring metrics at all "
-"levels, alerting and alarms for those metrics, and visualization tools for "
-"querying the logs and metrics in a single pane view."
-msgstr ""
-"OpenStack-Helm currently lacks a centralised mechanism for providing insight "
-"into the performance of the OpenStack services and infrastructure "
-"components. The log formats of the different components in OpenStack-Helm "
-"vary, which makes identifying causes for issues difficult across services.  "
-"To support operational readiness by default, OpenStack-Helm should include "
-"components for logging events in a common format, monitoring metrics at all "
-"levels, alerting and alarms for those metrics, and visualisation tools for "
-"querying the logs and metrics in a single pane view."
-
-msgid ""
-"OpenStack-Helm defines a centralized logging mechanism to provide insight "
-"into the state of the OpenStack services and infrastructure components as "
-"well as underlying Kubernetes platform. Among the requirements for a logging "
-"platform, where log data can come from and where log data need to be "
-"delivered are very variable. To support various logging scenarios, OpenStack-"
-"Helm should provide a flexible mechanism to meet with certain operation "
-"needs. This spec proposes fast and lightweight log forwarder and full "
-"featured log aggregator complementing each other providing a flexible and "
-"reliable solution. Especially, Fluentbit is proposed as a log forwarder and "
-"Fluentd is proposed as a main log aggregator and processor."
-msgstr ""
-"OpenStack-Helm defines a centralised logging mechanism to provide insight "
-"into the state of the OpenStack services and infrastructure components as "
-"well as underlying Kubernetes platform. Among the requirements for a logging "
-"platform, where log data can come from and where log data need to be "
-"delivered are very variable. To support various logging scenarios, OpenStack-"
-"Helm should provide a flexible mechanism to meet with certain operation "
-"needs. This spec proposes fast and lightweight log forwarder and full "
-"featured log aggregator complementing each other providing a flexible and "
-"reliable solution. Especially, Fluentbit is proposed as a log forwarder and "
-"Fluentd is proposed as a main log aggregator and processor."
-
-msgid ""
-"OpenStack-Helm documentation will be updated to indicate the usage of the "
-"nginx sidecar."
-msgstr ""
-"OpenStack-Helm documentation will be updated to indicate the usage of the "
-"Nginx sidecar."
-
-msgid "OpenStack-Helm for OpenStack services"
-msgstr "OpenStack-Helm for OpenStack services"
-
-msgid ""
-"OpenStack-Helm has developed a number of conventions around the format and "
-"ordering of charts' `values.yaml` file, in support of both reusable Helm-"
-"Toolkit functions and ease of developer ramp-up.  For 1.0 readiness, "
-"OpenStack-Helm must cement these conventions within a spec, as well as the "
-"ordering of `values.yaml` keys. These conventions must then be gated to "
-"guarantee conformity. The spec in progress can be found here [1]_."
-msgstr ""
-"OpenStack-Helm has developed a number of conventions around the format and "
-"ordering of charts' `values.yaml` file, in support of both reusable Helm-"
-"Toolkit functions and ease of developer ramp-up.  For 1.0 readiness, "
-"OpenStack-Helm must cement these conventions within a spec, as well as the "
-"ordering of `values.yaml` keys. These conventions must then be gated to "
-"guarantee conformity. The spec in progress can be found here [1]_."
-
-msgid ""
-"OpenStack-Helm has undergone rapid development and maturation over its "
-"lifetime, and is nearing the point of real-world readiness.  This spec "
-"details the functionality that must be implemented in OpenStack-Helm for it "
-"to be considered ready for a 1.0 release, as well as for general use."
-msgstr ""
-"OpenStack-Helm has undergone rapid development and maturation over its "
-"lifetime, and is nearing the point of real-world readiness.  This spec "
-"details the functionality that must be implemented in OpenStack-Helm for it "
-"to be considered ready for a 1.0 release, as well as for general use."
-
-msgid ""
-"OpenStack-Helm multinode guide includes scripts which are used to specify "
-"overrides and deploy charts."
-msgstr ""
-"OpenStack-Helm multinode guide includes scripts which are used to specify "
-"overrides and deploy charts."
-
-msgid ""
-"OpenStack-Helm supports a \"bring your own Kubernetes\" paradigm.  Any "
-"particular k8s configuration or feature requirements must be documented."
-msgstr ""
-"OpenStack-Helm supports a \"bring your own Kubernetes\" paradigm.  Any "
-"particular k8s configuration or feature requirements must be documented."
-
-msgid "OpenStack-Helm-Addons for ancillary services"
-msgstr "OpenStack-Helm-Addons for ancillary services"
-
-msgid "OpenStack-Helm-Infra for supporting services"
-msgstr "OpenStack-Helm-Infra for supporting services"
-
-msgid "Operating system"
-msgstr "Operating system"
-
-msgid ""
-"Operators should be able to use Openstack-Helm to deploy containerized "
-"openstack services with a docker registry has authentication turned on."
-msgstr ""
-"Operators should be able to use Openstack-Helm to deploy containerised "
-"OpenStack services with a docker registry has authentication turned on."
-
-msgid "Orchestration (heat)"
-msgstr "Orchestration (Heat)"
-
-msgid "Organizational auditing needs"
-msgstr "Organisational auditing needs"
-
-msgid "Other networking services provided by Neutron are:"
-msgstr "Other networking services provided by Neutron are:"
-
-msgid ""
-"Other services inside Neutron reference stack (L3/DHCP/metadata agents) are "
-"dependent on L2 connectivity agent. Thus, replacing OVS with LB would cause "
-"changes in mentioned services configuration."
-msgstr ""
-"Other services inside Neutron reference stack (L3/DHCP/metadata agents) are "
-"dependent on L2 connectivity agent. Thus, replacing OVS with LB would cause "
-"changes in mentioned services configuration."
-
-msgid ""
-"Our :ref:`images documentation` documentation claims to be independent of "
-"the image. However, some helm charts hard code paths of binaries, "
-"executables' runtime configurations, etc. Therefore, the image agnostic "
-"promise is broken."
-msgstr ""
-"Our :ref:`images documentation` documentation claims to be independent of "
-"the image. However, some Helm charts hard code paths of binaries, "
-"executables' runtime configurations, etc. Therefore, the image agnostic "
-"promise is broken."
-
-msgid "Performance Impact"
-msgstr "Performance Impact"
-
-msgid "Pete Birley <pete@port.direct>"
-msgstr "Pete Birley <pete@port.direct>"
-
-msgid "Platform Requirements"
-msgstr "Platform Requirements"
-
-msgid "PoC deployments of OpenStack-Helm"
-msgstr "PoC deployments of OpenStack-Helm"
-
-msgid "Port numbers for Ceph_Mon and Ceph_Mgr are different from default."
-msgstr "Port numbers for Ceph_Mon and Ceph_Mgr are different from default."
-
-msgid "Pre-pulling images on all nodes"
-msgstr "Pre-pulling images on all nodes"
-
-msgid "Prepare Host(s) for OpenStack-Helm deployment"
-msgstr "Prepare Host(s) for OpenStack-Helm deployment"
-
-msgid "Primary assignee:"
-msgstr "Primary assignee:"
-
-msgid "Primary assignees:"
-msgstr "Primary assignees:"
-
-msgid "Proactive monitoring of stack traces across all deployed infrastructure"
-msgstr ""
-"Proactive monitoring of stack traces across all deployed infrastructure"
-
-msgid "Problem Description"
-msgstr "Problem Description"
-
-msgid "Process and Tooling"
-msgstr "Process and Tooling"
-
-msgid "Project Specifications"
-msgstr "Project Specifications"
-
-msgid ""
-"Prometheus and Grafana meet OpenStack-Helm's monitoring requirements.  The "
-"Prometheus monitoring tool provides the ability to scrape targets for "
-"metrics over HTTP, and it stores these metrics in Prometheus's time-series "
-"database. The monitoring targets can be discovered via static configuration "
-"in Prometheus or through service discovery.  Prometheus includes a querying "
-"language that provides meaningful queries against the metrics gathered and "
-"supports the creation of rules to measure these metrics against for alerting "
-"purposes.  It also supports a wide range of Prometheus exporters for "
-"existing services, including Ceph and OpenStack.  Grafana supports "
-"Prometheus as a data source, and provides the ability to view the metrics "
-"gathered by Prometheus in a single pane dashboard.  Grafana can be "
-"bootstrapped with dashboards for each target scraped, or the dashboards can "
-"be added via Grafana's web interface directly.  To meet OpenStack-Helm's "
-"alerting needs, Alertmanager can be used to interface with Prometheus and "
-"send alerts based on Prometheus rule evaluations."
-msgstr ""
-"Prometheus and Grafana meet OpenStack-Helm's monitoring requirements.  The "
-"Prometheus monitoring tool provides the ability to scrape targets for "
-"metrics over HTTP, and it stores these metrics in Prometheus's time-series "
-"database. The monitoring targets can be discovered via static configuration "
-"in Prometheus or through service discovery.  Prometheus includes a querying "
-"language that provides meaningful queries against the metrics gathered and "
-"supports the creation of rules to measure these metrics against for alerting "
-"purposes.  It also supports a wide range of Prometheus exporters for "
-"existing services, including Ceph and OpenStack.  Grafana supports "
-"Prometheus as a data source, and provides the ability to view the metrics "
-"gathered by Prometheus in a single pane dashboard.  Grafana can be "
-"bootstrapped with dashboards for each target scraped, or the dashboards can "
-"be added via Grafana's web interface directly.  To meet OpenStack-Helm's "
-"alerting needs, Alertmanager can be used to interface with Prometheus and "
-"send alerts based on Prometheus rule evaluations."
-
-msgid "Prometheus chart"
-msgstr "Prometheus chart"
-
-msgid "Prometheus exporters"
-msgstr "Prometheus exporters"
-
-msgid "Proper directories mounted to retrieve logs from the node"
-msgstr "Proper directories mounted to retrieve logs from the node"
-
-msgid "Proposed Change"
-msgstr "Proposed Change"
-
-msgid ""
-"Proposes a common approach to software configuration, describing the distro/"
-"image specific differences for applications."
-msgstr ""
-"Proposes a common approach to software configuration, describing the distro/"
-"image specific differences for applications."
-
-msgid ""
-"Provide the credentials and add the manifest across all charts in OSH and "
-"OSH-infra"
-msgstr ""
-"Provide the credentials and add the manifest across all charts in OSH and "
-"OSH-infra"
-
-msgid "Providing the neutron plugin code."
-msgstr "Providing the Neutron plugin code."
-
-msgid "Provision of those services should be included inside SDN chart."
-msgstr "Provision of those services should be included inside SDN chart."
-
-msgid "Put .docker/config.json in docker/kubelet root directory on all nodes"
-msgstr "Put .docker/config.json in docker/kubelet root directory on all nodes"
-
-msgid "Record OpenStack service behavior and status"
-msgstr "Record OpenStack service behaviour and status"
-
-msgid "Record compute instance behavior across nodes and services"
-msgstr "Record compute instance behaviour across nodes and services"
-
-msgid ""
-"Reference the created secret by adding the ``imagePullSecrets:`` field to "
-"ServiceAccount resource template [2]_ in ``helm-toolkit/snippets/"
-"_kubernetes_pod_rbac_serviceaccount.tpl``. To handle it as optional, the "
-"field is wrapped in a conditional. For example,"
-msgstr ""
-"Reference the created secret by adding the ``imagePullSecrets:`` field to "
-"ServiceAccount resource template [2]_ in ``helm-toolkit/snippets/"
-"_kubernetes_pod_rbac_serviceaccount.tpl``. To handle it as optional, the "
-"field is wrapped in a conditional. For example,"
-
-msgid "References"
-msgstr "References"
-
-msgid ""
-"Release notes for the 1.0 release must be prepared, following OpenStack best "
-"practices.  The criteria for future changes that should be included in "
-"release notes in an ongoing fashion must be defined / documented as well."
-msgstr ""
-"Release notes for the 1.0 release must be prepared, following OpenStack best "
-"practices.  The criteria for future changes that should be included in "
-"release notes in an ongoing fashion must be defined / documented as well."
-
-msgid ""
-"Releated Specs: 1. OSH logging monitoring and alerting: https://review."
-"openstack.org/#/c/482687/"
-msgstr ""
-"Related Specs: 1. OSH logging monitoring and alerting: https://review."
-"openstack.org/#/c/482687/"
-
-msgid "Result from Steps 2, 3, 4:"
-msgstr "Result from Steps 2, 3, 4:"
-
-msgid "Results from Step 5, 6, 7:"
-msgstr "Results from Step 5, 6, 7:"
-
-msgid "SSH into VM and check it can access the internet"
-msgstr "SSH into VM and check it can access the Internet"
-
-msgid "Sane defaults for log retention and rotation policies"
-msgstr "Sane defaults for log retention and rotation policies"
-
-msgid "Script to update and execute: ``020-ingress.sh``"
-msgstr "Script to update and execute: ``020-ingress.sh``"
-
-msgid "Script to update and execute: ``030-ceph.sh``"
-msgstr "Script to update and execute: ``030-ceph.sh``"
-
-msgid "Script to update and execute: ``030-tenant-ceph.sh``"
-msgstr "Script to update and execute: ``030-tenant-ceph.sh``"
-
-msgid "Script to update and execute: ``040-tenant-ceph-ns-activate.sh``"
-msgstr "Script to update and execute: ``040-tenant-ceph-ns-activate.sh``"
-
-msgid "Script to update and execute: ``100-glance.sh``"
-msgstr "Script to update and execute: ``100-glance.sh``"
-
-msgid "Script to update and execute: ``110-cinder.sh``"
-msgstr "Script to update and execute: ``110-cinder.sh``"
-
-msgid "Script to update: ``090-tenant-ceph-radosgateway.sh``"
-msgstr "Script to update: ``090-tenant-ceph-radosgateway.sh``"
-
-msgid "Security Impact"
-msgstr "Security Impact"
-
-msgid "See above for documentation requirements."
-msgstr "See above for documentation requirements."
-
-msgid "See above for gating requirements."
-msgstr "See above for gating requirements."
-
-msgid "See above for the list of work items."
-msgstr "See above for the list of work items."
-
-msgid "Setup access to the external network from the development machine"
-msgstr "Setup access to the external network from the development machine"
-
-msgid "Single pane visualization capabilities"
-msgstr "Single pane visualisation capabilities"
-
-msgid "Specifications Process"
-msgstr "Specifications Process"
-
-msgid "Specifications Purpose"
-msgstr "Specifications Purpose"
-
-msgid ""
-"Specifications in this repository represent a consensus on the topics "
-"covered within.  They should be considered a mandate on the path forward "
-"with regards to the content on which they are drafted."
-msgstr ""
-"Specifications in this repository represent a consensus on the topics "
-"covered within.  They should be considered a mandate on the path forward "
-"with regards to the content on which they are drafted."
-
-msgid "StatefulSets"
-msgstr "StatefulSets"
-
-msgid "Support OCI image registry with authentication turned on"
-msgstr "Support OCI image registry with authentication turned on"
-
-msgid "Support linux bridge on neutron helm chart"
-msgstr "Support LinuxBridge on Neutron Helm chart"
-
-msgid "TODO - release management spec"
-msgstr "TODO - release management spec"
-
-msgid "Test Steps:"
-msgstr "Test Steps:"
-
-msgid "Testing"
-msgstr "Testing"
-
-msgid ""
-"Testing should include Helm tests for each of the included charts as well as "
-"an integration test in the gate."
-msgstr ""
-"Testing should include Helm tests for each of the included charts as well as "
-"an integration test in the gate."
-
-msgid ""
-"The LinuxBridge (LB) is Neutron's L2 agent, using linux kernel bridges as "
-"network configuration for VMs. Both OVS and LB are part of Neutron's Modular "
-"Layer 2 (ML2) framework, allowing to simultaneously utilize the variety of "
-"layer 2 networking technologies."
-msgstr ""
-"The LinuxBridge (LB) is Neutron's L2 agent, using linux kernel bridges as "
-"network configuration for VMs. Both OVS and LB are part of Neutron's Modular "
-"Layer 2 (ML2) framework, allowing to simultaneously utilise the variety of "
-"layer 2 networking technologies."
-
-msgid ""
-"The Neutron reference architecture provides mechanism_drivers OpenVSwitch "
-"(OVS) and linuxbridge (LB) with ML2 core_plugin framework."
-msgstr ""
-"The Neutron reference architecture provides mechanism_drivers OpenVSwitch "
-"(OVS) and LinuxBridge (LB) with ML2 core_plugin framework."
-
-msgid ""
-"The OpenStack-Helm Zuulv2 gates were written to allow use outside of "
-"OpenStack-Infra, to quickly set up a Kubernetes cluster, with the adoption "
-"of Zuulv3 underway it is logical to extend this paradigm to the Zuulv3 "
-"Playbooks. This will be driven via a ``Makefile`` that will allow developers "
-"to perform the following actions:"
-msgstr ""
-"The OpenStack-Helm Zuulv2 gates were written to allow use outside of "
-"OpenStack-Infra, to quickly set up a Kubernetes cluster, with the adoption "
-"of Zuulv3 underway it is logical to extend this paradigm to the Zuulv3 "
-"Playbooks. This will be driven via a ``Makefile`` that will allow developers "
-"to perform the following actions:"
-
-msgid ""
-"The OpenStack-Helm release process will be somewhat orthogonal to the "
-"OpenStack release process, and the differences and relationship between the "
-"two must be documented in a spec.  This will help folks quickly understand "
-"why OpenStack-Helm is a Release-Independent project from an OpenStack "
-"perspective."
-msgstr ""
-"The OpenStack-Helm release process will be somewhat orthogonal to the "
-"OpenStack release process, and the differences and relationship between the "
-"two must be documented in a spec.  This will help folks quickly understand "
-"why OpenStack-Helm is a Release-Independent project from an OpenStack "
-"perspective."
-
-msgid ""
-"The ``profiles`` yaml files (for example ``centos_7``, ``opensuse_15``) will "
-"be provided in each chart's ``example_values/`` directory. This folder will "
-"be masked to helm through a helmignore file. Its content is only for user "
-"consumption, not for inclusion in helm charts through the File directive. In "
-"other words, this is a user interface given for convenience merely using the "
-"abilities of the existing helm charts."
-msgstr ""
-"The ``profiles`` yaml files (for example ``centos_7``, ``opensuse_15``) will "
-"be provided in each chart's ``example_values/`` directory. This folder will "
-"be masked to Helm through a helmignore file. Its content is only for user "
-"consumption, not for inclusion in helm charts through the File directive. In "
-"other words, this is a user interface given for convenience merely using the "
-"abilities of the existing helm charts."
-
-msgid ""
-"The above chart must include sensible configuration values to make the "
-"logging platform usable by default. These include: proper input "
-"configurations for both Fluentbit and Fluentd, proper output configurations "
-"for both Fluentbit and Fluentd, proper metadata and formats applied to the "
-"logs via Fluentd."
-msgstr ""
-"The above chart must include sensible configuration values to make the "
-"logging platform usable by default. These include: proper input "
-"configurations for both Fluentbit and Fluentd, proper output configurations "
-"for both Fluentbit and Fluentd, proper metadata and formats applied to the "
-"logs via Fluentd."
-
-msgid ""
-"The alternative is to provide no organization layout for charts across all "
-"openstack-helm repositories."
-msgstr ""
-"The alternative is to provide no organization layout for charts across all "
-"openstack-helm repositories."
-
-msgid ""
-"The alternative would be to continue supporting the current bash driven "
-"containerized KubeADM and Kubelet approach, though this has the following "
-"issues:"
-msgstr ""
-"The alternative would be to continue supporting the current bash driven "
-"containerized KubeADM and Kubelet approach, though this has the following "
-"issues:"
-
-msgid ""
-"The bash scripts are largely undocumented and have grown to the point where "
-"they are very hard for a new developer to work on."
-msgstr ""
-"The bash scripts are largely undocumented and have grown to the point where "
-"they are very hard for a new developer to work on."
-
-msgid ""
-"The code can be supplied as modified neutron server image, or plugin can be "
-"mounted to original image. The :code:`manifests` section in :code:`neutron/"
-"values.yaml` should be enabled for below components:"
-msgstr ""
-"The code can be supplied as modified Neutron server image, or plugin can be "
-"mounted to original image. The :code:`manifests` section in :code:`neutron/"
-"values.yaml` should be enabled for below components:"
-
-msgid ""
-"The containerized Kubelet cannot survive a restart, as it does not setup "
-"mounts correctly."
-msgstr ""
-"The containerised Kubelet cannot survive a restart, as it does not setup "
-"mounts correctly."
-
-msgid ""
-"The credentials for the registry could be exposed by running the kubectl "
-"command: kubectl get secret <secret-name> --output=\"jsonpath={.data.\\."
-"dockerconfigjson}\" | base64 --decode"
-msgstr ""
-"The credentials for the registry could be exposed by running the kubectl "
-"command: kubectl get secret <secret-name> --output=\"jsonpath={.data.\\."
-"dockerconfigjson}\" | base64 --decode"
-
-msgid ""
-"The default ``values.yaml`` need to expose those abilities, by adding a new "
-"series of keys/values to add the necessary features."
-msgstr ""
-"The default ``values.yaml`` need to expose those abilities, by adding a new "
-"series of keys/values to add the necessary features."
-
-msgid "The detailed proposes change are described as following:"
-msgstr "The detailed proposes change are described as following:"
-
-msgid ""
-"The developer documentation in OpenStack-Helm should be updated to guide key "
-"ordering on value files."
-msgstr ""
-"The developer documentation in OpenStack-Helm should be updated to guide key "
-"ordering on value files."
-
-msgid ""
-"The developer documentation in OpenStack-Helm should be updated to match the "
-"gated developer deploy process."
-msgstr ""
-"The developer documentation in OpenStack-Helm should be updated to match the "
-"gated developer deploy process."
-
-msgid "The existing schema for images is the following:"
-msgstr "The existing schema for images is the following:"
-
-msgid ""
-"The following work items need to be completed for this Specification to be "
-"implemented."
-msgstr ""
-"The following work items need to be completed for this Specification to be "
-"implemented."
-
-msgid ""
-"The following work items need to be completed for this specification to be "
-"implemented."
-msgstr ""
-"The following work items need to be completed for this specification to be "
-"implemented."
-
-msgid ""
-"The last thing to be considered is VM network virtualization. What engine "
-"does SDN use? It is OpenVSwitch, Linux Bridges or l3 routing (no l2 "
-"connectivity). If SDN is using the OpenVSwitch, it can take advantage of "
-"existing OVS daemonsets. Any modification that would be required to OVS "
-"manifests can be included in base Neutron chart as a configurable option. In "
-"that way, the features of OVS can be shared between different SDNs. When "
-"using the OVS, default Neutron L2 agent should be disabled, but OVS-DB and "
-"OVS-vswitchd can be left enabled."
-msgstr ""
-"The last thing to be considered is VM network virtualization. What engine "
-"does SDN use? It is OpenVSwitch, Linux Bridges or L3 routing (no L2 "
-"connectivity). If SDN is using the OpenVSwitch, it can take advantage of "
-"existing OVS daemonsets. Any modification that would be required to OVS "
-"manifests can be included in base Neutron chart as a configurable option. In "
-"that way, the features of OVS can be shared between different SDNs. When "
-"using the OVS, default Neutron L2 agent should be disabled, but OVS-DB and "
-"OVS-vswitchd can be left enabled."
-
-msgid ""
-"The monolithic Ceph chart does not allow for following Ceph upgrade best "
-"practices, namely to upgrade Mons, OSDs, and client services in that order. "
-"The Ceph chart must therefore be split into at least three charts (one for "
-"each of the above upgrade phases) prior to 1.0 to ensure smooth in-place "
-"upgradability."
-msgstr ""
-"The monolithic Ceph chart does not allow for following Ceph upgrade best "
-"practices, namely to upgrade Mons, OSDs, and client services in that order. "
-"The Ceph chart must therefore be split into at least three charts (one for "
-"each of the above upgrade phases) prior to 1.0 to ensure smooth in-place "
-"upgradability."
-
-msgid ""
-"The move to Zuulv3 native operation of the OpenStack-Helm gates mean there "
-"would be no code reuse between the gate and developer environments, so "
-"supporting the existing code for Zuulv2 will incur significant tech-debt."
-msgstr ""
-"The move to Zuulv3 native operation of the OpenStack-Helm gates mean there "
-"would be no code reuse between the gate and developer environments, so "
-"supporting the existing code for Zuulv2 will incur significant tech-debt."
-
-msgid ""
-"The option ``enabled:`` under ``auth:`` and the manifest ``secret_registry:"
-"`` provide the ability for operator to determine whether they would like to "
-"have secrets generated and passed to kubernetes for pulling images."
-msgstr ""
-"The option ``enabled:`` under ``auth:`` and the manifest ``secret_registry:"
-"`` provide the ability for operator to determine whether they would like to "
-"have secrets generated and passed to Kubernetes for pulling images."
-
-msgid ""
-"The performance aspect of these point are restricted to deployment, and have "
-"no performance impact on operations."
-msgstr ""
-"The performance aspect of these point are restricted to deployment, and have "
-"no performance impact on operations."
-
-msgid "The proposal includes the following:"
-msgstr "The proposal includes the following:"
-
-msgid "The proposed requirements for a 1.0 release are as follows:"
-msgstr "The proposed requirements for a 1.0 release are as follows:"
-
-msgid ""
-"The proposes change would be to add in :code:`neutron/values.yaml` new "
-"section with boolean values describing which Neutron's Kubernetes resources "
-"should be enabled:"
-msgstr ""
-"The proposes change would be to add in :code:`neutron/values.yaml` new "
-"section with boolean values describing which Neutron's Kubernetes resources "
-"should be enabled:"
-
-msgid "The requirements for a logging collector/aggregator include:"
-msgstr "The requirements for a logging collector/aggregator include:"
-
-msgid "The requirements for a logging platform include:"
-msgstr "The requirements for a logging platform include:"
-
-msgid "The requirements for a monitoring platform include:"
-msgstr "The requirements for a monitoring platform include:"
-
-msgid ""
-"The secret would not be created with the default option ``enabled: false`` "
-"and ``secret_registry: true``. To enable secret creation, operator should "
-"override ``enabled:`` to true. The above example shows the default "
-"credentials, operator should override the ``username:`` and ``password:`` "
-"under ``auth:`` section to provide their own credentials."
-msgstr ""
-"The secret would not be created with the default option ``enabled: false`` "
-"and ``secret_registry: true``. To enable secret creation, operator should "
-"override ``enabled:`` to true. The above example shows the default "
-"credentials, operator should override the ``username:`` and ``password:`` "
-"under ``auth:`` section to provide their own credentials."
-
-msgid ""
-"The testing will be performed by the OpenStack-Helm gate to demonstrate the "
-"sidecar container correctly routes traffic to the correct services."
-msgstr ""
-"The testing will be performed by the OpenStack-Helm gate to demonstrate the "
-"sidecar container correctly routes traffic to the correct services."
-
-msgid ""
-"The top-level keys are based on the organizational keys common to all charts "
-"in the openstack-helm repositories.  The top-level keys are strictly ordered "
-"according to function, which creates a common organization pattern between "
-"all charts."
-msgstr ""
-"The top-level keys are based on the organisational keys common to all charts "
-"in the openstack-helm repositories.  The top-level keys are strictly ordered "
-"according to function, which creates a common organisation pattern between "
-"all charts."
-
-msgid ""
-"Then, add manifest ``secret-registry.yaml`` in ``templates/`` to leverage "
-"the function that will be added in helm-toolkit to create the secret. For "
-"example:"
-msgstr ""
-"Then, add manifest ``secret-registry.yaml`` in ``templates/`` to leverage "
-"the function that will be added in helm-toolkit to create the secret. For "
-"example:"
-
-msgid ""
-"Then, inside Kubernetes manifests, add global if statement, deciding if "
-"given manifest should be declared on Kubernetes API, for example :code:"
-"`neutron/templates/daemonset-ovs-agent.yaml`:"
-msgstr ""
-"Then, inside Kubernetes manifests, add global if statement, deciding if "
-"given manifest should be declared on Kubernetes API, for example :code:"
-"`neutron/templates/daemonset-ovs-agent.yaml`:"
-
-msgid ""
-"There is no significant performance impact as the traffic will be locally "
-"routed (via 127.0.0.1) and may potentially improve performance for services "
-"whose native TLS handling is inefficient."
-msgstr ""
-"There is no significant performance impact as the traffic will be locally "
-"routed (via 127.0.0.1) and may potentially improve performance for services "
-"whose native TLS handling is inefficient."
-
-msgid ""
-"There will be no security impact, as it will deploy the charts in OpenStack-"
-"Helm[-infra/-addons] upon a reference KubeADM administered cluster."
-msgstr ""
-"There will be no security impact, as it will deploy the charts in OpenStack-"
-"Helm[-infra/-addons] upon a reference KubeADM administered cluster."
-
-msgid "This Ceph cluster will be used by Cinder and Glance as storage backend."
-msgstr ""
-"This Ceph cluster will be used by Cinder and Glance as storage backend."
-
-msgid ""
-"This Ceph cluster will be used for k8s RBD storage (pvc). This can be used "
-"by entire Kubernetes cluster."
-msgstr ""
-"This Ceph cluster will be used for k8s RBD storage (pvc). This can be used "
-"by entire Kubernetes cluster."
-
-msgid "This approach:"
-msgstr "This approach:"
-
-msgid ""
-"This deployment process will be gated, to ensure that the development the "
-"environment is consistently working against ``master`` for the OpenStack-"
-"Helm repositories."
-msgstr ""
-"This deployment process will be gated, to ensure that the development the "
-"environment is consistently working against ``master`` for the OpenStack-"
-"Helm repositories."
-
-msgid ""
-"This enhances the system's security design by allowing pods with services "
-"that cannot natively manage TLS to secure the traffic to the service pod."
-msgstr ""
-"This enhances the system's security design by allowing pods with services "
-"that cannot natively manage TLS to secure the traffic to the service pod."
-
-msgid "This feature will not affect the performance of OpenStack-Helm."
-msgstr "This feature will not affect the performance of OpenStack-Helm."
-
-msgid ""
-"This guide shows how to setup multiple Ceph clusters. One Ceph cluster will "
-"be used for k8s RBD storage and while other Ceph cluster will be for tenant "
-"facing storage backend for Cinder and Glance."
-msgstr ""
-"This guide shows how to setup multiple Ceph clusters. One Ceph cluster will "
-"be used for k8s RBD storage and while other Ceph cluster will be for tenant "
-"facing storage backend for Cinder and Glance."
-
-msgid ""
-"This spec describes a point-in-time readiness for OpenStack-Helm 1.0, after "
-"which it will be for historical reference only."
-msgstr ""
-"This spec describes a point-in-time readiness for OpenStack-Helm 1.0, after "
-"which it will be for historical reference only."
-
-msgid ""
-"This spec describes a wide variety of self-contained work efforts, which "
-"will be implemented individually by the whole OpenStack-Helm team."
-msgstr ""
-"This spec describes a wide variety of self-contained work efforts, which "
-"will be implemented individually by the whole OpenStack-Helm team."
-
-msgid ""
-"This spec lays out the criteria for a stable and reliable 1.0 release, which "
-"can serve as the basis for real-world use as well as ongoing development. "
-"The alternative approaches would be to either iterate indefinitely without "
-"defining a 1.0 release, which would fail to signal to operators the point at "
-"which the platform is ready for real-world use; or, to define a 1.0 release "
-"which fails to satisfy key features which real-world operators need."
-msgstr ""
-"This spec lays out the criteria for a stable and reliable 1.0 release, which "
-"can serve as the basis for real-world use as well as ongoing development. "
-"The alternative approaches would be to either iterate indefinitely without "
-"defining a 1.0 release, which would fail to signal to operators the point at "
-"which the platform is ready for real-world use; or, to define a 1.0 release "
-"which fails to satisfy key features which real-world operators need."
-
-msgid ""
-"This spec will be worked helm chart by helm chart, starting with keystone."
-msgstr ""
-"This spec will be worked Helm chart by Helm chart, starting with Keystone."
-
-msgid ""
-"This specification also proposes to restrict the addition of any new top-"
-"level keys in charts across all OpenStack-Helm repositories, in order to "
-"maintain the common structure the ordering creates.  The addition of a new "
-"top-level key shall be agreed upon by the OpenStack-Helm team on a case-by-"
-"case basis.  The addition of any new top-level keys should be documented, "
-"and this specification shall be amended to account for any added keys."
-msgstr ""
-"This specification also proposes to restrict the addition of any new top-"
-"level keys in charts across all OpenStack-Helm repositories, in order to "
-"maintain the common structure the ordering creates.  The addition of a new "
-"top-level key shall be agreed upon by the OpenStack-Helm team on a case-by-"
-"case basis.  The addition of any new top-level keys should be documented, "
-"and this specification shall be amended to account for any added keys."
-
-msgid ""
-"This specification proposes defining entries in the values.yaml file into "
-"two categories: top-level keys, and their children (sub-level) keys."
-msgstr ""
-"This specification proposes defining entries in the values.yaml file into "
-"two categories: top-level keys, and their children (sub-level) keys."
-
-msgid ""
-"This specification proposes introducing a uniform values.yaml structure "
-"across all charts in openstack-helm, openstack-helm-infra, and openstack-"
-"helm-addons, with the goal of reducing the complexities of working across "
-"multiple charts and reducing the effort for creating new charts."
-msgstr ""
-"This specification proposes introducing a uniform values.yaml structure "
-"across all charts in openstack-helm, openstack-helm-infra, and openstack-"
-"helm-addons, with the goal of reducing the complexities of working across "
-"multiple charts and reducing the effort for creating new charts."
-
-msgid ""
-"This specification proposes to add a nginx sidecar container to the pod for "
-"service that requires the tls offloading. The nginx can be used to handle "
-"the TLS offoading and terminate the TLS connection, and routes the traffic "
-"to the service via localhost (127.0.0.1)."
-msgstr ""
-"This specification proposes to add a Nginx sidecar container to the pod for "
-"service that requires the TLS offloading. The Nginx can be used to handle "
-"the TLS offloading and terminate the TLS connection, and routes the traffic "
-"to the service via localhost (127.0.0.1)."
-
-msgid ""
-"This specification will address enablement of LinuxBridge network "
-"virtualization for OpenStack Helm (OSH). LinuxBridge is second available "
-"networking technology in Neutron's reference architecture. The first one is "
-"OVS, that is already implemented in OSH."
-msgstr ""
-"This specification will address enablement of LinuxBridge network "
-"virtualization for OpenStack Helm (OSH). LinuxBridge is second available "
-"networking technology in Neutron's reference architecture. The first one is "
-"OVS, that is already implemented in OSH."
-
-msgid "Time-series database for collected metrics"
-msgstr "Time-series database for Collected metrics"
-
-msgid "Time-series database for logs collected"
-msgstr "Time-series database for logs collected"
-
-msgid ""
-"To be able to install Neutron with multiple possible SDNs as networking "
-"plugin, Neutron chart should be modified to enable installation of base "
-"services with decomposable approach. This means that operator can define "
-"which components from base Neutron chart should be installed, and which "
-"should not. This plus proper configuration of Neutron chart would enable "
-"operator to flexibly provision OpenStack with chosen SDN."
-msgstr ""
-"To be able to install Neutron with multiple possible SDNs as networking "
-"plugin, Neutron chart should be modified to enable installation of base "
-"services with decomposable approach. This means that operator can define "
-"which components from base Neutron chart should be installed, and which "
-"should not. This plus proper configuration of Neutron chart would enable "
-"operator to flexibly provision OpenStack with chosen SDN."
-
-msgid ""
-"To be able to pull images from an OCI image registry which has the "
-"authentication turned on, kubernetes needs credentials. For each chart, a "
-"new ``endpoints:`` entry could be added in ``values.yaml`` to provide image "
-"credentials, a secret needs to be generated to hold the credentials and the "
-"``imagePullSecrets:`` field should be added in each service account to "
-"specify which secret should be used to get the credentials from when pulling "
-"images by kubelet."
-msgstr ""
-"To be able to pull images from an OCI image registry which has the "
-"authentication turned on, Kubernetes needs credentials. For each chart, a "
-"new ``endpoints:`` entry could be added in ``values.yaml`` to provide image "
-"credentials, a secret needs to be generated to hold the credentials and the "
-"``imagePullSecrets:`` field should be added in each service account to "
-"specify which secret should be used to get the credentials from when pulling "
-"images by kubelet."
-
-msgid ""
-"To enable new SDN solution, there should be separate chart created, which "
-"would handle the deployment of service, setting up the database and any "
-"related networking functionality that SDN is providing."
-msgstr ""
-"To enable new SDN solution, there should be separate chart created, which "
-"would handle the deployment of service, setting up the database and any "
-"related networking functionality that SDN is providing."
-
-msgid ""
-"To facilitate effective collaboration and communication across the OpenStack-"
-"Helm community team, work items for the enhancements above will be captured "
-"in Storyboard.  Therefore, migration from Launchpad to Storyboard must be "
-"accomplished prior to the 1.0 release.  Going forward, Storyboard will be "
-"leveraged as a tool to collaboratively define and communicate the OpenStack-"
-"Helm roadmap."
-msgstr ""
-"To facilitate effective collaboration and communication across the OpenStack-"
-"Helm community team, work items for the enhancements above will be captured "
-"in Storyboard.  Therefore, migration from Launchpad to Storyboard must be "
-"accomplished prior to the 1.0 release.  Going forward, Storyboard will be "
-"leveraged as a tool to collaboratively define and communicate the OpenStack-"
-"Helm roadmap."
-
-msgid ""
-"To minimize the performance impacts, the following should be considered:"
-msgstr ""
-"To minimise the performance impacts, the following should be considered:"
-
-msgid ""
-"To successfully enforce the ordering defined here, our gates need a method "
-"for validating the ordering and the schema of all values.yaml files.  "
-"Without such a mechanism, the overhead associated with properly reviewing "
-"and validating any changes to the structure will be substantial.  A tool, "
-"such as yamllint, would provide this functionality and remove the need to "
-"write a custom validation tool"
-msgstr ""
-"To successfully enforce the ordering defined here, our gates need a method "
-"for validating the ordering and the schema of all values.yaml files.  "
-"Without such a mechanism, the overhead associated with properly reviewing "
-"and validating any changes to the structure will be substantial.  A tool, "
-"such as yamllint, would provide this functionality and remove the need to "
-"write a custom validation tool"
-
-msgid "Top-level keys are placed in this order:"
-msgstr "Top-level keys are placed in this order:"
-
-msgid "Topic: osh-1.0-requirements_"
-msgstr "Topic: osh-1.0-requirements_"
-
-msgid "Trigger alerts when desired replicas fall below required number"
-msgstr "Trigger alerts when desired replicas fall below required number"
-
-msgid "Trigger alerts when services become unavailable or unresponsive"
-msgstr "Trigger alerts when services become unavailable or unresponsive"
-
-msgid "Under storage: mon directory have been updated."
-msgstr "Under storage: mon directory have been updated."
-
-msgid ""
-"Under storageclass section, values for following have been updated: "
-"ceph_configmap_name, admin_secret_name, admin_secret_namespace, "
-"user_secret_name"
-msgstr ""
-"Under storageclass section, values for following have been updated: "
-"ceph_configmap_name, admin_secret_name, admin_secret_namespace, "
-"user_secret_name"
-
-msgid ""
-"Update ``helm toolkit`` to provide snippet to create the nginx sidecar "
-"container for the services that require it."
-msgstr ""
-"Update ``helm toolkit`` to provide snippet to create the Nginx sidecar "
-"container for the services that require it."
-
-msgid ""
-"Update helm-toolkit serviceaccount template to pass the secret in a "
-"conditional"
-msgstr ""
-"Update helm-toolkit serviceaccount template to pass the secret in a "
-"conditional"
-
-msgid ""
-"Update helm-toolkit to provide manifest to create secret for registry "
-"authentication"
-msgstr ""
-"Update helm-toolkit to provide manifest to create secret for registry "
-"authentication"
-
-msgid "Update of Developer Documentation"
-msgstr "Update of Developer Documentation"
-
-msgid ""
-"Update of Makefile for OpenStack-Helm-Infra to allow modular deployment of "
-"components"
-msgstr ""
-"Update of Makefile for OpenStack-Helm-Infra to allow modular deployment of "
-"components"
-
-msgid "Update of developer documentation"
-msgstr "Update of developer documentation"
-
-msgid "Update relevant Documentation."
-msgstr "Update relevant Documentation."
-
-msgid "Update script as following:"
-msgstr "Update script as following:"
-
-msgid "Update script overrides as following:"
-msgstr "Update script overrides as following:"
-
-msgid "Update script to include namespace ``tenant-ceph`` as shown below."
-msgstr "Update script to include namespace ``tenant-ceph`` as shown below."
-
-msgid ""
-"Update script with following overrides. Note: The original RBD provisioner "
-"is now deprecated. The CSI RBD provisioner is selected here. If you prefer "
-"the original non-CSI RBD provisioner, then set rbd_provisioner to true "
-"instead."
-msgstr ""
-"Update script with following overrides. Note: The original RBD provisioner "
-"is now deprecated. The CSI RBD provisioner is selected here. If you prefer "
-"the original non-CSI RBD provisioner, then set rbd_provisioner to true "
-"instead."
-
-msgid "Update script with following overrides:"
-msgstr "Update script with following overrides:"
-
-msgid "Update script's override section with following:"
-msgstr "Update script's override section with following:"
-
-msgid "Update service charts to use the updated ``helm toolkit``."
-msgstr "Update service charts to use the updated ``helm toolkit``."
-
-msgid "Use Cases"
-msgstr "Use Cases"
-
-msgid "Use case"
-msgstr "Use case"
-
-msgid "Use cases"
-msgstr "Use cases"
-
-msgid ""
-"Use default overrides and execute following scripts as per OSH guide steps:"
-msgstr ""
-"Use default overrides and execute following scripts as per OSH guide steps:"
-
-msgid "VM networking performance would be dependent of SDN used."
-msgstr "VM networking performance would be dependent of SDN used."
-
-msgid ""
-"VM networking performance would be dependent on linux bridge implementation."
-msgstr ""
-"VM networking performance would be dependent on Linux bridge implementation."
-
-msgid "Values File Ordering"
-msgstr "Values File Ordering"
-
-msgid ""
-"Version requirements for the following must be documented and maintained:"
-msgstr ""
-"Version requirements for the following must be documented and maintained:"
-
-msgid ""
-"Visualize logged events to determine if an event is recurring or an outlier"
-msgstr ""
-"Visualise logged events to determine if an event is recurring or an outlier"
-
-msgid ""
-"Visualize performance to identify trends in traffic or utilization over time"
-msgstr ""
-"Visualise performance to identify trends in traffic or utilisation over time"
-
-msgid "We are disabling rbd and cephfs provisioners."
-msgstr "We are disabling rbd and cephfs provisioners."
-
-msgid ""
-"We need to adapt all the helm charts to remove the hard-coded bits, be image "
-"agnostic, to allow users to bring their own images."
-msgstr ""
-"We need to adapt all the Helm charts to remove the hard-coded bits, be image "
-"agnostic, to allow users to bring their own images."
-
-msgid "Web UI (horizon)"
-msgstr "Web UI (Horizon)"
-
-msgid ""
-"When possible, ``values_overrides/`` will refer to existing ``helm-toolkit`` "
-"functions to avoid repeating ourselves."
-msgstr ""
-"When possible, ``values_overrides/`` will refer to existing ``helm-toolkit`` "
-"functions to avoid repeating ourselves."
-
-msgid "Work Items"
-msgstr "Work Items"
-
-msgid ""
-"Work is underway to refactor common manifest patterns into reusable snippets "
-"in Helm-Toolkit.  The following manifests have yet to be combined:"
-msgstr ""
-"Work is underway to refactor common manifest patterns into reusable snippets "
-"in Helm-Toolkit.  The following manifests have yet to be combined:"
-
-msgid "Worker Deployments"
-msgstr "Worker Deployments"
-
-msgid "``040-ceph-ns-activate.sh``"
-msgstr "``040-ceph-ns-activate.sh``"
-
-msgid "``050-mariadb.sh``"
-msgstr "``050-mariadb.sh``"
-
-msgid "``060-rabbitmq.sh``"
-msgstr "``060-rabbitmq.sh``"
-
-msgid "``070-memcached.sh``"
-msgstr "``070-memcached.sh``"
-
-msgid "``080-keystone.sh``"
-msgstr "``080-keystone.sh``"
-
-msgid "``Ceph ConfigMaps``"
-msgstr "``Ceph ConfigMaps``"
-
-msgid "``Ceph Pods``"
-msgstr "``Ceph Pods``"
-
-msgid "``Ceph Status``"
-msgstr "``Ceph Status``"
-
-msgid "``Ceph endpoints``"
-msgstr "``Ceph endpoints``"
-
-msgid "``Ceph for RBD related labels:``"
-msgstr "``Ceph for RBD related labels:``"
-
-msgid "``Ceph for Tenant related labels:``"
-msgstr "``Ceph for Tenant related labels:``"
-
-msgid "``Ceph secrets``"
-msgstr "``Ceph secrets``"
-
-msgid "``Ceph services``"
-msgstr "``Ceph services``"
-
-msgid "``Openstack PV list``"
-msgstr "``Openstack PV list``"
-
-msgid "``Openstack Pods:``"
-msgstr "``Openstack Pods:``"
-
-msgid "``Openstack endpoints``"
-msgstr "``Openstack endpoints``"
-
-msgid "``Openstack secrets``"
-msgstr "``Openstack secrets``"
-
-msgid "``Openstack services``"
-msgstr "``Openstack services``"
-
-msgid "``Storage on node1, node2, node3:``"
-msgstr "``Storage on node1, node2, node3:``"
-
-msgid "``Storage on node4, node5, node6:``"
-msgstr "``Storage on node4, node5, node6:``"
-
-msgid "``ceph-mon-etc (ceph.conf)``"
-msgstr "``ceph-mon-etc (ceph.conf)``"
-
-msgid ""
-"``cephfs_provisioner: false`` and ``provision_storage_class: false`` are set "
-"to false to disable cephfs. ``deployment_mds: false`` is set to disable ceph-"
-"mds"
-msgstr ""
-"``cephfs_provisioner: false`` and ``provision_storage_class: false`` are set "
-"to false to disable cephfs. ``deployment_mds: false`` is set to disable ceph-"
-"mds"
-
-msgid "``for CHART in ceph-mon ceph-osd ceph-client; do``"
-msgstr "``for CHART in ceph-mon ceph-osd ceph-client; do``"
-
-msgid ""
-"``k8s node list with labels`` After applying above labels, node labels "
-"should look like following."
-msgstr ""
-"``k8s node list with labels`` After applying above labels, node labels "
-"should look like following."
-
-msgid "``k8s storageclass``"
-msgstr "``k8s storageclass``"
-
-msgid "``netstat ceph mon port``"
-msgstr "``netstat ceph mon port``"
-
-msgid "`values.yaml` changes"
-msgstr "`values.yaml` changes"
-
-msgid "bootstrap * sub-keys (alphabetical order)"
-msgstr "bootstrap * sub-keys (alphabetical order)"
-
-msgid "ceph"
-msgstr "ceph"
-
-msgid "conf * sub-keys (up-to-chart-developer)"
-msgstr "conf * sub-keys (up-to-chart-developer)"
-
-msgid "dependencies * sub-keys (alphabetical order)"
-msgstr "dependencies * sub-keys (alphabetical order)"
-
-msgid ""
-"diagram link: https://github.com/sktelecom-oslab/docs/blob/master/images/"
-"fluentbit-fluentd-diagram.png"
-msgstr ""
-"diagram link: https://github.com/sktelecom-oslab/docs/blob/master/images/"
-"fluentbit-fluentd-diagram.png"
-
-msgid "endpoints * sub-keys (alphabetical order)"
-msgstr "endpoints * sub-keys (alphabetical order)"
-
-msgid "etcd"
-msgstr "etcd"
-
-msgid "evrardjp"
-msgstr "evrardjp"
-
-msgid "fluentbit-fluentd logging architecture"
-msgstr "fluentbit-fluentd logging architecture"
-
-msgid ""
-"https://blueprints.launchpad.net/openstack-helm/+spec/developer-environment"
-msgstr ""
-"https://blueprints.launchpad.net/openstack-helm/+spec/developer-environment"
-
-msgid "https://kubernetes.io/docs/concepts/containers/images"
-msgstr "https://kubernetes.io/docs/concepts/containers/images"
-
-msgid ""
-"https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-"
-"account/#add-imagepullsecrets-to-a-service-account"
-msgstr ""
-"https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-"
-"account/#add-imagepullsecrets-to-a-service-account"
-
-msgid "https://review.openstack.org/#/c/552485/"
-msgstr "https://review.openstack.org/#/c/552485/"
-
-msgid "https://storyboard.openstack.org/#!/story/2005130"
-msgstr "https://storyboard.openstack.org/#!/story/2005130"
-
-msgid "images * sub-keys (alphabetical order)"
-msgstr "images * sub-keys (alphabetical order)"
-
-msgid "ingress"
-msgstr "ingress"
-
-msgid "k8s namespace: ceph"
-msgstr "k8s namespace: ceph"
-
-msgid "k8s namespace: tenant-ceph"
-msgstr "k8s namespace: tenant-ceph"
-
-msgid "k8s node labels:"
-msgstr "k8s node labels:"
-
-msgid "korzen (Artur Korzeniewski)"
-msgstr "korzen (Artur Korzeniewski)"
-
-msgid "labels * sub-keys (alphabetical order)"
-msgstr "labels * sub-keys (alphabetical order)"
-
-msgid "ldap"
-msgstr "ldap"
-
-msgid "libvirt"
-msgstr "libvirt"
-
-msgid "manifests * sub-keys (alphabetical order)"
-msgstr "manifests * sub-keys (alphabetical order)"
-
-msgid "mariadb"
-msgstr "mariadb"
-
-msgid "mattmceuen (Matt McEuen <matt.mceuen@att.com>) for coordination"
-msgstr "mattmceuen (Matt McEuen <matt.mceuen@att.com>) for coordination"
-
-msgid "memcached"
-msgstr "memcached"
-
-msgid "metric port: 9283"
-msgstr "metric port: 9283"
-
-msgid "metric port: 9284"
-msgstr "metric port: 9284"
-
-msgid "mgr endpoint port: 7000"
-msgstr "mgr endpoint port: 7000"
-
-msgid "mgr endpoint port: 7001"
-msgstr "mgr endpoint port: 7001"
-
-msgid "mon endpoint port: 6789"
-msgstr "mon endpoint port: 6789"
-
-msgid "mon endpoint port: 6790"
-msgstr "mon endpoint port: 6790"
-
-msgid "mon_addr and mon_host have non default mon port 6790."
-msgstr "mon_addr and mon_host have non default mon port 6790."
-
-msgid "mongodb"
-msgstr "mongodb"
-
-msgid "monitoring * sub-keys (alphabetical order)"
-msgstr "monitoring * sub-keys (alphabetical order)"
-
-msgid "network * sub-keys (alphabetical order)"
-msgstr "network * sub-keys (alphabetical order)"
-
-msgid "no ceph-mds"
-msgstr "no ceph-mds"
-
-msgid "no ceph-mds and ceph-rgw"
-msgstr "no ceph-mds and ceph-rgw"
-
-msgid "no storage classes"
-msgstr "no storage classes"
-
-msgid ""
-"openstack-control-plane=enabled, ceph-mon=enabled, ceph-mgr=enabled, ceph-"
-"rgw=enabled, ceph-mds=enabled, ceph-osd=enabled"
-msgstr ""
-"openstack-control-plane=enabled, ceph-mon=enabled, ceph-mgr=enabled, ceph-"
-"rgw=enabled, ceph-mds=enabled, ceph-osd=enabled"
-
-msgid ""
-"openstack-data-plane=enabled, openstack-compute-node=enabled, ceph-osd-"
-"tenant=enabled, openstack-data-plane=enabled"
-msgstr ""
-"openstack-data-plane=enabled, openstack-compute-node=enabled, ceph-osd-"
-"tenant=enabled, openstack-data-plane=enabled"
-
-msgid "openvswitch"
-msgstr "openvswitch"
-
-msgid "pod * sub-keys (alphabetical order)"
-msgstr "pod * sub-keys (alphabetical order)"
-
-msgid ""
-"portdirect (Pete Birley <pete@port.direct>) for the release management spec "
-"[2]_"
-msgstr ""
-"portdirect (Pete Birley <pete@port.direct>) for the release management spec "
-"[2]_"
-
-msgid "portdirect (Pete Birley)"
-msgstr "portdirect (Pete Birley)"
-
-msgid "postgresql"
-msgstr "postgresql"
-
-msgid ""
-"powerds (DaeSeong Kim <daeseong.kim@sk.com>) for the `values.yaml` ordering "
-"spec [1]_"
-msgstr ""
-"powerds (DaeSeong Kim <daeseong.kim@sk.com>) for the `values.yaml` ordering "
-"spec [1]_"
-
-msgid ""
-"powerds0111 (DaeSeong Kim <daeseong.kim@sk.com>) srwilkers (Steve Wilkerson "
-"<sw5822@att.com>)"
-msgstr ""
-"powerds0111 (DaeSeong Kim <daeseong.kim@sk.com>) srwilkers (Steve Wilkerson "
-"<sw5822@att.com>)"
-
-msgid "rabbitmq"
-msgstr "rabbitmq"
-
-msgid ""
-"randeep.jalli (Randeep Jalli <rj2083@att.com>) and renmak (Renis Makadia "
-"<renis.makadia@att.com>) for splitting up the Ceph chart"
-msgstr ""
-"randeep.jalli (Randeep Jalli <rj2083@att.com>) and renmak (Renis Makadia "
-"<renis.makadia@att.com>) for splitting up the Ceph chart"
-
-msgid ""
-"rwellum (Rich Wellum <richwellum@gmail.com>) for coordination of Storyboard "
-"adoption"
-msgstr ""
-"rwellum (Rich Wellum <richwellum@gmail.com>) for coordination of Storyboard "
-"adoption"
-
-msgid "secrets * sub-keys (alphabetical order)"
-msgstr "secrets * sub-keys (alphabetical order)"
-
-msgid "services do not handle TLS offloading and termination,"
-msgstr "services do not handle TLS offloading and termination,"
-
-msgid ""
-"services whose native handling of TLS offloading and termination cause major "
-"performance impact, for example, eventlet."
-msgstr ""
-"services whose native handling of TLS offloading and termination cause major "
-"performance impact, for example, eventlet."
-
-msgid ""
-"srwilker (Steve Wilkerson) portdirect (Pete Birley) lr699s (Larry Rensing)"
-msgstr ""
-"srwilker (Steve Wilkerson) portdirect (Pete Birley) lr699s (Larry Rensing)"
-
-msgid "storage classes: general (rbd based for pvc)"
-msgstr "storage classes: general (rbd based for pvc)"
-
-msgid "sungil (Sungil Im) jayahn (Jaesuk Ahn)"
-msgstr "sungil (Sungil Im) jayahn (Jaesuk Ahn)"
-
-msgid ""
-"tenant-ceph-control-plane=enabled, ceph-mon-tenant=enabled, ceph-mgr-"
-"tenant=enabled, ceph-rgw-tenant=enabled"
-msgstr ""
-"tenant-ceph-control-plane=enabled, ceph-mon-tenant=enabled, ceph-mgr-"
-"tenant=enabled, ceph-rgw-tenant=enabled"
-
-msgid ""
-"the impact of adding extra conditionals in the helm charts, to deal with "
-"multi-distro aspect (if not using the approach above, or when using an "
-"alternative approach)"
-msgstr ""
-"the impact of adding extra conditionals in the helm charts, to deal with "
-"multi-distro aspect (if not using the approach above, or when using an "
-"alternative approach)"
-
-msgid ""
-"the impact of adding functionality in the ``helm-toolkit`` to deal with a "
-"common multi-distro aspect (could possibly increase helm chart rendering "
-"time)"
-msgstr ""
-"the impact of adding functionality in the ``helm-toolkit`` to deal with a "
-"common multi-distro aspect (could possibly increase Helm chart rendering "
-"time)"
-
-msgid ""
-"the impact of exposing extra key/values in the helm chart ``values.yaml`` "
-"file (could possibly have a deployment speed/ram usage increase)."
-msgstr ""
-"the impact of exposing extra key/values in the helm chart ``values.yaml`` "
-"file (could possibly have a deployment speed/ram usage increase)."
diff --git a/doc/source/locale/en_GB/LC_MESSAGES/doc-testing.po b/doc/source/locale/en_GB/LC_MESSAGES/doc-testing.po
deleted file mode 100644
index fbbaae6c90..0000000000
--- a/doc/source/locale/en_GB/LC_MESSAGES/doc-testing.po
+++ /dev/null
@@ -1,1007 +0,0 @@
-# Andi Chandler <andi@gowling.com>, 2019. #zanata
-# Andi Chandler <andi@gowling.com>, 2020. #zanata
-msgid ""
-msgstr ""
-"Project-Id-Version: openstack-helm\n"
-"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-02-24 17:44+0000\n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-"PO-Revision-Date: 2020-02-24 05:03+0000\n"
-"Last-Translator: Andi Chandler <andi@gowling.com>\n"
-"Language-Team: English (United Kingdom)\n"
-"Language: en_GB\n"
-"X-Generator: Zanata 4.3.3\n"
-"Plural-Forms: nplurals=2; plural=(n != 1)\n"
-
-msgid ""
-"1) Initial Ceph and OpenStack deployment: Install Ceph and OpenStack charts "
-"on 3 nodes (mnode1, mnode2 and mnode3). Capture Ceph cluster status as well "
-"as K8s PODs status."
-msgstr ""
-"1) Initial Ceph and OpenStack deployment: Install Ceph and OpenStack charts "
-"on 3 nodes (mnode1, mnode2 and mnode3). Capture Ceph cluster status as well "
-"as K8s PODs status."
-
-msgid ""
-"1) Node reduction: Shutdown 1 of 3 nodes to simulate node failure. Capture "
-"effect of node failure on Ceph as well as other OpenStack services that are "
-"using Ceph."
-msgstr ""
-"1) Node reduction: Shutdown 1 of 3 nodes to simulate node failure. Capture "
-"effect of node failure on Ceph as well as other OpenStack services that are "
-"using Ceph."
-
-msgid "1) Remove out of quorum MON:"
-msgstr "1) Remove out of quorum MON:"
-
-msgid ""
-"2) Node expansion: Apply Ceph and OpenStack related labels to another unused "
-"k8 node. Node expansion should provide more resources for k8 to schedule "
-"PODs for Ceph and OpenStack services."
-msgstr ""
-"2) Node expansion: Apply Ceph and OpenStack related labels to another unused "
-"k8 node. Node expansion should provide more resources for k8 to schedule "
-"PODs for Ceph and OpenStack services."
-
-msgid ""
-"2) Node reduction (failure): Shutdown 1 of 3 nodes (mnode3) to test node "
-"failure. This should cause Ceph cluster to go in HEALTH_WARN state as it has "
-"lost 1 MON and 1 OSD. Capture Ceph cluster status as well as K8s PODs status."
-msgstr ""
-"2) Node reduction (failure): Shutdown 1 of 3 nodes (mnode3) to test node "
-"failure. This should cause Ceph cluster to go in HEALTH_WARN state as it has "
-"lost 1 MON and 1 OSD. Capture Ceph cluster status as well as K8s PODs status."
-
-msgid "2) Remove down OSD from Ceph cluster:"
-msgstr "2) Remove down OSD from Ceph cluster:"
-
-msgid "3 Node (VM based) env."
-msgstr "3 Node (VM based) env."
-
-msgid ""
-"3) Fix Ceph Cluster: After node expansion, perform maintenance on Ceph "
-"cluster to ensure quorum is reached and Ceph is HEALTH_OK."
-msgstr ""
-"3) Fix Ceph Cluster: After node expansion, perform maintenance on Ceph "
-"cluster to ensure quorum is reached and Ceph is HEALTH_OK."
-
-msgid ""
-"3) Node expansion: Add Ceph and OpenStack related labels to 4th node "
-"(mnode4) for expansion. Ceph cluster would show new MON and OSD being added "
-"to cluster. However Ceph cluster would continue to show HEALTH_WARN because "
-"1 MON and 1 OSD are still missing."
-msgstr ""
-"3) Node expansion: Add Ceph and OpenStack related labels to 4th node "
-"(mnode4) for expansion. Ceph cluster would show new MON and OSD being added "
-"to cluster. However Ceph cluster would continue to show HEALTH_WARN because "
-"1 MON and 1 OSD are still missing."
-
-msgid ""
-"4) Ceph cluster recovery: Perform Ceph maintenance to make Ceph cluster "
-"HEALTH_OK. Remove lost MON and OSD from Ceph cluster."
-msgstr ""
-"4) Ceph cluster recovery: Perform Ceph maintenance to make Ceph cluster "
-"HEALTH_OK. Remove lost MON and OSD from Ceph cluster."
-
-msgid ""
-"4. Replace the failed disk with a new one. If you repair (not replace) the "
-"failed disk, you may need to run the following:"
-msgstr ""
-"4. Replace the failed disk with a new one. If you repair (not replace) the "
-"failed disk, you may need to run the following:"
-
-msgid "6 Nodes (VM based) env"
-msgstr "6 Nodes (VM based) env"
-
-msgid ""
-"A Ceph Monitor running on voyager3 (whose Monitor database is destroyed) "
-"becomes out of quorum, and the mon-pod's status stays in ``Running`` -> "
-"``Error`` -> ``CrashLoopBackOff`` while keeps restarting."
-msgstr ""
-"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."
-
-msgid ""
-"Above output shows Ceph cluster in HEALTH_OK with all OSDs and MONs up and "
-"running."
-msgstr ""
-"Above output shows Ceph cluster in HEALTH_OK with all OSDs and MONs up and "
-"running."
-
-msgid "Above output shows that ``osd.1`` is down."
-msgstr "Above output shows that ``osd.1`` is down."
-
-msgid "Adding Tests"
-msgstr "Adding 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 ""
-"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."
-
-msgid ""
-"After 10+ miniutes, Ceph starts rebalancing with one node lost (i.e., 6 osds "
-"down) and the status stablizes with 18 osds."
-msgstr ""
-"After 10+ miniutes, Ceph starts rebalancing with one node lost (i.e., 6 osds "
-"down) and the status stablises with 18 osds."
-
-msgid "After applying labels, let's check status"
-msgstr "After applying labels, let's check status"
-
-msgid "After reboot (node voyager3), the node status changes to ``NotReady``."
-msgstr "After reboot (node voyager3), the node status changes to ``NotReady``."
-
-msgid ""
-"After the host is down (node voyager3), the node status changes to "
-"``NotReady``."
-msgstr ""
-"After the host is down (node voyager3), the node status changes to "
-"``NotReady``."
-
-msgid "All PODs are in running state."
-msgstr "All PODs are in running state."
-
-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 ""
-"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_."
-
-msgid ""
-"Also, the pod status of ceph-mon and ceph-osd changes from ``NodeLost`` back "
-"to ``Running``."
-msgstr ""
-"Also, the pod status of ceph-mon and ceph-osd changes from ``NodeLost`` back "
-"to ``Running``."
-
-msgid "Any Helm tests associated with a chart can be run by executing:"
-msgstr "Any Helm tests associated with a chart can be run by executing:"
-
-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 ""
-"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."
-
-msgid ""
-"As shown above, Ceph status is now HEALTH_OK and shows 3 MONs available."
-msgstr ""
-"As shown above, Ceph status is now HEALTH_OK and shows 3 MONs available."
-
-msgid ""
-"As shown in Ceph status above, ``osd: 4 osds: 3 up, 3 in`` 1 of 4 OSDs is "
-"still down. Let's remove that OSD."
-msgstr ""
-"As shown in Ceph status above, ``osd: 4 osds: 3 up, 3 in`` 1 of 4 OSDs is "
-"still down. Let's remove that OSD."
-
-msgid "Capture Ceph pods statuses."
-msgstr "Capture Ceph pods statuses."
-
-msgid "Capture Openstack pods statuses."
-msgstr "Capture Openstack pods statuses."
-
-msgid "Capture final Ceph pod statuses:"
-msgstr "Capture final Ceph pod statuses:"
-
-msgid "Capture final Openstack pod statuses:"
-msgstr "Capture final Openstack pod statuses:"
-
-msgid "Case: 1 out of 3 Monitor Processes is Down"
-msgstr "Case: 1 out of 3 Monitor Processes is Down"
-
-msgid "Case: 2 out of 3 Monitor Processes are Down"
-msgstr "Case: 2 out of 3 Monitor Processes are Down"
-
-msgid "Case: 3 out of 3 Monitor Processes are Down"
-msgstr "Case: 3 out of 3 Monitor Processes are Down"
-
-msgid "Case: A OSD pod is deleted"
-msgstr "Case: A OSD pod is deleted"
-
-msgid "Case: A disk fails"
-msgstr "Case: A disk fails"
-
-msgid "Case: A host machine where ceph-mon is running is down"
-msgstr "Case: A host machine where ceph-mon is running is down"
-
-msgid "Case: Monitor database is destroyed"
-msgstr "Case: Monitor database is destroyed"
-
-msgid "Case: OSD processes are killed"
-msgstr "Case: OSD processes are killed"
-
-msgid "Case: One host machine where ceph-mon is running is rebooted"
-msgstr "Case: One host machine where ceph-mon is running is rebooted"
-
-msgid "Caveats:"
-msgstr "Caveats:"
-
-msgid "Ceph - Node Reduction, Expansion and Ceph Recovery"
-msgstr "Ceph - Node Reduction, Expansion and Ceph Recovery"
-
-msgid "Ceph Cephfs provisioner docker images."
-msgstr "Ceph Cephfs provisioner docker images."
-
-msgid "Ceph Luminous point release images for Ceph components"
-msgstr "Ceph Luminous point release images for Ceph components"
-
-msgid "Ceph MON and OSD PODs got scheduled on mnode4 node."
-msgstr "Ceph MON and OSD PODs got scheduled on mnode4 node."
-
-msgid "Ceph RBD provisioner docker images."
-msgstr "Ceph RBD provisioner docker images."
-
-msgid "Ceph Resiliency"
-msgstr "Ceph Resiliency"
-
-msgid "Ceph Upgrade"
-msgstr "Ceph Upgrade"
-
-msgid ""
-"Ceph can be upgraded without downtime for Openstack components in a "
-"multinode env."
-msgstr ""
-"Ceph can be upgraded without downtime for Openstack components in a "
-"multinode env."
-
-msgid "Ceph cluster is in HEALTH_OK state with 3 MONs and 3 OSDs."
-msgstr "Ceph cluster is in HEALTH_OK state with 3 MONs and 3 OSDs."
-
-msgid "Ceph status shows 1 Ceph MON and 1 Ceph OSD missing."
-msgstr "Ceph status shows 1 Ceph MON and 1 Ceph OSD missing."
-
-msgid "Ceph status shows HEALTH_WARN as expected"
-msgstr "Ceph status shows HEALTH_WARN as expected"
-
-msgid "Ceph status shows that MON and OSD count has been increased."
-msgstr "Ceph status shows that MON and OSD count has been increased."
-
-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 ""
-"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."
-
-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 ""
-"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."
-
-msgid "Ceph status still shows HEALTH_WARN as one MON and OSD are still down."
-msgstr "Ceph status still shows HEALTH_WARN as one MON and OSD are still down."
-
-msgid "Ceph version: 12.2.3"
-msgstr "Ceph version: 12.2.3"
-
-msgid "Check Ceph Pods"
-msgstr "Check Ceph Pods"
-
-msgid "Check version of each Ceph components."
-msgstr "Check version of each Ceph components."
-
-msgid "Check which images Provisionors and Mon-Check PODs are using"
-msgstr "Check which images Provisionors and Mon-Check PODs are using"
-
-msgid "Cluster size: 4 host machines"
-msgstr "Cluster size: 4 host machines"
-
-msgid "Conclusion:"
-msgstr "Conclusion:"
-
-msgid "Confirm Ceph component's version."
-msgstr "Confirm Ceph component's version."
-
-msgid "Continue with OSH multinode guide to install other Openstack charts."
-msgstr "Continue with OSH multinode guide to install other Openstack charts."
-
-msgid "Deploy and Validate Ceph"
-msgstr "Deploy and Validate Ceph"
-
-msgid "Disk Failure"
-msgstr "Disk Failure"
-
-msgid "Docker Images:"
-msgstr "Docker Images:"
-
-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 ""
-"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_."
-
-msgid "Find that Ceph is healthy with a lost OSD (i.e., a total of 23 OSDs):"
-msgstr "Find that Ceph is healthy with a lost OSD (i.e., a total of 23 OSDs):"
-
-msgid "First, run ``ceph osd tree`` command to get list of OSDs."
-msgstr "First, run ``ceph osd tree`` command to get list of OSDs."
-
-msgid "Follow all steps from OSH multinode guide with below changes."
-msgstr "Follow all steps from OSH multinode guide with below changes."
-
-msgid ""
-"Followed OSH multinode guide steps to install Ceph and OpenStack charts up "
-"to Cinder."
-msgstr ""
-"Followed OSH multinode guide steps to install Ceph and OpenStack charts up "
-"to Cinder."
-
-msgid ""
-"Followed OSH multinode guide steps to setup nodes and install K8s cluster"
-msgstr ""
-"Followed OSH multinode guide steps to setup nodes and install K8s cluster"
-
-msgid "Followed OSH multinode guide steps upto Ceph install"
-msgstr "Followed OSH multinode guide steps up to Ceph install"
-
-msgid "Following is a partial part from script to show changes."
-msgstr "Following is a partial part from script to show changes."
-
-msgid ""
-"From the Kubernetes cluster, remove the failed OSD pod, which is running on "
-"``voyager4``:"
-msgstr ""
-"From the Kubernetes cluster, remove the failed OSD pod, which is running on "
-"``voyager4``:"
-
-msgid "Hardware Failure"
-msgstr "Hardware Failure"
-
-msgid "Helm Tests"
-msgstr "Helm Tests"
-
-msgid "Host Failure"
-msgstr "Host Failure"
-
-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 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."
-
-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 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."
-
-msgid ""
-"In this test env, MariaDB chart is deployed with only 1 replica. In order to "
-"test properly, the node with MariaDB server POD (mnode2) should not be "
-"shutdown."
-msgstr ""
-"In this test env, MariaDB chart is deployed with only 1 replica. In order to "
-"test properly, the node with MariaDB server POD (mnode2) should not be "
-"shutdown."
-
-msgid "In this test env, ``mnode3`` is out of quorum."
-msgstr "In this test env, ``mnode3`` is out of quorum."
-
-msgid ""
-"In this test env, each node has Ceph and OpenStack related PODs. Due to "
-"this, shutting down a Node will cause issue with Ceph as well as OpenStack "
-"services. These PODs level failures are captured following subsequent "
-"screenshots."
-msgstr ""
-"In this test env, each node has Ceph and OpenStack related PODs. Due to "
-"this, shutting down a Node will cause issue with Ceph as well as OpenStack "
-"services. These PODs level failures are captured following subsequent "
-"screenshots."
-
-msgid "In this test env, let's shutdown ``mnode3`` node."
-msgstr "In this test env, let's shutdown ``mnode3`` node."
-
-msgid ""
-"In this test env, let's use ``mnode4`` and apply Ceph and OpenStack related "
-"labels."
-msgstr ""
-"In this test env, let's use ``mnode4`` and apply Ceph and OpenStack related "
-"labels."
-
-msgid ""
-"In this test env, since out of quorum MON is no longer available due to node "
-"failure, we can processed with removing it from Ceph cluster."
-msgstr ""
-"In this test env, since out of quorum MON is no longer available due to node "
-"failure, we can processed with removing it from Ceph cluster."
-
-msgid "Install Ceph charts (12.2.4) by updating Docker images in overrides."
-msgstr "Install Ceph charts (12.2.4) by updating Docker images in overrides."
-
-msgid "Install Ceph charts (version 12.2.4)"
-msgstr "Install Ceph charts (version 12.2.4)"
-
-msgid "Install OSH components as per OSH multinode guide."
-msgstr "Install OSH components as per OSH multinode guide."
-
-msgid "Install Openstack charts"
-msgstr "Install Openstack charts"
-
-msgid ""
-"It takes longer (about 1 minute) for the killed Monitor processes to recover "
-"from ``down`` to ``up``."
-msgstr ""
-"It takes longer (about 1 minute) for the killed Monitor processes to recover "
-"from ``down`` to ``up``."
-
-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 "Let's add more resources for K8s to schedule PODs on."
-msgstr "Let's add more resources for K8s to schedule PODs on."
-
-msgid ""
-"Make sure only 3 nodes (mnode1, mnode2, mnode3) have Ceph and OpenStack "
-"related labels. K8s would only schedule PODs on these 3 nodes."
-msgstr ""
-"Make sure only 3 nodes (mnode1, mnode2, mnode3) have Ceph and OpenStack "
-"related labels. K8s would only schedule PODs on these 3 nodes."
-
-msgid "Mission"
-msgstr "Mission"
-
-msgid "Monitor Failure"
-msgstr "Monitor Failure"
-
-msgid ""
-"Note: To find the daemonset associated with a failed OSD, check out the "
-"followings:"
-msgstr ""
-"Note: To find the daemonset associated with a failed OSD, check out the "
-"followings:"
-
-msgid ""
-"Now that we have added new node for Ceph and OpenStack PODs, let's perform "
-"maintenance on Ceph cluster."
-msgstr ""
-"Now that we have added new node for Ceph and OpenStack PODs, let's perform "
-"maintenance on Ceph cluster."
-
-msgid "Number of disks: 24 (= 6 disks per host * 4 hosts)"
-msgstr "Number of disks: 24 (= 6 disks per host * 4 hosts)"
-
-msgid "OSD Failure"
-msgstr "OSD Failure"
-
-msgid "OSD count is set to 3 based on env setup."
-msgstr "OSD count is set to 3 based on env setup."
-
-msgid ""
-"Only 3 nodes will have Ceph and OpenStack related labels. Each of these 3 "
-"nodes will have one MON and one OSD running on them."
-msgstr ""
-"Only 3 nodes will have Ceph and OpenStack related labels. Each of these 3 "
-"nodes will have one MON and one OSD running on them."
-
-msgid "OpenStack PODs that were scheduled mnode3 also shows NodeLost/Unknown."
-msgstr "OpenStack PODs that were scheduled mnode3 also shows NodeLost/Unknown."
-
-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 ""
-"Our focus lies on resiliency for various failure scenarios but not on "
-"performance or stress testing."
-
-msgid "PODs that were scheduled on mnode3 node has status of NodeLost/Unknown."
-msgstr ""
-"PODs that were scheduled on mnode3 node has status of NodeLost/Unknown."
-
-msgid "Plan:"
-msgstr "Plan:"
-
-msgid "Recovery:"
-msgstr "Recovery:"
-
-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 ""
-"Remove the entire ceph-mon directory on voyager3, and then Ceph will "
-"automatically recreate the database by using the other ceph-mons' database."
-
-msgid ""
-"Remove the failed OSD (OSD ID = 2 in this example) from the Ceph cluster:"
-msgstr ""
-"Remove the failed OSD (OSD ID = 2 in this example) from the Ceph cluster:"
-
-msgid "Resiliency Tests for OpenStack-Helm/Ceph"
-msgstr "Resiliency Tests for OpenStack-Helm/Ceph"
-
-msgid "Run ``ceph osd purge`` command to remove OSD from ceph cluster."
-msgstr "Run ``ceph osd purge`` command to remove OSD from Ceph cluster."
-
-msgid "Running Tests"
-msgstr "Running Tests"
-
-msgid "Setup:"
-msgstr "Setup:"
-
-msgid ""
-"Showing partial output from kubectl describe command to show which image is "
-"Docker container is using"
-msgstr ""
-"Showing partial output from kubectl describe command to show which image is "
-"Docker container is using"
-
-msgid ""
-"Shutdown 1 of 3 nodes (mnode1, mnode2, mnode3) to simulate node failure/lost."
-msgstr ""
-"Shutdown 1 of 3 nodes (mnode1, mnode2, mnode3) to simulate node failure/lost."
-
-msgid ""
-"Since the node that was shutdown earlier had both Ceph and OpenStack PODs, "
-"mnode4 should get Ceph and OpenStack related labels as well."
-msgstr ""
-"Since the node that was shutdown earlier had both Ceph and OpenStack PODs, "
-"mnode4 should get Ceph and OpenStack related labels as well."
-
-msgid "Software Failure"
-msgstr "Software Failure"
-
-msgid "Solution:"
-msgstr "Solution:"
-
-msgid "Start a new OSD pod on ``voyager4``:"
-msgstr "Start a new OSD pod on ``voyager4``:"
-
-msgid "Step 1: Initial Ceph and OpenStack deployment"
-msgstr "Step 1: Initial Ceph and OpenStack deployment"
-
-msgid "Step 2: Node reduction (failure):"
-msgstr "Step 2: Node reduction (failure):"
-
-msgid "Step 3: Node Expansion"
-msgstr "Step 3: Node Expansion"
-
-msgid "Step 4: Ceph cluster recovery"
-msgstr "Step 4: Ceph cluster recovery"
-
-msgid "Steps:"
-msgstr "Steps:"
-
-msgid "Symptom:"
-msgstr "Symptom:"
-
-msgid "Test Environment"
-msgstr "Test Environment"
-
-msgid "Test Scenario:"
-msgstr "Test Scenario:"
-
-msgid "Test Scenarios:"
-msgstr "Test Scenarios:"
-
-msgid "Testing"
-msgstr "Testing"
-
-msgid "Testing Expectations"
-msgstr "Testing Expectations"
-
-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 ""
-"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."
-
-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 ""
-"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."
-
-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 ""
-"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."
-
-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 ""
-"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)."
-
-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 ""
-"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:"
-
-msgid "The pod status of ceph-mon and ceph-osd shows as ``NodeLost``."
-msgstr "The pod status of ceph-mon and ceph-osd shows as ``NodeLost``."
-
-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 ""
-"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."
-
-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 ""
-"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."
-
-msgid ""
-"This document captures steps and result from node reduction and expansion as "
-"well as ceph recovery."
-msgstr ""
-"This document captures steps and result from node reduction and expansion as "
-"well as Ceph recovery."
-
-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 ""
-"This guide documents steps showing Ceph version upgrade. The main goal of "
-"this document is to demonstrate Ceph chart update without downtime for OSH "
-"components."
-
-msgid ""
-"This is for the case when a host machine (where ceph-mon is running) is down."
-msgstr ""
-"This is for the case when a host machine (where ceph-mon is running) is down."
-
-msgid "This is to test a scenario when 1 out of 3 Monitor processes is down."
-msgstr "This is to test a scenario when 1 out of 3 Monitor processes is down."
-
-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 ""
-"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)."
-
-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 ""
-"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)."
-
-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 ""
-"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."
-
-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 note that it "
-"takes about 90 seconds for the OSD running in deleted pod to recover from "
-"``down`` to ``up``."
-msgstr ""
-"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 note that it "
-"takes about 90 seconds for the OSD running in deleted pod to recover from "
-"``down`` to ``up``."
-
-msgid "This is to test a scenario when some of the OSDs are down."
-msgstr "This is to test a scenario when some of the OSDs are down."
-
-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 ""
-"To bring down 1 Monitor process (out of 3), we identify a Monitor process "
-"and kill it from the monitor host (not a 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 ""
-"To bring down 6 OSDs (out of 24), we identify the OSD processes and kill "
-"them from a storage host (not a pod)."
-
-msgid "To replace the failed OSD, execute the following procedure:"
-msgstr "To replace the failed OSD, execute the following procedure:"
-
-msgid "Update Ceph Client chart with new overrides:"
-msgstr "Update Ceph Client chart with new overrides:"
-
-msgid "Update Ceph Mon chart with new overrides"
-msgstr "Update Ceph Mon chart with new overrides"
-
-msgid "Update Ceph OSD chart with new overrides:"
-msgstr "Update Ceph OSD chart with new overrides:"
-
-msgid "Update Ceph Provisioners chart with new overrides:"
-msgstr "Update Ceph Provisioners chart with new overrides:"
-
-msgid ""
-"Update ceph install script ``./tools/deployment/multinode/030-ceph.sh`` to "
-"add ``images:`` section in overrides as shown below."
-msgstr ""
-"Update Ceph install script ``./tools/deployment/multinode/030-ceph.sh`` to "
-"add ``images:`` section in overrides as shown below."
-
-msgid ""
-"Update, image section in new overrides ``ceph-update.yaml`` as shown below"
-msgstr ""
-"Update, image section in new overrides ``ceph-update.yaml`` as shown below"
-
-msgid "Upgrade Ceph charts to update version"
-msgstr "Upgrade Ceph charts to update version"
-
-msgid ""
-"Upgrade Ceph charts to version 12.2.5 by updating docker images in overrides."
-msgstr ""
-"Upgrade Ceph charts to version 12.2.5 by updating Docker images in overrides."
-
-msgid ""
-"Upgrade Ceph component version from ``12.2.4`` to ``12.2.5`` without "
-"downtime to OSH components."
-msgstr ""
-"Upgrade Ceph component version from ``12.2.4`` to ``12.2.5`` without "
-"downtime to OSH components."
-
-msgid ""
-"Use Ceph override file ``ceph.yaml`` that was generated previously and "
-"update images section as below"
-msgstr ""
-"Use Ceph override file ``ceph.yaml`` that was generated previously and "
-"update images section as below"
-
-msgid ""
-"Using ``ceph mon_status`` and ``ceph -s`` commands, confirm ID of MON that "
-"is out of quorum."
-msgstr ""
-"Using ``ceph mon_status`` and ``ceph -s`` commands, confirm ID of MON that "
-"is out of quorum."
-
-msgid ""
-"Validate the Ceph status (i.e., one OSD is added, so the total number of "
-"OSDs becomes 24):"
-msgstr ""
-"Validate the Ceph status (i.e., one OSD is added, so the total number of "
-"OSDs becomes 24):"
-
-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 takes about 90 seconds. The reason is that Kubernetes automatically "
-"restarts OSD pods whenever they are deleted."
-msgstr ""
-"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 takes about 90 seconds. The reason is that Kubernetes automatically "
-"restarts OSD pods whenever they are deleted."
-
-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 ""
-"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."
-
-msgid ""
-"We have 3 Monitors in this Ceph cluster, one on each of the 3 Monitor hosts."
-msgstr ""
-"We have 3 Monitors in this Ceph cluster, one on each of the 3 Monitor hosts."
-
-msgid ""
-"We intentionlly destroy a Monitor database by removing ``/var/lib/openstack-"
-"helm/ceph/mon/mon/ceph-voyager3/store.db``."
-msgstr ""
-"We intentionally destroy a Monitor database by removing ``/var/lib/openstack-"
-"helm/ceph/mon/mon/ceph-voyager3/store.db``."
-
-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 ""
-"We monitored the status of Ceph Monitor pods and noted that the symptoms are "
-"similar to when 1 or 2 Monitor processes are killed:"
-
-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 ""
-"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:"
-
-msgid "`Disk failure <./disk-failure.html>`_"
-msgstr "`Disk failure <./disk-failure.html>`_"
-
-msgid "`Host failure <./host-failure.html>`_"
-msgstr "`Host failure <./host-failure.html>`_"
-
-msgid "`Monitor failure <./monitor-failure.html>`_"
-msgstr "`Monitor failure <./monitor-failure.html>`_"
-
-msgid "`OSD failure <./osd-failure.html>`_"
-msgstr "`OSD failure <./osd-failure.html>`_"
-
-msgid "``Ceph MON Status:``"
-msgstr "``Ceph MON Status:``"
-
-msgid "``Ceph MON Status``"
-msgstr "``Ceph MON Status``"
-
-msgid "``Ceph PODs:``"
-msgstr "``Ceph PODs:``"
-
-msgid "``Ceph PODs``"
-msgstr "``Ceph PODs``"
-
-msgid "``Ceph Status:``"
-msgstr "``Ceph Status:``"
-
-msgid "``Ceph quorum status:``"
-msgstr "``Ceph quorum status:``"
-
-msgid "``Ceph quorum status``"
-msgstr "``Ceph quorum status``"
-
-msgid "``Ceph status:``"
-msgstr "``Ceph status:``"
-
-msgid "``Ceph status``"
-msgstr "``Ceph status``"
-
-msgid "``Check node status:``"
-msgstr "``Check node status:``"
-
-msgid "``Following are PODs scheduled on mnode3 before shutdown:``"
-msgstr "``Following are PODs scheduled on mnode3 before shutdown:``"
-
-msgid "``OpenStack PODs:``"
-msgstr "``OpenStack PODs:``"
-
-msgid "``OpenStack PODs``"
-msgstr "``OpenStack PODs``"
-
-msgid "``Remove MON from Ceph cluster``"
-msgstr "``Remove MON from Ceph cluster``"
-
-msgid "``Result/Observation:``"
-msgstr "``Result/Observation:``"
-
-msgid ""
-"``Results:`` All provisioner pods got terminated at once (same time). Other "
-"ceph pods are running. No interruption to OSH pods."
-msgstr ""
-"``Results:`` All provisioner pods got terminated at once (same time). Other "
-"Ceph pods are running. No interruption to 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 ""
-"``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."
-
-msgid ""
-"``Results:`` Rolling updates (one pod at a time). Other ceph pods are "
-"running. No interruption to OSH pods."
-msgstr ""
-"``Results:`` Rolling updates (one pod at a time). Other ceph pods are "
-"running. No interruption to 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`` and ``ceph_rbs_pool`` images are "
-"used for jobs. ``ceph_mon_check`` has one script that is stable so no need "
-"to upgrade."
-
-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 "``series of console outputs:``"
diff --git a/doc/source/locale/en_GB/LC_MESSAGES/doc-troubleshooting.po b/doc/source/locale/en_GB/LC_MESSAGES/doc-troubleshooting.po
deleted file mode 100644
index d5ee7a3ec6..0000000000
--- a/doc/source/locale/en_GB/LC_MESSAGES/doc-troubleshooting.po
+++ /dev/null
@@ -1,212 +0,0 @@
-# Andi Chandler <andi@gowling.com>, 2018. #zanata
-# Andi Chandler <andi@gowling.com>, 2020. #zanata
-# Andi Chandler <andi@gowling.com>, 2021. #zanata
-msgid ""
-msgstr ""
-"Project-Id-Version: openstack-helm 0.1.1.dev3462\n"
-"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2021-06-22 20:22+0000\n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-"PO-Revision-Date: 2021-06-24 03:47+0000\n"
-"Last-Translator: Andi Chandler <andi@gowling.com>\n"
-"Language-Team: English (United Kingdom)\n"
-"Language: en_GB\n"
-"X-Generator: Zanata 4.3.3\n"
-"Plural-Forms: nplurals=2; plural=(n != 1)\n"
-
-msgid "Backing up a PVC"
-msgstr "Backing up a PVC"
-
-msgid ""
-"Backing up a PVC stored in Ceph, is fairly straigthforward, in this example "
-"we use the PVC ``mysql-data-mariadb-server-0`` as an example, but this will "
-"also apply to any other services using PVCs eg. RabbitMQ, Postgres."
-msgstr ""
-"Backing up a PVC stored in Ceph, is fairly straightforward, in this example "
-"we use the PVC ``mysql-data-mariadb-server-0`` as an example, but this will "
-"also apply to any other services using PVCs e.g. RabbitMQ, Postgres."
-
-msgid ""
-"Before proceeding, it is important to ensure that you have deployed a client "
-"key in the namespace you wish to fulfill ``PersistentVolumeClaims``. To "
-"verify that your deployment namespace has a client key:"
-msgstr ""
-"Before proceeding, it is important to ensure that you have deployed a client "
-"key in the namespace you wish to fulfil ``PersistentVolumeClaims``. To "
-"verify that your deployment namespace has a client key:"
-
-msgid "Bugs and Feature requests"
-msgstr "Bugs and Feature requests"
-
-msgid "Ceph"
-msgstr "Ceph"
-
-msgid "Ceph Deployment Status"
-msgstr "Ceph Deployment Status"
-
-msgid "Ceph Validating PVC Operation"
-msgstr "Ceph Validating PVC Operation"
-
-msgid "Ceph Validating StorageClass"
-msgstr "Ceph Validating StorageClass"
-
-msgid "Channels"
-msgstr "Channels"
-
-msgid "Database Deployments"
-msgstr "Database Deployments"
-
-msgid ""
-"First, we want to validate that Ceph is working correctly. This can be done "
-"with the following Ceph command:"
-msgstr ""
-"First, we want to validate that Ceph is working correctly. This can be done "
-"with the following Ceph command:"
-
-msgid "Galera Cluster"
-msgstr "Galera Cluster"
-
-msgid "Getting help"
-msgstr "Getting help"
-
-msgid "Installation"
-msgstr "Installation"
-
-msgid ""
-"Join us on `IRC <irc://chat.oftc.net/openstack-helm>`_: #openstack-helm on "
-"oftc"
-msgstr ""
-"Join us on `IRC <irc://chat.oftc.net/openstack-helm>`_: #openstack-helm on "
-"oftc"
-
-msgid "Join us on `Slack <http://slack.k8s.io/>`_ - #openstack-helm"
-msgstr "Join us on `Slack <http://slack.k8s.io/>`_ - #openstack-helm"
-
-msgid ""
-"Next we can look at the storage class, to make sure that it was created "
-"correctly:"
-msgstr ""
-"Next we can look at the storage class, to make sure that it was created "
-"correctly:"
-
-msgid ""
-"Note: This step is not relevant for PVCs within the same namespace Ceph was "
-"deployed."
-msgstr ""
-"Note: This step is not relevant for PVCs within the same namespace Ceph was "
-"deployed."
-
-msgid "Once this has been done the workload can be restarted."
-msgstr "Once this has been done the workload can be restarted."
-
-msgid "PVC Preliminary Validation"
-msgstr "PVC Preliminary Validation"
-
-msgid "Persistent Storage"
-msgstr "Persistent Storage"
-
-msgid ""
-"Please, refer to `Contribution guidelines <../contributor/contributing."
-"html>`_."
-msgstr ""
-"Please, refer to `Contribution guidelines <../contributor/contributing."
-"html>`_."
-
-msgid ""
-"Restoring is just as straightforward. Once the workload consuming the device "
-"has been stopped, and the raw RBD device removed the following will import "
-"the back up and create a device:"
-msgstr ""
-"Restoring is just as straightforward. Once the workload consuming the device "
-"has been stopped, and the raw RBD device removed the following will import "
-"the back up and create a device:"
-
-msgid ""
-"Sometimes things go wrong. These guides will help you solve many common "
-"issues with the following:"
-msgstr ""
-"Sometimes things go wrong. These guides will help you solve many common "
-"issues with the following:"
-
-msgid ""
-"The parameters are what we're looking for here. If we see parameters passed "
-"to the StorageClass correctly, we will see the ``ceph-mon.ceph.svc.cluster."
-"local:6789`` hostname/port, things like ``userid``, and appropriate secrets "
-"used for volume claims."
-msgstr ""
-"The parameters are what we're looking for here. If we see parameters passed "
-"to the StorageClass correctly, we will see the ``ceph-mon.ceph.svc.cluster."
-"local:6789`` hostname/port, things like ``userid``, and appropriate secrets "
-"used for volume claims."
-
-msgid ""
-"This guide is to help users debug any general storage issues when deploying "
-"Charts in this repository."
-msgstr ""
-"This guide is to help users debug any general storage issues when deploying "
-"Charts in this repository."
-
-msgid ""
-"This guide is to help users debug any general storage issues when deploying "
-"charts in this repository."
-msgstr ""
-"This guide is to help users debug any general storage issues when deploying "
-"charts in this repository."
-
-msgid ""
-"To deploy the HWE kernel, prior to deploying Kubernetes and OpenStack-Helm "
-"the following commands should be run on each node:"
-msgstr ""
-"To deploy the HWE kernel, prior to deploying Kubernetes and OpenStack-Helm "
-"the following commands should be run on each node:"
-
-msgid ""
-"To make use of CephFS in Ubuntu the HWE Kernel is required, until the issue "
-"described `here <https://github.com/kubernetes-incubator/external-storage/"
-"issues/345>`_ is fixed."
-msgstr ""
-"To make use of CephFS in Ubuntu the HWE Kernel is required, until the issue "
-"described `here <https://github.com/kubernetes-incubator/external-storage/"
-"issues/345>`_ is fixed."
-
-msgid "To test MariaDB, do the following:"
-msgstr "To test MariaDB, do the following:"
-
-msgid ""
-"To validate persistent volume claim (PVC) creation, we've placed a test "
-"manifest `here <https://raw.githubusercontent.com/openstack/openstack-helm/"
-"master/tests/pvc-test.yaml>`_. Deploy this manifest and verify the job "
-"completes successfully."
-msgstr ""
-"To validate persistent volume claim (PVC) creation, we've placed a test "
-"manifest `here <https://raw.githubusercontent.com/openstack/openstack-helm/"
-"master/tests/pvc-test.yaml>`_. Deploy this manifest and verify the job "
-"completes successfully."
-
-msgid "Troubleshooting"
-msgstr "Troubleshooting"
-
-msgid "Ubuntu HWE Kernel"
-msgstr "Ubuntu HWE Kernel"
-
-msgid ""
-"Use one of your Ceph Monitors to check the status of the cluster. A couple "
-"of things to note above; our health is `HEALTH\\_OK`, we have 3 mons, we've "
-"established a quorum, and we can see that all of our OSDs are up and in the "
-"OSD map."
-msgstr ""
-"Use one of your Ceph Monitors to check the status of the cluster. A couple "
-"of things to note above; our health is `HEALTH\\_OK`, we have 3 mons, we've "
-"established a quorum, and we can see that all of our OSDs are up and in the "
-"OSD map."
-
-msgid ""
-"Without this, your RBD-backed PVCs will never reach the ``Bound`` state.  "
-"For more information, see how to `activate namespace for ceph <../install/"
-"multinode.html#activating-control-plane-namespace-for-ceph>`_."
-msgstr ""
-"Without this, your RBD-backed PVCs will never reach the ``Bound`` state.  "
-"For more information, see how to `activate namespace for Ceph <../install/"
-"multinode.html#activating-control-plane-namespace-for-ceph>`_."
diff --git a/doc/source/locale/en_GB/LC_MESSAGES/doc.po b/doc/source/locale/en_GB/LC_MESSAGES/doc.po
deleted file mode 100644
index 78ca186fc2..0000000000
--- a/doc/source/locale/en_GB/LC_MESSAGES/doc.po
+++ /dev/null
@@ -1,410 +0,0 @@
-# Andi Chandler <andi@gowling.com>, 2018. #zanata
-# Andi Chandler <andi@gowling.com>, 2019. #zanata
-# Andi Chandler <andi@gowling.com>, 2020. #zanata
-# Andi Chandler <andi@gowling.com>, 2021. #zanata
-# Andi Chandler <andi@gowling.com>, 2022. #zanata
-msgid ""
-msgstr ""
-"Project-Id-Version: openstack-helm 0.1.1.dev3879\n"
-"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2022-10-24 20:45+0000\n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-"PO-Revision-Date: 2022-11-07 02:36+0000\n"
-"Last-Translator: Andi Chandler <andi@gowling.com>\n"
-"Language-Team: English (United Kingdom)\n"
-"Language: en_GB\n"
-"X-Generator: Zanata 4.3.3\n"
-"Plural-Forms: nplurals=2; plural=(n != 1)\n"
-
-msgid ":ref:`genindex`"
-msgstr ":ref:`genindex`"
-
-msgid ":ref:`search`"
-msgstr ":ref:`search`"
-
-msgid "Adding Services"
-msgstr "Adding Services"
-
-msgid "Adding Tests"
-msgstr "Adding Tests"
-
-msgid ""
-"Any additional functions required for testing new charts or improving the "
-"gate workflow should be placed in the appropriate location."
-msgstr ""
-"Any additional functions required for testing new charts or improving the "
-"gate workflow should be placed in the appropriate location."
-
-msgid ""
-"Any tests that do not use the Rally testing framework would need to be "
-"handled in the appropriate manner in launch script. This would ideally "
-"result in new functions that could be reused, or expansion of the gate "
-"scripts to include scenarios beyond basic service launches."
-msgstr ""
-"Any tests that do not use the Rally testing framework would need to be "
-"handled in the appropriate manner in launch script. This would ideally "
-"result in new functions that could be reused, or expansion of the gate "
-"scripts to include scenarios beyond basic service launches."
-
-msgid ""
-"As charts for additional services are added to OpenStack-Helm, they should "
-"be included in the gates.  Adding new services to the gates allows a chart "
-"developer and the review team to identify any potential issues associated "
-"with a new service. All services are currently launched in the gate via a "
-"series of launch scripts of the format ``NNN-service-name.sh`` where ``NNN`` "
-"dictates the order these scripts are launched. The script should contain an "
-"installation command like:"
-msgstr ""
-"As charts for additional services are added to OpenStack-Helm, they should "
-"be included in the gates.  Adding new services to the gates allows a chart "
-"developer and the review team to identify any potential issues associated "
-"with a new service. All services are currently launched in the gate via a "
-"series of launch scripts of the format ``NNN-service-name.sh`` where ``NNN`` "
-"dictates the order these scripts are launched. The script should contain an "
-"installation command like:"
-
-msgid ""
-"As new charts are developed and the services are added to the gate, an "
-"associated Helm test should be introduced to the gates.  The appropriate "
-"place for executing these tests is in the respective service's launch "
-"script, and must be placed after the entry for installing the service and "
-"any associated overrides.  Any tests that use the Rally testing framework "
-"should leverage the helm_test_deployment function in the aforementioned "
-"funcs/helm.sh file. For example, a Helm test for Mistral might look like:"
-msgstr ""
-"As new charts are developed and the services are added to the gate, an "
-"associated Helm test should be introduced to the gates.  The appropriate "
-"place for executing these tests is in the respective service's launch "
-"script, and must be placed after the entry for installing the service and "
-"any associated overrides.  Any tests that use the Rally testing framework "
-"should leverage the helm_test_deployment function in the aforementioned "
-"funcs/helm.sh file. For example, a Helm test for Mistral might look like:"
-
-msgid ""
-"Bugs and enhancements are tracked via OpenStack-Helm's `Storyboard <https://"
-"storyboard.openstack.org/#!/project_group/64>`_."
-msgstr ""
-"Bugs and enhancements are tracked via OpenStack-Helm's `Storyboard <https://"
-"storyboard.openstack.org/#!/project_group/64>`_."
-
-msgid "Communication"
-msgstr "Communication"
-
-msgid ""
-"Community `IRC Meetings <http://eavesdrop.openstack.org/#OpenStack-"
-"Helm_Team_Meeting>`_: [Every Tuesday @ 1500 UTC], #openstack-helm in IRC "
-"(OFTC)"
-msgstr ""
-"Community `IRC Meetings <http://eavesdrop.openstack.org/#OpenStack-"
-"Helm_Team_Meeting>`_: [Every Tuesday @ 1500 UTC], #openstack-helm in IRC "
-"(OFTC)"
-
-msgid "Contents:"
-msgstr "Contents:"
-
-msgid "Contributing"
-msgstr "Contributing"
-
-msgid ""
-"Developers wishing to work on the OpenStack-Helm project should always base "
-"their work on the latest code, available from the OpenStack-Helm git "
-"repository."
-msgstr ""
-"Developers wishing to work on the OpenStack-Helm project should always base "
-"their work on the latest code, available from the OpenStack-Helm git "
-"repository."
-
-msgid ""
-"Functions for Helm specific operations, found in helm.sh.  These functions "
-"include: installing Helm, serving a Helm repository locally, linting and "
-"building all Helm charts, running Helm tests on a release, installing the "
-"helm template plugin, and running the helm template plugin against a chart."
-msgstr ""
-"Functions for Helm specific operations, found in helm.sh.  These functions "
-"include: installing Helm, serving a Helm repository locally, linting and "
-"building all Helm charts, running Helm tests on a release, installing the "
-"helm template plugin, and running the helm template plugin against a chart."
-
-msgid ""
-"Functions for Kubernetes specific operations, found in kube.sh.  These "
-"functions include: waiting for pods in a specific namespace to register as "
-"ready, waiting for all nodes to register as ready, install the requirements "
-"for the kubeadm-aio container used in the gates, building the kubeadm-aio "
-"container, launching the kubeadm-aio container, and replacing the kube-"
-"controller-manager with a specific image necessary for ceph functionality."
-msgstr ""
-"Functions for Kubernetes specific operations, found in kube.sh.  These "
-"functions include: waiting for pods in a specific namespace to register as "
-"ready, waiting for all nodes to register as ready, install the requirements "
-"for the kubeadm-aio container used in the gates, building the kubeadm-aio "
-"container, launching the kubeadm-aio container, and replacing the kube-"
-"controller-manager with a specific image necessary for Ceph functionality."
-
-msgid ""
-"Functions for OpenStack specific operations, found in openstack.sh.  These "
-"functions include: waiting for a successful ping, and waiting for a booted "
-"virtual machine's status to return as ACTIVE."
-msgstr ""
-"Functions for OpenStack specific operations, found in openstack.sh.  These "
-"functions include: waiting for a successful ping, and waiting for a booted "
-"virtual machine's status to return as ACTIVE."
-
-msgid "Functions for common host preparation operations, found in common.sh"
-msgstr "Functions for common host preparation operations, found in common.sh"
-
-msgid ""
-"Functions for network specific operations, found in network.sh.  These "
-"functions include: creating a backup of the host's resolv.conf file before "
-"deploying the kubeadm environments, restoring the original resolv.conf "
-"settings, creating a backup of the host's /etc/hosts file before adding the "
-"hosts interface and address, and restoring the original /etc/hosts file."
-msgstr ""
-"Functions for network specific operations, found in network.sh.  These "
-"functions include: creating a backup of the host's resolv.conf file before "
-"deploying the kubeadm environments, restoring the original resolv.conf "
-"settings, creating a backup of the host's /etc/hosts file before adding the "
-"hosts interface and address, and restoring the original /etc/hosts file."
-
-msgid "Gate Checks"
-msgstr "Gate Checks"
-
-msgid "Gate Functions"
-msgstr "Gate Functions"
-
-msgid "Gate Output"
-msgstr "Gate Output"
-
-msgid "Indices and Tables"
-msgstr "Indices and Tables"
-
-msgid "Installation and Development"
-msgstr "Installation and Development"
-
-msgid ""
-"Join us on `IRC <irc://chat.oftc.net/openstack-helm>`_: #openstack-helm on "
-"oftc"
-msgstr ""
-"Join us on `IRC <irc://chat.oftc.net/openstack-helm>`_: #openstack-helm on "
-"oftc"
-
-msgid ""
-"Join us on `Slack <https://kubernetes.slack.com/messages/C3WERB7DE/>`_ - "
-"#openstack-helm"
-msgstr ""
-"Join us on `Slack <https://kubernetes.slack.com/messages/C3WERB7DE/>`_ - "
-"#openstack-helm"
-
-msgid ""
-"Meeting Agenda Items: `Agenda <https://etherpad.openstack.org/p/openstack-"
-"helm-meeting-agenda>`_"
-msgstr ""
-"Meeting Agenda Items: `Agenda <https://etherpad.openstack.org/p/openstack-"
-"helm-meeting-agenda>`_"
-
-msgid "Mission"
-msgstr "Mission"
-
-msgid "OpenStack-Helm"
-msgstr "OpenStack-Helm"
-
-msgid "OpenStack-Helm Gates"
-msgstr "OpenStack-Helm Gates"
-
-msgid "OpenStack-Helm currently checks the following scenarios:"
-msgstr "OpenStack-Helm currently checks the following scenarios:"
-
-msgid ""
-"OpenStack-Helm's single node and multinode gates leverage the kubeadm-aio "
-"environment created and maintained for use as a development environment.  "
-"All information regarding the kubeadm-aio environment can be found here_."
-msgstr ""
-"OpenStack-Helm's single node and multinode gates leverage the kubeadm-aio "
-"environment created and maintained for use as a development environment.  "
-"All information regarding the kubeadm-aio environment can be found here_."
-
-msgid ""
-"Please review our `documentation <https://docs.openstack.org/openstack-helm/"
-"latest/>`_. For quick installation, evaluation, and convenience, we have a "
-"minikube based all-in-one solution that runs in a Docker container. The set "
-"up can be found `here <https://docs.openstack.org/openstack-helm/latest/"
-"install/developer/index.html>`_."
-msgstr ""
-"Please review our `documentation <https://docs.openstack.org/openstack-helm/"
-"latest/>`_. For quick installation, evaluation, and convenience, we have a "
-"minikube based all-in-one solution that runs in a Docker container. The set "
-"up can be found `here <https://docs.openstack.org/openstack-helm/latest/"
-"install/developer/index.html>`_."
-
-msgid ""
-"Provisioning a multi-node Ubuntu-1604 cluster and deploying the OpenStack "
-"services. This check is provided for both a two node cluster and a three "
-"node cluster."
-msgstr ""
-"Provisioning a multi-node Ubuntu-1604 cluster and deploying the OpenStack "
-"services. This check is provided for both a two node cluster and a three "
-"node cluster."
-
-msgid ""
-"Provisioning a single node cluster and deploying the OpenStack services.  "
-"This check is provided for: Ubuntu-1604, CentOS-7, and Fedora-25."
-msgstr ""
-"Provisioning a single node cluster and deploying the OpenStack services.  "
-"This check is provided for: Ubuntu-1604, CentOS-7, and Fedora-25."
-
-msgid "Repository"
-msgstr "Repository"
-
-msgid ""
-"Running Make on each chart, which lints and packages the charts.  This gate "
-"does not stand up a Kubernetes cluster."
-msgstr ""
-"Running Make on each chart, which lints and packages the charts.  This gate "
-"does not stand up a Kubernetes cluster."
-
-msgid ""
-"Some services in the gate require specific overrides to the default values "
-"in the chart's values.yaml file.  If a service requires multiple overrides "
-"to function in the gate, the service should include a separate values.yaml "
-"file placed in the tools/overrides/mvp directory.  The <service>.yaml MVP "
-"files provide a configuration file to use for overriding default "
-"configuration values in the chart's values.yaml as an alternative to "
-"overriding individual values during installation.  A chart that requires a "
-"MVP overrides file requires the following format:"
-msgstr ""
-"Some services in the gate require specific overrides to the default values "
-"in the chart's values.yaml file.  If a service requires multiple overrides "
-"to function in the gate, the service should include a separate values.yaml "
-"file placed in the tools/overrides/mvp directory.  The <service>.yaml MVP "
-"files provide a configuration file to use for overriding default "
-"configuration values in the chart's values.yaml as an alternative to "
-"overriding individual values during installation.  A chart that requires a "
-"MVP overrides file requires the following format:"
-
-msgid "Storyboard"
-msgstr "Storyboard"
-
-msgid "Testing any documentation changes and impacts."
-msgstr "Testing any documentation changes and impacts."
-
-msgid ""
-"The K8s directory contains the logs and output of the Kubernetes objects.  "
-"It includes: pods, nodes, secrets, services, namespaces, configmaps, "
-"deployments, daemonsets, and statefulsets.  Descriptions for the state of "
-"all resources during execution are found here, and this information can "
-"prove valuable when debugging issues raised during a check.  When a single "
-"node or multi-node check fails, this is the first place to look.  The logs "
-"found here are helpful when the templates render correctly, but the services "
-"are not functioning correctly, whether due to service configuration issues "
-"or issues with the pods themselves."
-msgstr ""
-"The K8s directory contains the logs and output of the Kubernetes objects.  "
-"It includes: pods, nodes, secrets, services, namespaces, configmaps, "
-"deployments, daemonsets, and statefulsets.  Descriptions for the state of "
-"all resources during execution are found here, and this information can "
-"prove valuable when debugging issues raised during a check.  When a single "
-"node or multi-node check fails, this is the first place to look.  The logs "
-"found here are helpful when the templates render correctly, but the services "
-"are not functioning correctly, whether due to service configuration issues "
-"or issues with the pods themselves."
-
-msgid ""
-"The dry-runs directory contains the rendered output of Helm dry-run installs "
-"on each of the OpenStack service charts.  This gives visibility into the "
-"manifests created by the templates with the supplied values.  When the dry-"
-"run gate fails, the reason should be apparent in the dry-runs output.  The "
-"logs found here are helpful in identifying issues resulting from using helm-"
-"toolkit functions incorrectly or other rendering issues with gotpl."
-msgstr ""
-"The dry-runs directory contains the rendered output of Helm dry-run installs "
-"on each of the OpenStack service charts.  This gives visibility into the "
-"manifests created by the templates with the supplied values.  When the dry-"
-"run gate fails, the reason should be apparent in the dry-runs output.  The "
-"logs found here are helpful in identifying issues resulting from using helm-"
-"toolkit functions incorrectly or other rendering issues with gotpl."
-
-msgid ""
-"The goal of OpenStack-Helm is to provide a collection of Helm charts that "
-"simply, resiliently, and flexibly deploy OpenStack and related services on "
-"Kubernetes."
-msgstr ""
-"The goal of OpenStack-Helm is to provide a collection of Helm charts that "
-"simply, resiliently, and flexibly deploy OpenStack and related services on "
-"Kubernetes."
-
-msgid ""
-"The nodes directory contains information about the node the gate tests are "
-"running on in openstack-infra.  This includes: the network interfaces, the "
-"contents of iptables, the host's resolv.conf, and the kernel IP routing "
-"table. These logs can be helpful when trying to identify issues with host "
-"networking or other issues at the node level."
-msgstr ""
-"The nodes directory contains information about the node the gate tests are "
-"running on in openstack-infra.  This includes: the network interfaces, the "
-"contents of iptables, the host's resolv.conf, and the kernel IP routing "
-"table. These logs can be helpful when trying to identify issues with host "
-"networking or other issues at the node level."
-
-msgid ""
-"This project is under active development. We encourage anyone interested in "
-"OpenStack-Helm to review our `Installation <https://docs.openstack.org/"
-"openstack-helm/latest/install/index.html>`_ documentation. Feel free to ask "
-"questions or check out our current `Storyboard backlog <https://storyboard."
-"openstack.org/#!/project_group/64>`_."
-msgstr ""
-"This project is under active development. We encourage anyone interested in "
-"OpenStack-Helm to review our `Installation <https://docs.openstack.org/"
-"openstack-helm/latest/install/index.html>`_ documentation. Feel free to ask "
-"questions or check out our current `Storyboard backlog <https://storyboard."
-"openstack.org/#!/project_group/64>`_."
-
-msgid "This results in the gate running the following:"
-msgstr "This results in the gate running the following:"
-
-msgid ""
-"To evaluate a multinode installation, follow the `Bare Metal <https://docs."
-"openstack.org/openstack-helm/latest/install/multinode.html>`_ install guide."
-msgstr ""
-"To evaluate a multinode installation, follow the `Bare Metal <https://docs."
-"openstack.org/openstack-helm/latest/install/multinode.html>`_ install guide."
-
-msgid ""
-"To facilitate ease of testing and debugging, information regarding gates and "
-"their functionality can be found here."
-msgstr ""
-"To facilitate ease of testing and debugging, information regarding gates and "
-"their functionality can be found here."
-
-msgid ""
-"To provide meaningful output from the gates, all information pertaining to "
-"the components of the cluster and workflow are output to the logs directory "
-"inside each gate.  The contents of the log directory are as follows:"
-msgstr ""
-"To provide meaningful output from the gates, all information pertaining to "
-"the components of the cluster and workflow are output to the logs directory "
-"inside each gate.  The contents of the log directory are as follows:"
-
-msgid ""
-"To provide reusable components for gate functionality, functions have been "
-"provided in the gates/funcs directory. These functions include:"
-msgstr ""
-"To provide reusable components for gate functionality, functions have been "
-"provided in the gates/funcs directory. These functions include:"
-
-msgid ""
-"We welcome contributions. Check out `this <CONTRIBUTING.rst>`_ document if "
-"you would like to get involved."
-msgstr ""
-"We welcome contributions. Check out `this <CONTRIBUTING.rst>`_ document if "
-"you would like to get involved."
-
-msgid "Welcome to OpenStack-Helm's documentation!"
-msgstr "Welcome to OpenStack-Helm's documentation!"
-
-msgid ""
-"`OpenStack-Helm git repository <https://opendev.org/openstack/openstack-helm/"
-">`_"
-msgstr ""
-"`OpenStack-Helm git repository <https://opendev.org/openstack/openstack-helm/"
-">`_"
diff --git a/doc/source/locale/id/LC_MESSAGES/doc-contributor.po b/doc/source/locale/id/LC_MESSAGES/doc-contributor.po
deleted file mode 100644
index ecb4a8e3b3..0000000000
--- a/doc/source/locale/id/LC_MESSAGES/doc-contributor.po
+++ /dev/null
@@ -1,158 +0,0 @@
-# suhartono <cloudsuhartono@gmail.com>, 2020. #zanata
-msgid ""
-msgstr ""
-"Project-Id-Version: openstack-helm 0.1.1.dev3685\n"
-"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2022-04-06 21:47+0000\n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-"PO-Revision-Date: 2020-05-09 05:05+0000\n"
-"Last-Translator: suhartono <cloudsuhartono@gmail.com>\n"
-"Language-Team: Indonesian\n"
-"Language: id\n"
-"X-Generator: Zanata 4.3.3\n"
-"Plural-Forms: nplurals=1; plural=0\n"
-
-msgid ""
-"Additional information could be found in `OpenDev Developer's Guide <https://"
-"docs.opendev.org/opendev/infra-manual/latest/developers.html>`_."
-msgstr ""
-"Informasi tambahan dapat ditemukan di `OpenDev Developer's Guide <https://"
-"docs.opendev.org/opendev/infra-manual/latest/developers.html>`_."
-
-msgid ""
-"All common PTL duties are enumerated in the `PTL guide <https://docs."
-"openstack.org/project-team-guide/ptl.html>`_."
-msgstr ""
-"Semua tugas PTL umum disebutkan dalam `PTL guide <https://docs.openstack.org/"
-"project-team-guide/ptl.html>`_."
-
-msgid ""
-"Below will cover the more project specific information you need to get "
-"started with OpenStack-Helm."
-msgstr ""
-"Di bawah ini akan mencakup informasi spesifik proyek lebih lanjut yang Anda "
-"perlukan untuk memulai dengan OpenStack-Helm."
-
-msgid "Bugs should be filed as stories in Storyboard, not GitHub."
-msgstr "Bug harus diajukan sebagai cerita di Storyboard, bukan GitHub."
-
-msgid ""
-"Changes affecting code base often require CI tests and documentation to be "
-"added in the same patch set."
-msgstr ""
-"Changes affecting code base often require CI tests and documentation to be "
-"added in the same patch set."
-
-msgid "Communication"
-msgstr "Komunikasi"
-
-msgid "Contacting the Core Team"
-msgstr "Menghubungi Tim Inti (Core Team)"
-
-msgid ""
-"For general information on contributing to OpenStack, please check out the "
-"`contributor guide <https://docs.openstack.org/contributors/>`_ to get "
-"started. It covers all the basics that are common to all OpenStack projects: "
-"the accounts you need, the basics of interacting with our Gerrit review "
-"system, how we communicate as a community, etc."
-msgstr ""
-"Untuk informasi umum tentang kontribusi ke OpenStack, silakan periksa "
-"`panduan kontributor <https://docs.openstack.org/contributors/>` _ untuk "
-"memulai. Ini mencakup semua dasar-dasar yang umum untuk semua proyek "
-"OpenStack: akun yang Anda butuhkan, dasar-dasar berinteraksi dengan sistem "
-"ulasan Gerrit kami, cara kami berkomunikasi sebagai komunitas, dll."
-
-msgid "Getting Your Patch Merged"
-msgstr "Mendapatkan Patch Anda Digabung (Getting Your Patch Merged)"
-
-msgid ""
-"If issue is on one of other OpenStack-Helm components, report it to the "
-"appropriate `group Storyboard`_."
-msgstr ""
-"Jika ada masalah pada salah satu komponen OpenStack-Helm lainnya, laporkan "
-"ke `grup Storyboard`_ yang sesuai."
-
-msgid ""
-"If you're looking for some smaller, easier work item to pick up and get "
-"started on, search for the 'low-hanging-fruit' tag."
-msgstr ""
-"Jika Anda mencari item pekerjaan yang lebih kecil dan lebih mudah untuk "
-"diambil dan memulai, cari tag 'low-hanging-fruit'."
-
-msgid ""
-"Join us on `Slack <https://kubernetes.slack.com/messages/C3WERB7DE/>`_ - "
-"#openstack-helm"
-msgstr ""
-"Bergabunglah dengan kami di `Slack <https://kubernetes.slack.com/messages/"
-"C3WERB7DE/>`_ - #openstack-helm"
-
-msgid ""
-"Meeting Agenda Items: `Agenda <https://etherpad.openstack.org/p/openstack-"
-"helm-meeting-agenda>`_"
-msgstr ""
-"Item Agenda Rapat: `Agenda <https://etherpad.openstack.org/p/openstack-helm-"
-"meeting-agenda>`_"
-
-msgid "New Feature Planning"
-msgstr "Perencanaan Fitur Baru"
-
-msgid ""
-"New features are planned and implemented trough the process described in "
-"`Project Specifications <../specs/index.html>`_ section of this document."
-msgstr ""
-"Fitur-fitur baru direncanakan dan diimplementasikan melalui proses yang "
-"diuraikan dalam bagian `Project Specifications <../specs/index.html>`_ pada "
-"dokumen ini."
-
-msgid ""
-"Other OpenStack-Helm component's tasks could be found on the `group "
-"Storyboard`_."
-msgstr ""
-"Tugas komponen OpenStack-Helm lain dapat ditemukan di `group Storyboard`_."
-
-msgid "Project Team Lead Duties"
-msgstr "Project Team Lead Duties"
-
-msgid ""
-"Project's Core Team could be contacted via IRC or Slack, usually during "
-"weekly meetings. List of current Cores could be found on a Members tab of "
-"`openstack-helm-core <https://review.opendev.org/#/admin/groups/1749,info>`_ "
-"Gerrit group."
-msgstr ""
-"Tim Inti Proyek dapat dihubungi melalui IRC atau Slack, biasanya selama "
-"pertemuan mingguan. Daftar Core saat ini dapat ditemukan di tab Anggota "
-"`openstack-helm-core <https://review.opendev.org/#/admin/groups/1749,info>` "
-"_ grup Gerrit."
-
-msgid "Pull requests submitted through GitHub will be ignored."
-msgstr "Permintaan penarikan yang diajukan melalui GitHub akan diabaikan."
-
-msgid "Reporting a Bug"
-msgstr "Melaporkan Bug"
-
-msgid "So You Want to Contribute..."
-msgstr "Jadi Anda Ingin Berkontribusi ..."
-
-msgid "Task Tracking"
-msgstr "Pelacakan Tugas (Task Tracking)"
-
-msgid ""
-"We require two Code-Review +2's from reviewers, before getting your patch "
-"merged with giving Workforce +1. Trivial patches (e.g. typos) could be "
-"merged with one Code-Review +2."
-msgstr ""
-"Kami memerlukan dua Code-Review +2 dari reviewer, sebelum patch Anda "
-"digabung dengan memberikan Workforce +1. Patches sepele (mis. Kesalahan "
-"ketik) dapat digabung dengan satu Code-Review +2."
-
-msgid "We track our tasks on our StoryBoard_."
-msgstr "Kami melacak tugas Anda di StoryBoard Anda."
-
-msgid ""
-"You found an issue and want to make sure we are aware of it? You can do so "
-"on our Storyboard_."
-msgstr ""
-"Anda menemukan masalah dan ingin memastikan kami mengetahuinya? Anda dapat "
-"melakukannya di Storyboard_ kami."
diff --git a/doc/source/locale/id/LC_MESSAGES/doc-devref.po b/doc/source/locale/id/LC_MESSAGES/doc-devref.po
deleted file mode 100644
index 3d2daae642..0000000000
--- a/doc/source/locale/id/LC_MESSAGES/doc-devref.po
+++ /dev/null
@@ -1,1171 +0,0 @@
-# suhartono <cloudsuhartono@gmail.com>, 2018. #zanata
-# suhartono <cloudsuhartono@gmail.com>, 2019. #zanata
-msgid ""
-msgstr ""
-"Project-Id-Version: openstack-helm 0.1.1.dev3685\n"
-"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2022-04-06 21:47+0000\n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-"PO-Revision-Date: 2019-07-17 08:07+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 ""
-"**Note:** The values defined in a PodDisruptionBudget may conflict with "
-"other values that have been provided if an operator chooses to leverage "
-"Rolling Updates for deployments.  In the case where an operator defines a "
-"``maxUnavailable`` and ``maxSurge`` within an update strategy that is higher "
-"than a ``minAvailable`` within a pod disruption budget, a scenario may occur "
-"where pods fail to be evicted from a deployment."
-msgstr ""
-"**Note:** Nilai yang ditentukan dalam PodDisruptionBudget mungkin "
-"bertentangan dengan nilai lain yang telah disediakan jika operator memilih "
-"untuk memanfaatkan Pembaruan Bergulir untuk penyebaran. Dalam kasus di mana "
-"operator mendefinisikan `` maksUnavailable`` dan `` MaxSurge`` dalam "
-"strategi pembaruan yang lebih tinggi dari `` minimum Tersedia dalam anggaran "
-"gangguan pod, skenario dapat terjadi di mana pod gagal digusur dari sebuah "
-"penyebaran."
-
-msgid ""
-":code:`neutron/templates/bin/_neutron-linuxbridge-agent-init.sh.tpl` is "
-"configuring the tunnel IP, external bridge and all bridge mappings defined "
-"in config. It is done in init container, and the IP for tunneling is shared "
-"using file :code:`/tmp/pod-shared/ml2-local-ip.ini` with main linuxbridge "
-"container."
-msgstr ""
-":code:`neutron/templates/bin/_neutron-linuxbridge-agent-init.sh.tpl` "
-"mengkonfigurasi IP terowongan (tunnel IP), jembatan eksternal dan semua "
-"pemetaan jembatan yang didefinisikan dalam konfigurasi. Hal ini dilakukan "
-"dalam init container, dan IP untuk tunneling dibagi menggunakan file :code:`/"
-"tmp/pod-shared/ml2-local-ip.ini` dengan wadah linuxbridge utama."
-
-msgid ""
-"A detail worth mentioning is that ovs is configured to use sockets, rather "
-"than the default loopback mechanism."
-msgstr ""
-"Detail yang perlu disebutkan adalah bahwa ov dikonfigurasi untuk menggunakan "
-"soket, daripada mekanisme loopback default."
-
-msgid ""
-"A long-term goal, besides being image agnostic, is to also be able to "
-"support any of the container runtimes that Kubernetes supports, even those "
-"that might not use Docker's own packaging format. This will allow the "
-"project to continue to offer maximum flexibility with regard to operator "
-"choice."
-msgstr ""
-"Sasaran jangka panjang, selain sebagai image agnostik, juga dapat mendukung "
-"salah satu dari runtimes kontainer yang didukung Kubernetes, bahkan yang "
-"mungkin tidak menggunakan format pengepakan Docker sendiri. Ini akan "
-"memungkinkan proyek untuk terus menawarkan fleksibilitas maksimum berkaitan "
-"dengan pilihan operator."
-
-msgid ""
-"A typical Helm daemonset may leverage a secret to store configuration data. "
-"However, there are cases where the same secret document can't be used for "
-"the entire daemonset, because there are node-specific differences."
-msgstr ""
-"Daemonset Helm biasa dapat memanfaatkan rahasia untuk menyimpan data "
-"konfigurasi. Namun, ada kasus di mana dokumen rahasia yang sama tidak dapat "
-"digunakan untuk seluruh daemonset, karena ada perbedaan spesifik node."
-
-msgid "Adapting your daemonset to support node/nodelabel overrides"
-msgstr "Menyesuaikan daemonset Anda untuk mendukung override node/nodelabel"
-
-msgid ""
-"All ``Deployment`` chart components are outfitted by default with rolling "
-"update strategies:"
-msgstr ""
-"Semua komponen chart ``Deployment`` sudah dilengkapi secara default dengan "
-"strategi pembaruan bergulir:"
-
-msgid "All dependencies described in neutron-dhcp-agent are valid here."
-msgstr ""
-"Semua dependensi yang dijelaskan dalam neutron-dhcp-agent berlaku di sini."
-
-msgid ""
-"All of the above configs are endpoints or path to the specific class "
-"implementing the interface. You can see the endpoints to class mapping in "
-"`setup.cfg <https://github.com/openstack/neutron/"
-"blob/412c49b3930ce8aecb0a07aec50a9607058e5bc7/setup.cfg#L69>`_."
-msgstr ""
-"Semua konfigurasi di atas adalah endpoints atau path ke kelas khusus yang "
-"mengimplementasikan antarmuka. Anda dapat melihat endpoints pemetaan kelas "
-"di `setup.cfg <https://github.com/openstack/neutron/"
-"blob/412c49b3930ce8aecb0a07aec50a9607058e5bc7/setup.cfg#L69>`_."
-
-msgid ""
-"Also note that other non-overridden values are inherited by hosts and labels "
-"with overrides. The following shows a set of example hosts and the values "
-"fed into each:"
-msgstr ""
-"Perhatikan juga bahwa nilai-nilai non-override lainnya diwarisi oleh host "
-"dan label dengan override. Berikut ini menunjukkan sekumpulan host contoh "
-"dan nilai yang dimasukkan ke masing-masing:"
-
-msgid ""
-"An illustrative example of an ``images:`` section taken from the heat chart:"
-msgstr ""
-"Contoh ilustratif dari bagian ``images:``yang diambil dari  heat chart:"
-
-msgid ""
-"Another place where the DHCP agent is dependent on L2 agent is the "
-"dependency for the L2 agent daemonset:"
-msgstr ""
-"Tempat lain di mana agen DHCP bergantung pada agen L2 adalah ketergantungan "
-"untuk daemonset agen L2:"
-
-msgid ""
-"As an example, this line uses the ``endpoints.keystone_endpoint_uri_lookup`` "
-"macro in the ``helm-toolkit`` chart (since it is used by all charts). Note "
-"that there is a second convention here. All ``{{ define }}`` macros in "
-"charts should be pre-fixed with the chart that is defining them. This allows "
-"developers to easily identify the source of a Helm macro and also avoid "
-"namespace collisions. In the example above, the macro ``endpoints."
-"keystone_endpoint_uri_lookup`` is defined in the ``helm-toolkit`` chart. "
-"This macro is passing three parameters (aided by the ``tuple`` method built "
-"into the go/sprig templating library used by Helm):"
-msgstr ""
-"Sebagai contoh, baris ini menggunakan makro ``endpoints."
-"keystone_endpoint_uri_lookup`` dalam bagan ``helm-toolkit`` (karena "
-"digunakan oleh semua charts). Perhatikan bahwa ada konvensi kedua di sini. "
-"Semua makro ``{{ define }}`` dalam charts harus diperbaiki dengan charts "
-"yang mendefinisikannya. Ini memungkinkan pengembang untuk dengan mudah "
-"mengidentifikasi sumber makro Helm dan juga menghindari tabrakan namespace. "
-"Pada contoh di atas, makro ``endpoints.keystone_endpoint_uri_lookup`` "
-"didefinisikan dalam chart ``helm-toolkit``. Makro ini melewati tiga "
-"parameter (dibantu oleh metode ``tuple`` yang dibangun di perpustakaan "
-"templating go/sprig yang digunakan oleh Helm):"
-
-msgid ""
-"As part of Neutron chart, this daemonset is running Neutron OVS agent. It is "
-"dependent on having :code:`openvswitch-db` and :code:`openvswitch-vswitchd` "
-"deployed and ready. Since its the default choice of the networking backend, "
-"all configuration is in place in `neutron/values.yaml`. :code:`neutron-ovs-"
-"agent` should not be deployed when another SDN is used in `network.backend`."
-msgstr ""
-"Sebagai bagian dari Neutron chart, daemon ini menjalankan agen Neutron OVS. "
-"Ini tergantung pada pemilikan  :code:`openvswitch-db` dan :code:`openvswitch-"
-"vswitchd`  disebarkan dan siap. Karena ini adalah pilihan default dari "
-"backend jaringan, semua konfigurasi sudah ada di `neutron/values.yaml`. :"
-"code:`neutron-ovs-agent` tidak boleh digunakan ketika SDN lain digunakan "
-"dalam` network.backend`."
-
-msgid "Assume the chart name is ``mychart``."
-msgstr "Asumsikan nama chart ``mychart``."
-
-msgid ""
-"By default, each endpoint is located in the same namespace as the current "
-"service's helm chart. To connect to a service which is running in a "
-"different Kubernetes namespace, a ``namespace`` can be provided for each "
-"individual endpoint."
-msgstr ""
-"Secara default, setiap endpoint ditempatkan di namespace yang sama dengan "
-"chart helm layanan (service's helm) saat ini. Untuk menyambung ke layanan "
-"yang berjalan di namespace Kubernetes yang berbeda, ``namespace`` dapat "
-"diberikan ke setiap endpoint individual."
-
-msgid ""
-"Charts should not use hard coded values such as ``http://keystone-api:5000`` "
-"because these are not compatible with operator overrides and do not support "
-"spreading components out over various namespaces."
-msgstr ""
-"Charts tidak boleh menggunakan nilai berkode keras (hard coded values) "
-"seperti ``http://keystone-api:5000`` karena ini tidak kompatibel dengan "
-"penggantian operator dan tidak mendukung penyebaran komponen di berbagai "
-"namespaces."
-
-msgid ""
-"Configuration of OVS bridges can be done via `neutron/templates/bin/_neutron-"
-"openvswitch-agent-init.sh.tpl`. The script is configuring the external "
-"network bridge and sets up any bridge mappings defined in :code:`conf."
-"auto_bridge_add`.  These values should align with :code:`conf.plugins."
-"openvswitch_agent.ovs.bridge_mappings`."
-msgstr ""
-"Konfigurasi jembatan OVS dapat dilakukan melalui `neutron/templates/bin/"
-"_neutron-openvswitch-agent-init.sh.tpl`. Skrip mengkonfigurasi jembatan "
-"jaringan eksternal dan mengatur setiap pemetaan jembatan yang didefinisikan "
-"dalam :code:`conf.auto_bridge_add`. Nilai-nilai ini harus sejajar dengan "
-"(align with) :code:`conf.plugins.openvswitch_agent.ovs.bridge_mappings`."
-
-msgid ""
-"Configure neutron-server with SDN specific core_plugin/mechanism_drivers."
-msgstr ""
-"Konfigurasikan neutron-server dengan SDN specific core_plugin/"
-"mechanism_drivers."
-
-msgid "Configuring network plugin"
-msgstr "Mengonfigurasi plugin jaringan"
-
-msgid ""
-"Consider the following (simplified) secret and daemonset pairing example:"
-msgstr ""
-"Pertimbangkan contoh pairing rahasia dan daemonset (disederhanakan) berikut:"
-
-msgid "Contents:"
-msgstr "Contents (isi):"
-
-msgid "Create separate chart with new SDN deployment method."
-msgstr "Buat chart terpisah dengan metode penerapan SDN baru."
-
-msgid ""
-"Currently OpenStack-Helm supports OpenVSwitch and LinuxBridge as a network "
-"virtualization engines. In order to support many possible backends (SDNs), "
-"modular architecture of Neutron chart was developed. OpenStack-Helm can "
-"support every SDN solution that has Neutron plugin, either core_plugin or "
-"mechanism_driver."
-msgstr ""
-"Saat ini OpenStack-Helm mendukung OpenVSwitch dan LinuxBridge sebagai mesin "
-"virtualisasi jaringan. Untuk mendukung banyak kemungkinan backend (SDNs), "
-"arsitektur modular Neutron chart dikembangkan. OpenStack-Helm dapat "
-"mendukung setiap solusi SDN yang memiliki plugin Neutron, baik core_plugin "
-"atau mechanism_driver."
-
-msgid "DHCP - auto-assign IP address and DNS info"
-msgstr "DHCP - auto-assign IP address dan info DNS"
-
-msgid ""
-"DHCP agent is running dnsmasq process which is serving the IP assignment and "
-"DNS info. DHCP agent is dependent on the L2 agent wiring the interface. So "
-"one should be aware that when changing the L2 agent, it also needs to be "
-"changed in the DHCP agent. The configuration of the DHCP agent includes "
-"option `interface_driver`, which will instruct how the tap interface created "
-"for serving the request should be wired."
-msgstr ""
-"Agen DHCP menjalankan proses dnsmasq yang melayani penugasan IP (IP "
-"assignment) dan info DNS. Agen DHCP tergantung pada agen L2 yang "
-"menghubungkan antar muka. Jadi orang harus menyadari bahwa ketika mengubah "
-"agen L2, itu juga perlu diubah dalam agen DHCP. Konfigurasi agen DHCP "
-"termasuk opsi `interface_driver`, yang akan menginstruksikan bagaimana "
-"antarmuka tap yang dibuat untuk melayani permintaan harus ditransfer."
-
-msgid "Developer References"
-msgstr "Referensi Pengembang"
-
-msgid ""
-"EFK (Elasticsearch, Fluent-bit & Fluentd, Kibana) based Logging Mechanism"
-msgstr ""
-"EFK (Elasticsearch, Fluent-bit & Fluentd, Kibana) berdasarkan Logging "
-"Mechanism"
-
-msgid "Endpoints"
-msgstr "Endpoints (titik akhir)"
-
-msgid "Exercising node/nodelabel overrides"
-msgstr "Melaksanakan penggantian node/nodelabel"
-
-msgid ""
-"Fluent-bit, Fluentd meet OpenStack-Helm's logging requirements for "
-"gathering, aggregating, and delivering of logged events. Fluent-bit runs as "
-"a daemonset on each node and mounts the `/var/lib/docker/containers` "
-"directory. The Docker container runtime engine directs events posted to "
-"stdout and stderr to this directory on the host. Fluent-bit then forward the "
-"contents of that directory to Fluentd. Fluentd runs as deployment at the "
-"designated nodes and expose service for Fluent-bit to forward logs. Fluentd "
-"should then apply the Logstash format to the logs. Fluentd can also write "
-"kubernetes and OpenStack metadata to the logs. Fluentd will then forward the "
-"results to Elasticsearch and to optionally Kafka. Elasticsearch indexes the "
-"logs in a logstash-* index by default. Kafka stores the logs in a ``logs`` "
-"topic by default. Any external tool can then consume the ``logs`` topic."
-msgstr ""
-"Fluent-bit, Fluentd memenuhi persyaratan logging OpenStack-Helm untuk "
-"gathering, aggregating, dan delivering peristiwa yang tercatat. Fluent-bit "
-"berjalan sebagai daemonset pada setiap node dan me-mount direktori  `/var/"
-"lib/docker/containers`. Engine runtime kontainer Docker mengarahkan events "
-"yang diposting ke stdout dan stderr ke direktori ini pada host. Fluent-bit "
-"kemudian meneruskan isi direktori itu ke Fluentd. Fluentd berfungsi sebagai "
-"penyebaran (deployment) di node yang ditunjuk dan mengekspos layanan untuk "
-"Fluent-bit ke forward logs. Fluentd kemudian harus menerapkan format "
-"Logstash ke log. Fluentd juga dapat menulis metadata kubernetes dan "
-"OpenStack ke log. Fluentd kemudian akan meneruskan hasil ke Elasticsearch "
-"dan ke opsional Kafka. Elasticsearch mengindeks log dalam logstash-* index "
-"secara default. Kafka menyimpan log dalam topik ``log`` secara default. "
-"Setiap alat eksternal kemudian dapat mengkonsumsi topik ``log``."
-
-msgid ""
-"For example, if you have some special conf setting that should be applied to "
-"``host1.fqdn``, and another special conf setting that should be applied to "
-"nodes labeled with ``someNodeLabel``, then three secret/daemonset pairs will "
-"be generated and registered with kubernetes: one for ``host1.fqdn``, one for "
-"``someNodeLabel``, and one for ``default``."
-msgstr ""
-"Sebagai contoh, jika Anda memiliki beberapa pengaturan konfigurasi khusus "
-"yang harus diterapkan ke ``host1.fqdn``, dan pengaturan konfigurasi khusus "
-"lain yang harus diterapkan pada node yang berlabel ``someNodeLabel``, maka "
-"tiga pasangan secret/daemonset akan menjadi dihasilkan dan terdaftar dengan "
-"kubernetes: satu untuk ``host1.fqdn``, satu untuk ``someNodeLabel``, dan "
-"satu untuk ``default``."
-
-msgid ""
-"For instance, in the Neutron chart ``values.yaml`` the following endpoints "
-"are defined:"
-msgstr ""
-"Sebagai contoh, dalam Neutron chart ``values.yaml``, endpoint berikut "
-"didefinisikan:"
-
-msgid "Host overrides supercede label overrides"
-msgstr "Host mengesampingkan penggantian label supercede"
-
-msgid ""
-"If :code:`.Values.manifests.daemonset_ovs_agent` will be set to false, "
-"neutron ovs agent would not be launched. In that matter, other type of L2 or "
-"L3 agent on compute node can be run."
-msgstr ""
-"Jika :code:`.Values.manifests.daemonset_ovs_agent` akan disetel ke false, "
-"agen neutron ovs tidak akan diluncurkan. Dalam hal ini, jenis lain dari agen "
-"L2 atau L3 pada node komputasi dapat dijalankan."
-
-msgid ""
-"If a node matches more than one nodelabel, only the last matching nodelabel "
-"will apply (last in terms of the order the overrides are defined in the "
-"YAML)."
-msgstr ""
-"Jika sebuah node cocok dengan lebih dari satu nodelabel, hanya nodelabel "
-"yang cocok yang akan berlaku (terakhir dalam urutan urutan yang "
-"didefinisikan di dalam YAML)."
-
-msgid "If required, add new networking agent label type."
-msgstr "Jika diperlukan, tambahkan jenis label agen jaringan baru."
-
-msgid ""
-"If the SDN implements its own version of L3 networking, neutron-l3-agent "
-"should not be started."
-msgstr ""
-"Jika SDN mengimplementasikan versi jaringan L3nya sendiri, neutron-l3-agent "
-"tidak boleh dimulai."
-
-msgid ""
-"If the SDN of your choice is using the ML2 core plugin, then the extra "
-"options in `neutron/ml2/plugins/ml2_conf.ini` should be configured:"
-msgstr ""
-"Jika SDN pilihan Anda menggunakan plugin ML2 core, maka opsi tambahan di "
-"`neutron/ml2/plugins/ml2_conf.ini` harus dikonfigurasi:"
-
-msgid ""
-"If there is no matching FQDN and no matching nodelabel, then the default "
-"daemonset/secret (with no overrides applied) is used."
-msgstr ""
-"Jika tidak ada FQDN yang cocok dan tidak ada nodelabel yang cocok, maka "
-"daemonset/secret default (tanpa override diterapkan) digunakan."
-
-msgid "Images"
-msgstr "Images"
-
-msgid "Implementation details of node/nodelabel overrides"
-msgstr "Detail implementasi dari penggantian node/nodelabel"
-
-msgid ""
-"In ``values.yaml`` in each chart, the same defaults are supplied in every "
-"chart, which allows the operator to override at upgrade or deployment time."
-msgstr ""
-"Dalam ``values.yaml`` di setiap chart, default yang sama disediakan dalam "
-"setiap chart, yang memungkinkan operator untuk meng-override saat upgrade "
-"atau waktu deployment."
-
-msgid ""
-"In order to add support for more SDNs, these steps need to be performed:"
-msgstr ""
-"Untuk menambahkan dukungan untuk lebih banyak SDN, langkah-langkah ini perlu "
-"dilakukan:"
-
-msgid ""
-"In order to meet modularity criteria of Neutron chart, section `manifests` "
-"in :code:`neutron/values.yaml` contains boolean values describing which "
-"Neutron's Kubernetes resources should be deployed:"
-msgstr ""
-"Untuk memenuhi kriteria modularitas chart Neutron, bagian `manifes` dalam :"
-"code:`neutron/values.yaml` berisi nilai boolean yang menjelaskan sumber "
-"Kubernetes Neutron mana yang harus digunakan:"
-
-msgid ""
-"In order to use linuxbridge in your OpenStack-Helm deployment, you need to "
-"label the compute and controller/network nodes with `linuxbridge=enabled` "
-"and use this `neutron/values.yaml` override:"
-msgstr ""
-"Untuk menggunakan linuxbridge dalam penyebaran OpenStack-Helm Anda, Anda "
-"perlu memberi label node komputasi dan controller/network dengan "
-"`linuxbridge=enabled` dan menggunakan pengalih (override) `neutron/values."
-"yaml` ini:"
-
-msgid ""
-"Instead of having one daemonset with one monolithic secret, this helm-"
-"toolkit feature permits a common daemonset and secret template, from which "
-"daemonset and secret pairings are auto-generated. It supports establishing "
-"value overrides for nodes with specific label value pairs and for targeting "
-"nodes with specific hostnames and hostlabels. The overridden configuration "
-"is merged with the normal config data, with the override data taking "
-"precedence."
-msgstr ""
-"Alih-alih memiliki satu daemonset dengan satu rahasia monolitik, fitur helm-"
-"toolkit ini memungkinkan daemonset dan templat rahasia umum, yang darinya "
-"daemonset dan pasangan rahasia dibuat secara otomatis. Ini mendukung "
-"penetapan nilai override untuk node dengan pasangan nilai label tertentu dan "
-"untuk menargetkan node dengan nama host dan label host tertentu. Konfigurasi "
-"yang ditimpa digabungkan dengan data konfigurasi normal, dengan penimpaan "
-"data yang diutamakan."
-
-msgid ""
-"Introducing a new SDN solution should consider how the above services are "
-"provided. It maybe required to disable built-in Neutron functionality."
-msgstr ""
-"Memperkenalkan solusi SDN baru harus mempertimbangkan bagaimana layanan di "
-"atas disediakan. Mungkin diperlukan untuk menonaktifkan fungsi Neutron "
-"bawaan."
-
-msgid ""
-"L3 agent is serving the routing capabilities for Neutron networks. It is "
-"also dependent on the L2 agent wiring the tap interface for the routers."
-msgstr ""
-"Agen L3 melayani kemampuan routing untuk jaringan Neutron. Hal ini juga "
-"tergantung pada agen L2 yang memasang antarmuka keran (tap interface) untuk "
-"router."
-
-msgid "L3 routing - creation of routers"
-msgstr "L3 routing - pembuatan router"
-
-msgid "Linuxbridge"
-msgstr "Linuxbridge"
-
-msgid ""
-"Linuxbridge is the second type of Neutron reference architecture L2 agent. "
-"It is running on nodes labeled `linuxbridge=enabled`. As mentioned before, "
-"all nodes that are requiring the L2 services need to be labeled with "
-"linuxbridge. This includes both the compute and controller/network nodes. It "
-"is not possible to label the same node with both openvswitch and linuxbridge "
-"(or any other network virtualization technology) at the same time."
-msgstr ""
-"Linuxbridge adalah tipe kedua dari arsitektur referensi Neutron, agen L2. "
-"Ini berjalan pada node berlabel `linuxbridge=enabled`. Seperti disebutkan "
-"sebelumnya, semua node yang membutuhkan layanan L2 perlu diberi label dengan "
-"linuxbridge. Ini termasuk node komputasi dan controller/network. Tidaklah "
-"mungkin untuk melabeli node yang sama dengan baik openvswitch dan "
-"linuxbridge (atau teknologi virtualisasi jaringan lainnya) pada saat yang "
-"bersamaan."
-
-msgid "Logging Mechanism"
-msgstr "Logging Mechanism (mekanisme logging)"
-
-msgid "Logging Requirements"
-msgstr "Logging Requirements (persyaratan logging)"
-
-msgid "Metadata - Provide proxy for Nova metadata service"
-msgstr "Metadata - Menyediakan proxy untuk layanan metadata Nova"
-
-msgid ""
-"Metadata-agent is a proxy to nova-metadata service. This one provides "
-"information about public IP, hostname, ssh keys, and any tenant specific "
-"information. The same dependencies apply for metadata as it is for DHCP and "
-"L3 agents. Other SDNs may require to force the config driver in nova, since "
-"the metadata service is not exposed by it."
-msgstr ""
-"Metadata-agent adalah proxy untuk layanan nova-metadata. Yang satu ini "
-"memberikan informasi tentang IP publik, nama host, kunci ssh, dan informasi "
-"khusus penyewa apa pun. Ketergantungan yang sama berlaku untuk metadata "
-"seperti halnya untuk DHCP dan agen L3. SDN lain mungkin perlu memaksa driver "
-"konfigurasi di nova, karena layanan metadata tidak terkena olehnya."
-
-msgid "Networking"
-msgstr "Networking (jaringan)"
-
-msgid "Neutron architecture"
-msgstr "Arsitektur Neutron"
-
-msgid "Neutron chart includes the following services:"
-msgstr "Chart Neutron mencakup layanan berikut:"
-
-msgid ""
-"Neutron-server service is scheduled on nodes with `openstack-control-"
-"plane=enabled` label."
-msgstr ""
-"Layanan Neutron-server dijadwalkan pada node dengan label `openstack-control-"
-"plane=enabled`."
-
-msgid "Node and node label specific daemonset configurations"
-msgstr "Node dan konfigurasi node label spesifik daemonset"
-
-msgid "Note that only one set of overrides is applied per node, such that:"
-msgstr ""
-"Perhatikan bahwa hanya satu set penggantian diterapkan per node, sehingga:"
-
-msgid ""
-"Note that some additional values have been injected into the config file, "
-"this is performed via statements in the configmap template, which also calls "
-"the ``helm-toolkit.utils.to_oslo_conf`` to convert the yaml to the required "
-"layout:"
-msgstr ""
-"Perhatikan bahwa beberapa nilai tambahan telah disuntikkan ke file "
-"konfigurasi, ini dilakukan melalui pernyataan dalam template configmap, yang "
-"juga memanggil ``helm-toolkit.utils.to_oslo_conf`` untuk mengonversi yaml ke "
-"tata letak yang diperlukan:"
-
-msgid ""
-"Note: Rolling update values can conflict with values defined in each "
-"service's PodDisruptionBudget.  See `here <https://docs.openstack.org/"
-"openstack-helm/latest/devref/pod-disruption-budgets.html>`_ for more "
-"information."
-msgstr ""
-"Catatan: Nilai pembaruan bergulir dapat bertentangan dengan nilai yang "
-"ditentukan dalam PodDisruptionBudget layanan masing-masing. Lihat `here "
-"<https://docs.openstack.org/openstack-helm/latest/devref/pod-disruption-"
-"budgets.html>`_ untuk informasi lebih lanjut."
-
-msgid "Nova config dependency"
-msgstr "Nova config dependency"
-
-msgid "Nova vcpu example"
-msgstr "Contoh Nova vcpu"
-
-msgid ""
-"Now we can wrap the existing YAML to make it support node and nodelabel "
-"overrides, with minimal changes to the existing YAML (note where $secretName "
-"has been substituted):"
-msgstr ""
-"Sekarang kita dapat membungkus YAML yang ada untuk membuatnya mendukung node "
-"dan menimpa nodelabel, dengan sedikit perubahan pada YAML yang ada "
-"(perhatikan di mana $secretName telah diganti):"
-
-msgid "OSLO-Config Values"
-msgstr "OSLO-Config Values"
-
-msgid ""
-"OpenStack-Helm defines a centralized logging mechanism to provide insight "
-"into the state of the OpenStack services and infrastructure components as "
-"well as underlying Kubernetes platform. Among the requirements for a logging "
-"platform, where log data can come from and where log data need to be "
-"delivered are very variable. To support various logging scenarios, OpenStack-"
-"Helm should provide a flexible mechanism to meet with certain operation "
-"needs."
-msgstr ""
-"OpenStack-Helm mendefinisikan mekanisme logging terpusat untuk memberikan "
-"wawasan tentang keadaan layanan OpenStack dan komponen infrastruktur serta "
-"platform Kubernetes yang mendasari. Di antara persyaratan untuk platform "
-"logging, di mana data log dapat berasal dari dan di mana data log harus "
-"dikirimkan sangat bervariasi. Untuk mendukung berbagai skenario logging, "
-"OpenStack-Helm harus menyediakan mekanisme yang fleksibel untuk memenuhi "
-"kebutuhan operasi tertentu."
-
-msgid ""
-"OpenStack-Helm generates oslo-config compatible formatted configuration "
-"files for services dynamically from values specified in a yaml tree. This "
-"allows operators to control any and all aspects of an OpenStack services "
-"configuration. An example snippet for an imaginary Keystone configuration is "
-"described here:"
-msgstr ""
-"OpenStack-Helm menghasilkan file konfigurasi yang diformat oslo-config "
-"kompatibel untuk layanan secara dinamis dari nilai yang ditentukan dalam "
-"pohon yaml (yaml tree). Ini memungkinkan operator untuk mengontrol setiap "
-"dan semua aspek dari konfigurasi layanan OpenStack. Contoh cuplikan untuk "
-"konfigurasi Keystone imajiner dijelaskan di sini:"
-
-msgid ""
-"OpenStack-Helm leverages PodDisruptionBudgets to enforce quotas that ensure "
-"that a certain number of replicas of a pod are available at any given time.  "
-"This is particularly important in the case when a Kubernetes node needs to "
-"be drained."
-msgstr ""
-"OpenStack-Helm memanfaatkan PodDisruptBudgets untuk memberlakukan kuota yang "
-"memastikan bahwa sejumlah replika pod tersedia pada waktu tertentu. Ini "
-"sangat penting dalam kasus ketika node Kubernetes perlu dibersihkan (drained)"
-
-msgid ""
-"OpenStack-Helm provides fast and lightweight log forwarder and full featured "
-"log aggregator complementing each other providing a flexible and reliable "
-"solution. Especially, Fluent-bit is used as a log forwarder and Fluentd is "
-"used as a main log aggregator and processor."
-msgstr ""
-"OpenStack-Helm menyediakan log forwarder yang cepat dan ringan dan agregator "
-"log fitur lengkap yang saling melengkapi menyediakan solusi yang fleksibel "
-"dan dapat diandalkan. Terutama, Fluent-bit digunakan sebagai log forwarder "
-"dan Fluentd digunakan sebagai aggregator dan prosesor log utama."
-
-msgid "OpenVSwitch"
-msgstr "OpenVSwitch"
-
-msgid "Other SDNs"
-msgstr "SDN lainnya"
-
-msgid "Other networking services provided by Neutron are:"
-msgstr "Layanan jaringan lain yang disediakan oleh Neutron adalah:"
-
-msgid "Pod Disruption Budgets"
-msgstr "Pod Disruption Budgets"
-
-msgid ""
-"SDNs implementing ML2 driver can add extra/plugin-specific configuration "
-"options in `neutron/ml2/plugins/ml2_conf.ini`. Or define its own "
-"`ml2_conf_<name>.ini` file where configs specific to the SDN would be placed."
-msgstr ""
-"Mengimplementasikan driver MLN SDN dapat menambahkan opsi konfigurasi extra/"
-"plugin-specific di `neutron/ml2/plugins/ml2_conf.ini`. Atau tentukan sendiri "
-"file `ml2_conf_<name>.ini` di mana konfigurasi khusus untuk SDN akan "
-"ditempatkan."
-
-msgid ""
-"Script in :code:`neutron/templates/bin/_neutron-openvswitch-agent-init.sh."
-"tpl` is responsible for determining the tunnel interface and its IP for "
-"later usage by :code:`neutron-ovs-agent`. The IP is set in init container "
-"and shared between init container and main container with :code:`neutron-ovs-"
-"agent` via file :code:`/tmp/pod-shared/ml2-local-ip.ini`."
-msgstr ""
-"Skrip dalam :code:`neutron/templates/bin/_neutron-openvswitch-agent-init.sh."
-"tpl` bertanggung jawab untuk menentukan antarmuka terowongan (tunnel "
-"interface) dan IP-nya untuk digunakan nanti oleh :code:`neutron-ovs-agent`.  "
-"IP diatur dalam init container  dan dibagi antara init container  dan "
-"container utama dengan :code:`neutron-ovs-agent`  melalui file :code:`/tmp/"
-"pod-shared/ml2-local-ip.ini`."
-
-msgid ""
-"Some nodes may have a different vcpu_pin_set in nova.conf due to differences "
-"in CPU hardware."
-msgstr ""
-"Beberapa node mungkin memiliki vcpu_pin_set yang berbeda di nova.conf karena "
-"perbedaan dalam perangkat keras CPU."
-
-msgid ""
-"Specify if new SDN would like to use existing services from Neutron: L3, "
-"DHCP, metadata."
-msgstr ""
-"Tentukan apakah SDN baru ingin menggunakan layanan yang ada dari Neutron: "
-"L3, DHCP, metadata."
-
-msgid ""
-"The Neutron reference architecture provides mechanism_drivers :code:"
-"`OpenVSwitch` (OVS) and :code:`linuxbridge` (LB) with ML2 :code:"
-"`core_plugin` framework."
-msgstr ""
-"Arsitektur referensi Neutron menyediakan mechanism_drivers :code:"
-"`OpenVSwitch` (OVS) dan :code:`linuxbridge` (LB) with ML2 :code:"
-"`core_plugin` framework."
-
-msgid ""
-"The OpenStack-Helm project also implements annotations across all chart "
-"configmaps so that changing resources inside containers, such as "
-"configuration files, triggers a Kubernetes rolling update. This means that "
-"those resources can be updated without deleting and redeploying the service "
-"and can be treated like any other upgrade, such as a container image change."
-msgstr ""
-"Proyek OpenStack-Helm juga mengimplementasikan anotasi di semua chart "
-"configmaps sehingga mengubah sumber daya di dalam kontainer, seperti file "
-"konfigurasi, memicu pembaruan bergulir Kubernetes. Ini berarti bahwa sumber "
-"daya tersebut dapat diperbarui tanpa menghapus dan menerapkan ulang layanan "
-"dan dapat diperlakukan seperti peningkatan lainnya, seperti perubahan "
-"container image."
-
-msgid ""
-"The OpenStack-Helm project assumes all upgrades will be done through Helm. "
-"This includes handling several different resource types. First, changes to "
-"the Helm chart templates themselves are handled. Second, all of the "
-"resources layered on top of the container image, such as ``ConfigMaps`` "
-"which includes both scripts and configuration files, are updated during an "
-"upgrade. Finally, any image references will result in rolling updates of "
-"containers, replacing them with the updating image."
-msgstr ""
-"Proyek OpenStack-Helm mengasumsikan semua upgrade akan dilakukan melalui "
-"Helm. Ini termasuk menangani beberapa jenis sumber daya yang berbeda. "
-"Pertama, perubahan pada bagan Helm templates itu sendiri ditangani. Kedua, "
-"semua sumber daya yang berlapis di atas container image, seperti "
-"``ConfigMaps`` yang mencakup file skrip dan konfigurasi, diperbarui selama "
-"upgrade. Akhirnya, setiap referensi image akan menghasilkan pembaruan "
-"bergulir kontainer, menggantikannya dengan image yang diperbarui."
-
-msgid ""
-"The OpenStack-Helm project today uses a mix of Docker images from "
-"Stackanetes and Kolla, but will likely standardize on a default set of "
-"images for all charts without any reliance on image-specific utilities."
-msgstr ""
-"Proyek OpenStack-Helm saat ini menggunakan campuran image Docker dari "
-"Stackanetes dan Kolla, tetapi kemungkinan akan distandardisasi pada "
-"sekumpulan image default untuk semua chart tanpa bergantung pada image-"
-"specific utilities."
-
-msgid ""
-"The ``hash`` function defined in the ``helm-toolkit`` chart ensures that any "
-"change to any file referenced by configmap-bin.yaml or configmap-etc.yaml "
-"results in a new hash, which will then trigger a rolling update."
-msgstr ""
-"Fungsi ``hash`` yang ditentukan dalam chart ``helm-toolkit`` memastikan "
-"bahwa perubahan apa pun ke file apa pun yang direferensikan oleh configmap-"
-"bin.yaml atau configmap-etc.yaml menghasilkan hash baru, yang kemudian akan "
-"memicu pemutaran memperbarui."
-
-msgid "The above configuration options are handled by `neutron/values.yaml`:"
-msgstr "Opsi konfigurasi di atas ditangani oleh `neutron/values.yaml`:"
-
-msgid ""
-"The chart will then generate one daemonset for each host and label override, "
-"in addition to a default daemonset for which no overrides are applied. Each "
-"daemonset generated will also exclude from its scheduling criteria all other "
-"hosts and labels defined in other overrides for the same daemonset, to "
-"ensure that there is no overlap of daemonsets (i.e., one and only one "
-"daemonset of a given type for each node)."
-msgstr ""
-"Chart tersebut kemudian akan menghasilkan satu daemonset untuk setiap host "
-"dan label override, selain daemonset default yang tidak menerapkan override. "
-"Setiap daemonset yang dihasilkan juga akan mengecualikan dari kriteria "
-"penjadwalannya semua host dan label lain yang didefinisikan dalam override "
-"lainnya untuk daemonset yang sama, untuk memastikan bahwa tidak ada tumpang "
-"tindih daemonset (mis., satu dan hanya satu daemonset dari jenis yang "
-"diberikan untuk setiap node)."
-
-msgid ""
-"The farther down the list the label appears, the greater precedence it has. "
-"e.g., \"another-label\" overrides will apply to a node containing both "
-"labels."
-msgstr ""
-"Semakin jauh ke bawah daftar label muncul, semakin prioritas yang lebih "
-"besar itu. misalnya, penggantian \"another-label\"  akan menerapkan ke nodus "
-"yang berisi kedua label."
-
-msgid ""
-"The following example demonstrates how to exercise the node/nodelabel "
-"overrides:"
-msgstr ""
-"Contoh berikut menunjukkan bagaimana menjalankan penggantian node/nodelabel:"
-
-msgid ""
-"The following standards are in use today, in addition to any components "
-"defined by the service itself:"
-msgstr ""
-"Standar berikut sedang digunakan saat ini, selain komponen yang ditentukan "
-"oleh layanan itu sendiri:"
-
-msgid ""
-"The macros that help translate these into the actual URLs necessary are "
-"defined in the ``helm-toolkit`` chart. For instance, the cinder chart "
-"defines a ``glance_api_servers`` definition in the ``cinder.conf`` template:"
-msgstr ""
-"Makro yang membantu menerjemahkan ini ke URL yang sebenarnya diperlukan "
-"didefinisikan dalam chart ``helm-toolkit``. Sebagai contoh, chart cinder "
-"mendefinisikan definisi ``glance_api_servers`` dalam template ``cinder."
-"conf``:"
-
-msgid ""
-"The order of precedence for matches is FQDN, node label, and then default. "
-"If a node matches both a FQDN and a nodelabel, then only the FQDN override "
-"is applied. Pay special attention to adding FQDN overrides for nodes that "
-"match a nodelabel override, as you would need to duplicate the nodelabel "
-"overrides for that node in the FQDN overrides for them to still apply."
-msgstr ""
-"Urutan yang diutamakan untuk kecocokan adalah FQDN, label node, dan kemudian "
-"default. Jika sebuah node cocok dengan FQDN dan nodelabel, maka hanya "
-"override FQDN yang diterapkan. Berikan perhatian khusus untuk menambahkan "
-"override FQDN untuk node yang cocok dengan override nodelabel, karena Anda "
-"perlu menduplikasi override nodelabel untuk node di override FQDN agar "
-"mereka tetap berlaku."
-
-msgid ""
-"The ovs set of daemonsets are running on the node labeled "
-"`openvswitch=enabled`. This includes the compute and controller/network "
-"nodes. For more flexibility, OpenVSwitch as a tool was split out of Neutron "
-"chart, and put in separate chart dedicated OpenVSwitch. Neutron OVS agent "
-"remains in Neutron chart. Splitting out the OpenVSwitch creates "
-"possibilities to use it with different SDNs, adjusting the configuration "
-"accordingly."
-msgstr ""
-"Set ovs daemon berjalan di node berlabel  `openvswitch = enabled`. Ini "
-"termasuk node komputasi dan controller/network. Untuk fleksibilitas lebih, "
-"OpenVSwitch sebagai alat dibagi dari chart Neutron, dan dimasukkan ke dalam "
-"chart terpisah yang didedikasikan OpenVSwitch. Agen OVS Neutron tetap dalam "
-"chart Neutron. Memisahkan OpenVSwitch menciptakan kemungkinan untuk "
-"menggunakannya dengan SDN berbeda, menyesuaikan konfigurasi yang sesuai."
-
-msgid ""
-"The project's core philosophy regarding images is that the toolsets required "
-"to enable the OpenStack services should be applied by Kubernetes itself. "
-"This requires OpenStack-Helm to develop common and simple scripts with "
-"minimal dependencies that can be overlaid on any image that meets the "
-"OpenStack core library requirements. The advantage of this is that the "
-"project can be image agnostic, allowing operators to use Stackanetes, Kolla, "
-"LOCI, or any image flavor and format they choose and they will all function "
-"the same."
-msgstr ""
-"Filosofi inti proyek mengenai images adalah bahwa alat yang diperlukan untuk "
-"mengaktifkan layanan OpenStack harus diterapkan oleh Kubernetes itu sendiri. "
-"Hal ini membutuhkan OpenStack-Helm untuk mengembangkan skrip umum dan "
-"sederhana dengan dependensi minimal yang dapat dihamparkan (overlaid) pada "
-"images apa pun yang memenuhi persyaratan perpustakaan inti OpenStack. "
-"Keuntungan dari ini adalah bahwa proyek dapat menjadi agnostik image, yang "
-"memungkinkan operator untuk menggunakan Stackanetes, Kolla, LOCI, atau "
-"berbagai flavor dan format image yang mereka pilih dan semuanya akan "
-"berfungsi sama."
-
-msgid ""
-"The project's goal is to provide a consistent mechanism for endpoints. "
-"OpenStack is a highly interconnected application, with various components "
-"requiring connectivity details to numerous services, including other "
-"OpenStack components and infrastructure elements such as databases, queues, "
-"and memcached infrastructure. The project's goal is to ensure that it can "
-"provide a consistent mechanism for defining these \"endpoints\" across all "
-"charts and provide the macros necessary to convert those definitions into "
-"usable endpoints. The charts should consistently default to building "
-"endpoints that assume the operator is leveraging all charts to build their "
-"OpenStack cloud. Endpoints should be configurable if an operator would like "
-"a chart to work with their existing infrastructure or run elements in "
-"different namespaces."
-msgstr ""
-"Tujuan proyek adalah menyediakan mekanisme yang konsisten untuk endpoints. "
-"OpenStack adalah aplikasi yang sangat saling berhubungan, dengan berbagai "
-"komponen yang membutuhkan rincian konektivitas ke berbagai layanan, termasuk "
-"komponen OpenStack dan elemen infrastruktur lainnya seperti database, "
-"antrian (queues), dan infrastruktur memcache. Tujuan proyek adalah untuk "
-"memastikan bahwa ia dapat memberikan mekanisme yang konsisten untuk "
-"mendefinisikan \"endpoints\" ini di semua charts dan menyediakan makro yang "
-"diperlukan untuk mengubah definisi tersebut menjadi endpoints yang dapat "
-"digunakan. Charts tersebut harus secara konsisten menjadi standar untuk "
-"membangun endpoints yang mengasumsikan operator memanfaatkan semua charts "
-"untuk membangun cloud OpenStack mereka. Endpoints harus dapat dikonfigurasi "
-"jika operator ingin bagan bekerja dengan infrastruktur yang ada atau "
-"menjalankan elemen di namespaces yang berbeda."
-
-msgid ""
-"The resulting logs can then be queried directly through Elasticsearch, or "
-"they can be viewed via Kibana. Kibana offers a dashboard that can create "
-"custom views on logged events, and Kibana integrates well with Elasticsearch "
-"by default."
-msgstr ""
-"Log yang dihasilkan kemudian dapat ditanyakan secara langsung melalui "
-"Elasticsearch, atau mereka dapat dilihat melalui Kibana. Kibana menawarkan "
-"dasbor yang dapat membuat tampilan khusus pada acara yang dicatat, dan "
-"Kibana terintegrasi dengan baik dengan Elasticsearch secara default."
-
-msgid ""
-"There is also a need for DHCP agent to pass ovs agent config file (in :code:"
-"`neutron/templates/bin/_neutron-dhcp-agent.sh.tpl`):"
-msgstr ""
-"Ada juga kebutuhan untuk agen DHCP untuk melewati file konfigurasi agen ovs "
-"(in :code:`neutron/templates/bin/_neutron-dhcp-agent.sh.tpl`):"
-
-msgid ""
-"These quotas are configurable by modifying the ``minAvailable`` field within "
-"each PodDisruptionBudget manifest, which is conveniently mapped to a "
-"templated variable inside the ``values.yaml`` file. The ``min_available`` "
-"within each service's ``values.yaml`` file can be represented by either a "
-"whole number, such as ``1``, or a percentage, such as ``80%``.  For example, "
-"when deploying 5 replicas of a pod (such as keystone-api), using "
-"``min_available: 3`` would enforce policy to ensure at least 3 replicas were "
-"running, whereas using ``min_available: 80%`` would ensure that 4 replicas "
-"of that pod are running."
-msgstr ""
-"Kuota ini dapat dikonfigurasi dengan memodifikasi field ``minAvailable`` "
-"dalam setiap manifes PodDisruptBudget, yang mudah dipetakan ke variabel "
-"templated di dalam file ``values.yaml``. File ``min_available`` dalam setiap "
-"file ``values.yaml`` masing-masing layanan dapat direpresentasikan dengan "
-"seluruh angka, seperti ``1``, atau persentase, seperti ``80%``. Misalnya, "
-"ketika menggunakan 5 replika pod (seperti keystone-api), menggunakan "
-"``min_available: 3`` akan memberlakukan kebijakan untuk memastikan "
-"setidaknya 3 replika sedang berjalan, sedangkan menggunakan ``min_available: "
-"80%`` akan memastikan bahwa 4 replika pod itu sedang berjalan."
-
-msgid ""
-"These values define all the endpoints that the Neutron chart may need in "
-"order to build full URL compatible endpoints to various services. Long-term, "
-"these will also include database, memcached, and rabbitmq elements in one "
-"place. Essentially, all external connectivity can be defined centrally."
-msgstr ""
-"Nilai ini mendefinisikan semua endpoints yang mungkin diperlukan Neutron "
-"chart untuk membangun endpoint kompatibel URL lengkap ke berbagai layanan. "
-"Jangka panjang, ini juga akan mencakup elemen database, memcached, dan "
-"rabbitmq di satu tempat. Pada dasarnya, semua konektivitas eksternal dapat "
-"didefinisikan secara terpusat."
-
-msgid ""
-"This daemonset includes the linuxbridge Neutron agent with bridge-utils and "
-"ebtables utilities installed. This is all that is needed, since linuxbridge "
-"uses native kernel libraries."
-msgstr ""
-"Daemonset ini termasuk linuxbridge Neutron agent dengan utilitas bridge-"
-"utils dan ebtables yang diinstal. Ini semua yang diperlukan, karena "
-"linuxbridge menggunakan pustaka kernel native."
-
-msgid "This is accomplished with the following annotation:"
-msgstr "Ini dilakukan dengan anotasi berikut:"
-
-msgid ""
-"This option will allow to configure the Neutron services in proper way, by "
-"checking what is the actual backed set in :code:`neutron/values.yaml`."
-msgstr ""
-"Pilihan ini akan memungkinkan untuk mengkonfigurasi layanan Neutron dengan "
-"cara yang tepat, dengan memeriksa apa yang sebenarnya didukung di set "
-"dalam  :code:`neutron/values.yaml`."
-
-msgid ""
-"This requirement is OVS specific, the `ovsdb_connection` string is defined "
-"in `openvswitch_agent.ini` file, specifying how DHCP agent can connect to "
-"ovs. When using other SDNs, running the DHCP agent may not be required. When "
-"the SDN solution is addressing the IP assignments in another way, neutron's "
-"DHCP agent should be disabled."
-msgstr ""
-"Persyaratan ini khusus OVS, string `ovsdb_connection` didefinisikan dalam "
-"file `openvswitch_agent.ini`, menentukan bagaimana agen DHCP dapat terhubung "
-"ke ov. Saat menggunakan SDN lain, menjalankan agen DHCP mungkin tidak "
-"diperlukan. Ketika solusi SDN menangani  IP assignments dengan cara lain, "
-"agen DHCP neutron harus dinonaktifkan."
-
-msgid ""
-"This runs the OVS tool and database. OpenVSwitch chart is not Neutron "
-"specific, it may be used with other technologies that are leveraging the OVS "
-"technology, such as OVN or ODL."
-msgstr ""
-"Ini menjalankan OVS tool dan database. Chart OpenVSwitch tidak spesifik "
-"Neutron, ia dapat digunakan dengan teknologi lain yang memanfaatkan "
-"teknologi OVS, seperti OVN atau ODL."
-
-msgid ""
-"This will be consumed by the templated ``configmap-etc.yaml`` manifest to "
-"produce the following config file:"
-msgstr ""
-"Ini akan digunakan oleh manifasi ``configmap-etc.yaml`` manifes untuk "
-"menghasilkan file konfigurasi berikut:"
-
-msgid ""
-"To address this use-case, the ``helm-toolkit.utils.daemonset_overrides`` "
-"template was added in helm-toolkit. This was created with the intention that "
-"it should be straightforward to convert (wrap) a pre-existing daemonset with "
-"the functionality to override secret parameters on a per-node or per-"
-"nodelabel basis."
-msgstr ""
-"Untuk mengatasi kasus penggunaan ini, templat ``helm-toolkit.utils."
-"daemonset_overrides`` ditambahkan dalam helm-toolkit. Ini dibuat dengan "
-"tujuan untuk mengkonversi (membungkus) daemonset yang sudah ada sebelumnya "
-"dengan fungsi untuk mengesampingkan parameter rahasia pada basis per-node "
-"atau per-nodelabel."
-
-msgid ""
-"To address this, we can specify overrides in the values fed to the chart. Ex:"
-msgstr ""
-"Untuk mengatasinya, kita bisa menentukan override dalam nilai yang "
-"diumpankan ke chart. Ex:"
-
-msgid ""
-"To be able to configure multiple networking plugins inside of OpenStack-"
-"Helm, a new configuration option is added:"
-msgstr ""
-"Untuk dapat mengkonfigurasi beberapa plugin jaringan di dalam OpenStack-"
-"Helm, opsi konfigurasi baru ditambahkan:"
-
-msgid ""
-"To enable new SDN solution, there should be separate chart created, which "
-"would handle the deployment of service, setting up the database and any "
-"related networking functionality that SDN is providing."
-msgstr ""
-"Untuk mengaktifkan solusi SDN baru, harus ada bagan terpisah yang dibuat, "
-"yang akan menangani penyebaran layanan, pengaturan database dan fungsi "
-"jaringan terkait yang disediakan SDN."
-
-msgid ""
-"To that end, all charts provide an ``images:`` section that allows operators "
-"to override images. Also, all default image references should be fully "
-"spelled out, even those hosted by Docker or Quay. Further, no default image "
-"reference should use ``:latest`` but rather should be pinned to a specific "
-"version to ensure consistent behavior for deployments over time."
-msgstr ""
-"Untuk itu, semua charts menyediakan bagian ``images:``yang memungkinkan "
-"operator untuk mengganti image. Juga, semua referensi image default harus "
-"sepenuhnya tereja (spelled out), bahkan yang dihosting oleh Docker atau "
-"Quay. Lebih lanjut, tidak ada referensi image default yang harus menggunakan "
-"``:latest`` tetapi sebaiknya disematkan (pinned) ke versi tertentu untuk "
-"memastikan perilaku yang konsisten untuk penerapan dari waktu ke waktu."
-
-msgid ""
-"To use other Neutron reference architecture types of SDN, these options "
-"should be configured in :code:`neutron.conf`:"
-msgstr ""
-"Untuk menggunakan jenis arsitektur referensi Neutron lainnya dari SDN, opsi "
-"ini harus dikonfigurasi :code:`neutron.conf`:"
-
-msgid ""
-"Today, the ``images:`` section has several common conventions. Most "
-"OpenStack services require a database initialization function, a database "
-"synchronization function, and a series of steps for Keystone registration "
-"and integration. Each component may also have a specific image that composes "
-"an OpenStack service. The images may or may not differ, but regardless, "
-"should all be defined in ``images``."
-msgstr ""
-"Hari ini, bagian ``images:`` memiliki beberapa konvensi umum. Sebagian besar "
-"layanan OpenStack memerlukan fungsi inisialisasi basis data, fungsi "
-"sinkronisasi basis data, dan serangkaian langkah untuk pendaftaran dan "
-"integrasi Keystone. Setiap komponen juga dapat memiliki image khusus yang "
-"membentuk layanan OpenStack. Images mungkin atau mungkin tidak berbeda, "
-"tetapi bagaimanapun, semua harus didefinisikan dalam ``images``."
-
-msgid "Typical networking API request is an operation of create/update/delete:"
-msgstr ""
-"Permintaan API jaringan tipikal adalah operasi dari create/update/delete:"
-
-msgid "Upgrades and Reconfiguration"
-msgstr "Upgrades dan Konfigurasi Ulang"
-
-msgid ""
-"Your daemonset should now support node and nodelabl level overrides. (Note "
-"that you will also need your chart to have helm-toolkit listed as a "
-"dependency.)"
-msgstr ""
-"Daemonset Anda sekarang harus mendukung level node dan nodelabl. (Perhatikan "
-"bahwa Anda juga akan membutuhkan bagan Anda agar helm-toolkit terdaftar "
-"sebagai dependensi.)"
-
-msgid ""
-"``host1.fqdn`` with labels ``compute-type: dpdk, sriov`` and ``another-"
-"label: another-value``:"
-msgstr ""
-"``host1.fqdn`` dengan label ``compute-type: dpdk, sriov`` dan ``another-"
-"label: another-value``:"
-
-msgid ""
-"``host2.fqdn`` with labels ``compute-type: dpdk, sriov`` and ``another-"
-"label: another-value``:"
-msgstr ""
-"``host2.fqdn`` dengan label ``compute-type: dpdk, sriov`` dan ``another-"
-"label: another-value``:"
-
-msgid ""
-"``host3.fqdn`` with labels ``compute-type: dpdk, sriov`` and ``another-"
-"label: another-value``:"
-msgstr ""
-"``host3.fqdn`` dengan label ``compute-type: dpdk, sriov`` dan ``another-"
-"label: another-value``:"
-
-msgid "``host4.fqdn`` with labels ``compute-type: dpdk, sriov``:"
-msgstr "``host4.fqdn`` dengan label ``compute-type: dpdk, sriov``:"
-
-msgid "``host5.fqdn`` with no labels:"
-msgstr "``host5.fqdn`` tanpa label:"
-
-msgid ""
-"db\\_drop: The image that will perform database deletion operations for the "
-"OpenStack service."
-msgstr ""
-"db\\_drop: Image yang akan melakukan operasi penghapusan basis data untuk "
-"layanan OpenStack."
-
-msgid ""
-"db\\_init: The image that will perform database creation operations for the "
-"OpenStack service."
-msgstr ""
-"db\\_init: Image yang akan melakukan operasi pembuatan basis data untuk "
-"layanan OpenStack."
-
-msgid ""
-"db\\_sync: The image that will perform database sync (schema initialization "
-"and migration) for the OpenStack service."
-msgstr ""
-"db\\_sync: Image yang akan melakukan sinkronisasi database (skema "
-"inisialisasi dan migrasi) untuk layanan OpenStack."
-
-msgid ""
-"dep\\_check: The image that will perform dependency checking in an init-"
-"container."
-msgstr ""
-"dep\\_check: Image yang akan melakukan pemeriksaan dependensi dalam init-"
-"container."
-
-msgid ""
-"image: This is the OpenStack service that the endpoint is being built for. "
-"This will be mapped to ``glance`` which is the image service for OpenStack."
-msgstr ""
-"image: Ini adalah layanan OpenStack yang endpoint sedang dibangun. Ini akan "
-"dipetakan ke ``glance`` yang merupakan layanan image untuk OpenStack."
-
-msgid ""
-"internal: This is the OpenStack endpoint type we are looking for - valid "
-"values would be ``internal``, ``admin``, and ``public``"
-msgstr ""
-"internal: Ini adalah tipe endpoint OpenStack yang kami cari - nilai yang "
-"valid adalah ``internal``, ``admin``, dan ``public``"
-
-msgid ""
-"ks\\_endpoints: The image that will perform keystone endpoint registration "
-"for the service."
-msgstr ""
-"ks\\_endpoints: Image yang akan melakukan pendaftaran endpoint keystone "
-"untuk layanan."
-
-msgid ""
-"ks\\_service: The image that will perform keystone service registration for "
-"the service."
-msgstr ""
-"ks\\_service: Image yang akan melakukan pendaftaran layanan keystone untuk "
-"layanan."
-
-msgid ""
-"ks\\_user: The image that will perform keystone user creation for the "
-"service."
-msgstr ""
-"ks\\_user: Image yang akan melakukan pembuatan pengguna keystone untuk "
-"layanan ini."
-
-msgid "network"
-msgstr "network"
-
-msgid "neutron-dhcp-agent"
-msgstr "neutron-dhcp-agent"
-
-msgid ""
-"neutron-dhcp-agent service is scheduled to run on nodes with the label "
-"`openstack-control-plane=enabled`."
-msgstr ""
-"layanan neutron-dhcp-agent dijadwalkan untuk berjalan di node dengan label "
-"`openstack-control-plane=enabled`."
-
-msgid "neutron-l3-agent"
-msgstr "neutron-l3-agent"
-
-msgid ""
-"neutron-l3-agent service is scheduled to run on nodes with the label "
-"`openstack-control-plane=enabled`."
-msgstr ""
-"layanan neutron-l3-agent dijadwalkan untuk berjalan di node dengan label "
-"`openstack-control-plane=enabled`."
-
-msgid "neutron-lb-agent"
-msgstr "neutron-lb-agent"
-
-msgid "neutron-metadata-agent"
-msgstr "neutron-metadata-agent"
-
-msgid ""
-"neutron-metadata-agent service is scheduled to run on nodes with the label "
-"`openstack-control-plane=enabled`."
-msgstr ""
-"layanan neutron-metadata-agent dijadwalkan untuk berjalan di node dengan "
-"label  `openstack-control-plane=enabled`."
-
-msgid "neutron-ovs-agent"
-msgstr "neutron-ovs-agent"
-
-msgid "neutron-server"
-msgstr "neutron-server"
-
-msgid ""
-"neutron-server is serving the networking REST API for operator and other "
-"OpenStack services usage. The internals of Neutron are highly flexible, "
-"providing plugin mechanisms for all networking services exposed. The "
-"consistent API is exposed to the user, but the internal implementation is up "
-"to the chosen SDN."
-msgstr ""
-"neutron-server melayani API REST jaringan untuk operator dan penggunaan "
-"layanan OpenStack lainnya. Internal Neutron sangat fleksibel, menyediakan "
-"mekanisme plugin untuk semua layanan jaringan yang terbuka. API yang "
-"konsisten terpapar kepada pengguna, tetapi implementasi internal terserah "
-"pada SDN yang dipilih."
-
-msgid "openvswitch-db and openvswitch-vswitchd"
-msgstr "openvswitch-db dan openvswitch-vswitchd"
-
-msgid "port"
-msgstr "port"
-
-msgid ""
-"pull\\_policy: The image pull policy, one of \"Always\", \"IfNotPresent\", "
-"and \"Never\" which will be used by all containers in the chart."
-msgstr ""
-"pull\\_policy: Kebijakan pengambilan image, salah satu \"Always\", "
-"\"IfNotPresent\", dan \"Never\" yang akan digunakan oleh semua kontainer "
-"dalam chart."
-
-msgid "subnet"
-msgstr "subnet"
diff --git a/doc/source/locale/id/LC_MESSAGES/doc-install.po b/doc/source/locale/id/LC_MESSAGES/doc-install.po
deleted file mode 100644
index 3a78306598..0000000000
--- a/doc/source/locale/id/LC_MESSAGES/doc-install.po
+++ /dev/null
@@ -1,1649 +0,0 @@
-# suhartono <cloudsuhartono@gmail.com>, 2018. #zanata
-# suhartono <cloudsuhartono@gmail.com>, 2019. #zanata
-# suhartono <cloudsuhartono@gmail.com>, 2020. #zanata
-msgid ""
-msgstr ""
-"Project-Id-Version: openstack-helm 0.1.1.dev3755\n"
-"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2022-05-25 23:10+0000\n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-"PO-Revision-Date: 2020-09-06 04:43+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 "**Check Chart Status**"
-msgstr "**Check Chart Status**"
-
-msgid ""
-"**First**, edit the ``values.yaml`` for Neutron, Glance, Horizon, Keystone, "
-"and Nova."
-msgstr ""
-"**First**, edit ``values.yaml`` untuk Neutron, Glance, Horizon, Keystone, "
-"dan Nova."
-
-msgid "**Review the Ingress configuration.**"
-msgstr "**Review the Ingress configuration.**"
-
-msgid ""
-"**Second** option would be as ``--set`` flags when calling ``helm install``"
-msgstr ""
-"Pilihan **Second** akan menjadi ``--set`` flags saat memanggil ``helm "
-"install``"
-
-msgid ""
-"**TaaS Agent, TaaS OVS Driver and TaaS SR-IOV Driver**: This forms the back-"
-"end of TaaS which runs as a ML2 agent extension on compute nodes. It handles "
-"the RPC calls made by TaaS Plugin and configures the mechanism driver, i.e. "
-"OpenVSwitch or SR-IOV Nic Switch."
-msgstr ""
-"**TaaS Agent, TaaS OVS Driver and TaaS SR-IOV Driver**: Ini membentuk back-"
-"end TaaS yang berjalan sebagai ekstensi agen ML2 pada node komputasi. Ini "
-"menangani panggilan RPC yang dibuat oleh TaaS Plugin dan mengkonfigurasi "
-"driver mekanisme, misal  OpenVSwitch atau SR-IOV Nic Switch."
-
-msgid ""
-"**TaaS Dashboard Plugin**: Horizon Plugin which adds GUI panels for TaaS "
-"resources in the Horizon Dashboard."
-msgstr ""
-"**TaaS Dashboard Plugin**: Horizon Plugin yang menambahkan panel GUI untuk "
-"sumber daya TaaS di Horizon Dashboard."
-
-msgid ""
-"**TaaS Plugin**: This is the front-end of TaaS which runs on controller node "
-"(Neutron server). This serves TaaS APIs and stores/retrieves TaaS "
-"configuration state to/from Neutron TaaS DB."
-msgstr ""
-"**TaaS Plugin**: Ini adalah front-end dari TaaS yang berjalan pada node "
-"pengontrol (server Neutron). Ini melayani TaaS API dan menyimpan/mengambil "
-"status konfigurasi TaaS ke/dari Neutron TaaS DB."
-
-msgid "16GB of RAM"
-msgstr "RAM 16GB"
-
-msgid "4 Cores"
-msgstr "4 Cores"
-
-msgid "48GB HDD"
-msgstr "48GB HDD"
-
-msgid "8 Cores"
-msgstr "8 Cores"
-
-msgid "8GB of RAM"
-msgstr "RAM 8GB"
-
-msgid ""
-"A correct DPDK configuration depends heavily on the specific hardware "
-"resources and its configuration. Before deploying Openvswitch with DPDK, "
-"check the amount and type of available hugepages on the host OS."
-msgstr ""
-"Konfigurasi DPDK yang benar sangat bergantung pada sumber daya perangkat "
-"keras spesifik dan konfigurasinya. Sebelum menggunakan Openvswitch dengan "
-"DPDK, periksa jumlah dan jenis hugepage yang tersedia di OS host."
-
-msgid "Activate the OpenStack namespace to be able to use Ceph"
-msgstr "Aktifkan namespace OpenStack untuk dapat menggunakan Ceph"
-
-msgid "Activate the openstack namespace to be able to use Ceph"
-msgstr "Aktifkan namespace openstack untuk dapat menggunakan Ceph"
-
-msgid ""
-"Add TaaS Dashboard dependency in ``requirements.txt`` file in ``openstack/"
-"horizon`` repo, i.e. https://opendev.org/openstack/horizon"
-msgstr ""
-"Tambahkan dependensi TaaS Dashboard dalam file ``requirement.txt`` di ``repo "
-"openstack/horizon``, yaitu https://opendev.org/openstack/horizon"
-
-msgid ""
-"Add TaaS and TaaS dashboard dependencies in :code:`upper-constraints.txt` "
-"file in :code:`openstack/requirements` repo, i.e. https://opendev.org/"
-"openstack/requirements"
-msgstr ""
-"Tambahkan TaaS dan dependensi dashboard TaaS dalam file :code:`upper-"
-"constraints.txt` dalam :code:`openstack/requirements` repo, i.e. https://"
-"opendev.org/openstack/requirements"
-
-msgid ""
-"Add TaaS dependency in ``requirements.txt`` file in ``openstack/neutron`` "
-"repo, i.e. https://opendev.org/openstack/neutron"
-msgstr ""
-"Tambahkan dependensi TaaS dalam file ``requirement.txt`` di repo ``openstack/"
-"neutron``, yaitu https://opendev.org/openstack/neutron "
-
-msgid "Add TaaS panel to Horizon Dashboard:"
-msgstr "Tambahkan panel TaaS ke Horizon Dashboard:"
-
-msgid ""
-"Add the address of the Kubernetes API, ``172.17.0.1``, and ``.svc.cluster."
-"local`` to your ``no_proxy`` and ``NO_PROXY`` environment variables."
-msgstr ""
-"Tambahkan alamat API Kubernetes, ``172,17,0,1``, dan ``.svc.cluster.local`` "
-"ke variabel lingkungan ``no_proxy`` dan ``NO_PROXY`` Anda."
-
-msgid ""
-"Add to the Install steps these flags - also adding a shell environment "
-"variable to save on repeat code."
-msgstr ""
-"Tambahkan ke langkah Instal flags ini - juga menambahkan variabel lingkungan "
-"shell untuk menghemat kode ulang."
-
-msgid "Adding a DPDK port to Openvswitch fails"
-msgstr "Menambahkan port DPDK ke Openvswitch gagal"
-
-msgid ""
-"Additional configuration variables can be found `here <https://github.com/"
-"openstack/openstack-helm-infra/blob/master/roles/deploy-kubeadm-aio-common/"
-"defaults/main.yml>`_. In particular, ``kubernetes_cluster_pod_subnet`` can "
-"be used to override the pod subnet set up by Calico (the default container "
-"SDN), if you have a preexisting network that conflicts with the default pod "
-"subnet of 192.168.0.0/16."
-msgstr ""
-"Variabel konfigurasi tambahan dapat ditemukan `here <https://github.com/"
-"openstack/openstack-helm-infra/blob/master/roles/deploy-kubeadm-aio-common/"
-"defaults/main.yml>`_. Khususnya, ``kubernetes_cluster_pod_subnet`` dapat "
-"digunakan untuk mengganti subnet pod yang diatur oleh Calico (kontainer "
-"default SDN), jika Anda memiliki jaringan yang sudah ada sebelumnya yang "
-"bertentangan (conflict) dengan subnet pod default 192.168.0.0/16."
-
-msgid ""
-"Additional information on Kubernetes Ceph-based integration can be found in "
-"the documentation for the `CephFS <https://github.com/kubernetes-incubator/"
-"external-storage/blob/master/ceph/cephfs/README.md>`_ and `RBD <https://"
-"github.com/kubernetes-incubator/external-storage/blob/master/ceph/rbd/README."
-"md>`_ storage provisioners, as well as for the alternative `NFS <https://"
-"github.com/kubernetes-incubator/external-storage/blob/master/nfs/README."
-"md>`_ provisioner."
-msgstr ""
-"Additional information on Kubernetes Ceph-based integration can be found in "
-"the documentation for the `CephFS <https://github.com/kubernetes-incubator/"
-"external-storage/blob/master/ceph/cephfs/README.md>`_ dan `RBD <https://"
-"github.com/kubernetes-incubator/external-storage/blob/master/ceph/rbd/README."
-"md>` _ storage provisioners, serta untuk alternatif `NFS <https: // github."
-"com/kubernetes-incubator/external-storage/blob/master/nfs/README.md>`_ "
-"provisioner."
-
-msgid ""
-"Additionally, the default configuration of the neutron chart must be adapted "
-"according to the underlying hardware. The corresponding configuration "
-"parameter is labeled with \"CHANGE-ME\" in the script \"values_overrides/"
-"dpdk.yaml\". Specifically, the \"ovs_dpdk\" configuration section should "
-"list all NICs which should be bound to DPDK with their corresponding PCI-"
-"IDs. Moreover, the name of each NIC needs to be unique, e.g., dpdk0, dpdk1, "
-"etc."
-msgstr ""
-"Selain itu, konfigurasi default grafik neutron harus disesuaikan sesuai "
-"dengan perangkat keras yang mendasarinya. Parameter konfigurasi yang sesuai "
-"diberi label dengan \"CHANGE-ME\" dalam skrip \"values_overrides/dpdk.yaml"
-"\".  Khususnya, bagian konfigurasi \"ovs_dpdk\" harus mencantumkan semua NIC "
-"yang harus terikat ke DPDK dengan PCI-ID yang sesuai. Selain itu, nama "
-"setiap NIC harus unik, mis., dpdk0, dpdk1, dll."
-
-msgid ""
-"After making the configuration changes, run a ``make`` and then install as "
-"you would from AIO or MultiNode instructions."
-msgstr ""
-"Setelah membuat perubahan konfigurasi, jalankan ``make`` dan kemudian instal "
-"seperti yang Anda lakukan dari instruksi AIO atau MultiNode."
-
-msgid ""
-"All commands below should be run as a normal user, not as root. Appropriate "
-"versions of Docker, Kubernetes, and Helm will be installed by the playbooks "
-"used below, so there's no need to install them ahead of time."
-msgstr ""
-"Semua perintah di bawah ini harus dijalankan sebagai pengguna biasa, bukan "
-"sebagai root. Versi Docker, Kubernetes, dan Helm yang sesuai akan dipasang "
-"oleh playbook yang digunakan di bawah ini, jadi tidak perlu menginstalnya "
-"terlebih dahulu."
-
-msgid ""
-"Alternatively, these steps can be performed by running the script directly::"
-msgstr ""
-"Atau, langkah-langkah ini dapat dilakukan dengan menjalankan skrip secara "
-"langsung ::"
-
-msgid ""
-"Alternatively, this step can be performed by running the script directly:"
-msgstr ""
-"Alternatifnya, langkah ini dapat dilakukan dengan menjalankan skrip secara "
-"langsung:"
-
-msgid ""
-"An Ingress is a collection of rules that allow inbound connections to reach "
-"the cluster services."
-msgstr ""
-"Ingress adalah kumpulan aturan yang memungkinkan koneksi masuk untuk "
-"menjangkau layanan kluster."
-
-msgid ""
-"Apart from the variables above with gerrit refspec values, additionally "
-"export following environment variables with values as applicable:"
-msgstr ""
-"Terlepas dari variabel di atas dengan nilai gerrit refspec, ekspor tambahan "
-"variabel lingkungan berikut dengan nilai yang berlaku:"
-
-msgid ""
-"As a final validation step, re-run the **openstack helm stack list** and "
-"**openstack helm keypair list** commands and confirm the returned results "
-"are shown as empty.::"
-msgstr ""
-"Sebagai langkah validasi terakhir, jalankan kembali **openstack helm stack "
-"list** dan **openstack helm keypair list** perintah dan konfirmasi hasil "
-"yang dikembalikan ditampilkan sebagai kosong.::"
-
-msgid ""
-"As any other Neutron plugin, TaaS neutron plugin functionality consists of "
-"following modules:"
-msgstr ""
-"Seperti plugin Neutron lainnya, fungsionalitas plugin neutron TaaS terdiri "
-"dari modul berikut:"
-
-msgid ""
-"Before deploying TaaS and/or TaaS Dashboard, it needs to be added in Neutron "
-"and/or Horizon LOCI images."
-msgstr ""
-"Sebelum menggunakan TaaS dan/atau TaaS Dashboard, perlu ditambahkan dalam "
-"image Neutron dan/atau Horizon LOCI."
-
-msgid ""
-"Below are some instructions and suggestions to help you get started with a "
-"Kubeadm All-in-One environment on Ubuntu 18.04. Other supported versions of "
-"Linux can also be used, with the appropriate changes to package installation."
-msgstr ""
-"Di bawah ini adalah beberapa petunjuk dan saran untuk membantu Anda memulai "
-"dengan lingkungan Kubeadm All-in-One di Ubuntu 18.04. Versi Linux yang "
-"didukung lainnya juga dapat digunakan, dengan perubahan yang sesuai untuk "
-"instalasi paket."
-
-msgid "Build the requirements LOCI image using above commit"
-msgstr "Buat persyaratan image LOCI menggunakan komit di atas"
-
-msgid ""
-"By default OSH will use Google DNS Server IPs (8.8.8.8, 8.8.4.4) and will "
-"update resolv.conf as a result. If those IPs are blocked by your proxy, "
-"running the OSH scripts will result in the inability to connect to anything "
-"on the network. These DNS nameserver entries can be changed by updating the "
-"external_dns_nameservers entry in the file ``openstack-helm-infra/tools/"
-"images/kubeadm-aio/assets/opt/playbooks/vars.yaml``."
-msgstr ""
-"Secara default, OSH akan menggunakan IP Server DNS Google (8.8.8.8, 8.8.4.4) "
-"dan sebagai hasilnya akan memperbarui resolv.conf. Jika IP tersebut diblokir "
-"oleh proxy Anda, menjalankan skrip OSH akan mengakibatkan ketidakmampuan "
-"untuk terhubung ke apa pun di jaringan. Entri nameserver DNS ini dapat "
-"diubah dengan memperbarui entri external_dns_nameservers dalam file "
-"``openstack-helm-infra/tools/images/kubeadm-aio/assets/opt/playbooks/vars."
-"yaml``."
-
-msgid ""
-"By default the Calico CNI will use ``192.168.0.0/16`` and Kubernetes "
-"services will use ``10.96.0.0/16`` as the CIDR for services. Check that "
-"these CIDRs are not in use on the development node before proceeding, or "
-"adjust as required."
-msgstr ""
-"Secara default, Calico CNI akan menggunakan layanan ``192.168.0.0/16`` dan "
-"Kubernetes akan menggunakan ``10.96.0.0/16`` sebagai CIDR untuk layanan. "
-"Periksa apakah CIDR ini tidak digunakan pada node pengembangan sebelum "
-"melanjutkan, atau sesuaikan sesuai kebutuhan."
-
-msgid ""
-"By default, this installation will use Google DNS Server IPs (8.8.8.8, "
-"8.8.4.4) and will update resolv.conf as a result. If those IPs are blocked "
-"by the proxy, this will overwrite the original DNS entries and result in the "
-"inability to connect to anything on the network behind the proxy. These DNS "
-"nameserver entries can be changed by updating the "
-"``external_dns_nameservers`` entry in this file:"
-msgstr ""
-"Secara default, instalasi ini akan menggunakan IP Server DNS Google "
-"(8.8.8.8, 8.8.4.4) dan sebagai hasilnya akan memperbarui resolv.conf. Jika "
-"IP tersebut diblokir oleh proxy, ini akan menimpa entri DNS asli dan "
-"mengakibatkan ketidakmampuan untuk terhubung ke apa pun di jaringan di "
-"belakang proxy. Entri nameserver DNS ini dapat diubah dengan memperbarui "
-"entri ``external_dns_nameservers`` dalam file ini:"
-
-msgid "Cleaning the Deployment"
-msgstr "Membersihkan Deployment"
-
-msgid "Clone the OpenStack-Helm Repos"
-msgstr "Mengkloning OpenStack-Helm Repos"
-
-msgid "Code examples below."
-msgstr "Contoh kode di bawah ini."
-
-msgid "Common Deployment Requirements"
-msgstr "Persyaratan Penerapan Umum"
-
-msgid "Configure OpenStack"
-msgstr "Konfigurasikan OpenStack"
-
-msgid "Configure TaaS in Neutron chart"
-msgstr "Konfigurasikan TaaS dalam chart Neutron"
-
-msgid ""
-"Configuring OpenStack for a particular production use-case is beyond the "
-"scope of this guide. Please refer to the OpenStack `Configuration <https://"
-"docs.openstack.org/latest/configuration/>`_ documentation for your selected "
-"version of OpenStack to determine what additional values overrides should be "
-"provided to the OpenStack-Helm charts to ensure appropriate networking, "
-"security, etc. is in place."
-msgstr ""
-"Mengonfigurasi OpenStack untuk kasus penggunaan produksi tertentu berada di "
-"luar ruang lingkup panduan ini. Silakan merujuk ke OpenStack `Configuration "
-"<https://docs.openstack.org/latest/configuration/>`_ dokumentasi untuk versi "
-"OpenStack pilihan Anda untuk menentukan apa penggantian nilai tambahan harus "
-"diberikan ke chart OpenStack-Helm untuk memastikan jaringan yang sesuai, "
-"keamanan, dll. sudah ada."
-
-msgid "Contents:"
-msgstr "Isi:"
-
-msgid ""
-"Copy the key: ``sudo cp ~/.ssh/id_rsa /etc/openstack-helm/deploy-key.pem``"
-msgstr ""
-"Salin kunci: ``sudo cp ~/.ssh/id_rsa /etc/openstack-helm/deploy-key.pem``"
-
-msgid "Create a patchset for ``openstack/horizon`` repo"
-msgstr "Buat patchset untuk repo ``openstack/horizon``"
-
-msgid "Create a patchset for ``openstack/neutron`` repo"
-msgstr "Buat patchset untuk repo ``openstack/neutron``"
-
-msgid "Create a patchset for ``openstack/requirements`` repo"
-msgstr "Buat patchset untuk repo ``openstack/requirements``"
-
-msgid "Create an environment file"
-msgstr "Buat file lingkungan"
-
-msgid "Create an inventory file"
-msgstr "Buat file inventaris"
-
-msgid ""
-"Create an ssh-key on the master node, and add the public key to each node "
-"that you intend to join the cluster."
-msgstr ""
-"Buat ssh-key pada node master, dan tambahkan kunci publik ke setiap node "
-"yang Anda inginkan untuk bergabung dengan cluster."
-
-msgid "Create loopback devices for CEPH"
-msgstr "Buat perangkat loopback untuk CEPH"
-
-msgid ""
-"Create two loopback devices for ceph as one disk for OSD data and other disk "
-"for block DB and block WAL. If loop0 and loop1  devices are busy in your "
-"case , feel free to change them in parameters by using --ceph-osd-data and --"
-"ceph-osd-dbwal options."
-msgstr ""
-"Buat dua perangkat loopback untuk ceph sebagai satu disk untuk data OSD dan "
-"disk lain untuk blok DB dan blok WAL. Jika perangkat loop0 dan loop1 sibuk "
-"dalam kasus Anda, jangan ragu untuk mengubahnya dalam parameter dengan "
-"menggunakan opsi --ceph-osd-data dan --ceph-osd-dbwal."
-
-msgid ""
-"Default log level for Neutron TaaS is :code:`INFO`. For changing it, "
-"override following parameter:"
-msgstr ""
-"Tingkat log default untuk Neutron TaaS adalah :code:`INFO`. Untuk "
-"mengubahnya, ganti parameter berikut:"
-
-msgid "Delete the keypair(s) returned from the list command above::"
-msgstr "Hapus keypair(s) yang dikembalikan dari perintah daftar di atas::"
-
-msgid ""
-"Delete the stacks returned from the *openstack helm stack list* command "
-"above::"
-msgstr ""
-"Hapus stacks yang dikembalikan dari *openstack helm stack list* perintah di "
-"atas ::"
-
-msgid ""
-"Depending on your specific proxy, https_proxy may be the same as http_proxy. "
-"Refer to your specific proxy documentation."
-msgstr ""
-"Bergantung pada proksi spesifik Anda, https_proxy mungkin sama dengan "
-"http_proxy. Rujuk ke dokumentasi proxy spesifik Anda."
-
-msgid "Deploy Barbican"
-msgstr "Terapkan Barbican"
-
-msgid "Deploy Ceph"
-msgstr "Terapkan Ceph"
-
-msgid "Deploy Cinder"
-msgstr "Terapkan Cinder"
-
-msgid "Deploy Compute Kit (Nova and Neutron)"
-msgstr "Menyebarkan Compute Kit (Nova dan Neutron)"
-
-msgid "Deploy Glance"
-msgstr "Terapkan Glance"
-
-msgid "Deploy Heat"
-msgstr "Terapkan Heat"
-
-msgid "Deploy Horizon"
-msgstr "Terapkan Horizon"
-
-msgid "Deploy Keystone"
-msgstr "Terapkan Keystone"
-
-msgid "Deploy Kubernetes & Helm"
-msgstr "Menyebarkan Kubernetes & Helm"
-
-msgid "Deploy Libvirt"
-msgstr "Terapkan Libvirt"
-
-msgid "Deploy MariaDB"
-msgstr "Terapkan MariaDB"
-
-msgid "Deploy Memcached"
-msgstr "Terapkan Memcached"
-
-msgid "Deploy NFS Provisioner"
-msgstr "Menerapkan NFS Provisioner"
-
-msgid "Deploy OVS-DPDK"
-msgstr "Menyebarkan OVS-DPDK"
-
-msgid "Deploy OpenStack-Helm"
-msgstr "Gunakan OpenStack-Helm"
-
-msgid "Deploy OpenvSwitch"
-msgstr "Terapkan OpenvSwitch"
-
-msgid "Deploy RabbitMQ"
-msgstr "Terapkan RabbitMQ"
-
-msgid "Deploy Rados Gateway for object store"
-msgstr "Menerapkan Rados Gateway untuk menyimpan objek"
-
-msgid "Deploy TaaS Dashboard Plugin"
-msgstr "Deploy TaaS Dashboard Plugin"
-
-msgid "Deploy TaaS Plugin"
-msgstr "Deploy TaaS Plugin"
-
-msgid "Deploy tap-as-a-service (TaaS) Neutron / Dashboard plugin"
-msgstr "Penyebaran plugin Tap-as-a-service (TaaS) Neutron/Dashboard"
-
-msgid "Deploy the ingress controller"
-msgstr "Pasang ingress controller"
-
-msgid "Deployment"
-msgstr "Penyebaran"
-
-msgid "Deployment With Ceph"
-msgstr "Deployment Dengan Ceph"
-
-msgid "Deployment With NFS"
-msgstr "Deployment Dengan NFS"
-
-msgid "Deployment with Tungsten Fabric"
-msgstr "Penerapan dengan Tungsten Fabric"
-
-msgid "Development"
-msgstr "Pengembangan"
-
-msgid "Environment tear-down"
-msgstr "Environment tear-down (lingkungan meruntuhkan)"
-
-msgid ""
-"Essentially the use of Ingress for OpenStack-Helm is an Nginx proxy service. "
-"Ingress (Nginx) is accessible by your cluster public IP - e.g. the IP "
-"associated with ``kubectl get pods -o wide --all-namespaces | grep ingress-"
-"api`` Ingress/Nginx will be listening for server name requests of \"keystone"
-"\" or \"keystone.openstack\" and will route those requests to the proper "
-"internal K8s Services. These public listeners in Ingress must match the "
-"external DNS that you will set up to access your OpenStack deployment. Note "
-"each rule also has a Service that directs Ingress Controllers allow access "
-"to the endpoints from within the cluster."
-msgstr ""
-"Pada dasarnya penggunaan Ingress for OpenStack-Helm adalah layanan proxy "
-"Nginx. Ingress (Nginx) dapat diakses oleh IP publik kluster Anda - mis. IP "
-"yang terkait dengan ``kubectl get pods -o wide --all-namespaces | grep "
-"ingress-api`` Ingress/Nginx akan mendengarkan permintaan nama server "
-"\"keystone\" atau \"keystone.openstack\" dan akan mengarahkan permintaan "
-"tersebut ke K8s Services internal yang tepat. Pendengar publik di Ingress "
-"harus sesuai dengan DNS eksternal yang akan Anda siapkan untuk mengakses "
-"penyebaran OpenStack Anda. Perhatikan setiap aturan (rule) juga memiliki "
-"Service yang mengarahkan Ingress Controllers memungkinkan akses ke endpoints "
-"dari dalam kluster."
-
-msgid "Examples"
-msgstr "Contoh"
-
-msgid ""
-"Execution of the **900-use-it.sh** script results in the creation of 4 heat "
-"stacks and a unique keypair enabling access to a newly created VM.  "
-"Subsequent runs of the **900-use-it.sh** script requires deletion of the "
-"stacks, a keypair, and key files, generated during the initial script "
-"execution."
-msgstr ""
-"Eksekusi skrip ** 900-use-it.sh ** menghasilkan penciptaan 4 heat stacks dan "
-"keypair unik yang memungkinkan akses ke VM yang baru dibuat. Proses "
-"selanjutnya dari skrip **900-use-it.sh ** memerlukan penghapusan stacks, "
-"keypair, dan key files, yang dihasilkan selama eksekusi skrip awal."
-
-msgid "Exercise the Cloud"
-msgstr "Latihlah Cloud"
-
-msgid "External DNS and FQDN"
-msgstr "External DNS dan FQDN"
-
-msgid "External DNS to FQDN/Ingress"
-msgstr "External DNS ke FQDN/Ingress"
-
-msgid ""
-"First you have to set up OpenStack and Linux versions and install needed "
-"packages"
-msgstr ""
-"Pertama, Anda harus mengatur versi OpenStack dan Linux dan menginstal paket "
-"yang diperlukan"
-
-msgid ""
-"For ``identity`` and ``dashboard`` at ``host_fdqn_override.public`` replace "
-"``null`` with the value as ``keystone.os.foo.org`` and ``horizon.os.foo.org``"
-msgstr ""
-"Untuk ``identity`` dan ``dashboard`` pada ``host_fdqn_override.public`` "
-"menggantikan ``null`` dengan nilai sebagai ``keystone.os.foo.org`` dan "
-"``horizon.os.foo.org``"
-
-msgid ""
-"For a deployment without cinder and horizon the system requirements are:"
-msgstr "Untuk penyebaran tanpa cinder dan horizon, persyaratan sistem adalah:"
-
-msgid ""
-"For a lab or proof-of-concept environment, the OpenStack-Helm gate scripts "
-"can be used to quickly deploy a multinode Kubernetes cluster using KubeADM "
-"and Ansible. Please refer to the deployment guide `here <./kubernetes-gate."
-"html>`__."
-msgstr ""
-"Untuk lingkungan lab atau proof-of-concept, skrip gerbang OpenStack-Helm "
-"dapat digunakan untuk dengan cepat menyebarkan kluster Kombetes multinode "
-"menggunakan KubeADM dan Ansible. Silakan lihat panduan penerapan `here <./"
-"kubernetes-gate.html>`__."
-
-msgid ""
-"For example if gerrit refspec for this commit is \"refs/changes/xx/xxxxxx/x"
-"\", so export the :code:`REQUIREMENTS_REF_SPEC` variable as follows:"
-msgstr ""
-"Misalnya jika gerrit refspec untuk commit ini adalah \"refs/changes/xx/"
-"xxxxxx/x\", jadi ekspor variabel :code:`REQUIREMENTS_REF_SPEC` sebagai "
-"berikut:"
-
-msgid ""
-"For example if gerrit refspec for this commit is \"refs/changes/xx/xxxxxx/x"
-"\"; so export the :code:`HORIZON_REF_SPEC` variable as follows:"
-msgstr ""
-"Sebagai contoh jika gerrit refspec untuk komit ini adalah \"refs/changes/xx/"
-"xxxxxx/x\"; jadi ekspor variabel :code:`HORIZON_REF_SPEC` sebagai berikut:"
-
-msgid ""
-"For example if gerrit refspec for this commit is \"refs/changes/xx/xxxxxx/x"
-"\"; so export the :code:`NEUTRON_REF_SPEC` variable as follows:"
-msgstr ""
-"Sebagai contoh jika gerrit refspec untuk komit ini adalah \"ref / "
-"perubahan / xx / xxxxxx / x\"; jadi ekspor variabel :code:`NEUTRON_REF_SPEC` "
-"sebagai berikut:"
-
-msgid "For more details, refer to TaaS specification: Tap-as-a-service_."
-msgstr "Untuk lebih jelasnya, lihat spesifikasi TaaS: Tap-as-a-service_."
-
-msgid ""
-"For other deployment options, select appropriate ``Deployment with ...`` "
-"option from `Index <../developer/index.html>`__ page."
-msgstr ""
-"Untuk opsi penerapan lainnya, pilih opsi ``Deployment with ...`` dari "
-"halaman `Index <../developer/index.html>`__ ."
-
-msgid "Gate-Based Kubernetes"
-msgstr "Gate-Based Kubernetes"
-
-msgid "Get the Nginx configuration from the Ingress Pod:"
-msgstr "Dapatkan konfigurasi Nginx dari Ingress Pod:"
-
-msgid "Get the ``helm status`` of your chart."
-msgstr "Dapatkan ``helm status`` dari chart Anda."
-
-msgid "Helm Chart Installation"
-msgstr "Pemasangan Helm Chart"
-
-msgid "Host Configuration"
-msgstr "Konfigurasi Host"
-
-msgid "Host Proxy & DNS Configuration"
-msgstr "Host Proxy dan Konfigurasi DNS"
-
-msgid ""
-"If OVS fails to start up because of no hugepages are available, check the "
-"configuration of the OVS daemonset. Older versions of helm-toolkit were not "
-"able to render hugepage configuration into the Kubernetes manifest and just "
-"removed the hugepage attributes. If no hugepage configuration is defined for "
-"the OVS daemonset, consider using a newer version of helm-toolkit."
-msgstr ""
-"Jika OVS gagal untuk memulai karena tidak ada hugepage yang tersedia, "
-"periksa konfigurasi daemonset OVS. Versi helm-toolkit yang lebih lama tidak "
-"dapat merender konfigurasi hugepage ke manifes Kubernetes dan hanya "
-"menghapus atribut hugepage. Jika tidak ada konfigurasi hugepage yang "
-"ditentukan untuk daemonset OVS, pertimbangkan untuk menggunakan versi helm-"
-"toolkit yang lebih baru."
-
-msgid ""
-"If doing an `AIO install <https://docs.openstack.org/openstack-helm/latest/"
-"install/developer/index.html>`__, all the ``--set`` flags"
-msgstr ""
-"Jika melakukan suatu `AIO install <https://docs.openstack.org/openstack-helm/"
-"latest/install/developer/index.html>`__, semua flags ``--set``"
-
-msgid ""
-"If you are not deploying OSH behind a proxy, skip this step and continue "
-"with \"Deploy Kubernetes & Helm\"."
-msgstr ""
-"Jika Anda tidak menggunakan OSH di belakang proxy, lewati langkah ini dan "
-"lanjutkan dengan \"Deploy Kubernetes & Helm\"."
-
-msgid "If you are not deploying OSH behind a proxy, skip this step."
-msgstr "Jika Anda tidak menggunakan OSH di belakang proxy, lewati langkah ini."
-
-msgid ""
-"Implementing the FQDN overrides **must** be done at install time. If you run "
-"these as helm upgrades, Ingress will notice the updates though none of the "
-"endpoint build-out jobs will run again, unless they are cleaned up manually "
-"or using a tool like Armada."
-msgstr ""
-"Menerapkan FQDN mengesampingkan **must** dilakukan pada waktu instalasi. "
-"Jika Anda menjalankan ini sebagai peningkatan helm, Ingress akan melihat "
-"pembaruan meskipun tidak ada tugas build-out endpoint yang akan berjalan "
-"lagi, kecuali mereka dibersihkan secara manual atau menggunakan alat seperti "
-"Armada."
-
-msgid ""
-"In order to access your OpenStack deployment on Kubernetes we can use the "
-"Ingress Controller or NodePorts to provide a pathway in. A background on "
-"Ingress, OpenStack-Helm fully qualified domain name (FQDN) overrides, "
-"installation, examples, and troubleshooting will be discussed here."
-msgstr ""
-"Untuk mengakses penyebaran OpenStack Anda di Kubernetes kita dapat "
-"menggunakan  Ingress Controller atau NodePorts untuk menyediakan jalur masuk "
-"(pathway in). Latar belakang tentang Ingress, OpenStack-Helm yang memenuhi "
-"syarat nama domain lengkap (FQDN) menimpa, pemasangan, contoh, dan pemecahan "
-"masalah akan dibahas di sini ."
-
-msgid ""
-"In order to allow OVS inside a pod to make use of hugepages, the "
-"corresponding type and amount of hugepages must be specified in the resource "
-"section of the OVS chart's values.yaml:"
-msgstr ""
-"Untuk memungkinkan OVS di dalam pod menggunakan hugepage, jenis dan jumlah "
-"hugepage yang sesuai harus ditentukan di bagian sumber daya dari OVS chart's "
-"values.yaml:"
-
-msgid ""
-"In order to deploy OSH behind a proxy, add the following entries to "
-"``openstack-helm-infra/tools/gate/devel/local-vars.yaml``:"
-msgstr ""
-"Untuk menggunakan OSH di belakang proxy, tambahkan entri berikut ke "
-"``openstack-helm-infra/tools/gate/devel/local-vars.yaml``:"
-
-msgid ""
-"In order to deploy OpenStack-Helm behind corporate proxy servers, add the "
-"following entries to ``openstack-helm-infra/tools/gate/devel/local-vars."
-"yaml``."
-msgstr ""
-"Untuk menyebarkan OpenStack-Helm di belakang server proxy perusahaan, "
-"tambahkan entri berikut ini ``openstack-helm-infra/tools/gate/devel/local-"
-"vars.yaml``."
-
-msgid ""
-"In order to drive towards a production-ready OpenStack solution, our goal is "
-"to provide containerized, yet stable `persistent volumes <https://kubernetes."
-"io/docs/concepts/storage/persistent-volumes/>`_ that Kubernetes can use to "
-"schedule applications that require state, such as MariaDB (Galera). Although "
-"we assume that the project should provide a \"batteries included\" approach "
-"towards persistent storage, we want to allow operators to define their own "
-"solution as well. Examples of this work will be documented in another "
-"section, however evidence of this is found throughout the project. If you "
-"find any issues or gaps, please create a `story <https://storyboard."
-"openstack.org/#!/project/886>`_ to track what can be done to improve our "
-"documentation."
-msgstr ""
-"Untuk menuju solusi OpenStack yang siap produksi, tujuan kami adalah "
-"menyediakan paket kemas (containerized), namun stabil `persistent volumes "
-"<https://kubernetes.io/docs/concepts/storage/persistent-volumes/>`_ yang "
-"dapat Kubernetes gunakan untuk menjadwalkan aplikasi yang membutuhkan "
-"status, seperti MariaDB (Galera). Meskipun kami menganggap bahwa proyek "
-"harus memberikan pendekatan \"batteries included\" terhadap penyimpanan "
-"persisten, kami ingin mengizinkan operator untuk menentukan solusi mereka "
-"sendiri juga. Contoh pekerjaan ini akan didokumentasikan di bagian lain, "
-"namun bukti ini ditemukan di seluruh proyek. Jika Anda menemukan masalah "
-"atau celah, silakan buat `story <https://storyboard.openstack.org/#!/"
-"project/886>`_ untuk melacak apa yang dapat dilakukan untuk meningkatkan "
-"dokumentasi kami."
-
-msgid ""
-"In the example above, bonding isn't used and hence an empty list is passed "
-"in the \"bonds\" section."
-msgstr ""
-"Dalam contoh di atas, ikatan tidak digunakan dan karenanya daftar kosong "
-"dilewatkan di bagian \"bonds\"."
-
-msgid ""
-"In this example, 8 hugepages of 1G size have been allocated. 2 of those are "
-"being used and 6 are still available."
-msgstr ""
-"Dalam contoh ini, 8 hugepage ukuran 1G telah dialokasikan. 2 dari mereka "
-"sedang digunakan dan 6 masih tersedia."
-
-msgid ""
-"In this example, the NIC with PCI-ID 0000:00:04.0 is connected to NUMA "
-"socket 1. As a result, this NIC can only be used by OVS if"
-msgstr ""
-"Dalam contoh ini, NIC dengan PCI-ID 0000:00:04.0  terhubung ke soket NUMA 1. "
-"Akibatnya, NIC ini hanya dapat digunakan oleh OVS jika"
-
-msgid "Ingress"
-msgstr "Ingress"
-
-msgid "Install Basic Utilities"
-msgstr "Install Basic Utilities"
-
-msgid "Install OpenStack packages"
-msgstr "Instal paket OpenStack"
-
-msgid "Install OpenStack-Helm"
-msgstr "Memasang OpenStack-Helm"
-
-msgid "Install k8s Minikube"
-msgstr "Instal k8s Minikube"
-
-msgid "Installation"
-msgstr "Instalasi"
-
-msgid "Intro"
-msgstr "Intro"
-
-msgid ""
-"It can be configured to give services externally-reachable URLs, load "
-"balance traffic, terminate SSL, offer name based virtual hosting, and more."
-msgstr ""
-"Ini dapat dikonfigurasi untuk memberikan layanan URL yang dapat dijangkau "
-"secara eksternal, memuat keseimbangan lalu lintas (load balance traffic), "
-"mengakhiri SSL, menawarkan virtual hosting berbasis nama, dan banyak lagi."
-
-msgid ""
-"It is recommended to add your own existing DNS nameserver entries to avoid "
-"losing connection."
-msgstr ""
-"Disarankan untuk menambahkan entri server nama DNS Anda sendiri yang ada "
-"untuk menghindari kehilangan koneksi."
-
-msgid "Kubernetes Preparation"
-msgstr "Persiapan Kubernetes"
-
-msgid "Kubernetes and Common Setup"
-msgstr "Kubernetes dan Pengaturan Umum"
-
-msgid "Latest Version Installs"
-msgstr "Pemasangan Versi Terbaru"
-
-msgid "List the keypair(s) generated during the script execution::"
-msgstr "Daftar keypair(s) yang dihasilkan selama eksekusi skrip::"
-
-msgid ""
-"List the stacks created during script execution which will need to be "
-"deleted::"
-msgstr "Daftar stacks yang dibuat selama eksekusi skrip yang perlu dihapus ::"
-
-msgid ""
-"Look for *server* configuration with a *server_name* matching your desired "
-"FQDN"
-msgstr ""
-"Carilah konfigurasi *server* dengan *server_name* sesuai dengan FQDN yang "
-"Anda inginkan"
-
-msgid ""
-"Managing and configuring a Kubernetes cluster is beyond the scope of "
-"OpenStack-Helm and this guide."
-msgstr ""
-"Mengelola dan mengkonfigurasi kluster Kubernetes berada di luar lingkup "
-"OpenStack-Helm dan panduan ini."
-
-msgid ""
-"Manually remove the keypair directories created from the script in the ~/."
-"ssh directory::"
-msgstr ""
-"Hapus secara manual direktori keypair yang dibuat dari skrip di  ~/.ssh "
-"directory::"
-
-msgid ""
-"Many of the default container images that are referenced across OpenStack-"
-"Helm charts are not intended for production use; for example, while LOCI and "
-"Kolla can be used to produce production-grade images, their public reference "
-"images are not prod-grade.  In addition, some of the default images use "
-"``latest`` or ``master`` tags, which are moving targets and can lead to "
-"unpredictable behavior.  For production-like deployments, we recommend "
-"building custom images, or at minimum caching a set of known images, and "
-"incorporating them into OpenStack-Helm via values overrides."
-msgstr ""
-"Banyak image kontainer default yang direferensikan di chart OpenStack-Helm "
-"tidak dimaksudkan untuk penggunaan produksi; misalnya, sementara LOCI dan "
-"Kolla dapat digunakan untuk menghasilkan image tingkat produksi, image "
-"referensi publik mereka tidak bermutu (not prod-grade). Selain itu, beberapa "
-"image default menggunakan tag ``latest`` atau ``master``, yang merupakan "
-"target bergerak dan dapat menyebabkan perilaku yang tidak dapat diprediksi. "
-"Untuk penyebaran seperti produksi, kami menyarankan Anda untuk membuat image "
-"khusus, atau minimal cache satu set image yang dikenal, dan menggabungkannya "
-"ke OpenStack-Helm melalui penggantian nilai."
-
-msgid ""
-"More information can be found in the `Openvswitch documentation <http://docs."
-"openvswitch.org/en/latest/intro/install/dpdk/>`_."
-msgstr ""
-"Informasi lebih lanjut dapat ditemukan di `Openvswitch documentation <http://"
-"docs.openvswitch.org/en/latest/intro/install/dpdk/>`_."
-
-msgid ""
-"More information on how to allocate and configure hugepages on the host OS "
-"can be found in the `Openvswitch documentation <http://docs.openvswitch.org/"
-"en/latest/intro/install/dpdk/>`_."
-msgstr ""
-"Informasi lebih lanjut tentang cara mengalokasikan dan mengonfigurasi "
-"hugepage pada OS host dapat ditemukan di `Openvswitch documentation <http://"
-"docs.openvswitch.org/en/latest/intro/install/dpdk/>`_."
-
-msgid "Multinode"
-msgstr "Multinode"
-
-msgid "Neutron TaaS support in Openstack-Helm commits:"
-msgstr "Dukungan Neutron TaaS di komit Openstack-Helm:"
-
-msgid "Neutron and Horizon LOCI images"
-msgstr "image Neutron dan Horizon LOCI"
-
-msgid ""
-"Note if you need to make a DNS change, you will have to do uninstall (``helm "
-"delete <chart>``) and install again."
-msgstr ""
-"Catatan jika Anda perlu membuat perubahan DNS, Anda harus melakukan "
-"uninstall (``helm delete <chart>``) dan instal lagi."
-
-msgid ""
-"Note that this command will only enable you to auth successfully using the "
-"``python-openstackclient`` CLI. To use legacy clients like the ``python-"
-"novaclient`` from the CLI, reference the auth values in ``/etc/openstack/"
-"clouds.yaml`` and run::"
-msgstr ""
-"Perhatikan bahwa perintah ini hanya akan memungkinkan Anda untuk auth "
-"berhasil menggunakan ``python-openstackclient`` CLI. Untuk menggunakan klien "
-"legacy seperti ``python-novaclient`` dari CLI, referensi nilai auth di  ``/"
-"etc/openstack/clouds.yaml`` dan jalankan ::"
-
-msgid "OSH Proxy & DNS Configuration"
-msgstr "Konfigurasi Proxy & DNS OSH"
-
-msgid ""
-"OSH runs updates for local apt packages, so we will need to set the proxy "
-"for apt as well by adding these lines to `/etc/apt/apt.conf`:"
-msgstr ""
-"OSH menjalankan pembaruan untuk paket apt lokal, jadi kami juga perlu "
-"mengatur proxy untuk apt dengan menambahkan baris-baris ini ke  `/etc/apt/"
-"apt.conf`:"
-
-msgid "OVS startup failure"
-msgstr "Kegagalan startup OVS"
-
-msgid ""
-"On the host or master node, install the latest versions of Git, CA Certs & "
-"Make if necessary"
-msgstr ""
-"Pada host atau node master, instal versi terbaru Git, CA Certs & Make jika "
-"perlu"
-
-msgid "On the master node create an environment file for the cluster:"
-msgstr "Pada node master buat file lingkungan untuk kluster:"
-
-msgid "On the master node create an inventory file for the cluster:"
-msgstr "Pada node master buat file inventaris untuk kluster:"
-
-msgid "On the master node run the playbooks:"
-msgstr "Pada node master jalankan playbook:"
-
-msgid "On the worker nodes:"
-msgstr "Di worker nodes:"
-
-msgid ""
-"Once OpenStack-Helm has been deployed, the cloud can be exercised either "
-"with the OpenStack client, or the same heat templates that are used in the "
-"validation gates."
-msgstr ""
-"Setelah OpenStack-Helm dikerahkan, cloud dapat dijalankan baik dengan klien "
-"OpenStack, atau heat template yang sama yang digunakan di gate validasi."
-
-msgid ""
-"Once installed, access the API's or Dashboard at `http://horizon.os.foo.org`"
-msgstr "Setelah dipasang, akses API atau Dasbor di `http://horizon.os.foo.org`"
-
-msgid ""
-"Once the above requirements are met, start deploying Openstack Helm using "
-"the deployment scripts under the dpdk directory in an increasing order"
-msgstr ""
-"Setelah persyaratan di atas terpenuhi, mulailah menggunakan Openstack Helm "
-"menggunakan skrip deployment di bawah direktori dpdk dalam urutan yang "
-"meningkat"
-
-msgid ""
-"Once the host has been configured the repos containing the OpenStack-Helm "
-"charts should be cloned onto each node in the cluster:"
-msgstr ""
-"Setelah host dikonfigurasi, repositori yang berisi chart OpenStack-Helm "
-"harus dikloning ke setiap node dalam kluster:"
-
-msgid ""
-"Once the host has been configured the repos containing the OpenStack-Helm "
-"charts should be cloned:"
-msgstr ""
-"Setelah host dikonfigurasi, repositori yang berisi chart OpenStack-Helm "
-"harus dikloning:"
-
-msgid ""
-"One can also specify the name of Openstack release and container OS "
-"distribution as overrides before running the deployment scripts, for "
-"instance,"
-msgstr ""
-"Seseorang juga dapat menentukan nama rilis Openstack dan distribusi OS "
-"kontainer sebagai penggantian sebelum menjalankan skrip penyebaran, misalnya,"
-
-msgid ""
-"OpenStack-Helm uses the hosts networking namespace for many pods including, "
-"Ceph, Neutron and Nova components. For this, to function, as expected pods "
-"need to be able to resolve DNS requests correctly. Ubuntu Desktop and some "
-"other distributions make use of ``mdns4_minimal`` which does not operate as "
-"Kubernetes expects with its default TLD of ``.local``. To operate at "
-"expected either change the ``hosts`` line in the ``/etc/nsswitch.conf``, or "
-"confirm that it matches:"
-msgstr ""
-"OpenStack-Helm menggunakan namespace jaringan host untuk banyak pod "
-"termasuk, Ceph, Neutron dan Nova komponen. Untuk ini, berfungsi, seperti "
-"yang diharapkan pod harus dapat menyelesaikan permintaan DNS dengan benar. "
-"Desktop Ubuntu dan beberapa distro lain memanfaatkan ``mdns4_minimal`` yang "
-"tidak beroperasi karena Kubernetes mengharapkan dengan TLD defaultnya ``."
-"local``. Untuk beroperasi pada diharapkan baik mengubah baris ``host`` di ``/"
-"etc/nsswitch.conf``, atau konfirmasi bahwa itu cocok:"
-
-msgid ""
-"OpenStack-Helm utilizes the `Kubernetes Ingress Controller <https://"
-"kubernetes.io/docs/concepts/services-networking/ingress/>`__"
-msgstr ""
-"OpenStack-Helm memanfaatkan `Kubernetes Ingress Controller <https://"
-"kubernetes.io/docs/concepts/services-networking/ingress/>`__"
-
-msgid "OpenStack-Helm-Infra KubeADM deployment"
-msgstr "OpenStack-Helm-Infra KubeADM deployment"
-
-msgid ""
-"Other versions and considerations (such as other CNI SDN providers), config "
-"map data, and value overrides will be included in other documentation as we "
-"explore these options further."
-msgstr ""
-"Versi dan pertimbangan lain (seperti penyedia CNI SDN lainnya), data peta "
-"konfigurasi, dan penggantian nilai akan dimasukkan dalam dokumentasi lain "
-"saat kami mengeksplorasi opsi ini lebih lanjut."
-
-msgid "Override images in Neutron chart"
-msgstr "Override image dalam chart Neutron"
-
-msgid ""
-"Override the :code:`images` section parameters for Neutron chart with the "
-"custom LOCI image's tag, prepared as explained in above sections."
-msgstr ""
-"Override parameter bagian :code:`images` untuk chart Neutron dengan tag "
-"image LOCI kustom, disiapkan seperti dijelaskan di bagian di atas."
-
-msgid "Overview"
-msgstr "Ikhtisar"
-
-msgid "PMD threads have been assigned to NUMA socket 1."
-msgstr "Threads PMD telah ditetapkan ke soket NUMA 1."
-
-msgid "Passwordless Sudo"
-msgstr "Passwordless Sudo"
-
-msgid ""
-"Please see the supported application versions outlined in the `source "
-"variable file <https://github.com/openstack/openstack-helm-infra/blob/master/"
-"roles/build-images/defaults/main.yml>`_."
-msgstr ""
-"Silakan lihat versi aplikasi yang didukung yang diuraikan dalam `source "
-"variable file <https://github.com/openstack/openstack-helm-infra/blob/master/"
-"roles/build-images/defaults/main.yml>`_."
-
-msgid "Plugins"
-msgstr "Plugins"
-
-msgid "Prepare LOCI images"
-msgstr "Mempersiapkan image LOCI"
-
-msgid ""
-"Prepare Neutron or Horizon LOCI image using this requirements image as :code:"
-"`docker build --build-arg WHEELS` command argument."
-msgstr ""
-"Mempersiapkan image Neutron atau Horizon LOCI menggunakan image persyaratan "
-"ini sebagai argumen perintah :code:`docker build --build-arg WHEELS`."
-
-msgid ""
-"Prepare a requirements LOCI image with Neutron TaaS and TaaS Dashboard code "
-"installed."
-msgstr ""
-"Mempersiapkan persyaratan image LOCI dengan Neutron TaaS dan TaaS Dashboard "
-"code yang diinstal."
-
-msgid ""
-"Prepare ahead of time your FQDN and DNS layouts. There are a handful of "
-"OpenStack endpoints you will want to expose for API and Dashboard access."
-msgstr ""
-"Persiapkan sebelumnya tata letak FQDN dan DNS Anda. Ada beberapa endpoint "
-"OpenStack yang ingin Anda buka untuk akses API dan Dashboard."
-
-msgid "Prepare host"
-msgstr "Siapkan host"
-
-msgid "Prepare host and openstack helm for tf"
-msgstr "Siapkan host dan openstack helm untuk tf"
-
-msgid "Proxy Configuration"
-msgstr "Konfigurasi Proxy"
-
-msgid "Putting it all together"
-msgstr "Menyatukan semuanya"
-
-msgid "References"
-msgstr "Referensi"
-
-msgid "Removing Helm Charts"
-msgstr "Menghapus Helm Chart"
-
-msgid "Requirements"
-msgstr "Persyaratan"
-
-msgid "Requirements LOCI image"
-msgstr "Persyaratan image LOCI"
-
-msgid "Requirements and Host Configuration"
-msgstr "Persyaratan dan Konfigurasi Host"
-
-msgid "Run the playbooks"
-msgstr "Jalankan playbook"
-
-msgid "SSH-Key preparation"
-msgstr "Persiapan SSH-Key"
-
-msgid ""
-"Set correct ownership: ``sudo chown ubuntu /etc/openstack-helm/deploy-key."
-"pem``"
-msgstr ""
-"Setel kepemilikan yang benar: ``sudo chown ubuntu /etc/openstack-helm/deploy-"
-"key.pem``"
-
-msgid "Set log level for TaaS"
-msgstr "Setel tingkat log untuk TaaS"
-
-msgid ""
-"Set your local environment variables to use the proxy information. This "
-"involves adding or setting the following values in ``/etc/environment``:"
-msgstr ""
-"Setel variabel lingkungan lokal Anda untuk menggunakan informasi proxy. Ini "
-"melibatkan penambahan atau pengaturan nilai berikut di ``/etc/environment``:"
-
-msgid "Setup Clients on the host and assemble the charts"
-msgstr "Siapkan Klien pada host dan susun chart"
-
-msgid "Setup DNS for use cluster DNS"
-msgstr "Setup DNS untuk menggunakan DNS cluster"
-
-msgid "Setup Glance"
-msgstr "Setup Glance"
-
-msgid "Setup Heat"
-msgstr "Setup Heat"
-
-msgid "Setup Ingress"
-msgstr "Setup Ingress"
-
-msgid "Setup Keystone"
-msgstr "Setup Keystone"
-
-msgid "Setup MariaDB"
-msgstr "Setup MariaDB"
-
-msgid "Setup Memcached"
-msgstr "Setup Memcached"
-
-msgid "Setup NFS"
-msgstr "Setup NFS"
-
-msgid "Setup Neutron and Nova"
-msgstr "Setup Neutron dan Nova"
-
-msgid "Setup OpenStack client"
-msgstr "Atur klien OpenStack"
-
-msgid "Setup RabbitMQ"
-msgstr "Setup RabbitMQ"
-
-msgid "Setup Tungsten Fabric"
-msgstr "Setup Tungsten Fabric"
-
-msgid "Setup env for apply values_overrides"
-msgstr "Siapkan env untuk menerapkan values_overrides"
-
-msgid "Setup libvirt"
-msgstr "Setup libvirt"
-
-msgid "Setup the gateway to the public network"
-msgstr "Siapkan gateway ke jaringan publik"
-
-msgid "Subsequent Runs & Post Clean-up"
-msgstr "Subsequent Runs & Post Clean-up"
-
-msgid "System Requirements"
-msgstr "Persyaratan sistem"
-
-msgid "TaaS Architecture"
-msgstr "Arsitektur TaaS"
-
-msgid ""
-"TaaS dashboard plugin can be deployed simply by using custom LOCI images "
-"having TaaS Dashboard code installed (as explained in above sections), i.e. "
-"override the :code:`images` section parameters for Horizon charts:"
-msgstr ""
-"Plugin dashboard TaaS dapat digunakan hanya dengan menggunakan image LOCI "
-"kustom yang memasang kode Dashboard TaaS (seperti dijelaskan di bagian di "
-"atas), misal  override parameter bagian :code:`images`  untuk chart Horizon:"
-
-msgid ""
-"TaaS plugin provides a mechanism to mirror certain traffic (for example "
-"tagged with specific VLANs) from a source VM to any traffic analyzer VM. "
-"When packet will be forwarded, the original value of source and target ip/"
-"ports information will not be altered and the system administrator will be "
-"able to run, for ex. tcpdump, on the target VM to trace these packets."
-msgstr ""
-"Plugin TaaS menyediakan mekanisme untuk mencerminkan lalu lintas tertentu "
-"(misalnya ditandai dengan VLAN tertentu) dari sumber VM ke VM penganalisa "
-"lalu lintas apa pun. Ketika paket akan diteruskan, nilai asli sumber dan "
-"informasi target ip/port tidak akan diubah dan administrator sistem akan "
-"dapat berjalan, misalnya. tcpdump, pada VM target untuk melacak paket ini."
-
-msgid ""
-"Test this by ssh'ing to a node and then executing a command with 'sudo'. "
-"Neither operation should require a password."
-msgstr ""
-"Uji ini dengan ssh'ing ke node dan kemudian jalankan perintah dengan 'sudo'. "
-"Operasi tidak harus menggunakan kata sandi."
-
-msgid ""
-"The NUMA socket a given NIC is connected to can be found in the ovs-vswitchd "
-"log:"
-msgstr ""
-"Soket NUMA yang terhubung dengan NIC dapat ditemukan di log ovs-vswitchd:"
-
-msgid ""
-"The OpenStack clients and Kubernetes RBAC rules, along with assembly of the "
-"charts can be performed by running the following commands:"
-msgstr ""
-"Klien OpenStack dan aturan Kubernetes RBAC, bersama dengan perakitan chart "
-"dapat dilakukan dengan menjalankan perintah berikut:"
-
-msgid ""
-"The `./tools/deployment/multinode/kube-node-subnet.sh` script requires "
-"docker to run."
-msgstr ""
-"Script `./tools/deployment/multinode/kube-node-subnet.sh` membutuhkan docker "
-"untuk menjalankan."
-
-msgid ""
-"The ``.svc.cluster.local`` address is required to allow the OpenStack client "
-"to communicate without being routed through proxy servers. The IP address "
-"``172.17.0.1`` is the advertised IP address for the Kubernetes API server. "
-"Replace the addresses if your configuration does not match the one defined "
-"above."
-msgstr ""
-"Alamat ``.svc.cluster.local`` diperlukan untuk memungkinkan klien OpenStack "
-"berkomunikasi tanpa diarahkan melalui server proxy. Alamat IP ``172.17.0.1`` "
-"adalah alamat IP yang diiklankan (advertised) untuk server API Kubernetes. "
-"Ganti alamat jika konfigurasi Anda tidak sesuai dengan yang didefinisikan di "
-"atas."
-
-msgid "The default FQDN's for OpenStack-Helm are"
-msgstr "Default FQDN untuk OpenStack-Helm adalah"
-
-msgid ""
-"The example above uses the default values used by ``openstack-helm-infra``."
-msgstr ""
-"Contoh di atas menggunakan nilai default yang digunakan oleh ``openstack-"
-"helm-infra``."
-
-msgid ""
-"The following commands all assume that they are run from the ``/opt/"
-"openstack-helm`` directory."
-msgstr ""
-"Perintah berikut semua menganggap bahwa mereka dijalankan dari direktori  ``/"
-"opt/openstack-helm``."
-
-msgid ""
-"The following commands all assume that they are run from the ``openstack-"
-"helm`` directory and the repos have been cloned as above."
-msgstr ""
-"Perintah berikut semua berasumsi bahwa mereka dijalankan dari direktori "
-"``openstack-helm`` dan repo telah dikloning seperti di atas."
-
-msgid ""
-"The following steps serve as a guide to clean-up the client environment by "
-"deleting stacks and respective artifacts created during the **900-use-it."
-"sh** script:"
-msgstr ""
-"Langkah-langkah berikut berfungsi sebagai panduan untuk membersihkan "
-"lingkungan klien dengan menghapus stacks dan artefak masing-masing yang "
-"dibuat selama skrip **900-use-it.sh **:"
-
-msgid ""
-"The installation procedures below, will take an administrator from a new "
-"``kubeadm`` installation to OpenStack-Helm deployment."
-msgstr ""
-"Prosedur instalasi di bawah ini, akan mengambil administrator dari instalasi "
-"``kubeadm`` baru ke penyebaran OpenStack-Helm."
-
-msgid ""
-"The mapping of CPU cores to NUMA sockets can be determined by means of "
-"``lspci``, for instance:"
-msgstr ""
-"Pemetaan cores CPU ke soket NUMA dapat ditentukan dengan menggunakan "
-"``lspci``, misalnya:"
-
-msgid "The recommended minimum system requirements for a full deployment are:"
-msgstr ""
-"Persyaratan sistem minimum yang disarankan untuk penyebaran lengkap adalah:"
-
-msgid ""
-"The script below configures Ceph to use loopback devices created in previous "
-"step as backend for ceph osds. To configure a custom block device-based "
-"backend, please refer to the ``ceph-osd`` `values.yaml <https://github.com/"
-"openstack/openstack-helm/blob/master/ceph-osd/values.yaml>`_."
-msgstr ""
-"Script di bawah mengkonfigurasi Ceph untuk menggunakan perangkat loopback "
-"yang dibuat pada langkah sebelumnya sebagai backend untuk ceph osds. Untuk "
-"mengonfigurasi backend berbasis perangkat khusus blokir, silakan merujuk ke  "
-"``ceph-osd`` `values.yaml <https://github.com/openstack/openstack-helm/blob/"
-"master/ceph-osd/values.yaml>`_."
-
-msgid ""
-"The upstream Ceph image repository does not currently pin tags to specific "
-"Ceph point releases.  This can lead to unpredictable results in long-lived "
-"deployments.  In production scenarios, we strongly recommend overriding the "
-"Ceph images to use either custom built images or controlled, cached images."
-msgstr ""
-"Repositori image Ceph hulu saat ini tidak pin tag untuk rilis Ceph point "
-"tertentu. Hal ini dapat menyebabkan hasil yang tak terduga dalam penempatan "
-"jangka panjang. Dalam skenario produksi, kami sangat menyarankan untuk "
-"mengganti image Ceph untuk menggunakan apakah image yang dibuat khusus "
-"ataupun image yang dikontrol dan di-cache."
-
-msgid ""
-"These commands will restore the environment back to a clean Kubernetes "
-"deployment, that can either be manually removed or over-written by "
-"restarting the deployment process. It is recommended to restart the host "
-"before doing so to ensure any residual state, eg. Network interfaces are "
-"removed."
-msgstr ""
-"Perintah ini akan memulihkan lingkungan kembali ke penyebaran Kubernetes "
-"bersih, yang dapat dihapus secara manual atau ditulis berlebihan dengan "
-"memulai kembali proses penerapan. Dianjurkan untuk me-restart host sebelum "
-"melakukannya untuk memastikan setiap status yang tersisa, misalnya Network "
-"interfaces dihapus."
-
-msgid "These values can be retrieved by running:"
-msgstr "Nilai-nilai ini dapat diambil dengan menjalankan:"
-
-msgid ""
-"This guide assumes that users wishing to deploy behind a proxy have already "
-"defined the conventional proxy environment variables ``http_proxy``, "
-"``https_proxy``, and ``no_proxy``."
-msgstr ""
-"Panduan ini mengasumsikan bahwa pengguna yang ingin menyebarkan di belakang "
-"proxy telah mendefinisikan variabel lingkungan proksi konvensional "
-"``http_proxy``, ``https_proxy``, dan ``no_proxy``."
-
-msgid "This guide covers the minimum number of requirements to get started."
-msgstr "Panduan ini mencakup jumlah minimum persyaratan untuk memulai."
-
-msgid ""
-"This guide explains how to deploy tap-as-a-service (TaaS) Neutron plugin and "
-"TaaS Dashboard plugin in Neutron and Horizon charts respectively."
-msgstr ""
-"Panduan ini menjelaskan cara menggunakan plugin Tap-as-a-service (TaaS) "
-"Neutron dan plugin TaaS Dashboard di masing-masing chart Neutron dan Horizon."
-
-msgid ""
-"This installation, by default will use Google DNS servers, 8.8.8.8 or "
-"8.8.4.4 and updates resolv.conf. These DNS nameserver entries can be changed "
-"by updating file ``/opt/openstack-helm-infra/tools/images/kubeadm-aio/assets/"
-"opt/playbooks/vars.yaml`` under section ``external_dns_nameservers``. This "
-"change must be done on each node in your cluster."
-msgstr ""
-"Instalasi ini, secara default akan menggunakan server DNS Google, 8.8.8.8 "
-"atau 8.8.4.4 dan memperbarui resolv.conf. Entri server nama DNS ini dapat "
-"diubah dengan memperbarui file ``/opt/openstack-helm-infra/tools/images/"
-"kubeadm-aio/assets/opt/playbooks/vars.yaml`` di bawah bagian "
-"``external_dns_nameservers``. Perubahan ini harus dilakukan pada setiap node "
-"di kluster Anda."
-
-msgid "This is a two step process, i.e."
-msgstr "Ini adalah proses dua langkah, misal"
-
-msgid ""
-"This script will create two loopback devices for Ceph as one disk for OSD "
-"data and other disk for block DB and block WAL. If default devices (loop0 "
-"and loop1) are busy in your case, feel free to change them by exporting "
-"environment variables(CEPH_OSD_DATA_DEVICE and CEPH_OSD_DB_WAL_DEVICE)."
-msgstr ""
-"Script ini akan membuat dua perangkat loopback untuk Ceph sebagai satu disk "
-"untuk data OSD dan disk lain untuk memblokir DB dan memblokir WAL. Jika "
-"perangkat default (loop0 dan loop1) sibuk dalam kasus Anda, jangan ragu "
-"untuk mengubahnya dengan mengekspor variabel lingkungan "
-"(CEPH_OSD_DATA_DEVICE dan CEPH_OSD_DB_WAL_DEVICE)."
-
-msgid ""
-"This will delete all Kubernetes resources generated when the chart was "
-"instantiated. However for OpenStack charts, by default, this will not delete "
-"the database and database users that were created when the chart was "
-"installed. All OpenStack projects can be configured such that upon deletion, "
-"their database will also be removed. To delete the database when the chart "
-"is deleted the database drop job must be enabled before installing the "
-"chart. There are two ways to enable the job, set the job_db_drop value to "
-"true in the chart's ``values.yaml`` file, or override the value using the "
-"helm install command as follows:"
-msgstr ""
-"Ini akan menghapus semua sumber daya Kubernetes yang dihasilkan saat chart "
-"dibuat. Namun untuk chart OpenStack, secara default, ini tidak akan "
-"menghapus database dan pengguna database yang dibuat ketika chart dipasang. "
-"Semua proyek OpenStack dapat dikonfigurasi sedemikian rupa sehingga pada "
-"saat penghapusan, database mereka juga akan dihapus. Untuk menghapus "
-"database ketika chart dihapus, pekerjaan drop database harus diaktifkan "
-"sebelum menginstal chart. Ada dua cara untuk mengaktifkan pekerjaan, "
-"mengatur nilai job_db_drop menjadi true dalam file ``values.yaml`` pada "
-"chart, atau mengganti nilai menggunakan perintah penginstalan helm seperti "
-"berikut:"
-
-msgid ""
-"Throughout this guide the assumption is that the user is: ``ubuntu``. "
-"Because this user has to execute root level commands remotely to other "
-"nodes, it is advised to add the following lines to ``/etc/sudoers`` for each "
-"node:"
-msgstr ""
-"Sepanjang panduan ini, asumsinya adalah bahwa pengguna adalah: ``ubuntu``. "
-"Karena pengguna ini harus mengeksekusi perintah level root dari jarak jauh "
-"ke node lain, disarankan untuk menambahkan baris berikut ke ``/etc/sudoers`` "
-"untuk setiap node:"
-
-msgid ""
-"To allocate hugepages to NUMA sockets in OVS, ensure that the "
-"``socket_memory`` attribute in values.yaml specifies a value for the "
-"corresponding NUMA socket. In the following example, OVS will use one 1G "
-"hugepage for NUMA socket 0 and socket 1."
-msgstr ""
-"Untuk mengalokasikan hugepage ke soket NUMA di OVS, pastikan bahwa atribut "
-"``socket_memory`` dalam values.yaml menentukan nilai untuk soket NUMA yang "
-"sesuai. Dalam contoh berikut, OVS akan menggunakan satu hugepage 1G untuk "
-"NUMA socket 0 dan socket 1."
-
-msgid ""
-"To continue to deploy OpenStack on Kubernetes via OSH, see :doc:`Deploy "
-"NFS<./deploy-with-nfs>` or :doc:`Deploy Ceph<./deploy-with-ceph>`."
-msgstr ""
-"Untuk terus menggunakan OpenStack di Kubernetes melalui OSH, lihat :doc:"
-"`Deploy NFS<./deploy-with-nfs>` or :doc:`Deploy Ceph<./deploy-with-ceph>`."
-
-msgid ""
-"To copy the ssh key to each node, this can be accomplished with the ``ssh-"
-"copy-id`` command, for example: *ssh-copy-id ubuntu@192.168.122.178*"
-msgstr ""
-"Untuk menyalin kunci ssh ke setiap node, ini dapat diselesaikan dengan "
-"perintah ``ssh-copy-id``, misalnya: *ssh-copy-id ubuntu@192.168.122.178*"
-
-msgid "To delete an installed helm chart, use the following command:"
-msgstr "Untuk menghapus  helm chart yang terpasang, gunakan perintah berikut:"
-
-msgid "To generate the key you can use ``ssh-keygen -t rsa``"
-msgstr "Untuk menghasilkan kunci yang dapat Anda gunakan ``ssh-keygen -t rsa``"
-
-msgid ""
-"To run further commands from the CLI manually, execute the following to set "
-"up authentication credentials::"
-msgstr ""
-"Untuk menjalankan perintah lebih lanjut dari CLI secara manual, jalankan "
-"perintah berikut untuk menyiapkan kredensial otentikasi ::"
-
-msgid ""
-"To tear-down, the development environment charts should be removed first "
-"from the 'openstack' namespace and then the 'ceph' namespace using the "
-"commands from the `Removing Helm Charts` section. Additionally charts should "
-"be removed from the 'nfs' and 'libvirt' namespaces if deploying with NFS "
-"backing or bare metal development support. You can run the following "
-"commands to loop through and delete the charts, then stop the kubelet "
-"systemd unit and remove all the containers before removing the directories "
-"used on the host by pods."
-msgstr ""
-"Untuk meruntuhkan (tear-down), chart lingkungan pengembangan harus dihapus "
-"pertama dari namespace 'openstack' dan kemudian namespace 'ceph' menggunakan "
-"perintah dari bagian `Removing Helm Charts`. Selain itu, chart harus dihapus "
-"dari namespace 'nfs' dan 'libvirt' jika digunakan dengan dukungan dukungan "
-"NFS atau bare metal. Anda dapat menjalankan perintah berikut untuk mengulang "
-"dan menghapus chart, kemudian menghentikan unit kubelet systemd dan "
-"menghapus semua kontainer sebelum menghapus direktori yang digunakan pada "
-"host oleh pod."
-
-msgid "Troubleshooting"
-msgstr "Penyelesaian masalah"
-
-msgid ""
-"Tungsten Fabric is the multicloud and multistack network solution which you "
-"can use for your OpenStack as a network plugin. This document decribes how "
-"you can deploy a single node Open Stack based on Tungsten Fabric using "
-"openstack helm for development purpose."
-msgstr ""
-"Tungsten Fabric adalah solusi jaringan multicloud dan multistack yang dapat "
-"Anda gunakan untuk OpenStack Anda sebagai plugin jaringan. Dokumen ini "
-"menjelaskan bagaimana Anda bisa menggunakan Open Stack node tunggal "
-"berdasarkan Tungsten Fabric menggunakan OpenStack helm untuk tujuan "
-"pengembangan."
-
-msgid ""
-"Two similar options exist to set the FQDN overrides for External DNS mapping."
-msgstr ""
-"Dua opsi serupa ada untuk mengatur FQDN menimpa untuk pemetaan DNS Eksternal."
-
-msgid ""
-"Until the Ubuntu kernel shipped with 16.04 supports CephFS subvolume mounts "
-"by default the `HWE Kernel <../troubleshooting/ubuntu-hwe-kernel.html>`__ is "
-"required to use CephFS."
-msgstr ""
-"Sampai kernel Ubuntu yang dikirim dengan 16.04 mendukung CephFS subvolume "
-"mount secara default `HWE Kernel <../troubleshooting/ubuntu-hwe-kernel."
-"html>`__ diperlukan untuk menggunakan CephFS."
-
-msgid ""
-"Update your lab/environment DNS server with your appropriate host values "
-"creating A Records for the edge node IP's and various FQDN's. Alternatively "
-"you can test these settings locally by editing your ``/etc/hosts``. Below is "
-"an example with a dummy domain ``os.foo.org`` and dummy Ingress IP "
-"``1.2.3.4``."
-msgstr ""
-"Perbarui server DNS lab/environment Anda dengan nilai host yang sesuai Anda "
-"membuat A Records untuk node edge IP dan berbagai FQDN. Atau Anda dapat "
-"menguji pengaturan ini secara lokal dengan mengedit ``/etc/hosts`` Anda. Di "
-"bawah ini adalah contoh dengan dummy domain ``os.foo.org`` dan dummy Ingress "
-"IP ``1.2.3.4``."
-
-msgid ""
-"Use above gerrit commits to prepare the LOCI images using following script:"
-msgstr ""
-"Gunakan komit gerrit di atas untuk menyiapkan image LOCI menggunakan skrip "
-"berikut:"
-
-msgid ""
-"Use it as ``docker build --build-arg PROJECT_REF=${REQUIREMENTS_REF_SPEC}`` "
-"command argument to build the requirements LOCI image."
-msgstr ""
-"Gunakan sebagai argumen perintah  ``docker build --build-arg PROJECT_REF="
-"${REQUIREMENTS_REF_SPEC}`` untuk membangun image LOCI persyaratan."
-
-msgid "Using Horizon as an example, find the ``endpoints`` config."
-msgstr ""
-"Dengan menggunakan Horizon sebagai contoh, cari konfigurasi ``endpoints``."
-
-msgid ""
-"Using the Helm packages previously pushed to the local Helm repository, run "
-"the following commands to instruct tiller to create an instance of the given "
-"chart. During installation, the helm client will print useful information "
-"about resources created, the state of the Helm releases, and whether any "
-"additional configuration steps are necessary."
-msgstr ""
-"Dengan menggunakan paket Helm yang sebelumnya didorong ke repositori Helm "
-"setempat, jalankan perintah berikut untuk menginstruksikan tiller untuk "
-"membuat instance dari chart yang diberikan. Selama instalasi, klien helm "
-"akan mencetak informasi yang berguna tentang sumber daya yang dibuat, "
-"keadaan rilis Helm, dan berbagai langkah konfigurasi tambahan diperlukan."
-
-msgid "Verify the *v1beta1/Ingress* resource has a Host with your FQDN value"
-msgstr ""
-"Verifikasi sumber daya *v1beta1/Ingress* memiliki Host dengan nilai FQDN Anda"
-
-msgid ""
-"We are going to install Ceph OSDs backed by loopback devices as this will "
-"help us not to attach extra disks, in case if you have enough disks on the "
-"node then feel free to skip creating loopback devices by exporting "
-"CREATE_LOOPBACK_DEVICES_FOR_CEPH to false and export the  block devices "
-"names as environment variables(CEPH_OSD_DATA_DEVICE and "
-"CEPH_OSD_DB_WAL_DEVICE)."
-msgstr ""
-"Kami akan menginstal OSD Ceph yang didukung oleh perangkat loopback karena "
-"ini akan membantu kami untuk tidak memasang disk tambahan, jika Anda "
-"memiliki cukup disk pada node, silakan lewati pembuatan perangkat loopback "
-"dengan mengekspor CREATE_LOOPBACK_DEVICES_FOR_CEPH ke false dan mengekspor "
-"perangkat blok nama sebagai variabel lingkungan (CEPH_OSD_DATA_DEVICE dan "
-"CEPH_OSD_DB_WAL_DEVICE)."
-
-msgid ""
-"We want to change the **public** configurations to match our DNS layouts "
-"above. In each Chart ``values.yaml`` is a ``endpoints`` configuration that "
-"has ``host_fqdn_override``'s for each API that the Chart either produces or "
-"is dependent on. `Read more about how Endpoints are developed <https://docs."
-"openstack.org/openstack-helm/latest/devref/endpoints.html>`__. Note while "
-"Glance Registry is listening on a Ingress http endpoint, you will not need "
-"to expose the registry for external services."
-msgstr ""
-"Kami ingin mengubah konfigurasi ***public*** agar sesuai dengan tata letak "
-"DNS kami di atas. Di setiap Chart ``values.yaml`` adalah konfigurasi "
-"``endpoints`` yang memiliki ``host_fqdn_override`` untuk setiap API yang "
-"dihasilkan oleh Chart atau tergantung pada. `Read more about how Endpoints "
-"are developed <https://docs.openstack.org/openstack-helm/latest/devref/"
-"endpoints.html>`__. Catatan sementara Glance Registry sedang mendengarkan "
-"pada endpoint http Ingress, Anda tidak perlu mengekspos registri untuk "
-"layanan eksternal."
-
-msgid ""
-"While deploying neutron-server and L2 agents, TaaS should be enabled in "
-"``conf: neutron`` section to add TaaS as a service plugin; in ``conf: "
-"plugins`` section to add TaaS as a L2 agent extension; in ``conf: "
-"taas_plugin`` section to configure the ``service_provider`` endpoint used by "
-"Neutron TaaS plugin:"
-msgstr ""
-"Saat menggunakan neutron-server dan agen L2, TaaS harus diaktifkan di bagian "
-"``conf: neutron`` untuk menambahkan TaaS sebagai plugin layanan; di bagian "
-"`` conf: plugins`` untuk menambahkan TaaS sebagai ekstensi agen L2; di "
-"bagian  ``conf: taas_plugin`` untuk mengkonfigurasi endpoint "
-"``service_provider`` yang digunakan oleh plugin Neutron TaaS:"
-
-msgid ""
-"You can use any Kubernetes deployment tool to bring up a working Kubernetes "
-"cluster for use with OpenStack-Helm. For production deployments, please "
-"choose (and tune appropriately) a highly-resilient Kubernetes distribution, "
-"e.g.:"
-msgstr ""
-"Anda dapat menggunakan alat penyebaran Kubernetes untuk memunculkan kluster "
-"Kubernetes yang berfungsi untuk digunakan dengan OpenStack-Helm. Untuk "
-"penyebaran produksi, pilih (dan selaraskan dengan tepat) distribusi "
-"Kubernetes yang sangat tangguh (highly-resilient), misalnya:"
-
-msgid ""
-"You can use any Kubernetes deployment tool to bring up a working Kubernetes "
-"cluster for use with OpenStack-Helm. This guide describes how to simply "
-"stand up a multinode Kubernetes cluster via the OpenStack-Helm gate scripts, "
-"which use KubeADM and Ansible. Although this cluster won't be production-"
-"grade, it will serve as a quick starting point in a lab or proof-of-concept "
-"environment."
-msgstr ""
-"Anda dapat menggunakan alat penyebaran Kubernetes untuk memunculkan klaster "
-"Kubernetes yang berfungsi untuk digunakan dengan OpenStack-Helm. Panduan ini "
-"menjelaskan cara untuk hanya berdiri multinode Kubernetes klaster melalui "
-"skrip gate OpenStack-Helm, yang menggunakan KubeADM dan Ansible. Meskipun "
-"klaster ini tidak akan menjadi kelas produksi (production-grade), ini akan "
-"berfungsi sebagai titik awal yang cepat di laboratorium atau lingkungan "
-"proof-of-concept."
-
-msgid ""
-"You may now deploy kubernetes, and helm onto your machine, first move into "
-"the ``openstack-helm`` directory and then run the following:"
-msgstr ""
-"Anda sekarang dapat menyebarkan kubernetes, dan helm ke komputer Anda, "
-"pertama-tama masuk ke direktori ``openstack-helm`` dan kemudian jalankan "
-"yang berikut:"
-
-msgid ""
-"Your changes to `/etc/environment` will not be applied until you source them:"
-msgstr ""
-"Perubahan Anda ke  `/etc/environment` tidak akan diterapkan sampai Anda "
-"sumbernya:"
-
-msgid ""
-"`Airship <https://airshipit.org/>`_, a declarative open cloud infrastructure "
-"platform"
-msgstr ""
-"`Airship <https://airshipit.org/>`_, platform infrastruktur cloud terbuka "
-"deklaratif"
-
-msgid ""
-"`KubeADM <https://kubernetes.io/docs/setup/independent/high-availability/"
-">`_, the foundation of a number of Kubernetes installation solutions"
-msgstr ""
-"`KubeADM <https://kubernetes.io/docs/setup/independent/high-availability/"
-">`_, fondasi sejumlah solusi instalasi Kubernetes"
-
-msgid "https://review.openstack.org/#/c/597200/"
-msgstr "https://review.openstack.org/#/c/597200/"
-
-msgid "https://review.openstack.org/#/c/607392/"
-msgstr "https://review.openstack.org/#/c/607392/"
-
-msgid "https://review.openstack.org/#/c/621606/"
-msgstr "https://review.openstack.org/#/c/621606/"
-
-msgid "hugepages have been allocated on NUMA socket 1 by OVS, and"
-msgstr "hugepage telah dialokasikan pada NUMA socket 1 oleh OVS, dan"
-
-msgid ""
-"if you are rerunning the below script then make sure to skip the loopback "
-"device creation by exporting CREATE_LOOPBACK_DEVICES_FOR_CEPH to false."
-msgstr ""
-"jika Anda menjalankan ulang skrip di bawah ini, pastikan untuk melewati "
-"pembuatan perangkat loopback dengan mengekspor "
-"CREATE_LOOPBACK_DEVICES_FOR_CEPH ke false."
-
-msgid ""
-"node_one, node_two and node_three below are all worker nodes, children of "
-"the master node that the commands below are executed on."
-msgstr ""
-"node_one, node_two dan node_three di bawah ini adalah semua node pekerja "
-"(worker node), anak-anak (children) dari node master dimana perintah di "
-"bawah ini dieksekusi."
diff --git a/doc/source/locale/id/LC_MESSAGES/doc-specs.po b/doc/source/locale/id/LC_MESSAGES/doc-specs.po
deleted file mode 100644
index 16a599b8c1..0000000000
--- a/doc/source/locale/id/LC_MESSAGES/doc-specs.po
+++ /dev/null
@@ -1,2861 +0,0 @@
-# suhartono <cloudsuhartono@gmail.com>, 2019. #zanata
-msgid ""
-msgstr ""
-"Project-Id-Version: openstack-helm 0.1.1.dev3685\n"
-"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2022-04-06 21:47+0000\n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-"PO-Revision-Date: 2019-05-27 04:14+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 "**Charts in the appropriate project**"
-msgstr "**Charts in the appropriate project**"
-
-msgid "**Combined helm-toolkit**"
-msgstr "**Combined helm-toolkit**"
-
-msgid "**Document Kubernetes requirements**"
-msgstr "**Document Kubernetes requirements**"
-
-msgid "**Document version requirements**"
-msgstr "**Document version requirements**"
-
-msgid "**Helm test for all charts**"
-msgstr "**Helm test for all charts**"
-
-msgid "**Inclusion of all core services**"
-msgstr "**Inclusion of all core services**"
-
-msgid "**LMA Operations Guide**"
-msgstr "**LMA Operations Guide**"
-
-msgid "**OpenStack-Helm release process**"
-msgstr "**OpenStack-Helm release process**"
-
-msgid "**Release notes**"
-msgstr "**Release notes**"
-
-msgid "**Resiliency across reboots**"
-msgstr "**Resiliency across reboots**"
-
-msgid "**Split Ceph chart**"
-msgstr "**Split Ceph chart**"
-
-msgid "**Standardization of manifests**"
-msgstr "**Standardization of manifests**"
-
-msgid "**Standardization of values**"
-msgstr "**Standardization of values**"
-
-msgid "**Upgrades**"
-msgstr "**Upgrades**"
-
-msgid "**Values-driven config files**"
-msgstr "**Values-driven config files**"
-
-msgid "1) Prepare scripts:"
-msgstr "1) Siapkan skrip:"
-
-msgid ""
-"1. For each chart, add a new entry ``oci_image_registry:`` under ``endpoints:"
-"`` in ``values.yaml``. The entry ``oci_image_registry:`` has the ``auth:`` "
-"section which provides the credentials for accessing registry images and an "
-"option ``enabled:`` to determine whether images authentication is required "
-"or not. The registry basic information would also be included for generating "
-"the registry URL by the endpoint lookup functions. Also add a new entry "
-"``oci_image_registry:`` under ``secrets:`` to indicate the secret name. In "
-"order to create the secret that holds the provided credentials, add a new "
-"component ``secret_registry`` in ``manifests:`` section. For example:"
-msgstr ""
-"1. Untuk setiap chart, tambahkan entri baru ``oci_image_registry:`` di bawah "
-"``endpoints:`` di ``values.yaml``. Entri  ``oci_image_registry:``  memiliki "
-"bagian ``auth:`` yang menyediakan kredensial untuk mengakses image registri "
-"dan opsi ``enabled:`` untuk menentukan apakah otentikasi image diperlukan "
-"atau tidak. Informasi dasar registri juga akan dimasukkan untuk menghasilkan "
-"URL registri oleh fungsi pencarian endpoint. Juga tambahkan entri baru "
-"``oci_image_registry:`` di bawah ``secrets:`` untuk menunjukkan nama "
-"rahasia. Untuk membuat rahasia yang memegang kredensial yang disediakan, "
-"tambahkan komponen baru ``secret_registry`` di bagian ``manifes:``. Sebagai "
-"contoh:"
-
-msgid "2 Replace occurrence of ``ceph.yaml`` with ``tenant-ceph.yaml``"
-msgstr "2 Ganti kemunculan ``ceph.yaml`` dengan ``tenant-ceph.yaml``"
-
-msgid "2) Deploy ingress chart:"
-msgstr "2) Menyebarkan ingress chart:"
-
-msgid ""
-"3 For tenant Ceph, no need to deploy ceph-provisioners. Update script to "
-"``for CHART in ceph-mon ceph-osd ceph-client; do``"
-msgstr ""
-"3 untuk tenant Ceph, tidak perlu menggunakan ceph-provisioners. Update skrip "
-"ke ``for CHART in ceph-mon ceph-osd ceph-client; do``"
-
-msgid "3) Deploy Ceph for RBD:"
-msgstr "3) Menyebarkan Ceph untuk RBD:"
-
-msgid "4) Deploy MariaDB, RabbitMQ, Memcached and Keystone:"
-msgstr "4) Menyebarkan MariaDB, RabbitMQ, Memcached dan Keystone:"
-
-msgid "5) Deploy Ceph for Tenant:"
-msgstr "5) Menyebarkan Ceph untuk Tenant:"
-
-msgid "6 VM based hosts (node1, node2, node3, node4, node5, node6)"
-msgstr "6 VM based hosts (node1, node2, node3, node4, node5, node6)"
-
-msgid "6) Enable Openstack namespace to use Tenant Ceph:"
-msgstr "6) Aktifkan Openstack namespace untuk menggunakan Tenant Ceph:"
-
-msgid "7) Tenant Ceph: Deploy Rados Gateway:"
-msgstr "7) Tenant Ceph: Deploy Rados Gateway:"
-
-msgid "8) Deploy Glance:"
-msgstr "8) Menyebarkan Glance:"
-
-msgid "9) Deploy Cinder:"
-msgstr "9) Menyebarkan Cinder:"
-
-msgid ""
-"A basic Logging, Monitoring, and Alerting-oriented operations guide must be "
-"in place, illustrating for operators (and developers) how to set up and use "
-"an example LMA setup for OpenStack and supporting services.  It will include "
-"instructions on how to perform basic configuration and how to access and use "
-"the user interfaces at a high level.  It will also link out to more detailed "
-"documentation for the LMA tooling itself."
-msgstr ""
-"Panduan operasi Logging, Monitoring, dan Alerting-oriented dasar harus ada, "
-"menggambarkan bagi operator (dan pengembang) bagaimana mengatur dan "
-"menggunakan contoh pengaturan LMA untuk OpenStack dan layanan pendukung. Ini "
-"akan mencakup instruksi tentang cara melakukan konfigurasi dasar dan cara "
-"mengakses dan menggunakan antarmuka pengguna di tingkat tinggi. Ini juga "
-"akan menghubungkan ke dokumentasi yang lebih rinci untuk perkakas LMA itu "
-"sendiri."
-
-msgid ""
-"A few areas have been identified on changes required. Each of them will be a "
-"work item."
-msgstr ""
-"Beberapa area telah diidentifikasi pada perubahan yang diperlukan. Masing-"
-"masing akan menjadi work item."
-
-msgid ""
-"A foundational requirement of 1.0 readiness is the presence of robust gating "
-"that will ensure functionality, backward compatibility, and upgradeability. "
-"This will allow development to continue and for support for new versions of "
-"OpenStack to be added post-1.0. The following gating requirements must be "
-"met:"
-msgstr ""
-"Persyaratan mendasar dari kesiapan 1.0 adalah keberadaan gating yang kuat "
-"yang akan memastikan fungsionalitas, kompatibilitas mundur (backward "
-"compatibility), dan peningkatan kemampuan. Ini akan memungkinkan "
-"pengembangan untuk melanjutkan dan untuk dukungan untuk versi baru OpenStack "
-"ditambahkan post-1.0. Persyaratan gating berikut harus dipenuhi:"
-
-msgid ""
-"A gate will be added to OpenStack-Helm that runs through the developer "
-"environment deployment process."
-msgstr ""
-"Gate akan ditambahkan ke OpenStack-Helm yang dijalankan melalui proses "
-"penyebaran lingkungan pengembang."
-
-msgid ""
-"A number of in-progress and planned development efforts must be completed "
-"prior to 1.0, to ensure a stable OpenStack-Helm interface thereafter."
-msgstr ""
-"Sejumlah upaya pengembangan yang sedang berlangsung dan yang direncanakan "
-"harus diselesaikan sebelum 1.0, untuk memastikan antarmuka OpenStack-Helm "
-"yang stabil sesudahnya."
-
-msgid ""
-"A set of scripts will be provided to exercise the deployed environment that "
-"checks the basic functionality of the deployed cloud, driven where possible "
-"via OpenStack heat:"
-msgstr ""
-"Seperangkat skrip akan disediakan untuk menjalankan lingkungan yang "
-"digunakan yang memeriksa fungsi dasar cloud yang digunakan, didorong jika "
-"memungkinkan melalui OpenStack heat:"
-
-msgid ""
-"A specification should precede any broad-reaching technical changes or "
-"proposals to OpenStack-Helm.  Examples of changes requiring a specification "
-"include:  a standard format to the values.yaml files, multiple backend "
-"support for neutron, and the approach for logging and monitoring in "
-"OpenStack-Helm.  Some additional features will not need an accompanying "
-"specification, but may be tied back to an existing specification.  An "
-"example of this would be introducing a service in OpenStack-Helm that could "
-"be included under the scope of a specification already drafted and approved."
-msgstr ""
-"Spesifikasi harus mendahului setiap perubahan teknis yang luas atau proposal "
-"ke OpenStack-Helm. Contoh perubahan yang memerlukan spesifikasi meliputi: "
-"format standar untuk file values.yaml, dukungan backend berganda untuk "
-"neutron, dan pendekatan untuk logging dan pemantauan di OpenStack-Helm. "
-"Beberapa fitur tambahan tidak memerlukan spesifikasi yang menyertainya, "
-"tetapi mungkin terikat kembali ke spesifikasi yang ada. Contohnya adalah "
-"memperkenalkan layanan di OpenStack-Helm yang dapat dimasukkan dalam lingkup "
-"spesifikasi yang telah disusun dan disetujui."
-
-msgid "API Deployments"
-msgstr "API Deployments"
-
-msgid "Ability to apply custom metadata and uniform format to logs"
-msgstr ""
-"Kemampuan untuk menerapkan metadata kustom dan format seragam untuk log"
-
-msgid "Ability to perform custom queries against metrics collected"
-msgstr ""
-"Kemampuan untuk melakukan kueri kustom terhadap metrik yang dikumpulkan"
-
-msgid "Ability to perform custom queries against stored logs"
-msgstr "Kemampuan untuk melakukan kueri kustom terhadap log yang tersimpan"
-
-msgid ""
-"Above output shows ``http://ceph-rgw.openstack.svc.cluster.local`` which "
-"shows that swift is pointing to tenant-ceph."
-msgstr ""
-"Output di atas menunjukkan ``http://ceph-rgw.openstack.svc.cluster.local`` "
-"yang menunjukkan bahwa swift menunjuk ke tenant-ceph."
-
-msgid ""
-"Above output shows that tenant ceph now has 19 pools including one for "
-"Cinder."
-msgstr ""
-"Output di atas menunjukkan bahwa tenant ceph sekarang memiliki 19 pool "
-"termasuk satu untuk Cinder."
-
-msgid "Add Linux Bridge as first alternative for OVS - separate spec needed."
-msgstr ""
-"Tambahkan Linux Bridge sebagai alternatif pertama untuk OVS - spesifikasi "
-"terpisah diperlukan."
-
-msgid "Add LinuxBridge daemonset"
-msgstr "Tambahkan daemonset LinuxBridge"
-
-msgid ""
-"Add a helm-toolkit function ``helm-toolkit.manifests.secret_registry`` to "
-"create a manifest for secret generation. For example:"
-msgstr ""
-"Tambahkan fungsi helm-toolkit ``helm-toolkit.manifests.secret_registry`` "
-"untuk membuat manifes untuk pembuatan rahasia. Sebagai contoh:"
-
-msgid ""
-"Add a template highlighting the updated values ordering for use in chart "
-"development"
-msgstr ""
-"Tambahkan template highlighting urutan nilai yang diperbarui untuk digunakan "
-"dalam pengembangan chart"
-
-msgid "Add documentation on how to use LinuxBridge"
-msgstr "Tambahkan dokumentasi tentang cara menggunakan LinuxBridge"
-
-msgid "Add gate for developer environment"
-msgstr "Tambahkan gate untuk lingkungan pengembang"
-
-msgid "Add gate job testing VM network connectivity"
-msgstr "Tambahkan gate job testing konektivitas jaringan VM"
-
-msgid ""
-"Add one SDN to see if proposed change is working OK - separate spec needed."
-msgstr ""
-"Tambahkan satu SDN untuk melihat apakah perubahan yang diajukan berfungsi "
-"dengan baik - pisahkan spesifikasi yang diperlukan."
-
-msgid "Add or remove nodes depending on utilization"
-msgstr "Tambah atau hapus node tergantung pada pemanfaatan"
-
-msgid "Additional assignees TBD"
-msgstr "Additional assignees TBD"
-
-msgid ""
-"Aggregator also send aggregated logs to Kafka for external tools to consume"
-msgstr ""
-"Aggregator juga mengirim log agregat ke Kafka untuk dikonsumsi oleh alat "
-"eksternal"
-
-msgid "Alerting capabilities to notify operators when thresholds exceeded"
-msgstr ""
-"Memperingatkan kemampuan untuk memberi tahu operator ketika ambang melebihi"
-
-msgid "Alertmanager chart"
-msgstr "Alertmanager chart"
-
-msgid ""
-"All charts must include sensible configuration values to make the monitoring "
-"platform usable by default.  These include:  static Prometheus "
-"configurations for the included exporters, static dashboards for Grafana "
-"mounted via configMaps and configurations for Alertmanager out of the box."
-msgstr ""
-"Semua chart harus menyertakan nilai konfigurasi yang masuk akal untuk "
-"membuat platform pemantauan dapat digunakan secara default. Ini termasuk: "
-"konfigurasi statis Prometheus untuk eksportir yang disertakan, dasbor statis "
-"untuk Grafana yang dipasang melalui configMaps dan konfigurasi untuk "
-"Alertmanager di luar kotak."
-
-msgid ""
-"All charts require valid and sensible default values to provide operational "
-"value out of the box."
-msgstr ""
-"Semua chart memerlukan nilai default yang valid dan masuk akal untuk "
-"memberikan nilai operasional di luar kotak."
-
-msgid ""
-"All charts should follow design approaches applied to all other OpenStack-"
-"Helm charts, including the use of helm-toolkit."
-msgstr ""
-"Semua chart harus mengikuti pendekatan desain yang diterapkan pada semua "
-"chart OpenStack-Helm lainnya, termasuk penggunaan helm-toolkit."
-
-msgid "All charts should migrate to their appropriate home project as follows:"
-msgstr ""
-"Semua chart harus bermigrasi ke home project yang sesuai sebagai berikut:"
-
-msgid ""
-"All keys under top-level keys are listed in alphabetical order, with the "
-"exception of the conf key.  As some configuration files require a strict "
-"ordering of their content, excluding this key from any alphabetical "
-"organization is required."
-msgstr ""
-"Semua kunci di bawah top-level keys terdaftar dalam urutan abjad, dengan "
-"pengecualian kunci conf. Karena beberapa file konfigurasi memerlukan urutan "
-"konten yang ketat, tidak termasuk kunci ini dari organisasi alfabet apa pun "
-"diperlukan."
-
-msgid "All services in OpenStack-Helm log to stdout and stderr by default"
-msgstr ""
-"Semua layanan di OpenStack-Helm log ke stdout dan stderr secara default"
-
-msgid ""
-"All services running within the platform should be subject to the security "
-"practices applied to the other OpenStack-Helm charts."
-msgstr ""
-"Semua layanan yang berjalan dalam platform harus tunduk pada praktik "
-"keamanan yang diterapkan pada grafik OpenStack-Helm lainnya."
-
-msgid ""
-"All services should survive node reboots, and their functionality validated "
-"following a reboot by a gate."
-msgstr ""
-"Semua layanan harus selamat dari reboot node, dan fungsinya divalidasi "
-"setelah reboot oleh gate."
-
-msgid ""
-"All three charts must include sensible configuration values to make the "
-"logging platform usable by default.  These include: proper input "
-"configurations for Fluentd, proper metadata and formats applied to the logs "
-"via Fluentd, sensible indexes created for Elasticsearch, and proper "
-"configuration values for Kibana to query the Elasticsearch indexes "
-"previously created."
-msgstr ""
-"Ketiga grafik harus menyertakan nilai konfigurasi yang masuk akal untuk "
-"membuat platform logging dapat digunakan secara default. Ini termasuk: "
-"konfigurasi input yang tepat untuk Fluentd, metadata yang tepat dan format "
-"yang diterapkan pada log melalui Fluentd, indeks yang masuk akal yang dibuat "
-"untuk Elasticsearch, dan nilai konfigurasi yang tepat untuk Kibana untuk "
-"menanyakan indeks Elasticsearch yang sebelumnya dibuat."
-
-msgid "Allow the usage of multiple base images in OSH."
-msgstr "Izinkan penggunaan beberapa image dasar dalam OSH."
-
-msgid ""
-"Allows different profiles of apache, should some charts require different "
-"args for example for the same kind of images, by using yaml dict merges "
-"features."
-msgstr ""
-"Mengizinkan profil apache yang berbeda, jika beberapa bagan memerlukan "
-"argumen yang berbeda misalnya untuk jenis image yang sama, dengan "
-"menggunakan fitur penggabungan dict yaml."
-
-msgid ""
-"Alter webserver configuration per distro. Different distros have different "
-"expectations in terms of path (including a different series of files "
-"required), and it would make the operators' life easier by using their "
-"expected distro paths."
-msgstr ""
-"Ubah konfigurasi server web per distro. Distro yang berbeda memiliki harapan "
-"yang berbeda dalam hal path (termasuk serangkaian file yang berbeda "
-"diperlukan), dan itu akan membuat hidup para operator lebih mudah dengan "
-"menggunakan path distro yang mereka harapkan."
-
-msgid "Alternatives"
-msgstr "Alternatif"
-
-msgid ""
-"Alternatives to decomposable Neutron chart would be to copy whole Neutron "
-"chart and create spin-offs with new SDN enabled. This approach has drawbacks "
-"of maintaining the whole neutron chart in many places, and copies of "
-"standard services may be out of sync with OSH improvements. This implies "
-"constant maintenance effort to up to date."
-msgstr ""
-"Alternatif untuk chart Neutron terurai (decomposable) adalah menyalin "
-"seluruh chart Neutron dan membuat spin-off dengan SDN baru diaktifkan. "
-"Pendekatan ini memiliki kelemahan dalam mempertahankan bagan neutron "
-"keseluruhan di banyak tempat, dan salinan layanan standar mungkin tidak "
-"selaras dengan perbaikan OSH. Ini menyiratkan upaya pemeliharaan yang "
-"konstan hingga terbaru."
-
-msgid "Angie Wang (angiewang)"
-msgstr "Angie Wang (angiewang)"
-
-msgid ""
-"Another place where Neutron L2 agent should be pointed is dependencies list "
-"in other OpenStack projects. Currently, :code:`nova-compute` has dependency "
-"for :code:`ovs-agent` in :code:`nova/values.yaml`, it should be changed to:"
-msgstr ""
-"Tempat lain di mana agen L2 Neutron harus ditunjuk adalah daftar dependensi "
-"dalam proyek OpenStack lainnya. Saat ini, :code:`nova-compute` memiliki "
-"ketergantungan untuk :code:`ovs-agent`  dalam :code:`nova/values.yaml`, "
-"harus diubah menjadi:"
-
-msgid "Any other changes to the external interface of OpenStack-Helm"
-msgstr "Perubahan lain apa pun pada antarmuka eksternal OpenStack-Helm"
-
-msgid ""
-"As mentioned before, configuration of L3/DHCP/metadata agent should be "
-"adjusted to use LinuxBridge, sample configuration override:"
-msgstr ""
-"Seperti disebutkan sebelumnya, konfigurasi agen L3/DHCP/metadata harus "
-"disesuaikan untuk menggunakan LinuxBridge, konfigurasi sampel diganti:"
-
-msgid "Assign Floating IP to VM"
-msgstr "Tetapkan IP Mengambang (Floating IP) ke VM"
-
-msgid "Assignee(s)"
-msgstr "Assignee(s)"
-
-msgid ""
-"At this point, curated scripts will be used to deploy OpenStack-Helm "
-"services on demand as desired, with documentation provided to allow a new "
-"developer to quickly set up either a single or multimode deployment of a "
-"reference `OpenStack Compute Kit <https://governance.openstack.org/tc/"
-"reference/tags/starter-kit_compute.html>`_ environment with the addition of:"
-msgstr ""
-"Pada titik ini, skrip yang dikurasi (curated) akan digunakan untuk "
-"menggunakan layanan OpenStack-Helm sesuai permintaan seperti yang "
-"diinginkan, dengan dokumentasi yang disediakan untuk memungkinkan pengembang "
-"baru dengan cepat mengatur penyebaran tunggal atau multimode dari referensi  "
-"`OpenStack Compute Kit <https: // governance.openstack.org/tc/reference/tags/"
-"starter-kit_compute.html>`_ lingkungan dengan penambahan:"
-
-msgid ""
-"Authentication should be enabled for normal users to access Kube API server "
-"via either kubectl command or kube REST API call."
-msgstr ""
-"Otentikasi harus diaktifkan untuk pengguna normal untuk mengakses server API "
-"Kube melalui perintah kubectl atau panggilan API REST kube."
-
-msgid "Backed by highly available storage"
-msgstr "Didukung oleh penyimpanan yang sangat tersedia"
-
-msgid ""
-"Before drafting a specification, a blueprint should be filed in Storyboard_ "
-"along with any dependencies the blueprint requires.  Once the blueprint has "
-"been registered, submit the specification as a patch set to the specs/ "
-"directory using the supplied template."
-msgstr ""
-"Sebelum menyusun spesifikasi, blueprint harus diajukan di Storyboard_ "
-"bersama dengan setiap dependensi yang diperlukan blueprint. Setelah "
-"blueprint terdaftar, kirimkan spesifikasi sebagai patch yang disetel ke "
-"direktori spesifikasi menggunakan templat yang disediakan."
-
-msgid "Before using Openstack-Helm to deploy openstack services,"
-msgstr ""
-"Sebelum menggunakan Openstack-Helm untuk menggunakan layanan openstack,"
-
-msgid "Bin ConfigMaps"
-msgstr "Bin ConfigMaps"
-
-msgid ""
-"Blueprint: https://blueprints.launchpad.net/openstack-helm/+spec/nginx-"
-"sidecar"
-msgstr ""
-"Blueprint: https://blueprints.launchpad.net/openstack-helm/+spec/nginx-"
-"sidecar"
-
-msgid "Blueprint: neutron-multiple-sdns_"
-msgstr "Blueprint: neutron-multiple-sdns_"
-
-msgid "Blueprint: support-linux-bridge-on-neutron_"
-msgstr "Blueprint: support-linux-bridge-on-neutron_"
-
-msgid "Blueprint: support-oci-image-registry-with-authentication-turned-on_"
-msgstr "Blueprint: support-oci-image-registry-with-authentication-turned-on_"
-
-msgid "Blueprints: 1. osh-logging-framework_"
-msgstr "Cetak Biru: 1. osh-logging-framework_"
-
-msgid "Blueprints: 1. osh-monitoring_ 2. osh-logging-framework_"
-msgstr "Blueprints: 1. osh-monitoring_ 2. osh-logging-framework_"
-
-msgid ""
-"But above alternatives have limitations and security impact. i.e...require "
-"root access to configure on all nodes, all pods can read any configured "
-"private registries, all pods can use any images cached on a node [1]_"
-msgstr ""
-"Tetapi alternatif di atas memiliki keterbatasan dan dampak keamanan. i.e ... "
-"memerlukan akses root untuk mengkonfigurasi pada semua node, semua pod dapat "
-"membaca register pribadi yang dikonfigurasi, semua pod dapat menggunakan "
-"image apa pun yang di-cache pada sebuah node [1] _"
-
-msgid ""
-"By default, :code:`daemonset_lb_agent` will be set to false to remain "
-"default behaviour of installing OVS as networking agent."
-msgstr ""
-"Secara default, :code:`daemonset_lb_agent` akan disetel ke false untuk tetap "
-"menjadi perilaku default menginstal OVS sebagai agen jaringan."
-
-msgid "Ceph Clusters:"
-msgstr "Ceph Clusters:"
-
-msgid "Ceph backed Block Storage (cinder)"
-msgstr "Object Storage (cinder) yang didukung Ceph"
-
-msgid "Ceph backed Object Storage"
-msgstr "Object Storage yang didukung Ceph"
-
-msgid "Ceph for RBD:"
-msgstr "Ceph for RBD:"
-
-msgid "Ceph for Tenant:"
-msgstr "Ceph untuk Tenant:"
-
-msgid "Ceph metrics: total pool usage, latency, health, etc"
-msgstr "Metrik Ceph: total penggunaan pool, latensi, kesehatan, dll"
-
-msgid ""
-"Change ordering of keys across all charts in openstack-helm, openstack-helm-"
-"infra, and openstack-helm-addons"
-msgstr ""
-"Ubah urutan kunci di semua chart di openstack-helm, openstack-helm-infra, "
-"dan openstack-helm-addons"
-
-msgid ""
-"Charts for all core OpenStack services must be present to achieve 1.0 "
-"releasability.  The only core service outstanding at this time is Swift."
-msgstr ""
-"Chart untuk semua layanan OpenStack inti harus ada untuk mencapai 1.0 "
-"releasability. Satu-satunya layanan inti yang beredar saat ini adalah Swift."
-
-msgid ""
-"Charts for exporters: kube-state-metrics, ceph-exporter, openstack-exporter?"
-msgstr ""
-"Chart untuk eksportir: kube-state-metrics, ceph-exporter, openstack-exporter?"
-
-msgid "Code Completion and Refactoring"
-msgstr "Code Completion dan Refactoring"
-
-msgid "Collect logs from the node by Fluentbit"
-msgstr "Kumpulkan log dari node dengan Fluentbit"
-
-msgid "Common method to configure all monitoring targets"
-msgstr "Metode umum untuk mengonfigurasi semua target pemantauan"
-
-msgid ""
-"Comprehensive documentation is key to the ability for real-world operators "
-"to benefit from OpenStack-Helm, and so it is a requirement for 1.0 "
-"releasability. The following outstanding items must be completed from a "
-"documentation perspective:"
-msgstr ""
-"Dokumentasi yang komprehensif adalah kunci kemampuan operator real-world "
-"untuk mendapatkan manfaat dari OpenStack-Helm, dan karenanya merupakan "
-"persyaratan untuk 1.0 releasability. Barang luar biasa (outstanding) berikut "
-"harus diselesaikan dari perspektif dokumentasi:"
-
-msgid "Configurable log rotation mechanism"
-msgstr "Mekanisme rotasi log yang dapat dikonfigurasi"
-
-msgid "Configuration in :code:`neutron.conf` and :code:`ml2_conf.ini`"
-msgstr "Konfigurasi dalam :code:`neutron.conf` and :code:`ml2_conf.ini`"
-
-msgid ""
-"Cover the following logging use cases https://review.openstack.org/#/"
-"c/482687/"
-msgstr ""
-"Cover kasus penggunaan logging berikut https://review.openstack.org/#/"
-"c/482687/"
-
-msgid "Create SSH Key in nova"
-msgstr "Buat SSH Key di nova"
-
-msgid "Create VM on tenant network"
-msgstr "Buat VM di jaringan tenant"
-
-msgid ""
-"Create conditionals in the helm charts. This is problematic, as the amount "
-"of conditionals will increase and will be harder to maintain. Overrides "
-"files are easy to sync between charts."
-msgstr ""
-"Buat persyaratan di helm chart. Ini bermasalah, karena jumlah persyaratan "
-"akan meningkat dan akan lebih sulit untuk dipertahankan. File yang di-"
-"overrided mudah disinkronkan di antara chart."
-
-msgid "Create external network"
-msgstr "Buat jaringan eksternal"
-
-msgid "Create tenant network"
-msgstr " Buat jaringan penyewa (tenant)"
-
-msgid "Create tenant router to link tenant network and external"
-msgstr "Buat router tenant untuk menghubungkan jaringan tenant dan eksternal"
-
-msgid "CronJobs"
-msgstr "CronJobs"
-
-msgid ""
-"Currently OpenStack-Helm supports OpenVSwitch as a network virtualization "
-"engine. In order to support many possible backends (SDNs), changes are "
-"required in neutron chart and in deployment techniques. OpenStack-Helm can "
-"support every SDN solution that has Neutron plugin, either core_plugin or "
-"mechanism_driver."
-msgstr ""
-"Saat ini OpenStack-Helm mendukung OpenVSwitch sebagai mesin virtualisasi "
-"jaringan. Untuk mendukung banyak kemungkinan backend (SDNs), perubahan "
-"diperlukan dalam chart neutron dan teknik penyebaran. OpenStack-Helm dapat "
-"mendukung setiap solusi SDN yang memiliki plugin Neutron, baik core_plugin "
-"atau mechanism_driver"
-
-msgid ""
-"Currently both OpenStack-Helm and OpenStack-Helm-Infra have their own "
-"parallel versions of the Helm-Toolkit library chart.  They must be combined "
-"into a single chart in OpenStack-Helm-Infra prior to 1.0."
-msgstr ""
-"Saat ini baik OpenStack-Helm dan OpenStack-Helm-Infra memiliki versi paralel "
-"mereka sendiri dari chart pustaka Helm-Toolkit. Mereka harus digabungkan "
-"menjadi satu chart tunggal di OpenStack-Helm-Infra sebelum 1.0."
-
-msgid "DHCP - auto-assign IP address and DNS info"
-msgstr "DHCP - auto-assign IP address dan DNS info"
-
-msgid "Database drop Job"
-msgstr "Database drop Job"
-
-msgid "Deploy Kubernetes via KubeADM, with charts for CNI and DNS services"
-msgstr ""
-"Menyebarkan Kubernet melalui KubeADM, dengan grafik untuk layanan CNI dan DNS"
-
-msgid "Deploying multuple Ceph clusters"
-msgstr "Menyebarkan multiple cluster Ceph"
-
-msgid ""
-"Develop scripts for bringing up OpenStack-Helm Charts and perform basic "
-"interactive tests"
-msgstr ""
-"Kembangkan skrip untuk memunculkan OpenStack-Helm Charts dan melakukan tes "
-"interaktif dasar"
-
-msgid "Developer Environment"
-msgstr "Lingkungan Pengembang"
-
-msgid ""
-"Developers require a simple way of instantiating a working environment for "
-"OpenStack-Helm, that allows them to quickly begin development of the "
-"project. This is more complex to achieve than many OpenStack Projects that "
-"can simply rely upon a devstack plugin to achieve this. This is as OpenStack-"
-"Helm is focused on the deployment of OpenStack (and associated) Projects, "
-"rather than the development of the projects themselves, and also requires "
-"additional supporting infrastructure, e.g. Kubernetes and a CNI."
-msgstr ""
-"Pengembang membutuhkan cara sederhana untuk membuat contoh lingkungan kerja "
-"OpenStack-Helm, yang memungkinkan mereka untuk dengan cepat memulai "
-"pengembangan proyek. Ini lebih kompleks untuk dicapai daripada banyak "
-"OpenStack Project yang hanya dapat mengandalkan plugin devstack untuk "
-"mencapai ini. Ini karena OpenStack-Helm berfokus pada penyebaran OpenStack "
-"Project (dan yang terkait), daripada pengembangan proyek itu sendiri, dan "
-"juga membutuhkan infrastruktur pendukung tambahan, misal Kubernetes dan CNI."
-
-msgid "Development of OpenStack-Helm"
-msgstr "Perkembangan OpenStack-Helm"
-
-msgid "Documentation"
-msgstr "Dokumentasi"
-
-msgid "Documentation Impact"
-msgstr "Dampak Dokumentasi"
-
-msgid ""
-"Documentation of how new SDN can be enabled, how Neutron should be "
-"configured. Also, for each new SDN that would be incorporated, the "
-"architecture overview should be provided."
-msgstr ""
-"Dokumentasi tentang bagaimana SDN baru dapat diaktifkan, bagaimana Neutron "
-"harus dikonfigurasi. Juga, untuk setiap SDN baru yang akan dimasukkan, "
-"tinjauan arsitektur harus disediakan."
-
-msgid "Documentation of how to enable the registry secret generation"
-msgstr "Dokumentasi cara mengaktifkan pembuatan rahasia registri"
-
-msgid "Documentation on how to use LinuxBridge with Neutron chart."
-msgstr "Dokumentasi tentang cara menggunakan LinuxBridge dengan chart Neutron."
-
-msgid ""
-"Documentation should be included for each of the included charts as well as "
-"documentation detailing the requirements for a usable monitoring platform, "
-"preferably with sane default values out of the box."
-msgstr ""
-"Dokumentasi harus disertakan untuk masing-masing grafik termasuk juga "
-"dokumentasi yang merinci persyaratan untuk platform pemantauan yang dapat "
-"digunakan, lebih disukai dengan default values out of the box yang masuk "
-"akal."
-
-msgid "Duplicate scripts as shows below for later use."
-msgstr ""
-"Duplikat skrip seperti yang ditunjukkan di bawah ini untuk digunakan nanti."
-
-msgid ""
-"Dynamically alter webserver environment conditionally in the helm chart. For "
-"example, for apache, ensure the necessary modules to run openstack are "
-"available and loaded at helm chart deploy time. This will leverage the "
-"binaries listed in ``values.yaml``. These series of commands are "
-"distribution/image dependent, as commands to list modules to load might "
-"differ. However with a few parameters, we can get a very distro independent "
-"process which would allow us to load all the required apache modules."
-msgstr ""
-"Secara dinamis mengubah lingkungan server web secara kondisional di helm "
-"chart.  Sebagai contoh, untuk apache, pastikan modul yang diperlukan untuk "
-"menjalankan openstack tersedia dan dimuat pada waktu penggelaran helm chart. "
-"Ini akan memanfaatkan binari yang terdaftar di ``values.yaml``. Rangkaian "
-"perintah ini bergantung pada distribution/image, karena perintah untuk "
-"mendaftar modul yang akan dimuat mungkin berbeda. Namun dengan beberapa "
-"parameter, kita bisa mendapatkan proses independen distro yang memungkinkan "
-"kita memuat semua modul apache yang diperlukan."
-
-msgid ""
-"Each chart's values.yaml file contains various settings such as docker image "
-"definition, chart structure setting, form of the resources being "
-"distributed, and process configuration.  Currently, the structure of the "
-"yaml file is complicated, and finding keys between charts proves difficult "
-"due to the lack of uniform values organization across charts."
-msgstr ""
-"Setiap file values.yaml chart berisi berbagai pengaturan seperti definisi "
-"docker image, pengaturan struktur chart, bentuk sumber daya yang "
-"didistribusikan, dan konfigurasi proses. Saat ini, struktur file yaml rumit, "
-"dan menemukan kunci di antara chart terbukti sulit karena kurangnya nilai "
-"seragam organisasi di seluruh chart."
-
-msgid ""
-"Edit all helm charts to remove possible references to image specific "
-"elements, replacing them with values overrides or conditionals."
-msgstr ""
-"Edit semua bagan helm untuk menghapus referensi yang mungkin untuk elemen "
-"spesifik image, override dengan nilai yang menimpa atau kondisional."
-
-msgid "Elasticsearch chart"
-msgstr "Elasticsearch chart"
-
-msgid ""
-"Elasticsearch configured in a highly available manner with sane defaults"
-msgstr ""
-"Elasticsearch dikonfigurasi dengan cara yang sangat tersedia dengan standar "
-"yang masuk akal"
-
-msgid "Elasticsearch configured to prevent memory swapping to disk"
-msgstr "Elasticsearch dikonfigurasi untuk mencegah pertukaran memori ke disk"
-
-msgid "Env Setup:"
-msgstr "Env Setup:"
-
-msgid "Etc ConfigMaps"
-msgstr "Etc ConfigMaps"
-
-msgid "Every Fluentbit send logs to Fluentd with Kubernetes metadata attached"
-msgstr ""
-"Setiap Fluentbit mengirim log ke Fluentd dengan metadata Kubernetes terlampir"
-
-msgid ""
-"Every Kubernetes manifest inside Neutron chart can be enabled or disabled. "
-"That would provide flexibility to the operator, to choose which Neutron "
-"components are reusable with different type of SDNs. For example, neutron-"
-"server which is serving the API and configuring the database can be used "
-"with different types of SDN plugin, and provider of that SDN chart would not "
-"need to copy all logic from Neutron base chart to manage the API and "
-"database."
-msgstr ""
-"Setiap manifes Kubernet dalam chart Neutron dapat diaktifkan atau "
-"dinonaktifkan. Itu akan memberikan fleksibilitas kepada operator, untuk "
-"memilih komponen Neutron mana yang dapat digunakan kembali dengan berbagai "
-"jenis SDN. Misalnya, server neutron yang melayani API dan mengonfigurasi "
-"basis data dapat digunakan dengan berbagai jenis plugin SDN, dan penyedia "
-"chart SDN itu tidak perlu menyalin semua logika dari chart dasar Neutron "
-"untuk mengelola API dan basis data."
-
-msgid "Example OpenStack-Helm metrics requiring monitoring include:"
-msgstr "Contoh metrik OpenStack-Helm yang membutuhkan pemantauan meliputi:"
-
-msgid "Example uses for centralized logging include:"
-msgstr "Contoh penggunaan untuk logging terpusat meliputi:"
-
-msgid ""
-"Example uses for centralized logging with Fluentbit and Fluentd include:"
-msgstr ""
-"Contoh penggunaan untuk logging terpusat dengan Fluentbit dan Fluentd "
-"meliputi:"
-
-msgid "Examples of how these metrics can be used include:"
-msgstr "Contoh bagaimana metrik ini dapat digunakan meliputi:"
-
-msgid ""
-"Examples of how to set up the above under KubeADM and KubeSpray-based "
-"clusters must be documented as well."
-msgstr ""
-"Contoh cara mengatur di atas di bawah KubeADM dan cluster berbasis KubeSpray "
-"harus didokumentasikan juga."
-
-msgid "Execute script"
-msgstr "Jalankan skrip"
-
-msgid "Execute script."
-msgstr "Jalankan skrip."
-
-msgid ""
-"Exposes security/configuration features of software, allowing deployers to "
-"configure software to their needs."
-msgstr ""
-"Mengekspos fitur security/configuration perangkat lunak, memungkinkan "
-"penyebar untuk mengkonfigurasi perangkat lunak sesuai kebutuhan mereka."
-
-msgid "External charts (Calico)"
-msgstr "External charts (Calico)"
-
-msgid "Find all backtraces for a tenant id's uuid"
-msgstr "Temukan semua backtraces untuk uuid id penyewa"
-
-msgid ""
-"Find all logged events that match a pattern (service, pod, behavior, etc)"
-msgstr ""
-"Temukan semua peristiwa yang dicatat yang cocok dengan pola (layanan, pod, "
-"perilaku, dll)"
-
-msgid ""
-"First reasonable testing in gates would be to setup Linux Bridge and check "
-"if VM network connectivity is working."
-msgstr ""
-"Pengujian masuk akal pertama di gate adalah untuk mengatur Linux Bridge dan "
-"memeriksa apakah konektivitas jaringan VM berfungsi."
-
-msgid ""
-"Fluentbit, Fluentd meet OpenStack-Helm's logging requirements for gathering, "
-"aggregating, and delivering of logged events. Fluntbit runs as a daemonset "
-"on each node and mounts the /var/lib/docker/containers directory. The Docker "
-"container runtime engine directs events posted to stdout and stderr to this "
-"directory on the host. Fluentbit then forward the contents of that directory "
-"to Fluentd. Fluentd runs as deployment at the designated nodes and expose "
-"service for Fluentbit to forward logs. Fluentd should then apply the "
-"Logstash format to the logs. Fluentd can also write Kubernetes and OpenStack "
-"metadata to the logs. Fluentd will then forward the results to Elasticsearch "
-"and to optionally Kafka. Elasticsearch indexes the logs in a logstash-* "
-"index by default. Kafka stores the logs in a 'logs' topic by default. Any "
-"external tool can then consume the 'logs' topic."
-msgstr ""
-"Fluentbit, Fluentd memenuhi persyaratan logging OpenStack-Helm untuk "
-"mengumpulkan, mengagregasi, dan mengirimkan peristiwa yang dicatat. Fluntbit "
-"berjalan sebagai daemonset pada setiap node dan me-mount direktori /var/lib/"
-"docker/containers. Mesin runtime kontainer Docker mengarahkan event yang "
-"diposting ke stdout dan stderr ke direktori ini di host. Fluentbit kemudian "
-"meneruskan isi direktori itu ke Fluentd. Fluentd berjalan sebagai penyebaran "
-"di node yang ditunjuk dan mengekspos layanan untuk Fluentbit untuk "
-"meneruskan log. Fluentd kemudian harus menerapkan format Logstash ke log. "
-"Fluentd juga dapat menulis metadata Kubernetes dan OpenStack ke log. Fluentd "
-"kemudian akan meneruskan hasilnya ke Elasticsearch dan ke opsional Kafka. "
-"Elasticsearch mengindeks log dalam logstash-* index secara default. Kafka "
-"menyimpan log dalam topik 'log' secara default. Alat eksternal apa pun "
-"kemudian dapat menggunakan topik 'log'."
-
-msgid "Fluentbit-Fluentd logging chart"
-msgstr "Fluentbit-Fluentd logging chart"
-
-msgid "Fluentd chart"
-msgstr "Fluentd chart"
-
-msgid "Fluentd properly filters and categorizes logs"
-msgstr "Fluentd memfilter dan mengkategorikan log dengan benar"
-
-msgid ""
-"Fluentd send aggregated logs to Elasticsearch for the internal use cases"
-msgstr ""
-"Fluentd mengirim log agregat ke Elasticsearch untuk kasus penggunaan internal"
-
-msgid "Fluentd then attaches Kubernetes and/or OpenStack metadata"
-msgstr "Fluentd kemudian melampirkan Kubernetes dan/atau metadata OpenStack"
-
-msgid ""
-"Fluentd, Elasticsearch, and Kibana meet OpenStack-Helm's logging "
-"requirements for capture, storage and visualization of logged events.  "
-"Fluentd runs as a daemonset on each node and mounts the /var/lib/docker/"
-"containers directory. The Docker container runtime engine directs events "
-"posted to stdout and stderr to this directory on the host.  Fluentd should "
-"then declare the contents of that directory as an input stream, and use the "
-"fluent-plugin-elasticsearch plugin to apply the Logstash format to the "
-"logs.  Fluentd will also use the fluentd-plugin-kubernetes-metadata plugin "
-"to write Kubernetes metadata to the log record.  Fluentd will then forward "
-"the results to Elasticsearch, which indexes the logs in a logstash-* index "
-"by default.  The resulting logs can then be queried directly through "
-"Elasticsearch, or they can be viewed via Kibana. Kibana offers a dashboard "
-"that can create custom views on logged events, and Kibana integrates well "
-"with Elasticsearch by default."
-msgstr ""
-"Fluentd, Elasticsearch, dan Kibana memenuhi persyaratan logging OpenStack-"
-"Helm untuk menangkap, menyimpan, dan memvisualisasikan event yang dicatat. "
-"Fluentd berjalan sebagai daemonset pada setiap node dan me-mount direktori /"
-"var/lib/docker/containers. Mesin runtime kontainer Docker mengarahkan event "
-"yang diposting ke stdout dan stderr ke direktori ini di host. Fluentd "
-"kemudian harus mendeklarasikan isi direktori itu sebagai aliran input, dan "
-"menggunakan plugin fluent-plugin-elasticsearch untuk menerapkan format "
-"Logstash ke log. Fluentd juga akan menggunakan plugin fluentd-plugin-"
-"kubernetes-metadata untuk menulis metadata Kubernetes ke catatan log. "
-"Fluentd kemudian akan meneruskan hasilnya ke Elasticsearch, yang secara "
-"default mengindeks log dalam indeks logstash-*. Log yang dihasilkan kemudian "
-"dapat ditanyakan langsung melalui Elasticsearch, atau mereka dapat dilihat "
-"melalui Kibana. Kibana menawarkan dasbor yang dapat membuat tampilan kustom "
-"pada event yang dicatat, dan Kibana terintegrasi dengan baik dengan "
-"Elasticsearch secara default."
-
-msgid ""
-"For Tenant Ceph, we will not be provisioning storage classes therefor, "
-"update script to not install ceph-provisioners chart as following."
-msgstr ""
-"Untuk Tenant Ceph, kami tidak akan menyediakan kelas penyimpanan karenanya, "
-"update skrip untuk tidak memasang chart ceph-provisioners sebagai berikut."
-
-msgid ""
-"For the ``Category B`` helm charts, an informal testing has been done in the "
-"past to ensure image independence. However, there is nothing exercising this "
-"independence in gates. Due to that, code of the helm charts might or might "
-"not require adapting."
-msgstr ""
-"Untuk  ``Category B`` helm chart, pengujian informal telah dilakukan di masa "
-"lalu untuk memastikan independensi image. Namun, tidak ada yang melaksanakan "
-"independensi ini di gate. Karena itu, kode helm chart mungkin perlu atau "
-"tidak perlu diadaptasi."
-
-msgid ""
-"For this spec, we assume ``imagename1`` and ``imagename2`` are similarly "
-"built. This means we do not require any override per image. Instead we "
-"require a generic kind of override, per application, usable by all charts."
-msgstr ""
-"Untuk spek ini, kami mengasumsikan ``imagename1`` dan ``imagename2`` "
-"dibangun dengan cara yang sama. Ini berarti kami tidak memerlukan "
-"penggantian apa pun per image. Sebagai gantinya, kami memerlukan jenis "
-"override umum, per aplikasi, dapat digunakan oleh semua chart."
-
-msgid "Gate job testing VM network connectivity."
-msgstr "Gate job testing konektivitas jaringan VM"
-
-msgid "Gating"
-msgstr "Gating"
-
-msgid ""
-"Gating must prove that upgrades from each supported OpenStack version to the "
-"next operate flawlessly, using the default image set (LOCI).  Specifically, "
-"each OpenStack chart should be upgraded from one release to the next, and "
-"each infrastructure service from one minor version to the next.  Both the "
-"container image and configuration must be modified as part of this upgrade. "
-"At minimum, Newton to Ocata upgrade must be validated for the 1.0 release."
-msgstr ""
-"Gating harus membuktikan bahwa upgrade dari setiap versi OpenStack yang "
-"didukung ke operasi selanjutnya dengan sempurna, menggunakan set image "
-"default (LOCI). Secara khusus, setiap bagan OpenStack harus ditingkatkan "
-"dari satu rilis ke yang berikutnya, dan setiap layanan infrastruktur dari "
-"satu versi minor ke yang berikutnya. Baik image kontainer maupun konfigurasi "
-"harus dimodifikasi sebagai bagian dari upgrade ini. Minimal, upgrade Newton "
-"ke Ocata harus divalidasi untuk rilis 1.0."
-
-msgid "Grafana chart"
-msgstr "Grafana chart"
-
-msgid ""
-"Having services configured, also the services pod dependencies should be "
-"updated to reflect the new kind on L2 agent:"
-msgstr ""
-"Setelah layanan dikonfigurasi, dependensi pod layanan juga harus diperbarui "
-"untuk mencerminkan jenis baru pada agen L2:"
-
-msgid "Helm"
-msgstr "Helm"
-
-msgid "Helm chart for Alertmanager"
-msgstr "Helm chart untuk Alertmanager"
-
-msgid "Helm chart for Elasticsearch"
-msgstr "Helm chart untuk Elasticsearch"
-
-msgid "Helm chart for Fluentbit-Fluentd Combination"
-msgstr "Helm chart untuk Fluentbit-Fluentd Combination"
-
-msgid "Helm chart for Fluentd"
-msgstr "Helm chart untuk Fluentd"
-
-msgid "Helm chart for Grafana"
-msgstr "Helm chart untuk Grafana"
-
-msgid "Helm chart for Kibana"
-msgstr "Helm chart untuk Kibana"
-
-msgid "Helm chart for Prometheus"
-msgstr "Helm chart untuk Prometheus"
-
-msgid "Helm charts for any appropriate Prometheus exporters"
-msgstr "Helm chart untuk eksportir Prometheus yang tepat"
-
-msgid ""
-"Helm charts for which we are building images in osh-images. (Called further "
-"``Category B`` helm charts)"
-msgstr ""
-"helm chart dimana kami sedang membangun gambar dalam gambar-osh. (Disebut "
-"lebih lanjut ``Category B`` helm chart)"
-
-msgid ""
-"Helm charts for which we use official upstream images. (Called further "
-"``Category A`` helm charts)"
-msgstr ""
-"Helm chart yang kami gunakan menggunakan image hulu resmi. (Disebut lebih "
-"lanjut ``Category A`` helm chart)"
-
-msgid "Helm must be installed"
-msgstr "Helm harus dipasang"
-
-msgid ""
-"Helm test is the building block for all gating.  Each chart must integrate a "
-"helm-test script which validates proper functionality.  This is already a "
-"merge criterion for new charts, but a handful of older charts still need for "
-"helm test functionality to be added.  No additional charts will be merged "
-"prior to 1.0 unless they meet this requirement (and others in this document)."
-msgstr ""
-"Tes helm adalah blok bangunan untuk semua gating. Setiap chart harus "
-"mengintegrasikan skrip uji coba yang memvalidasi fungsi yang tepat. Ini "
-"sudah menjadi kriteria penggabungan untuk chart baru, tetapi beberapa chart "
-"lama masih perlu ditambahkan fungsionalitas uji helm. Tidak ada grafik "
-"tambahan yang akan digabung sebelum 1.0 kecuali mereka memenuhi persyaratan "
-"ini (dan yang lainnya dalam dokumen ini)."
-
-msgid "Here is a list of the current specs:"
-msgstr "Berikut adalah daftar spesifikasi saat ini:"
-
-msgid "Host utilization: memory usage, CPU usage, disk I/O, network I/O, etc"
-msgstr ""
-"Pemanfaatan host: penggunaan memori, penggunaan CPU, disk I / O, I / O "
-"jaringan, dll"
-
-msgid "Hosts must use KubeDNS / CoreDNS for resolution"
-msgstr "Host harus menggunakan KubeDNS / CoreDNS untuk resolusi"
-
-msgid ""
-"I propose to extend the conf schema with generic software information. For "
-"example, for apache2:"
-msgstr ""
-"Saya mengusulkan untuk memperluas skema conf dengan informasi perangkat "
-"lunak umum. Misalnya, untuk apache2:"
-
-msgid "Identify etcd performance that could lead to cluster instability"
-msgstr ""
-"Identifikasi kinerja etcd yang dapat menyebabkan ketidakstabilan cluster"
-
-msgid ""
-"Identify issues with Kubernetes components, such as: etcd, CNI, scheduler, "
-"etc"
-msgstr ""
-"Identifikasi masalah dengan komponen Kubernetes, seperti: etcd, CNI, "
-"scheduler, dll"
-
-msgid ""
-"Identify issues with infrastructure components, such as RabbitMQ, mariadb, "
-"etc"
-msgstr ""
-"Identifikasi masalah dengan komponen infrastruktur, seperti RabbitMQ, "
-"mariadb, dll"
-
-msgid "Identify opportunities for improving Prometheus's operation over time"
-msgstr ""
-"Identifikasi peluang untuk meningkatkan operasi Prometheus dari waktu ke "
-"waktu"
-
-msgid ""
-"If .Values.endpoints.oci_image_registry.auth.enabled will be set to true, "
-"then any containers created with the current service account will have the "
-"``imagePullSecrets`` automatically added to their spec and the secret will "
-"be passed to kubelet to be used for pulling images."
-msgstr ""
-"Jika .Values.endpoints.oci_image_registry.auth.enabled akan disetel ke true, "
-"maka setiap kontainer yang dibuat dengan akun layanan saat ini akan memiliki "
-"``imagePullSecrets`` secara otomatis ditambahkan ke spesifikasi mereka dan "
-"rahasia akan diteruskan ke kubelet untuk digunakan untuk menarik image."
-
-msgid ""
-"If :code:`.Values.manifests.daemonset_ovs_agent` will be set to false, "
-"neutron ovs agent would not be launched. In that matter, other type of L2 or "
-"L3 agent on compute node can be run."
-msgstr ""
-"If :code:`.Values.manifests.daemonset_ovs_agent` akan disetel ke false, agen "
-"neutron ovs tidak akan diluncurkan. Dalam hal ini, agen L2 atau L3 jenis "
-"lain pada node komputasi dapat dijalankan."
-
-msgid "Implement decomposable Neutron chart"
-msgstr "Terapkan chart Neutron terurai (decomposable)"
-
-msgid "Implementation"
-msgstr "Pelaksanaan"
-
-msgid ""
-"In a secured deployment, TLS certificates are used to protect the transports "
-"amongst the various components.  In some cases, this requires additional "
-"mechanism to handle TLS offloading and to terminate the connection "
-"gracefully:"
-msgstr ""
-"Dalam penyebaran yang aman, sertifikat TLS digunakan untuk melindungi "
-"transportasi di antara berbagai komponen. Dalam beberapa kasus, ini "
-"membutuhkan mekanisme tambahan untuk menangani pemuatan TLS dan untuk "
-"mengakhiri koneksi dengan lembut:"
-
-msgid "In above example OVS and Neutron OVS agent are disabled."
-msgstr "Dalam contoh di atas agen OVS dan Neutron OVS dinonaktifkan."
-
-msgid ""
-"In all cases, we will need to provide different ``profiles`` (in other "
-"words, overrides), to test different image providers use cases in CI."
-msgstr ""
-"Dalam semua kasus, kami akan perlu memberikan ``profil`` yang berbeda "
-"(dengan kata lain, override), untuk menguji berbagai kasus penggunaan "
-"penyedia image dalam CI."
-
-msgid ""
-"In order to maximize flexibility for operators, and to help facilitate "
-"upgrades to newer versions of containerized software without editing the "
-"chart itself, all configuration files will be specified dynamically based on "
-"`values.yaml` and overrides.  In most cases the config files will be "
-"generated based on the YAML values tree itself, and in some cases the config "
-"file content will be specified in `values.yaml` as a string literal."
-msgstr ""
-"Untuk memaksimalkan fleksibilitas bagi operator, dan untuk membantu "
-"memfasilitasi upgrade ke versi yang lebih baru dari perangkat lunak "
-"containerized tanpa mengedit chart itu sendiri, semua file konfigurasi akan "
-"ditentukan secara dinamis berdasarkan pada `values.yaml` dan override. Dalam "
-"kebanyakan kasus file config akan dihasilkan berdasarkan pada YAML values "
-"tree itu sendiri, dan dalam beberapa kasus konten file config akan "
-"ditentukan dalam `values.yaml` sebagai string literal."
-
-msgid "In particular, these charts must move to OpenStack-Helm-Infra:"
-msgstr "Secara khusus, chart ini harus pindah ke OpenStack-Helm-Infra:"
-
-msgid ""
-"In the current openstack-helm, all charts provide an ``images:`` section in "
-"their ``values.yaml`` that have the container images references. By default, "
-"the container images are all downloaded from a registry hosted by Docker or "
-"Quay. However, the image references can be overridden by operators to "
-"download images from any OCI image registry. In the case that the OCI image "
-"registry has authentication turned on, kubelet would fail to download the "
-"images because the current Openstack-Helm does not provide a way to pass the "
-"OCI image registry credentials to kubernetes when pulling images."
-msgstr ""
-"Di openstack-helm saat ini, semua chart menyediakan bagian ``images:`` di "
-"``values.yaml`` mereka yang memiliki referensi image kontainer. Secara "
-"default, semua image kontainer diunduh dari registri yang diselenggarakan "
-"oleh Docker atau Quay. Namun, referensi image dapat diganti oleh operator "
-"untuk mengunduh image dari registri image OCI. Jika registry image OCI telah "
-"dihidupkan otentikasi, kubelet akan gagal mengunduh image karena Openstack-"
-"Helm saat ini tidak menyediakan cara untuk meneruskan kredensial registri "
-"image OCI ke kubernet ketika menarik image."
-
-msgid "Include the URL of your Storyboard RFE:"
-msgstr "Sertakan URL RF Storyboard Anda:"
-
-msgid ""
-"Installing OVS requires Kubernetes worker node labeling with tag :code:"
-"`openvswitch=enabled`. To mark nodes where LB should be used, new tag will "
-"be introduced: :code:`linuxbridge=enabled`."
-msgstr ""
-"Instalasi OVS membutuhkan pelabelan node Kubernetes worker dengan tag :code:"
-"`openvswitch=enabled`. Untuk menandai node tempat LB harus digunakan, tag "
-"baru akan diperkenalkan: :code:`linuxbridge=enabled`."
-
-msgid "Instead of using nginx, haproxy can be used instead."
-msgstr "Daripada menggunakan nginx, haproxy dapat digunakan sebagai gantinya."
-
-msgid ""
-"Introducing a new SDN solution should consider how the above services are "
-"provided. It may be required to disable the built-in Neutron functionality."
-msgstr ""
-"Memperkenalkan solusi SDN baru harus mempertimbangkan bagaimana layanan di "
-"atas disediakan. Mungkin diperlukan untuk menonaktifkan fungsionalitas "
-"Neutron bawaan (built-in)."
-
-msgid ""
-"It is important to notice that the helm charts can be split in two "
-"categories for now:"
-msgstr ""
-"Penting untuk diperhatikan bahwa chart helm dapat dibagi menjadi dua "
-"kategori untuk saat ini:"
-
-msgid "Kibana chart"
-msgstr "Kibana chart"
-
-msgid "Kubernetes"
-msgstr "Kubernetes"
-
-msgid "Kubernetes metrics: pod status, replica availability, job status, etc"
-msgstr ""
-"Metrik Kubernetes: status pod, ketersediaan replika, status pekerjaan, dll"
-
-msgid ""
-"Kubernetes must enable mount propagation (until it is enabled by default)"
-msgstr ""
-"Kubernet harus mengaktifkan propagasi mount (sampai diaktifkan secara "
-"default)"
-
-msgid "L3 routing - creation of routers"
-msgstr "L3 routing - pembuatan router"
-
-msgid "Labels assigned to nodes: node1, node2, node3:"
-msgstr "Label diberikan ke node: node1, node2, node3:"
-
-msgid "Labels assigned to nodes: node4, node5, node6:"
-msgstr "Label diberikan ke node: node4, node5, node6:"
-
-msgid ""
-"Labels for mon, osd, rgw, mgr and job have been updated for tenant Ceph."
-msgstr ""
-"Label untuk mon, osd, rgw, mgr dan pekerjaan telah diperbarui untuk tenant "
-"Ceph."
-
-msgid ""
-"Let's consider how new SDN can take advantage of disaggregated Neutron "
-"services architecture. First assumption is that neutron-server functionality "
-"would be common for all SDNs, as it provides networking API, database "
-"management and Keystone interaction. Required modifications are:"
-msgstr ""
-"Mari kita pertimbangkan bagaimana SDN baru dapat memanfaatkan arsitektur "
-"layanan Neutron terpilah (disaggregated). Asumsi pertama adalah bahwa "
-"fungsionalitas server neutron akan umum untuk semua SDN, karena menyediakan "
-"API jaringan, manajemen basis data, dan interaksi Keystone. Modifikasi yang "
-"diperlukan adalah:"
-
-msgid ""
-"LinuxBridge installation with neutron chart takes advantaged of decomposable "
-"neutron chart in OSH. LinuxBridge agent will be added as daemonset, "
-"similarly how OVS is implemented. New value :code:`daemonset_lb_agent` "
-"should be added in :code:`neutron/values.yaml` in :code:`manifests` section:"
-msgstr ""
-"Instalasi LinuxBridge dengan chart neutron mengambil keuntungan dari chart "
-"neutron decomposable di OSH. Agen LinuxBridge akan ditambahkan sebagai "
-"daemonset, sama seperti bagaimana OVS diimplementasikan. Nilai baru :code:"
-"`daemonset_lb_agent`  harus ditambahkan dalam :code:`neutron/values.yaml` di "
-"hagian :code:`manifests``:"
-
-msgid "LinuxBridge should be also enabled in :code:`manifests` section:"
-msgstr "LinuxBridge juga harus diaktifkan di bagian :code:`manifests` :"
-
-msgid ""
-"LinuxBridge should support external bridge configuration, as well as auto "
-"bridge add mechanism implemented for OVS."
-msgstr ""
-"LinuxBridge harus mendukung konfigurasi jembatan eksternal, serta mekanisme "
-"penambahan jembatan otomatis yang diterapkan untuk OVS."
-
-msgid "Log aggregator deployment runs on a selected node as deployment"
-msgstr ""
-"Penerapan agregator log berjalan pada node yang dipilih sebagai penyebaran"
-
-msgid "Log aggregator is able to send data to Elasticsearch and Kafka"
-msgstr "Log aggregator dapat mengirim data ke Elasticsearch dan Kafka"
-
-msgid "Log aggregator should be scalable"
-msgstr "Log agregator harus scalable"
-
-msgid "Log aggregator should have HA capability"
-msgstr "Log aggregator harus memiliki kemampuan HA"
-
-msgid "Log aggregator should have a flexible output capability to choose from"
-msgstr ""
-"Log aggregator harus memiliki kemampuan output yang fleksibel untuk dipilih"
-
-msgid "Log collection daemon runs on each node to forward logs to aggregator"
-msgstr ""
-"Log koleksi daemon berjalan pada setiap node untuk meneruskan log ke "
-"aggregator"
-
-msgid "Log collection daemon runs on each node to forward logs to storage"
-msgstr ""
-"Log koleksi daemon berjalan pada setiap node untuk meneruskan log ke "
-"penyimpanan"
-
-msgid "Log collection daemon should have a minimal server footprint"
-msgstr "Daemon pengumpulan log harus memiliki jejak server minimal"
-
-msgid "Logging"
-msgstr "Logging"
-
-msgid "Logging Requirements"
-msgstr "Persyaratan Logging"
-
-msgid "Logging Use Cases"
-msgstr "Mencatat Penggunaan Kasus (logging use case)"
-
-msgid "Logical Diagram"
-msgstr "Diagram Logika"
-
-msgid ""
-"Make following changes to script: 1 Replace occurrence of ``ceph-fs-uuid."
-"txt`` with ``tenant-ceph-fs-uuid.txt``"
-msgstr ""
-"Buat perubahan berikut pada skrip: 1 Ganti kemunculan ``ceph-fs-uuid.txt`` "
-"dengan ``tenant-ceph-fs-uuid.txt``"
-
-msgid ""
-"Make webserver binary path/arguments templated using ``values.yaml``. As "
-"expressed above, this allows us to provide different overrides per image/"
-"distribution to automatically wire things."
-msgstr ""
-"Buat path/argument biner webserver templated menggunakan ``values.yaml``. "
-"Seperti yang dinyatakan di atas, ini memungkinkan kami untuk memberikan "
-"penggantian yang berbeda per image/distribution untuk secara otomatis "
-"mentransfer berbagai hal."
-
-msgid "Metadata- Provide proxy for Nova metadata service"
-msgstr "Metadata- Berikan proxy untuk layanan Nova metadata"
-
-msgid "Monitoring"
-msgstr "Pemantauan"
-
-msgid "Monitoring Requirements"
-msgstr "Persyaratan Pemantauan"
-
-msgid "Monitoring Use Cases"
-msgstr "Memonitor Kasus Penggunaan"
-
-msgid ""
-"More information about the blueprint + specification lifecycle can be found "
-"here_."
-msgstr ""
-"Informasi lebih lanjut tentang siklus hidup blueprint + spesifikasi dapat "
-"ditemukan here_."
-
-msgid "Multi-OS Support"
-msgstr "Dukungan Multi-OS"
-
-msgid "Neutron multiple SDNs"
-msgstr "Neutron multiple SDNs"
-
-msgid "New charts"
-msgstr "New charts"
-
-msgid ""
-"Next, Neutron services like L3 routing, DHCP and metadata serving should be "
-"considered. If SDN provides its own implementation, the Neutron's default "
-"one should be disabled:"
-msgstr ""
-"Selanjutnya, layanan Neutron seperti L3 routing, DHCP dan penyajian metadata "
-"harus dipertimbangkan. Jika SDN menyediakan implementasinya sendiri, default "
-"Neutron harus dinonaktifkan:"
-
-msgid "Nginx Sidecar"
-msgstr "Nginx Sidecar"
-
-msgid "No benchmark was done to evaluate:"
-msgstr "Tidak ada patokan yang dilakukan untuk mengevaluasi:"
-
-msgid ""
-"No change in testing is required, *per se*. It is expected the new software "
-"configuration would be tested with the current practices."
-msgstr ""
-"Tidak diperlukan perubahan dalam pengujian, *per se*. Diharapkan konfigurasi "
-"perangkat lunak baru akan diuji dengan praktik saat ini."
-
-msgid ""
-"No direct impact, as there is no change in the current software/"
-"configuration location, merely a templating change."
-msgstr ""
-"Tidak ada dampak langsung, karena tidak ada perubahan pada lokasi software/"
-"configuration saat ini, hanya perubahan templating."
-
-msgid "No impact"
-msgstr "Tidak ada dampak"
-
-msgid "No performance impact"
-msgstr "Tidak ada dampak kinerja"
-
-msgid "No security impact."
-msgstr "Tidak ada dampak keamanan."
-
-msgid "None"
-msgstr "None"
-
-msgid ""
-"None more than this spec, as it should be relatively transparent for the "
-"user. However, extra documentation to explain the usage of "
-"``value_overrides`` would be welcomed."
-msgstr ""
-"Tidak lebih dari spesifikasi ini, karena seharusnya relatif transparan untuk "
-"pengguna. Namun, dokumentasi tambahan untuk menjelaskan penggunaan "
-"``value_overrides`` akan disambut."
-
-msgid ""
-"Not providing a support of multiple images. This leads to ease of "
-"maintainance and reduced gate impact, with the risk of having less "
-"contributors. For available overrides, users would have to provide many "
-"overrides themselves, while this spec proposes a common community approach."
-msgstr ""
-"Tidak memberikan dukungan multiple image. Ini mengarah pada kemudahan "
-"pemeliharaan dan mengurangi dampak gate, dengan risiko memiliki lebih "
-"sedikit kontributor. Untuk override yang tersedia, pengguna harus "
-"menyediakan sendiri banyak override, sementara spesifikasi ini mengusulkan "
-"pendekatan komunitas umum."
-
-msgid "Note that mon_addr and mon_host have default mon port 6789."
-msgstr "Perhatikan bahwa mon_addr dan mon_host memiliki mon port default 6789."
-
-msgid "OSH Logging, Monitoring, and Alerting"
-msgstr "OSH Logging, Monitoring, dan Alerting"
-
-msgid ""
-"OVS is an alternative in Neutron reference architecture. It is already in "
-"tree."
-msgstr ""
-"OVS adalah alternatif dalam arsitektur referensi Neutron. Sudah ada di tree."
-
-msgid ""
-"On top of that, the newly provided `example_values/` must aim for being "
-"tested **as soon as possible upon delivery**. Without tests, those examples "
-"will decrepit. The changes in CI pipelines for making use of "
-"`example_values` is outside the scope of this spec."
-msgstr ""
-"Selain itu, `example_values/` yang baru disediakan harus bertujuan untuk "
-"diuji ***as soon as possible upon delivery**. Tanpa tes, contoh itu akan "
-"usang. Perubahan dalam pipeline CI untuk menggunakan `example_values` berada "
-"di luar cakupan spec ini."
-
-msgid ""
-"Only provide one way to configure software, and expect to always have the "
-"same versions. This is further away from the \"image independent\" contract, "
-"with extra burden: We will need to maintain a curated list of versions, deal "
-"with the differences of the defaults (selinux/apparmor profiles come to mind "
-"as path sensitive for example), and different expectations for operational "
-"teams (\"The code is not where I expect it to be in the image\"). Embracing "
-"difference could even allow deployers to have different expectations for "
-"images, for example: apache+mod_wsgi vs uwsgi standalone or uwsgi + nginx."
-msgstr ""
-"Hanya menyediakan satu cara untuk mengkonfigurasi perangkat lunak, dan "
-"berharap untuk selalu memiliki versi yang sama. Ini lebih jauh dari kontrak "
-"\"image independent\", dengan beban tambahan: Kita perlu mempertahankan "
-"daftar versi yang dikuratori (curated), menangani perbedaan default (profil "
-"selinux/apparmor muncul di pikiran sebagai path sensitif misalnya), dan "
-"harapan yang berbeda untuk tim operasional (\"The code is not where I expect "
-"it to be in the image\"). Merangkul perbedaan bahkan dapat memungkinkan para "
-"deployer untuk memiliki harapan yang berbeda untuk image, misalnya: apache"
-"+mod_wsgi vs uwsgi standalone or uwsgi + nginx."
-
-msgid ""
-"OpenStack metrics: tenants, networks, flavors, floating IPs, quotas, etc"
-msgstr ""
-"Metrik OpenStack: tenants, networks, flavors, floating IPs, quotas, dll"
-
-msgid "OpenStack-Helm 1.0 Requirements"
-msgstr "OpenStack-Helm 1.0 Requirements"
-
-msgid ""
-"OpenStack-Helm currently lacks a centralized mechanism for providing insight "
-"into the performance of the OpenStack services and infrastructure "
-"components. The log formats of the different components in OpenStack-Helm "
-"vary, which makes identifying causes for issues difficult across services.  "
-"To support operational readiness by default, OpenStack-Helm should include "
-"components for logging events in a common format, monitoring metrics at all "
-"levels, alerting and alarms for those metrics, and visualization tools for "
-"querying the logs and metrics in a single pane view."
-msgstr ""
-"OpenStack-Helm saat ini tidak memiliki mekanisme terpusat untuk memberikan "
-"wawasan tentang kinerja layanan OpenStack dan komponen infrastruktur. Format "
-"log dari berbagai komponen di OpenStack-Helm bervariasi, yang membuat "
-"mengidentifikasi penyebab masalah sulit di seluruh layanan. Untuk mendukung "
-"kesiapan operasional secara default, OpenStack-Helm harus menyertakan "
-"komponen untuk mencatat peristiwa dalam format umum, memantau metrik di "
-"semua tingkatan, mengingatkan dan alarm untuk metrik tersebut, dan alat "
-"visualisasi untuk menanyakan log dan metrik dalam tampilan panel tunggal."
-
-msgid ""
-"OpenStack-Helm defines a centralized logging mechanism to provide insight "
-"into the state of the OpenStack services and infrastructure components as "
-"well as underlying Kubernetes platform. Among the requirements for a logging "
-"platform, where log data can come from and where log data need to be "
-"delivered are very variable. To support various logging scenarios, OpenStack-"
-"Helm should provide a flexible mechanism to meet with certain operation "
-"needs. This spec proposes fast and lightweight log forwarder and full "
-"featured log aggregator complementing each other providing a flexible and "
-"reliable solution. Especially, Fluentbit is proposed as a log forwarder and "
-"Fluentd is proposed as a main log aggregator and processor."
-msgstr ""
-"OpenStack-Helm mendefinisikan mekanisme logging terpusat untuk memberikan "
-"wawasan (insight) tentang status layanan OpenStack dan komponen "
-"infrastruktur serta platform Kubernetes yang mendasarinya. Di antara "
-"persyaratan untuk platform logging, dari mana data log dapat berasal dan "
-"dari mana data log harus dikirim sangat bervariasi. Untuk mendukung berbagai "
-"skenario logging, OpenStack-Helm harus menyediakan mekanisme yang fleksibel "
-"untuk memenuhi kebutuhan operasi tertentu. Spesifikasi ini mengusulkan log "
-"forwarder cepat dan ringan dan agregator log berfitur lengkap yang saling "
-"melengkapi memberikan solusi yang fleksibel dan andal. Terutama, Fluentbit "
-"diusulkan sebagai log forwarder dan Fluentd diusulkan sebagai agregator dan "
-"prosesor log utama."
-
-msgid ""
-"OpenStack-Helm documentation will be updated to indicate the usage of the "
-"nginx sidecar."
-msgstr ""
-"Dokumentasi OpenStack-Helm akan diperbarui untuk menunjukkan penggunaan "
-"nginx sidecar."
-
-msgid "OpenStack-Helm for OpenStack services"
-msgstr "OpenStack-Helm untuk layanan OpenStack"
-
-msgid ""
-"OpenStack-Helm has developed a number of conventions around the format and "
-"ordering of charts' `values.yaml` file, in support of both reusable Helm-"
-"Toolkit functions and ease of developer ramp-up.  For 1.0 readiness, "
-"OpenStack-Helm must cement these conventions within a spec, as well as the "
-"ordering of `values.yaml` keys. These conventions must then be gated to "
-"guarantee conformity. The spec in progress can be found here [1]_."
-msgstr ""
-"OpenStack-Helm telah mengembangkan sejumlah konvensi seputar format dan "
-"pemesanan file chart ``values.yaml`, untuk mendukung kedua fungsi Helm-"
-"Toolkit yang dapat digunakan kembali dan kemudahan pengembangan pengembang. "
-"Untuk kesiapan 1.0, OpenStack-Helm harus menambahkan konvensi ini dalam "
-"spesifikasi, serta urutan kunci `values.yaml`. Konvensi ini kemudian harus "
-"terjaga keamanannya untuk menjamin kepatuhan. Spesifikasi yang sedang "
-"berjalan dapat ditemukan di sini [1] _."
-
-msgid ""
-"OpenStack-Helm has undergone rapid development and maturation over its "
-"lifetime, and is nearing the point of real-world readiness.  This spec "
-"details the functionality that must be implemented in OpenStack-Helm for it "
-"to be considered ready for a 1.0 release, as well as for general use."
-msgstr ""
-"OpenStack-Helm telah mengalami perkembangan dan pematangan yang cepat selama "
-"masa hidupnya, dan mendekati titik kesiapan real-world. Spesifikasi ini "
-"merinci fungsionalitas yang harus diimplementasikan di OpenStack-Helm agar "
-"dianggap siap untuk rilis 1.0, serta untuk penggunaan umum."
-
-msgid ""
-"OpenStack-Helm multinode guide includes scripts which are used to specify "
-"overrides and deploy charts."
-msgstr ""
-"Panduan multinode OpenStack-Helm mencakup skrip yang digunakan untuk "
-"menentukan override dan menyebarkan chart."
-
-msgid ""
-"OpenStack-Helm supports a \"bring your own Kubernetes\" paradigm.  Any "
-"particular k8s configuration or feature requirements must be documented."
-msgstr ""
-"OpenStack-Helm mendukung paradigma \"bring your own Kubernetes\". "
-"Konfigurasi k8 tertentu atau persyaratan fitur harus didokumentasikan."
-
-msgid "OpenStack-Helm-Addons for ancillary services"
-msgstr "OpenStack-Helm-Addons untuk layanan tambahan"
-
-msgid "OpenStack-Helm-Infra for supporting services"
-msgstr "OpenStack-Helm-Infra untuk layanan pendukung"
-
-msgid "Operating system"
-msgstr "Operating system"
-
-msgid ""
-"Operators should be able to use Openstack-Helm to deploy containerized "
-"openstack services with a docker registry has authentication turned on."
-msgstr ""
-"Operator harus dapat menggunakan Openstack-Helm untuk menggunakan layanan "
-"openstack containerized dengan registry docker yang telah mengaktifkan "
-"otentikasi."
-
-msgid "Orchestration (heat)"
-msgstr "Orchestration (heat)"
-
-msgid "Organizational auditing needs"
-msgstr "Kebutuhan audit organisasi"
-
-msgid "Other networking services provided by Neutron are:"
-msgstr "Layanan jaringan lain yang disediakan oleh Neutron adalah:"
-
-msgid ""
-"Other services inside Neutron reference stack (L3/DHCP/metadata agents) are "
-"dependent on L2 connectivity agent. Thus, replacing OVS with LB would cause "
-"changes in mentioned services configuration."
-msgstr ""
-"Layanan lain di dalam stack referensi Neutron (L3/DHCP/metadata agents) "
-"bergantung pada agen konektivitas L2. Jadi, mengganti OVS dengan LB akan "
-"menyebabkan perubahan dalam konfigurasi layanan yang disebutkan."
-
-msgid ""
-"Our :ref:`images documentation` documentation claims to be independent of "
-"the image. However, some helm charts hard code paths of binaries, "
-"executables' runtime configurations, etc. Therefore, the image agnostic "
-"promise is broken."
-msgstr ""
-"Dokumentasi kami :ref:`images documentation` mengklaim tidak tergantung dari "
-"image. Namun, beberapa helm menunjukkan jalur kode yang sulit dari binari, "
-"konfigurasi runtime yang dapat dieksekusi, dll. Oleh karena itu, janji "
-"agnostik image rusak."
-
-msgid "Performance Impact"
-msgstr "Dampak Kinerja"
-
-msgid "Pete Birley <pete@port.direct>"
-msgstr "Pete Birley <pete@port.direct>"
-
-msgid "Platform Requirements"
-msgstr "Persyaratan Platform"
-
-msgid "PoC deployments of OpenStack-Helm"
-msgstr "Deployment PoC dari OpenStack-Helm"
-
-msgid "Port numbers for Ceph_Mon and Ceph_Mgr are different from default."
-msgstr "Nomor port untuk Ceph_Mon dan Ceph_Mgr berbeda dari default."
-
-msgid "Pre-pulling images on all nodes"
-msgstr "Pre-pulling image di semua node"
-
-msgid "Prepare Host(s) for OpenStack-Helm deployment"
-msgstr "Mempersiapkan Host untuk penerapan OpenStack-Helm"
-
-msgid "Primary assignee:"
-msgstr "Penugasan utama (primary assignee):"
-
-msgid "Primary assignees:"
-msgstr "Penerima tugas utama (primary assignees):"
-
-msgid "Proactive monitoring of stack traces across all deployed infrastructure"
-msgstr "Pemantauan proaktif stack trace di semua infrastruktur yang digunakan"
-
-msgid "Problem Description"
-msgstr "Deskripsi Masalah"
-
-msgid "Process and Tooling"
-msgstr "Proses dan Tooling"
-
-msgid "Project Specifications"
-msgstr "Spesifikasi Proyek"
-
-msgid ""
-"Prometheus and Grafana meet OpenStack-Helm's monitoring requirements.  The "
-"Prometheus monitoring tool provides the ability to scrape targets for "
-"metrics over HTTP, and it stores these metrics in Prometheus's time-series "
-"database. The monitoring targets can be discovered via static configuration "
-"in Prometheus or through service discovery.  Prometheus includes a querying "
-"language that provides meaningful queries against the metrics gathered and "
-"supports the creation of rules to measure these metrics against for alerting "
-"purposes.  It also supports a wide range of Prometheus exporters for "
-"existing services, including Ceph and OpenStack.  Grafana supports "
-"Prometheus as a data source, and provides the ability to view the metrics "
-"gathered by Prometheus in a single pane dashboard.  Grafana can be "
-"bootstrapped with dashboards for each target scraped, or the dashboards can "
-"be added via Grafana's web interface directly.  To meet OpenStack-Helm's "
-"alerting needs, Alertmanager can be used to interface with Prometheus and "
-"send alerts based on Prometheus rule evaluations."
-msgstr ""
-"Prometheus dan Grafana memenuhi persyaratan pemantauan OpenStack-Helm. Alat "
-"pemantauan Prometheus menyediakan kemampuan untuk mengikis target (scrape "
-"target) untuk metrik melalui HTTP, dan alat ini menyimpan metrik ini dalam "
-"basis data seri waktu Prometheus. Sasaran pemantauan dapat ditemukan melalui "
-"konfigurasi statis di Prometheus atau melalui penemuan layanan. Prometheus "
-"menyertakan bahasa kueri yang menyediakan kueri yang berarti terhadap metrik "
-"yang dikumpulkan dan mendukung pembuatan aturan untuk mengukur metrik ini "
-"untuk keperluan peringatan. Ini juga mendukung berbagai eksportir Prometheus "
-"untuk layanan yang ada, termasuk Ceph dan OpenStack. Grafana mendukung "
-"Prometheus sebagai sumber data, dan menyediakan kemampuan untuk melihat "
-"metrik yang dikumpulkan oleh Prometheus dalam dasbor panel tunggal. Grafana "
-"dapat di-bootstrap dengan dasbor untuk setiap target yang dikorek, atau "
-"dasbor dapat ditambahkan melalui antarmuka web Grafana secara langsung. "
-"Untuk memenuhi kebutuhan peringatan OpenStack-Helm, Alertmanager dapat "
-"digunakan untuk berinteraksi dengan Prometheus dan mengirim peringatan "
-"berdasarkan evaluasi aturan Prometheus."
-
-msgid "Prometheus chart"
-msgstr "Prometheus chart"
-
-msgid "Prometheus exporters"
-msgstr "Prometheus exporters"
-
-msgid "Proper directories mounted to retrieve logs from the node"
-msgstr "Direktori yang tepat dipasang untuk mengambil log dari node"
-
-msgid "Proposed Change"
-msgstr "Usulan Perubahan"
-
-msgid ""
-"Proposes a common approach to software configuration, describing the distro/"
-"image specific differences for applications."
-msgstr ""
-"Mengusulkan pendekatan umum untuk konfigurasi perangkat lunak, menjelaskan "
-"perbedaan specific distro/image untuk aplikasi."
-
-msgid ""
-"Provide the credentials and add the manifest across all charts in OSH and "
-"OSH-infra"
-msgstr ""
-"Berikan kredensial dan tambahkan manifes di semua chart di OSH dan OSH-infra"
-
-msgid "Providing the neutron plugin code."
-msgstr "Memberikan kode plugin neutron."
-
-msgid "Provision of those services should be included inside SDN chart."
-msgstr "Penyediaan layanan tersebut harus dimasukkan dalam chart SDN."
-
-msgid "Put .docker/config.json in docker/kubelet root directory on all nodes"
-msgstr ""
-"Masukkan .docker/config.json di direktori root docker/kubelet di semua node"
-
-msgid "Record OpenStack service behavior and status"
-msgstr "Catat perilaku dan status layanan OpenStack"
-
-msgid "Record compute instance behavior across nodes and services"
-msgstr "Catat perilaku instance komputasi di seluruh node dan layanan"
-
-msgid ""
-"Reference the created secret by adding the ``imagePullSecrets:`` field to "
-"ServiceAccount resource template [2]_ in ``helm-toolkit/snippets/"
-"_kubernetes_pod_rbac_serviceaccount.tpl``. To handle it as optional, the "
-"field is wrapped in a conditional. For example,"
-msgstr ""
-"Referensi rahasia yang dibuat dengan menambahkan field  ``imagePullSecrets:"
-"`` ke templat sumber daya ServiceAccount [2] _ dalam ``helm-toolkit/snippets/"
-"_kubernetes_pod_rbac_serviceaccount.tpl``.  Untuk menanganinya sebagai "
-"opsional, field dikemas dalam kondisi. Sebagai contoh,"
-
-msgid "References"
-msgstr "Referensi"
-
-msgid ""
-"Release notes for the 1.0 release must be prepared, following OpenStack best "
-"practices.  The criteria for future changes that should be included in "
-"release notes in an ongoing fashion must be defined / documented as well."
-msgstr ""
-"Catatan rilis untuk rilis 1.0 harus disiapkan, mengikuti praktik terbaik "
-"OpenStack. Kriteria untuk perubahan di masa depan yang harus dimasukkan "
-"dalam catatan rilis dengan cara yang berkelanjutan harus didefinisikan / "
-"didokumentasikan juga."
-
-msgid ""
-"Releated Specs: 1. OSH logging monitoring and alerting: https://review."
-"openstack.org/#/c/482687/"
-msgstr ""
-"Spesifikasi yang Diresmikan: 1. Pemantauan dan peringatan logging OSH: "
-"https://review.openstack.org/#/c/482687/"
-
-msgid "Result from Steps 2, 3, 4:"
-msgstr "Hasil dari Langkah 2, 3, 4:"
-
-msgid "Results from Step 5, 6, 7:"
-msgstr "Hasil dari Langkah 5, 6, 7:"
-
-msgid "SSH into VM and check it can access the internet"
-msgstr "SSH ke VM dan periksa apakah dapat mengakses internet"
-
-msgid "Sane defaults for log retention and rotation policies"
-msgstr "Sane default untuk penyimpanan retensi dan kebijakan rotasi"
-
-msgid "Script to update and execute: ``020-ingress.sh``"
-msgstr "Skrip untuk update dan menjalankan: ``020-ingress.sh``"
-
-msgid "Script to update and execute: ``030-ceph.sh``"
-msgstr "Skrip untuk update dan menjalankan: ``030-ceph.sh``"
-
-msgid "Script to update and execute: ``030-tenant-ceph.sh``"
-msgstr "Skrip untuk update dan menjalankan: ``030-tenant-ceph.sh``"
-
-msgid "Script to update and execute: ``040-tenant-ceph-ns-activate.sh``"
-msgstr "Skrip untuk update dan menjalankan: ``040-tenant-ceph-ns-activate.sh``"
-
-msgid "Script to update and execute: ``100-glance.sh``"
-msgstr "Skrip untuk update dan menjalankan: ``100-glance.sh``"
-
-msgid "Script to update and execute: ``110-cinder.sh``"
-msgstr "Skrip untuk update dan menjalankan: ``110-cinder.sh``"
-
-msgid "Script to update: ``090-tenant-ceph-radosgateway.sh``"
-msgstr "Skrip untuk update: ``090-tenant-ceph-radosgateway.sh``"
-
-msgid "Security Impact"
-msgstr "Dampak Keamanan"
-
-msgid "See above for documentation requirements."
-msgstr "Lihat di atas untuk persyaratan dokumentasi."
-
-msgid "See above for gating requirements."
-msgstr "Lihat di atas untuk persyaratan gating."
-
-msgid "See above for the list of work items."
-msgstr "Lihat di atas untuk daftar item pekerjaan."
-
-msgid "Setup access to the external network from the development machine"
-msgstr "Atur akses ke jaringan eksternal dari mesin pengembangan"
-
-msgid "Single pane visualization capabilities"
-msgstr "Kemampuan visualisasi panel tunggal"
-
-msgid "Specifications Process"
-msgstr "Spesifikasi Proses"
-
-msgid "Specifications Purpose"
-msgstr "Specifications Purpose (spesifikasi tujuan)"
-
-msgid ""
-"Specifications in this repository represent a consensus on the topics "
-"covered within.  They should be considered a mandate on the path forward "
-"with regards to the content on which they are drafted."
-msgstr ""
-"Spesifikasi dalam repositori ini mewakili konsensus tentang topik yang "
-"dicakup di dalam. Mereka harus dianggap sebagai mandat di jalan ke depan "
-"sehubungan dengan konten yang mereka buat."
-
-msgid "StatefulSets"
-msgstr "StatefulSets"
-
-msgid "Support OCI image registry with authentication turned on"
-msgstr "Mendukung OCI image registry dengan otentikasi dihidupkan"
-
-msgid "Support linux bridge on neutron helm chart"
-msgstr "Mendukung linux bridge pada chart helm neutron"
-
-msgid "TODO - release management spec"
-msgstr "TODO - rilis spesifikasi manajemen"
-
-msgid "Test Steps:"
-msgstr "Langkah uji:"
-
-msgid "Testing"
-msgstr "Pengujian"
-
-msgid ""
-"Testing should include Helm tests for each of the included charts as well as "
-"an integration test in the gate."
-msgstr ""
-"Pengujian harus mencakup tes Helm untuk masing-masing chart termasuk juga "
-"tes integrasi di gate."
-
-msgid ""
-"The LinuxBridge (LB) is Neutron's L2 agent, using linux kernel bridges as "
-"network configuration for VMs. Both OVS and LB are part of Neutron's Modular "
-"Layer 2 (ML2) framework, allowing to simultaneously utilize the variety of "
-"layer 2 networking technologies."
-msgstr ""
-"LinuxBridge (LB) adalah agen L2 Neutron, menggunakan jembatan kernel Linux "
-"sebagai konfigurasi jaringan untuk VM. Baik OVS dan LB adalah bagian dari "
-"kerangka kerja Modular Layer 2 (ML2) Neutron, memungkinkan untuk secara "
-"bersamaan memanfaatkan berbagai teknologi jaringan layer 2."
-
-msgid ""
-"The Neutron reference architecture provides mechanism_drivers OpenVSwitch "
-"(OVS) and linuxbridge (LB) with ML2 core_plugin framework."
-msgstr ""
-"Arsitektur referensi Neutron menyediakan mechanism_drivers OpenVSwitch (OVS) "
-"dan linuxbridge (LB) dengan ML2 core_plugin framework."
-
-msgid ""
-"The OpenStack-Helm Zuulv2 gates were written to allow use outside of "
-"OpenStack-Infra, to quickly set up a Kubernetes cluster, with the adoption "
-"of Zuulv3 underway it is logical to extend this paradigm to the Zuulv3 "
-"Playbooks. This will be driven via a ``Makefile`` that will allow developers "
-"to perform the following actions:"
-msgstr ""
-"Gate OpenStack-Helm Zuulv2 ditulis untuk memungkinkan penggunaan di luar "
-"OpenStack-Infra, untuk dengan cepat membuat kluster Kubernetes, dengan "
-"adopsi Zuulv3 yang sedang berjalan, logis untuk memperluas paradigma ini ke "
-"Playbook Zuulv3. Ini akan didorong melalui ``Makefile`` yang akan "
-"memungkinkan pengembang untuk melakukan tindakan berikut:"
-
-msgid ""
-"The OpenStack-Helm release process will be somewhat orthogonal to the "
-"OpenStack release process, and the differences and relationship between the "
-"two must be documented in a spec.  This will help folks quickly understand "
-"why OpenStack-Helm is a Release-Independent project from an OpenStack "
-"perspective."
-msgstr ""
-"Proses rilis OpenStack-Helm akan sedikit ortogonal untuk proses rilis "
-"OpenStack, dan perbedaan dan hubungan antara keduanya harus didokumentasikan "
-"dalam sebuah spec. Ini akan membantu orang dengan cepat memahami mengapa "
-"OpenStack-Helm adalah proyek Release-Independent dari perspektif OpenStack."
-
-msgid ""
-"The ``profiles`` yaml files (for example ``centos_7``, ``opensuse_15``) will "
-"be provided in each chart's ``example_values/`` directory. This folder will "
-"be masked to helm through a helmignore file. Its content is only for user "
-"consumption, not for inclusion in helm charts through the File directive. In "
-"other words, this is a user interface given for convenience merely using the "
-"abilities of the existing helm charts."
-msgstr ""
-"File ``profile`` yaml (misalnya ``centos_7``, ``opensuse_15``) akan "
-"disediakan di setiap direktori ``example_values/`` chart. Folder ini akan "
-"ditutup untuk dikunci melalui file helmignore. Kontennya hanya untuk "
-"konsumsi pengguna, bukan untuk dimasukkan dalam helm chart melalui arahan "
-"File. Dengan kata lain, ini adalah antarmuka pengguna yang diberikan untuk "
-"kenyamanan hanya menggunakan kemampuan helm chart yang ada."
-
-msgid ""
-"The above chart must include sensible configuration values to make the "
-"logging platform usable by default. These include: proper input "
-"configurations for both Fluentbit and Fluentd, proper output configurations "
-"for both Fluentbit and Fluentd, proper metadata and formats applied to the "
-"logs via Fluentd."
-msgstr ""
-"Bagan di atas harus menyertakan nilai konfigurasi yang masuk akal untuk "
-"membuat platform logging dapat digunakan secara default. Ini termasuk: "
-"konfigurasi input yang tepat untuk Fluentbit dan Fluentd, konfigurasi output "
-"yang tepat untuk Fluentbit dan Fluentd, metadata yang tepat dan format yang "
-"diterapkan pada log melalui Fluentd."
-
-msgid ""
-"The alternative is to provide no organization layout for charts across all "
-"openstack-helm repositories."
-msgstr ""
-"Alternatifnya adalah tidak menyediakan tata letak organisasi untuk chart di "
-"semua repositori openstack-helm."
-
-msgid ""
-"The alternative would be to continue supporting the current bash driven "
-"containerized KubeADM and Kubelet approach, though this has the following "
-"issues:"
-msgstr ""
-"Alternatifnya adalah untuk terus mendukung pendekatan Kubelet  dan bash "
-"driven containerized KubeADM saat ini, meskipun ini memiliki masalah sebagai "
-"berikut:"
-
-msgid ""
-"The bash scripts are largely undocumented and have grown to the point where "
-"they are very hard for a new developer to work on."
-msgstr ""
-"Script bash sebagian besar tidak berdokumen dan telah berkembang ke titik di "
-"mana mereka sangat sulit untuk dikembangkan oleh pengembang baru."
-
-msgid ""
-"The code can be supplied as modified neutron server image, or plugin can be "
-"mounted to original image. The :code:`manifests` section in :code:`neutron/"
-"values.yaml` should be enabled for below components:"
-msgstr ""
-"Kode dapat diberikan sebagai image server neutron yang dimodifikasi, atau "
-"plugin dapat dipasang ke image asli. Bagian :code:`manifests` dalam  :code:"
-"`neutron/values.yaml` harus diaktifkan untuk komponen di bawah ini:"
-
-msgid ""
-"The containerized Kubelet cannot survive a restart, as it does not setup "
-"mounts correctly."
-msgstr ""
-"Kubelet containerized tidak dapat selamat dari restart, karena ia tidak "
-"memasang mount dengan benar."
-
-msgid ""
-"The credentials for the registry could be exposed by running the kubectl "
-"command: kubectl get secret <secret-name> --output=\"jsonpath={.data.\\."
-"dockerconfigjson}\" | base64 --decode"
-msgstr ""
-"Kredensial untuk registri dapat diekspos dengan menjalankan perintah "
-"kubectl: kubectl get secret <secret-name> --output=\"jsonpath={.data.\\."
-"dockerconfigjson}\" | base64 --decode"
-
-msgid ""
-"The default ``values.yaml`` need to expose those abilities, by adding a new "
-"series of keys/values to add the necessary features."
-msgstr ""
-"Default ``values.yaml`` perlu mengekspos kemampuan itu, dengan menambahkan "
-"serangkaian keys/values baru untuk menambahkan fitur yang diperlukan."
-
-msgid "The detailed proposes change are described as following:"
-msgstr "Usulan perubahan yang rinci dijelaskan sebagai berikut:"
-
-msgid ""
-"The developer documentation in OpenStack-Helm should be updated to guide key "
-"ordering on value files."
-msgstr ""
-"Dokumentasi pengembang di OpenStack-Helm harus diperbarui untuk memandu "
-"pengurutan kunci pada file nilai."
-
-msgid ""
-"The developer documentation in OpenStack-Helm should be updated to match the "
-"gated developer deploy process."
-msgstr ""
-"Dokumentasi pengembang di OpenStack-Helm harus diperbarui agar sesuai dengan "
-"proses penerapan pengembang yang terjaga keamanannya."
-
-msgid "The existing schema for images is the following:"
-msgstr "Skema yang ada untuk image adalah sebagai berikut:"
-
-msgid ""
-"The following work items need to be completed for this Specification to be "
-"implemented."
-msgstr ""
-"Item pekerjaan berikut ini perlu diselesaikan agar Spesifikasi ini dapat "
-"diimplementasikan."
-
-msgid ""
-"The following work items need to be completed for this specification to be "
-"implemented."
-msgstr ""
-"Item pekerjaan berikut ini perlu diselesaikan agar spesifikasi ini dapat "
-"diimplementasikan."
-
-msgid ""
-"The last thing to be considered is VM network virtualization. What engine "
-"does SDN use? It is OpenVSwitch, Linux Bridges or l3 routing (no l2 "
-"connectivity). If SDN is using the OpenVSwitch, it can take advantage of "
-"existing OVS daemonsets. Any modification that would be required to OVS "
-"manifests can be included in base Neutron chart as a configurable option. In "
-"that way, the features of OVS can be shared between different SDNs. When "
-"using the OVS, default Neutron L2 agent should be disabled, but OVS-DB and "
-"OVS-vswitchd can be left enabled."
-msgstr ""
-"Hal terakhir yang harus dipertimbangkan adalah VM network virtualization. "
-"Mesin apa yang SDN gunakan? Ini adalah OpenVSwitch, Linux Bridges atau l3 "
-"routing (tanpa konektivitas l2). Jika SDN menggunakan OpenVSwitch, ia dapat "
-"memanfaatkan daemonset OVS yang ada. Setiap modifikasi yang akan diperlukan "
-"untuk manifes OVS dapat dimasukkan dalam chart Neutron dasar sebagai opsi "
-"yang dapat dikonfigurasi. Dengan cara itu, fitur OVS dapat dibagi antara SDN "
-"yang berbeda. Saat menggunakan OVS, agen Neutron L2 default harus "
-"dinonaktifkan, tetapi OVS-DB dan OVS-vswitchd dapat dibiarkan aktif."
-
-msgid ""
-"The monolithic Ceph chart does not allow for following Ceph upgrade best "
-"practices, namely to upgrade Mons, OSDs, and client services in that order. "
-"The Ceph chart must therefore be split into at least three charts (one for "
-"each of the above upgrade phases) prior to 1.0 to ensure smooth in-place "
-"upgradability."
-msgstr ""
-"Chart Ceph monolitik tidak memungkinkan untuk mengikuti praktik terbaik "
-"upgrade Ceph, yaitu untuk upgrade Mons, OSD, dan layanan klien dalam urutan "
-"itu. Oleh karena itu, Ceph chart harus dibagi menjadi setidaknya tiga chart "
-"(satu untuk masing-masing fase peningkatan di atas) sebelum 1.0 untuk "
-"memastikan kelancaran upgrade in-place."
-
-msgid ""
-"The move to Zuulv3 native operation of the OpenStack-Helm gates mean there "
-"would be no code reuse between the gate and developer environments, so "
-"supporting the existing code for Zuulv2 will incur significant tech-debt."
-msgstr ""
-"Perpindahan ke operasi asli Zuulv3 dari gate OpenStack-Helm berarti tidak "
-"akan ada kode yang digunakan kembali antara gate dan lingkungan pengembang, "
-"sehingga mendukung kode yang ada untuk Zuulv2 akan menimbulkan tech-debt "
-"yang signifikan."
-
-msgid ""
-"The option ``enabled:`` under ``auth:`` and the manifest ``secret_registry:"
-"`` provide the ability for operator to determine whether they would like to "
-"have secrets generated and passed to kubernetes for pulling images."
-msgstr ""
-"Opsi ``enabled:`` di bawah ``auth:`` dan manifes ``secret_registry:`` "
-"memberikan kemampuan bagi operator untuk menentukan apakah mereka ingin "
-"memiliki rahasia yang dihasilkan dan diteruskan ke kubernetes untuk menarik "
-"image."
-
-msgid ""
-"The performance aspect of these point are restricted to deployment, and have "
-"no performance impact on operations."
-msgstr ""
-"Aspek kinerja point ini dibatasi untuk penggunaan, dan tidak memiliki dampak "
-"kinerja pada operasi."
-
-msgid "The proposal includes the following:"
-msgstr "Proposal tersebut meliputi:"
-
-msgid "The proposed requirements for a 1.0 release are as follows:"
-msgstr "Persyaratan yang diusulkan untuk rilis 1.0 adalah sebagai berikut:"
-
-msgid ""
-"The proposes change would be to add in :code:`neutron/values.yaml` new "
-"section with boolean values describing which Neutron's Kubernetes resources "
-"should be enabled:"
-msgstr ""
-"Perubahan yang diajukan adalah menambahkan :code:`neutron/values.yaml` "
-"bagian baru dengan nilai boolean yang menggambarkan sumber daya Kubernet "
-"Neutron mana yang harus diaktifkan:"
-
-msgid "The requirements for a logging collector/aggregator include:"
-msgstr "Persyaratan untuk kolektor/agregator logging meliputi:"
-
-msgid "The requirements for a logging platform include:"
-msgstr "Persyaratan untuk platform logging meliputi:"
-
-msgid "The requirements for a monitoring platform include:"
-msgstr "Persyaratan untuk platform pemantauan meliputi:"
-
-msgid ""
-"The secret would not be created with the default option ``enabled: false`` "
-"and ``secret_registry: true``. To enable secret creation, operator should "
-"override ``enabled:`` to true. The above example shows the default "
-"credentials, operator should override the ``username:`` and ``password:`` "
-"under ``auth:`` section to provide their own credentials."
-msgstr ""
-"Rahasia tidak akan dibuat dengan opsi default ``enabled: false``  dan "
-"``secret_registry: true``. Untuk mengaktifkan pembuatan rahasia, operator "
-"harus mengganti ``enabled:`` menjadi true. Contoh di atas menunjukkan "
-"kredensial default, operator harus mengganti  ``username:`` and ``password:"
-"``  di bawah bagian ``auth:`` untuk memberikan kredensial mereka sendiri."
-
-msgid ""
-"The testing will be performed by the OpenStack-Helm gate to demonstrate the "
-"sidecar container correctly routes traffic to the correct services."
-msgstr ""
-"Pengujian akan dilakukan oleh gate OpenStack-Helm untuk mendemonstrasikan "
-"sidecar container dengan benar mengarahkan lalu lintas ke layanan yang benar."
-
-msgid ""
-"The top-level keys are based on the organizational keys common to all charts "
-"in the openstack-helm repositories.  The top-level keys are strictly ordered "
-"according to function, which creates a common organization pattern between "
-"all charts."
-msgstr ""
-"Top-level keys didasarkan pada kunci organisasi yang umum untuk semua chart "
-"di repositori openstack-helm.  Top-level keys diatur secara ketat sesuai "
-"dengan fungsinya, yang menciptakan pola organisasi yang sama di antara semua "
-"chart."
-
-msgid ""
-"Then, add manifest ``secret-registry.yaml`` in ``templates/`` to leverage "
-"the function that will be added in helm-toolkit to create the secret. For "
-"example:"
-msgstr ""
-"Kemudian, tambahkan manifes ``secret-registry.yaml`` di ``templates/`` untuk "
-"meningkatkan fungsi yang akan ditambahkan dalam helm-toolkit untuk membuat "
-"rahasia. Sebagai contoh:"
-
-msgid ""
-"Then, inside Kubernetes manifests, add global if statement, deciding if "
-"given manifest should be declared on Kubernetes API, for example :code:"
-"`neutron/templates/daemonset-ovs-agent.yaml`:"
-msgstr ""
-"Kemudian, di dalam manifes Kubernetes, tambahkan global if statement, "
-"putuskan jika manifes yang diberikan harus dideklarasikan pada API "
-"Kubernetes, misalnya :code:`neutron/templates/daemonset-ovs-agent.yaml`:"
-
-msgid ""
-"There is no significant performance impact as the traffic will be locally "
-"routed (via 127.0.0.1) and may potentially improve performance for services "
-"whose native TLS handling is inefficient."
-msgstr ""
-"Tidak ada dampak kinerja yang signifikan karena lalu lintas akan dirutekan "
-"secara lokal (melalui 127.0.0.1) dan berpotensi meningkatkan kinerja untuk "
-"layanan yang penanganan TLS native tidak efisien."
-
-msgid ""
-"There will be no security impact, as it will deploy the charts in OpenStack-"
-"Helm[-infra/-addons] upon a reference KubeADM administered cluster."
-msgstr ""
-"Tidak akan ada dampak keamanan, karena akan menyebarkan grafik di OpenStack-"
-"Helm[-infra/-addons] pada cluster yang dikelola KubeADM referensi"
-
-msgid "This Ceph cluster will be used by Cinder and Glance as storage backend."
-msgstr ""
-"Cluster Ceph ini akan digunakan oleh Cinder dan Glance sebagai backend "
-"penyimpanan."
-
-msgid ""
-"This Ceph cluster will be used for k8s RBD storage (pvc). This can be used "
-"by entire Kubernetes cluster."
-msgstr ""
-"Cluster Ceph ini akan digunakan k8s RBD storage (pvc). Ini dapat digunakan "
-"oleh seluruh cluster Kubernetes."
-
-msgid "This approach:"
-msgstr "Pendekatan ini:"
-
-msgid ""
-"This deployment process will be gated, to ensure that the development the "
-"environment is consistently working against ``master`` for the OpenStack-"
-"Helm repositories."
-msgstr ""
-"Proses deployment ini akan terjaga keamanannya, untuk memastikan bahwa "
-"pengembangan lingkungan bekerja secara konsisten terhadap ``master`` untuk "
-"repositori OpenStack-Helm."
-
-msgid ""
-"This enhances the system's security design by allowing pods with services "
-"that cannot natively manage TLS to secure the traffic to the service pod."
-msgstr ""
-"Ini meningkatkan desain keamanan sistem dengan memungkinkan pod dengan "
-"layanan yang tidak dapat mengelola TLS untuk mengamankan lalu lintas ke pod "
-"layanan."
-
-msgid "This feature will not affect the performance of OpenStack-Helm."
-msgstr "Fitur ini tidak akan mempengaruhi kinerja OpenStack-Helm."
-
-msgid ""
-"This guide shows how to setup multiple Ceph clusters. One Ceph cluster will "
-"be used for k8s RBD storage and while other Ceph cluster will be for tenant "
-"facing storage backend for Cinder and Glance."
-msgstr ""
-"Panduan ini menunjukkan cara mengatur multiple cluster Ceph. Satu cluster "
-"Ceph akan digunakan untuk penyimpanan RBD k8s dan sementara cluster Ceph "
-"lainnya akan untuk penyewa menghadapi backend penyimpanan untuk Cinder dan "
-"Glance."
-
-msgid ""
-"This spec describes a point-in-time readiness for OpenStack-Helm 1.0, after "
-"which it will be for historical reference only."
-msgstr ""
-"Spesifikasi ini menggambarkan kesiapan point-in-time untuk OpenStack-Helm "
-"1.0, setelah itu hanya untuk referensi sejarah."
-
-msgid ""
-"This spec describes a wide variety of self-contained work efforts, which "
-"will be implemented individually by the whole OpenStack-Helm team."
-msgstr ""
-"Spesifikasi ini menjelaskan berbagai upaya kerja mandiri, yang akan "
-"dilaksanakan secara individual oleh seluruh tim OpenStack-Helm."
-
-msgid ""
-"This spec lays out the criteria for a stable and reliable 1.0 release, which "
-"can serve as the basis for real-world use as well as ongoing development. "
-"The alternative approaches would be to either iterate indefinitely without "
-"defining a 1.0 release, which would fail to signal to operators the point at "
-"which the platform is ready for real-world use; or, to define a 1.0 release "
-"which fails to satisfy key features which real-world operators need."
-msgstr ""
-"Spesifikasi ini menjabarkan kriteria untuk rilis 1.0 yang stabil dan andal, "
-"yang dapat berfungsi sebagai dasar untuk penggunaan di real-world serta "
-"pengembangan yang berkelanjutan. Pendekatan alternatif adalah untuk "
-"melakukan iterate tanpa batas tanpa mendefinisikan rilis 1.0, yang akan "
-"gagal memberi sinyal kepada operator, titik di mana platform siap untuk "
-"penggunaan real-world; atau, untuk menentukan rilis 1.0 yang gagal memenuhi "
-"fitur utama yang dibutuhkan operator real-world."
-
-msgid ""
-"This spec will be worked helm chart by helm chart, starting with keystone."
-msgstr ""
-"Spesifikasi ini akan dikerjakan helm chart dengan helm chart, dimulai dengan "
-"keystone."
-
-msgid ""
-"This specification also proposes to restrict the addition of any new top-"
-"level keys in charts across all OpenStack-Helm repositories, in order to "
-"maintain the common structure the ordering creates.  The addition of a new "
-"top-level key shall be agreed upon by the OpenStack-Helm team on a case-by-"
-"case basis.  The addition of any new top-level keys should be documented, "
-"and this specification shall be amended to account for any added keys."
-msgstr ""
-"Spesifikasi ini juga mengusulkan untuk membatasi penambahan top-level keys "
-"baru dalam chart di semua repositori OpenStack-Helm, untuk menjaga struktur "
-"umum yang dibuat oleh pengurutan. Penambahan top-level key yang baru harus "
-"disetujui oleh tim OpenStack-Helm berdasarkan kasus per kasus. Penambahan "
-"top-level key yang baru harus didokumentasikan, dan spesifikasi ini harus "
-"diubah untuk memperhitungkan setiap kunci yang ditambahkan."
-
-msgid ""
-"This specification proposes defining entries in the values.yaml file into "
-"two categories: top-level keys, and their children (sub-level) keys."
-msgstr ""
-"Spesifikasi ini mengusulkan pendefinisian entri dalam file values.yaml ke "
-"dalam dua kategori: top-level keys, dan their children (sub-level) keys."
-
-msgid ""
-"This specification proposes introducing a uniform values.yaml structure "
-"across all charts in openstack-helm, openstack-helm-infra, and openstack-"
-"helm-addons, with the goal of reducing the complexities of working across "
-"multiple charts and reducing the effort for creating new charts."
-msgstr ""
-"Spesifikasi ini mengusulkan untuk memperkenalkan nilai yang seragam. "
-"Struktur yaml di semua chart di openstack-helm, openstack-helm-infra, dan "
-"openstack-helm-addons, dengan tujuan mengurangi kompleksitas bekerja di "
-"berbagai chart dan mengurangi upaya untuk menciptakan chart yang baru."
-
-msgid ""
-"This specification proposes to add a nginx sidecar container to the pod for "
-"service that requires the tls offloading. The nginx can be used to handle "
-"the TLS offoading and terminate the TLS connection, and routes the traffic "
-"to the service via localhost (127.0.0.1)."
-msgstr ""
-"Spesifikasi ini mengusulkan untuk menambahkan kontainer sidecar nginx ke pod "
-"untuk layanan yang memerlukan pembongkaran tls. Nginx dapat digunakan untuk "
-"menangani pemutusan TLS dan mengakhiri koneksi TLS, dan merutekan (route) "
-"lalu lintas ke layanan melalui localhost (127.0.0.1)."
-
-msgid ""
-"This specification will address enablement of LinuxBridge network "
-"virtualization for OpenStack Helm (OSH). LinuxBridge is second available "
-"networking technology in Neutron's reference architecture. The first one is "
-"OVS, that is already implemented in OSH."
-msgstr ""
-"Spesifikasi ini akan membahas pemberlakuan virtualisasi jaringan LinuxBridge "
-"untuk OpenStack Helm (OSH). LinuxBridge adalah teknologi jaringan kedua yang "
-"tersedia dalam arsitektur referensi Neutron. Yang pertama adalah OVS, yang "
-"sudah diimplementasikan dalam OSH."
-
-msgid "Time-series database for collected metrics"
-msgstr "Database time-serie untuk metrik yang dikumpulkan"
-
-msgid "Time-series database for logs collected"
-msgstr "Database time-series untuk log dikumpulkan"
-
-msgid ""
-"To be able to install Neutron with multiple possible SDNs as networking "
-"plugin, Neutron chart should be modified to enable installation of base "
-"services with decomposable approach. This means that operator can define "
-"which components from base Neutron chart should be installed, and which "
-"should not. This plus proper configuration of Neutron chart would enable "
-"operator to flexibly provision OpenStack with chosen SDN."
-msgstr ""
-"Untuk dapat menginstal Neutron dengan beberapa kemungkinan SDN sebagai "
-"plugin jaringan, chart Neutron harus dimodifikasi untuk memungkinkan "
-"instalasi layanan dasar dengan pendekatan yang dapat didekomposisi. Ini "
-"berarti bahwa operator dapat menentukan komponen mana dari chart Neutron "
-"dasar yang harus dipasang, dan mana yang tidak. Konfigurasi chart Neutron "
-"plus yang tepat ini akan memungkinkan operator untuk secara fleksibel "
-"menyediakan OpenStack dengan SDN yang dipilih."
-
-msgid ""
-"To be able to pull images from an OCI image registry which has the "
-"authentication turned on, kubernetes needs credentials. For each chart, a "
-"new ``endpoints:`` entry could be added in ``values.yaml`` to provide image "
-"credentials, a secret needs to be generated to hold the credentials and the "
-"``imagePullSecrets:`` field should be added in each service account to "
-"specify which secret should be used to get the credentials from when pulling "
-"images by kubelet."
-msgstr ""
-"Untuk dapat menarik image dari registri image OCI yang otentikasi "
-"dihidupkan, kubernetes memerlukan kredensial. Untuk setiap chart, entri "
-"``endpoints:`` baru dapat ditambahkan dalam ``values.yaml`` untuk memberikan "
-"kredensial image, rahasia perlu dibuat untuk memegang kredensial dan field "
-"``imagePullSecrets:`` harus berupa ditambahkan di setiap akun layanan untuk "
-"menentukan rahasia mana yang harus digunakan untuk mendapatkan kredensial "
-"mulai saat menarik image dengan kubelet."
-
-msgid ""
-"To enable new SDN solution, there should be separate chart created, which "
-"would handle the deployment of service, setting up the database and any "
-"related networking functionality that SDN is providing."
-msgstr ""
-"Untuk mengaktifkan solusi SDN baru, harus ada chart terpisah yang dibuat, "
-"yang akan menangani penyebaran layanan, pengaturan basis data dan segala "
-"fungsi jaringan terkait yang disediakan oleh SDN."
-
-msgid ""
-"To facilitate effective collaboration and communication across the OpenStack-"
-"Helm community team, work items for the enhancements above will be captured "
-"in Storyboard.  Therefore, migration from Launchpad to Storyboard must be "
-"accomplished prior to the 1.0 release.  Going forward, Storyboard will be "
-"leveraged as a tool to collaboratively define and communicate the OpenStack-"
-"Helm roadmap."
-msgstr ""
-"Untuk memfasilitasi kolaborasi dan komunikasi yang efektif di seluruh tim "
-"komunitas OpenStack-Helm, item pekerjaan untuk peningkatan di atas akan "
-"ditangkap di Storyboard. Oleh karena itu, migrasi dari Launchpad ke "
-"Storyboard harus diselesaikan sebelum rilis 1.0. Ke depan, Storyboard akan "
-"dimanfaatkan sebagai alat untuk secara kolaboratif mendefinisikan dan "
-"mengkomunikasikan roadmap OpenStack-Helm."
-
-msgid ""
-"To minimize the performance impacts, the following should be considered:"
-msgstr ""
-"Untuk meminimalkan dampak kinerja, hal-hal berikut harus dipertimbangkan:"
-
-msgid ""
-"To successfully enforce the ordering defined here, our gates need a method "
-"for validating the ordering and the schema of all values.yaml files.  "
-"Without such a mechanism, the overhead associated with properly reviewing "
-"and validating any changes to the structure will be substantial.  A tool, "
-"such as yamllint, would provide this functionality and remove the need to "
-"write a custom validation tool"
-msgstr ""
-"Untuk berhasil menegakkan pengurutan yang ditentukan di sini, gate kami "
-"memerlukan metode untuk memvalidasi pengurutan dan skema semua file values."
-"yaml. Tanpa mekanisme seperti itu, overhead yang terkait dengan meninjau dan "
-"memvalidasi setiap perubahan pada struktur akan menjadi substansial. Alat, "
-"seperti yamllint, akan menyediakan fungsi ini dan menghapus kebutuhan untuk "
-"menulis alat validasi kustom."
-
-msgid "Top-level keys are placed in this order:"
-msgstr "Top-level keys ditempatkan dalam urutan ini:"
-
-msgid "Topic: osh-1.0-requirements_"
-msgstr "Topic: osh-1.0-requirements_"
-
-msgid "Trigger alerts when desired replicas fall below required number"
-msgstr ""
-"Peringatan pemicu ketika replika yang diinginkan berada di bawah angka yang "
-"dibutuhkan"
-
-msgid "Trigger alerts when services become unavailable or unresponsive"
-msgstr ""
-"Pemicu peringatan ketika layanan menjadi tidak tersedia atau tidak responsif"
-
-msgid "Under storage: mon directory have been updated."
-msgstr "Di bawah penyimpanan: direktori mon telah diperbarui."
-
-msgid ""
-"Under storageclass section, values for following have been updated: "
-"ceph_configmap_name, admin_secret_name, admin_secret_namespace, "
-"user_secret_name"
-msgstr ""
-"Di bawah bagian storageclass, nilai untuk yang berikut telah diperbarui: "
-"ceph_configmap_name, admin_secret_name, admin_secret_namespace, "
-"user_secret_name"
-
-msgid ""
-"Update ``helm toolkit`` to provide snippet to create the nginx sidecar "
-"container for the services that require it."
-msgstr ""
-"Perbarui ``helm toolkit`` untuk memberikan cuplikan untuk membuat nginx "
-"sidecar container  untuk layanan yang membutuhkannya."
-
-msgid ""
-"Update helm-toolkit serviceaccount template to pass the secret in a "
-"conditional"
-msgstr ""
-"Update templat akun layanan helm-toolkit untuk memberikan rahasia secara "
-"bersyarat"
-
-msgid ""
-"Update helm-toolkit to provide manifest to create secret for registry "
-"authentication"
-msgstr ""
-"Update helm-toolkit untuk menyediakan manifes untuk membuat rahasia untuk "
-"otentikasi registri"
-
-msgid "Update of Developer Documentation"
-msgstr "Update Dokumentasi Pengembang"
-
-msgid ""
-"Update of Makefile for OpenStack-Helm-Infra to allow modular deployment of "
-"components"
-msgstr ""
-"Update Makefile untuk OpenStack-Helm-Infra sehingga memungkinkan penempatan "
-"komponen secara modular"
-
-msgid "Update of developer documentation"
-msgstr "Update dokumentasi pengembang"
-
-msgid "Update relevant Documentation."
-msgstr "Update Dokumentasi yang relevan."
-
-msgid "Update script as following:"
-msgstr "Update skrip sebagai berikut:"
-
-msgid "Update script overrides as following:"
-msgstr "Update override skrip sebagai berikut:"
-
-msgid "Update script to include namespace ``tenant-ceph`` as shown below."
-msgstr ""
-"Update skrip untuk memasukkan namespace ``tenant-ceph`` seperti yang "
-"ditunjukkan di bawah ini."
-
-msgid "Update script with following overrides:"
-msgstr "Update skrip dengan override berikut:"
-
-msgid "Update script's override section with following:"
-msgstr "Update bagian override skrip dengan yang berikut:"
-
-msgid "Update service charts to use the updated ``helm toolkit``."
-msgstr ""
-"Perbarui chart layanan untuk menggunakan yang diperbarui ``helm toolkit``."
-
-msgid "Use Cases"
-msgstr "Use Case"
-
-msgid "Use case"
-msgstr "Use case"
-
-msgid "Use cases"
-msgstr "Gunakan kasus"
-
-msgid ""
-"Use default overrides and execute following scripts as per OSH guide steps:"
-msgstr ""
-"Gunakan override default dan jalankan skrip berikut sesuai langkah panduan "
-"OSH:"
-
-msgid "VM networking performance would be dependent of SDN used."
-msgstr "Kinerja jaringan VM akan tergantung pada SDN yang digunakan."
-
-msgid ""
-"VM networking performance would be dependent on linux bridge implementation."
-msgstr "Kinerja jaringan VM akan tergantung pada implementasi jembatan linux."
-
-msgid "Values File Ordering"
-msgstr "Nilai Pengurutan File"
-
-msgid ""
-"Version requirements for the following must be documented and maintained:"
-msgstr ""
-"Persyaratan versi untuk yang berikut ini harus didokumentasikan dan "
-"dipelihara:"
-
-msgid ""
-"Visualize logged events to determine if an event is recurring or an outlier"
-msgstr ""
-"Visualisasikan event yang dicatat untuk menentukan apakah suatu event "
-"berulang atau outlier"
-
-msgid ""
-"Visualize performance to identify trends in traffic or utilization over time"
-msgstr ""
-"Visualisasikan kinerja untuk mengidentifikasi tren lalu lintas atau "
-"pemanfaatan seiring waktu"
-
-msgid "We are disabling rbd and cephfs provisioners."
-msgstr "Kami menonaktifkan provisioner rbd dan cephfs."
-
-msgid ""
-"We need to adapt all the helm charts to remove the hard-coded bits, be image "
-"agnostic, to allow users to bring their own images."
-msgstr ""
-"Kita perlu mengadaptasi semua bagan helm untuk menghapus bit yang dikodekan, "
-"menjadi agnostik image, untuk memungkinkan pengguna membawa image mereka "
-"sendiri."
-
-msgid "Web UI (horizon)"
-msgstr "Web UI (horizon)"
-
-msgid ""
-"When possible, ``values_overrides/`` will refer to existing ``helm-toolkit`` "
-"functions to avoid repeating ourselves."
-msgstr ""
-"Jika memungkinkan, ``values_overrides/``  akan merujuk ke fungsi ``helm-"
-"toolkit`` yang ada untuk menghindari pengulangan diri."
-
-msgid "Work Items"
-msgstr "Work Items"
-
-msgid ""
-"Work is underway to refactor common manifest patterns into reusable snippets "
-"in Helm-Toolkit.  The following manifests have yet to be combined:"
-msgstr ""
-"Pekerjaan sedang dilakukan untuk memperbaiki pola manifes umum menjadi "
-"potongan yang dapat digunakan kembali di Helm-Toolkit. Manifes berikut belum "
-"digabungkan:"
-
-msgid "Worker Deployments"
-msgstr "Worker Deployments"
-
-msgid "``040-ceph-ns-activate.sh``"
-msgstr "``040-ceph-ns-activate.sh``"
-
-msgid "``050-mariadb.sh``"
-msgstr "``050-mariadb.sh``"
-
-msgid "``060-rabbitmq.sh``"
-msgstr "``060-rabbitmq.sh``"
-
-msgid "``070-memcached.sh``"
-msgstr "``070-memcached.sh``"
-
-msgid "``080-keystone.sh``"
-msgstr "``080-keystone.sh``"
-
-msgid "``Ceph ConfigMaps``"
-msgstr "``Ceph ConfigMaps``"
-
-msgid "``Ceph Pods``"
-msgstr "``Ceph Pods``"
-
-msgid "``Ceph Status``"
-msgstr "``Ceph Status``"
-
-msgid "``Ceph endpoints``"
-msgstr "``Ceph endpoints``"
-
-msgid "``Ceph for RBD related labels:``"
-msgstr "``Ceph for RBD related labels:``"
-
-msgid "``Ceph for Tenant related labels:``"
-msgstr "``Ceph for Tenant related labels:``"
-
-msgid "``Ceph secrets``"
-msgstr "``Ceph secrets``"
-
-msgid "``Ceph services``"
-msgstr "``Ceph services``"
-
-msgid "``Openstack PV list``"
-msgstr "``Openstack PV list``"
-
-msgid "``Openstack Pods:``"
-msgstr "``Openstack Pods:``"
-
-msgid "``Openstack endpoints``"
-msgstr "``Openstack endpoints``"
-
-msgid "``Openstack secrets``"
-msgstr "``Openstack secrets``"
-
-msgid "``Openstack services``"
-msgstr "``Openstack services``"
-
-msgid "``Storage on node1, node2, node3:``"
-msgstr "``Storage on node1, node2, node3:``"
-
-msgid "``Storage on node4, node5, node6:``"
-msgstr "``Storage on node4, node5, node6:``"
-
-msgid "``ceph-mon-etc (ceph.conf)``"
-msgstr "``ceph-mon-etc (ceph.conf)``"
-
-msgid ""
-"``cephfs_provisioner: false`` and ``provision_storage_class: false`` are set "
-"to false to disable cephfs. ``deployment_mds: false`` is set to disable ceph-"
-"mds"
-msgstr ""
-"``cephfs_provisioner: false`` dan ``provision_storage_class: false`` disetel "
-"ke false untuk menonaktifkan cephfs. ``deployment_mds: false`` diatur untuk "
-"menonaktifkan ceph-mds."
-
-msgid "``for CHART in ceph-mon ceph-osd ceph-client; do``"
-msgstr "``for CHART in ceph-mon ceph-osd ceph-client; do``"
-
-msgid ""
-"``k8s node list with labels`` After applying above labels, node labels "
-"should look like following."
-msgstr ""
-"``k8s node list with labels`` Setelah menerapkan label di atas, label node "
-"akan terlihat seperti berikut."
-
-msgid "``k8s storageclass``"
-msgstr "``k8s storageclass``"
-
-msgid "``netstat ceph mon port``"
-msgstr "``netstat ceph mon port``"
-
-msgid "`values.yaml` changes"
-msgstr "`values.yaml` changes"
-
-msgid "bootstrap * sub-keys (alphabetical order)"
-msgstr "bootstrap * sub-keys (sesuai abjad)"
-
-msgid "ceph"
-msgstr "ceph"
-
-msgid "conf * sub-keys (up-to-chart-developer)"
-msgstr "conf * sub-keys (up-to-chart-developer)"
-
-msgid "dependencies * sub-keys (alphabetical order)"
-msgstr "dependencies * sub-keys (sesuai abjad)"
-
-msgid ""
-"diagram link: https://github.com/sktelecom-oslab/docs/blob/master/images/"
-"fluentbit-fluentd-diagram.png"
-msgstr ""
-"diagram link: https://github.com/sktelecom-oslab/docs/blob/master/images/"
-"fluentbit-fluentd-diagram.png"
-
-msgid "endpoints * sub-keys (alphabetical order)"
-msgstr "endpoints * sub-keys (sesuai abjad)"
-
-msgid "etcd"
-msgstr "etcd"
-
-msgid "evrardjp"
-msgstr "evrardjp"
-
-msgid "fluentbit-fluentd logging architecture"
-msgstr "arsitektur logging fluentbit-fluentd"
-
-msgid ""
-"https://blueprints.launchpad.net/openstack-helm/+spec/developer-environment"
-msgstr ""
-"https://blueprints.launchpad.net/openstack-helm/+spec/developer-environment"
-
-msgid "https://kubernetes.io/docs/concepts/containers/images"
-msgstr "https://kubernetes.io/docs/concepts/containers/images"
-
-msgid ""
-"https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-"
-"account/#add-imagepullsecrets-to-a-service-account"
-msgstr ""
-"https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-"
-"account/#add-imagepullsecrets-to-a-service-account"
-
-msgid "https://review.openstack.org/#/c/552485/"
-msgstr "https://review.openstack.org/#/c/552485/"
-
-msgid "https://storyboard.openstack.org/#!/story/2005130"
-msgstr "https://storyboard.openstack.org/#!/story/2005130"
-
-msgid "images * sub-keys (alphabetical order)"
-msgstr "images * sub-keys (sesuai abjad)"
-
-msgid "ingress"
-msgstr "ingress"
-
-msgid "k8s namespace: ceph"
-msgstr "k8s namespace: ceph"
-
-msgid "k8s namespace: tenant-ceph"
-msgstr "k8s namespace: tenant-ceph"
-
-msgid "k8s node labels:"
-msgstr "k8s node labels:"
-
-msgid "korzen (Artur Korzeniewski)"
-msgstr "korzen (Artur Korzeniewski)"
-
-msgid "labels * sub-keys (alphabetical order)"
-msgstr "labels * sub-keys (sesuai abjad)"
-
-msgid "ldap"
-msgstr "ldap"
-
-msgid "libvirt"
-msgstr "libvirt"
-
-msgid "manifests * sub-keys (alphabetical order)"
-msgstr "manifests * sub-keys  (sesuai abjad)"
-
-msgid "mariadb"
-msgstr "mariadb"
-
-msgid "mattmceuen (Matt McEuen <matt.mceuen@att.com>) for coordination"
-msgstr "mattmceuen (Matt McEuen <matt.mceuen@att.com>) untuk koordinasi"
-
-msgid "memcached"
-msgstr "memcached"
-
-msgid "metric port: 9283"
-msgstr "metric port: 9283"
-
-msgid "metric port: 9284"
-msgstr "metric port: 9284"
-
-msgid "mgr endpoint port: 7000"
-msgstr "mgr endpoint port: 7000"
-
-msgid "mgr endpoint port: 7001"
-msgstr "mgr endpoint port: 7001"
-
-msgid "mon endpoint port: 6789"
-msgstr "mon endpoint port: 6789"
-
-msgid "mon endpoint port: 6790"
-msgstr "mon endpoint port: 6790"
-
-msgid "mon_addr and mon_host have non default mon port 6790."
-msgstr "mon_addr and mon_host memiliki port mon standar 6790."
-
-msgid "mongodb"
-msgstr "mongodb"
-
-msgid "monitoring * sub-keys (alphabetical order)"
-msgstr "monitoring * sub-keys  (sesuai abjad)"
-
-msgid "network * sub-keys (alphabetical order)"
-msgstr "network * sub-keys  (sesuai abjad)"
-
-msgid "no ceph-mds"
-msgstr "no ceph-mds"
-
-msgid "no ceph-mds and ceph-rgw"
-msgstr "no ceph-mds dan ceph-rgw"
-
-msgid "no storage classes"
-msgstr "no storage classes"
-
-msgid ""
-"openstack-control-plane=enabled, ceph-mon=enabled, ceph-mgr=enabled, ceph-"
-"rgw=enabled, ceph-mds=enabled, ceph-osd=enabled"
-msgstr ""
-"openstack-control-plane=enabled, ceph-mon=enabled, ceph-mgr=enabled, ceph-"
-"rgw=enabled, ceph-mds=enabled, ceph-osd=enabled"
-
-msgid ""
-"openstack-data-plane=enabled, openstack-compute-node=enabled, ceph-osd-"
-"tenant=enabled, openstack-data-plane=enabled"
-msgstr ""
-"openstack-data-plane=enabled, openstack-compute-node=enabled, ceph-osd-"
-"tenant=enabled, openstack-data-plane=enabled"
-
-msgid "openvswitch"
-msgstr "openvswitch"
-
-msgid "pod * sub-keys (alphabetical order)"
-msgstr "pod * sub-keys (sesuai abjad)"
-
-msgid ""
-"portdirect (Pete Birley <pete@port.direct>) for the release management spec "
-"[2]_"
-msgstr ""
-"portdirect (Pete Birley <pete@port.direct>) untuk spesifikasi manajemen "
-"rilis [2] _"
-
-msgid "portdirect (Pete Birley)"
-msgstr "portdirect (Pete Birley)"
-
-msgid "postgresql"
-msgstr "postgresql"
-
-msgid ""
-"powerds (DaeSeong Kim <daeseong.kim@sk.com>) for the `values.yaml` ordering "
-"spec [1]_"
-msgstr ""
-"powerds (DaeSeong Kim <daeseong.kim@sk.com>) untuk `values.yaml` ordering "
-"spec [1]_"
-
-msgid ""
-"powerds0111 (DaeSeong Kim <daeseong.kim@sk.com>) srwilkers (Steve Wilkerson "
-"<sw5822@att.com>)"
-msgstr ""
-"powerds0111 (DaeSeong Kim <daeseong.kim@sk.com>) srwilkers (Steve Wilkerson "
-"<sw5822@att.com>)"
-
-msgid "rabbitmq"
-msgstr "rabbitmq"
-
-msgid ""
-"randeep.jalli (Randeep Jalli <rj2083@att.com>) and renmak (Renis Makadia "
-"<renis.makadia@att.com>) for splitting up the Ceph chart"
-msgstr ""
-"randeep.jalli (Randeep Jalli <rj2083@att.com>) dan renmak (Renis Makadia "
-"<renis.makadia@att.com>) untuk membagi chart Ceph"
-
-msgid ""
-"rwellum (Rich Wellum <richwellum@gmail.com>) for coordination of Storyboard "
-"adoption"
-msgstr ""
-"rwellum (Rich Wellum <richwellum@gmail.com>) untuk koordinasi adopsi "
-"Storyboard"
-
-msgid "secrets * sub-keys (alphabetical order)"
-msgstr "secrets * sub-keys (sesuai abjad)"
-
-msgid "services do not handle TLS offloading and termination,"
-msgstr "layanan tidak menangani pemuatan dan pemutusan TLS,"
-
-msgid ""
-"services whose native handling of TLS offloading and termination cause major "
-"performance impact, for example, eventlet."
-msgstr ""
-"layanan dengan penanganan native pemuatan dan pemutusan TLS menyebabkan "
-"dampak kinerja utama, misalnya, eventlet."
-
-msgid ""
-"srwilker (Steve Wilkerson) portdirect (Pete Birley) lr699s (Larry Rensing)"
-msgstr ""
-"srwilker (Steve Wilkerson) portdirect (Pete Birley) lr699s (Larry Rensing)"
-
-msgid "storage classes: general (rbd based for pvc)"
-msgstr "storage classes: general (rbd based for pvc)"
-
-msgid "sungil (Sungil Im) jayahn (Jaesuk Ahn)"
-msgstr "sungil (Sungil Im) jayahn (Jaesuk Ahn)"
-
-msgid ""
-"tenant-ceph-control-plane=enabled, ceph-mon-tenant=enabled, ceph-mgr-"
-"tenant=enabled, ceph-rgw-tenant=enabled"
-msgstr ""
-"tenant-ceph-control-plane=enabled, ceph-mon-tenant=enabled, ceph-mgr-"
-"tenant=enabled, ceph-rgw-tenant=enabled"
-
-msgid ""
-"the impact of adding extra conditionals in the helm charts, to deal with "
-"multi-distro aspect (if not using the approach above, or when using an "
-"alternative approach)"
-msgstr ""
-"dampak dari penambahan persyaratan extra di helm chart, untuk menangani "
-"aspek multi-distro (jika tidak menggunakan pendekatan di atas, atau ketika "
-"menggunakan pendekatan alternatif)"
-
-msgid ""
-"the impact of adding functionality in the ``helm-toolkit`` to deal with a "
-"common multi-distro aspect (could possibly increase helm chart rendering "
-"time)"
-msgstr ""
-"dampak dari penambahan fungsionalitas dalam ``helm-toolkit`` untuk menangani "
-"aspek multi-distro yang umum (mungkin dapat meningkatkan waktu rendering "
-"chart helm)"
-
-msgid ""
-"the impact of exposing extra key/values in the helm chart ``values.yaml`` "
-"file (could possibly have a deployment speed/ram usage increase)."
-msgstr ""
-"dampak dari mengekspos key/value tambahan dalam file helm ``values.yaml`` "
-"(mungkin bisa memiliki kecepatan deployment / peningkatan penggunaan ram)."
diff --git a/doc/source/locale/id/LC_MESSAGES/doc-testing.po b/doc/source/locale/id/LC_MESSAGES/doc-testing.po
deleted file mode 100644
index 268abeb58b..0000000000
--- a/doc/source/locale/id/LC_MESSAGES/doc-testing.po
+++ /dev/null
@@ -1,1032 +0,0 @@
-# suhartono <cloudsuhartono@gmail.com>, 2018. #zanata
-# suhartono <cloudsuhartono@gmail.com>, 2019. #zanata
-msgid ""
-msgstr ""
-"Project-Id-Version: openstack-helm 0.1.1.dev3685\n"
-"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2022-04-06 21:47+0000\n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-"PO-Revision-Date: 2019-05-28 12:08+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 ""
-"1) Initial Ceph and OpenStack deployment: Install Ceph and OpenStack charts "
-"on 3 nodes (mnode1, mnode2 and mnode3). Capture Ceph cluster status as well "
-"as K8s PODs status."
-msgstr ""
-"1) Penyebaran Ceph dan OpenStack awal: Pasang bagan Ceph dan OpenStack pada "
-"3 node (mnode1, mnode2 dan mnode3). Capture Ceph cluster status serta status "
-"PODs K8s."
-
-msgid ""
-"1) Node reduction: Shutdown 1 of 3 nodes to simulate node failure. Capture "
-"effect of node failure on Ceph as well as other OpenStack services that are "
-"using Ceph."
-msgstr ""
-"1) Node reduction: Shutdown 1 dari 3 node untuk mensimulasikan kegagalan "
-"node. Menangkap efek kegagalan node pada Ceph serta layanan OpenStack lain "
-"yang menggunakan Ceph."
-
-msgid "1) Remove out of quorum MON:"
-msgstr "1) Hapus dari quorum MON:"
-
-msgid ""
-"2) Node expansion: Apply Ceph and OpenStack related labels to another unused "
-"k8 node. Node expansion should provide more resources for k8 to schedule "
-"PODs for Ceph and OpenStack services."
-msgstr ""
-"2) Ekspansi Node: Menerapkan label terkait Ceph dan OpenStack ke nodus k8 "
-"yang tidak digunakan lainnya. Perluasan node harus menyediakan lebih banyak "
-"sumber daya untuk k8 untuk menjadwalkan POD untuk layanan Ceph dan OpenStack."
-
-msgid ""
-"2) Node reduction (failure): Shutdown 1 of 3 nodes (mnode3) to test node "
-"failure. This should cause Ceph cluster to go in HEALTH_WARN state as it has "
-"lost 1 MON and 1 OSD. Capture Ceph cluster status as well as K8s PODs status."
-msgstr ""
-"2) Pengurangan Node (kegagalan): Shutdown 1 dari 3 node (mnode3) untuk "
-"menguji kegagalan node. Ini harus menyebabkan Ceph cluster masuk dalam "
-"kondisi HEALTH_WARN karena telah kehilangan 1 MON dan 1 OSD. Capture Ceph "
-"cluster status serta status PODs K8s."
-
-msgid "2) Remove down OSD from Ceph cluster:"
-msgstr "2) Hapus OSD dari Ceph cluster:"
-
-msgid "3 Node (VM based) env."
-msgstr "3 Node (VM based) env."
-
-msgid ""
-"3) Fix Ceph Cluster: After node expansion, perform maintenance on Ceph "
-"cluster to ensure quorum is reached and Ceph is HEALTH_OK."
-msgstr ""
-"3) Perbaiki Ceph Cluster: Setelah perluasan node, lakukan perawatan pada "
-"cluster Ceph untuk memastikan kuorum tercapai dan Ceph adalah HEALTH_OK."
-
-msgid ""
-"3) Node expansion: Add Ceph and OpenStack related labels to 4th node "
-"(mnode4) for expansion. Ceph cluster would show new MON and OSD being added "
-"to cluster. However Ceph cluster would continue to show HEALTH_WARN because "
-"1 MON and 1 OSD are still missing."
-msgstr ""
-"3) Node ekspansi: Tambahkan Ceph dan OpenStack terkait label ke 4 node "
-"(mnode4) untuk ekspansi. Ceph cluster akan menunjukkan MON baru dan OSD yang "
-"ditambahkan ke cluster. Namun cluster Ceph akan terus menunjukkan "
-"HEALTH_WARN karena 1 MON dan 1 OSD masih hilang."
-
-msgid ""
-"4) Ceph cluster recovery: Perform Ceph maintenance to make Ceph cluster "
-"HEALTH_OK. Remove lost MON and OSD from Ceph cluster."
-msgstr ""
-"4) Ceph cluster recovery: Lakukan Ceph maintenance untuk membuat Ceph "
-"cluster HEALTH_OK. Hapus MON dan OSD yang hilang dari cluster Ceph."
-
-msgid ""
-"4. Replace the failed disk with a new one. If you repair (not replace) the "
-"failed disk, you may need to run the following:"
-msgstr ""
-"4. Ganti disk yang gagal dengan yang baru. Jika Anda memperbaiki (bukan "
-"mengganti) disk yang gagal, Anda mungkin perlu menjalankan yang berikut:"
-
-msgid "6 Nodes (VM based) env"
-msgstr "6 Nodes (VM based) env"
-
-msgid ""
-"A Ceph Monitor running on voyager3 (whose Monitor database is destroyed) "
-"becomes out of quorum, and the mon-pod's status stays in ``Running`` -> "
-"``Error`` -> ``CrashLoopBackOff`` while keeps restarting."
-msgstr ""
-"Monitor Ceph yang berjalan di voyager3 (yang database Monitor-nya dimatikan) "
-"menjadi tidak di quorum, dan status mon-pod tetap dalam ``Running`` -> "
-"``Error`` -> ``CrashLoopBackOff`` sementara terus restart."
-
-msgid ""
-"Above output shows Ceph cluster in HEALTH_OK with all OSDs and MONs up and "
-"running."
-msgstr ""
-"Output di atas menunjukkan Ceph cluster di HEALTH_OK dengan semua OSD dan "
-"MONS aktif dan berjalan."
-
-msgid "Above output shows that ``osd.1`` is down."
-msgstr "Output di atas menunjukkan bahwa ``osd.1`` sedang down."
-
-msgid "Adding Tests"
-msgstr "Menambahkan Tes"
-
-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 ""
-"Informasi tambahan tentang tes Helm untuk OpenStack-Helm dan cara melakukan "
-"tes ini secara lokal melalui skrip yang digunakan di gate dapat ditemukan di "
-"direktori 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 ""
-"Setelah 10+ menit, Ceph mulai menyeimbangkan kembali dengan satu node yang "
-"hilang (yaitu, 6 osds turun) dan statusnya stabil dengan 18 osds."
-
-msgid "After applying labels, let's check status"
-msgstr "Setelah menerapkan label, mari periksa status"
-
-msgid "After reboot (node voyager3), the node status changes to ``NotReady``."
-msgstr ""
-"Setelah reboot (node voyager3), status node berubah menjadi ``NotReady``."
-
-msgid ""
-"After the host is down (node voyager3), the node status changes to "
-"``NotReady``."
-msgstr ""
-"Setelah host mati (node voyager3), status node berubah menjadi ``NotReady``."
-
-msgid "All PODs are in running state."
-msgstr "Semua POD dalam keadaan berjalan."
-
-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 ""
-"Semua tes harus ditambahkan ke gate selama pengembangan, dan diperlukan "
-"untuk chart layanan baru sebelum penggabungan. Semua tes Helm harus "
-"dimasukkan sebagai bagian dari skrip pemasangan. Contoh ini dapat dilihat "
-"dalam skrip ini_."
-
-msgid ""
-"Also, the pod status of ceph-mon and ceph-osd changes from ``NodeLost`` back "
-"to ``Running``."
-msgstr ""
-"Juga, status pod ceph-mon dan ceph-osd berubah dari ``NodeLost`` kembali ke "
-"``Running``."
-
-msgid "Any Helm tests associated with a chart can be run by executing:"
-msgstr ""
-"Tes Helm apa pun yang terkait dengan chart dapat dijalankan dengan "
-"mengeksekusi:"
-
-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 ""
-"Setiap template untuk tes Helm yang diajukan harus mengikuti filosofi yang "
-"diterapkan dalam template lain. Ini termasuk: penggunaan menimpa di mana "
-"yang sesuai, penggunaan pencarian endpoint dan fungsi umum lainnya dalam "
-"helm-toolkit, dan pemasangan semua scripting template yang diperlukan "
-"melalui template configmap-bin untuk chart layanan. Jika pengujian Rally "
-"tidak sesuai atau memadai untuk chart layanan, pengujian tambahan apa pun "
-"harus didokumentasikan dengan tepat dan mematuhi harapan yang sama."
-
-msgid ""
-"As shown above, Ceph status is now HEALTH_OK and shows 3 MONs available."
-msgstr ""
-"Seperti yang ditunjukkan di atas, status Ceph sekarang HEALTH_OK dan "
-"menunjukkan 3 MON tersedia."
-
-msgid ""
-"As shown in Ceph status above, ``osd: 4 osds: 3 up, 3 in`` 1 of 4 OSDs is "
-"still down. Let's remove that OSD."
-msgstr ""
-"Seperti yang ditunjukkan dalam status Ceph di atas, ``osd: 4 osds: 3 up, 3 "
-"in`` 1 dari 4 OSDs masih turun. Mari hapus OSD itu."
-
-msgid "Capture Ceph pods statuses."
-msgstr "Capture Ceph pods statuses."
-
-msgid "Capture Openstack pods statuses."
-msgstr "Capture Openstack pods statuses."
-
-msgid "Capture final Ceph pod statuses:"
-msgstr "Capture final Ceph pod statuses:"
-
-msgid "Capture final Openstack pod statuses:"
-msgstr "Capture final Openstack pod statuses:"
-
-msgid "Case: 1 out of 3 Monitor Processes is Down"
-msgstr "Kasus: 1 dari 3 Proses Monitor Sedang Turun"
-
-msgid "Case: 2 out of 3 Monitor Processes are Down"
-msgstr "Kasus: 2 dari 3 Proses Monitor Sedang Turun"
-
-msgid "Case: 3 out of 3 Monitor Processes are Down"
-msgstr "Kasus: 3 dari 3 Proses Monitor Sedang Turun"
-
-msgid "Case: A OSD pod is deleted"
-msgstr "Kasus: Pod OSD dihapus"
-
-msgid "Case: A disk fails"
-msgstr "Kasus: Disk gagal"
-
-msgid "Case: A host machine where ceph-mon is running is down"
-msgstr "Kasus: Mesin host di mana ceph-mon sedang bekerja sedang mati"
-
-msgid "Case: Monitor database is destroyed"
-msgstr "Kasus: Database monitor dimusnahkan"
-
-msgid "Case: OSD processes are killed"
-msgstr "Kasus: Proses OSD dimatikan"
-
-msgid "Case: One host machine where ceph-mon is running is rebooted"
-msgstr "Kasus: Satu mesin host di mana ceph-mon sedang dijalankan di-reboot"
-
-msgid "Caveats:"
-msgstr "Caveats:"
-
-msgid "Ceph - Node Reduction, Expansion and Ceph Recovery"
-msgstr "Ceph - Node Reduction, Expansion, dan Ceph Recovery"
-
-msgid "Ceph Cephfs provisioner docker images."
-msgstr "Ceph Cephfs provisioner docker images."
-
-msgid "Ceph Luminous point release images for Ceph components"
-msgstr "Ceph Luminous point melepaskan image untuk komponen Ceph"
-
-msgid "Ceph MON and OSD PODs got scheduled on mnode4 node."
-msgstr "Ceph MON dan OSD POD dijadwalkan pada node mnode4."
-
-msgid "Ceph RBD provisioner docker images."
-msgstr "Ceph RBD provisioner docker images."
-
-msgid "Ceph Resiliency"
-msgstr "Ceph Resiliency"
-
-msgid "Ceph Upgrade"
-msgstr "Ceph Upgrade"
-
-msgid ""
-"Ceph can be upgraded without downtime for Openstack components in a "
-"multinode env."
-msgstr ""
-"Ceph dapat ditingkatkan tanpa downtime untuk komponen OpenStack dalam "
-"multinode env."
-
-msgid "Ceph cluster is in HEALTH_OK state with 3 MONs and 3 OSDs."
-msgstr "Ceph cluster dalam keadaan HEALTH_OK dengan 3 MON dan 3 OSD."
-
-msgid "Ceph status shows 1 Ceph MON and 1 Ceph OSD missing."
-msgstr "Status Ceph menunjukkan 1 Ceph MON dan 1 Ceph OSD hilang."
-
-msgid "Ceph status shows HEALTH_WARN as expected"
-msgstr "Status Ceph menunjukkan HEALTH_WARN seperti yang diharapkan"
-
-msgid "Ceph status shows that MON and OSD count has been increased."
-msgstr "Status Ceph menunjukkan bahwa jumlah MON dan OSD telah ditingkatkan."
-
-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 ""
-"Status Ceph menunjukkan bahwa ceph-mon yang berjalan pada ``voyager3`` "
-"menjadi tidak dapat digunakan. Juga, 6 osds yang berjalan pada ``voyager3`` "
-"sedang down (yaitu, 18 dari 24 osds naik). Beberapa kelompok penempatan "
-"menjadi terdegradasi dan berukuran kecil."
-
-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 ""
-"Status Ceph menunjukkan bahwa ceph-mon yang berjalan pada ``voyager3`` "
-"menjadi tidak dapat digunakan. Juga, enam osds yang berjalan di ``voyager3`` "
-"turun; yaitu, 18 osds naik dari 24 osds."
-
-msgid "Ceph status still shows HEALTH_WARN as one MON and OSD are still down."
-msgstr ""
-"Status Ceph masih menunjukkan HEALTH_WARN sebagai satu MON dan OSD masih "
-"dalam keadaan down."
-
-msgid "Ceph version: 12.2.3"
-msgstr "Ceph versi: 12.2.3"
-
-msgid "Check Ceph Pods"
-msgstr "Periksa Ceph Pods"
-
-msgid "Check version of each Ceph components."
-msgstr "Periksa versi setiap komponen Ceph."
-
-msgid "Check which images Provisionors and Mon-Check PODs are using"
-msgstr "Periksa image mana yang digunakan Provisionors dan Mon-Check PODs"
-
-msgid "Cluster size: 4 host machines"
-msgstr "Ukuran cluster: 4 mesin host"
-
-msgid "Conclusion:"
-msgstr "Kesimpulan:"
-
-msgid "Confirm Ceph component's version."
-msgstr "Konfirmasi versi komponen Ceph."
-
-msgid "Continue with OSH multinode guide to install other Openstack charts."
-msgstr ""
-"Lanjutkan dengan panduan multinode OSH untuk menginstal chart Openstack "
-"lainnya."
-
-msgid "Deploy and Validate Ceph"
-msgstr "Menyebarkan dan Memvalidasi Ceph"
-
-msgid "Disk Failure"
-msgstr "Kegagalan Disk"
-
-msgid "Docker Images:"
-msgstr "Docker Images:"
-
-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 ""
-"Setiap OpenStack-Helm chart harus menyertakan tes Helm yang diperlukan untuk "
-"memberikan pemeriksaan (sanity check) kewarasan untuk layanan OpenStack. "
-"Informasi tentang menggunakan kerangka pengujian Helm dapat ditemukan di "
-"repositori Helm. Saat ini, kerangka pengujian Rally digunakan untuk "
-"menyediakan pemeriksaan ini untuk layanan inti. Kerangka uji Keystone Helm "
-"dapat digunakan sebagai referensi, dan dapat ditemukan di sini_."
-
-msgid "Find that Ceph is healthy with a lost OSD (i.e., a total of 23 OSDs):"
-msgstr "Temukan bahwa Ceph sehat dengan OSD yang hilang (yaitu, total 23 OSD):"
-
-msgid "First, run ``ceph osd tree`` command to get list of OSDs."
-msgstr ""
-"Pertama, jalankan perintah ``ceph osd tree`` untuk mendapatkan daftar OSD."
-
-msgid "Follow all steps from OSH multinode guide with below changes."
-msgstr ""
-"Ikuti semua langkah dari panduan multinode OSH dengan perubahan di bawah ini."
-
-msgid ""
-"Followed OSH multinode guide steps to install Ceph and OpenStack charts up "
-"to Cinder."
-msgstr ""
-"Mengikuti panduan langkah multinode OSH untuk menginstal grafik Ceph dan "
-"OpenStack hingga Cinder."
-
-msgid ""
-"Followed OSH multinode guide steps to setup nodes and install K8s cluster"
-msgstr ""
-"Mengikuti langkah-langkah panduan multinode OSH untuk mengatur node dan "
-"menginstal K8s cluster"
-
-msgid "Followed OSH multinode guide steps upto Ceph install"
-msgstr "Mengikuti panduan multinode OSH langkah-langkah upto Ceph menginstal"
-
-msgid "Following is a partial part from script to show changes."
-msgstr ""
-"Berikut ini adalah bagian parsial dari skrip untuk menunjukkan perubahan."
-
-msgid ""
-"From the Kubernetes cluster, remove the failed OSD pod, which is running on "
-"``voyager4``:"
-msgstr ""
-"Dari kluster Kubernetes, hapus pod OSD yang gagal, yang berjalan di "
-"``voyager4``:"
-
-msgid "Hardware Failure"
-msgstr "Kegagalan perangkat keras"
-
-msgid "Helm Tests"
-msgstr "Tes Helm"
-
-msgid "Host Failure"
-msgstr "Host Failure"
-
-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 ""
-"Sementara itu, kami memantau status Ceph dan mencatat bahwa dibutuhkan "
-"sekitar 30 detik untuk 6 OSD untuk memulihkan dari ``down`` ke ``up``. "
-"Alasannya adalah Kubernetes secara otomatis merestart pod OSD setiap kali "
-"mereka dimatikan."
-
-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 ""
-"Sementara itu, kami memantau status Ceph dan mencatat bahwa dibutuhkan "
-"sekitar 24 detik untuk proses Monitor yang mati untuk memulihkan dari "
-"``down`` ke ``up``. Alasannya adalah Kubernetes secara otomatis me-restart "
-"pod setiap kali mereka dimatikan."
-
-msgid ""
-"In this test env, MariaDB chart is deployed with only 1 replica. In order to "
-"test properly, the node with MariaDB server POD (mnode2) should not be "
-"shutdown."
-msgstr ""
-"Dalam test env, tabel MariaDB dikerahkan hanya dengan 1 replika. Untuk "
-"menguji dengan benar, node dengan server POD MariaDB (mnode2) tidak boleh "
-"dimatikan."
-
-msgid "In this test env, ``mnode3`` is out of quorum."
-msgstr "Dalam tes env ini, `` mnode3`` keluar dari quorum."
-
-msgid ""
-"In this test env, each node has Ceph and OpenStack related PODs. Due to "
-"this, shutting down a Node will cause issue with Ceph as well as OpenStack "
-"services. These PODs level failures are captured following subsequent "
-"screenshots."
-msgstr ""
-"Dalam tes env ini, setiap node memiliki POD yang terkait dengan Ceph dan "
-"OpenStack. Karena ini, mematikan Node akan menyebabkan masalah dengan Ceph "
-"serta layanan OpenStack. Tingkat kegagalan PODs ini ditangkap setelah "
-"screenshot berikutnya."
-
-msgid "In this test env, let's shutdown ``mnode3`` node."
-msgstr "Dalam tes ini env, mari kita mematikan node `` mnode3``."
-
-msgid ""
-"In this test env, let's use ``mnode4`` and apply Ceph and OpenStack related "
-"labels."
-msgstr ""
-"Dalam tes env ini, mari kita gunakan ``mnode4`` dan menerapkan label terkait "
-"Ceph dan OpenStack."
-
-msgid ""
-"In this test env, since out of quorum MON is no longer available due to node "
-"failure, we can processed with removing it from Ceph cluster."
-msgstr ""
-"Dalam  test env ini, sejak quorum MON tidak lagi tersedia karena kegagalan "
-"node, kami dapat memprosesnya dengan menghapusnya dari cluster Ceph."
-
-msgid "Install Ceph charts (12.2.4) by updating Docker images in overrides."
-msgstr ""
-"Instal Ceph charts (12.2.4) dengan memperbarui Docker images di overrides."
-
-msgid "Install Ceph charts (version 12.2.4)"
-msgstr "Pasang chart Ceph (versi 12.2.4)"
-
-msgid "Install OSH components as per OSH multinode guide."
-msgstr "Instal komponen OSH sesuai panduan multinode OSH."
-
-msgid "Install Openstack charts"
-msgstr "Pasang chart Openstack"
-
-msgid ""
-"It takes longer (about 1 minute) for the killed Monitor processes to recover "
-"from ``down`` to ``up``."
-msgstr ""
-"Diperlukan waktu lebih lama (sekitar 1 menit) untuk proses Monitor yang mati "
-"untuk memulihkan dari ``down`` ke ``up``."
-
-msgid "Kubernetes version: 1.10.5"
-msgstr "Kubernetes versi: 1.10.5"
-
-msgid "Kubernetes version: 1.9.3"
-msgstr "Kubernetes version: 1.9.3"
-
-msgid "Let's add more resources for K8s to schedule PODs on."
-msgstr ""
-"Mari tambahkan lebih banyak sumber daya untuk K8 untuk menjadwalkan POD."
-
-msgid ""
-"Make sure only 3 nodes (mnode1, mnode2, mnode3) have Ceph and OpenStack "
-"related labels. K8s would only schedule PODs on these 3 nodes."
-msgstr ""
-"Pastikan hanya 3 node (mnode1, mnode2, mnode3) yang memiliki label terkait "
-"Ceph dan OpenStack. K8 hanya akan menjadwalkan POD pada 3 node ini."
-
-msgid "Mission"
-msgstr "Misi"
-
-msgid "Monitor Failure"
-msgstr "Memantau Kegagalan"
-
-msgid ""
-"Note: To find the daemonset associated with a failed OSD, check out the "
-"followings:"
-msgstr ""
-"Catatan: Untuk menemukan daemon yang terkait dengan OSD yang gagal, periksa "
-"yang berikut:"
-
-msgid ""
-"Now that we have added new node for Ceph and OpenStack PODs, let's perform "
-"maintenance on Ceph cluster."
-msgstr ""
-"Sekarang kita telah menambahkan node baru untuk Ceph dan OpenStack PODs, "
-"mari kita melakukan pemeliharaan pada cluster Ceph."
-
-msgid "Number of disks: 24 (= 6 disks per host * 4 hosts)"
-msgstr "Jumlah disk: 24 (= 6 disk per host * 4 host)"
-
-msgid "OSD Failure"
-msgstr "Kegagalan OSD"
-
-msgid "OSD count is set to 3 based on env setup."
-msgstr "Penghitungan OSD diatur ke 3 berdasarkan pada env setup."
-
-msgid ""
-"Only 3 nodes will have Ceph and OpenStack related labels. Each of these 3 "
-"nodes will have one MON and one OSD running on them."
-msgstr ""
-"Hanya 3 node yang memiliki label terkait Ceph dan OpenStack. Masing-masing "
-"dari 3 node ini akan memiliki satu MON dan satu OSD yang berjalan pada "
-"mereka."
-
-msgid "OpenStack PODs that were scheduled mnode3 also shows NodeLost/Unknown."
-msgstr ""
-"OpenStack PODs yang dijadwalkan mnode3 juga menunjukkan NodeLost / Unknown."
-
-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 ""
-"Fokus kami terletak pada ketahanan untuk berbagai skenario kegagalan tetapi "
-"tidak pada kinerja atau stress testing."
-
-msgid "PODs that were scheduled on mnode3 node has status of NodeLost/Unknown."
-msgstr ""
-"POD yang dijadwalkan pada node mnode3 memiliki status NodeLost / Unknown."
-
-msgid "Plan:"
-msgstr "Rencana:"
-
-msgid "Recovery:"
-msgstr "Pemulihan:"
-
-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 ""
-"Hapus seluruh direktori ceph-mon di voyager3, dan kemudian Ceph akan secara "
-"otomatis membuat ulang database dengan menggunakan database ceph-mons "
-"lainnya."
-
-msgid ""
-"Remove the failed OSD (OSD ID = 2 in this example) from the Ceph cluster:"
-msgstr "Hapus OSD yang gagal (OSD ID = 2 dalam contoh ini) dari kluster Ceph:"
-
-msgid "Resiliency Tests for OpenStack-Helm/Ceph"
-msgstr "Tes Ketahanan untuk OpenStack-Helm/Ceph"
-
-msgid "Run ``ceph osd purge`` command to remove OSD from ceph cluster."
-msgstr ""
-"Jalankan perintah ``ceph osd purge`` untuk menghapus OSD dari ceph cluster."
-
-msgid "Running Tests"
-msgstr "Menjalankan Tes"
-
-msgid "Setup:"
-msgstr "Mempersiapkan:"
-
-msgid ""
-"Showing partial output from kubectl describe command to show which image is "
-"Docker container is using"
-msgstr ""
-"Menampilkan sebagian output dari kubectl menggambarkan perintah untuk "
-"menunjukkan image mana yang digunakan oleh container Docker"
-
-msgid ""
-"Shutdown 1 of 3 nodes (mnode1, mnode2, mnode3) to simulate node failure/lost."
-msgstr ""
-"Shutdown 1 dari 3 node (mnode1, mnode2, mnode3) untuk mensimulasikan "
-"kegagalan node / lost."
-
-msgid ""
-"Since the node that was shutdown earlier had both Ceph and OpenStack PODs, "
-"mnode4 should get Ceph and OpenStack related labels as well."
-msgstr ""
-"Karena node yang shutdown sebelumnya memiliki Ceph dan OpenStack PODs, "
-"mnode4 harus mendapatkan label terkait Ceph dan OpenStack juga."
-
-msgid "Software Failure"
-msgstr "Kegagalan Perangkat Lunak"
-
-msgid "Solution:"
-msgstr "Solusi:"
-
-msgid "Start a new OSD pod on ``voyager4``:"
-msgstr "Mulai pod LED baru pada ``voyager 4``:"
-
-msgid "Step 1: Initial Ceph and OpenStack deployment"
-msgstr "Langkah 1: Penyebaran Ceph dan OpenStack awal"
-
-msgid "Step 2: Node reduction (failure):"
-msgstr "Langkah 2: Pengurangan nodus (kegagalan):"
-
-msgid "Step 3: Node Expansion"
-msgstr "Langkah 3: Ekspansi Node"
-
-msgid "Step 4: Ceph cluster recovery"
-msgstr "Langkah 4: Ceph cluster recovery"
-
-msgid "Steps:"
-msgstr "Langkah:"
-
-msgid "Symptom:"
-msgstr "Gejala:"
-
-msgid "Test Environment"
-msgstr "Uji Lingkungan"
-
-msgid "Test Scenario:"
-msgstr "Test Scenario:"
-
-msgid "Test Scenarios:"
-msgstr "Skenario Uji:"
-
-msgid "Testing"
-msgstr "Pengujian"
-
-msgid "Testing Expectations"
-msgstr "Menguji Ekspektasi"
-
-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 ""
-"Tujuan dari uji ketahanan kami untuk `OpenStack-Helm/Ceph <https://github."
-"com/openstack/openstack-helm/tree/master/ceph>`_ adalah untuk menunjukkan "
-"gejala kegagalan perangkat lunak/perangkat keras dan memberikan solusi."
-
-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 ""
-"Log dari mon-pod gagal menunjukkan proses ceph-mon tidak dapat berjalan "
-"karena ``/var/lib/ceph/mon/ceph-voyager3/store.db`` tidak ada."
-
-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 ""
-"Status node ``voyager3`` berubah menjadi ``Ready`` setelah node naik lagi. "
-"Juga, Ceph pod di-restart secara otomatis. Status Ceph menunjukkan bahwa "
-"monitor yang dijalankan pada ``voyager3`` sekarang dalam kuorum."
-
-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 ""
-"Status node ``voyager3`` berubah menjadi ``Ready`` setelah node naik lagi. "
-"Juga, Ceph pod di-restart secara otomatis. Status Ceph menunjukkan bahwa "
-"monitor yang berjalan pada ``voyager3`` sekarang berada di kuorum dan 6 osds "
-"akan kembali (yaitu, total 24 osds naik)."
-
-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 ""
-"Output dari tes Helm dapat dilihat dengan melihat log dari pod yang dibuat "
-"oleh tes Helm. Log ini dapat dilihat dengan:"
-
-msgid "The pod status of ceph-mon and ceph-osd shows as ``NodeLost``."
-msgstr "Status pod ceph-mon dan ceph-osd ditampilkan sebagai ``NodeLost``."
-
-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 ""
-"Status pod (di mana ketiga proses Monitor dimatikan) diubah sebagai berikut: "
-"``Running`` -> ``Error`` -> ``CrashLoopBackOff`` -> ``Running`` dan proses "
-"pemulihan ini memakan waktu sekitar 1 menit."
-
-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 ""
-"Status pod (di mana kedua proses Monitor mati) diubah sebagai berikut: "
-"``Running`` -> ``Error`` -> ``CrashLoopBackOff`` -> ``Running`` dan proses "
-"pemulihan ini memakan waktu sekitar 1 menit."
-
-msgid ""
-"This document captures steps and result from node reduction and expansion as "
-"well as ceph recovery."
-msgstr ""
-"Dokumen ini menangkap (capture) langkah dan hasil dari pengurangan dan "
-"perluasan node serta pemulihan ceph."
-
-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 ""
-"Panduan ini mendokumentasikan langkah-langkah yang menunjukkan upgrade versi "
-"Ceph. Tujuan utama dari dokumen ini adalah untuk mendemonstrasikan pembaruan "
-"Ceph chart tanpa downtime untuk komponen OSH."
-
-msgid ""
-"This is for the case when a host machine (where ceph-mon is running) is down."
-msgstr ""
-"Ini untuk kasus ketika mesin host (di mana ceph-mon sedang berjalan) sedang "
-"mati."
-
-msgid "This is to test a scenario when 1 out of 3 Monitor processes is down."
-msgstr "Ini untuk menguji skenario ketika 1 dari 3 proses Monitor mati."
-
-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 ""
-"Ini untuk menguji skenario ketika 2 dari 3 proses Monitor sedang down. Untuk "
-"menurunkan 2 proses Monitor (dari 3), kami mengidentifikasi dua proses "
-"Monitor dan mematikannya dari 2 monitor host (bukan 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 ""
-"Ini untuk menguji skenario ketika 3 dari 3 proses Monitor sedang down. Untuk "
-"menurunkan 3 proses Monitor (dari 3), kami mengidentifikasi semua 3 proses "
-"Monitor dan mematikannya dari 3 monitor host (bukan pod)."
-
-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 ""
-"Ini untuk menguji skenario ketika terjadi kegagalan disk. Kami memonitor "
-"status ceph dan melihat satu OSD (osd.2) di voyager4 yang memiliki ``/dev/"
-"sdh`` sebagai backend sedang down (mati)."
-
-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 note that it "
-"takes about 90 seconds for the OSD running in deleted pod to recover from "
-"``down`` to ``up``."
-msgstr ""
-"Ini untuk menguji skenario ketika pod OSD dihapus oleh ``kubectl delete $ "
-"OSD_POD_NAME``. Sementara itu, kami memantau status Ceph dan perhatikan "
-"bahwa dibutuhkan sekitar 90 detik untuk OSD yang berjalan di pod yang "
-"dihapus untuk memulihkan dari  ``down`` ke ``up``."
-
-msgid "This is to test a scenario when some of the OSDs are down."
-msgstr "Ini untuk menguji skenario ketika beberapa OSD turun."
-
-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 ""
-"Untuk menurunkan 1 proses Monitor (dari 3), kami mengidentifikasi proses "
-"Monitor dan mematikannya dari host monitor (bukan 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 ""
-"Untuk menurunkan 6 OSD (dari 24), kami mengidentifikasi proses OSD dan "
-"mematikannya  dari host penyimpanan (bukan pod)."
-
-msgid "To replace the failed OSD, execute the following procedure:"
-msgstr "Untuk mengganti OSD yang gagal, jalankan prosedur berikut:"
-
-msgid "Update Ceph Client chart with new overrides:"
-msgstr "Perbarui Ceph Client chart dengan override baru:"
-
-msgid "Update Ceph Mon chart with new overrides"
-msgstr "Perbarui Ceph Mon chart dengan override baru"
-
-msgid "Update Ceph OSD chart with new overrides:"
-msgstr "Perbarui Ceph OSD chart dengan override baru:"
-
-msgid "Update Ceph Provisioners chart with new overrides:"
-msgstr "Perbarui Ceph Provisioners chart dengan override baru:"
-
-msgid ""
-"Update ceph install script ``./tools/deployment/multinode/030-ceph.sh`` to "
-"add ``images:`` section in overrides as shown below."
-msgstr ""
-"Perbarui ceph install script ``./tools/deployment/multinode/030-ceph.sh`` "
-"untuk menambahkan bagian ``images:`` di override seperti yang ditunjukkan di "
-"bawah ini."
-
-msgid ""
-"Update, image section in new overrides ``ceph-update.yaml`` as shown below"
-msgstr ""
-"Pembaruan, bagian image di overrides baru ``ceph-update.yaml`` seperti yang "
-"ditunjukkan di bawah ini"
-
-msgid "Upgrade Ceph charts to update version"
-msgstr "Tingkatkan Ceph charts untuk memperbarui versi"
-
-msgid ""
-"Upgrade Ceph charts to version 12.2.5 by updating docker images in overrides."
-msgstr ""
-"Tingkatkan Ceph chart ke versi 12.2.5 dengan memperbarui image docker di "
-"overrides."
-
-msgid ""
-"Upgrade Ceph component version from ``12.2.4`` to ``12.2.5`` without "
-"downtime to OSH components."
-msgstr ""
-"Upgrade versi komponen Ceph dari ``12.2.4`` ke ``12.2.5`` tanpa waktu henti "
-"ke komponen OSH."
-
-msgid ""
-"Use Ceph override file ``ceph.yaml`` that was generated previously and "
-"update images section as below"
-msgstr ""
-"Gunakan Ceph override file ``ceph.yaml`` yang telah dibuat sebelumnya dan "
-"perbarui bagian image seperti di bawah ini"
-
-msgid ""
-"Using ``ceph mon_status`` and ``ceph -s`` commands, confirm ID of MON that "
-"is out of quorum."
-msgstr ""
-"Dengan menggunakan perintah ``ceph mon_status`` dan ``ceph -s``, "
-"konfirmasikan ID MON yang keluar dari quorum."
-
-msgid ""
-"Validate the Ceph status (i.e., one OSD is added, so the total number of "
-"OSDs becomes 24):"
-msgstr ""
-"Validasi status Ceph (yaitu satu OSD ditambahkan, sehingga jumlah total OSD "
-"menjadi 24):"
-
-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 takes about 90 seconds. The reason is that Kubernetes automatically "
-"restarts OSD pods whenever they are deleted."
-msgstr ""
-"Kami juga memantau status pod melalui ``kubectl get pods -n ceph``  selama "
-"proses ini. Status pod OSD yang dihapus diubah sebagai berikut: "
-"``Terminating`` -> ``Init:1/3`` -> ``Init:2/3`` -> ``Init:3/3`` -> "
-"``Running``, dan proses ini membutuhkan waktu sekitar 90 detik. Alasannya "
-"adalah Kubernetes secara otomatis merestart pod OSD setiap kali dihapus."
-
-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 ""
-"Kami juga memantau status pod Monitor melalui ``kubectl get pods -n ceph``, "
-"dan status pod (di mana proses Monitor mati) berubah sebagai berikut: "
-"``Running`` -> ``Error`` -> ``Running`` dan proses pemulihan ini membutuhkan "
-"waktu sekitar 24 detik."
-
-msgid ""
-"We have 3 Monitors in this Ceph cluster, one on each of the 3 Monitor hosts."
-msgstr ""
-"Kami memiliki 3 Monitor di cluster Ceph ini, satu di masing-masing dari 3 "
-"host Monitor."
-
-msgid ""
-"We intentionlly destroy a Monitor database by removing ``/var/lib/openstack-"
-"helm/ceph/mon/mon/ceph-voyager3/store.db``."
-msgstr ""
-"Kami bermaksud menghancurkan database Monitor dengan menghapus ``/var/lib/"
-"openstack-helm/ceph/mon/mon/ceph-voyager3/store.db``."
-
-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 ""
-"Kami memantau status pod Ceph Monitor dan mencatat bahwa gejalanya mirip "
-"dengan ketika 1 atau 2 proses Monitor dimatikan:"
-
-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 ""
-"Kami memantau status Ceph ketika proses Monitor dimatikan dan mencatat bahwa "
-"gejala mirip dengan ketika 1 Proses monitor dimatikan:"
-
-msgid "`Disk failure <./disk-failure.html>`_"
-msgstr "`Disk failure <./disk-failure.html>`_"
-
-msgid "`Host failure <./host-failure.html>`_"
-msgstr "`Host failure <./host-failure.html>`_"
-
-msgid "`Monitor failure <./monitor-failure.html>`_"
-msgstr "`Monitor failure <./monitor-failure.html>`_"
-
-msgid "`OSD failure <./osd-failure.html>`_"
-msgstr "`OSD failure <./osd-failure.html>`_"
-
-msgid "``Ceph MON Status:``"
-msgstr "``Ceph MON Status:``"
-
-msgid "``Ceph MON Status``"
-msgstr "``Ceph MON Status``"
-
-msgid "``Ceph PODs:``"
-msgstr "``Ceph PODs:``"
-
-msgid "``Ceph PODs``"
-msgstr "``Ceph PODs``"
-
-msgid "``Ceph Status:``"
-msgstr "``Ceph Status:``"
-
-msgid "``Ceph quorum status:``"
-msgstr "``Ceph quorum status:``"
-
-msgid "``Ceph quorum status``"
-msgstr "``Ceph quorum status``"
-
-msgid "``Ceph status:``"
-msgstr "``Ceph status:``"
-
-msgid "``Ceph status``"
-msgstr "``Ceph status``"
-
-msgid "``Check node status:``"
-msgstr "``Check node status:``"
-
-msgid "``Following are PODs scheduled on mnode3 before shutdown:``"
-msgstr "``Following are PODs scheduled on mnode3 before shutdown:``"
-
-msgid "``OpenStack PODs:``"
-msgstr "``OpenStack PODs:``"
-
-msgid "``OpenStack PODs``"
-msgstr "``OpenStack PODs``"
-
-msgid "``Remove MON from Ceph cluster``"
-msgstr "``Remove MON from Ceph cluster``"
-
-msgid "``Result/Observation:``"
-msgstr "``Result/Observation:``"
-
-msgid ""
-"``Results:`` All provisioner pods got terminated at once (same time). Other "
-"ceph pods are running. No interruption to OSH pods."
-msgstr ""
-"``Results:`` Semua pod penyedia dihentikan sekaligus (saat yang sama). Ceph "
-"pod lainnya sedang berjalan. Tidak ada gangguan pada pod OSH."
-
-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 ""
-"``Results:`` Mon pod mendapat pembaruan satu per satu (pembaruan bergulir). "
-"Setiap Mon pod mendapat respawn dan berada dalam 1/1 keadaan sebelum Mon pod "
-"berikutnya diperbarui. Setiap Mon pod mulai dihidupkan ulang. Ceph pod "
-"lainnya tidak terpengaruh dengan pembaruan ini. Tidak ada gangguan pada pod "
-"OSH."
-
-msgid ""
-"``Results:`` Rolling updates (one pod at a time). Other ceph pods are "
-"running. No interruption to OSH pods."
-msgstr ""
-"``Results:`` Bergulir pembaruan (satu pod dalam satu waktu). Ceph pod "
-"lainnya sedang berjalan. Tidak ada gangguan pada pod OSH."
-
-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 ""
-"Image ``ceph_bootstrap``, ``ceph-config_helper`` and ``ceph_rbs_pool`` "
-"digunakan untuk pekerjaan. ``ceph_mon_check`` memiliki satu skrip yang "
-"stabil sehingga tidak perlu melakukan upgrade."
-
-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 "``series of console outputs:``"
diff --git a/doc/source/locale/id/LC_MESSAGES/doc-troubleshooting.po b/doc/source/locale/id/LC_MESSAGES/doc-troubleshooting.po
deleted file mode 100644
index 577fc59c31..0000000000
--- a/doc/source/locale/id/LC_MESSAGES/doc-troubleshooting.po
+++ /dev/null
@@ -1,207 +0,0 @@
-# suhartono <cloudsuhartono@gmail.com>, 2018. #zanata
-# suhartono <cloudsuhartono@gmail.com>, 2020. #zanata
-msgid ""
-msgstr ""
-"Project-Id-Version: openstack-helm 0.1.1.dev3685\n"
-"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2022-04-06 21:47+0000\n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-"PO-Revision-Date: 2020-05-08 08:25+0000\n"
-"Last-Translator: suhartono <cloudsuhartono@gmail.com>\n"
-"Language-Team: Indonesian\n"
-"Language: id\n"
-"X-Generator: Zanata 4.3.3\n"
-"Plural-Forms: nplurals=1; plural=0\n"
-
-msgid "Backing up a PVC"
-msgstr "Mencadangkan PVC"
-
-msgid ""
-"Backing up a PVC stored in Ceph, is fairly straigthforward, in this example "
-"we use the PVC ``mysql-data-mariadb-server-0`` as an example, but this will "
-"also apply to any other services using PVCs eg. RabbitMQ, Postgres."
-msgstr ""
-"Mencadangkan PVC yang disimpan di Ceph, cukup ketat, dalam contoh ini kita "
-"menggunakan PVC ``mysql-data-mariadb-server-0`` sebagai contoh, tetapi ini "
-"juga akan berlaku untuk layanan lain yang menggunakan PVC misalnya. "
-"RabbitMQ, Postgres."
-
-msgid ""
-"Before proceeding, it is important to ensure that you have deployed a client "
-"key in the namespace you wish to fulfill ``PersistentVolumeClaims``. To "
-"verify that your deployment namespace has a client key:"
-msgstr ""
-"Sebelum melanjutkan, penting untuk memastikan bahwa Anda telah menggunakan "
-"kunci klien di ruang nama (namespace) yang ingin Anda penuhi "
-"``PersistentVolumeClaims``. Untuk memverifikasi bahwa namespace penyebaran "
-"Anda memiliki kunci klien:"
-
-msgid "Bugs and Feature requests"
-msgstr "Permintaan Bug dan Fitur"
-
-msgid "Ceph"
-msgstr "Ceph"
-
-msgid "Ceph Deployment Status"
-msgstr "Status Penerapan Ceph"
-
-msgid "Ceph Validating PVC Operation"
-msgstr "Ceph Memvalidasi Operasi PVC"
-
-msgid "Ceph Validating StorageClass"
-msgstr "Ceph Validating StorageClass"
-
-msgid "Channels"
-msgstr "Channels"
-
-msgid "Database Deployments"
-msgstr "Database Deployments"
-
-msgid ""
-"First, we want to validate that Ceph is working correctly. This can be done "
-"with the following Ceph command:"
-msgstr ""
-"Pertama, kami ingin memvalidasi bahwa Ceph berfungsi dengan benar. Ini dapat "
-"dilakukan dengan perintah Ceph berikut:"
-
-msgid "Galera Cluster"
-msgstr "Galera Cluster"
-
-msgid "Getting help"
-msgstr "Mendapatkan bantuan"
-
-msgid "Installation"
-msgstr "Instalasi"
-
-msgid "Join us on `Slack <http://slack.k8s.io/>`_ - #openstack-helm"
-msgstr ""
-"Bergabunglah dengan kami `Slack <http://slack.k8s.io/>`_ - #openstack-helm"
-
-msgid ""
-"Next we can look at the storage class, to make sure that it was created "
-"correctly:"
-msgstr ""
-"Selanjutnya kita dapat melihat kelas penyimpanan, untuk memastikan bahwa itu "
-"dibuat dengan benar:"
-
-msgid ""
-"Note: This step is not relevant for PVCs within the same namespace Ceph was "
-"deployed."
-msgstr ""
-"Catatan: Langkah ini tidak relevan untuk PVC dalam ruang nama (namespace) "
-"yang sama Ceph dikerahkan."
-
-msgid "Once this has been done the workload can be restarted."
-msgstr "Setelah ini selesai, beban kerja (workload) dapat dimulai kembali."
-
-msgid "PVC Preliminary Validation"
-msgstr "Validasi Pendahuluan PVC"
-
-msgid "Persistent Storage"
-msgstr "Penyimpanan Persisten"
-
-msgid ""
-"Please, refer to `Contribution guidelines <../contributor/contributing."
-"html>`_."
-msgstr ""
-"Silakan merujuk `Contribution guidelines <../contributor/contributing."
-"html>`_."
-
-msgid ""
-"Restoring is just as straightforward. Once the workload consuming the device "
-"has been stopped, and the raw RBD device removed the following will import "
-"the back up and create a device:"
-msgstr ""
-"Memulihkan sama mudahnya. Setelah beban kerja yang memakan perangkat telah "
-"dihentikan, dan perangkat RBD mentah yang dihapus berikut ini akan mengimpor "
-"cadangan dan membuat perangkat:"
-
-msgid ""
-"Sometimes things go wrong. These guides will help you solve many common "
-"issues with the following:"
-msgstr ""
-"Terkadang ada yang salah. Panduan ini akan membantu Anda memecahkan banyak "
-"masalah umum dengan hal-hal berikut:"
-
-msgid ""
-"The parameters are what we're looking for here. If we see parameters passed "
-"to the StorageClass correctly, we will see the ``ceph-mon.ceph.svc.cluster."
-"local:6789`` hostname/port, things like ``userid``, and appropriate secrets "
-"used for volume claims."
-msgstr ""
-"Parameternya adalah apa yang kami cari di sini. Jika kita melihat parameter "
-"yang dikirimkan ke StorageClass dengan benar, kita akan melihat hostname/"
-"port  ``ceph-mon.ceph.svc.cluster.local: 6789``, hal-hal seperti ``userid``, "
-"dan rahasia yang sesuai digunakan untuk klaim volume ."
-
-msgid ""
-"This guide is to help users debug any general storage issues when deploying "
-"Charts in this repository."
-msgstr ""
-"Panduan ini untuk membantu pengguna mendebug masalah penyimpanan umum apa "
-"pun saat menerapkan Charts dalam repositori ini."
-
-msgid ""
-"This guide is to help users debug any general storage issues when deploying "
-"charts in this repository."
-msgstr ""
-"Panduan ini untuk membantu pengguna mendebug masalah penyimpanan umum apa "
-"pun saat menerapkan grafik di repositori ini."
-
-msgid ""
-"To deploy the HWE kernel, prior to deploying Kubernetes and OpenStack-Helm "
-"the following commands should be run on each node:"
-msgstr ""
-"Untuk menyebarkan kernel HWE, sebelum menyebarkan Kubernetes dan OpenStack-"
-"Helm, perintah berikut harus dijalankan pada setiap node:"
-
-msgid ""
-"To make use of CephFS in Ubuntu the HWE Kernel is required, until the issue "
-"described `here <https://github.com/kubernetes-incubator/external-storage/"
-"issues/345>`_ is fixed."
-msgstr ""
-"Untuk menggunakan CephFS di Ubuntu, Kernel HWE diperlukan, sampai masalah "
-"tersebut dijelaskan `here <https://github.com/kubernetes-incubator/external-"
-"storage/issues/345>`_ telah diperbaiki."
-
-msgid "To test MariaDB, do the following:"
-msgstr "Untuk menguji MariaDB, lakukan hal berikut:"
-
-msgid ""
-"To validate persistent volume claim (PVC) creation, we've placed a test "
-"manifest `here <https://raw.githubusercontent.com/openstack/openstack-helm/"
-"master/tests/pvc-test.yaml>`_. Deploy this manifest and verify the job "
-"completes successfully."
-msgstr ""
-"Untuk memvalidasi pembuatan persistent volume claim (PVC, kami menempatkan "
-"manifes tes `here <https://raw.githubusercontent.com/openstack/openstack-"
-"helm/master/tests/pvc-test.yaml>`_. Gunakan manifes ini dan verifikasi bahwa "
-"pekerjaan telah selesai dengan sukses."
-
-msgid "Troubleshooting"
-msgstr "Penyelesaian masalah"
-
-msgid "Ubuntu HWE Kernel"
-msgstr "Ubuntu HWE Kernel"
-
-msgid ""
-"Use one of your Ceph Monitors to check the status of the cluster. A couple "
-"of things to note above; our health is `HEALTH\\_OK`, we have 3 mons, we've "
-"established a quorum, and we can see that all of our OSDs are up and in the "
-"OSD map."
-msgstr ""
-"Gunakan salah satu Ceph Monitors Anda untuk memeriksa status cluster. "
-"Beberapa hal yang perlu diperhatikan di atas; kesehatan kita adalah  `HEALTH"
-"\\_OK`, kita memiliki 3 mons, kita telah membentuk kuorum, dan kita dapat "
-"melihat bahwa semua OSD kita sudah naik dan di peta OSD."
-
-msgid ""
-"Without this, your RBD-backed PVCs will never reach the ``Bound`` state.  "
-"For more information, see how to `activate namespace for ceph <../install/"
-"multinode.html#activating-control-plane-namespace-for-ceph>`_."
-msgstr ""
-"Tanpa ini, RBD-backed PVCs Anda tidak akan pernah mencapai status ``Bound``. "
-"Untuk informasi lebih lanjut, lihat caranya `activate namespace for ceph <../"
-"install/multinode.html#activating-control-plane-namespace-for-ceph>`_."
diff --git a/doc/source/locale/id/LC_MESSAGES/doc.po b/doc/source/locale/id/LC_MESSAGES/doc.po
deleted file mode 100644
index 4226280669..0000000000
--- a/doc/source/locale/id/LC_MESSAGES/doc.po
+++ /dev/null
@@ -1,384 +0,0 @@
-# suhartono <cloudsuhartono@gmail.com>, 2018. #zanata
-# suhartono <cloudsuhartono@gmail.com>, 2019. #zanata
-# suhartono <cloudsuhartono@gmail.com>, 2020. #zanata
-msgid ""
-msgstr ""
-"Project-Id-Version: openstack-helm 0.1.1.dev3879\n"
-"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2022-10-24 20:45+0000\n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-"PO-Revision-Date: 2020-05-08 08:23+0000\n"
-"Last-Translator: suhartono <cloudsuhartono@gmail.com>\n"
-"Language-Team: Indonesian\n"
-"Language: id\n"
-"X-Generator: Zanata 4.3.3\n"
-"Plural-Forms: nplurals=1; plural=0\n"
-
-msgid ":ref:`genindex`"
-msgstr ":ref:`genindex`"
-
-msgid ":ref:`search`"
-msgstr ":ref:`search`"
-
-msgid "Adding Services"
-msgstr "Menambahkan Layanan"
-
-msgid "Adding Tests"
-msgstr "Menambahkan Tes"
-
-msgid ""
-"Any additional functions required for testing new charts or improving the "
-"gate workflow should be placed in the appropriate location."
-msgstr ""
-"Setiap fungsi tambahan yang diperlukan untuk menguji chart baru atau "
-"meningkatkan gate workflow harus ditempatkan di lokasi yang tepat."
-
-msgid ""
-"Any tests that do not use the Rally testing framework would need to be "
-"handled in the appropriate manner in launch script. This would ideally "
-"result in new functions that could be reused, or expansion of the gate "
-"scripts to include scenarios beyond basic service launches."
-msgstr ""
-"Setiap tes yang tidak menggunakan kerangka pengujian Rally harus ditangani "
-"dengan cara yang sesuai dalam skrip peluncuran. Ini idealnya menghasilkan "
-"fungsi baru yang dapat digunakan kembali, atau perluasan skrip gate untuk "
-"memasukkan skenario di luar peluncuran layanan dasar."
-
-msgid ""
-"As charts for additional services are added to OpenStack-Helm, they should "
-"be included in the gates.  Adding new services to the gates allows a chart "
-"developer and the review team to identify any potential issues associated "
-"with a new service. All services are currently launched in the gate via a "
-"series of launch scripts of the format ``NNN-service-name.sh`` where ``NNN`` "
-"dictates the order these scripts are launched. The script should contain an "
-"installation command like:"
-msgstr ""
-"Karena chart untuk layanan tambahan ditambahkan ke OpenStack-Helm, mereka "
-"harus dimasukkan ke dalam gate. Menambahkan layanan baru ke gate "
-"memungkinkan pengembang chart dan tim peninjau untuk mengidentifikasi setiap "
-"potensi masalah yang terkait dengan layanan baru. Semua layanan saat ini "
-"diluncurkan di gate melalui serangkaian skrip peluncuran format ``NNN-"
-"service-name.sh`` dimana ``NNN`` mendikte perintah skrip ini diluncurkan. "
-"Skrip harus berisi perintah pemasangan seperti:"
-
-msgid ""
-"As new charts are developed and the services are added to the gate, an "
-"associated Helm test should be introduced to the gates.  The appropriate "
-"place for executing these tests is in the respective service's launch "
-"script, and must be placed after the entry for installing the service and "
-"any associated overrides.  Any tests that use the Rally testing framework "
-"should leverage the helm_test_deployment function in the aforementioned "
-"funcs/helm.sh file. For example, a Helm test for Mistral might look like:"
-msgstr ""
-"Ketika chart baru dikembangkan dan layanan ditambahkan ke gate, tes Helm "
-"yang terkait harus diperkenalkan ke gate. Tempat yang tepat untuk "
-"mengeksekusi tes ini adalah di skrip peluncuran layanan masing-masing, dan "
-"harus ditempatkan setelah entri untuk menginstal layanan dan menimpa yang "
-"terkait. Setiap tes yang menggunakan kerangka pengujian Rally harus "
-"memanfaatkan fungsi helm_test_deployment di file funcs/helm.sh yang "
-"disebutkan di atas. Misalnya, tes Helm untuk Mistral mungkin terlihat "
-"seperti:"
-
-msgid ""
-"Bugs and enhancements are tracked via OpenStack-Helm's `Storyboard <https://"
-"storyboard.openstack.org/#!/project_group/64>`_."
-msgstr ""
-"Bug dan perangkat tambahan dilacak via OpenStack-Helm's `Storyboard <https://"
-"storyboard.openstack.org/#!/project_group/64>`_."
-
-msgid "Communication"
-msgstr "Komunikasi"
-
-msgid "Contents:"
-msgstr "Isi:"
-
-msgid "Contributing"
-msgstr "Berkontribusi"
-
-msgid ""
-"Developers wishing to work on the OpenStack-Helm project should always base "
-"their work on the latest code, available from the OpenStack-Helm git "
-"repository."
-msgstr ""
-"Pengembang yang ingin bekerja pada proyek OpenStack-Helm harus selalu "
-"mendasarkan pekerjaan mereka pada kode terbaru, tersedia dari repositori git "
-"OpenStack-Helm."
-
-msgid ""
-"Functions for Helm specific operations, found in helm.sh.  These functions "
-"include: installing Helm, serving a Helm repository locally, linting and "
-"building all Helm charts, running Helm tests on a release, installing the "
-"helm template plugin, and running the helm template plugin against a chart."
-msgstr ""
-"Fungsi untuk operasi khusus Helm, ditemukan di helm.sh. Fungsi-fungsi ini "
-"meliputi: memasang Helm, melayani repositori Helm secara lokal, membuat "
-"linting dan membangun semua Helm chart, menjalankan tes Helm pada rilis, "
-"menginstal plugin template kemudi, dan menjalankan plugin template helm "
-"terhadap chart."
-
-msgid ""
-"Functions for Kubernetes specific operations, found in kube.sh.  These "
-"functions include: waiting for pods in a specific namespace to register as "
-"ready, waiting for all nodes to register as ready, install the requirements "
-"for the kubeadm-aio container used in the gates, building the kubeadm-aio "
-"container, launching the kubeadm-aio container, and replacing the kube-"
-"controller-manager with a specific image necessary for ceph functionality."
-msgstr ""
-"Fungsi untuk Kubernetes operasi spesifik, ditemukan di kube.sh. Fungsi-"
-"fungsi ini meliputi: menunggu pod dalam namespace tertentu untuk mendaftar "
-"sebagai siap (ready), menunggu semua node untuk mendaftar sebagai siap, "
-"menginstal persyaratan untuk kontainer kubeadm-aio yang digunakan di gate, "
-"membangun kontainer kubeadm-aio, meluncurkan kontainer kubeadm- aio, dan "
-"mengganti kube-controller-manager dengan image spesifik yang diperlukan "
-"untuk fungsi ceph."
-
-msgid ""
-"Functions for OpenStack specific operations, found in openstack.sh.  These "
-"functions include: waiting for a successful ping, and waiting for a booted "
-"virtual machine's status to return as ACTIVE."
-msgstr ""
-"Fungsi untuk operasi spesifik OpenStack, ditemukan di openstack.sh. Fungsi-"
-"fungsi ini meliputi: menunggu ping yang berhasil, dan menunggu status mesin "
-"virtual boot untuk kembali sebagai AKTIF."
-
-msgid "Functions for common host preparation operations, found in common.sh"
-msgstr "Fungsi untuk operasi persiapan host umum, ditemukan di common.sh"
-
-msgid ""
-"Functions for network specific operations, found in network.sh.  These "
-"functions include: creating a backup of the host's resolv.conf file before "
-"deploying the kubeadm environments, restoring the original resolv.conf "
-"settings, creating a backup of the host's /etc/hosts file before adding the "
-"hosts interface and address, and restoring the original /etc/hosts file."
-msgstr ""
-"Fungsi untuk operasi spesifik jaringan, ditemukan di network.sh. Fungsi-"
-"fungsi ini meliputi: membuat cadangan file resolv.conf host sebelum "
-"menyebarkan lingkungan kubeadm, memulihkan pengaturan resolv.conf asli, "
-"membuat cadangan file /etc/hosts milik  host sebelum menambahkan antarmuka "
-"dan alamat host, dan memulihkan file /etc/hosts asli."
-
-msgid "Gate Checks"
-msgstr "Gate Checks (pemeriksaan gate)"
-
-msgid "Gate Functions"
-msgstr "Gate Functions (fungsi gate)"
-
-msgid "Gate Output"
-msgstr "Gate Output"
-
-msgid "Indices and Tables"
-msgstr "Indeks dan Tabel"
-
-msgid "Installation and Development"
-msgstr "Instalasi dan Pengembangan"
-
-msgid ""
-"Join us on `Slack <https://kubernetes.slack.com/messages/C3WERB7DE/>`_ - "
-"#openstack-helm"
-msgstr ""
-"Bergabunglah dengan kami `Slack <https://kubernetes.slack.com/messages/"
-"C3WERB7DE/>`_ - #openstack-helm"
-
-msgid ""
-"Meeting Agenda Items: `Agenda <https://etherpad.openstack.org/p/openstack-"
-"helm-meeting-agenda>`_"
-msgstr ""
-"Item Agenda Rapat: `Agenda <https://etherpad.openstack.org/p/openstack-helm-"
-"meeting-agenda>`_"
-
-msgid "Mission"
-msgstr "Misi"
-
-msgid "OpenStack-Helm"
-msgstr "OpenStack-Helm"
-
-msgid "OpenStack-Helm Gates"
-msgstr "OpenStack-Helm Gates"
-
-msgid "OpenStack-Helm currently checks the following scenarios:"
-msgstr "OpenStack-Helm saat ini memeriksa skenario berikut:"
-
-msgid ""
-"OpenStack-Helm's single node and multinode gates leverage the kubeadm-aio "
-"environment created and maintained for use as a development environment.  "
-"All information regarding the kubeadm-aio environment can be found here_."
-msgstr ""
-"Node tunggal OpenStack-Helm dan gate multinode memanfaatkan lingkungan "
-"kubeadm-aio yang dibuat dan dipelihara untuk digunakan sebagai lingkungan "
-"pengembangan. Semua informasi mengenai lingkungan kubeadm-aio dapat "
-"ditemukan di sini_."
-
-msgid ""
-"Provisioning a multi-node Ubuntu-1604 cluster and deploying the OpenStack "
-"services. This check is provided for both a two node cluster and a three "
-"node cluster."
-msgstr ""
-"Menyediakan multi-node klaster Ubuntu-1604 dan menyebarkan layanan "
-"OpenStack. Pemeriksaan ini disediakan untuk dua klaster node dan tiga "
-"klaster node."
-
-msgid ""
-"Provisioning a single node cluster and deploying the OpenStack services.  "
-"This check is provided for: Ubuntu-1604, CentOS-7, and Fedora-25."
-msgstr ""
-"Menyediakan satu klaster node dan menyebarkan layanan OpenStack. Pemeriksaan "
-"ini disediakan untuk: Ubuntu-1604, CentOS-7, dan Fedora-25."
-
-msgid "Repository"
-msgstr "Repository (repositori)"
-
-msgid ""
-"Running Make on each chart, which lints and packages the charts.  This gate "
-"does not stand up a Kubernetes cluster."
-msgstr ""
-"Menjalankan Make pada setiap chart, yang lint dan package chart. Gate ini "
-"tidak memiliki kluster Kubernetes."
-
-msgid ""
-"Some services in the gate require specific overrides to the default values "
-"in the chart's values.yaml file.  If a service requires multiple overrides "
-"to function in the gate, the service should include a separate values.yaml "
-"file placed in the tools/overrides/mvp directory.  The <service>.yaml MVP "
-"files provide a configuration file to use for overriding default "
-"configuration values in the chart's values.yaml as an alternative to "
-"overriding individual values during installation.  A chart that requires a "
-"MVP overrides file requires the following format:"
-msgstr ""
-"Beberapa layanan di gate memerlukan pengunggahan spesifik ke nilai default "
-"di file values.yaml chart. Jika suatu layanan memerlukan beberapa override "
-"untuk berfungsi di gate, layanan harus menyertakan file values.yaml yang "
-"terpisah yang ditempatkan di direktori tools/overrides/mvp. File MVP "
-"<service>.yaml menyediakan file konfigurasi yang digunakan untuk "
-"mengesampingkan nilai konfigurasi default di values.yaml milik chart sebagai "
-"alternatif untuk menimpa nilai individual selama instalasi. Sebuah chart "
-"yang membutuhkan file menimpa MVP membutuhkan format berikut:"
-
-msgid "Storyboard"
-msgstr "Storyboard (papan cerita)"
-
-msgid "Testing any documentation changes and impacts."
-msgstr "Menguji perubahan dan dampak dokumentasi apa pun."
-
-msgid ""
-"The K8s directory contains the logs and output of the Kubernetes objects.  "
-"It includes: pods, nodes, secrets, services, namespaces, configmaps, "
-"deployments, daemonsets, and statefulsets.  Descriptions for the state of "
-"all resources during execution are found here, and this information can "
-"prove valuable when debugging issues raised during a check.  When a single "
-"node or multi-node check fails, this is the first place to look.  The logs "
-"found here are helpful when the templates render correctly, but the services "
-"are not functioning correctly, whether due to service configuration issues "
-"or issues with the pods themselves."
-msgstr ""
-"Direktori K8s berisi log dan output dari objek Kubernetes. Ini termasuk: "
-"pod, node, rahasia, layanan, namespace, configaps, penyebaran, daemon, dan "
-"statefulset. Deskripsi untuk keadaan semua sumber daya selama eksekusi "
-"ditemukan di sini, dan informasi ini dapat terbukti bermanfaat ketika "
-"masalah debug dinaikkan selama pemeriksaan. Ketika pemeriksaan node tunggal "
-"atau multi-node gagal, ini adalah tempat pertama untuk melihat. Log yang "
-"ditemukan di sini bermanfaat ketika template dirender dengan benar, tetapi "
-"layanan tidak berfungsi dengan benar, baik karena masalah konfigurasi "
-"layanan atau masalah dengan pod itu sendiri."
-
-msgid ""
-"The dry-runs directory contains the rendered output of Helm dry-run installs "
-"on each of the OpenStack service charts.  This gives visibility into the "
-"manifests created by the templates with the supplied values.  When the dry-"
-"run gate fails, the reason should be apparent in the dry-runs output.  The "
-"logs found here are helpful in identifying issues resulting from using helm-"
-"toolkit functions incorrectly or other rendering issues with gotpl."
-msgstr ""
-"Direktori dry-run berisi output yang diberikan dari pemasangan Helm dry-run "
-"pada masing-masing chart layanan OpenStack. Ini memberikan visibilitas ke "
-"manifes yang dibuat oleh template dengan nilai yang disediakan. Ketika gate "
-"dry-run gagal, alasannya harus jelas dalam output dry-run. Log ditemukan di "
-"sini sangat membantu dalam mengidentifikasi masalah yang dihasilkan dari "
-"penggunaan fungsi-fungsi helm-toolkit yang salah atau masalah rendering "
-"lainnya dengan gotpl."
-
-msgid ""
-"The goal of OpenStack-Helm is to provide a collection of Helm charts that "
-"simply, resiliently, and flexibly deploy OpenStack and related services on "
-"Kubernetes."
-msgstr ""
-"Tujuan OpenStack-Helm adalah untuk menyediakan koleksi grafik Helm yang "
-"sederhana, tangguh, dan secara fleksibel menggunakan OpenStack dan layanan "
-"terkait di Kubernetes."
-
-msgid ""
-"The nodes directory contains information about the node the gate tests are "
-"running on in openstack-infra.  This includes: the network interfaces, the "
-"contents of iptables, the host's resolv.conf, and the kernel IP routing "
-"table. These logs can be helpful when trying to identify issues with host "
-"networking or other issues at the node level."
-msgstr ""
-"Direktori node berisi informasi tentang node dimana gate test sedang "
-"berjalan di openstack-infra. Ini termasuk: antarmuka jaringan, isi iptables, "
-"resolv.conf host, dan tabel routing IP kernel. Log ini dapat membantu ketika "
-"mencoba mengidentifikasi masalah dengan jaringan host atau masalah lain di "
-"tingkat node."
-
-msgid ""
-"This project is under active development. We encourage anyone interested in "
-"OpenStack-Helm to review our `Installation <https://docs.openstack.org/"
-"openstack-helm/latest/install/index.html>`_ documentation. Feel free to ask "
-"questions or check out our current `Storyboard backlog <https://storyboard."
-"openstack.org/#!/project_group/64>`_."
-msgstr ""
-"Proyek ini sedang dalam pengembangan aktif. Kami mendorong siapa pun yang "
-"tertarik dengan OpenStack-Helm untuk meninjau dokumentasi kami `Installation "
-"<https://docs.openstack.org/openstack-helm/latest/install/index.html>`_. "
-"Jangan ragu untuk bertanya atau memeriksa saat ini `Storyboard backlog "
-"<https://storyboard.openstack.org/#!/project_group/64>`_."
-
-msgid "This results in the gate running the following:"
-msgstr "Ini menghasilkan gate menjalankan berikut:"
-
-msgid ""
-"To evaluate a multinode installation, follow the `Bare Metal <https://docs."
-"openstack.org/openstack-helm/latest/install/multinode.html>`_ install guide."
-msgstr ""
-"Untuk mengevaluasi instalasi multinode, ikuti panduan pemasangan `Bare Metal "
-"<https://docs.openstack.org/openstack-helm/latest/install/multinode.html>` _."
-
-msgid ""
-"To facilitate ease of testing and debugging, information regarding gates and "
-"their functionality can be found here."
-msgstr ""
-"Untuk memfasilitasi kemudahan pengujian dan debugging, informasi mengenai "
-"gate dan fungsinya dapat ditemukan di sini."
-
-msgid ""
-"To provide meaningful output from the gates, all information pertaining to "
-"the components of the cluster and workflow are output to the logs directory "
-"inside each gate.  The contents of the log directory are as follows:"
-msgstr ""
-"Untuk memberikan output yang berarti dari gate, semua informasi yang "
-"berkaitan dengan komponen cluster dan alur kerja adalah output ke direktori "
-"log di dalam setiap gate. Isi dari direktori log adalah sebagai berikut:"
-
-msgid ""
-"To provide reusable components for gate functionality, functions have been "
-"provided in the gates/funcs directory. These functions include:"
-msgstr ""
-"Untuk menyediakan komponen yang dapat digunakan kembali untuk fungsi gate, "
-"fungsi telah disediakan di direktori gates/funcs. Fungsi-fungsi ini termasuk:"
-
-msgid ""
-"We welcome contributions. Check out `this <CONTRIBUTING.rst>`_ document if "
-"you would like to get involved."
-msgstr ""
-"Kami menyambut kontribusi. Lihatlah dokumen `CONTRIBUTING.rst>` _ ini jika "
-"Anda ingin terlibat."
-
-msgid "Welcome to OpenStack-Helm's documentation!"
-msgstr "Selamat datang di dokumentasi OpenStack-Helm!"
-
-msgid ""
-"`OpenStack-Helm git repository <https://opendev.org/openstack/openstack-helm/"
-">`_"
-msgstr ""
-"`OpenStack-Helm git repository <https://opendev.org/openstack/openstack-helm/"
-">`_"
diff --git a/doc/source/locale/ko_KR/LC_MESSAGES/doc-devref.po b/doc/source/locale/ko_KR/LC_MESSAGES/doc-devref.po
deleted file mode 100644
index 041ee3523f..0000000000
--- a/doc/source/locale/ko_KR/LC_MESSAGES/doc-devref.po
+++ /dev/null
@@ -1,891 +0,0 @@
-# Soonyeul Park <ardentpark@gmail.com>, 2018. #zanata
-# Sungjin Kang <gang.sungjin@gmail.com>, 2018. #zanata
-# Sungjin Kang <gang.sungjin@gmail.com>, 2019. #zanata
-msgid ""
-msgstr ""
-"Project-Id-Version: openstack-helm 0.1.1.dev3631\n"
-"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2022-02-23 21:11+0000\n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-"PO-Revision-Date: 2019-03-19 09:34+0000\n"
-"Last-Translator: Sungjin Kang <gang.sungjin@gmail.com>\n"
-"Language-Team: Korean (South Korea)\n"
-"Language: ko_KR\n"
-"X-Generator: Zanata 4.3.3\n"
-"Plural-Forms: nplurals=1; plural=0\n"
-
-msgid ""
-"**Note:** The values defined in a PodDisruptionBudget may conflict with "
-"other values that have been provided if an operator chooses to leverage "
-"Rolling Updates for deployments.  In the case where an operator defines a "
-"``maxUnavailable`` and ``maxSurge`` within an update strategy that is higher "
-"than a ``minAvailable`` within a pod disruption budget, a scenario may occur "
-"where pods fail to be evicted from a deployment."
-msgstr ""
-"**참고:** PodDisruptionBudget 에 정의된 값들은 운영자가 배포를 위한 롤링 업데"
-"이트를 활용하도록 선택한 경우 제공되는 다른 값들과 충돌할 수 있습니다. 운영자"
-"가 pod 중단 비용에서의 ``minAvailable`` 보다 큰 ``maxUnavailable`` 과 "
-"``maxSurge`` 를 업데이트 전략으로 정의한 경우, 배포에서 pod가 제거되지 않는 "
-"시나리오가 발생할 수 있습니다."
-
-msgid ""
-":code:`neutron/templates/bin/_neutron-linuxbridge-agent-init.sh.tpl` is "
-"configuring the tunnel IP, external bridge and all bridge mappings defined "
-"in config. It is done in init container, and the IP for tunneling is shared "
-"using file :code:`/tmp/pod-shared/ml2-local-ip.ini` with main linuxbridge "
-"container."
-msgstr ""
-":code:`neutron/templates/bin/_neutron-linuxbridge-agent-init.sh.tpl`은 터널 "
-"IP, 외부 브리지, 그리고 config에 정의된 모든 브리지 매핑을 구성합니다.그것은 "
-"init 컨테이너에서 완료되고, 터널링을 위한 IP는 :code:`/tmp/pod-shared/ml2-"
-"local-ip.ini` 파일을 사용하여 linuxbridge 컨테이너와 공유됩니다."
-
-msgid ""
-"A detail worth mentioning is that ovs is configured to use sockets, rather "
-"than the default loopback mechanism."
-msgstr ""
-"언급할 가치가 있는 세부사항은 ovs가 기본 루프백 메커니즘 대신에 소켓을 사용하"
-"여 구성된다는 것입니다. "
-
-msgid ""
-"A long-term goal, besides being image agnostic, is to also be able to "
-"support any of the container runtimes that Kubernetes supports, even those "
-"that might not use Docker's own packaging format. This will allow the "
-"project to continue to offer maximum flexibility with regard to operator "
-"choice."
-msgstr ""
-"이미지에서 자유로워지는 것 외에도 장기 목표는 Kubernetes가 지원하는 모든 컨테"
-"이너 런타임도 지원할 수 있으며, Docker의 자체 패키징 포맷을 사용하지 않는 컨"
-"테이너 런타임도 지원할 수 있습니다. 이는 프로젝트에 운영자의 선택과 관련하여 "
-"최대한의 유연성을 허용할 것입니다."
-
-msgid ""
-"All ``Deployment`` chart components are outfitted by default with rolling "
-"update strategies:"
-msgstr ""
-"모든 ``Deployment`` 차트 구성요소는 기본적으로 롤링 업데이트 전략으로 갖춰집"
-"니다:"
-
-msgid "All dependencies described in neutron-dhcp-agent are valid here."
-msgstr "neutron-dhcp-agent에 서술된 모든 의존성은 여기에서 유효합니다."
-
-msgid ""
-"All of the above configs are endpoints or path to the specific class "
-"implementing the interface. You can see the endpoints to class mapping in "
-"`setup.cfg <https://github.com/openstack/neutron/"
-"blob/412c49b3930ce8aecb0a07aec50a9607058e5bc7/setup.cfg#L69>`_."
-msgstr ""
-"위의 모든 구성은 인터페이스를 구현하는 특정 클래스에 대한 endpoints나 경로입"
-"니다. `setup.cfg <https://github.com/openstack/neutron/"
-"blob/412c49b3930ce8aecb0a07aec50a9607058e5bc7/setup.cfg#L69>`_에서 클래스 매"
-"핑에 대한 endpoints를 볼 수 있습니다."
-
-msgid ""
-"An illustrative example of an ``images:`` section taken from the heat chart:"
-msgstr "heat 차트에서 가져온 ``images:`` 섹션의 실제 사례:"
-
-msgid ""
-"Another place where the DHCP agent is dependent on L2 agent is the "
-"dependency for the L2 agent daemonset:"
-msgstr ""
-"DHCP 에이전트가 L2 에이전트에 종속된 위치는 L2 에이전트 deamonset에 대한 종속"
-"성입니다:"
-
-msgid ""
-"As part of Neutron chart, this daemonset is running Neutron OVS agent. It is "
-"dependent on having :code:`openvswitch-db` and :code:`openvswitch-vswitchd` "
-"deployed and ready. Since its the default choice of the networking backend, "
-"all configuration is in place in `neutron/values.yaml`. :code:`neutron-ovs-"
-"agent` should not be deployed when another SDN is used in `network.backend`."
-msgstr ""
-"Neutron 차트의 일부로서, 이 데몬세트는 Neutron OVS 에이전트를 실행 중입니다. "
-"그것은 :code:`openvswitch-db`와 :code:`openvswitch-vswitchd`를 배포하고 준비"
-"하는데 의존합니다. 네트워킹 백엔드 기본 선택이기 때문에, 모든 구성은 "
-"`neutron/values.yaml`에 위치합니다. 다른 SDN이 `network.backend`에서 사용될 "
-"때 :code:`neutron-ovs-agent`를 배포해서는 안됩니다."
-
-msgid ""
-"By default, each endpoint is located in the same namespace as the current "
-"service's helm chart. To connect to a service which is running in a "
-"different Kubernetes namespace, a ``namespace`` can be provided for each "
-"individual endpoint."
-msgstr ""
-"기본적으로, 각 endpoint는 현재 서비스의 helm 차트와 같은 네임스페이스에 위치"
-"합니다. 다른 Kubernetes 네임 스페이스에서 실행중인 서비스에 연결하여 각 "
-"endpoint에 ``namespace`` 를 제공할 수 있습니다."
-
-msgid ""
-"Charts should not use hard coded values such as ``http://keystone-api:5000`` "
-"because these are not compatible with operator overrides and do not support "
-"spreading components out over various namespaces."
-msgstr ""
-"차트는 ``http://keystone-api:5000`` 과 같은 하드 코딩된 값을 사용하면 안됩니"
-"다. 왜냐하면 이 값들은 운영자의 오버라이드와 호환되지 않으며 다양한 네임스페"
-"이스로 확장되는 구성요소들을 지원하지 않기 때문입니다."
-
-msgid ""
-"Configuration of OVS bridges can be done via `neutron/templates/bin/_neutron-"
-"openvswitch-agent-init.sh.tpl`. The script is configuring the external "
-"network bridge and sets up any bridge mappings defined in :code:`conf."
-"auto_bridge_add`.  These values should align with :code:`conf.plugins."
-"openvswitch_agent.ovs.bridge_mappings`."
-msgstr ""
-"OVS 브릿지 구성은 `neutron/templates/bin/_neutron-openvswitch-agent-init.sh."
-"tpl`에서 할 수 있습니다. 이 스크립트는 외부 네트워크 브릿지를 구성하고, :"
-"code:`conf.auto_bridge_add` 에서 정의하는 브릿지 매핑을 설정합니다. 이 값들"
-"은 :code:`conf.plugins.openvswitch_agent.ovs.bridge_mappings`와 같아야합니다."
-
-msgid ""
-"Configure neutron-server with SDN specific core_plugin/mechanism_drivers."
-msgstr ""
-"SDN 특정 core_plugin/mechanism_drivers를 사용하여 neutron-server를 구성하십시"
-"오."
-
-msgid "Configuring network plugin"
-msgstr "네트워크 플러그인 구성"
-
-msgid "Contents:"
-msgstr "목차:"
-
-msgid "Create separate chart with new SDN deployment method."
-msgstr "새로운 SDN 배포 방법으로 별도의 차트를 생성하십시오."
-
-msgid ""
-"Currently OpenStack-Helm supports OpenVSwitch and LinuxBridge as a network "
-"virtualization engines. In order to support many possible backends (SDNs), "
-"modular architecture of Neutron chart was developed. OpenStack-Helm can "
-"support every SDN solution that has Neutron plugin, either core_plugin or "
-"mechanism_driver."
-msgstr ""
-"현재 OpenStack-Helm은 OpenVSwitch 및 LinuxBridge를 네트워크 가상화 엔진으로 "
-"지원합니다. 가능한 많은 backend(SDNs)들을 지원하기 위해, Neutron 차트의 모듈"
-"식 구조가 개발되었습니다. OpenStack-Helm은 core_plugin 또는 mechanism_driver"
-"인 Neutron 플러그인이 있는 모든 SDN 솔루션을 지원할 수 있습니다."
-
-msgid "DHCP - auto-assign IP address and DNS info"
-msgstr "DHCP - IP 주소와 DNS 정보 자동 할당"
-
-msgid ""
-"DHCP agent is running dnsmasq process which is serving the IP assignment and "
-"DNS info. DHCP agent is dependent on the L2 agent wiring the interface. So "
-"one should be aware that when changing the L2 agent, it also needs to be "
-"changed in the DHCP agent. The configuration of the DHCP agent includes "
-"option `interface_driver`, which will instruct how the tap interface created "
-"for serving the request should be wired."
-msgstr ""
-"DHCP 에이전트가 IP 할당 및 DNS 정보를 제공하는 dnsmasq 프로세스를 실행 중입니"
-"다. DHCP 에이전트는 인터페이스를 연결하는 L2 에이전트에 의존합니다. 그래서 "
-"L2 에이전트를 변경할 때 DHCP 에이전트에서 알고 있어야 하고, 또한 DHCP 에이전"
-"트에서 변경될 필요가 있습니다. DHCP 에이전트 구성은 요청을 제공하기 위해 생성"
-"된 탭 인터페이스가 어떻게 연결되어야 할지 지시할 interface_driver 옵션을 포함"
-"합니다."
-
-msgid "Developer References"
-msgstr "개발자 참고자료"
-
-msgid ""
-"EFK (Elasticsearch, Fluent-bit & Fluentd, Kibana) based Logging Mechanism"
-msgstr "EFK (Elasticsearch, Fluent-bit & Fluentd, Kibana) 기반 로깅 매커니즘"
-
-msgid "Endpoints"
-msgstr "Endpoints"
-
-msgid ""
-"Fluent-bit, Fluentd meet OpenStack-Helm's logging requirements for "
-"gathering, aggregating, and delivering of logged events. Fluent-bit runs as "
-"a daemonset on each node and mounts the `/var/lib/docker/containers` "
-"directory. The Docker container runtime engine directs events posted to "
-"stdout and stderr to this directory on the host. Fluent-bit then forward the "
-"contents of that directory to Fluentd. Fluentd runs as deployment at the "
-"designated nodes and expose service for Fluent-bit to forward logs. Fluentd "
-"should then apply the Logstash format to the logs. Fluentd can also write "
-"kubernetes and OpenStack metadata to the logs. Fluentd will then forward the "
-"results to Elasticsearch and to optionally Kafka. Elasticsearch indexes the "
-"logs in a logstash-* index by default. Kafka stores the logs in a ``logs`` "
-"topic by default. Any external tool can then consume the ``logs`` topic."
-msgstr ""
-"Fluent-bit, Fluentd는 기록된 이벤트의 수집, 집계, 그리고 전달을 위한 로깅 요"
-"구사항을 충족합니다. Fluent-bit는 각 노드에서 daemonset으로 실행하고 `/var/"
-"lib/docker/containers` 디렉터리를 마운트합니다. Docker 컨테이너 런타임 엔진"
-"은 stdout과 stderr에 게시된 이벤트를 호스트의 상기 디렉터리로 보냅니다. 그런 "
-"다음 Fluent-bit는 해당 디렉터리의 내용을 Fluentd로 전달합니다. Fluentd는 지정"
-"된 노드에서 배포로 동작하고 Fluent-bit의 전달 로그로 서비스를 표시합니다. 그"
-"런 다음 Fluentd는 Logstash 포맷을 로그에 적용해야 합니다. Fluentd는 또한 "
-"kubernetes와 OpenStack의 메타데이터를 로그에 작성합니다. Fluentd는 그 결과를 "
-"Elasticsearch와 선택적으로 Kafka에 전달합니다. Elasticsearch는 기본적으로 로"
-"그를 logstash-*로 색인합니다. Kafka는 기본적으로 로그를 ``logs`` 주제로 보관"
-"합니다. 그러면 외부 도구가 ``logs`` 주제를 사용할 수 있습니다."
-
-msgid ""
-"For instance, in the Neutron chart ``values.yaml`` the following endpoints "
-"are defined:"
-msgstr ""
-"예를 들어, Neutron 차트 ``values.yaml`` 에서 다음과 같은 endpoints가 정의됩니"
-"다:"
-
-msgid "Host overrides supercede label overrides"
-msgstr "호스트가 대체 라벨의 오버라이드를 오버라이드합니다."
-
-msgid ""
-"If :code:`.Values.manifests.daemonset_ovs_agent` will be set to false, "
-"neutron ovs agent would not be launched. In that matter, other type of L2 or "
-"L3 agent on compute node can be run."
-msgstr ""
-":code:`.Values.manifests.daemonset_ovs_agent` 가 false로 설정된다면, neutron "
-"ovs 에이전트는 시작되지 않을 것입니다. 그 때, 컴퓨트 노드의 다른 타입의 L2나 "
-"L3 에이전트가 실행됩니다."
-
-msgid "If required, add new networking agent label type."
-msgstr "필요하다면, 새로운 네트워킹 에이전트 라벨 타입을 추가하십시오."
-
-msgid ""
-"If the SDN implements its own version of L3 networking, neutron-l3-agent "
-"should not be started."
-msgstr ""
-"SDN이 L3 네트워킹의 한 버전을 구현한다면, neutron-l3-agent는 시작되어서는 안"
-"됩니다."
-
-msgid ""
-"If the SDN of your choice is using the ML2 core plugin, then the extra "
-"options in `neutron/ml2/plugins/ml2_conf.ini` should be configured:"
-msgstr ""
-"선택한 SDN이 ML2 코어 플러그인을 사용하고 있다면, `neutron/ml2/plugins/"
-"ml2_conf.ini` 의 추가 옵션이 구성되어야 합니다:"
-
-msgid "Images"
-msgstr "이미지"
-
-msgid ""
-"In ``values.yaml`` in each chart, the same defaults are supplied in every "
-"chart, which allows the operator to override at upgrade or deployment time."
-msgstr ""
-"각 차트의 ``values.yaml`` 에는, 업그레이드나 배포 시기에 운영자의 오버라이드"
-"가 허용되는 동일한 기본값이 모든 차트에 제공됩니다."
-
-msgid ""
-"In order to add support for more SDNs, these steps need to be performed:"
-msgstr "더 많은 SDN들을 추가하기 위해서, 이 과정들을 수행할 필요가 있습니다:"
-
-msgid ""
-"In order to meet modularity criteria of Neutron chart, section `manifests` "
-"in :code:`neutron/values.yaml` contains boolean values describing which "
-"Neutron's Kubernetes resources should be deployed:"
-msgstr ""
-"Neutron 차트의 모듈성 기준을 충족하기 위해서, :code:`neutron/values.yaml`의 "
-"섹션 매니페스트는 어떤 Neutron의 Kubernetes 리소스가 배포되어야 하는지 서술하"
-"는 boolean 값들을 포함하고 있습니다:"
-
-msgid ""
-"In order to use linuxbridge in your OpenStack-Helm deployment, you need to "
-"label the compute and controller/network nodes with `linuxbridge=enabled` "
-"and use this `neutron/values.yaml` override:"
-msgstr ""
-"OpenStack-Helm 배치에서 linuxbridge를 사용하기 위해, compute와 controller/"
-"network 노드를 `linuxbridge=enabled`로 라벨할 필요가 있고 이것을 `neutron/"
-"values.yaml`에 오버라이드하여 사용합니다."
-
-msgid ""
-"Introducing a new SDN solution should consider how the above services are "
-"provided. It maybe required to disable built-in Neutron functionality."
-msgstr ""
-"새로운 SDN 솔루션 도입은 위의 서비스가 어떻게 제공되는지를 고려해야합니다. "
-"Neutron 내장 함수를 비활성화가 필요할 수도 있습니다."
-
-msgid ""
-"L3 agent is serving the routing capabilities for Neutron networks. It is "
-"also dependent on the L2 agent wiring the tap interface for the routers."
-msgstr ""
-"L3 에이전트는 Neutron 네트워크를 위한 라우팅 능력을 제공하고 있습니다. 또한 "
-"라우터를 위한 탭 인터페이스를 연결하는 L2 에이전트에 의존합니다."
-
-msgid "L3 routing - creation of routers"
-msgstr "L3 라우팅 - 라우터 생성"
-
-msgid "Linuxbridge"
-msgstr "Linuxbridge"
-
-msgid ""
-"Linuxbridge is the second type of Neutron reference architecture L2 agent. "
-"It is running on nodes labeled `linuxbridge=enabled`. As mentioned before, "
-"all nodes that are requiring the L2 services need to be labeled with "
-"linuxbridge. This includes both the compute and controller/network nodes. It "
-"is not possible to label the same node with both openvswitch and linuxbridge "
-"(or any other network virtualization technology) at the same time."
-msgstr ""
-"Linuxbridge는 Neutron 참조 구조 L2 에이전트의 두 번째 타입입니다. 그것은 "
-"`linuxbridge=enabled`로 라벨된 노드에서 실행 중입니다. 앞서 언급했듯이, L2 서"
-"비스를 요구하는 모든 노드는 linuxbridge로 라벨될 필요가 있습니다. 이는 "
-"compute와 controller/network 노드 모두를 포함합니다. 같은 노드에 openvswitch"
-"와 linuxbridge (또는 다른 네트워크 가상화 기술)를 동시에 라벨하는 것은 불가능"
-"합니다."
-
-msgid "Logging Mechanism"
-msgstr "로깅 매커니즘"
-
-msgid "Logging Requirements"
-msgstr "로깅 요구사항"
-
-msgid "Metadata - Provide proxy for Nova metadata service"
-msgstr "메타데이터 - Nova 메타데이터 서비스를 위한 프록시 제공"
-
-msgid ""
-"Metadata-agent is a proxy to nova-metadata service. This one provides "
-"information about public IP, hostname, ssh keys, and any tenant specific "
-"information. The same dependencies apply for metadata as it is for DHCP and "
-"L3 agents. Other SDNs may require to force the config driver in nova, since "
-"the metadata service is not exposed by it."
-msgstr ""
-"Metadata-agent는 nova-metadata 서비스에 대한 프록시입니다. 이것은 공용 IP, 호"
-"스트명, ssh 키, 그리고 tenant 특정 정보에 대한 정보를 제공합니다. DHCP와 L3 "
-"에이전트와 마찬가지로 메타데이터에도 동일한 의존성을 적용합니다. 다른 SDN은 "
-"메타데이터 서비스가 노출되어 있지 않으므로 nova에서 드라이버 구성을 강제할 것"
-"을 요구할지도 모릅니다."
-
-msgid "Networking"
-msgstr "네트워킹"
-
-msgid "Neutron architecture"
-msgstr "Neutron 구조"
-
-msgid "Neutron chart includes the following services:"
-msgstr "Neutron 차트는 다음의 서비스들을 포함합니다:"
-
-msgid ""
-"Neutron-server service is scheduled on nodes with `openstack-control-"
-"plane=enabled` label."
-msgstr ""
-"Neutron-server 서비스는 `openstack-control-plane=enabled` 라벨로 노드에 스케"
-"줄됩니다."
-
-msgid "Note that only one set of overrides is applied per node, such that:"
-msgstr ""
-"노드마다 다음과 같이 단 하나의 오버라이드 세트만 적용되는 점을 참고하십시오:"
-
-msgid ""
-"Note that some additional values have been injected into the config file, "
-"this is performed via statements in the configmap template, which also calls "
-"the ``helm-toolkit.utils.to_oslo_conf`` to convert the yaml to the required "
-"layout:"
-msgstr ""
-"구성 파일에 몇 가지 추가 값들이 주입되었음을 참고하십시오, 이는 configmap 템"
-"플릿의 문장을 통해 수행되며, 또한 yaml을 필요한 레이아웃으로 변환하기 위해 "
-"``helm-toolkit.utils.to_oslo_conf`` 를 호출합니다:"
-
-msgid ""
-"Note: Rolling update values can conflict with values defined in each "
-"service's PodDisruptionBudget.  See `here <https://docs.openstack.org/"
-"openstack-helm/latest/devref/pod-disruption-budgets.html>`_ for more "
-"information."
-msgstr ""
-"참고: 롤링 업데이트 값은 각 서비스의 PodDisruptionBudget에 정의된 값들과 충돌"
-"할 수 있습니다. 자세한 정보는 `여기 <https://docs.openstack.org/openstack-"
-"helm/latest/devref/pod-disruption-budgets.html>`_ 를 참조하십시오."
-
-msgid "Nova config dependency"
-msgstr "Nova config 의존성"
-
-msgid "OSLO-Config Values"
-msgstr "OSLO-Config 값"
-
-msgid ""
-"OpenStack-Helm defines a centralized logging mechanism to provide insight "
-"into the state of the OpenStack services and infrastructure components as "
-"well as underlying Kubernetes platform. Among the requirements for a logging "
-"platform, where log data can come from and where log data need to be "
-"delivered are very variable. To support various logging scenarios, OpenStack-"
-"Helm should provide a flexible mechanism to meet with certain operation "
-"needs."
-msgstr ""
-"OpenStack-Helm은 OpenStack 서비스와 인프라 구성요소의 상태 뿐만 아니라 기본 "
-"Kubernetes 플랫폼에 대한 통찰력을 제공하는 중앙 집중식 로깅 메커니즘을 정의합"
-"니다. 로깅 플랫폼에 대한 요구사항 중 로그 데이터를 가져올 곳과 로그 데이터를 "
-"전달되어야 할 곳은 매우 다양합니다. 다양한 로깅 시나리오를 지원하기 위해서, "
-"OpenStack-Helm은 특정 작업 요구를 충족할 수 있는 유연한 메커니즘을 제공해야 "
-"합니다."
-
-msgid ""
-"OpenStack-Helm generates oslo-config compatible formatted configuration "
-"files for services dynamically from values specified in a yaml tree. This "
-"allows operators to control any and all aspects of an OpenStack services "
-"configuration. An example snippet for an imaginary Keystone configuration is "
-"described here:"
-msgstr ""
-"OpenStack-Helm은 yaml 트리에 지정된 값에서 동적으로 서비스를 위한 oslo-"
-"config 호환 형식의 구성 파일을 생성합니다. 이는 운영자가 OpenStack 서비스 구"
-"성 전반을 제어할 수 있도록 합니다. 가상의 키스톤 구성에 대한 짧은 예시가 여"
-"기 있습니다:"
-
-msgid ""
-"OpenStack-Helm provides fast and lightweight log forwarder and full featured "
-"log aggregator complementing each other providing a flexible and reliable "
-"solution. Especially, Fluent-bit is used as a log forwarder and Fluentd is "
-"used as a main log aggregator and processor."
-msgstr ""
-"OpenStack-Helm은 신속하고 가벼운 로그 전달자와 완전한 기능을 갖춘 로그 수집기"
-"를 제공하여 서로 보완하여 유연하고 신뢰할 수 있는 솔루션을 제공합니다. 특히, "
-"Fluent-bit는 로그 전달자로 사용되고 Fluentd는 주 로그 수집기와 프로세서로 사"
-"용됩니다."
-
-msgid "OpenVSwitch"
-msgstr "OpenVSwitch"
-
-msgid "Other SDNs"
-msgstr "다른 SDN들"
-
-msgid "Other networking services provided by Neutron are:"
-msgstr "Neutron에 의해 제공되는 다른 네트워킹 서비스:"
-
-msgid "Pod Disruption Budgets"
-msgstr "Pod 중단 비용"
-
-msgid ""
-"SDNs implementing ML2 driver can add extra/plugin-specific configuration "
-"options in `neutron/ml2/plugins/ml2_conf.ini`. Or define its own "
-"`ml2_conf_<name>.ini` file where configs specific to the SDN would be placed."
-msgstr ""
-"ML2 드라이버를 구현하는 SDN은 extra/plugin-specific 구성 옵션을 `neutron/ml2/"
-"plugins/ml2_conf.ini`에 추가할 수 있습니다. 또는 SDN의 고유 구성이 배치될 자"
-"체 `ml2_conf_<name>.ini` 파일을 정의하십시오."
-
-msgid ""
-"Script in :code:`neutron/templates/bin/_neutron-openvswitch-agent-init.sh."
-"tpl` is responsible for determining the tunnel interface and its IP for "
-"later usage by :code:`neutron-ovs-agent`. The IP is set in init container "
-"and shared between init container and main container with :code:`neutron-ovs-"
-"agent` via file :code:`/tmp/pod-shared/ml2-local-ip.ini`."
-msgstr ""
-":code:`neutron/templates/bin/_neutron-openvswitch-agent-init.sh.tpl`의 스크립"
-"트는 :code:`neutron-ovs-agent`에 의한 나중의 사용을 위한 터널 인터페이스와 IP"
-"를 결정할 책임이 있습니다. IP는 init 컨테이너에 설정되고 init 컨테이너와 "
-"main 컨테이너 사이에서 :code:`/tmp/pod-shared/ml2-local-ip.ini`을 통한 :code:"
-"`neutron-ovs-agent`로 공유됩니다."
-
-msgid ""
-"Specify if new SDN would like to use existing services from Neutron: L3, "
-"DHCP, metadata."
-msgstr ""
-"새로운 SDN이 Neutron의 기존 서비스들을 사용할지 명시하십시오: L3, DHCP, 메타"
-"데이터."
-
-msgid ""
-"The Neutron reference architecture provides mechanism_drivers :code:"
-"`OpenVSwitch` (OVS) and :code:`linuxbridge` (LB) with ML2 :code:"
-"`core_plugin` framework."
-msgstr ""
-"Neutron 참조 구조는 ML2 :code:`core_plugin` 프레임워크와 함께 :code:"
-"`OpenVSwitch` (OVS) 와 :code:`linuxbridge` (LB) mechanism_drivers를 제공합니"
-"다."
-
-msgid ""
-"The OpenStack-Helm project also implements annotations across all chart "
-"configmaps so that changing resources inside containers, such as "
-"configuration files, triggers a Kubernetes rolling update. This means that "
-"those resources can be updated without deleting and redeploying the service "
-"and can be treated like any other upgrade, such as a container image change."
-msgstr ""
-"OpenStack-Helm 프로젝트는 또한 모든 차트 configmap에 annotations를 구현하여 "
-"구성 파일과 같은 컨테이너 내부의 변경 리소스가 Kubernetes 롤링 업데이트를 촉"
-"발합니다. 이는 서비스를 삭제하거나 재배포하지 않고 해당 리소스들에 대한 업데"
-"이트를 할 수 있으며 컨테이너 이미비 변경과 같은 다른 업그레이드와 같이 처리 "
-"할 수 있음을 의미합니다."
-
-msgid ""
-"The OpenStack-Helm project assumes all upgrades will be done through Helm. "
-"This includes handling several different resource types. First, changes to "
-"the Helm chart templates themselves are handled. Second, all of the "
-"resources layered on top of the container image, such as ``ConfigMaps`` "
-"which includes both scripts and configuration files, are updated during an "
-"upgrade. Finally, any image references will result in rolling updates of "
-"containers, replacing them with the updating image."
-msgstr ""
-"OpenStack-Helm 프로젝트는 모든 업그레이드가 Helm을 통해 수행된다고 가정합니"
-"다. 이는 몇몇 다른 리소스 타입의 처리를 포함합니다. 첫째, Helm 차트 템플릿 자"
-"체의 변경이 처리됩니다. 둘째, ``ConfigMaps`` 와 같이 컨테이너 이미지 위에 계"
-"층화된 모든 리소스가 업그레이드 중에 업데이트 됩니다. 마지막으로, 모든 이미"
-"지 참조는 컨테이너의 롤링 업데이트를 가져오고, 업데이트한 이미지로 대체합니"
-"다."
-
-msgid ""
-"The OpenStack-Helm project today uses a mix of Docker images from "
-"Stackanetes and Kolla, but will likely standardize on a default set of "
-"images for all charts without any reliance on image-specific utilities."
-msgstr ""
-"OpenStack-Helm 프로젝트는 현재 Stackanetes와 Kolla의 Docker 이미지를 혼합하"
-"여 사용하지만, 이미지 특정 유틸리티에 의존하지 않고 모든 차트를 위한 기본 이"
-"미지 세트를 표준화할 것입니다."
-
-msgid ""
-"The ``hash`` function defined in the ``helm-toolkit`` chart ensures that any "
-"change to any file referenced by configmap-bin.yaml or configmap-etc.yaml "
-"results in a new hash, which will then trigger a rolling update."
-msgstr ""
-"``helm-toolkit`` 차트에서 정의된 ``hash`` 함수는 configmap-bin.yaml 또는 "
-"configmap-etc.yaml에서 참조되는 모든 파일에 대한 변화가 롤링 업데이트를 촉발"
-"할 새로운 hash를 생성하는 것을 보장합니다."
-
-msgid "The above configuration options are handled by `neutron/values.yaml`:"
-msgstr "위의 구성 옵션은 'neutrol/values.yaml` 에 의해 조절됩니다:"
-
-msgid ""
-"The farther down the list the label appears, the greater precedence it has. "
-"e.g., \"another-label\" overrides will apply to a node containing both "
-"labels."
-msgstr ""
-"라벨이 표시된 목록이 낮을수록, 우선순위가 높아집니다. 예를 들어, \\\"another-"
-"label\\\" 의 오버라이드는 두 라벨 모두를 포함한 노드에 적용될 것입니다. "
-
-msgid ""
-"The following standards are in use today, in addition to any components "
-"defined by the service itself:"
-msgstr ""
-"서비스 자체로 정의된 구성요소 외에도, 다음의 표준들이 현재 사용되고 있습니다."
-
-msgid ""
-"The macros that help translate these into the actual URLs necessary are "
-"defined in the ``helm-toolkit`` chart. For instance, the cinder chart "
-"defines a ``glance_api_servers`` definition in the ``cinder.conf`` template:"
-msgstr ""
-"이들을 실제 필요한 URL로 변환하는 데 도움이 되는 매크로는 ``helm-toolkit`` 차"
-"트에 정의되어 있습니다. 예를 들어, cinder 차트는 ``glance_api_servers`` 정의"
-"를 ``cinder.conf`` 템플릿에 정의합니다:"
-
-msgid ""
-"The ovs set of daemonsets are running on the node labeled "
-"`openvswitch=enabled`. This includes the compute and controller/network "
-"nodes. For more flexibility, OpenVSwitch as a tool was split out of Neutron "
-"chart, and put in separate chart dedicated OpenVSwitch. Neutron OVS agent "
-"remains in Neutron chart. Splitting out the OpenVSwitch creates "
-"possibilities to use it with different SDNs, adjusting the configuration "
-"accordingly."
-msgstr ""
-"데몬세트의 ovs 세트는 `openvswitch=enabled`로 라벨된 노드에서 실행 중입니다. "
-"이는 compute와 controller/network 노드를 포함합니다. 유연성을 높이기 위해서, "
-"OpenVSwitch를 도구로 사용하여 Neutron 차트를 분리하고 OpenVSwitch 전용의 별"
-"도 차트를 넣었습니다. Neutron OVS 에이전트는 Neutron 차트에 남아있습니다. "
-"OpenVSwitch를 분할하면 다른 SDN과 함께 사용할 수 있는 가능성이 생기기 때문"
-"에, 적절하게 구성을 조정합니다."
-
-msgid ""
-"The project's core philosophy regarding images is that the toolsets required "
-"to enable the OpenStack services should be applied by Kubernetes itself. "
-"This requires OpenStack-Helm to develop common and simple scripts with "
-"minimal dependencies that can be overlaid on any image that meets the "
-"OpenStack core library requirements. The advantage of this is that the "
-"project can be image agnostic, allowing operators to use Stackanetes, Kolla, "
-"LOCI, or any image flavor and format they choose and they will all function "
-"the same."
-msgstr ""
-"이미지에 관한 프로젝트의 핵심 철학은 OpenStack 서비스를 활성화하는 데 필요한 "
-"도구모음이 Kubernetes 자체에서 적용되어야 한다는 것입니다. 이는 OpenStack-"
-"Helm에 OpenStack 핵심 라이브러리의 요구사항을 충족하는 이미지들에 중첩될 수 "
-"있는 최소한의 의존성으로 일반적이고 단순한 스크립트를 개발할 것을 요구합니"
-"다. 이것의 장점은 운영자들이 Stackanetes, Kolla, LOCI, 또는 그들이 선택하고 "
-"동일하게 기능할 이미지 flavor와 포맷을 사용하는 것을 허락하여 프로젝트가 이미"
-"지에서 자유로워지는 것입니다."
-
-msgid ""
-"The project's goal is to provide a consistent mechanism for endpoints. "
-"OpenStack is a highly interconnected application, with various components "
-"requiring connectivity details to numerous services, including other "
-"OpenStack components and infrastructure elements such as databases, queues, "
-"and memcached infrastructure. The project's goal is to ensure that it can "
-"provide a consistent mechanism for defining these \"endpoints\" across all "
-"charts and provide the macros necessary to convert those definitions into "
-"usable endpoints. The charts should consistently default to building "
-"endpoints that assume the operator is leveraging all charts to build their "
-"OpenStack cloud. Endpoints should be configurable if an operator would like "
-"a chart to work with their existing infrastructure or run elements in "
-"different namespaces."
-msgstr ""
-"프로젝트의 목표는 endpoints에 대한 일관된 매커니즘을 제공하는 것입니다. "
-"OpenStack은 다른 OpenStack 구성요소 와 데이터베이스, 큐, 그리고 memcached 인"
-"프라와 같은 인프라 요소를 포함하여 다양한 서비스에 대한 연결 세부 사항을 필요"
-"로 하는 다양한 구성요소와 고도로 상호 연결된 응용 프로그램입니다. 프로젝트의 "
-"목표는 모든 차트에서 이러한 \"endpoints\"를 정의하는 일관된 메커니즘을 제공하"
-"고 이러한 정의를 유용한 endpoints로 변환하는 데 필요한 매크로를 제공하는 것입"
-"니다. 차트는 운영자가 그들의 OpenStack 클라우드를 구축하기 위하여 모든 차트"
-"를 활용하고 있다고 가정하고 endpoints 구축을 일관되게 기본값으로 설정해야 합"
-"니다. 운영자가 차트를 그들의 기존 인프라와 함께 사용하기를 원하거나 다른 네임"
-"스페이스의 요소를 실행하려면 Endpoints를 구성 할 수 있어야 합니다."
-
-msgid ""
-"The resulting logs can then be queried directly through Elasticsearch, or "
-"they can be viewed via Kibana. Kibana offers a dashboard that can create "
-"custom views on logged events, and Kibana integrates well with Elasticsearch "
-"by default."
-msgstr ""
-"로그의 결과는 Elasticsearch를 통해 직접 쿼리하거나 Kibana를 통해 볼 수 있습니"
-"다. Kibana는 기록된 이벤트에 대한 사용자 정의 뷰를 만들 수 있는 대시보드를 제"
-"공하며 Kibana는 기본적으로 Elasticsearch와 잘 통합됩니다."
-
-msgid ""
-"There is also a need for DHCP agent to pass ovs agent config file (in :code:"
-"`neutron/templates/bin/_neutron-dhcp-agent.sh.tpl`):"
-msgstr ""
-"또한 DHCP 에이전트가 ovs 에이전트 구성 파일을 전달할 필요가 있습니다(:code:"
-"`neutron/templates/bin/_neutron-dhcp-agent.sh.tpl` 내):"
-
-msgid ""
-"These values define all the endpoints that the Neutron chart may need in "
-"order to build full URL compatible endpoints to various services. Long-term, "
-"these will also include database, memcached, and rabbitmq elements in one "
-"place. Essentially, all external connectivity can be defined centrally."
-msgstr ""
-"이 값들은 Neutron 차트가 다양한 서비스에 URL과 완전 호환되는 endpoints를 구축"
-"하는데 필요할 수 있는 모든 endpoints를 정의합니다. 장기적으로, 이들은 또한 데"
-"이터베이스, memcached, 그리고 rabbitmq 요소들을 한 곳에 포함할 것입니다. 근본"
-"적으로, 모든 외부 연결을 중앙에서 정의할 수 있습니다."
-
-msgid ""
-"This daemonset includes the linuxbridge Neutron agent with bridge-utils and "
-"ebtables utilities installed. This is all that is needed, since linuxbridge "
-"uses native kernel libraries."
-msgstr ""
-"이 daemonset은 bridge-utils와 ebtables 유틸리티가 설치된 linuxbridge Neutron "
-"에이전트를 포함합니다.linuxbridge가 네이티브 커널 라이브러리를 사용하기 때문"
-"에 이 모든 것이 필요합니다."
-
-msgid "This is accomplished with the following annotation:"
-msgstr "이는 다음 annotation으로 수행됩니다:"
-
-msgid ""
-"This option will allow to configure the Neutron services in proper way, by "
-"checking what is the actual backed set in :code:`neutron/values.yaml`."
-msgstr ""
-"이 옵션은 :code:`neutron/values.yaml`의 실제 backend set이 무엇인지 확인하"
-"여, Neuron 서비스를 적절한 방법으로 구성할 수 있도록 허락할 것입니다."
-
-msgid ""
-"This requirement is OVS specific, the `ovsdb_connection` string is defined "
-"in `openvswitch_agent.ini` file, specifying how DHCP agent can connect to "
-"ovs. When using other SDNs, running the DHCP agent may not be required. When "
-"the SDN solution is addressing the IP assignments in another way, neutron's "
-"DHCP agent should be disabled."
-msgstr ""
-"이 요구사항은 OVS 특정이며, `ovsdb_connection` 문자열은 DHCP 에이전트가 어떻"
-"게 ovs에 연결할 수 있는지 명세하는 `openvswitch_agent.ini` 파일에 정의됩니"
-"다. 다른 SDN을 사용할 때, DHCP 에이전트 실행은 요구되지 않을 것입니다. SDN 솔"
-"루션이 다른 방식으로 IP 할당을 지정할 때, neutron의 DHCP 에이전트를 비활성화"
-"해야 합니다."
-
-msgid ""
-"This runs the OVS tool and database. OpenVSwitch chart is not Neutron "
-"specific, it may be used with other technologies that are leveraging the OVS "
-"technology, such as OVN or ODL."
-msgstr ""
-"이것은 OVS 툴과 데이터베이스를 실행합니다. OpenVSwitch 차트는 특정 Neutron이 "
-"아니라, OVN이나 ODL과 같은 OVS 기술을 활용하는 다른 기술들에 사용될 것입니다."
-
-msgid ""
-"This will be consumed by the templated ``configmap-etc.yaml`` manifest to "
-"produce the following config file:"
-msgstr ""
-"이것은 템플릿화 된 ``configmap-etc.yaml`` 매니페스트에 의해 다음의 구성 파일"
-"을 생산하기 위해 소비될 것입니다:"
-
-msgid ""
-"To be able to configure multiple networking plugins inside of OpenStack-"
-"Helm, a new configuration option is added:"
-msgstr ""
-"OpenStack-Helm 내 다중 네트워킹 플러그인을 구성하는 것을 가능하게 하기 위해"
-"서, 새로운 구성 옵션이 추가되었습니다:"
-
-msgid ""
-"To enable new SDN solution, there should be separate chart created, which "
-"would handle the deployment of service, setting up the database and any "
-"related networking functionality that SDN is providing."
-msgstr ""
-"새로운 SDN 솔루션을 가능하게 하기 위해 서비스 배포, 데이터베이스 설정, 그리"
-"고 SDN이 제공하고 있는 관련된 모든 네트워크 기능을 처리하는 별도의 차트가 생"
-"성되어 있어야 합니다."
-
-msgid ""
-"To that end, all charts provide an ``images:`` section that allows operators "
-"to override images. Also, all default image references should be fully "
-"spelled out, even those hosted by Docker or Quay. Further, no default image "
-"reference should use ``:latest`` but rather should be pinned to a specific "
-"version to ensure consistent behavior for deployments over time."
-msgstr ""
-"이를 위해, 모든 차트는 운영자들이 이미지를 오버라이드할 수 있는 ``images`` 섹"
-"션을 제공합니다. 또한, 모든 기본 이미지 참조는 Docker 또는 Quay에 의해 호스팅"
-"되었더라도 완전히 작성되어야 합니다. 나아가, 어떤 기본 이미지 참조도 ``:"
-"latest` 를 사용하면 안되지만, 대신에 배포 후에 일관된 동작을 보장하는 특정 버"
-"전으로 고정되어야 합니다."
-
-msgid ""
-"To use other Neutron reference architecture types of SDN, these options "
-"should be configured in :code:`neutron.conf`:"
-msgstr ""
-"다른 Neutron 참조 구조 타입의 SDN을 사용하려면, 이러한 옵션을 neutron.conf에"
-"서 구성해야 합니다:"
-
-msgid ""
-"Today, the ``images:`` section has several common conventions. Most "
-"OpenStack services require a database initialization function, a database "
-"synchronization function, and a series of steps for Keystone registration "
-"and integration. Each component may also have a specific image that composes "
-"an OpenStack service. The images may or may not differ, but regardless, "
-"should all be defined in ``images``."
-msgstr ""
-"현재, ``images:`` 섹션에는 몇가지 규칙이 있습니다. 대부분의 OpenStack 서비스"
-"는 데이터베이스 초기화 기능, 데이터베이스 동기화 기능, 그리고 Keystone 등록"
-"과 통합을 위한 단계를 요구합니다. 각 구성요소에는 OpenStack 서비스를 구성하"
-"는 특정 이미지가 있을 수도 있습니다. 이미지는 다를 수 있지만, 이에 관계없이 "
-"모두 ``images``에 정의되어야 합니다."
-
-msgid "Typical networking API request is an operation of create/update/delete:"
-msgstr "일반적인 네트워킹 API 요청은 생성/갱신/삭제 작업입니다:"
-
-msgid "Upgrades and Reconfiguration"
-msgstr "업그레이드 및 재구성"
-
-msgid ""
-"``host1.fqdn`` with labels ``compute-type: dpdk, sriov`` and ``another-"
-"label: another-value``:"
-msgstr ""
-"``compute-type: dpdk, sriov`` 와 ``another-label: another-value`` 라벨의 "
-"``host1.fqdn`` :"
-
-msgid ""
-"``host2.fqdn`` with labels ``compute-type: dpdk, sriov`` and ``another-"
-"label: another-value``:"
-msgstr ""
-"``compute-type: dpdk, sriov`` 와 ``another-label: another-value`` 라벨의 "
-"``host2.fqdn`` :"
-
-msgid ""
-"``host3.fqdn`` with labels ``compute-type: dpdk, sriov`` and ``another-"
-"label: another-value``:"
-msgstr ""
-"``compute-type: dpdk, sriov`` 와 ``another-label: another-value`` 라벨의 "
-"``host3.fqdn`` :"
-
-msgid "``host4.fqdn`` with labels ``compute-type: dpdk, sriov``:"
-msgstr "``compute-type: dpdk, sriov`` 라벨의 ``host4.fqdn`` :"
-
-msgid "``host5.fqdn`` with no labels:"
-msgstr "라벨이 없는 ``host5.fqdn`` :"
-
-msgid ""
-"db\\_drop: The image that will perform database deletion operations for the "
-"OpenStack service."
-msgstr "db\\_drop: OpenStack 서비스를 위한 데이터베이스 삭제를 수행할 이미지"
-
-msgid ""
-"db\\_init: The image that will perform database creation operations for the "
-"OpenStack service."
-msgstr ""
-"db\\_init: OpenStack 서비스를 위한 데이터베이스 생성 작업을 수행할 이미지"
-
-msgid ""
-"db\\_sync: The image that will perform database sync (schema initialization "
-"and migration) for the OpenStack service."
-msgstr ""
-"db\\_sync: OpenStack 서비스를 위한 데이터베이스 동기화(초기화와 이동 스키마)"
-"를 수행할 이미지"
-
-msgid ""
-"dep\\_check: The image that will perform dependency checking in an init-"
-"container."
-msgstr "dep\\_check: init-container에서 의존성 검사를 수행할 이미지."
-
-msgid ""
-"image: This is the OpenStack service that the endpoint is being built for. "
-"This will be mapped to ``glance`` which is the image service for OpenStack."
-msgstr ""
-"image : 이것은 endpoint가 구축하고 있는 OpenStack 서비스입니다. 이것은 "
-"OpenStack을 위한 이미지 서비스인 ``glance``로 매핑될 것입니다."
-
-msgid ""
-"internal: This is the OpenStack endpoint type we are looking for - valid "
-"values would be ``internal``, ``admin``, and ``public``"
-msgstr ""
-"internal : 이것은 우리가 찾고 있는 OpenStack endpoint 타입입니다. - 유효한 값"
-"은 ``internal``, ``admin``, 그리고 ``public`` 입니다."
-
-msgid ""
-"ks\\_endpoints: The image that will perform keystone endpoint registration "
-"for the service."
-msgstr "ks\\_endpoints: 서비스를 위한 키스톤 endpoint 등록을 수행할 이미지"
-
-msgid ""
-"ks\\_service: The image that will perform keystone service registration for "
-"the service."
-msgstr "ks\\_service: 서비스를 위한 키스톤 사용자 등록을 수행할 이미지"
-
-msgid ""
-"ks\\_user: The image that will perform keystone user creation for the "
-"service."
-msgstr "ks\\_user : 서비스를 위한 키스톤 사용자 생성을 수행할 이미지"
-
-msgid "network"
-msgstr "네트워크"
-
-msgid "neutron-dhcp-agent"
-msgstr "neutron-dhcp-agent"
-
-msgid ""
-"neutron-dhcp-agent service is scheduled to run on nodes with the label "
-"`openstack-control-plane=enabled`."
-msgstr ""
-"neutron-dhcp-agent 서비스는 `openstack-control-plane=enabled` 라벨로 노드에"
-"서 실행되도록 스케줄됩니다."
-
-msgid "neutron-l3-agent"
-msgstr "neutron-l3-agent"
-
-msgid ""
-"neutron-l3-agent service is scheduled to run on nodes with the label "
-"`openstack-control-plane=enabled`."
-msgstr ""
-"neutron-l3-agent 서비스는 `openstack-control-plane=enabled` 라벨로 노드에서 "
-"실행되도록 스케줄됩니다."
-
-msgid "neutron-lb-agent"
-msgstr "neutron-lb-agent"
-
-msgid "neutron-metadata-agent"
-msgstr "neutron-metadata-agent"
-
-msgid ""
-"neutron-metadata-agent service is scheduled to run on nodes with the label "
-"`openstack-control-plane=enabled`."
-msgstr ""
-"neutron-metadata-agent 서비스는 `openstack-control-plane=enabled` 라벨로 노드"
-"에서 실행되도록 스케줄됩니다."
-
-msgid "neutron-ovs-agent"
-msgstr "neutron-ovs-agent"
-
-msgid "neutron-server"
-msgstr "neutron-server"
-
-msgid ""
-"neutron-server is serving the networking REST API for operator and other "
-"OpenStack services usage. The internals of Neutron are highly flexible, "
-"providing plugin mechanisms for all networking services exposed. The "
-"consistent API is exposed to the user, but the internal implementation is up "
-"to the chosen SDN."
-msgstr ""
-"neutron-server는 운영자와 다른 OpenStack 서비스 사용을 위한 네트워킹 REST API"
-"를 제공합니다. Neutron 내부 구조는 유연성이 뛰어나, 노출된 모든 네트워킹 서비"
-"스를 위한 플러그인 매커니즘을 제공합니다. 일관된 API는 사용자에게 노출되지"
-"만, 내부 구현은 선택된 SDN가 결정합니다."
-
-msgid "openvswitch-db and openvswitch-vswitchd"
-msgstr "openvswitch-db와 openvswitch-vswitchd"
-
-msgid "port"
-msgstr "포트"
-
-msgid ""
-"pull\\_policy: The image pull policy, one of \"Always\", \"IfNotPresent\", "
-"and \"Never\" which will be used by all containers in the chart."
-msgstr ""
-"pull\\_policy: 차트 내 모든 컨테이너가 사용할 \"Always\", \"IfNotPresent\", "
-"그리고 \"Never\" 중 하나의 이미지 pull 정책"
-
-msgid "subnet"
-msgstr "서브넷"
diff --git a/doc/source/locale/ko_KR/LC_MESSAGES/doc-install.po b/doc/source/locale/ko_KR/LC_MESSAGES/doc-install.po
deleted file mode 100644
index 5eb33e5d65..0000000000
--- a/doc/source/locale/ko_KR/LC_MESSAGES/doc-install.po
+++ /dev/null
@@ -1,1262 +0,0 @@
-# Soonyeul Park <ardentpark@gmail.com>, 2018. #zanata
-# Sungjin Kang <gang.sungjin@gmail.com>, 2018. #zanata
-# Lee Jongwon <tothebinaryworld@gmail.com>, 2019. #zanata
-# Sungjin Kang <gang.sungjin@gmail.com>, 2019. #zanata
-# SeongHo Park <glgl2131@naver.com>, 2020. #zanata
-# Lee Jongwon <tothebinaryworld@gmail.com>, 2021. #zanata
-# Lee Jongwon <tothebinaryworld@gmail.com>, 2023. #zanata
-msgid ""
-msgstr ""
-"Project-Id-Version: openstack-helm 0.1.1.dev3911\n"
-"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2023-03-04 03:32+0000\n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-"PO-Revision-Date: 2023-03-14 02:37+0000\n"
-"Last-Translator: Lee Jongwon <tothebinaryworld@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 "**Check Chart Status**"
-msgstr "**Chart 상태 확인**"
-
-msgid ""
-"**First**, edit the ``values.yaml`` for Neutron, Glance, Horizon, Keystone, "
-"and Nova."
-msgstr ""
-"**첫째**, Neutron, Glance, Horizon, Keystone, and Nova 를 위해 ``values."
-"yaml`` 를 편집하시오."
-
-msgid "**Review the Ingress configuration.**"
-msgstr "**Ingress 구성을 검토합니다.**"
-
-msgid ""
-"**Second** option would be as ``--set`` flags when calling ``helm install``"
-msgstr ""
-"``helm install`` 을 호출할 때 **두 번째** 옵션은 ``--set``가 될 것입니다."
-
-msgid ""
-"**TaaS Agent, TaaS OVS Driver and TaaS SR-IOV Driver**: This forms the back-"
-"end of TaaS which runs as a ML2 agent extension on compute nodes. It handles "
-"the RPC calls made by TaaS Plugin and configures the mechanism driver, i.e. "
-"OpenVSwitch or SR-IOV Nic Switch."
-msgstr ""
-"**TaaS 에이전트, TaaS OVS 드라이버, TaaS SR-IOV 드라이버**: Compute 노드에서 "
-"ML2 에이전트 확장으로 실행되는 TaaS 백엔드 서버입니다. TaaS 플러그인이 만든 "
-"RPC 콜을 처리하고 OpenVSwitch나 SR-IOV Nic 스위치와 같은 메커니즘 드라이버를 "
-"구성합니다."
-
-msgid ""
-"**TaaS Dashboard Plugin**: Horizon Plugin which adds GUI panels for TaaS "
-"resources in the Horizon Dashboard."
-msgstr ""
-"**TaaS Dashboard 플러그인**: Horizon Dashboard에서 TaaS 리소스를 위한 GUI 패"
-"널을 추가하는 Horizon 플러그인입니다."
-
-msgid ""
-"**TaaS Plugin**: This is the front-end of TaaS which runs on controller node "
-"(Neutron server). This serves TaaS APIs and stores/retrieves TaaS "
-"configuration state to/from Neutron TaaS DB."
-msgstr ""
-"**TaaS Plugin**: 컨트놀러 노드 (Neutron 서버)에서 실행되는 TaaS 프론트 서버입"
-"니다. TaaS API를 제공하고 Neutron TaaS DB에서 TaaS 구성 상태를 저장, 검색합니"
-"다."
-
-msgid "16GB of RAM"
-msgstr "16GB of RAM"
-
-msgid "4 Cores"
-msgstr "4 Cores"
-
-msgid "48GB HDD"
-msgstr "48GB HDD"
-
-msgid "8 Cores"
-msgstr "8 Cores"
-
-msgid "8GB of RAM"
-msgstr "8GB of RAM"
-
-msgid "Activate the OpenStack namespace to be able to use Ceph"
-msgstr "Ceph를 사용하려면 OpenStack 네임 스페이스를 활성화하십시오"
-
-msgid "Activate the openstack namespace to be able to use Ceph"
-msgstr "Ceph를 사용할 수 있도록 OpenStack namespace를 활성화합니다."
-
-msgid "Add TaaS panel to Horizon Dashboard:"
-msgstr "Horizon 대시보드에 TaaS 패널을 추가하십시오."
-
-msgid ""
-"Add the address of the Kubernetes API, ``172.17.0.1``, and ``.svc.cluster."
-"local`` to your ``no_proxy`` and ``NO_PROXY`` environment variables."
-msgstr ""
-"Kubernetes API의 주소 ``172.17.0.1`` 과 ``.svc.cluster.local`` 을 "
-"``no_proxy`` 와 ``NO_PROXY`` 환경 변수에 추가하십시오."
-
-msgid ""
-"Add to the Install steps these flags - also adding a shell environment "
-"variable to save on repeat code."
-msgstr ""
-"플래그들을 설치 과정에 추가하십시오 - 또한 반복 코드를 저장할 셸 환경 변수를 "
-"추가하십시오."
-
-msgid ""
-"Additional configuration variables can be found `here <https://github.com/"
-"openstack/openstack-helm-infra/blob/master/roles/deploy-kubeadm-aio-common/"
-"defaults/main.yml>`_. In particular, ``kubernetes_cluster_pod_subnet`` can "
-"be used to override the pod subnet set up by Calico (the default container "
-"SDN), if you have a preexisting network that conflicts with the default pod "
-"subnet of 192.168.0.0/16."
-msgstr ""
-"추가 구성 변수는 `여기 <https://github.com/openstack/openstack-helm-infra/"
-"blob/master/roles/deploy-kubeadm-aio-common/defaults/main.yml>`_ 에서 확인할 "
-"수 있습니다. 특히 ``kubernetes_cluster_pod_subnet`` 은 기본 pod 서브넷 "
-"192.168.0.0/16 과 충돌하는 기존 네트워크가 있는 경우, Calico (기본 컨테이너 "
-"SDN) 이 설정한 pod 서브넷을 무시하여 사용할 수 있습니다."
-
-msgid ""
-"Additional information on Kubernetes Ceph-based integration can be found in "
-"the documentation for the `CephFS <https://github.com/kubernetes-incubator/"
-"external-storage/blob/master/ceph/cephfs/README.md>`_ and `RBD <https://"
-"github.com/kubernetes-incubator/external-storage/blob/master/ceph/rbd/README."
-"md>`_ storage provisioners, as well as for the alternative `NFS <https://"
-"github.com/kubernetes-incubator/external-storage/blob/master/nfs/README."
-"md>`_ provisioner."
-msgstr ""
-"Kubernetes을 Ceph 기반으로 통합하기 위한 추가 정보는 `CephFS  <https://"
-"github.com/kubernetes-incubator/external-storage/blob/master/ceph/cephfs/"
-"README.md>`_ 와 `RBD <https://github.com/kubernetes-incubator/external-"
-"storage/blob/master/ceph/rbd/README.md>`_ 스토리지 공급자와 대체 `NFS "
-"<https://github.com/kubernetes-incubator/external-storage/blob/master/nfs/"
-"README.md>`_ 공급자에 대한 문서에서 찾을 수 있습니다."
-
-msgid ""
-"After making the configuration changes, run a ``make`` and then install as "
-"you would from AIO or MultiNode instructions."
-msgstr ""
-"구성을 변경한 후, ``make``를 실행하고 AIO 또는 다중 노드 명령에서 했던 바와 "
-"같이 설치하십시오."
-
-msgid ""
-"All commands below should be run as a normal user, not as root. Appropriate "
-"versions of Docker, Kubernetes, and Helm will be installed by the playbooks "
-"used below, so there's no need to install them ahead of time."
-msgstr ""
-"아래의 모든 명령은 root가 아닌 일반 사용자로 실행해야 합니다. Docker, "
-"Kubernetes, 그리고 Helm의 적절한 버전이 아래에 사용된 playbook에 의해 설치될 "
-"것이므로, 사전에 설치할 필요가 없습니다."
-
-msgid ""
-"Alternatively, these steps can be performed by running the script directly::"
-msgstr "대신에, 이 단계는 스크립트를 직접 실행함으로써 수행 가능합니다. "
-
-msgid ""
-"Alternatively, this step can be performed by running the script directly:"
-msgstr "대안으로, 직접 스크립트를 실행하여 이 단계를 수행할 수 있습니다:"
-
-msgid ""
-"An Ingress is a collection of rules that allow inbound connections to reach "
-"the cluster services."
-msgstr ""
-"Ingress는 인바운드 연결이 클러스터 서비스에 도달하도록 허락하는 규칙들의 모음"
-"입니다."
-
-msgid ""
-"As any other Neutron plugin, TaaS neutron plugin functionality consists of "
-"following modules:"
-msgstr ""
-"다른 Neutron 플러그인과 마찬가지로 TaaS Neutron 플러그인 기능은 다음 모듈로 "
-"구성됩니다."
-
-msgid ""
-"Before deploying TaaS and/or TaaS Dashboard, it needs to be added in Neutron "
-"and/or Horizon LOCI images."
-msgstr ""
-"TaaS, TaaS Dashboard를 배포하기 전, Neutron, Horizon LOCI 이미지를 추가해야 "
-"합니다."
-
-msgid ""
-"By default the Calico CNI will use ``192.168.0.0/16`` and Kubernetes "
-"services will use ``10.96.0.0/16`` as the CIDR for services. Check that "
-"these CIDRs are not in use on the development node before proceeding, or "
-"adjust as required."
-msgstr ""
-"기본적으로 Calico CNI는 ``192.168.0.0/16`` 을 사용할 것이고 Kubernetes 서비스"
-"는 ``10.96.0.0/16`` 을 서비스를 위한 CIDR로 사용할 것입니다. 진행하기 전에 "
-"이 CIDR이 개발 노드에서 사용하지 않는지 확인하거나 필요에 따라 조정하십시오."
-
-msgid ""
-"By default, this installation will use Google DNS Server IPs (8.8.8.8, "
-"8.8.4.4) and will update resolv.conf as a result. If those IPs are blocked "
-"by the proxy, this will overwrite the original DNS entries and result in the "
-"inability to connect to anything on the network behind the proxy. These DNS "
-"nameserver entries can be changed by updating the "
-"``external_dns_nameservers`` entry in this file:"
-msgstr ""
-"기본적으로, 이 설치는 구글 DNS 서버 IP(8.8.8.8, 8.8.4.4)를 사용하며 결과적으"
-"로 resolv.conf를 업데이트 합니다. 해당 IP가 프록시에 의해 차단된 경우 원래 "
-"DNS 항목을 덮어 쓰고 프록시 뒤에 있는 어떤 항목에도 연결할 수 없습니다. 이 "
-"DNS 네임서버 항목은 이 파일에서 ``external_dns_nameservers`` 항목을 업데이트"
-"하여 변경할 수 있습니다."
-
-msgid "Cleaning the Deployment"
-msgstr "배포 정리"
-
-msgid "Clone the OpenStack-Helm Repos"
-msgstr "OpenStack-Helm 저장소 Clone"
-
-msgid "Code examples below."
-msgstr "아래의 코드 예제를 확인하세요."
-
-msgid "Common Deployment Requirements"
-msgstr "일반적인 배포 요구 사항"
-
-msgid "Configure OpenStack"
-msgstr "OpenStack 구성"
-
-msgid "Configure TaaS in Neutron chart"
-msgstr "Neutron 차트의 TaaS를 설정하십시오. "
-
-msgid ""
-"Configuring OpenStack for a particular production use-case is beyond the "
-"scope of this guide. Please refer to the OpenStack `Configuration <https://"
-"docs.openstack.org/latest/configuration/>`_ documentation for your selected "
-"version of OpenStack to determine what additional values overrides should be "
-"provided to the OpenStack-Helm charts to ensure appropriate networking, "
-"security, etc. is in place."
-msgstr ""
-"특정 프로덕션 유즈 케이스에 맞게 OpenStack을 구성하는 방법은 이 가이드에서 지"
-"원하지 않습니다. 선택한 OpenStack 버전에 대한 OpenStack `구성 <https://docs."
-"openstack.org/latest/configuration/>`_ 문서를 참조하여 적절한 네트워킹, 보안 "
-"등을 위한 OpenStack-Helm chart에 어떤 추가 값이 작성되어야 하는지 결정하십시"
-"오."
-
-msgid "Contents:"
-msgstr "목차:"
-
-msgid ""
-"Copy the key: ``sudo cp ~/.ssh/id_rsa /etc/openstack-helm/deploy-key.pem``"
-msgstr "키 복사: ``sudo cp ~/.ssh/id_rsa/openstack-helm/deploy-key.pem``"
-
-msgid "Create a patchset for ``openstack/horizon`` repo"
-msgstr "``openstack/horizon`` 저장소에 대한 패치셋을 생성합니다"
-
-msgid "Create a patchset for ``openstack/neutron`` repo"
-msgstr "``openstack/neutron`` 저장소에 대한 패치를 생성하십시오. "
-
-msgid "Create a patchset for ``openstack/requirements`` repo"
-msgstr "``openstack/requirements`` 레포에서 패치셋 생성"
-
-msgid "Create an environment file"
-msgstr "환경 파일 생성"
-
-msgid "Create an inventory file"
-msgstr "인벤토리 파일 생성"
-
-msgid ""
-"Create an ssh-key on the master node, and add the public key to each node "
-"that you intend to join the cluster."
-msgstr ""
-"Master 노드에 ssh-key를 생성합니다. 그리고 클러스터로 묶을 각 노드에 공개 키"
-"를 추가합니다."
-
-msgid "Create loopback devices for CEPH"
-msgstr "CEPH를 사용하기 위한 루프백 장치를 생성하십시오. "
-
-msgid ""
-"Default log level for Neutron TaaS is :code:`INFO`. For changing it, "
-"override following parameter:"
-msgstr ""
-"Neutron TaaS의 기본 로그 레벨은 :code:`INFO`입니다. 로그 레벨을 변경하려면 다"
-"음 매개변수를 재설정하십시오."
-
-msgid "Delete the keypair(s) returned from the list command above::"
-msgstr "위의 리스트 명령어로 확인된 키쌍을 삭제합니다:"
-
-msgid ""
-"Depending on your specific proxy, https_proxy may be the same as http_proxy. "
-"Refer to your specific proxy documentation."
-msgstr ""
-"특정 프록시에 따라서, https_proxy가 http_proxy와 같을 수도 있습니다. 특정 프"
-"록시 관련 문서를 참조하십시오. "
-
-msgid "Deploy Barbican"
-msgstr "Barbican 배포"
-
-msgid "Deploy Ceph"
-msgstr "Ceph 배포"
-
-msgid "Deploy Cinder"
-msgstr "Cinder 배포"
-
-msgid "Deploy Compute Kit (Nova and Neutron)"
-msgstr "컴퓨팅 키트 (Nova and Neutron) 배포"
-
-msgid "Deploy Glance"
-msgstr "Glance 배포"
-
-msgid "Deploy Heat"
-msgstr "Heat 배포"
-
-msgid "Deploy Horizon"
-msgstr "Horizon 배포"
-
-msgid "Deploy Keystone"
-msgstr "Keystone 배포"
-
-msgid "Deploy Kubernetes & Helm"
-msgstr "Kubernetes & Helm 배포"
-
-msgid "Deploy Libvirt"
-msgstr "Libvirt 배포"
-
-msgid "Deploy MariaDB"
-msgstr "MariaDB 배포"
-
-msgid "Deploy Memcached"
-msgstr "Memcached 배포"
-
-msgid "Deploy NFS Provisioner"
-msgstr "NFS Provisioner 배포"
-
-msgid "Deploy OVS-DPDK"
-msgstr "OVS-DPDK 배포"
-
-msgid "Deploy OpenStack-Helm"
-msgstr "OpenStack-Helm 배포"
-
-msgid "Deploy OpenvSwitch"
-msgstr "OpenvSwitch 배포"
-
-msgid "Deploy RabbitMQ"
-msgstr "RabbitMQ 배포"
-
-msgid "Deploy Rados Gateway for object store"
-msgstr "개체 저장을 위한 Rados Gateway 배포"
-
-msgid "Deploy TaaS Dashboard Plugin"
-msgstr "TaaS 대시보드 플러그인을 활성화 하십시오."
-
-msgid "Deploy TaaS Plugin"
-msgstr "TaaS 플러그인을 활성화 하십시오."
-
-msgid "Deploy tap-as-a-service (TaaS) Neutron / Dashboard plugin"
-msgstr "TaaS(Tap-as-a-Service) Neutron / Dashboard 플러그인 배포"
-
-msgid "Deploy the ingress controller"
-msgstr "ingress controller 배포"
-
-msgid "Deployment"
-msgstr "배포"
-
-msgid "Deployment With Ceph"
-msgstr "Ceph를 사용한 배포"
-
-msgid "Deployment With NFS"
-msgstr "NFS를 사용한 배포"
-
-msgid "Deployment with Tungsten Fabric"
-msgstr "Tungsten Fabric를 사용한 배포"
-
-msgid "Development"
-msgstr "개발"
-
-msgid "Environment tear-down"
-msgstr "환경 해제"
-
-msgid ""
-"Essentially the use of Ingress for OpenStack-Helm is an Nginx proxy service. "
-"Ingress (Nginx) is accessible by your cluster public IP - e.g. the IP "
-"associated with ``kubectl get pods -o wide --all-namespaces | grep ingress-"
-"api`` Ingress/Nginx will be listening for server name requests of \"keystone"
-"\" or \"keystone.openstack\" and will route those requests to the proper "
-"internal K8s Services. These public listeners in Ingress must match the "
-"external DNS that you will set up to access your OpenStack deployment. Note "
-"each rule also has a Service that directs Ingress Controllers allow access "
-"to the endpoints from within the cluster."
-msgstr ""
-"본질적으로 OpenStack-Helm을 위한 Ingress의 사용은 Nginx 프록시 서비스입니다. "
-"Ingress(Nginx)는 클러스터 공용 IP를 통해 접근할 수 있습니다. - 예시, "
-"``kubectl get pods -o wide --all-namespace | grep ingress-api`` 와 관련된 "
-"IP. Ingress/Nginx 는 \\\"keystone\\\" 또는 \\\"keystone.openstack\\\" 의 서버"
-"명 요청을 수신 대기하고 요청들을 적절한 내부 K8s 서비스로 경로를 설정할 것입"
-"니다. Ingress의 공용 리스너는 OpenStack 배포에 액세스하도록 설정할 외부 DNS"
-"와 일치해야 합니다. 각 규칙에는 Ingress Controller가 클러스터 내에서 endpoint"
-"에 대한 접근을 허용하도록 지시하는 서비스 또한 있음을 참고하십시오."
-
-msgid "Examples"
-msgstr "예제"
-
-msgid "Exercise the Cloud"
-msgstr "클라우드 실습"
-
-msgid "External DNS and FQDN"
-msgstr "외부 DNS와 FQDN"
-
-msgid "External DNS to FQDN/Ingress"
-msgstr "외부 DNS에서 FQDN/Ingress"
-
-msgid ""
-"First you have to set up OpenStack and Linux versions and install needed "
-"packages"
-msgstr "우선 오픈스택과 리눅스 버전 및 필수 패키지를 설치해야 합니다. "
-
-msgid ""
-"For ``identity`` and ``dashboard`` at ``host_fdqn_override.public`` replace "
-"``null`` with the value as ``keystone.os.foo.org`` and ``horizon.os.foo.org``"
-msgstr ""
-"``host_fdqn_override.public`` 의 ``identity`` 와 ``dashboard`` 에서 ``null`` "
-"값을 ``keystone.os.foo.org`` 와 ``horizon.os.foo.org`` 으로 바꾸십시오."
-
-msgid ""
-"For a deployment without cinder and horizon the system requirements are:"
-msgstr "cinder와 horizon 없이 배포하기 위한 시스템 요구 사항:"
-
-msgid ""
-"For a lab or proof-of-concept environment, the OpenStack-Helm gate scripts "
-"can be used to quickly deploy a multinode Kubernetes cluster using KubeADM "
-"and Ansible. Please refer to the deployment guide `here <./kubernetes-gate."
-"html>`__."
-msgstr ""
-"Lab이나 PoC 환경인 경우, OpenStack-Helm 게이트 스크립트를 이용하여 KubeADM과 "
-"Ansible을 사용한 멀티노드 Kubernetes 클러스터를 빠르게 구성할 수 있습니다. 자"
-"세한 배포 가이드는 `여기 <./kubernetes-gate.html>`__ 를 참조하십시오."
-
-msgid "For more details, refer to TaaS specification: Tap-as-a-service_."
-msgstr "더 자세한 내용은 TaaS 사양서를 참조하십시오: Tap-as-a-service_"
-
-msgid ""
-"For other deployment options, select appropriate ``Deployment with ...`` "
-"option from `Index <../developer/index.html>`__ page."
-msgstr ""
-"다른 배포 옵션의 경우, `Index <../developer/index.html>`__ 페이지에서 적절한 "
-"``Deployment with ...`` 옵션을 선택하십시오."
-
-msgid "Gate-Based Kubernetes"
-msgstr "Gate 기반 Kubernetes"
-
-msgid "Get the Nginx configuration from the Ingress Pod:"
-msgstr "Ingress Pod에서 Ningx 구성을 가져옵니다:"
-
-msgid "Get the ``helm status`` of your chart."
-msgstr "Chart에서 ``helm status`` 를 가져옵니다."
-
-msgid "Helm Chart Installation"
-msgstr "Helm Chart 설치"
-
-msgid "Host Configuration"
-msgstr "호스트 구성"
-
-msgid "Host Proxy & DNS Configuration"
-msgstr "Host Proxy & DNS 설정"
-
-msgid ""
-"If doing an `AIO install <https://docs.openstack.org/openstack-helm/latest/"
-"install/developer/index.html>`__, all the ``--set`` flags"
-msgstr ""
-"만약 `AIO install <https://docs.openstack.org/openstack-helm/latest/install/"
-"developer/index.html>`__ 을 하려면, 모두 ``--set`` 플러그를 설정합니다."
-
-msgid ""
-"If you are not deploying OSH behind a proxy, skip this step and continue "
-"with \"Deploy Kubernetes & Helm\"."
-msgstr ""
-"프록시 뒷단에 OSH를 구성하는 게 아니라면, 이 단계를 건너 뛰고 \"Deploy "
-"Kubernetes & Helm\" 단계에서 시작하십시오."
-
-msgid "If you are not deploying OSH behind a proxy, skip this step."
-msgstr "프록시 뒷단에 OSH를 구성하는 게 아니라면, 이 단계를 건너 뛰십시오."
-
-msgid ""
-"Implementing the FQDN overrides **must** be done at install time. If you run "
-"these as helm upgrades, Ingress will notice the updates though none of the "
-"endpoint build-out jobs will run again, unless they are cleaned up manually "
-"or using a tool like Armada."
-msgstr ""
-"설치 시에 FQDN 오버라이드 구현을 **반드시** 해야합니다. helm 업그레이드로 실"
-"행하면, 수동으로 정리되거나 Armada와 같은 도구를 사용하지 않는 한, 어떤 "
-"endpoint 구축 작업도 재실행되지 않을 것이기 때문에  Ingress는 업데이트를 알"
-"릴 것입니다. "
-
-msgid ""
-"In order to access your OpenStack deployment on Kubernetes we can use the "
-"Ingress Controller or NodePorts to provide a pathway in. A background on "
-"Ingress, OpenStack-Helm fully qualified domain name (FQDN) overrides, "
-"installation, examples, and troubleshooting will be discussed here."
-msgstr ""
-"Kubernetes에서 OpenStack 배포에 접근하기 위해 Ingress Controller 또는 진입 경"
-"로를 제공하는 NodePorts 를 사용할 수 있습니다. Ingress의 배경지식으로, "
-"OpenStack-Helm의 fully qualified domain name(FQDN) 오버라이드, 설치, 예시, 그"
-"리고 트러블슈팅이 여기서 논의될 것입니다."
-
-msgid ""
-"In order to allow OVS inside a pod to make use of hugepages, the "
-"corresponding type and amount of hugepages must be specified in the resource "
-"section of the OVS chart's values.yaml:"
-msgstr ""
-"pod 내부의 OVS가 hugepage를 사용하도록 하려면, OVS 차트의 values.yml 자원 섹"
-"션에서  일치하는 유형과 hugepage의 용량을 특정해야 합니다."
-
-msgid ""
-"In order to deploy OpenStack-Helm behind corporate proxy servers, add the "
-"following entries to ``openstack-helm-infra/tools/gate/devel/local-vars."
-"yaml``."
-msgstr ""
-"기업 프록시 서버에서 OpenStack-Helm을 배포하려면,  ``openstack-helm-infra/"
-"tools/gate/devel/local-vars.yaml`` 에 다음의 항목들을 추가하십시오."
-
-msgid ""
-"In order to drive towards a production-ready OpenStack solution, our goal is "
-"to provide containerized, yet stable `persistent volumes <https://kubernetes."
-"io/docs/concepts/storage/persistent-volumes/>`_ that Kubernetes can use to "
-"schedule applications that require state, such as MariaDB (Galera). Although "
-"we assume that the project should provide a \"batteries included\" approach "
-"towards persistent storage, we want to allow operators to define their own "
-"solution as well. Examples of this work will be documented in another "
-"section, however evidence of this is found throughout the project. If you "
-"find any issues or gaps, please create a `story <https://storyboard."
-"openstack.org/#!/project/886>`_ to track what can be done to improve our "
-"documentation."
-msgstr ""
-"제품으로 사용이 완료된 OpenStack 솔루션을 목표로 우리는 Kubernetes 가 "
-"MariaDB (Galera)와 같이 상태를 필요로하는 스케쥴 애플리케이션에서 사용할 수 "
-"있는 컨테이너화된 안정적인 `persistent volumes <https://kubernetes.io/docs/"
-"concepts/storage/persistent-volumes/>`_ 를 제공하는 것입니다. 프로젝트에서 "
-"presistent storage에 대한 \"배터리 포함(batteries included)\" 접근 방식을 제"
-"공해야한다고 가정하지만 운영자가 자체 솔루션을 정의할 수 있도록 하고 싶습니"
-"다. 이 작업에 대한 예제는 다른 절에서 문서화 될 것이지만, 이 증명은 프로젝트 "
-"전체에서 확인됩니다. 문제가 있거나 틈이 발견되면 문서를 개선하기 위해 수행할 "
-"수 있는 `story <https://storyboard.openstack.org/#!/project/886>`_ 를 생성하"
-"여 추적할 수 있도록 작성하십시오."
-
-msgid ""
-"In the example above, bonding isn't used and hence an empty list is passed "
-"in the \"bonds\" section."
-msgstr ""
-"위 예제에서는, 본딩이 사용되지 않았기 때문에 비어 있는 리스트가 \"bonds\" 섹"
-"션으로 전달 됩니다. "
-
-msgid ""
-"In this example, 8 hugepages of 1G size have been allocated. 2 of those are "
-"being used and 6 are still available."
-msgstr ""
-"이 예제에서는 1G의 8 hugepage가 할당되었습니다. 그 중 2개는 사용 중이고 6개"
-"는 사용 가능합니다. "
-
-msgid "Ingress"
-msgstr "Ingress"
-
-msgid "Install Basic Utilities"
-msgstr "기본 유틸리티를 설치하십시오."
-
-msgid "Install OpenStack packages"
-msgstr "오픈스택 패키지를 설치하십시오."
-
-msgid "Install OpenStack-Helm"
-msgstr "OpenStack-Helm 설치"
-
-msgid "Install k8s Minikube"
-msgstr "k8s Minikube를 설치하십시오."
-
-msgid "Installation"
-msgstr "설치"
-
-msgid ""
-"It can be configured to give services externally-reachable URLs, load "
-"balance traffic, terminate SSL, offer name based virtual hosting, and more."
-msgstr ""
-"외부적으로 도달 가능한 URL, 로드 밸런스 트래픽, SSL 종료, 이름 기반 가상 호스"
-"팅 제공 등의 서비스를 제공하도록 구성할 수 있습니다."
-
-msgid ""
-"It is recommended to add your own existing DNS nameserver entries to avoid "
-"losing connection."
-msgstr ""
-"연결 끊김을 방지하기 위해서는 기존 DNS 네임서버 항목을 별도로 추가하는 것이 "
-"권장됩니다. "
-
-msgid "Kubernetes Preparation"
-msgstr "Kubernetes 준비"
-
-msgid "Kubernetes and Common Setup"
-msgstr "Kubernetes와 일반 설치"
-
-msgid "Latest Version Installs"
-msgstr "최신 버전 설치"
-
-msgid "List the keypair(s) generated during the script execution::"
-msgstr "스크립트 실행 중 생성된 키쌍을 나열합니다::"
-
-msgid ""
-"Look for *server* configuration with a *server_name* matching your desired "
-"FQDN"
-msgstr ""
-"원하는 FQDN과 일치하는 *server_name* 을 가진 *server* 에대한 구성을 찾습니다"
-
-msgid ""
-"Managing and configuring a Kubernetes cluster is beyond the scope of "
-"OpenStack-Helm and this guide."
-msgstr ""
-"Kubernetes 클러스터를 관리하고 구성하는 내용은 OpenStack-Helm과 이 가이드에서"
-"는 다루지 않습니다."
-
-msgid ""
-"Manually remove the keypair directories created from the script in the ~/."
-"ssh directory::"
-msgstr ""
-"~/.ssh 디렉토리의 스크립트에서 생성 된 키페어 디렉토리를 수동으로 삭제하십시"
-"오::"
-
-msgid ""
-"Many of the default container images that are referenced across OpenStack-"
-"Helm charts are not intended for production use; for example, while LOCI and "
-"Kolla can be used to produce production-grade images, their public reference "
-"images are not prod-grade.  In addition, some of the default images use "
-"``latest`` or ``master`` tags, which are moving targets and can lead to "
-"unpredictable behavior.  For production-like deployments, we recommend "
-"building custom images, or at minimum caching a set of known images, and "
-"incorporating them into OpenStack-Helm via values overrides."
-msgstr ""
-"OpenStack-Helm chart 에서 참조되는 많은 기본 컨테이너 이미지는 실사용의 용도"
-"로 사용되지 않습니다. 예를 들어 LOCI와 Kolla는 프로덕션 등급 이미지를 구성하"
-"는데 사용할 수 있지만 공개 참조 이미지는 생산성이 떨어집니다. 또한 일부 기본 "
-"이미지는 ``latest`` 또는 ``master`` 태그를 사용하는데, 이는 변경될 수 있는 태"
-"그이기에 예측 할 수 없는 행동을 유발할 수 있습니다. 프로덕션과 같은 배포의 경"
-"우, 커스텀 이미지를 작성하거나 알려진 이미지 세트를 캐싱하고 값을 재정의하여 "
-"OpenStack-Helm에 통합하는 것이 좋습니다."
-
-msgid ""
-"More information can be found in the `Openvswitch documentation <http://docs."
-"openvswitch.org/en/latest/intro/install/dpdk/>`_."
-msgstr ""
-"더 많은 정보는 `Openvswitch 문서 <http://docs.openvswitch.org/en/latest/"
-"intro/install/dpdk/>`_에서  확인할 수 있습니다."
-
-msgid ""
-"More information on how to allocate and configure hugepages on the host OS "
-"can be found in the `Openvswitch documentation <http://docs.openvswitch.org/"
-"en/latest/intro/install/dpdk/>`_."
-msgstr ""
-"호스트 OS에 hugepage를 설정하고 할당하는 방법에 대한 더 많은 정보는 "
-"`Openvswitch documentation <http://docs.openvswitch.org/en/latest/intro/"
-"install/dpdk/>`_에서 확인 가능합니다."
-
-msgid "Multinode"
-msgstr "멀티노드"
-
-msgid "Neutron TaaS Architecture"
-msgstr "Neutron TaaS 아키텍처"
-
-msgid "Neutron and Horizon LOCI images"
-msgstr "Neutron과 Horizon 이미지들"
-
-msgid ""
-"Note if you need to make a DNS change, you will have to do uninstall (``helm "
-"delete <chart>``) and install again."
-msgstr ""
-"DNS 변경이 필요한 경우, 제거 (``helm delete <chart>``) 하고 다시 설치해야 할 "
-"것임을 참고하십시오."
-
-msgid ""
-"Note that this command will only enable you to auth successfully using the "
-"``python-openstackclient`` CLI. To use legacy clients like the ``python-"
-"novaclient`` from the CLI, reference the auth values in ``/etc/openstack/"
-"clouds.yaml`` and run::"
-msgstr ""
-"이 명령은 ``python-openstackclient`` CLI를 사용하여 성공적으로 인증할 수 있"
-"을 것임을 참고하십시오. CLI에서 ``python-novaclient`` 와 같은 레거시 클라이언"
-"트를 사용하려면, ``/etc/openstack/clouds.yaml`` 의 인증값을 참조하고 다음을 "
-"실행합니다:"
-
-msgid "OSH Proxy & DNS Configuration"
-msgstr "OSH Proxy & DNS 설정"
-
-msgid "OVS startup failure"
-msgstr "OVS 기동 실패"
-
-msgid ""
-"On the host or master node, install the latest versions of Git, CA Certs & "
-"Make if necessary"
-msgstr ""
-"필요한 경우, 호스트 또는 마스터 노드에 최신 버전의 Git, CA Certs, 그리고 Make"
-"를 설치하십시오"
-
-msgid "On the master node create an environment file for the cluster:"
-msgstr "Master 노드에서 클러스터에 대한 환경 파일을 만듭니다:"
-
-msgid "On the master node create an inventory file for the cluster:"
-msgstr "클러스터에 대한 인벤토리 파일을 master 노드에 생성합니다:"
-
-msgid "On the master node run the playbooks:"
-msgstr "Master 노드에서 플레이북 실행:"
-
-msgid "On the worker nodes:"
-msgstr "Worker 노드에서:"
-
-msgid ""
-"Once OpenStack-Helm has been deployed, the cloud can be exercised either "
-"with the OpenStack client, or the same heat templates that are used in the "
-"validation gates."
-msgstr ""
-"OpenStack-Helm이 배포되면, OpenStack client 또는 검증 게이트에서 사용되는 것"
-"과 동일한 heat 템플릿으로 클라우드를 실습할 수 있습니다."
-
-msgid ""
-"Once installed, access the API's or Dashboard at `http://horizon.os.foo.org`"
-msgstr ""
-"설치가 완료되면, API's 나 `http://horizon.os.foo.org` 대시보드로 접속합니다."
-
-msgid ""
-"Once the above requirements are met, start deploying Openstack Helm using "
-"the deployment scripts under the dpdk directory in an increasing order"
-msgstr ""
-"위의 요구 사항이 충족 되었다면, dpk 디렉토리에서 오름차순으로 배포 스크립트"
-"를 이용해서 Openstack Helm을 시작하십시오. "
-
-msgid ""
-"Once the host has been configured the repos containing the OpenStack-Helm "
-"charts should be cloned onto each node in the cluster:"
-msgstr ""
-"호스트가 구성되면, OpenStack-Helm chart 가 포함된 repo가 클러스터 각 노드에 "
-"복제됩니다."
-
-msgid ""
-"Once the host has been configured the repos containing the OpenStack-Helm "
-"charts should be cloned:"
-msgstr ""
-"호스트가 구성되면 OpenStack-Helm 차트가 포함된 저장소가 clone되어야 합니다:"
-
-msgid ""
-"OpenStack-Helm uses the hosts networking namespace for many pods including, "
-"Ceph, Neutron and Nova components. For this, to function, as expected pods "
-"need to be able to resolve DNS requests correctly. Ubuntu Desktop and some "
-"other distributions make use of ``mdns4_minimal`` which does not operate as "
-"Kubernetes expects with its default TLD of ``.local``. To operate at "
-"expected either change the ``hosts`` line in the ``/etc/nsswitch.conf``, or "
-"confirm that it matches:"
-msgstr ""
-"OpenStack-Helm은 Ceph, Neutron 및 Nova 구성 요소를 포함한 많은 pod를 위한 호"
-"소트 네트워킹 네임스페이스를 사용합니다. 이를 위해, 기능적으로, 예상되는 pod"
-"들은 DNS 요청을 정확하게 해결할 수 있을 필요가 있습니다. Ubuntu Desktop과 다"
-"른 배포판은 Kubernetes가 ``.local`` 의 기본 TLD로 예상하여 동작하지 않는 "
-"``mdns4_minimal`` 을 활용합니다. 예상대로 동작하려면 ``/etc/nsswitch.conf`` "
-"의 ``hosts`` 행을 변경하거나 일치하는지 확인하십시오:"
-
-msgid ""
-"OpenStack-Helm utilizes the `Kubernetes Ingress Controller <https://"
-"kubernetes.io/docs/concepts/services-networking/ingress/>`__"
-msgstr ""
-"OpenStack-Helm 은 `Kubernetes Ingress Controller <https://kubernetes.io/docs/"
-"concepts/services-networking/ingress/>`__ 을 활용합니다."
-
-msgid "OpenStack-Helm-Infra KubeADM deployment"
-msgstr "OpenStack-Helm-Infra KubeADM 배포"
-
-msgid ""
-"Other versions and considerations (such as other CNI SDN providers), config "
-"map data, and value overrides will be included in other documentation as we "
-"explore these options further."
-msgstr ""
-"다른 버전과 고려 사항들(다른 CNI SDN 제공자들과 같은), 설정 맵 데이터, 값 오"
-"버라이드는 우리가 옵션들을 더 자세히 조사할때 다른 문서에 포함될 것입니다."
-
-msgid "Override images in Neutron chart"
-msgstr "Neutron 차트 이미지를 재정의합니다"
-
-msgid "Overview"
-msgstr "개요"
-
-msgid "PMD threads have been assigned to NUMA socket 1."
-msgstr "PMD 쓰레드가 NUMA socket 1에 할당 되었습니다."
-
-msgid "Passwordless Sudo"
-msgstr "Sudo 비밀번호 생략"
-
-msgid ""
-"Please see the supported application versions outlined in the `source "
-"variable file <https://github.com/openstack/openstack-helm-infra/blob/master/"
-"roles/build-images/defaults/main.yml>`_."
-msgstr ""
-"`소스 변수 파일 <https://github.com/openstack/openstack-helm-infra/blob/"
-"master/roles/build-images/defaults/main.yml>`_ 에 작성된 애플리케이션 버전을 "
-"확인하십시오."
-
-msgid "Plugins"
-msgstr "플러그인"
-
-msgid "Prepare LOCI images"
-msgstr "LOCI 이미지 준비"
-
-msgid ""
-"Prepare Neutron or Horizon LOCI image using this requirements image as :code:"
-"`docker build --build-arg WHEELS` command argument."
-msgstr ""
-"Requirements 이미지를 :code:`docker build --build-arg WHEELS` 명령을 사용해"
-"서 Neutron / Horizon LOCI 이미지를 준비합니다."
-
-msgid ""
-"Prepare a requirements LOCI image with Neutron TaaS and TaaS Dashboard code "
-"installed."
-msgstr ""
-"Neutron TaaS, TaaS Dashboard 코드가 설치된 requirements LOCI 이미지를 준비합"
-"니다."
-
-msgid ""
-"Prepare ahead of time your FQDN and DNS layouts. There are a handful of "
-"OpenStack endpoints you will want to expose for API and Dashboard access."
-msgstr ""
-"미리 FQDN과 DNS 레이아웃을 준비하십시오. API와 대시보드 접근을 위해 공개하는 "
-"소수의 OpenStack endpoint 가 있습니다."
-
-msgid "Prepare host"
-msgstr "호스트를 준비하십시오."
-
-msgid "Prepare host and openstack helm for tf"
-msgstr "호스트와 tf를 사용하기 위한 오픈스택 헬름을 준비하십시오."
-
-msgid "Proxy Configuration"
-msgstr "프록시 구성"
-
-msgid "Putting it all together"
-msgstr "종합하자면"
-
-msgid "References"
-msgstr "참고"
-
-msgid "Removing Helm Charts"
-msgstr "Helm 차트 제거"
-
-msgid "Requirements"
-msgstr "요구 사항"
-
-msgid "Requirements LOCI image"
-msgstr "Requirements LOCI 이미지"
-
-msgid "Requirements and Host Configuration"
-msgstr "요구 사항 및 호스트 구성"
-
-msgid "Run the playbooks"
-msgstr "플래이북 실행"
-
-msgid "SSH-Key preparation"
-msgstr "SSH-Key 준비"
-
-msgid ""
-"Set correct ownership: ``sudo chown ubuntu /etc/openstack-helm/deploy-key."
-"pem``"
-msgstr ""
-"Ownership 변경: ``sudo chown ubuntu /etc/openstack-helm/deploy-key.pem``"
-
-msgid "Set log level for TaaS"
-msgstr "TaaS에 대한 로그 레벨을 설정하십시오."
-
-msgid ""
-"Set your local environment variables to use the proxy information. This "
-"involves adding or setting the following values in ``/etc/environment``:"
-msgstr ""
-"프록시 정보를 사용하기 위한 로컬 환경 변수를 설정하십시오. 이는 ``/etc/"
-"environment``의 값을 설정하거나 추가하는 것을 포함합니다. :"
-
-msgid "Setup Clients on the host and assemble the charts"
-msgstr "호스트의 클라이언트 설치 및 차트 assemble"
-
-msgid "Setup DNS for use cluster DNS"
-msgstr "클러스터 DNS 용도의 DNS 설치"
-
-msgid "Setup Glance"
-msgstr "Glance 설치"
-
-msgid "Setup Heat"
-msgstr "Heat 설치"
-
-msgid "Setup Ingress"
-msgstr "Ingress 설치"
-
-msgid "Setup Keystone"
-msgstr "Keystone 설치"
-
-msgid "Setup MariaDB"
-msgstr "MariaDB 설치"
-
-msgid "Setup Memcached"
-msgstr "Memchaced 설치"
-
-msgid "Setup NFS"
-msgstr "NFS 설치"
-
-msgid "Setup Neutron and Nova"
-msgstr "Neturon과 Nova 설치"
-
-msgid "Setup OpenStack client"
-msgstr "오픈스택 클라이언트를 설치하십시오."
-
-msgid "Setup RabbitMQ"
-msgstr "RabbitMQ 설치"
-
-msgid "Setup Tungsten Fabric"
-msgstr "Tungsten Fabric 설치"
-
-msgid "Setup libvirt"
-msgstr "libvirt 설치"
-
-msgid "Setup the gateway to the public network"
-msgstr "공용 네트워크로의 게이트웨이 설치"
-
-msgid "System Requirements"
-msgstr "시스템 요구 사항"
-
-msgid "TaaS Architecture"
-msgstr "TaaS 아키텍처"
-
-msgid ""
-"TaaS plugin provides a mechanism to mirror certain traffic (for example "
-"tagged with specific VLANs) from a source VM to any traffic analyzer VM. "
-"When packet will be forwarded, the original value of source and target ip/"
-"ports information will not be altered and the system administrator will be "
-"able to run, for ex. tcpdump, on the target VM to trace these packets."
-msgstr ""
-"TaaS 플러그인은 소스 VM에서 모든 트레픽을 분석하는 VM으로 특정 트래픽 (예, 특"
-"정 VLAN 테그)을 미러링하는 메커니즘을 제공합니다. 패킷이 전달 될때 원본과 타"
-"겟 IP/Port 정보를 기존 값 변경없이 시스템 관리자가 실행할 수 있습니다. 예: 패"
-"킷 추적을 위해 타겟 VM에서 tcpdump를 실행합니다"
-
-msgid ""
-"Test this by ssh'ing to a node and then executing a command with 'sudo'. "
-"Neither operation should require a password."
-msgstr ""
-"노드에 ssh 로 접속하여 'sudo' 명령을 실행하여 테스트합니다. 이 작업에서는 암"
-"호를 물어보지 않습니다."
-
-msgid ""
-"The OpenStack clients and Kubernetes RBAC rules, along with assembly of the "
-"charts can be performed by running the following commands:"
-msgstr ""
-"차트 assembly와 마찬가지로, OpenStack 클라이언트 및 Kubernetes RBAC 규칙들은 "
-"다음 명령을 실행하여 수행될 수 있습니다."
-
-msgid ""
-"The `./tools/deployment/multinode/kube-node-subnet.sh` script requires "
-"docker to run."
-msgstr ""
-"`./tools/deployment/multinode/kube-node-subnet.sh`스크립트는 docker에서 실행"
-"되어야 합니다."
-
-msgid ""
-"The ``.svc.cluster.local`` address is required to allow the OpenStack client "
-"to communicate without being routed through proxy servers. The IP address "
-"``172.17.0.1`` is the advertised IP address for the Kubernetes API server. "
-"Replace the addresses if your configuration does not match the one defined "
-"above."
-msgstr ""
-"``.svc.cluster.local`` 주소는 프록시 서버를 통해 라우팅하지 않고 OpenStack 클"
-"라이언트와 통신할 수 있도록 하는 것을 필요로 합니다. IP 주소 ``172.17.0.1`` "
-"은 Kubernetes API 서버를 위해 알려진 주소입니다. 구성이 위에 정의된 것과 일치"
-"하지 않으면 주소를 교체하십시오."
-
-msgid "The default FQDN's for OpenStack-Helm are"
-msgstr "OpenStack-Helm을 위한 기본 FQDN은 다음과 같습니다."
-
-msgid ""
-"The example above uses the default values used by ``openstack-helm-infra``."
-msgstr ""
-"위의 예제는 ``openstack-helm-infra`` 에서 사용되는 기본값들을 사용합니다."
-
-msgid ""
-"The following commands all assume that they are run from the ``/opt/"
-"openstack-helm`` directory."
-msgstr ""
-"다음에 나오는 명령들이 ``/opt/openstack-helm`` 디렉토리에서 실행된다고 가정합"
-"니다."
-
-msgid ""
-"The following commands all assume that they are run from the ``openstack-"
-"helm`` directory and the repos have been cloned as above."
-msgstr ""
-"다음 명령은 ``openstack-helm`` 디렉터리에서 실행되고 저장소가 위와 같이 clone"
-"되어 있음을 가정합니다."
-
-msgid ""
-"The installation procedures below, will take an administrator from a new "
-"``kubeadm`` installation to OpenStack-Helm deployment."
-msgstr ""
-"아래의 설치 과정은 관리자가 새로운 ``kubeadm`` 설치에서 OpenStack-Helm 배포"
-"가 가능하게 합니다."
-
-msgid ""
-"The mapping of CPU cores to NUMA sockets can be determined by means of "
-"``lspci``, for instance:"
-msgstr ""
-"NUMA 소켓에 대응되는 CPU 코어는 ``lspci`` 명령을 통해 결정될 수 있습니다, 예"
-"를 들면:"
-
-msgid "The recommended minimum system requirements for a full deployment are:"
-msgstr "전체 배포를 위해 권장되는 시스템 최소 요구 사항:"
-
-msgid ""
-"The upstream Ceph image repository does not currently pin tags to specific "
-"Ceph point releases.  This can lead to unpredictable results in long-lived "
-"deployments.  In production scenarios, we strongly recommend overriding the "
-"Ceph images to use either custom built images or controlled, cached images."
-msgstr ""
-"업스트림 Ceph 이미지 저장소는 현재 특정 Ceph 포인트 릴리즈에 태그를 지정하지 "
-"않습니다. 이로 인해 오래전 배포된 시스템에서는 예기치 않은 결과가 발생할 수 "
-"있습니다. 프로덕션 시나리오에서는 Ceph 이미지를 재정의하여 커스텀 빌드 이미"
-"지 또는 제어된 캐시 이미지를 사용하는 것이 좋습니다."
-
-msgid ""
-"These commands will restore the environment back to a clean Kubernetes "
-"deployment, that can either be manually removed or over-written by "
-"restarting the deployment process. It is recommended to restart the host "
-"before doing so to ensure any residual state, eg. Network interfaces are "
-"removed."
-msgstr ""
-"이 명령들은 배포 프로세스를 재시작하여 수동으로 제거하거나 덮어써서, "
-"Kubernetes 배포 환경으로 복구할 것입니다. 잔여 상태를 확인하기 전에 호스트를 "
-"다시 시작하는 것을 권장합니다. 예시. 네트워크 인터페이스 제거 여부."
-
-msgid "These values can be retrieved by running:"
-msgstr "이 값들은 실행함으로써 조회 될 수 있습니다:"
-
-msgid ""
-"This guide assumes that users wishing to deploy behind a proxy have already "
-"defined the conventional proxy environment variables ``http_proxy``, "
-"``https_proxy``, and ``no_proxy``."
-msgstr ""
-"이 가이드는 프록시에서 배포하려는 사용자가 이미 일반 프록시 환경 변수 "
-"``http_proxy``, ``https_proxy``, 그리고 ``no_proxy`` 를 정의했다고 가정합니"
-"다."
-
-msgid "This guide covers the minimum number of requirements to get started."
-msgstr "이 가이드는 시작을 위한 최소한의 요구 사항들을 다룹니다."
-
-msgid ""
-"This guide explains how to deploy tap-as-a-service (TaaS) Neutron plugin and "
-"TaaS Dashboard plugin in Neutron and Horizon charts respectively."
-msgstr ""
-"이 가이드는 Neutron과 Horizon 차트에서의 TaaS (Tap-as-a-Service) Neutron 플러"
-"그인과 TaaS Dashboard 플러그인을 배포하는 방법에 대해서 설명합니다."
-
-msgid ""
-"This installation, by default will use Google DNS servers, 8.8.8.8 or "
-"8.8.4.4 and updates resolv.conf. These DNS nameserver entries can be changed "
-"by updating file ``/opt/openstack-helm-infra/tools/images/kubeadm-aio/assets/"
-"opt/playbooks/vars.yaml`` under section ``external_dns_nameservers``. This "
-"change must be done on each node in your cluster."
-msgstr ""
-"설치시 기본적으로 Google DNS 서버 (8.8.8.8, 8.8.4.4)를 사용하고 resolv.conf "
-"파일을 업데이트합니다. 이러한 DNS 네임서버 항목은 ``/opt/openstack-helm/"
-"infra/tools/images/kubeadm-aio/asserts/opt/playbooks/vars.yaml`` 파일에서 "
-"``external_dns_nameservers`` 섹션에서 업데이트하여 변경합니다. 이 변경은 클러"
-"스터에 속한 모든 노드에서 수행해야합니다."
-
-msgid "This is a two step process, i.e."
-msgstr "두 단계 프로세스 입니다."
-
-msgid ""
-"This will delete all Kubernetes resources generated when the chart was "
-"instantiated. However for OpenStack charts, by default, this will not delete "
-"the database and database users that were created when the chart was "
-"installed. All OpenStack projects can be configured such that upon deletion, "
-"their database will also be removed. To delete the database when the chart "
-"is deleted the database drop job must be enabled before installing the "
-"chart. There are two ways to enable the job, set the job_db_drop value to "
-"true in the chart's ``values.yaml`` file, or override the value using the "
-"helm install command as follows:"
-msgstr ""
-"이는 차트가 인스턴스화될 때 생성된 모든 Kubernetes 자원을 삭제할 것입니다. 그"
-"러나 OpenStack 차트의 경우, 기본적으로 차트를 설치할 때 생성된 데이터베이스"
-"와 데이터베이스 사용자는 삭제하지 않을 것입니다. 모든 OpenStack 프로젝트는 삭"
-"제 중에, 해당 데이터베이스 또한 제거되도록 구성할 수 있습니다. 차트가 삭제될 "
-"때 데이터베이스를 삭제하려면 차트를 설치하기 전에 데이터베이스 drop 작업이 사"
-"용 가능해야합니다. 작업을 사용 가능하도록 하는 두 가지 방법이 있습니다, 차트"
-"의 ``values.yaml`` 파일의 job_db_drop의 값을 true로 설정하거나, 다음의 helm "
-"설치 명령을 사용하여 값을 오버라이드하십시오:"
-
-msgid ""
-"Throughout this guide the assumption is that the user is: ``ubuntu``. "
-"Because this user has to execute root level commands remotely to other "
-"nodes, it is advised to add the following lines to ``/etc/sudoers`` for each "
-"node:"
-msgstr ""
-"이 가이드 전체에서 사용자: ``ubuntu`` 라 가정합니다. 이 사용자는 root 수준의 "
-"명령을 다른 노드에 원격으로 실행해야하기 때문에, 각 노드의 ``/etc/sudoers`` "
-"에 다음 줄을 추가하는 것을 권장합니다:"
-
-msgid ""
-"To copy the ssh key to each node, this can be accomplished with the ``ssh-"
-"copy-id`` command, for example: *ssh-copy-id ubuntu@192.168.122.178*"
-msgstr ""
-"각 노드에 ssh 키를 복사하려면, ``ssh-copy-id`` 명령을 사용하면됩니다. 예를 들"
-"어: *ssh-copy-id ubuntu@192.168.122.178*"
-
-msgid "To delete an installed helm chart, use the following command:"
-msgstr "설치된 helm 차트를 제거하려면, 다음의 명령을 사용하십시오:"
-
-msgid "To generate the key you can use ``ssh-keygen -t rsa``"
-msgstr "``ssh-keygen -t rsa`` 명령을 이용하여 키를 생성합니다."
-
-msgid "To get started with OSH, we will need  ``git``,  ``curl`` and ``make``."
-msgstr "OSH를 시작하려면,  ``git``,  ``curl`` and ``make`` 가 필요합니다. "
-
-msgid ""
-"To run further commands from the CLI manually, execute the following to set "
-"up authentication credentials::"
-msgstr ""
-"CLI 에서 수동으로 더 많은 명령들을 실행하기 위해, 다음의 인증 자격 증명서 설"
-"정을 실행하십시오:"
-
-msgid ""
-"To tear-down, the development environment charts should be removed first "
-"from the 'openstack' namespace and then the 'ceph' namespace using the "
-"commands from the `Removing Helm Charts` section. Additionally charts should "
-"be removed from the 'nfs' and 'libvirt' namespaces if deploying with NFS "
-"backing or bare metal development support. You can run the following "
-"commands to loop through and delete the charts, then stop the kubelet "
-"systemd unit and remove all the containers before removing the directories "
-"used on the host by pods."
-msgstr ""
-"해제하기 위해, 개발 환경 차트는 `Removing Helm Chart` 섹션의 명령을 사용하여 "
-"먼저 \\'openstack\\' 네임스페이스에서 제거되고 \\'ceph\\' 네임스페이스에서 제"
-"거되어야 합니다. NFS backing 이나 베어 메탈 개발 지원으로 배포하려면, 추가적"
-"인 차트는 \\'nfs\\' 와 \\'libvirt\\' 네임스페이스에서 제거되어야 합니다. 루프"
-"문을 통해 차트들을 삭제하고, kubelet systemd unit 을 중지하며, pod 별로 호스"
-"트에서 사용되는 디렉터리를 삭제하기 전에 모든 컨테이너들을 삭제합니다."
-
-msgid "Troubleshooting"
-msgstr "트러블 슈팅"
-
-msgid ""
-"Tungsten Fabric is the multicloud and multistack network solution which you "
-"can use for your OpenStack as a network plugin. This document decribes how "
-"you can deploy a single node Open Stack based on Tungsten Fabric using "
-"openstack helm for development purpose."
-msgstr ""
-"Tungsten Fabric은 오픈스택 네트워크 플러그인으로 사용할 수 있는 멀티 클라우"
-"드, 멀티 스택 솔루션입니다. 이 문서는 개발 목적으로 오픈 스택 헬름을 이용하"
-"여 Tungsten Fabric에 기반한 싱글 노드 오픈스택을 배포하는 방법에 대해 설명합"
-"니다. "
-
-msgid ""
-"Two similar options exist to set the FQDN overrides for External DNS mapping."
-msgstr ""
-"외부 DNS 매핑을 위한 FQDN 오버라이드를 설정하는 두 가지 유사한 옵션이 존재합"
-"니다."
-
-msgid ""
-"Until the Ubuntu kernel shipped with 16.04 supports CephFS subvolume mounts "
-"by default the `HWE Kernel <../troubleshooting/ubuntu-hwe-kernel.html>`__ is "
-"required to use CephFS."
-msgstr ""
-"Ubuntu 16.04 커널에서 서브 볼륨 마운트로 CephFS를 지원하기 전까지 `HWE "
-"Kernel <../troubleshooting/ubuntu-hwe-kernel.html>`__ 을 이용하여 CephFS를 사"
-"용해야합니다."
-
-msgid ""
-"Update your lab/environment DNS server with your appropriate host values "
-"creating A Records for the edge node IP's and various FQDN's. Alternatively "
-"you can test these settings locally by editing your ``/etc/hosts``. Below is "
-"an example with a dummy domain ``os.foo.org`` and dummy Ingress IP "
-"``1.2.3.4``."
-msgstr ""
-"엣지 노드 IP와 다양한 FQDN에 대한 A Record를 생성하여 적절한 호스트 값으로 실"
-"험실/환경 DNS 서버를 갱신합니다. 대안으로 ``/etc/hosts`` 를 편집하여 설정을 "
-"지역적으로 테스트할 수 있습니다. 아래는 더미 도메인 ``os.foo.org`` 와 더미 "
-"Ingress IP ``1.2.3.4`` 로 된 예시입니다."
-
-msgid "Using Horizon as an example, find the ``endpoints`` config."
-msgstr "Horizon을 예로 들 때, ``endpoints`` 구성을 찾으십시오."
-
-msgid ""
-"Using the Helm packages previously pushed to the local Helm repository, run "
-"the following commands to instruct tiller to create an instance of the given "
-"chart. During installation, the helm client will print useful information "
-"about resources created, the state of the Helm releases, and whether any "
-"additional configuration steps are necessary."
-msgstr ""
-"이전에 로컬 Helm 저장소로 push된 Helm 패키지를 사용하여, tiller가 주어진 차트"
-"의 인스턴스를 생성하는 것을 수행하도록 다음 명령을 실행하십시오. 설치 중에, "
-"helm 클라이언트는 자원의 생성, Helm 릴리즈 상태, 그리고 추가 구성 단계가 필요"
-"한지에 대한 유용한 정보를 출력할 것입니다."
-
-msgid "Verify the *v1beta1/Ingress* resource has a Host with your FQDN value"
-msgstr "*v1beta1/Ingress* 리소스에 FQDN 값이 있는 호스트가 있는지 확인합니다."
-
-msgid ""
-"We want to change the **public** configurations to match our DNS layouts "
-"above. In each Chart ``values.yaml`` is a ``endpoints`` configuration that "
-"has ``host_fqdn_override``'s for each API that the Chart either produces or "
-"is dependent on. `Read more about how Endpoints are developed <https://docs."
-"openstack.org/openstack-helm/latest/devref/endpoints.html>`__. Note while "
-"Glance Registry is listening on a Ingress http endpoint, you will not need "
-"to expose the registry for external services."
-msgstr ""
-"**public** 구성을 위의 DNS 레이아웃과 일치하도록 변경하고자 합니다. 각 차트에"
-"서 ``values.yaml`` 은 차트를 생산하거나 종속하는 각 API에 대해 "
-"``host_fqdn_override`` 를 갖고 있는 ``endpoints`` 구성입니다. `어떻게 "
-"Endpoint가 개발되는지에 대해 더 읽어보십시오 <https://docs.openstack.org/"
-"openstack-helm/latest/devref/endpoints.html>`__ . Glance 레지스트리가 "
-"Ingress http endpoint에서 수신 대기하는 동안, 외부 서비스를 위해 레지스트리"
-"를 노출할 필요가 없을 것임을 참고하십시오."
-
-msgid ""
-"You can use any Kubernetes deployment tool to bring up a working Kubernetes "
-"cluster for use with OpenStack-Helm. For production deployments, please "
-"choose (and tune appropriately) a highly-resilient Kubernetes distribution, "
-"e.g.:"
-msgstr ""
-"Kubernetes 배포 도구를 사용하여 OpenStack-Helm 과 함께 사용할 수 있는 "
-"Kubernetes 클러스터를 불러올 수 있습니다. 프로덕션 배포의 경우, 탄력적인 "
-"Kubernetes 배포를 선택하고 적절히 조정하십시오. 예:"
-
-msgid ""
-"You can use any Kubernetes deployment tool to bring up a working Kubernetes "
-"cluster for use with OpenStack-Helm. This guide describes how to simply "
-"stand up a multinode Kubernetes cluster via the OpenStack-Helm gate scripts, "
-"which use KubeADM and Ansible. Although this cluster won't be production-"
-"grade, it will serve as a quick starting point in a lab or proof-of-concept "
-"environment."
-msgstr ""
-"Kubernetes 배포 도구를 사용하여 OpenStack-Helm과 함께 사용할 수 있는 "
-"Kubernetes 클러스터를 불러올 수 있습니다. 이 가이드는 KubeADM과 Ansible을 사"
-"용하는 OpenStack-Helm 게이트 스크립트를 통해 간단하게 멀티 노드 Kubernetes 클"
-"러스터를 구성하는 방법에 대해 설명합니다. 이 클러스터는 프로덕션 수준은 아니"
-"지만 lab 이나 PoC 환경에서 빠른 시작을 할 수 있는 역할을 합니다."
-
-msgid ""
-"You may now deploy kubernetes, and helm onto your machine, first move into "
-"the ``openstack-helm`` directory and then run the following:"
-msgstr ""
-"이제 kubernetes와 helm을 머신에 배포할 수 있습니다. 먼저 ``openstack-helm`` "
-"디렉터리로 이동하여 다음을 실행하십시오:"
-
-msgid ""
-"`Airship <https://airshipit.org/>`_, a declarative open cloud infrastructure "
-"platform"
-msgstr ""
-"`Airship <https://airshipit.org/>`_, 선언형 오픈 클라우드 인프라 플랫폼"
-
-msgid ""
-"`KubeADM <https://kubernetes.io/docs/setup/independent/high-availability/"
-">`_, the foundation of a number of Kubernetes installation solutions"
-msgstr ""
-"`KubeADM <https://kubernetes.io/docs/setup/independent/high-availability/"
-">`_, 다수의 노드에 기초 구성이 가능한 Kubernetes 설치 솔루션"
-
-msgid "https://review.openstack.org/#/c/597200/"
-msgstr "https://review.openstack.org/#/c/597200/"
-
-msgid "https://review.openstack.org/#/c/607392/"
-msgstr "https://review.openstack.org/#/c/607392/"
-
-msgid "https://review.openstack.org/#/c/621606/"
-msgstr "https://review.openstack.org/#/c/621606/"
-
-msgid ""
-"node_one, node_two and node_three below are all worker nodes, children of "
-"the master node that the commands below are executed on."
-msgstr ""
-"아래의 node_one, node_two, node_three는 현재 클러스터의 worker 노드이며, 아"
-"래 명령이 실행되는 master 노드의 하위 노드입니다."
diff --git a/doc/source/locale/ko_KR/LC_MESSAGES/doc-troubleshooting.po b/doc/source/locale/ko_KR/LC_MESSAGES/doc-troubleshooting.po
deleted file mode 100644
index 4dccbb4bc4..0000000000
--- a/doc/source/locale/ko_KR/LC_MESSAGES/doc-troubleshooting.po
+++ /dev/null
@@ -1,202 +0,0 @@
-# Soonyeul Park <ardentpark@gmail.com>, 2018. #zanata
-# KEONWOO LEE <lkeonw0o@naver.com>, 2020. #zanata
-msgid ""
-msgstr ""
-"Project-Id-Version: openstack-helm 0.1.1.dev3462\n"
-"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2021-06-22 20:22+0000\n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-"PO-Revision-Date: 2020-09-08 02:58+0000\n"
-"Last-Translator: KEONWOO LEE <lkeonw0o@naver.com>\n"
-"Language-Team: Korean (South Korea)\n"
-"Language: ko_KR\n"
-"X-Generator: Zanata 4.3.3\n"
-"Plural-Forms: nplurals=1; plural=0\n"
-
-msgid "Backing up a PVC"
-msgstr "PVC 백업"
-
-msgid ""
-"Backing up a PVC stored in Ceph, is fairly straigthforward, in this example "
-"we use the PVC ``mysql-data-mariadb-server-0`` as an example, but this will "
-"also apply to any other services using PVCs eg. RabbitMQ, Postgres."
-msgstr ""
-"Ceph에 저장된 PVC를 백업하는 것은 아주 간단합니다. 본 예시에서 PVC의 ``mysql-"
-"data-mariadb-server-0`` 을 예로 들겠지만, 이는 또한 RabbitMQ, Postgres 와 같"
-"은 다른 서비스에도 적용 가능할 것입니다."
-
-msgid ""
-"Before proceeding, it is important to ensure that you have deployed a client "
-"key in the namespace you wish to fulfill ``PersistentVolumeClaims``. To "
-"verify that your deployment namespace has a client key:"
-msgstr ""
-"진행하기 전에, ``PersistentVolumeClaims`` 를 만족하기를 원하는 네임스페이스"
-"에 클라이언트 키를 배포했는지 보장하는 것이 중요합니다. 네임스페이스가 클라이"
-"언트 키를 가지고 있는지에 대한 검증은 다음과 같습니다:"
-
-msgid "Bugs and Feature requests"
-msgstr "버그와 기능 요청"
-
-msgid "Ceph"
-msgstr "Ceph"
-
-msgid "Ceph Deployment Status"
-msgstr "Ceph 배포 상태"
-
-msgid "Ceph Validating PVC Operation"
-msgstr "Ceph의 PVC 작업 검증"
-
-msgid "Ceph Validating StorageClass"
-msgstr "Ceph의 StorageClass 검증"
-
-msgid "Channels"
-msgstr "채널"
-
-msgid "Database Deployments"
-msgstr "데이터베이스 배포"
-
-msgid ""
-"First, we want to validate that Ceph is working correctly. This can be done "
-"with the following Ceph command:"
-msgstr ""
-"먼저, Ceph가 정확하게 작동하고 있는지 확인하고 싶습니다. 이는 다음과 같은 "
-"Ceph 명령을 통해 수행될 수 있습니다:"
-
-msgid "Galera Cluster"
-msgstr "Galera 클러스터"
-
-msgid "Getting help"
-msgstr "도움말"
-
-msgid "Installation"
-msgstr "설치"
-
-msgid "Join us on `Slack <http://slack.k8s.io/>`_ - #openstack-helm"
-msgstr "`Slack <http://slack.k8s.io/>`_ - #openstack-helm 에 가입합니다."
-
-msgid ""
-"Next we can look at the storage class, to make sure that it was created "
-"correctly:"
-msgstr ""
-"다음으로 올바르게 생성되었는지를 확인하기 위해, 저장소 클래스를 살펴볼 수 있"
-"습니다:"
-
-msgid ""
-"Note: This step is not relevant for PVCs within the same namespace Ceph was "
-"deployed."
-msgstr ""
-"참고: 이 단계는 Ceph가 배포된 동일한 네임스페이스 내의 PVC와는 관련이 없습니"
-"다."
-
-msgid "Once this has been done the workload can be restarted."
-msgstr "이 작업이 완료되면 워크로드를 재시작할 수 있습니다."
-
-msgid "PVC Preliminary Validation"
-msgstr "PVC 사전 검증"
-
-msgid "Persistent Storage"
-msgstr "Persistent 스토리지"
-
-msgid ""
-"Please, refer to `Contribution guidelines <../contributor/contributing."
-"html>`_."
-msgstr ""
-" `컨트리뷰션 가이드라인  <../contributor/contributing.html>`_ 을 참조하세요"
-
-msgid ""
-"Restoring is just as straightforward. Once the workload consuming the device "
-"has been stopped, and the raw RBD device removed the following will import "
-"the back up and create a device:"
-msgstr ""
-"복구도 마찬가지로 간단합니다. 장치를 소비하는 워크로드가 멈추고 raw RBD 장치"
-"가 제거되면, 다음과 같이 백업을 가져와 장치를 생성할 것입니다:"
-
-msgid ""
-"Sometimes things go wrong. These guides will help you solve many common "
-"issues with the following:"
-msgstr ""
-"가끔 이상이 발생할 때, 이 안내서가 다음과 같은 여러가지 일반적인 문제들을 해"
-"결하는 데 도움이 될 것입니다."
-
-msgid ""
-"The parameters are what we're looking for here. If we see parameters passed "
-"to the StorageClass correctly, we will see the ``ceph-mon.ceph.svc.cluster."
-"local:6789`` hostname/port, things like ``userid``, and appropriate secrets "
-"used for volume claims."
-msgstr ""
-"여기서 찾고있는 것은 매개 변수입니다. 매개 변수가 StorageClass를 올바르게 통"
-"과했는지 확인했다면, ``userid``, 그리고 볼륨 클레임을 위해 사용되는 적절한 비"
-"밀과 같은 ``ceph-mon.ceph.svc.cluster.local:6789`` hostname/port 를 확인할 "
-"수 있습니다."
-
-msgid ""
-"This guide is to help users debug any general storage issues when deploying "
-"Charts in this repository."
-msgstr ""
-"이 안내서는 사용자가 저장소에 차트를 배포할 때의 일반적인 저장소 문제들을 디"
-"버그하는 것을 돕기 위한 것입니다."
-
-msgid ""
-"This guide is to help users debug any general storage issues when deploying "
-"charts in this repository."
-msgstr ""
-"이 안내서는 사용자가 저장소에 차트를 배포할 때의 일반적인 저장소 문제들을 디"
-"버그하는 것을 돕기 위한 것입니다."
-
-msgid ""
-"To deploy the HWE kernel, prior to deploying Kubernetes and OpenStack-Helm "
-"the following commands should be run on each node:"
-msgstr ""
-"HWE 커널을 배포하려면, Kubernetes와 OpenStack-Helm을 배포하기 전에 각 노드에"
-"서 다음과 같은 명령을 실행해야 합니다."
-
-msgid ""
-"To make use of CephFS in Ubuntu the HWE Kernel is required, until the issue "
-"described `here <https://github.com/kubernetes-incubator/external-storage/"
-"issues/345>`_ is fixed."
-msgstr ""
-"Ubuntu에서 CephFS를 사용하려면, `여기 <https://github.com/kubernetes-"
-"incubator/external-storage/issues/345>`_ 에 기술된 문제가 해결될 때까지 HWE "
-"커널이 필요합니다."
-
-msgid "To test MariaDB, do the following:"
-msgstr "MariaDB를 테스트하려면, 다음과 같이 수행하십시오:"
-
-msgid ""
-"To validate persistent volume claim (PVC) creation, we've placed a test "
-"manifest `here <https://raw.githubusercontent.com/openstack/openstack-helm/"
-"master/tests/pvc-test.yaml>`_. Deploy this manifest and verify the job "
-"completes successfully."
-msgstr ""
-"persistent volume claim (PVC) 생성을 검증하기 위해서, `여기 <https://raw."
-"githubusercontent.com/openstack/openstack-helm/master/tests/pvc-test.yaml>`_ "
-"에 테스트 매니페스트를 배치하였습니다. 이 매니페스트를 배포하고 작업이 성공적"
-"으로 완료되었는지 확인합니다."
-
-msgid "Troubleshooting"
-msgstr "트러블슈팅"
-
-msgid "Ubuntu HWE Kernel"
-msgstr "Ubuntu HWE 커널"
-
-msgid ""
-"Use one of your Ceph Monitors to check the status of the cluster. A couple "
-"of things to note above; our health is `HEALTH\\_OK`, we have 3 mons, we've "
-"established a quorum, and we can see that all of our OSDs are up and in the "
-"OSD map."
-msgstr ""
-"Ceph 모니터 중 하나를 사용하여 클러스터의 상태를 점검하십시오. 위의 몇 가지 "
-"사항을 참고했을 때; health는 `HEALTH\\_OK`, mon은 3개로 quorum을 설정하였고, "
-"모든 OSD가 up되어 OSD 맵 안에 있음을 확인할 수 있습니다."
-
-msgid ""
-"Without this, your RBD-backed PVCs will never reach the ``Bound`` state.  "
-"For more information, see how to `activate namespace for ceph <../install/"
-"multinode.html#activating-control-plane-namespace-for-ceph>`_."
-msgstr ""
-"이것 없이는, RBD-backed PVC 는 절대로 ``Bound`` 상태가 될 수 없을 것입니다. "
-"더 많은 정보를 위해서는, 어떻게 `ceph를 위한 네임스페이스를 활성화 <../"
-"install/multinode.html#activating-control-plane-namespace-for-ceph>`_ 하는지 "
-"보십시오."
diff --git a/doc/source/locale/ko_KR/LC_MESSAGES/doc.po b/doc/source/locale/ko_KR/LC_MESSAGES/doc.po
deleted file mode 100644
index c401cbc0f7..0000000000
--- a/doc/source/locale/ko_KR/LC_MESSAGES/doc.po
+++ /dev/null
@@ -1,356 +0,0 @@
-# Ian Y. Choi <ianyrchoi@gmail.com>, 2018. #zanata
-# Soonyeul Park <ardentpark@gmail.com>, 2018. #zanata
-# Sungjin Kang <gang.sungjin@gmail.com>, 2018. #zanata
-msgid ""
-msgstr ""
-"Project-Id-Version: openstack-helm 0.1.1.dev3879\n"
-"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2022-10-24 20:45+0000\n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-"PO-Revision-Date: 2018-10-21 06:41+0000\n"
-"Last-Translator: Sungjin Kang <gang.sungjin@gmail.com>\n"
-"Language-Team: Korean (South Korea)\n"
-"Language: ko_KR\n"
-"X-Generator: Zanata 4.3.3\n"
-"Plural-Forms: nplurals=1; plural=0\n"
-
-msgid ":ref:`genindex`"
-msgstr ":ref:`genindex`"
-
-msgid ":ref:`search`"
-msgstr ":ref:`search`"
-
-msgid "Adding Services"
-msgstr "서비스 추가"
-
-msgid "Adding Tests"
-msgstr "테스트 추가"
-
-msgid ""
-"Any additional functions required for testing new charts or improving the "
-"gate workflow should be placed in the appropriate location."
-msgstr ""
-"새로운 차트들을 테스트하거나 게이트 워크 플로우를 개선하기 위한 추가적인 기능"
-"들은 적절한 장소에 위치해야 합니다."
-
-msgid ""
-"Any tests that do not use the Rally testing framework would need to be "
-"handled in the appropriate manner in launch script. This would ideally "
-"result in new functions that could be reused, or expansion of the gate "
-"scripts to include scenarios beyond basic service launches."
-msgstr ""
-"Rally 테스팅 프레임워크를 사용하지 않은 테스트는 시작 스크립트에서 적절한 방"
-"식으로 처리해야 합니다. 이는 재사용 될 수 있는 새로운 기능이나, 기본 서비스 "
-"시작 이상의 시나리오들을 포함하기 위한 게이트 스크립트들의 확장이라는 이상적"
-"인 결과를 가져올 것입니다."
-
-msgid ""
-"As charts for additional services are added to OpenStack-Helm, they should "
-"be included in the gates.  Adding new services to the gates allows a chart "
-"developer and the review team to identify any potential issues associated "
-"with a new service. All services are currently launched in the gate via a "
-"series of launch scripts of the format ``NNN-service-name.sh`` where ``NNN`` "
-"dictates the order these scripts are launched. The script should contain an "
-"installation command like:"
-msgstr ""
-"추가적인 서비스들을 위한 차트로서 OpenStack-Helm에 추가되기 위해, 그들은 그 "
-"게이트에 포함되어야만 합니다. 새로운 서비스들을 게이트에 추가하는 것은 차트 "
-"개발자와 검토 팀에게 새로운 서비스와 연관된 잠재적인 문제를 확인하는 것을 허"
-"락합니다. 모든 서비스는 현재 게이트 내에서 ``NNN``이 이 스크립트들이 시작되"
-"는 순서를 지정하는 ``NNN-service-name.sh``라는 일련의 시작 스크립트 형식을 통"
-"해 시작됩니다."
-
-msgid ""
-"As new charts are developed and the services are added to the gate, an "
-"associated Helm test should be introduced to the gates.  The appropriate "
-"place for executing these tests is in the respective service's launch "
-"script, and must be placed after the entry for installing the service and "
-"any associated overrides.  Any tests that use the Rally testing framework "
-"should leverage the helm_test_deployment function in the aforementioned "
-"funcs/helm.sh file. For example, a Helm test for Mistral might look like:"
-msgstr ""
-"새 차트들이 개발되고 서비스가 게이트에 추가되기 위해서, 연관된 Helm 테스트가 "
-"게이트에 도입되어야 합니다. 이러한 테스트들을 실행하기 위한 최적 위치는 각 서"
-"비스의 시작 스크립트에 있으며, 서비스와 관련 오버라이드들을 설치하기 위한 엔"
-"트리 뒤에 있어야 합니다. Rally 테스팅 프레임워크를 사용하는 테스트들은 앞서 "
-"언급한 funcs/helm.sh 파일의 helm_test_deployment 기능을 활용해야 합니다. 예"
-"를 들어, Mistral을 위한 Helm 테스트는 아래와 같이 보일 것입니다:"
-
-msgid ""
-"Bugs and enhancements are tracked via OpenStack-Helm's `Storyboard <https://"
-"storyboard.openstack.org/#!/project_group/64>`_."
-msgstr ""
-"버그 및 개선사항은 OpenStack-Helm의 `Storyboard <https://storyboard."
-"openstack.org/#!/project_group/64>`_ 에서 추적이 이루어집니다."
-
-msgid "Communication"
-msgstr "의사소통"
-
-msgid "Contents:"
-msgstr "목차:"
-
-msgid "Contributing"
-msgstr "기여하기"
-
-msgid ""
-"Developers wishing to work on the OpenStack-Helm project should always base "
-"their work on the latest code, available from the OpenStack-Helm git "
-"repository."
-msgstr ""
-"OpenStack-Helm 프로젝트에서 작업하고자 하는 개발자는 OpenStack-Helm git 저장"
-"소에서 제공하는 최신 코드를 가지고서 작업하여야 합니다."
-
-msgid ""
-"Functions for Helm specific operations, found in helm.sh.  These functions "
-"include: installing Helm, serving a Helm repository locally, linting and "
-"building all Helm charts, running Helm tests on a release, installing the "
-"helm template plugin, and running the helm template plugin against a chart."
-msgstr ""
-"Helm 특정 작업들을 위한 기능들은, helm.sh에서 찾을 수 있습니다. 이 기능들은 "
-"포함합니다: Helm 설치, 로컬의 Helm 저장소 제공, 모든 Helm 차트에 대한 linting"
-"과 building, 배포 상에서 Helm 테스트를 수행, Helm 템플릿 플러그인 설치, 그리"
-"고 차트에 대한 Helm 템플릿 플러그인을 실행합니다."
-
-msgid ""
-"Functions for Kubernetes specific operations, found in kube.sh.  These "
-"functions include: waiting for pods in a specific namespace to register as "
-"ready, waiting for all nodes to register as ready, install the requirements "
-"for the kubeadm-aio container used in the gates, building the kubeadm-aio "
-"container, launching the kubeadm-aio container, and replacing the kube-"
-"controller-manager with a specific image necessary for ceph functionality."
-msgstr ""
-"Kubernetes 특정 작업들을 위한 기능들은, kube.sh에서 찾을 수 있습니다. 이 기능"
-"들은 포함합니다: 준비 상태로 등록하기 위해 특정 namespace 내의 pod들을 대기, "
-"준비 상태로 등록하기 위해 모든 node를 대기, 게이트들에서 사용되는 kubeadm-"
-"aio 컨테이너를 위한 요구사항들을 설치, kubeadm-aio 컨테이너 빌드, kubeadm-"
-"aio 컨테이너 시작, 그리고 kube-controller-manager를 ceph 기능을 위해 필요한 "
-"특정 이미지로 대체."
-
-msgid ""
-"Functions for OpenStack specific operations, found in openstack.sh.  These "
-"functions include: waiting for a successful ping, and waiting for a booted "
-"virtual machine's status to return as ACTIVE."
-msgstr ""
-"OpenStack 특정 작업들을 위한 기능들은, openstack.sh에서 찾을 수 있습니다. 이 "
-"기능들은 포함합니다: 성공적인 ping을 대기, 그리고 부팅된 가상머신의 상태를 "
-"ACTIVE로 반환하기 위해 대기."
-
-msgid "Functions for common host preparation operations, found in common.sh"
-msgstr "일반 호스트 작업 준비 기능은, common.sh에서 찾을 수 있습니다."
-
-msgid ""
-"Functions for network specific operations, found in network.sh.  These "
-"functions include: creating a backup of the host's resolv.conf file before "
-"deploying the kubeadm environments, restoring the original resolv.conf "
-"settings, creating a backup of the host's /etc/hosts file before adding the "
-"hosts interface and address, and restoring the original /etc/hosts file."
-msgstr ""
-"네트워크 특정 작업들을 위한 기능들은, network.sh에서 찾을 수 있습니다. 이 기"
-"능들은 포함합니다: kubeadm 환경들에 배포하기 전에 호스트의 resolv.conf 파일"
-"의 백업을 생성, 원본 resolv.conf 설정들을 복구, hosts의 인터페이스와 주소를 "
-"추가하기 전에 호스트의 /etc/hosts 파일의 백업을 생성, 그리고 원본 /etc/hosts "
-"파일을 복구."
-
-msgid "Gate Checks"
-msgstr "게이트 점검 사항"
-
-msgid "Gate Functions"
-msgstr "게이트 기능"
-
-msgid "Gate Output"
-msgstr "게이트 출력"
-
-msgid "Indices and Tables"
-msgstr "색인 및 표"
-
-msgid "Installation and Development"
-msgstr "설치 및 배포"
-
-msgid ""
-"Join us on `Slack <https://kubernetes.slack.com/messages/C3WERB7DE/>`_ - "
-"#openstack-helm"
-msgstr ""
-"`Slack <https://kubernetes.slack.com/messages/C3WERB7DE/>`_ - #openstack-"
-"helm 에 가입합니다"
-
-msgid ""
-"Meeting Agenda Items: `Agenda <https://etherpad.openstack.org/p/openstack-"
-"helm-meeting-agenda>`_"
-msgstr ""
-"미팅 아젠다 항목: `Agenda <https://etherpad.openstack.org/p/openstack-helm-"
-"meeting-agenda>`_"
-
-msgid "Mission"
-msgstr "임무"
-
-msgid "OpenStack-Helm"
-msgstr "OpenStack-Helm"
-
-msgid "OpenStack-Helm Gates"
-msgstr "OpenStack-Helm 게이트"
-
-msgid "OpenStack-Helm currently checks the following scenarios:"
-msgstr "OpenStack-Helm은 현재 다음의 시나리오들을 점검합니다:"
-
-msgid ""
-"OpenStack-Helm's single node and multinode gates leverage the kubeadm-aio "
-"environment created and maintained for use as a development environment.  "
-"All information regarding the kubeadm-aio environment can be found here_."
-msgstr ""
-"OpenStack-Helm의 단일 노드와 다중 노드 게이트를 개발환경으로 사용하기 위해 생"
-"성되고 유지되는 kubeadm-aio 환경을 활용합니다. kubeadm-aio 환경에 관한 모든 "
-"정보는 여기에서 찾을 수 있습니다."
-
-msgid ""
-"Provisioning a multi-node Ubuntu-1604 cluster and deploying the OpenStack "
-"services. This check is provided for both a two node cluster and a three "
-"node cluster."
-msgstr ""
-"다중 노드의 Ubuntu-1604 클러스터를 프로비저닝하고 OpenStack 서비스에 배포합니"
-"다. 두 노드와 세 노드의 클러스터 모두 이를 제공합니다."
-
-msgid ""
-"Provisioning a single node cluster and deploying the OpenStack services.  "
-"This check is provided for: Ubuntu-1604, CentOS-7, and Fedora-25."
-msgstr ""
-"단일 노드를 프로비저닝하고 OpenStack 서비스에 배포합니다. Ubuntu-1604, "
-"CentOS-7, 그리고 Fedora-25가 이를 제공합니다. "
-
-msgid "Repository"
-msgstr "저장소"
-
-msgid ""
-"Running Make on each chart, which lints and packages the charts.  This gate "
-"does not stand up a Kubernetes cluster."
-msgstr ""
-"lint하고 package한 각 chart마다 make를 실행합니다. 이 게이트는 Kubernes 클러"
-"스터를 유지하지 않습니다."
-
-msgid ""
-"Some services in the gate require specific overrides to the default values "
-"in the chart's values.yaml file.  If a service requires multiple overrides "
-"to function in the gate, the service should include a separate values.yaml "
-"file placed in the tools/overrides/mvp directory.  The <service>.yaml MVP "
-"files provide a configuration file to use for overriding default "
-"configuration values in the chart's values.yaml as an alternative to "
-"overriding individual values during installation.  A chart that requires a "
-"MVP overrides file requires the following format:"
-msgstr ""
-"게이트의 어떤 서비스는 차트의 value.yaml 파일의 기본값에 대한  특정 오버라이"
-"드들을 요구합니다. 서비스가 게이트에서 기능하기 위한 다수의 오버라이드를 요구"
-"한다면, 그 서비스는 tools/overrides/mvp 디렉터리 내 별도의 values.yaml 파일"
-"을 포함해야 합니다. <service>.yaml MVP 파일들은 설치 중에 오버라이딩한 개개"
-"의 값들에 대한 대안으로 차트의 values.yaml의 기본 구성 값들을 오버라이딩 하"
-"여 사용하기 위한 구성 파일을 제공합니다. MVP 오버라이드 파일이 요구한 차트는 "
-"다음의 포맷을 요구로 합니다:"
-
-msgid "Storyboard"
-msgstr "Storyboard"
-
-msgid "Testing any documentation changes and impacts."
-msgstr "문서 변경과 영향 테스트"
-
-msgid ""
-"The K8s directory contains the logs and output of the Kubernetes objects.  "
-"It includes: pods, nodes, secrets, services, namespaces, configmaps, "
-"deployments, daemonsets, and statefulsets.  Descriptions for the state of "
-"all resources during execution are found here, and this information can "
-"prove valuable when debugging issues raised during a check.  When a single "
-"node or multi-node check fails, this is the first place to look.  The logs "
-"found here are helpful when the templates render correctly, but the services "
-"are not functioning correctly, whether due to service configuration issues "
-"or issues with the pods themselves."
-msgstr ""
-"K8s 디렉터리는 Kubernetes 오즈젝트에 대한 로그와 출력물이 저장됩니다. 여기에"
-"는 pods, nodes, secrets, services, namespaces, configmaps, deployments, "
-"daemonsets, statefulsets 들이 포함됩니다. 실행 중인 모든 자원의 상태를 확인"
-"할 수 있는 설명들이 여기에 있으며, 이 정보는 검사 중 발생하는 문제를 디버깅할"
-"때 유용합니다. 단일 노드 또는 다중 노드 검사가 실패했을 때, 여기를 가장 먼저 "
-"확인합니다. 이곳에 있는 로그는 템플릿으로 올바르게 렌더링되지만 서비스 구성 "
-"문제나 pods 자체 관련된 문제로 인해 제대로 작동하지 않을때 유용합니다."
-
-msgid ""
-"The dry-runs directory contains the rendered output of Helm dry-run installs "
-"on each of the OpenStack service charts.  This gives visibility into the "
-"manifests created by the templates with the supplied values.  When the dry-"
-"run gate fails, the reason should be apparent in the dry-runs output.  The "
-"logs found here are helpful in identifying issues resulting from using helm-"
-"toolkit functions incorrectly or other rendering issues with gotpl."
-msgstr ""
-"dry-runs 디렉터리는 각 OpenStack 서비스 차트의 Helm 모의 설치들에서 만들어진 "
-"출력을 포함하고 있습니다. 이렇게하면 제공된 값으로 템플릿들이 만든 매니페스트"
-"를 볼 수 있습니다. 모의 게이트가 실패하면, 모의 출력에서 그 이유가 분명해야 "
-"합니다. 이곳에서 발견할 수 있는 로그는 helm-toolkit 기능들의 오용이나 gotpl"
-"로 만들어진 다른 문제들의 결과에 따른 문제들을 확인하는데 도움이 됩니다."
-
-msgid ""
-"The goal of OpenStack-Helm is to provide a collection of Helm charts that "
-"simply, resiliently, and flexibly deploy OpenStack and related services on "
-"Kubernetes."
-msgstr ""
-"OpenStack-Helm 목표는 Kubernetes 위에 OpenStack 및 관련 서비스들을 단순하고, "
-"탄력적이며, 유연하게 배포하는 Helm 차트에 대한 집합을 제공하는 데 있습니다."
-
-msgid ""
-"The nodes directory contains information about the node the gate tests are "
-"running on in openstack-infra.  This includes: the network interfaces, the "
-"contents of iptables, the host's resolv.conf, and the kernel IP routing "
-"table. These logs can be helpful when trying to identify issues with host "
-"networking or other issues at the node level."
-msgstr ""
-"노드의 디렉터리는 해당 노드에 대한 정보를 포함합니다. 게이트 테스트는 "
-"openstack-infra 내에서 동작합니다. 이것은 포함합니다: 네트워크 인터페이스, "
-"iptables 내용, 호스트의 resolv.conf, 그리고 커널 IP 라우팅 테이블. 이 로그들"
-"은 노드 레벨에서 호스트 네트워킹이나 다른 문제들을 확인하고자 할 때 도움이 됩"
-"니다."
-
-msgid ""
-"This project is under active development. We encourage anyone interested in "
-"OpenStack-Helm to review our `Installation <https://docs.openstack.org/"
-"openstack-helm/latest/install/index.html>`_ documentation. Feel free to ask "
-"questions or check out our current `Storyboard backlog <https://storyboard."
-"openstack.org/#!/project_group/64>`_."
-msgstr ""
-"이 프로젝트는 적극적으로 개발 중인 상태입니다. OpenStack-Helm에 대해 관심있"
-"는 분들은 `Installation <https://docs.openstack.org/openstack-helm/latest/"
-"install/index.html>`_ 문서를 살펴 보십시오. 자유롭게 질문하거나 현재 "
-"`Storyboard 백로그 <https://storyboard.openstack.org/#!/project_group/64>`_ "
-"를 살펴봅니다."
-
-msgid "This results in the gate running the following:"
-msgstr "게이트 실행 결과는 다음과 같습니다."
-
-msgid ""
-"To evaluate a multinode installation, follow the `Bare Metal <https://docs."
-"openstack.org/openstack-helm/latest/install/multinode.html>`_ install guide."
-msgstr ""
-"멀티노드 설치를 평가해 보려면 `Bare Metal <https://docs.openstack.org/"
-"openstack-helm/latest/install/multinode.html>`_ 설치 가이드를 따릅니다."
-
-msgid ""
-"To facilitate ease of testing and debugging, information regarding gates and "
-"their functionality can be found here."
-msgstr ""
-"테스팅 및 디버깅을 보다 쉽게 해 주는, 게이트 및 해당 기능에 대한 정보를 여기"
-"에서 찾을 수 있습니다."
-
-msgid ""
-"To provide meaningful output from the gates, all information pertaining to "
-"the components of the cluster and workflow are output to the logs directory "
-"inside each gate.  The contents of the log directory are as follows:"
-msgstr ""
-"게이트로부터 의미 있는 출력을 제공하기 위해서는, 클러스터와 워크 플로우의 구"
-"성요소와 관련된 모든 정보가 각 게이트 내부의 logs 디렉터리에 출력됩니다. 로"
-"그 디렉터리의 내용들은 다음과 같습니다:"
-
-msgid ""
-"To provide reusable components for gate functionality, functions have been "
-"provided in the gates/funcs directory. These functions include:"
-msgstr ""
-"게이트의 기능을 위한 재사용 가능한 구성요소들을 제공하기 위해, gates/funcs 디"
-"렉터리 내에 기능들을 제공합니다. 이 기능들은 포함합니다:"
-
-msgid "Welcome to OpenStack-Helm's documentation!"
-msgstr "OpenStack-Helm의 문서에 오신 것을 환영합니다!"
diff --git a/doc/source/locale/ru/LC_MESSAGES/doc-troubleshooting.po b/doc/source/locale/ru/LC_MESSAGES/doc-troubleshooting.po
deleted file mode 100644
index 7e33f2accb..0000000000
--- a/doc/source/locale/ru/LC_MESSAGES/doc-troubleshooting.po
+++ /dev/null
@@ -1,204 +0,0 @@
-# Roman Gorshunov <roman.gorshunov@att.com>, 2020. #zanata
-msgid ""
-msgstr ""
-"Project-Id-Version: openstack-helm 0.1.1.dev3462\n"
-"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2021-06-22 20:22+0000\n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-"PO-Revision-Date: 2020-03-06 04:06+0000\n"
-"Last-Translator: Roman Gorshunov <roman.gorshunov@att.com>\n"
-"Language-Team: Russian\n"
-"Language: ru\n"
-"X-Generator: Zanata 4.3.3\n"
-"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
-"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2)\n"
-
-msgid "Backing up a PVC"
-msgstr "Резервное копирование PVC"
-
-msgid ""
-"Backing up a PVC stored in Ceph, is fairly straigthforward, in this example "
-"we use the PVC ``mysql-data-mariadb-server-0`` as an example, but this will "
-"also apply to any other services using PVCs eg. RabbitMQ, Postgres."
-msgstr ""
-"Резервное копирование PVC, хранящегося в Ceph, достаточно просто. Ниже для "
-"примера приведён PVC ``mysql-data-mariadb-server-0``, но та же процедура "
-"подходит и для любых других сервисов, использующих PVC, таких как RabbitMQ "
-"или Postgres."
-
-msgid ""
-"Before proceeding, it is important to ensure that you have deployed a client "
-"key in the namespace you wish to fulfill ``PersistentVolumeClaims``. To "
-"verify that your deployment namespace has a client key:"
-msgstr ""
-"Перед тем, как продолжить далее, важно убедиться, что вы установили "
-"клиентский ключ в том пространстве имён, в котором вы собираетесь заполнять "
-"``PersistentVolumeClaims``. Выполните нижеприведённую команду для проверки "
-"того, что в этом пространстве имён есть клиеннтский ключ:"
-
-msgid "Bugs and Feature requests"
-msgstr "Сообщения об ошибках и запросы нового функционала"
-
-msgid "Ceph"
-msgstr "Ceph"
-
-msgid "Ceph Deployment Status"
-msgstr "Статус развёртывания Ceph"
-
-msgid "Ceph Validating PVC Operation"
-msgstr "Проверка работы PVC Ceph"
-
-msgid "Ceph Validating StorageClass"
-msgstr "Проверка StorageClass'а Ceph"
-
-msgid "Channels"
-msgstr "Чаты"
-
-msgid "Database Deployments"
-msgstr "Развёртывание баз данных"
-
-msgid ""
-"First, we want to validate that Ceph is working correctly. This can be done "
-"with the following Ceph command:"
-msgstr ""
-"В начале давайте проверим, что Ceph работоспособен. Это можно сделать с "
-"помощью следующей команды Ceph:"
-
-msgid "Galera Cluster"
-msgstr "Кластер Galera"
-
-msgid "Getting help"
-msgstr "Помощь"
-
-msgid "Installation"
-msgstr "Установка и развёртывание"
-
-msgid "Join us on `Slack <http://slack.k8s.io/>`_ - #openstack-helm"
-msgstr ""
-"Присоединяйтесь к нам в `Slack <http://slack.k8s.io/>`_ - #openstack-helm"
-
-msgid ""
-"Next we can look at the storage class, to make sure that it was created "
-"correctly:"
-msgstr ""
-"Далее мы можем посмотреть на класс хранилища, чтобы убедиться, что он создан "
-"корректно:"
-
-msgid ""
-"Note: This step is not relevant for PVCs within the same namespace Ceph was "
-"deployed."
-msgstr ""
-"Важно: Этот шаг не имеет отношения к PVC в тех же пространствах имён, в "
-"которых развёрнут Ceph."
-
-msgid "Once this has been done the workload can be restarted."
-msgstr "После вполнения процедуры рабочая нагрузка может быть перезапущена."
-
-msgid "PVC Preliminary Validation"
-msgstr "Предварительная проверка PVC"
-
-msgid "Persistent Storage"
-msgstr "Постоянное хранилище"
-
-msgid ""
-"Restoring is just as straightforward. Once the workload consuming the device "
-"has been stopped, and the raw RBD device removed the following will import "
-"the back up and create a device:"
-msgstr ""
-"Восстановление - так же достаточно простая процедура. Как только рабочая "
-"нагрузка использующая устройство остановлена, и отключено устройство с "
-"сырыми данными RBD, нижеприведённая процедура импортирует резерную копию и "
-"создаст устройство."
-
-msgid ""
-"Sometimes things go wrong. These guides will help you solve many common "
-"issues with the following:"
-msgstr ""
-"Иногда что-то идёт не так. Эти руководства помогут вам разрешить многие из "
-"типичных проблем:"
-
-msgid ""
-"The parameters are what we're looking for here. If we see parameters passed "
-"to the StorageClass correctly, we will see the ``ceph-mon.ceph.svc.cluster."
-"local:6789`` hostname/port, things like ``userid``, and appropriate secrets "
-"used for volume claims."
-msgstr ""
-"Здесь мы должны обратить внимание на параметры. Если они корректно преданы "
-"StorageClass'у, то мы увидим имя хоста/порт как ``ceph-mon.ceph.svc.cluster."
-"local:6789``, а так же ``userid``, и соответствующие секреты, использующиеся "
-"для запроса томов хранилищ."
-
-msgid ""
-"This guide is to help users debug any general storage issues when deploying "
-"Charts in this repository."
-msgstr ""
-"Это руководство предназначается для помощи пользователям в поиске и "
-"исправлении типичных ошибок в подсистеме хранения данных при развёртывании "
-"Chart'ов этого репозитория."
-
-msgid ""
-"This guide is to help users debug any general storage issues when deploying "
-"charts in this repository."
-msgstr ""
-"Это руководство предназначается для помощи пользователям в поиске и "
-"исправлении типичных ошибок в подсистеме хранения данных при развёртывании "
-"Chart'ов этого репозитория."
-
-msgid ""
-"To deploy the HWE kernel, prior to deploying Kubernetes and OpenStack-Helm "
-"the following commands should be run on each node:"
-msgstr ""
-"Для развёртывания HWE ядра перед установкой Kubernetes и OpenStack-Helm, "
-"команды, приведённые ниже, должны быть выполнены на каждом узле:"
-
-msgid ""
-"To make use of CephFS in Ubuntu the HWE Kernel is required, until the issue "
-"described `here <https://github.com/kubernetes-incubator/external-storage/"
-"issues/345>`_ is fixed."
-msgstr ""
-"До исправления проблемы, описанной `здесь <https://github.com/kubernetes-"
-"incubator/external-storage/issues/345>`_, для использования CephFS в Ubuntu "
-"требуется использовать HWE ядро."
-
-msgid "To test MariaDB, do the following:"
-msgstr "Выполните эти команды для тестирования MariaDB:"
-
-msgid ""
-"To validate persistent volume claim (PVC) creation, we've placed a test "
-"manifest `here <https://raw.githubusercontent.com/openstack/openstack-helm/"
-"master/tests/pvc-test.yaml>`_. Deploy this manifest and verify the job "
-"completes successfully."
-msgstr ""
-"Для проверки создания требования постоянного хранилища (PVC) мы "
-"`опубликовали <https://raw.githubusercontent.com/openstack/openstack-helm/"
-"master/tests/pvc-test.yaml>`_ тестовый манифест. Разверните его, и "
-"убедитесь, что задание успешно завершается."
-
-msgid "Troubleshooting"
-msgstr "Поиск и устранение неполадок"
-
-msgid "Ubuntu HWE Kernel"
-msgstr "HWE ядро Ubuntu"
-
-msgid ""
-"Use one of your Ceph Monitors to check the status of the cluster. A couple "
-"of things to note above; our health is `HEALTH\\_OK`, we have 3 mons, we've "
-"established a quorum, and we can see that all of our OSDs are up and in the "
-"OSD map."
-msgstr ""
-"Для проверки статуса кластера, воспользуйтесь одним из мониторов Ceph. "
-"Некоторые замечания: статус здоровья - `HEALTH\\_OK`, у нас 3 монитора, "
-"установлен кворум, а так же мы можем видеть, что все наши OSD работоспособны "
-"и присутствуют в карте OSD."
-
-msgid ""
-"Without this, your RBD-backed PVCs will never reach the ``Bound`` state.  "
-"For more information, see how to `activate namespace for ceph <../install/"
-"multinode.html#activating-control-plane-namespace-for-ceph>`_."
-msgstr ""
-"Без этого ваш PVC с RBD бэкэндом никогда не достигнет состояния ``Bound`` "
-"(Подключен). За более подробной информацией обратитесь к разделу `активация "
-"пространства имён Ceph <../install/multinode.html#activating-control-plane-"
-"namespace-for-ceph>`_."
diff --git a/tox.ini b/tox.ini
index 78e34f50e7..d1f0373649 100644
--- a/tox.ini
+++ b/tox.ini
@@ -19,7 +19,7 @@ deps =
   -r{toxinidir}/doc/requirements.txt
 commands =
   rm -rf doc/build
-  docstheme-build-translated.sh
+  sphinx-build -W --keep-going -b html -j auto doc/source doc/build/html
 allowlist_externals =
   rm