Imported Translations from Zanata

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

Change-Id: Ia187ceea37f815a16048a1565d4d4cdb317c755e
This commit is contained in:
OpenStack Proposal Bot 2019-07-25 08:52:32 +00:00
parent 2c166a726c
commit c5f7192b34
3 changed files with 185 additions and 101 deletions

View File

@ -4,7 +4,7 @@ msgid ""
msgstr ""
"Project-Id-Version: openstack-helm\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-05-27 21:13+0000\n"
"POT-Creation-Date: 2019-07-24 22:37+0000\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
@ -87,16 +87,6 @@ msgstr ""
"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 the configmap for each:"
msgstr ""
"Beachten Sie auch, dass andere nicht überschriebene Werte von Hosts und "
"Labels mit Überschreibungen geerbt werden. Im Folgenden sehen Sie eine Reihe "
"von Beispiel-Hosts und die Werte, die in die Konfigurationsdatei für jede "
"eingegeben wurden:"
msgid ""
"An illustrative example of an ``images:`` section taken from the heat chart:"
msgstr ""
@ -410,9 +400,6 @@ msgstr ""
"Der Neutron-Server-Dienst wird auf Knoten mit der Markierung ``openstack-"
"control-plane = enabled`` geplant."
msgid "Node and label specific configurations"
msgstr "Knoten- und labelspezifische Konfigurationen"
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 "
@ -702,17 +689,6 @@ msgstr ""
"erstellen kann, und Kibana integriert sich standardmäßig gut in "
"Elasticsearch."
msgid ""
"There are situations where we need to define configuration differently for "
"different nodes in the environment. For example, we may require that some "
"nodes have a different vcpu_pin_set or other hardware specific deltas in "
"nova.conf."
msgstr ""
"Es gibt Situationen, in denen wir die Konfiguration für verschiedene Knoten "
"in der Umgebung unterschiedlich definieren müssen. Zum Beispiel können wir "
"verlangen, dass einige Knoten ein anderes vcpu_pin_set oder andere "
"hardwarespezifische Deltas in nova.conf haben."
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`):"
@ -790,12 +766,6 @@ msgstr ""
"Um mehrere Netzwerk-Plugins innerhalb von OpenStack-Helm konfigurieren zu "
"können, wurde eine neue Konfigurationsoption hinzugefügt:"
msgid ""
"To do this, we can specify overrides in the values fed to the chart. Ex:"
msgstr ""
"Um dies zu tun, können wir Überschreibungen in den Werten angeben, die dem "
"Chart zugeführt werden. Ex:"
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 "

View File

@ -4,11 +4,11 @@ msgid ""
msgstr ""
"Project-Id-Version: openstack-helm\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-05-27 21:13+0000\n"
"POT-Creation-Date: 2019-07-24 22:37+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:04+0000\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"
@ -64,6 +64,18 @@ msgstr ""
"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:"
@ -89,11 +101,11 @@ msgstr ""
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 the configmap for each:"
"fed into each:"
msgstr ""
"Juga perhatikan bahwa nilai non-override lainnya diwarisi oleh host dan "
"label dengan override. Berikut ini menunjukkan satu set contoh hosts dan "
"nilai yang dimasukkan ke dalam configmap untuk masing-masing:"
"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:"
@ -132,25 +144,26 @@ msgstr ""
"dengan image yang diperbarui untuk membawa skema inline dengan rilis Newton."
msgid ""
"As an example, this line uses the ``endpoint_type_lookup_addr`` 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 ``endpoint_type_lookup_addr`` 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):"
"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 ``endpoint_type_lookup_addr`` "
"dalam chart ``helm-toolkit`` (karena digunakan oleh semua chart). Perhatikan "
"bahwa ada konvention kedua di sini. Semua makro ``{{ define }}`` dalam chart "
"harus diperbaiki dengan chart yang mendefinisikannya. Ini memungkinkan "
"pengembang untuk dengan mudah mengidentifikasi sumber makro Helm dan juga "
"menghindari tabrakan namespace. Pada contoh di atas, makro "
"``endpoint_type_lookup_addr`` 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):"
"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 "
@ -166,6 +179,9 @@ msgstr ""
"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 "
@ -209,6 +225,11 @@ msgstr ""
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):"
@ -258,6 +279,9 @@ msgstr ""
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 "
@ -286,6 +310,20 @@ msgstr ""
"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:"
@ -305,6 +343,15 @@ msgstr ""
"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."
@ -322,9 +369,19 @@ 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."
@ -358,6 +415,23 @@ msgstr ""
"`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."
@ -434,8 +508,8 @@ msgstr ""
"Layanan Neutron-server dijadwalkan pada node dengan label `openstack-control-"
"plane=enabled`."
msgid "Node and label specific configurations"
msgstr "Node dan label konfigurasi tertentu"
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 ""
@ -466,6 +540,18 @@ msgstr ""
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"
@ -556,6 +642,13 @@ msgstr ""
"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."
@ -626,6 +719,22 @@ msgstr ""
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 "
@ -635,6 +744,12 @@ msgstr ""
"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:"
@ -652,6 +767,20 @@ msgstr ""
"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 "
@ -727,17 +856,6 @@ msgstr ""
"dasbor yang dapat membuat tampilan khusus pada acara yang dicatat, dan "
"Kibana terintegrasi dengan baik dengan Elasticsearch secara default."
msgid ""
"There are situations where we need to define configuration differently for "
"different nodes in the environment. For example, we may require that some "
"nodes have a different vcpu_pin_set or other hardware specific deltas in "
"nova.conf."
msgstr ""
"Ada situasi di mana kita perlu mendefinisikan konfigurasi secara berbeda "
"untuk berbagai node di lingkungan. Sebagai contoh, kami mungkin mengharuskan "
"beberapa node memiliki vcpu_pin_set yang berbeda atau delta spesifik "
"perangkat keras lainnya di nova.conf."
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`):"
@ -827,6 +945,25 @@ 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:"
@ -834,12 +971,6 @@ msgstr ""
"Untuk dapat mengkonfigurasi beberapa plugin jaringan di dalam OpenStack-"
"Helm, opsi konfigurasi baru ditambahkan:"
msgid ""
"To do this, we can specify overrides in the values fed to the chart. Ex:"
msgstr ""
"Untuk melakukan ini, kita dapat spesifik menimpa nilai yang diumpankan ke "
"chart. Ex:"
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 "
@ -899,6 +1030,15 @@ msgstr ""
"Setiap kali kita mengubah agen L2, itu harus tercermin dalam `nova/values."
"yaml` dalam resolusi ketergantungan untuk 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 ""
"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``:"

