Imported Translations from Zanata

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

Change-Id: If637272e1f78b54db73ec9b4bc6be06074b06191
This commit is contained in:
OpenStack Proposal Bot 2018-12-29 08:46:11 +00:00
parent c0418b0fd0
commit 5fc8e25e4a
4 changed files with 493 additions and 8 deletions

View File

@ -3,11 +3,11 @@ msgid ""
msgstr ""
"Project-Id-Version: openstack-helm\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-10-24 23:52+0000\n"
"POT-Creation-Date: 2018-12-28 18: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-09-24 03:59+0000\n"
"PO-Revision-Date: 2018-12-19 01:49+0000\n"
"Last-Translator: suhartono <cloudsuhartono@gmail.com>\n"
"Language-Team: Indonesian\n"
"Language: id\n"
@ -99,6 +99,13 @@ msgid ""
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 "
@ -158,6 +165,17 @@ msgstr ""
"code:`neutron-ovs-agent` tidak boleh digunakan ketika SDN lain digunakan "
"dalam` network.backend`."
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 "
@ -168,6 +186,19 @@ msgstr ""
"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:`network."
"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 membuat pemetaan jembatan yang didefinisikan dalam :"
"code:`network.auto_bridge_add`. Nilai ini harus sejajar :code:`conf.plugins."
"openvswitch_agent.ovs.bridge_mappings`."
msgid ""
"Configure neutron-server with SDN specific core_plugin/mechanism_drivers."
msgstr ""
@ -735,6 +766,18 @@ msgstr ""
"setidaknya 3 replika berjalan, sedangkan menggunakan ``min_available: 80%`` "
"akan memastikan bahwa 4 replika pod tersebut 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 "

View File

@ -3,11 +3,11 @@ msgid ""
msgstr ""
"Project-Id-Version: openstack-helm\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-10-24 23:52+0000\n"
"POT-Creation-Date: 2018-12-28 18: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-09-27 06:38+0000\n"
"PO-Revision-Date: 2018-12-19 01:55+0000\n"
"Last-Translator: suhartono <cloudsuhartono@gmail.com>\n"
"Language-Team: Indonesian\n"
"Language: id\n"
@ -166,9 +166,27 @@ 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 ""
"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:"
@ -470,6 +488,13 @@ msgstr ""
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 ""
"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-"
@ -577,6 +602,13 @@ msgstr ""
"variable file <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 ""
"Persiapkan sebelumnya tata letak FQDN dan DNS Anda. Ada beberapa endpoint "
"OpenStack yang ingin Anda buka untuk akses API dan Dashboard."
msgid "Proxy Configuration"
msgstr "Konfigurasi Proxy"
@ -845,6 +877,15 @@ msgid ""
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 ""
"Until the Ubuntu kernel shipped with 16.04 supports CephFS subvolume mounts "
"by default the `HWE Kernel <../troubleshooting/ubuntu-hwe-kernel.html>`__ is "
@ -888,6 +929,24 @@ 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 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 ""
"You can use any Kubernetes deployment tool to bring up a working Kubernetes "
"cluster for use with OpenStack-Helm. For production deployments, please "

View File

@ -3,20 +3,98 @@ msgid ""
msgstr ""
"Project-Id-Version: openstack-helm\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-10-24 23:52+0000\n"
"POT-Creation-Date: 2018-12-28 18: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-09-25 05:17+0000\n"
"PO-Revision-Date: 2018-12-19 02:40+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`` -> "
@ -26,6 +104,16 @@ msgstr ""
"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"
@ -45,6 +133,9 @@ 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``."
@ -55,6 +146,9 @@ msgid ""
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 "
@ -95,6 +189,19 @@ msgstr ""
"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 and shows 3 MONs available."
msgstr ""
"Seperti yang ditunjukkan di atas, status Ceph sekarang HEALTH_OK dan 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."
@ -137,12 +244,18 @@ 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."
@ -152,6 +265,25 @@ 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 "
@ -171,6 +303,11 @@ msgstr ""
"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"
@ -224,10 +361,27 @@ msgstr ""
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"
@ -273,6 +427,46 @@ msgstr ""
"``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."
@ -299,6 +493,17 @@ 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"
@ -312,6 +517,13 @@ 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)"
@ -321,6 +533,18 @@ 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"
@ -334,6 +558,10 @@ 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:"
@ -355,6 +583,10 @@ 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"
@ -368,6 +600,19 @@ 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"
@ -377,6 +622,18 @@ 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:"
@ -389,6 +646,9 @@ msgstr "Uji Lingkungan"
msgid "Test Scenario:"
msgstr "Test Scenario:"
msgid "Test Scenarios:"
msgstr "Skenario Uji:"
msgid "Testing"
msgstr "Pengujian"
@ -459,6 +719,13 @@ msgstr ""
"``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 "
@ -504,6 +771,17 @@ msgstr ""
"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."
@ -573,6 +851,13 @@ 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):"
@ -580,6 +865,19 @@ 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) "
@ -630,6 +928,51 @@ 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."

View File

@ -3,11 +3,11 @@ msgid ""
msgstr ""
"Project-Id-Version: openstack-helm\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-10-24 23:52+0000\n"
"POT-Creation-Date: 2018-12-28 18: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-09-23 12:49+0000\n"
"PO-Revision-Date: 2018-12-19 01:45+0000\n"
"Last-Translator: suhartono <cloudsuhartono@gmail.com>\n"
"Language-Team: Indonesian\n"
"Language: id\n"
@ -108,6 +108,15 @@ 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 "
@ -269,6 +278,9 @@ msgstr ""
"Permintaan tarik (pull request) yang dikirimkan melalui GitHub akan "
"diabaikan."
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."
@ -301,6 +313,27 @@ 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 "
@ -388,6 +421,13 @@ msgstr ""
msgid "Welcome to OpenStack-Helm's documentation!"
msgstr "Selamat datang di dokumentasi OpenStack-Helm!"
msgid ""
"`OpenStack-Helm git repository <https://git.openstack.org/cgit/openstack/"
"openstack-helm/>`_"
msgstr ""
"`OpenStack-Helm git repository <https://git.openstack.org/cgit/openstack/"
"openstack-helm/>`_"
msgid "https://docs.openstack.org/infra/manual/developers.html"
msgstr "https://docs.openstack.org/infra/manual/developers.html"