openstack-helm/doc/source/locale/id/LC_MESSAGES/doc-devref.po

# suhartono <cloudsuhartono@gmail.com>, 2018. #zanata
# suhartono <cloudsuhartono@gmail.com>, 2019. #zanata
msgid ""
msgstr ""
"Project-Id-Version: openstack-helm\n"
"Report-Msgid-Bugs-To: \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-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 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. OpenStack-Helm developers will continue to work with "
"the Helm community or develop charts that will support job removal prior to "
"an upgrade, which will recreate services with updated images. An example of "
"where this behavior would be desirable is when an updated db\\_sync image "
"has updated to point from a Mitaka image to a Newton image. 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 ""
"Saat Helm berdiri hari ini, ada beberapa masalah ketika Anda memperbarui "
"image dalam chart yang mungkin telah digunakan oleh pekerjaan yang sudah "
"berjalan hingga selesai atau masih dalam penerbangan (in flight). Pengembang "
"OpenStack-Helm akan terus bekerja dengan komunitas Helm atau mengembangkan "
"chart yang akan mendukung penghapusan pekerjaan sebelum peningkatan, yang "
"akan menciptakan layanan dengan image yang diperbarui. Contoh di mana "
"perilaku ini akan diinginkan adalah ketika image db\\_sync yang diperbarui "
"telah diperbarui untuk menunjuk dari image Mitaka ke citra Newton. Dalam hal "
"ini, operator kemungkinan akan menginginkan pekerjaan db\\_sync, yang sudah "
"dijalankan dan diselesaikan selama instalasi situs, untuk dijalankan kembali "
"dengan image yang diperbarui untuk membawa skema inline dengan rilis Newton."

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 ""
"Whenever we change the L2 agent, it should be reflected in `nova/values."
"yaml` in dependency resolution for nova-compute."
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``:"
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 ""
"api: This is the port to map to for the service. Some components, such as "
"glance, provide an ``api`` port and a ``registry`` port, for example."
msgstr ""
"api: Ini adalah port untuk dipetakan ke layanan. Beberapa komponen, seperti "
"glance, menyediakan port ``api`` dan port ``registry``, misalnya."

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"