View File

@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: openstack-helm\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-05-27 21:13+0000\n"
"POT-Creation-Date: 2019-07-24 22:37+0000\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
@ -82,15 +82,6 @@ msgstr ""
"blob/412c49b3930ce8aecb0a07aec50a9607058e5bc7/setup.cfg#L69>`_에서 클래스 매"
"핑에 대한 endpoints를 볼 수 있습니다."
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 the configmap for each:"
msgstr ""
"또한 다른 오버라이드되지 않은 값들은 오버라이드된 호스트와 라벨에 의해 상속됨"
"을 참고하십시오. 다음은 호스트 예시 세트와 각 configmap 에 입력된 값들을 보여"
"줍니다:"
msgid ""
"An illustrative example of an ``images:`` section taken from the heat chart:"
msgstr "heat 차트에서 가져온 ``images:`` 섹션의 실제 사례:"
@ -389,9 +380,6 @@ msgstr ""
"Neutron-server 서비스는 `openstack-control-plane=enabled` 라벨로 노드에 스케"
"줄됩니다."
msgid "Node and label specific configurations"
msgstr "노드와 라벨 특정 구성"
msgid "Note that only one set of overrides is applied per node, such that:"
msgstr ""
"노드마다 다음과 같이 단 하나의 오버라이드 세트만 적용되는 점을 참고하십시오:"
@ -653,16 +641,6 @@ msgstr ""
"다. Kibana는 기록된 이벤트에 대한 사용자 정의 뷰를 만들 수 있는 대시보드를 제"
"공하며 Kibana는 기본적으로 Elasticsearch와 잘 통합됩니다."
msgid ""
"There are situations where we need to define configuration differently for "
"different nodes in the environment. For example, we may require that some "
"nodes have a different vcpu_pin_set or other hardware specific deltas in "
"nova.conf."
msgstr ""
"환경의 각각의 노드들에 대해 구성을 다르게 정의해야 하는 상황이 있습니다. 예"
"를 들어, 어떤 노드가 nova.conf 에서 다른 vcpu_pi_set 또는 다른 하드웨어 특정 "
"delta를 갖도록 요구할 수 있습니다."
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`):"
@ -735,10 +713,6 @@ msgstr ""
"OpenStack-Helm 내 다중 네트워킹 플러그인을 구성하는 것을 가능하게 하기 위해"
"서, 새로운 구성 옵션이 추가되었습니다:"
msgid ""
"To do this, we can specify overrides in the values fed to the chart. Ex:"
msgstr "이를 위해, 차트에 입력된 값의 오버라이드를 명시할 수 있습니다. 예시:"
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 "