diff --git a/doc/source/locale/de/LC_MESSAGES/doc-install.po b/doc/source/locale/de/LC_MESSAGES/doc-install.po index 87ff23ad81..f9f3bdc1d1 100644 --- a/doc/source/locale/de/LC_MESSAGES/doc-install.po +++ b/doc/source/locale/de/LC_MESSAGES/doc-install.po @@ -2,9 +2,9 @@ # Robert Simai , 2018. #zanata msgid "" msgstr "" -"Project-Id-Version: openstack-helm 0.1.1.dev3067\n" +"Project-Id-Version: openstack-helm 0.1.1.dev3685\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2020-07-09 22:40+0000\n" +"POT-Creation-Date: 2022-04-06 21:47+0000\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" @@ -143,13 +143,6 @@ msgstr "" "diese CIDRs nicht auf dem Entwicklungsknoten verwendet werden, bevor Sie " "fortfahren, oder passen Sie sie wie erforderlich an." -msgid "" -"Cinder deployment is not tested in the OSH development environment community " -"gates" -msgstr "" -"Die Cinder-Bereitstellung wird nicht in den Community-Gates der OSH-" -"Entwicklungsumgebung getestet" - msgid "Cleaning the Deployment" msgstr "Reinigung der Bereitstellung" @@ -348,13 +341,6 @@ msgstr "Erhalten Sie den ``Helm Status`` Ihres Charts." msgid "Helm Chart Installation" msgstr "Helm Chart Installation" -msgid "" -"Horizon deployment is not tested in the OSH development environment " -"community gates" -msgstr "" -"Die Horizon-Bereitstellung wird nicht in den Community-Gates der OSH-" -"Entwicklungsumgebung getestet" - msgid "Host Configuration" msgstr "Hostkonfiguration" @@ -748,18 +734,6 @@ msgstr "" "wird. Es wird empfohlen, den Host vorher neu zu starten, um einen Reststatus " "sicherzustellen, z.B. Netzwerkschnittstellen werden entfernt." -msgid "" -"This command will deploy a single node KubeADM administered cluster. This " -"will use the parameters in ``${OSH_INFRA_PATH}/playbooks/vars.yaml`` to " -"control the deployment, which can be over-ridden by adding entries to ``" -"${OSH_INFRA_PATH}/tools/gate/devel/local-vars.yaml``." -msgstr "" -"Mit diesem Befehl wird ein KubeADM-Cluster mit einem einzigen Knoten " -"bereitgestellt. Dies verwendet die Parameter in ``${OSH_INFRA_PATH}/" -"playbooks/vars.yaml``, um die Bereitstellung zu steuern, die durch " -"Hinzufügen von Einträgen zu ``${OSH_INFRA_PATH}/tools/gate/devel/local-vars." -"yaml``." - msgid "" "This guide assumes that users wishing to deploy behind a proxy have already " "defined the conventional proxy environment variables ``http_proxy``, " diff --git a/doc/source/locale/en_GB/LC_MESSAGES/doc-install.po b/doc/source/locale/en_GB/LC_MESSAGES/doc-install.po index 4becd60769..4204ae7196 100644 --- a/doc/source/locale/en_GB/LC_MESSAGES/doc-install.po +++ b/doc/source/locale/en_GB/LC_MESSAGES/doc-install.po @@ -3,9 +3,9 @@ # Andi Chandler , 2021. #zanata msgid "" msgstr "" -"Project-Id-Version: openstack-helm 0.1.1.dev3505\n" +"Project-Id-Version: openstack-helm 0.1.1.dev3685\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2021-08-31 21:22+0000\n" +"POT-Creation-Date: 2022-04-06 21:47+0000\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" @@ -299,13 +299,6 @@ msgstr "" "nameserver entries can be changed by updating the " "``external_dns_nameservers`` entry in this file:" -msgid "" -"Cinder deployment is not tested in the OSH development environment community " -"gates" -msgstr "" -"Cinder deployment is not tested in the OSH development environment community " -"gates" - msgid "Cleaning the Deployment" msgstr "Cleaning the Deployment" @@ -610,13 +603,6 @@ msgstr "Get the ``helm status`` of your chart." msgid "Helm Chart Installation" msgstr "Helm Chart Installation" -msgid "" -"Horizon deployment is not tested in the OSH development environment " -"community gates" -msgstr "" -"Horizon deployment is not tested in the OSH development environment " -"community gates" - msgid "Host Configuration" msgstr "Host Configuration" @@ -1315,17 +1301,6 @@ msgstr "" msgid "These values can be retrieved by running:" msgstr "These values can be retrieved by running:" -msgid "" -"This command will deploy a single node KubeADM administered cluster. This " -"will use the parameters in ``${OSH_INFRA_PATH}/playbooks/vars.yaml`` to " -"control the deployment, which can be over-ridden by adding entries to ``" -"${OSH_INFRA_PATH}/tools/gate/devel/local-vars.yaml``." -msgstr "" -"This command will deploy a single node KubeADM administered cluster. This " -"will use the parameters in ``${OSH_INFRA_PATH}/playbooks/vars.yaml`` to " -"control the deployment, which can be over-ridden by adding entries to ``" -"${OSH_INFRA_PATH}/tools/gate/devel/local-vars.yaml``." - msgid "" "This guide assumes that users wishing to deploy behind a proxy have already " "defined the conventional proxy environment variables ``http_proxy``, " diff --git a/doc/source/locale/id/LC_MESSAGES/doc-contributor.po b/doc/source/locale/id/LC_MESSAGES/doc-contributor.po new file mode 100644 index 0000000000..ecb4a8e3b3 --- /dev/null +++ b/doc/source/locale/id/LC_MESSAGES/doc-contributor.po @@ -0,0 +1,158 @@ +# suhartono , 2020. #zanata +msgid "" +msgstr "" +"Project-Id-Version: openstack-helm 0.1.1.dev3685\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2022-04-06 21:47+0000\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"PO-Revision-Date: 2020-05-09 05:05+0000\n" +"Last-Translator: suhartono \n" +"Language-Team: Indonesian\n" +"Language: id\n" +"X-Generator: Zanata 4.3.3\n" +"Plural-Forms: nplurals=1; plural=0\n" + +msgid "" +"Additional information could be found in `OpenDev Developer's Guide `_." +msgstr "" +"Informasi tambahan dapat ditemukan di `OpenDev Developer's Guide `_." + +msgid "" +"All common PTL duties are enumerated in the `PTL guide `_." +msgstr "" +"Semua tugas PTL umum disebutkan dalam `PTL guide `_." + +msgid "" +"Below will cover the more project specific information you need to get " +"started with OpenStack-Helm." +msgstr "" +"Di bawah ini akan mencakup informasi spesifik proyek lebih lanjut yang Anda " +"perlukan untuk memulai dengan OpenStack-Helm." + +msgid "Bugs should be filed as stories in Storyboard, not GitHub." +msgstr "Bug harus diajukan sebagai cerita di Storyboard, bukan GitHub." + +msgid "" +"Changes affecting code base often require CI tests and documentation to be " +"added in the same patch set." +msgstr "" +"Changes affecting code base often require CI tests and documentation to be " +"added in the same patch set." + +msgid "Communication" +msgstr "Komunikasi" + +msgid "Contacting the Core Team" +msgstr "Menghubungi Tim Inti (Core Team)" + +msgid "" +"For general information on contributing to OpenStack, please check out the " +"`contributor guide `_ to get " +"started. It covers all the basics that are common to all OpenStack projects: " +"the accounts you need, the basics of interacting with our Gerrit review " +"system, how we communicate as a community, etc." +msgstr "" +"Untuk informasi umum tentang kontribusi ke OpenStack, silakan periksa " +"`panduan kontributor ` _ untuk " +"memulai. Ini mencakup semua dasar-dasar yang umum untuk semua proyek " +"OpenStack: akun yang Anda butuhkan, dasar-dasar berinteraksi dengan sistem " +"ulasan Gerrit kami, cara kami berkomunikasi sebagai komunitas, dll." + +msgid "Getting Your Patch Merged" +msgstr "Mendapatkan Patch Anda Digabung (Getting Your Patch Merged)" + +msgid "" +"If issue is on one of other OpenStack-Helm components, report it to the " +"appropriate `group Storyboard`_." +msgstr "" +"Jika ada masalah pada salah satu komponen OpenStack-Helm lainnya, laporkan " +"ke `grup Storyboard`_ yang sesuai." + +msgid "" +"If you're looking for some smaller, easier work item to pick up and get " +"started on, search for the 'low-hanging-fruit' tag." +msgstr "" +"Jika Anda mencari item pekerjaan yang lebih kecil dan lebih mudah untuk " +"diambil dan memulai, cari tag 'low-hanging-fruit'." + +msgid "" +"Join us on `Slack `_ - " +"#openstack-helm" +msgstr "" +"Bergabunglah dengan kami di `Slack `_ - #openstack-helm" + +msgid "" +"Meeting Agenda Items: `Agenda `_" +msgstr "" +"Item Agenda Rapat: `Agenda `_" + +msgid "New Feature Planning" +msgstr "Perencanaan Fitur Baru" + +msgid "" +"New features are planned and implemented trough the process described in " +"`Project Specifications <../specs/index.html>`_ section of this document." +msgstr "" +"Fitur-fitur baru direncanakan dan diimplementasikan melalui proses yang " +"diuraikan dalam bagian `Project Specifications <../specs/index.html>`_ pada " +"dokumen ini." + +msgid "" +"Other OpenStack-Helm component's tasks could be found on the `group " +"Storyboard`_." +msgstr "" +"Tugas komponen OpenStack-Helm lain dapat ditemukan di `group Storyboard`_." + +msgid "Project Team Lead Duties" +msgstr "Project Team Lead Duties" + +msgid "" +"Project's Core Team could be contacted via IRC or Slack, usually during " +"weekly meetings. List of current Cores could be found on a Members tab of " +"`openstack-helm-core `_ " +"Gerrit group." +msgstr "" +"Tim Inti Proyek dapat dihubungi melalui IRC atau Slack, biasanya selama " +"pertemuan mingguan. Daftar Core saat ini dapat ditemukan di tab Anggota " +"`openstack-helm-core ` " +"_ grup Gerrit." + +msgid "Pull requests submitted through GitHub will be ignored." +msgstr "Permintaan penarikan yang diajukan melalui GitHub akan diabaikan." + +msgid "Reporting a Bug" +msgstr "Melaporkan Bug" + +msgid "So You Want to Contribute..." +msgstr "Jadi Anda Ingin Berkontribusi ..." + +msgid "Task Tracking" +msgstr "Pelacakan Tugas (Task Tracking)" + +msgid "" +"We require two Code-Review +2's from reviewers, before getting your patch " +"merged with giving Workforce +1. Trivial patches (e.g. typos) could be " +"merged with one Code-Review +2." +msgstr "" +"Kami memerlukan dua Code-Review +2 dari reviewer, sebelum patch Anda " +"digabung dengan memberikan Workforce +1. Patches sepele (mis. Kesalahan " +"ketik) dapat digabung dengan satu Code-Review +2." + +msgid "We track our tasks on our StoryBoard_." +msgstr "Kami melacak tugas Anda di StoryBoard Anda." + +msgid "" +"You found an issue and want to make sure we are aware of it? You can do so " +"on our Storyboard_." +msgstr "" +"Anda menemukan masalah dan ingin memastikan kami mengetahuinya? Anda dapat " +"melakukannya di Storyboard_ kami." diff --git a/doc/source/locale/id/LC_MESSAGES/doc-devref.po b/doc/source/locale/id/LC_MESSAGES/doc-devref.po new file mode 100644 index 0000000000..3d2daae642 --- /dev/null +++ b/doc/source/locale/id/LC_MESSAGES/doc-devref.po @@ -0,0 +1,1171 @@ +# suhartono , 2018. #zanata +# suhartono , 2019. #zanata +msgid "" +msgstr "" +"Project-Id-Version: openstack-helm 0.1.1.dev3685\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2022-04-06 21:47+0000\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"PO-Revision-Date: 2019-07-17 08:07+0000\n" +"Last-Translator: suhartono \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 `_." +msgstr "" +"Semua konfigurasi di atas adalah endpoints atau path ke kelas khusus yang " +"mengimplementasikan antarmuka. Anda dapat melihat endpoints pemetaan kelas " +"di `setup.cfg `_." + +msgid "" +"Also note that other non-overridden values are inherited by hosts and labels " +"with overrides. The following shows a set of example hosts and the values " +"fed into each:" +msgstr "" +"Perhatikan juga bahwa nilai-nilai non-override lainnya diwarisi oleh host " +"dan label dengan override. Berikut ini menunjukkan sekumpulan host contoh " +"dan nilai yang dimasukkan ke masing-masing:" + +msgid "" +"An illustrative example of an ``images:`` section taken from the heat chart:" +msgstr "" +"Contoh ilustratif dari bagian ``images:``yang diambil dari heat chart:" + +msgid "" +"Another place where the DHCP agent is dependent on L2 agent is the " +"dependency for the L2 agent daemonset:" +msgstr "" +"Tempat lain di mana agen DHCP bergantung pada agen L2 adalah ketergantungan " +"untuk daemonset agen L2:" + +msgid "" +"As an example, this line uses the ``endpoints.keystone_endpoint_uri_lookup`` " +"macro in the ``helm-toolkit`` chart (since it is used by all charts). Note " +"that there is a second convention here. All ``{{ define }}`` macros in " +"charts should be pre-fixed with the chart that is defining them. This allows " +"developers to easily identify the source of a Helm macro and also avoid " +"namespace collisions. In the example above, the macro ``endpoints." +"keystone_endpoint_uri_lookup`` is defined in the ``helm-toolkit`` chart. " +"This macro is passing three parameters (aided by the ``tuple`` method built " +"into the go/sprig templating library used by Helm):" +msgstr "" +"Sebagai contoh, baris ini menggunakan makro ``endpoints." +"keystone_endpoint_uri_lookup`` dalam bagan ``helm-toolkit`` (karena " +"digunakan oleh semua charts). Perhatikan bahwa ada konvensi kedua di sini. " +"Semua makro ``{{ define }}`` dalam charts harus diperbaiki dengan charts " +"yang mendefinisikannya. Ini memungkinkan pengembang untuk dengan mudah " +"mengidentifikasi sumber makro Helm dan juga menghindari tabrakan namespace. " +"Pada contoh di atas, makro ``endpoints.keystone_endpoint_uri_lookup`` " +"didefinisikan dalam chart ``helm-toolkit``. Makro ini melewati tiga " +"parameter (dibantu oleh metode ``tuple`` yang dibangun di perpustakaan " +"templating go/sprig yang digunakan oleh Helm):" + +msgid "" +"As part of Neutron chart, this daemonset is running Neutron OVS agent. It is " +"dependent on having :code:`openvswitch-db` and :code:`openvswitch-vswitchd` " +"deployed and ready. Since its the default choice of the networking backend, " +"all configuration is in place in `neutron/values.yaml`. :code:`neutron-ovs-" +"agent` should not be deployed when another SDN is used in `network.backend`." +msgstr "" +"Sebagai bagian dari Neutron chart, daemon ini menjalankan agen Neutron OVS. " +"Ini tergantung pada pemilikan :code:`openvswitch-db` dan :code:`openvswitch-" +"vswitchd` disebarkan dan siap. Karena ini adalah pilihan default dari " +"backend jaringan, semua konfigurasi sudah ada di `neutron/values.yaml`. :" +"code:`neutron-ovs-agent` tidak boleh digunakan ketika SDN lain digunakan " +"dalam` network.backend`." + +msgid "Assume the chart name is ``mychart``." +msgstr "Asumsikan nama chart ``mychart``." + +msgid "" +"By default, each endpoint is located in the same namespace as the current " +"service's helm chart. To connect to a service which is running in a " +"different Kubernetes namespace, a ``namespace`` can be provided for each " +"individual endpoint." +msgstr "" +"Secara default, setiap endpoint ditempatkan di namespace yang sama dengan " +"chart helm layanan (service's helm) saat ini. Untuk menyambung ke layanan " +"yang berjalan di namespace Kubernetes yang berbeda, ``namespace`` dapat " +"diberikan ke setiap endpoint individual." + +msgid "" +"Charts should not use hard coded values such as ``http://keystone-api:5000`` " +"because these are not compatible with operator overrides and do not support " +"spreading components out over various namespaces." +msgstr "" +"Charts tidak boleh menggunakan nilai berkode keras (hard coded values) " +"seperti ``http://keystone-api:5000`` karena ini tidak kompatibel dengan " +"penggantian operator dan tidak mendukung penyebaran komponen di berbagai " +"namespaces." + +msgid "" +"Configuration of OVS bridges can be done via `neutron/templates/bin/_neutron-" +"openvswitch-agent-init.sh.tpl`. The script is configuring the external " +"network bridge and sets up any bridge mappings defined in :code:`conf." +"auto_bridge_add`. These values should align with :code:`conf.plugins." +"openvswitch_agent.ovs.bridge_mappings`." +msgstr "" +"Konfigurasi jembatan OVS dapat dilakukan melalui `neutron/templates/bin/" +"_neutron-openvswitch-agent-init.sh.tpl`. Skrip mengkonfigurasi jembatan " +"jaringan eksternal dan mengatur setiap pemetaan jembatan yang didefinisikan " +"dalam :code:`conf.auto_bridge_add`. Nilai-nilai ini harus sejajar dengan " +"(align with) :code:`conf.plugins.openvswitch_agent.ovs.bridge_mappings`." + +msgid "" +"Configure neutron-server with SDN specific core_plugin/mechanism_drivers." +msgstr "" +"Konfigurasikan neutron-server dengan SDN specific core_plugin/" +"mechanism_drivers." + +msgid "Configuring network plugin" +msgstr "Mengonfigurasi plugin jaringan" + +msgid "" +"Consider the following (simplified) secret and daemonset pairing example:" +msgstr "" +"Pertimbangkan contoh pairing rahasia dan daemonset (disederhanakan) berikut:" + +msgid "Contents:" +msgstr "Contents (isi):" + +msgid "Create separate chart with new SDN deployment method." +msgstr "Buat chart terpisah dengan metode penerapan SDN baru." + +msgid "" +"Currently OpenStack-Helm supports OpenVSwitch and LinuxBridge as a network " +"virtualization engines. In order to support many possible backends (SDNs), " +"modular architecture of Neutron chart was developed. OpenStack-Helm can " +"support every SDN solution that has Neutron plugin, either core_plugin or " +"mechanism_driver." +msgstr "" +"Saat ini OpenStack-Helm mendukung OpenVSwitch dan LinuxBridge sebagai mesin " +"virtualisasi jaringan. Untuk mendukung banyak kemungkinan backend (SDNs), " +"arsitektur modular Neutron chart dikembangkan. OpenStack-Helm dapat " +"mendukung setiap solusi SDN yang memiliki plugin Neutron, baik core_plugin " +"atau mechanism_driver." + +msgid "DHCP - auto-assign IP address and DNS info" +msgstr "DHCP - auto-assign IP address dan info DNS" + +msgid "" +"DHCP agent is running dnsmasq process which is serving the IP assignment and " +"DNS info. DHCP agent is dependent on the L2 agent wiring the interface. So " +"one should be aware that when changing the L2 agent, it also needs to be " +"changed in the DHCP agent. The configuration of the DHCP agent includes " +"option `interface_driver`, which will instruct how the tap interface created " +"for serving the request should be wired." +msgstr "" +"Agen DHCP menjalankan proses dnsmasq yang melayani penugasan IP (IP " +"assignment) dan info DNS. Agen DHCP tergantung pada agen L2 yang " +"menghubungkan antar muka. Jadi orang harus menyadari bahwa ketika mengubah " +"agen L2, itu juga perlu diubah dalam agen DHCP. Konfigurasi agen DHCP " +"termasuk opsi `interface_driver`, yang akan menginstruksikan bagaimana " +"antarmuka tap yang dibuat untuk melayani permintaan harus ditransfer." + +msgid "Developer References" +msgstr "Referensi Pengembang" + +msgid "" +"EFK (Elasticsearch, Fluent-bit & Fluentd, Kibana) based Logging Mechanism" +msgstr "" +"EFK (Elasticsearch, Fluent-bit & Fluentd, Kibana) berdasarkan Logging " +"Mechanism" + +msgid "Endpoints" +msgstr "Endpoints (titik akhir)" + +msgid "Exercising node/nodelabel overrides" +msgstr "Melaksanakan penggantian node/nodelabel" + +msgid "" +"Fluent-bit, Fluentd meet OpenStack-Helm's logging requirements for " +"gathering, aggregating, and delivering of logged events. Fluent-bit runs as " +"a daemonset on each node and mounts the `/var/lib/docker/containers` " +"directory. The Docker container runtime engine directs events posted to " +"stdout and stderr to this directory on the host. Fluent-bit then forward the " +"contents of that directory to Fluentd. Fluentd runs as deployment at the " +"designated nodes and expose service for Fluent-bit to forward logs. Fluentd " +"should then apply the Logstash format to the logs. Fluentd can also write " +"kubernetes and OpenStack metadata to the logs. Fluentd will then forward the " +"results to Elasticsearch and to optionally Kafka. Elasticsearch indexes the " +"logs in a logstash-* index by default. Kafka stores the logs in a ``logs`` " +"topic by default. Any external tool can then consume the ``logs`` topic." +msgstr "" +"Fluent-bit, Fluentd memenuhi persyaratan logging OpenStack-Helm untuk " +"gathering, aggregating, dan delivering peristiwa yang tercatat. Fluent-bit " +"berjalan sebagai daemonset pada setiap node dan me-mount direktori `/var/" +"lib/docker/containers`. Engine runtime kontainer Docker mengarahkan events " +"yang diposting ke stdout dan stderr ke direktori ini pada host. Fluent-bit " +"kemudian meneruskan isi direktori itu ke Fluentd. Fluentd berfungsi sebagai " +"penyebaran (deployment) di node yang ditunjuk dan mengekspos layanan untuk " +"Fluent-bit ke forward logs. Fluentd kemudian harus menerapkan format " +"Logstash ke log. Fluentd juga dapat menulis metadata kubernetes dan " +"OpenStack ke log. Fluentd kemudian akan meneruskan hasil ke Elasticsearch " +"dan ke opsional Kafka. Elasticsearch mengindeks log dalam logstash-* index " +"secara default. Kafka menyimpan log dalam topik ``log`` secara default. " +"Setiap alat eksternal kemudian dapat mengkonsumsi topik ``log``." + +msgid "" +"For example, if you have some special conf setting that should be applied to " +"``host1.fqdn``, and another special conf setting that should be applied to " +"nodes labeled with ``someNodeLabel``, then three secret/daemonset pairs will " +"be generated and registered with kubernetes: one for ``host1.fqdn``, one for " +"``someNodeLabel``, and one for ``default``." +msgstr "" +"Sebagai contoh, jika Anda memiliki beberapa pengaturan konfigurasi khusus " +"yang harus diterapkan ke ``host1.fqdn``, dan pengaturan konfigurasi khusus " +"lain yang harus diterapkan pada node yang berlabel ``someNodeLabel``, maka " +"tiga pasangan secret/daemonset akan menjadi dihasilkan dan terdaftar dengan " +"kubernetes: satu untuk ``host1.fqdn``, satu untuk ``someNodeLabel``, dan " +"satu untuk ``default``." + +msgid "" +"For instance, in the Neutron chart ``values.yaml`` the following endpoints " +"are defined:" +msgstr "" +"Sebagai contoh, dalam Neutron chart ``values.yaml``, endpoint berikut " +"didefinisikan:" + +msgid "Host overrides supercede label overrides" +msgstr "Host mengesampingkan penggantian label supercede" + +msgid "" +"If :code:`.Values.manifests.daemonset_ovs_agent` will be set to false, " +"neutron ovs agent would not be launched. In that matter, other type of L2 or " +"L3 agent on compute node can be run." +msgstr "" +"Jika :code:`.Values.manifests.daemonset_ovs_agent` akan disetel ke false, " +"agen neutron ovs tidak akan diluncurkan. Dalam hal ini, jenis lain dari agen " +"L2 atau L3 pada node komputasi dapat dijalankan." + +msgid "" +"If a node matches more than one nodelabel, only the last matching nodelabel " +"will apply (last in terms of the order the overrides are defined in the " +"YAML)." +msgstr "" +"Jika sebuah node cocok dengan lebih dari satu nodelabel, hanya nodelabel " +"yang cocok yang akan berlaku (terakhir dalam urutan urutan yang " +"didefinisikan di dalam YAML)." + +msgid "If required, add new networking agent label type." +msgstr "Jika diperlukan, tambahkan jenis label agen jaringan baru." + +msgid "" +"If the SDN implements its own version of L3 networking, neutron-l3-agent " +"should not be started." +msgstr "" +"Jika SDN mengimplementasikan versi jaringan L3nya sendiri, neutron-l3-agent " +"tidak boleh dimulai." + +msgid "" +"If the SDN of your choice is using the ML2 core plugin, then the extra " +"options in `neutron/ml2/plugins/ml2_conf.ini` should be configured:" +msgstr "" +"Jika SDN pilihan Anda menggunakan plugin ML2 core, maka opsi tambahan di " +"`neutron/ml2/plugins/ml2_conf.ini` harus dikonfigurasi:" + +msgid "" +"If there is no matching FQDN and no matching nodelabel, then the default " +"daemonset/secret (with no overrides applied) is used." +msgstr "" +"Jika tidak ada FQDN yang cocok dan tidak ada nodelabel yang cocok, maka " +"daemonset/secret default (tanpa override diterapkan) digunakan." + +msgid "Images" +msgstr "Images" + +msgid "Implementation details of node/nodelabel overrides" +msgstr "Detail implementasi dari penggantian node/nodelabel" + +msgid "" +"In ``values.yaml`` in each chart, the same defaults are supplied in every " +"chart, which allows the operator to override at upgrade or deployment time." +msgstr "" +"Dalam ``values.yaml`` di setiap chart, default yang sama disediakan dalam " +"setiap chart, yang memungkinkan operator untuk meng-override saat upgrade " +"atau waktu deployment." + +msgid "" +"In order to add support for more SDNs, these steps need to be performed:" +msgstr "" +"Untuk menambahkan dukungan untuk lebih banyak SDN, langkah-langkah ini perlu " +"dilakukan:" + +msgid "" +"In order to meet modularity criteria of Neutron chart, section `manifests` " +"in :code:`neutron/values.yaml` contains boolean values describing which " +"Neutron's Kubernetes resources should be deployed:" +msgstr "" +"Untuk memenuhi kriteria modularitas chart Neutron, bagian `manifes` dalam :" +"code:`neutron/values.yaml` berisi nilai boolean yang menjelaskan sumber " +"Kubernetes Neutron mana yang harus digunakan:" + +msgid "" +"In order to use linuxbridge in your OpenStack-Helm deployment, you need to " +"label the compute and controller/network nodes with `linuxbridge=enabled` " +"and use this `neutron/values.yaml` override:" +msgstr "" +"Untuk menggunakan linuxbridge dalam penyebaran OpenStack-Helm Anda, Anda " +"perlu memberi label node komputasi dan controller/network dengan " +"`linuxbridge=enabled` dan menggunakan pengalih (override) `neutron/values." +"yaml` ini:" + +msgid "" +"Instead of having one daemonset with one monolithic secret, this helm-" +"toolkit feature permits a common daemonset and secret template, from which " +"daemonset and secret pairings are auto-generated. It supports establishing " +"value overrides for nodes with specific label value pairs and for targeting " +"nodes with specific hostnames and hostlabels. The overridden configuration " +"is merged with the normal config data, with the override data taking " +"precedence." +msgstr "" +"Alih-alih memiliki satu daemonset dengan satu rahasia monolitik, fitur helm-" +"toolkit ini memungkinkan daemonset dan templat rahasia umum, yang darinya " +"daemonset dan pasangan rahasia dibuat secara otomatis. Ini mendukung " +"penetapan nilai override untuk node dengan pasangan nilai label tertentu dan " +"untuk menargetkan node dengan nama host dan label host tertentu. Konfigurasi " +"yang ditimpa digabungkan dengan data konfigurasi normal, dengan penimpaan " +"data yang diutamakan." + +msgid "" +"Introducing a new SDN solution should consider how the above services are " +"provided. It maybe required to disable built-in Neutron functionality." +msgstr "" +"Memperkenalkan solusi SDN baru harus mempertimbangkan bagaimana layanan di " +"atas disediakan. Mungkin diperlukan untuk menonaktifkan fungsi Neutron " +"bawaan." + +msgid "" +"L3 agent is serving the routing capabilities for Neutron networks. It is " +"also dependent on the L2 agent wiring the tap interface for the routers." +msgstr "" +"Agen L3 melayani kemampuan routing untuk jaringan Neutron. Hal ini juga " +"tergantung pada agen L2 yang memasang antarmuka keran (tap interface) untuk " +"router." + +msgid "L3 routing - creation of routers" +msgstr "L3 routing - pembuatan router" + +msgid "Linuxbridge" +msgstr "Linuxbridge" + +msgid "" +"Linuxbridge is the second type of Neutron reference architecture L2 agent. " +"It is running on nodes labeled `linuxbridge=enabled`. As mentioned before, " +"all nodes that are requiring the L2 services need to be labeled with " +"linuxbridge. This includes both the compute and controller/network nodes. It " +"is not possible to label the same node with both openvswitch and linuxbridge " +"(or any other network virtualization technology) at the same time." +msgstr "" +"Linuxbridge adalah tipe kedua dari arsitektur referensi Neutron, agen L2. " +"Ini berjalan pada node berlabel `linuxbridge=enabled`. Seperti disebutkan " +"sebelumnya, semua node yang membutuhkan layanan L2 perlu diberi label dengan " +"linuxbridge. Ini termasuk node komputasi dan controller/network. Tidaklah " +"mungkin untuk melabeli node yang sama dengan baik openvswitch dan " +"linuxbridge (atau teknologi virtualisasi jaringan lainnya) pada saat yang " +"bersamaan." + +msgid "Logging Mechanism" +msgstr "Logging Mechanism (mekanisme logging)" + +msgid "Logging Requirements" +msgstr "Logging Requirements (persyaratan logging)" + +msgid "Metadata - Provide proxy for Nova metadata service" +msgstr "Metadata - Menyediakan proxy untuk layanan metadata Nova" + +msgid "" +"Metadata-agent is a proxy to nova-metadata service. This one provides " +"information about public IP, hostname, ssh keys, and any tenant specific " +"information. The same dependencies apply for metadata as it is for DHCP and " +"L3 agents. Other SDNs may require to force the config driver in nova, since " +"the metadata service is not exposed by it." +msgstr "" +"Metadata-agent adalah proxy untuk layanan nova-metadata. Yang satu ini " +"memberikan informasi tentang IP publik, nama host, kunci ssh, dan informasi " +"khusus penyewa apa pun. Ketergantungan yang sama berlaku untuk metadata " +"seperti halnya untuk DHCP dan agen L3. SDN lain mungkin perlu memaksa driver " +"konfigurasi di nova, karena layanan metadata tidak terkena olehnya." + +msgid "Networking" +msgstr "Networking (jaringan)" + +msgid "Neutron architecture" +msgstr "Arsitektur Neutron" + +msgid "Neutron chart includes the following services:" +msgstr "Chart Neutron mencakup layanan berikut:" + +msgid "" +"Neutron-server service is scheduled on nodes with `openstack-control-" +"plane=enabled` label." +msgstr "" +"Layanan Neutron-server dijadwalkan pada node dengan label `openstack-control-" +"plane=enabled`." + +msgid "Node and node label specific daemonset configurations" +msgstr "Node dan konfigurasi node label spesifik daemonset" + +msgid "Note that only one set of overrides is applied per node, such that:" +msgstr "" +"Perhatikan bahwa hanya satu set penggantian diterapkan per node, sehingga:" + +msgid "" +"Note that some additional values have been injected into the config file, " +"this is performed via statements in the configmap template, which also calls " +"the ``helm-toolkit.utils.to_oslo_conf`` to convert the yaml to the required " +"layout:" +msgstr "" +"Perhatikan bahwa beberapa nilai tambahan telah disuntikkan ke file " +"konfigurasi, ini dilakukan melalui pernyataan dalam template configmap, yang " +"juga memanggil ``helm-toolkit.utils.to_oslo_conf`` untuk mengonversi yaml ke " +"tata letak yang diperlukan:" + +msgid "" +"Note: Rolling update values can conflict with values defined in each " +"service's PodDisruptionBudget. See `here `_ for more " +"information." +msgstr "" +"Catatan: Nilai pembaruan bergulir dapat bertentangan dengan nilai yang " +"ditentukan dalam PodDisruptionBudget layanan masing-masing. Lihat `here " +"`_ 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_.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_.ini` di mana konfigurasi khusus untuk SDN akan " +"ditempatkan." + +msgid "" +"Script in :code:`neutron/templates/bin/_neutron-openvswitch-agent-init.sh." +"tpl` is responsible for determining the tunnel interface and its IP for " +"later usage by :code:`neutron-ovs-agent`. The IP is set in init container " +"and shared between init container and main container with :code:`neutron-ovs-" +"agent` via file :code:`/tmp/pod-shared/ml2-local-ip.ini`." +msgstr "" +"Skrip dalam :code:`neutron/templates/bin/_neutron-openvswitch-agent-init.sh." +"tpl` bertanggung jawab untuk menentukan antarmuka terowongan (tunnel " +"interface) dan IP-nya untuk digunakan nanti oleh :code:`neutron-ovs-agent`. " +"IP diatur dalam init container dan dibagi antara init container dan " +"container utama dengan :code:`neutron-ovs-agent` melalui file :code:`/tmp/" +"pod-shared/ml2-local-ip.ini`." + +msgid "" +"Some nodes may have a different vcpu_pin_set in nova.conf due to differences " +"in CPU hardware." +msgstr "" +"Beberapa node mungkin memiliki vcpu_pin_set yang berbeda di nova.conf karena " +"perbedaan dalam perangkat keras CPU." + +msgid "" +"Specify if new SDN would like to use existing services from Neutron: L3, " +"DHCP, metadata." +msgstr "" +"Tentukan apakah SDN baru ingin menggunakan layanan yang ada dari Neutron: " +"L3, DHCP, metadata." + +msgid "" +"The Neutron reference architecture provides mechanism_drivers :code:" +"`OpenVSwitch` (OVS) and :code:`linuxbridge` (LB) with ML2 :code:" +"`core_plugin` framework." +msgstr "" +"Arsitektur referensi Neutron menyediakan mechanism_drivers :code:" +"`OpenVSwitch` (OVS) dan :code:`linuxbridge` (LB) with ML2 :code:" +"`core_plugin` framework." + +msgid "" +"The OpenStack-Helm project also implements annotations across all chart " +"configmaps so that changing resources inside containers, such as " +"configuration files, triggers a Kubernetes rolling update. This means that " +"those resources can be updated without deleting and redeploying the service " +"and can be treated like any other upgrade, such as a container image change." +msgstr "" +"Proyek OpenStack-Helm juga mengimplementasikan anotasi di semua chart " +"configmaps sehingga mengubah sumber daya di dalam kontainer, seperti file " +"konfigurasi, memicu pembaruan bergulir Kubernetes. Ini berarti bahwa sumber " +"daya tersebut dapat diperbarui tanpa menghapus dan menerapkan ulang layanan " +"dan dapat diperlakukan seperti peningkatan lainnya, seperti perubahan " +"container image." + +msgid "" +"The OpenStack-Helm project assumes all upgrades will be done through Helm. " +"This includes handling several different resource types. First, changes to " +"the Helm chart templates themselves are handled. Second, all of the " +"resources layered on top of the container image, such as ``ConfigMaps`` " +"which includes both scripts and configuration files, are updated during an " +"upgrade. Finally, any image references will result in rolling updates of " +"containers, replacing them with the updating image." +msgstr "" +"Proyek OpenStack-Helm mengasumsikan semua upgrade akan dilakukan melalui " +"Helm. Ini termasuk menangani beberapa jenis sumber daya yang berbeda. " +"Pertama, perubahan pada bagan Helm templates itu sendiri ditangani. Kedua, " +"semua sumber daya yang berlapis di atas container image, seperti " +"``ConfigMaps`` yang mencakup file skrip dan konfigurasi, diperbarui selama " +"upgrade. Akhirnya, setiap referensi image akan menghasilkan pembaruan " +"bergulir kontainer, menggantikannya dengan image yang diperbarui." + +msgid "" +"The OpenStack-Helm project today uses a mix of Docker images from " +"Stackanetes and Kolla, but will likely standardize on a default set of " +"images for all charts without any reliance on image-specific utilities." +msgstr "" +"Proyek OpenStack-Helm saat ini menggunakan campuran image Docker dari " +"Stackanetes dan Kolla, tetapi kemungkinan akan distandardisasi pada " +"sekumpulan image default untuk semua chart tanpa bergantung pada image-" +"specific utilities." + +msgid "" +"The ``hash`` function defined in the ``helm-toolkit`` chart ensures that any " +"change to any file referenced by configmap-bin.yaml or configmap-etc.yaml " +"results in a new hash, which will then trigger a rolling update." +msgstr "" +"Fungsi ``hash`` yang ditentukan dalam chart ``helm-toolkit`` memastikan " +"bahwa perubahan apa pun ke file apa pun yang direferensikan oleh configmap-" +"bin.yaml atau configmap-etc.yaml menghasilkan hash baru, yang kemudian akan " +"memicu pemutaran memperbarui." + +msgid "The above configuration options are handled by `neutron/values.yaml`:" +msgstr "Opsi konfigurasi di atas ditangani oleh `neutron/values.yaml`:" + +msgid "" +"The chart will then generate one daemonset for each host and label override, " +"in addition to a default daemonset for which no overrides are applied. Each " +"daemonset generated will also exclude from its scheduling criteria all other " +"hosts and labels defined in other overrides for the same daemonset, to " +"ensure that there is no overlap of daemonsets (i.e., one and only one " +"daemonset of a given type for each node)." +msgstr "" +"Chart tersebut kemudian akan menghasilkan satu daemonset untuk setiap host " +"dan label override, selain daemonset default yang tidak menerapkan override. " +"Setiap daemonset yang dihasilkan juga akan mengecualikan dari kriteria " +"penjadwalannya semua host dan label lain yang didefinisikan dalam override " +"lainnya untuk daemonset yang sama, untuk memastikan bahwa tidak ada tumpang " +"tindih daemonset (mis., satu dan hanya satu daemonset dari jenis yang " +"diberikan untuk setiap node)." + +msgid "" +"The farther down the list the label appears, the greater precedence it has. " +"e.g., \"another-label\" overrides will apply to a node containing both " +"labels." +msgstr "" +"Semakin jauh ke bawah daftar label muncul, semakin prioritas yang lebih " +"besar itu. misalnya, penggantian \"another-label\" akan menerapkan ke nodus " +"yang berisi kedua label." + +msgid "" +"The following example demonstrates how to exercise the node/nodelabel " +"overrides:" +msgstr "" +"Contoh berikut menunjukkan bagaimana menjalankan penggantian node/nodelabel:" + +msgid "" +"The following standards are in use today, in addition to any components " +"defined by the service itself:" +msgstr "" +"Standar berikut sedang digunakan saat ini, selain komponen yang ditentukan " +"oleh layanan itu sendiri:" + +msgid "" +"The macros that help translate these into the actual URLs necessary are " +"defined in the ``helm-toolkit`` chart. For instance, the cinder chart " +"defines a ``glance_api_servers`` definition in the ``cinder.conf`` template:" +msgstr "" +"Makro yang membantu menerjemahkan ini ke URL yang sebenarnya diperlukan " +"didefinisikan dalam chart ``helm-toolkit``. Sebagai contoh, chart cinder " +"mendefinisikan definisi ``glance_api_servers`` dalam template ``cinder." +"conf``:" + +msgid "" +"The order of precedence for matches is FQDN, node label, and then default. " +"If a node matches both a FQDN and a nodelabel, then only the FQDN override " +"is applied. Pay special attention to adding FQDN overrides for nodes that " +"match a nodelabel override, as you would need to duplicate the nodelabel " +"overrides for that node in the FQDN overrides for them to still apply." +msgstr "" +"Urutan yang diutamakan untuk kecocokan adalah FQDN, label node, dan kemudian " +"default. Jika sebuah node cocok dengan FQDN dan nodelabel, maka hanya " +"override FQDN yang diterapkan. Berikan perhatian khusus untuk menambahkan " +"override FQDN untuk node yang cocok dengan override nodelabel, karena Anda " +"perlu menduplikasi override nodelabel untuk node di override FQDN agar " +"mereka tetap berlaku." + +msgid "" +"The ovs set of daemonsets are running on the node labeled " +"`openvswitch=enabled`. This includes the compute and controller/network " +"nodes. For more flexibility, OpenVSwitch as a tool was split out of Neutron " +"chart, and put in separate chart dedicated OpenVSwitch. Neutron OVS agent " +"remains in Neutron chart. Splitting out the OpenVSwitch creates " +"possibilities to use it with different SDNs, adjusting the configuration " +"accordingly." +msgstr "" +"Set ovs daemon berjalan di node berlabel `openvswitch = enabled`. Ini " +"termasuk node komputasi dan controller/network. Untuk fleksibilitas lebih, " +"OpenVSwitch sebagai alat dibagi dari chart Neutron, dan dimasukkan ke dalam " +"chart terpisah yang didedikasikan OpenVSwitch. Agen OVS Neutron tetap dalam " +"chart Neutron. Memisahkan OpenVSwitch menciptakan kemungkinan untuk " +"menggunakannya dengan SDN berbeda, menyesuaikan konfigurasi yang sesuai." + +msgid "" +"The project's core philosophy regarding images is that the toolsets required " +"to enable the OpenStack services should be applied by Kubernetes itself. " +"This requires OpenStack-Helm to develop common and simple scripts with " +"minimal dependencies that can be overlaid on any image that meets the " +"OpenStack core library requirements. The advantage of this is that the " +"project can be image agnostic, allowing operators to use Stackanetes, Kolla, " +"LOCI, or any image flavor and format they choose and they will all function " +"the same." +msgstr "" +"Filosofi inti proyek mengenai images adalah bahwa alat yang diperlukan untuk " +"mengaktifkan layanan OpenStack harus diterapkan oleh Kubernetes itu sendiri. " +"Hal ini membutuhkan OpenStack-Helm untuk mengembangkan skrip umum dan " +"sederhana dengan dependensi minimal yang dapat dihamparkan (overlaid) pada " +"images apa pun yang memenuhi persyaratan perpustakaan inti OpenStack. " +"Keuntungan dari ini adalah bahwa proyek dapat menjadi agnostik image, yang " +"memungkinkan operator untuk menggunakan Stackanetes, Kolla, LOCI, atau " +"berbagai flavor dan format image yang mereka pilih dan semuanya akan " +"berfungsi sama." + +msgid "" +"The project's goal is to provide a consistent mechanism for endpoints. " +"OpenStack is a highly interconnected application, with various components " +"requiring connectivity details to numerous services, including other " +"OpenStack components and infrastructure elements such as databases, queues, " +"and memcached infrastructure. The project's goal is to ensure that it can " +"provide a consistent mechanism for defining these \"endpoints\" across all " +"charts and provide the macros necessary to convert those definitions into " +"usable endpoints. The charts should consistently default to building " +"endpoints that assume the operator is leveraging all charts to build their " +"OpenStack cloud. Endpoints should be configurable if an operator would like " +"a chart to work with their existing infrastructure or run elements in " +"different namespaces." +msgstr "" +"Tujuan proyek adalah menyediakan mekanisme yang konsisten untuk endpoints. " +"OpenStack adalah aplikasi yang sangat saling berhubungan, dengan berbagai " +"komponen yang membutuhkan rincian konektivitas ke berbagai layanan, termasuk " +"komponen OpenStack dan elemen infrastruktur lainnya seperti database, " +"antrian (queues), dan infrastruktur memcache. Tujuan proyek adalah untuk " +"memastikan bahwa ia dapat memberikan mekanisme yang konsisten untuk " +"mendefinisikan \"endpoints\" ini di semua charts dan menyediakan makro yang " +"diperlukan untuk mengubah definisi tersebut menjadi endpoints yang dapat " +"digunakan. Charts tersebut harus secara konsisten menjadi standar untuk " +"membangun endpoints yang mengasumsikan operator memanfaatkan semua charts " +"untuk membangun cloud OpenStack mereka. Endpoints harus dapat dikonfigurasi " +"jika operator ingin bagan bekerja dengan infrastruktur yang ada atau " +"menjalankan elemen di namespaces yang berbeda." + +msgid "" +"The resulting logs can then be queried directly through Elasticsearch, or " +"they can be viewed via Kibana. Kibana offers a dashboard that can create " +"custom views on logged events, and Kibana integrates well with Elasticsearch " +"by default." +msgstr "" +"Log yang dihasilkan kemudian dapat ditanyakan secara langsung melalui " +"Elasticsearch, atau mereka dapat dilihat melalui Kibana. Kibana menawarkan " +"dasbor yang dapat membuat tampilan khusus pada acara yang dicatat, dan " +"Kibana terintegrasi dengan baik dengan Elasticsearch secara default." + +msgid "" +"There is also a need for DHCP agent to pass ovs agent config file (in :code:" +"`neutron/templates/bin/_neutron-dhcp-agent.sh.tpl`):" +msgstr "" +"Ada juga kebutuhan untuk agen DHCP untuk melewati file konfigurasi agen ovs " +"(in :code:`neutron/templates/bin/_neutron-dhcp-agent.sh.tpl`):" + +msgid "" +"These quotas are configurable by modifying the ``minAvailable`` field within " +"each PodDisruptionBudget manifest, which is conveniently mapped to a " +"templated variable inside the ``values.yaml`` file. The ``min_available`` " +"within each service's ``values.yaml`` file can be represented by either a " +"whole number, such as ``1``, or a percentage, such as ``80%``. For example, " +"when deploying 5 replicas of a pod (such as keystone-api), using " +"``min_available: 3`` would enforce policy to ensure at least 3 replicas were " +"running, whereas using ``min_available: 80%`` would ensure that 4 replicas " +"of that pod are running." +msgstr "" +"Kuota ini dapat dikonfigurasi dengan memodifikasi field ``minAvailable`` " +"dalam setiap manifes PodDisruptBudget, yang mudah dipetakan ke variabel " +"templated di dalam file ``values.yaml``. File ``min_available`` dalam setiap " +"file ``values.yaml`` masing-masing layanan dapat direpresentasikan dengan " +"seluruh angka, seperti ``1``, atau persentase, seperti ``80%``. Misalnya, " +"ketika menggunakan 5 replika pod (seperti keystone-api), menggunakan " +"``min_available: 3`` akan memberlakukan kebijakan untuk memastikan " +"setidaknya 3 replika sedang berjalan, sedangkan menggunakan ``min_available: " +"80%`` akan memastikan bahwa 4 replika pod itu sedang berjalan." + +msgid "" +"These values define all the endpoints that the Neutron chart may need in " +"order to build full URL compatible endpoints to various services. Long-term, " +"these will also include database, memcached, and rabbitmq elements in one " +"place. Essentially, all external connectivity can be defined centrally." +msgstr "" +"Nilai ini mendefinisikan semua endpoints yang mungkin diperlukan Neutron " +"chart untuk membangun endpoint kompatibel URL lengkap ke berbagai layanan. " +"Jangka panjang, ini juga akan mencakup elemen database, memcached, dan " +"rabbitmq di satu tempat. Pada dasarnya, semua konektivitas eksternal dapat " +"didefinisikan secara terpusat." + +msgid "" +"This daemonset includes the linuxbridge Neutron agent with bridge-utils and " +"ebtables utilities installed. This is all that is needed, since linuxbridge " +"uses native kernel libraries." +msgstr "" +"Daemonset ini termasuk linuxbridge Neutron agent dengan utilitas bridge-" +"utils dan ebtables yang diinstal. Ini semua yang diperlukan, karena " +"linuxbridge menggunakan pustaka kernel native." + +msgid "This is accomplished with the following annotation:" +msgstr "Ini dilakukan dengan anotasi berikut:" + +msgid "" +"This option will allow to configure the Neutron services in proper way, by " +"checking what is the actual backed set in :code:`neutron/values.yaml`." +msgstr "" +"Pilihan ini akan memungkinkan untuk mengkonfigurasi layanan Neutron dengan " +"cara yang tepat, dengan memeriksa apa yang sebenarnya didukung di set " +"dalam :code:`neutron/values.yaml`." + +msgid "" +"This requirement is OVS specific, the `ovsdb_connection` string is defined " +"in `openvswitch_agent.ini` file, specifying how DHCP agent can connect to " +"ovs. When using other SDNs, running the DHCP agent may not be required. When " +"the SDN solution is addressing the IP assignments in another way, neutron's " +"DHCP agent should be disabled." +msgstr "" +"Persyaratan ini khusus OVS, string `ovsdb_connection` didefinisikan dalam " +"file `openvswitch_agent.ini`, menentukan bagaimana agen DHCP dapat terhubung " +"ke ov. Saat menggunakan SDN lain, menjalankan agen DHCP mungkin tidak " +"diperlukan. Ketika solusi SDN menangani IP assignments dengan cara lain, " +"agen DHCP neutron harus dinonaktifkan." + +msgid "" +"This runs the OVS tool and database. OpenVSwitch chart is not Neutron " +"specific, it may be used with other technologies that are leveraging the OVS " +"technology, such as OVN or ODL." +msgstr "" +"Ini menjalankan OVS tool dan database. Chart OpenVSwitch tidak spesifik " +"Neutron, ia dapat digunakan dengan teknologi lain yang memanfaatkan " +"teknologi OVS, seperti OVN atau ODL." + +msgid "" +"This will be consumed by the templated ``configmap-etc.yaml`` manifest to " +"produce the following config file:" +msgstr "" +"Ini akan digunakan oleh manifasi ``configmap-etc.yaml`` manifes untuk " +"menghasilkan file konfigurasi berikut:" + +msgid "" +"To address this use-case, the ``helm-toolkit.utils.daemonset_overrides`` " +"template was added in helm-toolkit. This was created with the intention that " +"it should be straightforward to convert (wrap) a pre-existing daemonset with " +"the functionality to override secret parameters on a per-node or per-" +"nodelabel basis." +msgstr "" +"Untuk mengatasi kasus penggunaan ini, templat ``helm-toolkit.utils." +"daemonset_overrides`` ditambahkan dalam helm-toolkit. Ini dibuat dengan " +"tujuan untuk mengkonversi (membungkus) daemonset yang sudah ada sebelumnya " +"dengan fungsi untuk mengesampingkan parameter rahasia pada basis per-node " +"atau per-nodelabel." + +msgid "" +"To address this, we can specify overrides in the values fed to the chart. Ex:" +msgstr "" +"Untuk mengatasinya, kita bisa menentukan override dalam nilai yang " +"diumpankan ke chart. Ex:" + +msgid "" +"To be able to configure multiple networking plugins inside of OpenStack-" +"Helm, a new configuration option is added:" +msgstr "" +"Untuk dapat mengkonfigurasi beberapa plugin jaringan di dalam OpenStack-" +"Helm, opsi konfigurasi baru ditambahkan:" + +msgid "" +"To enable new SDN solution, there should be separate chart created, which " +"would handle the deployment of service, setting up the database and any " +"related networking functionality that SDN is providing." +msgstr "" +"Untuk mengaktifkan solusi SDN baru, harus ada bagan terpisah yang dibuat, " +"yang akan menangani penyebaran layanan, pengaturan database dan fungsi " +"jaringan terkait yang disediakan SDN." + +msgid "" +"To that end, all charts provide an ``images:`` section that allows operators " +"to override images. Also, all default image references should be fully " +"spelled out, even those hosted by Docker or Quay. Further, no default image " +"reference should use ``:latest`` but rather should be pinned to a specific " +"version to ensure consistent behavior for deployments over time." +msgstr "" +"Untuk itu, semua charts menyediakan bagian ``images:``yang memungkinkan " +"operator untuk mengganti image. Juga, semua referensi image default harus " +"sepenuhnya tereja (spelled out), bahkan yang dihosting oleh Docker atau " +"Quay. Lebih lanjut, tidak ada referensi image default yang harus menggunakan " +"``:latest`` tetapi sebaiknya disematkan (pinned) ke versi tertentu untuk " +"memastikan perilaku yang konsisten untuk penerapan dari waktu ke waktu." + +msgid "" +"To use other Neutron reference architecture types of SDN, these options " +"should be configured in :code:`neutron.conf`:" +msgstr "" +"Untuk menggunakan jenis arsitektur referensi Neutron lainnya dari SDN, opsi " +"ini harus dikonfigurasi :code:`neutron.conf`:" + +msgid "" +"Today, the ``images:`` section has several common conventions. Most " +"OpenStack services require a database initialization function, a database " +"synchronization function, and a series of steps for Keystone registration " +"and integration. Each component may also have a specific image that composes " +"an OpenStack service. The images may or may not differ, but regardless, " +"should all be defined in ``images``." +msgstr "" +"Hari ini, bagian ``images:`` memiliki beberapa konvensi umum. Sebagian besar " +"layanan OpenStack memerlukan fungsi inisialisasi basis data, fungsi " +"sinkronisasi basis data, dan serangkaian langkah untuk pendaftaran dan " +"integrasi Keystone. Setiap komponen juga dapat memiliki image khusus yang " +"membentuk layanan OpenStack. Images mungkin atau mungkin tidak berbeda, " +"tetapi bagaimanapun, semua harus didefinisikan dalam ``images``." + +msgid "Typical networking API request is an operation of create/update/delete:" +msgstr "" +"Permintaan API jaringan tipikal adalah operasi dari create/update/delete:" + +msgid "Upgrades and Reconfiguration" +msgstr "Upgrades dan Konfigurasi Ulang" + +msgid "" +"Your daemonset should now support node and nodelabl level overrides. (Note " +"that you will also need your chart to have helm-toolkit listed as a " +"dependency.)" +msgstr "" +"Daemonset Anda sekarang harus mendukung level node dan nodelabl. (Perhatikan " +"bahwa Anda juga akan membutuhkan bagan Anda agar helm-toolkit terdaftar " +"sebagai dependensi.)" + +msgid "" +"``host1.fqdn`` with labels ``compute-type: dpdk, sriov`` and ``another-" +"label: another-value``:" +msgstr "" +"``host1.fqdn`` dengan label ``compute-type: dpdk, sriov`` dan ``another-" +"label: another-value``:" + +msgid "" +"``host2.fqdn`` with labels ``compute-type: dpdk, sriov`` and ``another-" +"label: another-value``:" +msgstr "" +"``host2.fqdn`` dengan label ``compute-type: dpdk, sriov`` dan ``another-" +"label: another-value``:" + +msgid "" +"``host3.fqdn`` with labels ``compute-type: dpdk, sriov`` and ``another-" +"label: another-value``:" +msgstr "" +"``host3.fqdn`` dengan label ``compute-type: dpdk, sriov`` dan ``another-" +"label: another-value``:" + +msgid "``host4.fqdn`` with labels ``compute-type: dpdk, sriov``:" +msgstr "``host4.fqdn`` dengan label ``compute-type: dpdk, sriov``:" + +msgid "``host5.fqdn`` with no labels:" +msgstr "``host5.fqdn`` tanpa label:" + +msgid "" +"db\\_drop: The image that will perform database deletion operations for the " +"OpenStack service." +msgstr "" +"db\\_drop: Image yang akan melakukan operasi penghapusan basis data untuk " +"layanan OpenStack." + +msgid "" +"db\\_init: The image that will perform database creation operations for the " +"OpenStack service." +msgstr "" +"db\\_init: Image yang akan melakukan operasi pembuatan basis data untuk " +"layanan OpenStack." + +msgid "" +"db\\_sync: The image that will perform database sync (schema initialization " +"and migration) for the OpenStack service." +msgstr "" +"db\\_sync: Image yang akan melakukan sinkronisasi database (skema " +"inisialisasi dan migrasi) untuk layanan OpenStack." + +msgid "" +"dep\\_check: The image that will perform dependency checking in an init-" +"container." +msgstr "" +"dep\\_check: Image yang akan melakukan pemeriksaan dependensi dalam init-" +"container." + +msgid "" +"image: This is the OpenStack service that the endpoint is being built for. " +"This will be mapped to ``glance`` which is the image service for OpenStack." +msgstr "" +"image: Ini adalah layanan OpenStack yang endpoint sedang dibangun. Ini akan " +"dipetakan ke ``glance`` yang merupakan layanan image untuk OpenStack." + +msgid "" +"internal: This is the OpenStack endpoint type we are looking for - valid " +"values would be ``internal``, ``admin``, and ``public``" +msgstr "" +"internal: Ini adalah tipe endpoint OpenStack yang kami cari - nilai yang " +"valid adalah ``internal``, ``admin``, dan ``public``" + +msgid "" +"ks\\_endpoints: The image that will perform keystone endpoint registration " +"for the service." +msgstr "" +"ks\\_endpoints: Image yang akan melakukan pendaftaran endpoint keystone " +"untuk layanan." + +msgid "" +"ks\\_service: The image that will perform keystone service registration for " +"the service." +msgstr "" +"ks\\_service: Image yang akan melakukan pendaftaran layanan keystone untuk " +"layanan." + +msgid "" +"ks\\_user: The image that will perform keystone user creation for the " +"service." +msgstr "" +"ks\\_user: Image yang akan melakukan pembuatan pengguna keystone untuk " +"layanan ini." + +msgid "network" +msgstr "network" + +msgid "neutron-dhcp-agent" +msgstr "neutron-dhcp-agent" + +msgid "" +"neutron-dhcp-agent service is scheduled to run on nodes with the label " +"`openstack-control-plane=enabled`." +msgstr "" +"layanan neutron-dhcp-agent dijadwalkan untuk berjalan di node dengan label " +"`openstack-control-plane=enabled`." + +msgid "neutron-l3-agent" +msgstr "neutron-l3-agent" + +msgid "" +"neutron-l3-agent service is scheduled to run on nodes with the label " +"`openstack-control-plane=enabled`." +msgstr "" +"layanan neutron-l3-agent dijadwalkan untuk berjalan di node dengan label " +"`openstack-control-plane=enabled`." + +msgid "neutron-lb-agent" +msgstr "neutron-lb-agent" + +msgid "neutron-metadata-agent" +msgstr "neutron-metadata-agent" + +msgid "" +"neutron-metadata-agent service is scheduled to run on nodes with the label " +"`openstack-control-plane=enabled`." +msgstr "" +"layanan neutron-metadata-agent dijadwalkan untuk berjalan di node dengan " +"label `openstack-control-plane=enabled`." + +msgid "neutron-ovs-agent" +msgstr "neutron-ovs-agent" + +msgid "neutron-server" +msgstr "neutron-server" + +msgid "" +"neutron-server is serving the networking REST API for operator and other " +"OpenStack services usage. The internals of Neutron are highly flexible, " +"providing plugin mechanisms for all networking services exposed. The " +"consistent API is exposed to the user, but the internal implementation is up " +"to the chosen SDN." +msgstr "" +"neutron-server melayani API REST jaringan untuk operator dan penggunaan " +"layanan OpenStack lainnya. Internal Neutron sangat fleksibel, menyediakan " +"mekanisme plugin untuk semua layanan jaringan yang terbuka. API yang " +"konsisten terpapar kepada pengguna, tetapi implementasi internal terserah " +"pada SDN yang dipilih." + +msgid "openvswitch-db and openvswitch-vswitchd" +msgstr "openvswitch-db dan openvswitch-vswitchd" + +msgid "port" +msgstr "port" + +msgid "" +"pull\\_policy: The image pull policy, one of \"Always\", \"IfNotPresent\", " +"and \"Never\" which will be used by all containers in the chart." +msgstr "" +"pull\\_policy: Kebijakan pengambilan image, salah satu \"Always\", " +"\"IfNotPresent\", dan \"Never\" yang akan digunakan oleh semua kontainer " +"dalam chart." + +msgid "subnet" +msgstr "subnet" diff --git a/doc/source/locale/id/LC_MESSAGES/doc-install.po b/doc/source/locale/id/LC_MESSAGES/doc-install.po new file mode 100644 index 0000000000..69e5833126 --- /dev/null +++ b/doc/source/locale/id/LC_MESSAGES/doc-install.po @@ -0,0 +1,1659 @@ +# suhartono , 2018. #zanata +# suhartono , 2019. #zanata +# suhartono , 2020. #zanata +msgid "" +msgstr "" +"Project-Id-Version: openstack-helm 0.1.1.dev3685\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2022-04-06 21:47+0000\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"PO-Revision-Date: 2020-09-06 04:43+0000\n" +"Last-Translator: suhartono \n" +"Language-Team: Indonesian\n" +"Language: id\n" +"X-Generator: Zanata 4.3.3\n" +"Plural-Forms: nplurals=1; plural=0\n" + +msgid "**Check Chart Status**" +msgstr "**Check Chart Status**" + +msgid "" +"**First**, edit the ``values.yaml`` for Neutron, Glance, Horizon, Keystone, " +"and Nova." +msgstr "" +"**First**, edit ``values.yaml`` untuk Neutron, Glance, Horizon, Keystone, " +"dan Nova." + +msgid "**Review the Ingress configuration.**" +msgstr "**Review the Ingress configuration.**" + +msgid "" +"**Second** option would be as ``--set`` flags when calling ``helm install``" +msgstr "" +"Pilihan **Second** akan menjadi ``--set`` flags saat memanggil ``helm " +"install``" + +msgid "" +"**TaaS Agent, TaaS OVS Driver and TaaS SR-IOV Driver**: This forms the back-" +"end of TaaS which runs as a ML2 agent extension on compute nodes. It handles " +"the RPC calls made by TaaS Plugin and configures the mechanism driver, i.e. " +"OpenVSwitch or SR-IOV Nic Switch." +msgstr "" +"**TaaS Agent, TaaS OVS Driver and TaaS SR-IOV Driver**: Ini membentuk back-" +"end TaaS yang berjalan sebagai ekstensi agen ML2 pada node komputasi. Ini " +"menangani panggilan RPC yang dibuat oleh TaaS Plugin dan mengkonfigurasi " +"driver mekanisme, misal OpenVSwitch atau SR-IOV Nic Switch." + +msgid "" +"**TaaS Dashboard Plugin**: Horizon Plugin which adds GUI panels for TaaS " +"resources in the Horizon Dashboard." +msgstr "" +"**TaaS Dashboard Plugin**: Horizon Plugin yang menambahkan panel GUI untuk " +"sumber daya TaaS di Horizon Dashboard." + +msgid "" +"**TaaS Plugin**: This is the front-end of TaaS which runs on controller node " +"(Neutron server). This serves TaaS APIs and stores/retrieves TaaS " +"configuration state to/from Neutron TaaS DB." +msgstr "" +"**TaaS Plugin**: Ini adalah front-end dari TaaS yang berjalan pada node " +"pengontrol (server Neutron). Ini melayani TaaS API dan menyimpan/mengambil " +"status konfigurasi TaaS ke/dari Neutron TaaS DB." + +msgid "16GB of RAM" +msgstr "RAM 16GB" + +msgid "4 Cores" +msgstr "4 Cores" + +msgid "48GB HDD" +msgstr "48GB HDD" + +msgid "8 Cores" +msgstr "8 Cores" + +msgid "8GB of RAM" +msgstr "RAM 8GB" + +msgid "" +"A correct DPDK configuration depends heavily on the specific hardware " +"resources and its configuration. Before deploying Openvswitch with DPDK, " +"check the amount and type of available hugepages on the host OS." +msgstr "" +"Konfigurasi DPDK yang benar sangat bergantung pada sumber daya perangkat " +"keras spesifik dan konfigurasinya. Sebelum menggunakan Openvswitch dengan " +"DPDK, periksa jumlah dan jenis hugepage yang tersedia di OS host." + +msgid "Activate the OpenStack namespace to be able to use Ceph" +msgstr "Aktifkan namespace OpenStack untuk dapat menggunakan Ceph" + +msgid "Activate the openstack namespace to be able to use Ceph" +msgstr "Aktifkan namespace openstack untuk dapat menggunakan Ceph" + +msgid "" +"Add TaaS Dashboard dependency in ``requirements.txt`` file in ``openstack/" +"horizon`` repo, i.e. https://opendev.org/openstack/horizon" +msgstr "" +"Tambahkan dependensi TaaS Dashboard dalam file ``requirement.txt`` di ``repo " +"openstack/horizon``, yaitu https://opendev.org/openstack/horizon" + +msgid "" +"Add TaaS and TaaS dashboard dependencies in :code:`upper-constraints.txt` " +"file in :code:`openstack/requirements` repo, i.e. https://opendev.org/" +"openstack/requirements" +msgstr "" +"Tambahkan TaaS dan dependensi dashboard TaaS dalam file :code:`upper-" +"constraints.txt` dalam :code:`openstack/requirements` repo, i.e. https://" +"opendev.org/openstack/requirements" + +msgid "" +"Add TaaS dependency in ``requirements.txt`` file in ``openstack/neutron`` " +"repo, i.e. https://opendev.org/openstack/neutron" +msgstr "" +"Tambahkan dependensi TaaS dalam file ``requirement.txt`` di repo ``openstack/" +"neutron``, yaitu https://opendev.org/openstack/neutron " + +msgid "Add TaaS panel to Horizon Dashboard:" +msgstr "Tambahkan panel TaaS ke Horizon Dashboard:" + +msgid "" +"Add the address of the Kubernetes API, ``172.17.0.1``, and ``.svc.cluster." +"local`` to your ``no_proxy`` and ``NO_PROXY`` environment variables." +msgstr "" +"Tambahkan alamat API Kubernetes, ``172,17,0,1``, dan ``.svc.cluster.local`` " +"ke variabel lingkungan ``no_proxy`` dan ``NO_PROXY`` Anda." + +msgid "" +"Add to the Install steps these flags - also adding a shell environment " +"variable to save on repeat code." +msgstr "" +"Tambahkan ke langkah Instal flags ini - juga menambahkan variabel lingkungan " +"shell untuk menghemat kode ulang." + +msgid "Adding a DPDK port to Openvswitch fails" +msgstr "Menambahkan port DPDK ke Openvswitch gagal" + +msgid "" +"Additional configuration variables can be found `here `_. In particular, ``kubernetes_cluster_pod_subnet`` can " +"be used to override the pod subnet set up by Calico (the default container " +"SDN), if you have a preexisting network that conflicts with the default pod " +"subnet of 192.168.0.0/16." +msgstr "" +"Variabel konfigurasi tambahan dapat ditemukan `here `_. Khususnya, ``kubernetes_cluster_pod_subnet`` dapat " +"digunakan untuk mengganti subnet pod yang diatur oleh Calico (kontainer " +"default SDN), jika Anda memiliki jaringan yang sudah ada sebelumnya yang " +"bertentangan (conflict) dengan subnet pod default 192.168.0.0/16." + +msgid "" +"Additional information on Kubernetes Ceph-based integration can be found in " +"the documentation for the `CephFS `_ and `RBD `_ storage provisioners, as well as for the alternative `NFS `_ provisioner." +msgstr "" +"Additional information on Kubernetes Ceph-based integration can be found in " +"the documentation for the `CephFS `_ dan `RBD ` _ storage provisioners, serta untuk alternatif `NFS `_ " +"provisioner." + +msgid "" +"Additionally, the default configuration of the neutron chart must be adapted " +"according to the underlying hardware. The corresponding configuration " +"parameter is labeled with \"CHANGE-ME\" in the script \"values_overrides/" +"dpdk.yaml\". Specifically, the \"ovs_dpdk\" configuration section should " +"list all NICs which should be bound to DPDK with their corresponding PCI-" +"IDs. Moreover, the name of each NIC needs to be unique, e.g., dpdk0, dpdk1, " +"etc." +msgstr "" +"Selain itu, konfigurasi default grafik neutron harus disesuaikan sesuai " +"dengan perangkat keras yang mendasarinya. Parameter konfigurasi yang sesuai " +"diberi label dengan \"CHANGE-ME\" dalam skrip \"values_overrides/dpdk.yaml" +"\". Khususnya, bagian konfigurasi \"ovs_dpdk\" harus mencantumkan semua NIC " +"yang harus terikat ke DPDK dengan PCI-ID yang sesuai. Selain itu, nama " +"setiap NIC harus unik, mis., dpdk0, dpdk1, dll." + +msgid "" +"After making the configuration changes, run a ``make`` and then install as " +"you would from AIO or MultiNode instructions." +msgstr "" +"Setelah membuat perubahan konfigurasi, jalankan ``make`` dan kemudian instal " +"seperti yang Anda lakukan dari instruksi AIO atau MultiNode." + +msgid "" +"All commands below should be run as a normal user, not as root. Appropriate " +"versions of Docker, Kubernetes, and Helm will be installed by the playbooks " +"used below, so there's no need to install them ahead of time." +msgstr "" +"Semua perintah di bawah ini harus dijalankan sebagai pengguna biasa, bukan " +"sebagai root. Versi Docker, Kubernetes, dan Helm yang sesuai akan dipasang " +"oleh playbook yang digunakan di bawah ini, jadi tidak perlu menginstalnya " +"terlebih dahulu." + +msgid "" +"Alternatively, these steps can be performed by running the script directly::" +msgstr "" +"Atau, langkah-langkah ini dapat dilakukan dengan menjalankan skrip secara " +"langsung ::" + +msgid "" +"Alternatively, this step can be performed by running the script directly:" +msgstr "" +"Alternatifnya, langkah ini dapat dilakukan dengan menjalankan skrip secara " +"langsung:" + +msgid "" +"An Ingress is a collection of rules that allow inbound connections to reach " +"the cluster services." +msgstr "" +"Ingress adalah kumpulan aturan yang memungkinkan koneksi masuk untuk " +"menjangkau layanan kluster." + +msgid "" +"Apart from the variables above with gerrit refspec values, additionally " +"export following environment variables with values as applicable:" +msgstr "" +"Terlepas dari variabel di atas dengan nilai gerrit refspec, ekspor tambahan " +"variabel lingkungan berikut dengan nilai yang berlaku:" + +msgid "" +"As a final validation step, re-run the **openstack helm stack list** and " +"**openstack helm keypair list** commands and confirm the returned results " +"are shown as empty.::" +msgstr "" +"Sebagai langkah validasi terakhir, jalankan kembali **openstack helm stack " +"list** dan **openstack helm keypair list** perintah dan konfirmasi hasil " +"yang dikembalikan ditampilkan sebagai kosong.::" + +msgid "" +"As any other Neutron plugin, TaaS neutron plugin functionality consists of " +"following modules:" +msgstr "" +"Seperti plugin Neutron lainnya, fungsionalitas plugin neutron TaaS terdiri " +"dari modul berikut:" + +msgid "" +"Before deploying TaaS and/or TaaS Dashboard, it needs to be added in Neutron " +"and/or Horizon LOCI images." +msgstr "" +"Sebelum menggunakan TaaS dan/atau TaaS Dashboard, perlu ditambahkan dalam " +"image Neutron dan/atau Horizon LOCI." + +msgid "" +"Below are some instructions and suggestions to help you get started with a " +"Kubeadm All-in-One environment on Ubuntu 18.04. Other supported versions of " +"Linux can also be used, with the appropriate changes to package installation." +msgstr "" +"Di bawah ini adalah beberapa petunjuk dan saran untuk membantu Anda memulai " +"dengan lingkungan Kubeadm All-in-One di Ubuntu 18.04. Versi Linux yang " +"didukung lainnya juga dapat digunakan, dengan perubahan yang sesuai untuk " +"instalasi paket." + +msgid "Build the requirements LOCI image using above commit" +msgstr "Buat persyaratan image LOCI menggunakan komit di atas" + +msgid "" +"By default OSH will use Google DNS Server IPs (8.8.8.8, 8.8.4.4) and will " +"update resolv.conf as a result. If those IPs are blocked by your proxy, " +"running the OSH scripts will result in the inability to connect to anything " +"on the network. These DNS nameserver entries can be changed by updating the " +"external_dns_nameservers entry in the file ``openstack-helm-infra/tools/" +"images/kubeadm-aio/assets/opt/playbooks/vars.yaml``." +msgstr "" +"Secara default, OSH akan menggunakan IP Server DNS Google (8.8.8.8, 8.8.4.4) " +"dan sebagai hasilnya akan memperbarui resolv.conf. Jika IP tersebut diblokir " +"oleh proxy Anda, menjalankan skrip OSH akan mengakibatkan ketidakmampuan " +"untuk terhubung ke apa pun di jaringan. Entri nameserver DNS ini dapat " +"diubah dengan memperbarui entri external_dns_nameservers dalam file " +"``openstack-helm-infra/tools/images/kubeadm-aio/assets/opt/playbooks/vars." +"yaml``." + +msgid "" +"By default the Calico CNI will use ``192.168.0.0/16`` and Kubernetes " +"services will use ``10.96.0.0/16`` as the CIDR for services. Check that " +"these CIDRs are not in use on the development node before proceeding, or " +"adjust as required." +msgstr "" +"Secara default, Calico CNI akan menggunakan layanan ``192.168.0.0/16`` dan " +"Kubernetes akan menggunakan ``10.96.0.0/16`` sebagai CIDR untuk layanan. " +"Periksa apakah CIDR ini tidak digunakan pada node pengembangan sebelum " +"melanjutkan, atau sesuaikan sesuai kebutuhan." + +msgid "" +"By default, this installation will use Google DNS Server IPs (8.8.8.8, " +"8.8.4.4) and will update resolv.conf as a result. If those IPs are blocked " +"by the proxy, this will overwrite the original DNS entries and result in the " +"inability to connect to anything on the network behind the proxy. These DNS " +"nameserver entries can be changed by updating the " +"``external_dns_nameservers`` entry in this file:" +msgstr "" +"Secara default, instalasi ini akan menggunakan IP Server DNS Google " +"(8.8.8.8, 8.8.4.4) dan sebagai hasilnya akan memperbarui resolv.conf. Jika " +"IP tersebut diblokir oleh proxy, ini akan menimpa entri DNS asli dan " +"mengakibatkan ketidakmampuan untuk terhubung ke apa pun di jaringan di " +"belakang proxy. Entri nameserver DNS ini dapat diubah dengan memperbarui " +"entri ``external_dns_nameservers`` dalam file ini:" + +msgid "Cleaning the Deployment" +msgstr "Membersihkan Deployment" + +msgid "Clone the OpenStack-Helm Repos" +msgstr "Mengkloning OpenStack-Helm Repos" + +msgid "Code examples below." +msgstr "Contoh kode di bawah ini." + +msgid "Common Deployment Requirements" +msgstr "Persyaratan Penerapan Umum" + +msgid "Configure OpenStack" +msgstr "Konfigurasikan OpenStack" + +msgid "Configure TaaS in Neutron chart" +msgstr "Konfigurasikan TaaS dalam chart Neutron" + +msgid "" +"Configuring OpenStack for a particular production use-case is beyond the " +"scope of this guide. Please refer to the OpenStack `Configuration `_ 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 " +"`_ dokumentasi untuk versi " +"OpenStack pilihan Anda untuk menentukan apa penggantian nilai tambahan harus " +"diberikan ke chart OpenStack-Helm untuk memastikan jaringan yang sesuai, " +"keamanan, dll. sudah ada." + +msgid "Contents:" +msgstr "Isi:" + +msgid "" +"Copy the key: ``sudo cp ~/.ssh/id_rsa /etc/openstack-helm/deploy-key.pem``" +msgstr "" +"Salin kunci: ``sudo cp ~/.ssh/id_rsa /etc/openstack-helm/deploy-key.pem``" + +msgid "Create a patchset for ``openstack/horizon`` repo" +msgstr "Buat patchset untuk repo ``openstack/horizon``" + +msgid "Create a patchset for ``openstack/neutron`` repo" +msgstr "Buat patchset untuk repo ``openstack/neutron``" + +msgid "Create a patchset for ``openstack/requirements`` repo" +msgstr "Buat patchset untuk repo ``openstack/requirements``" + +msgid "Create an environment file" +msgstr "Buat file lingkungan" + +msgid "Create an inventory file" +msgstr "Buat file inventaris" + +msgid "" +"Create an ssh-key on the master node, and add the public key to each node " +"that you intend to join the cluster." +msgstr "" +"Buat ssh-key pada node master, dan tambahkan kunci publik ke setiap node " +"yang Anda inginkan untuk bergabung dengan cluster." + +msgid "Create loopback devices for CEPH" +msgstr "Buat perangkat loopback untuk CEPH" + +msgid "" +"Create two loopback devices for ceph as one disk for OSD data and other disk " +"for block DB and block WAL. If loop0 and loop1 devices are busy in your " +"case , feel free to change them in parameters by using --ceph-osd-data and --" +"ceph-osd-dbwal options." +msgstr "" +"Buat dua perangkat loopback untuk ceph sebagai satu disk untuk data OSD dan " +"disk lain untuk blok DB dan blok WAL. Jika perangkat loop0 dan loop1 sibuk " +"dalam kasus Anda, jangan ragu untuk mengubahnya dalam parameter dengan " +"menggunakan opsi --ceph-osd-data dan --ceph-osd-dbwal." + +msgid "" +"Default log level for Neutron TaaS is :code:`INFO`. For changing it, " +"override following parameter:" +msgstr "" +"Tingkat log default untuk Neutron TaaS adalah :code:`INFO`. Untuk " +"mengubahnya, ganti parameter berikut:" + +msgid "Delete the keypair(s) returned from the list command above::" +msgstr "Hapus keypair(s) yang dikembalikan dari perintah daftar di atas::" + +msgid "" +"Delete the stacks returned from the *openstack helm stack list* command " +"above::" +msgstr "" +"Hapus stacks yang dikembalikan dari *openstack helm stack list* perintah di " +"atas ::" + +msgid "" +"Depending on your specific proxy, https_proxy may be the same as http_proxy. " +"Refer to your specific proxy documentation." +msgstr "" +"Bergantung pada proksi spesifik Anda, https_proxy mungkin sama dengan " +"http_proxy. Rujuk ke dokumentasi proxy spesifik Anda." + +msgid "Deploy Barbican" +msgstr "Terapkan Barbican" + +msgid "Deploy Ceph" +msgstr "Terapkan Ceph" + +msgid "Deploy Cinder" +msgstr "Terapkan Cinder" + +msgid "Deploy Compute Kit (Nova and Neutron)" +msgstr "Menyebarkan Compute Kit (Nova dan Neutron)" + +msgid "Deploy Glance" +msgstr "Terapkan Glance" + +msgid "Deploy Heat" +msgstr "Terapkan Heat" + +msgid "Deploy Horizon" +msgstr "Terapkan Horizon" + +msgid "Deploy Keystone" +msgstr "Terapkan Keystone" + +msgid "Deploy Kubernetes & Helm" +msgstr "Menyebarkan Kubernetes & Helm" + +msgid "Deploy Libvirt" +msgstr "Terapkan Libvirt" + +msgid "Deploy MariaDB" +msgstr "Terapkan MariaDB" + +msgid "Deploy Memcached" +msgstr "Terapkan Memcached" + +msgid "Deploy NFS Provisioner" +msgstr "Menerapkan NFS Provisioner" + +msgid "Deploy OVS-DPDK" +msgstr "Menyebarkan OVS-DPDK" + +msgid "Deploy OpenStack-Helm" +msgstr "Gunakan OpenStack-Helm" + +msgid "Deploy OpenvSwitch" +msgstr "Terapkan OpenvSwitch" + +msgid "Deploy RabbitMQ" +msgstr "Terapkan RabbitMQ" + +msgid "Deploy Rados Gateway for object store" +msgstr "Menerapkan Rados Gateway untuk menyimpan objek" + +msgid "Deploy TaaS Dashboard Plugin" +msgstr "Deploy TaaS Dashboard Plugin" + +msgid "Deploy TaaS Plugin" +msgstr "Deploy TaaS Plugin" + +msgid "Deploy tap-as-a-service (TaaS) Neutron / Dashboard plugin" +msgstr "Penyebaran plugin Tap-as-a-service (TaaS) Neutron/Dashboard" + +msgid "Deploy the ingress controller" +msgstr "Pasang ingress controller" + +msgid "Deployment" +msgstr "Penyebaran" + +msgid "Deployment With Ceph" +msgstr "Deployment Dengan Ceph" + +msgid "Deployment With NFS" +msgstr "Deployment Dengan NFS" + +msgid "Deployment with Tungsten Fabric" +msgstr "Penerapan dengan Tungsten Fabric" + +msgid "Development" +msgstr "Pengembangan" + +msgid "Environment tear-down" +msgstr "Environment tear-down (lingkungan meruntuhkan)" + +msgid "" +"Essentially the use of Ingress for OpenStack-Helm is an Nginx proxy service. " +"Ingress (Nginx) is accessible by your cluster public IP - e.g. the IP " +"associated with ``kubectl get pods -o wide --all-namespaces | grep ingress-" +"api`` Ingress/Nginx will be listening for server name requests of \"keystone" +"\" or \"keystone.openstack\" and will route those requests to the proper " +"internal K8s Services. These public listeners in Ingress must match the " +"external DNS that you will set up to access your OpenStack deployment. Note " +"each rule also has a Service that directs Ingress Controllers allow access " +"to the endpoints from within the cluster." +msgstr "" +"Pada dasarnya penggunaan Ingress for OpenStack-Helm adalah layanan proxy " +"Nginx. Ingress (Nginx) dapat diakses oleh IP publik kluster Anda - mis. IP " +"yang terkait dengan ``kubectl get pods -o wide --all-namespaces | grep " +"ingress-api`` Ingress/Nginx akan mendengarkan permintaan nama server " +"\"keystone\" atau \"keystone.openstack\" dan akan mengarahkan permintaan " +"tersebut ke K8s Services internal yang tepat. Pendengar publik di Ingress " +"harus sesuai dengan DNS eksternal yang akan Anda siapkan untuk mengakses " +"penyebaran OpenStack Anda. Perhatikan setiap aturan (rule) juga memiliki " +"Service yang mengarahkan Ingress Controllers memungkinkan akses ke endpoints " +"dari dalam kluster." + +msgid "Examples" +msgstr "Contoh" + +msgid "" +"Execution of the **900-use-it.sh** script results in the creation of 4 heat " +"stacks and a unique keypair enabling access to a newly created VM. " +"Subsequent runs of the **900-use-it.sh** script requires deletion of the " +"stacks, a keypair, and key files, generated during the initial script " +"execution." +msgstr "" +"Eksekusi skrip ** 900-use-it.sh ** menghasilkan penciptaan 4 heat stacks dan " +"keypair unik yang memungkinkan akses ke VM yang baru dibuat. Proses " +"selanjutnya dari skrip **900-use-it.sh ** memerlukan penghapusan stacks, " +"keypair, dan key files, yang dihasilkan selama eksekusi skrip awal." + +msgid "Exercise the Cloud" +msgstr "Latihlah Cloud" + +msgid "External DNS and FQDN" +msgstr "External DNS dan FQDN" + +msgid "External DNS to FQDN/Ingress" +msgstr "External DNS ke FQDN/Ingress" + +msgid "" +"First you have to set up OpenStack and Linux versions and install needed " +"packages" +msgstr "" +"Pertama, Anda harus mengatur versi OpenStack dan Linux dan menginstal paket " +"yang diperlukan" + +msgid "" +"For ``identity`` and ``dashboard`` at ``host_fdqn_override.public`` replace " +"``null`` with the value as ``keystone.os.foo.org`` and ``horizon.os.foo.org``" +msgstr "" +"Untuk ``identity`` dan ``dashboard`` pada ``host_fdqn_override.public`` " +"menggantikan ``null`` dengan nilai sebagai ``keystone.os.foo.org`` dan " +"``horizon.os.foo.org``" + +msgid "" +"For a deployment without cinder and horizon the system requirements are:" +msgstr "Untuk penyebaran tanpa cinder dan horizon, persyaratan sistem adalah:" + +msgid "" +"For a lab or proof-of-concept environment, the OpenStack-Helm gate scripts " +"can be used to quickly deploy a multinode Kubernetes cluster using KubeADM " +"and Ansible. Please refer to the deployment guide `here <./kubernetes-gate." +"html>`__." +msgstr "" +"Untuk lingkungan lab atau proof-of-concept, skrip gerbang OpenStack-Helm " +"dapat digunakan untuk dengan cepat menyebarkan kluster Kombetes multinode " +"menggunakan KubeADM dan Ansible. Silakan lihat panduan penerapan `here <./" +"kubernetes-gate.html>`__." + +msgid "" +"For example if gerrit refspec for this commit is \"refs/changes/xx/xxxxxx/x" +"\", so export the :code:`REQUIREMENTS_REF_SPEC` variable as follows:" +msgstr "" +"Misalnya jika gerrit refspec untuk commit ini adalah \"refs/changes/xx/" +"xxxxxx/x\", jadi ekspor variabel :code:`REQUIREMENTS_REF_SPEC` sebagai " +"berikut:" + +msgid "" +"For example if gerrit refspec for this commit is \"refs/changes/xx/xxxxxx/x" +"\"; so export the :code:`HORIZON_REF_SPEC` variable as follows:" +msgstr "" +"Sebagai contoh jika gerrit refspec untuk komit ini adalah \"refs/changes/xx/" +"xxxxxx/x\"; jadi ekspor variabel :code:`HORIZON_REF_SPEC` sebagai berikut:" + +msgid "" +"For example if gerrit refspec for this commit is \"refs/changes/xx/xxxxxx/x" +"\"; so export the :code:`NEUTRON_REF_SPEC` variable as follows:" +msgstr "" +"Sebagai contoh jika gerrit refspec untuk komit ini adalah \"ref / " +"perubahan / xx / xxxxxx / x\"; jadi ekspor variabel :code:`NEUTRON_REF_SPEC` " +"sebagai berikut:" + +msgid "For more details, refer to TaaS specification: Tap-as-a-service_." +msgstr "Untuk lebih jelasnya, lihat spesifikasi TaaS: Tap-as-a-service_." + +msgid "" +"For other deployment options, select appropriate ``Deployment with ...`` " +"option from `Index <../developer/index.html>`__ page." +msgstr "" +"Untuk opsi penerapan lainnya, pilih opsi ``Deployment with ...`` dari " +"halaman `Index <../developer/index.html>`__ ." + +msgid "Gate-Based Kubernetes" +msgstr "Gate-Based Kubernetes" + +msgid "Get the Nginx configuration from the Ingress Pod:" +msgstr "Dapatkan konfigurasi Nginx dari Ingress Pod:" + +msgid "Get the ``helm status`` of your chart." +msgstr "Dapatkan ``helm status`` dari chart Anda." + +msgid "Helm Chart Installation" +msgstr "Pemasangan Helm Chart" + +msgid "Host Configuration" +msgstr "Konfigurasi Host" + +msgid "Host Proxy & DNS Configuration" +msgstr "Host Proxy dan Konfigurasi DNS" + +msgid "" +"If OVS fails to start up because of no hugepages are available, check the " +"configuration of the OVS daemonset. Older versions of helm-toolkit were not " +"able to render hugepage configuration into the Kubernetes manifest and just " +"removed the hugepage attributes. If no hugepage configuration is defined for " +"the OVS daemonset, consider using a newer version of helm-toolkit." +msgstr "" +"Jika OVS gagal untuk memulai karena tidak ada hugepage yang tersedia, " +"periksa konfigurasi daemonset OVS. Versi helm-toolkit yang lebih lama tidak " +"dapat merender konfigurasi hugepage ke manifes Kubernetes dan hanya " +"menghapus atribut hugepage. Jika tidak ada konfigurasi hugepage yang " +"ditentukan untuk daemonset OVS, pertimbangkan untuk menggunakan versi helm-" +"toolkit yang lebih baru." + +msgid "" +"If doing an `AIO install `__, all the ``--set`` flags" +msgstr "" +"Jika melakukan suatu `AIO install `__, semua flags ``--set``" + +msgid "" +"If you are not deploying OSH behind a proxy, skip this step and continue " +"with \"Deploy Kubernetes & Helm\"." +msgstr "" +"Jika Anda tidak menggunakan OSH di belakang proxy, lewati langkah ini dan " +"lanjutkan dengan \"Deploy Kubernetes & Helm\"." + +msgid "If you are not deploying OSH behind a proxy, skip this step." +msgstr "Jika Anda tidak menggunakan OSH di belakang proxy, lewati langkah ini." + +msgid "" +"Implementing the FQDN overrides **must** be done at install time. If you run " +"these as helm upgrades, Ingress will notice the updates though none of the " +"endpoint build-out jobs will run again, unless they are cleaned up manually " +"or using a tool like Armada." +msgstr "" +"Menerapkan FQDN mengesampingkan **must** dilakukan pada waktu instalasi. " +"Jika Anda menjalankan ini sebagai peningkatan helm, Ingress akan melihat " +"pembaruan meskipun tidak ada tugas build-out endpoint yang akan berjalan " +"lagi, kecuali mereka dibersihkan secara manual atau menggunakan alat seperti " +"Armada." + +msgid "" +"In order to access your OpenStack deployment on Kubernetes we can use the " +"Ingress Controller or NodePorts to provide a pathway in. A background on " +"Ingress, OpenStack-Helm fully qualified domain name (FQDN) overrides, " +"installation, examples, and troubleshooting will be discussed here." +msgstr "" +"Untuk mengakses penyebaran OpenStack Anda di Kubernetes kita dapat " +"menggunakan Ingress Controller atau NodePorts untuk menyediakan jalur masuk " +"(pathway in). Latar belakang tentang Ingress, OpenStack-Helm yang memenuhi " +"syarat nama domain lengkap (FQDN) menimpa, pemasangan, contoh, dan pemecahan " +"masalah akan dibahas di sini ." + +msgid "" +"In order to allow OVS inside a pod to make use of hugepages, the " +"corresponding type and amount of hugepages must be specified in the resource " +"section of the OVS chart's values.yaml:" +msgstr "" +"Untuk memungkinkan OVS di dalam pod menggunakan hugepage, jenis dan jumlah " +"hugepage yang sesuai harus ditentukan di bagian sumber daya dari OVS chart's " +"values.yaml:" + +msgid "" +"In order to deploy OSH behind a proxy, add the following entries to " +"``openstack-helm-infra/tools/gate/devel/local-vars.yaml``:" +msgstr "" +"Untuk menggunakan OSH di belakang proxy, tambahkan entri berikut ke " +"``openstack-helm-infra/tools/gate/devel/local-vars.yaml``:" + +msgid "" +"In order to deploy OpenStack-Helm behind corporate proxy servers, add the " +"following entries to ``openstack-helm-infra/tools/gate/devel/local-vars." +"yaml``." +msgstr "" +"Untuk menyebarkan OpenStack-Helm di belakang server proxy perusahaan, " +"tambahkan entri berikut ini ``openstack-helm-infra/tools/gate/devel/local-" +"vars.yaml``." + +msgid "" +"In order to drive towards a production-ready OpenStack solution, our goal is " +"to provide containerized, yet stable `persistent volumes `_ that Kubernetes can use to " +"schedule applications that require state, such as MariaDB (Galera). Although " +"we assume that the project should provide a \"batteries included\" approach " +"towards persistent storage, we want to allow operators to define their own " +"solution as well. Examples of this work will be documented in another " +"section, however evidence of this is found throughout the project. If you " +"find any issues or gaps, please create a `story `_ to track what can be done to improve our " +"documentation." +msgstr "" +"Untuk menuju solusi OpenStack yang siap produksi, tujuan kami adalah " +"menyediakan paket kemas (containerized), namun stabil `persistent volumes " +"`_ yang " +"dapat Kubernetes gunakan untuk menjadwalkan aplikasi yang membutuhkan " +"status, seperti MariaDB (Galera). Meskipun kami menganggap bahwa proyek " +"harus memberikan pendekatan \"batteries included\" terhadap penyimpanan " +"persisten, kami ingin mengizinkan operator untuk menentukan solusi mereka " +"sendiri juga. Contoh pekerjaan ini akan didokumentasikan di bagian lain, " +"namun bukti ini ditemukan di seluruh proyek. Jika Anda menemukan masalah " +"atau celah, silakan buat `story `_ untuk melacak apa yang dapat dilakukan untuk meningkatkan " +"dokumentasi kami." + +msgid "" +"In the example above, bonding isn't used and hence an empty list is passed " +"in the \"bonds\" section." +msgstr "" +"Dalam contoh di atas, ikatan tidak digunakan dan karenanya daftar kosong " +"dilewatkan di bagian \"bonds\"." + +msgid "" +"In this example, 8 hugepages of 1G size have been allocated. 2 of those are " +"being used and 6 are still available." +msgstr "" +"Dalam contoh ini, 8 hugepage ukuran 1G telah dialokasikan. 2 dari mereka " +"sedang digunakan dan 6 masih tersedia." + +msgid "" +"In this example, the NIC with PCI-ID 0000:00:04.0 is connected to NUMA " +"socket 1. As a result, this NIC can only be used by OVS if" +msgstr "" +"Dalam contoh ini, NIC dengan PCI-ID 0000:00:04.0 terhubung ke soket NUMA 1. " +"Akibatnya, NIC ini hanya dapat digunakan oleh OVS jika" + +msgid "Ingress" +msgstr "Ingress" + +msgid "Install Basic Utilities" +msgstr "Install Basic Utilities" + +msgid "Install OpenStack packages" +msgstr "Instal paket OpenStack" + +msgid "Install OpenStack-Helm" +msgstr "Memasang OpenStack-Helm" + +msgid "Install k8s Minikube" +msgstr "Instal k8s Minikube" + +msgid "Installation" +msgstr "Instalasi" + +msgid "Intro" +msgstr "Intro" + +msgid "" +"It can be configured to give services externally-reachable URLs, load " +"balance traffic, terminate SSL, offer name based virtual hosting, and more." +msgstr "" +"Ini dapat dikonfigurasi untuk memberikan layanan URL yang dapat dijangkau " +"secara eksternal, memuat keseimbangan lalu lintas (load balance traffic), " +"mengakhiri SSL, menawarkan virtual hosting berbasis nama, dan banyak lagi." + +msgid "" +"It is recommended to add your own existing DNS nameserver entries to avoid " +"losing connection." +msgstr "" +"Disarankan untuk menambahkan entri server nama DNS Anda sendiri yang ada " +"untuk menghindari kehilangan koneksi." + +msgid "Kubernetes Preparation" +msgstr "Persiapan Kubernetes" + +msgid "Kubernetes and Common Setup" +msgstr "Kubernetes dan Pengaturan Umum" + +msgid "Latest Version Installs" +msgstr "Pemasangan Versi Terbaru" + +msgid "List the keypair(s) generated during the script execution::" +msgstr "Daftar keypair(s) yang dihasilkan selama eksekusi skrip::" + +msgid "" +"List the stacks created during script execution which will need to be " +"deleted::" +msgstr "Daftar stacks yang dibuat selama eksekusi skrip yang perlu dihapus ::" + +msgid "" +"Look for *server* configuration with a *server_name* matching your desired " +"FQDN" +msgstr "" +"Carilah konfigurasi *server* dengan *server_name* sesuai dengan FQDN yang " +"Anda inginkan" + +msgid "" +"Managing and configuring a Kubernetes cluster is beyond the scope of " +"OpenStack-Helm and this guide." +msgstr "" +"Mengelola dan mengkonfigurasi kluster Kubernetes berada di luar lingkup " +"OpenStack-Helm dan panduan ini." + +msgid "" +"Manually remove the keypair directories created from the script in the ~/." +"ssh directory::" +msgstr "" +"Hapus secara manual direktori keypair yang dibuat dari skrip di ~/.ssh " +"directory::" + +msgid "" +"Many of the default container images that are referenced across OpenStack-" +"Helm charts are not intended for production use; for example, while LOCI and " +"Kolla can be used to produce production-grade images, their public reference " +"images are not prod-grade. In addition, some of the default images use " +"``latest`` or ``master`` tags, which are moving targets and can lead to " +"unpredictable behavior. For production-like deployments, we recommend " +"building custom images, or at minimum caching a set of known images, and " +"incorporating them into OpenStack-Helm via values overrides." +msgstr "" +"Banyak image kontainer default yang direferensikan di chart OpenStack-Helm " +"tidak dimaksudkan untuk penggunaan produksi; misalnya, sementara LOCI dan " +"Kolla dapat digunakan untuk menghasilkan image tingkat produksi, image " +"referensi publik mereka tidak bermutu (not prod-grade). Selain itu, beberapa " +"image default menggunakan tag ``latest`` atau ``master``, yang merupakan " +"target bergerak dan dapat menyebabkan perilaku yang tidak dapat diprediksi. " +"Untuk penyebaran seperti produksi, kami menyarankan Anda untuk membuat image " +"khusus, atau minimal cache satu set image yang dikenal, dan menggabungkannya " +"ke OpenStack-Helm melalui penggantian nilai." + +msgid "" +"More information can be found in the `Openvswitch documentation `_." +msgstr "" +"Informasi lebih lanjut dapat ditemukan di `Openvswitch documentation `_." + +msgid "" +"More information on how to allocate and configure hugepages on the host OS " +"can be found in the `Openvswitch documentation `_." +msgstr "" +"Informasi lebih lanjut tentang cara mengalokasikan dan mengonfigurasi " +"hugepage pada OS host dapat ditemukan di `Openvswitch documentation `_." + +msgid "Multinode" +msgstr "Multinode" + +msgid "Neutron TaaS support in Openstack-Helm commits:" +msgstr "Dukungan Neutron TaaS di komit Openstack-Helm:" + +msgid "Neutron and Horizon LOCI images" +msgstr "image Neutron dan Horizon LOCI" + +msgid "" +"Note if you need to make a DNS change, you will have to do uninstall (``helm " +"delete ``) and install again." +msgstr "" +"Catatan jika Anda perlu membuat perubahan DNS, Anda harus melakukan " +"uninstall (``helm delete ``) dan instal lagi." + +msgid "" +"Note that OVS-DPDK deployment has been tested with Openstack Rocky release " +"and Ubuntu Bionic container distributions. If the above variables aren't " +"set, the defaults (currently Openstack Ocata and Ubuntu Xenial) will be used." +msgstr "" +"Perhatikan bahwa penyebaran OVS-DPDK telah diuji dengan rilis Openstack " +"Rocky dan distribusi kontainer Ubuntu Bionic. Jika variabel di atas tidak " +"disetel, defaultnya (saat ini Openstack Ocata dan Ubuntu Xenial) akan " +"digunakan." + +msgid "" +"Note that this command will only enable you to auth successfully using the " +"``python-openstackclient`` CLI. To use legacy clients like the ``python-" +"novaclient`` from the CLI, reference the auth values in ``/etc/openstack/" +"clouds.yaml`` and run::" +msgstr "" +"Perhatikan bahwa perintah ini hanya akan memungkinkan Anda untuk auth " +"berhasil menggunakan ``python-openstackclient`` CLI. Untuk menggunakan klien " +"legacy seperti ``python-novaclient`` dari CLI, referensi nilai auth di ``/" +"etc/openstack/clouds.yaml`` dan jalankan ::" + +msgid "OSH Proxy & DNS Configuration" +msgstr "Konfigurasi Proxy & DNS OSH" + +msgid "" +"OSH runs updates for local apt packages, so we will need to set the proxy " +"for apt as well by adding these lines to `/etc/apt/apt.conf`:" +msgstr "" +"OSH menjalankan pembaruan untuk paket apt lokal, jadi kami juga perlu " +"mengatur proxy untuk apt dengan menambahkan baris-baris ini ke `/etc/apt/" +"apt.conf`:" + +msgid "OVS startup failure" +msgstr "Kegagalan startup OVS" + +msgid "" +"On the host or master node, install the latest versions of Git, CA Certs & " +"Make if necessary" +msgstr "" +"Pada host atau node master, instal versi terbaru Git, CA Certs & Make jika " +"perlu" + +msgid "On the master node create an environment file for the cluster:" +msgstr "Pada node master buat file lingkungan untuk kluster:" + +msgid "On the master node create an inventory file for the cluster:" +msgstr "Pada node master buat file inventaris untuk kluster:" + +msgid "On the master node run the playbooks:" +msgstr "Pada node master jalankan playbook:" + +msgid "On the worker nodes:" +msgstr "Di worker nodes:" + +msgid "" +"Once OpenStack-Helm has been deployed, the cloud can be exercised either " +"with the OpenStack client, or the same heat templates that are used in the " +"validation gates." +msgstr "" +"Setelah OpenStack-Helm dikerahkan, cloud dapat dijalankan baik dengan klien " +"OpenStack, atau heat template yang sama yang digunakan di gate validasi." + +msgid "" +"Once installed, access the API's or Dashboard at `http://horizon.os.foo.org`" +msgstr "Setelah dipasang, akses API atau Dasbor di `http://horizon.os.foo.org`" + +msgid "" +"Once the above requirements are met, start deploying Openstack Helm using " +"the deployment scripts under the dpdk directory in an increasing order" +msgstr "" +"Setelah persyaratan di atas terpenuhi, mulailah menggunakan Openstack Helm " +"menggunakan skrip deployment di bawah direktori dpdk dalam urutan yang " +"meningkat" + +msgid "" +"Once the host has been configured the repos containing the OpenStack-Helm " +"charts should be cloned onto each node in the cluster:" +msgstr "" +"Setelah host dikonfigurasi, repositori yang berisi chart OpenStack-Helm " +"harus dikloning ke setiap node dalam kluster:" + +msgid "" +"Once the host has been configured the repos containing the OpenStack-Helm " +"charts should be cloned:" +msgstr "" +"Setelah host dikonfigurasi, repositori yang berisi chart OpenStack-Helm " +"harus dikloning:" + +msgid "" +"One can also specify the name of Openstack release and container OS " +"distribution as overrides before running the deployment scripts, for " +"instance," +msgstr "" +"Seseorang juga dapat menentukan nama rilis Openstack dan distribusi OS " +"kontainer sebagai penggantian sebelum menjalankan skrip penyebaran, misalnya," + +msgid "" +"OpenStack-Helm uses the hosts networking namespace for many pods including, " +"Ceph, Neutron and Nova components. For this, to function, as expected pods " +"need to be able to resolve DNS requests correctly. Ubuntu Desktop and some " +"other distributions make use of ``mdns4_minimal`` which does not operate as " +"Kubernetes expects with its default TLD of ``.local``. To operate at " +"expected either change the ``hosts`` line in the ``/etc/nsswitch.conf``, or " +"confirm that it matches:" +msgstr "" +"OpenStack-Helm menggunakan namespace jaringan host untuk banyak pod " +"termasuk, Ceph, Neutron dan Nova komponen. Untuk ini, berfungsi, seperti " +"yang diharapkan pod harus dapat menyelesaikan permintaan DNS dengan benar. " +"Desktop Ubuntu dan beberapa distro lain memanfaatkan ``mdns4_minimal`` yang " +"tidak beroperasi karena Kubernetes mengharapkan dengan TLD defaultnya ``." +"local``. Untuk beroperasi pada diharapkan baik mengubah baris ``host`` di ``/" +"etc/nsswitch.conf``, atau konfirmasi bahwa itu cocok:" + +msgid "" +"OpenStack-Helm utilizes the `Kubernetes Ingress Controller `__" +msgstr "" +"OpenStack-Helm memanfaatkan `Kubernetes Ingress Controller `__" + +msgid "OpenStack-Helm-Infra KubeADM deployment" +msgstr "OpenStack-Helm-Infra KubeADM deployment" + +msgid "" +"Other versions and considerations (such as other CNI SDN providers), config " +"map data, and value overrides will be included in other documentation as we " +"explore these options further." +msgstr "" +"Versi dan pertimbangan lain (seperti penyedia CNI SDN lainnya), data peta " +"konfigurasi, dan penggantian nilai akan dimasukkan dalam dokumentasi lain " +"saat kami mengeksplorasi opsi ini lebih lanjut." + +msgid "Override images in Neutron chart" +msgstr "Override image dalam chart Neutron" + +msgid "" +"Override the :code:`images` section parameters for Neutron chart with the " +"custom LOCI image's tag, prepared as explained in above sections." +msgstr "" +"Override parameter bagian :code:`images` untuk chart Neutron dengan tag " +"image LOCI kustom, disiapkan seperti dijelaskan di bagian di atas." + +msgid "Overview" +msgstr "Ikhtisar" + +msgid "PMD threads have been assigned to NUMA socket 1." +msgstr "Threads PMD telah ditetapkan ke soket NUMA 1." + +msgid "Passwordless Sudo" +msgstr "Passwordless Sudo" + +msgid "" +"Please see the supported application versions outlined in the `source " +"variable file `_." +msgstr "" +"Silakan lihat versi aplikasi yang didukung yang diuraikan dalam `source " +"variable file `_." + +msgid "Plugins" +msgstr "Plugins" + +msgid "Prepare LOCI images" +msgstr "Mempersiapkan image LOCI" + +msgid "" +"Prepare Neutron or Horizon LOCI image using this requirements image as :code:" +"`docker build --build-arg WHEELS` command argument." +msgstr "" +"Mempersiapkan image Neutron atau Horizon LOCI menggunakan image persyaratan " +"ini sebagai argumen perintah :code:`docker build --build-arg WHEELS`." + +msgid "" +"Prepare a requirements LOCI image with Neutron TaaS and TaaS Dashboard code " +"installed." +msgstr "" +"Mempersiapkan persyaratan image LOCI dengan Neutron TaaS dan TaaS Dashboard " +"code yang diinstal." + +msgid "" +"Prepare ahead of time your FQDN and DNS layouts. There are a handful of " +"OpenStack endpoints you will want to expose for API and Dashboard access." +msgstr "" +"Persiapkan sebelumnya tata letak FQDN dan DNS Anda. Ada beberapa endpoint " +"OpenStack yang ingin Anda buka untuk akses API dan Dashboard." + +msgid "Prepare host" +msgstr "Siapkan host" + +msgid "Prepare host and openstack helm for tf" +msgstr "Siapkan host dan openstack helm untuk tf" + +msgid "Proxy Configuration" +msgstr "Konfigurasi Proxy" + +msgid "Putting it all together" +msgstr "Menyatukan semuanya" + +msgid "References" +msgstr "Referensi" + +msgid "Removing Helm Charts" +msgstr "Menghapus Helm Chart" + +msgid "Requirements" +msgstr "Persyaratan" + +msgid "Requirements LOCI image" +msgstr "Persyaratan image LOCI" + +msgid "Requirements and Host Configuration" +msgstr "Persyaratan dan Konfigurasi Host" + +msgid "Run the playbooks" +msgstr "Jalankan playbook" + +msgid "SSH-Key preparation" +msgstr "Persiapan SSH-Key" + +msgid "" +"Set correct ownership: ``sudo chown ubuntu /etc/openstack-helm/deploy-key." +"pem``" +msgstr "" +"Setel kepemilikan yang benar: ``sudo chown ubuntu /etc/openstack-helm/deploy-" +"key.pem``" + +msgid "Set log level for TaaS" +msgstr "Setel tingkat log untuk TaaS" + +msgid "" +"Set your local environment variables to use the proxy information. This " +"involves adding or setting the following values in ``/etc/environment``:" +msgstr "" +"Setel variabel lingkungan lokal Anda untuk menggunakan informasi proxy. Ini " +"melibatkan penambahan atau pengaturan nilai berikut di ``/etc/environment``:" + +msgid "Setup Clients on the host and assemble the charts" +msgstr "Siapkan Klien pada host dan susun chart" + +msgid "Setup DNS for use cluster DNS" +msgstr "Setup DNS untuk menggunakan DNS cluster" + +msgid "Setup Glance" +msgstr "Setup Glance" + +msgid "Setup Heat" +msgstr "Setup Heat" + +msgid "Setup Ingress" +msgstr "Setup Ingress" + +msgid "Setup Keystone" +msgstr "Setup Keystone" + +msgid "Setup MariaDB" +msgstr "Setup MariaDB" + +msgid "Setup Memcached" +msgstr "Setup Memcached" + +msgid "Setup NFS" +msgstr "Setup NFS" + +msgid "Setup Neutron and Nova" +msgstr "Setup Neutron dan Nova" + +msgid "Setup OpenStack client" +msgstr "Atur klien OpenStack" + +msgid "Setup RabbitMQ" +msgstr "Setup RabbitMQ" + +msgid "Setup Tungsten Fabric" +msgstr "Setup Tungsten Fabric" + +msgid "Setup env for apply values_overrides" +msgstr "Siapkan env untuk menerapkan values_overrides" + +msgid "Setup libvirt" +msgstr "Setup libvirt" + +msgid "Setup the gateway to the public network" +msgstr "Siapkan gateway ke jaringan publik" + +msgid "Subsequent Runs & Post Clean-up" +msgstr "Subsequent Runs & Post Clean-up" + +msgid "System Requirements" +msgstr "Persyaratan sistem" + +msgid "TaaS Architecture" +msgstr "Arsitektur TaaS" + +msgid "" +"TaaS dashboard plugin can be deployed simply by using custom LOCI images " +"having TaaS Dashboard code installed (as explained in above sections), i.e. " +"override the :code:`images` section parameters for Horizon charts:" +msgstr "" +"Plugin dashboard TaaS dapat digunakan hanya dengan menggunakan image LOCI " +"kustom yang memasang kode Dashboard TaaS (seperti dijelaskan di bagian di " +"atas), misal override parameter bagian :code:`images` untuk chart Horizon:" + +msgid "" +"TaaS plugin provides a mechanism to mirror certain traffic (for example " +"tagged with specific VLANs) from a source VM to any traffic analyzer VM. " +"When packet will be forwarded, the original value of source and target ip/" +"ports information will not be altered and the system administrator will be " +"able to run, for ex. tcpdump, on the target VM to trace these packets." +msgstr "" +"Plugin TaaS menyediakan mekanisme untuk mencerminkan lalu lintas tertentu " +"(misalnya ditandai dengan VLAN tertentu) dari sumber VM ke VM penganalisa " +"lalu lintas apa pun. Ketika paket akan diteruskan, nilai asli sumber dan " +"informasi target ip/port tidak akan diubah dan administrator sistem akan " +"dapat berjalan, misalnya. tcpdump, pada VM target untuk melacak paket ini." + +msgid "" +"Test this by ssh'ing to a node and then executing a command with 'sudo'. " +"Neither operation should require a password." +msgstr "" +"Uji ini dengan ssh'ing ke node dan kemudian jalankan perintah dengan 'sudo'. " +"Operasi tidak harus menggunakan kata sandi." + +msgid "" +"The NUMA socket a given NIC is connected to can be found in the ovs-vswitchd " +"log:" +msgstr "" +"Soket NUMA yang terhubung dengan NIC dapat ditemukan di log ovs-vswitchd:" + +msgid "" +"The OpenStack clients and Kubernetes RBAC rules, along with assembly of the " +"charts can be performed by running the following commands:" +msgstr "" +"Klien OpenStack dan aturan Kubernetes RBAC, bersama dengan perakitan chart " +"dapat dilakukan dengan menjalankan perintah berikut:" + +msgid "" +"The `./tools/deployment/multinode/kube-node-subnet.sh` script requires " +"docker to run." +msgstr "" +"Script `./tools/deployment/multinode/kube-node-subnet.sh` membutuhkan docker " +"untuk menjalankan." + +msgid "" +"The ``.svc.cluster.local`` address is required to allow the OpenStack client " +"to communicate without being routed through proxy servers. The IP address " +"``172.17.0.1`` is the advertised IP address for the Kubernetes API server. " +"Replace the addresses if your configuration does not match the one defined " +"above." +msgstr "" +"Alamat ``.svc.cluster.local`` diperlukan untuk memungkinkan klien OpenStack " +"berkomunikasi tanpa diarahkan melalui server proxy. Alamat IP ``172.17.0.1`` " +"adalah alamat IP yang diiklankan (advertised) untuk server API Kubernetes. " +"Ganti alamat jika konfigurasi Anda tidak sesuai dengan yang didefinisikan di " +"atas." + +msgid "The default FQDN's for OpenStack-Helm are" +msgstr "Default FQDN untuk OpenStack-Helm adalah" + +msgid "" +"The example above uses the default values used by ``openstack-helm-infra``." +msgstr "" +"Contoh di atas menggunakan nilai default yang digunakan oleh ``openstack-" +"helm-infra``." + +msgid "" +"The following commands all assume that they are run from the ``/opt/" +"openstack-helm`` directory." +msgstr "" +"Perintah berikut semua menganggap bahwa mereka dijalankan dari direktori ``/" +"opt/openstack-helm``." + +msgid "" +"The following commands all assume that they are run from the ``openstack-" +"helm`` directory and the repos have been cloned as above." +msgstr "" +"Perintah berikut semua berasumsi bahwa mereka dijalankan dari direktori " +"``openstack-helm`` dan repo telah dikloning seperti di atas." + +msgid "" +"The following steps serve as a guide to clean-up the client environment by " +"deleting stacks and respective artifacts created during the **900-use-it." +"sh** script:" +msgstr "" +"Langkah-langkah berikut berfungsi sebagai panduan untuk membersihkan " +"lingkungan klien dengan menghapus stacks dan artefak masing-masing yang " +"dibuat selama skrip **900-use-it.sh **:" + +msgid "" +"The installation procedures below, will take an administrator from a new " +"``kubeadm`` installation to OpenStack-Helm deployment." +msgstr "" +"Prosedur instalasi di bawah ini, akan mengambil administrator dari instalasi " +"``kubeadm`` baru ke penyebaran OpenStack-Helm." + +msgid "" +"The mapping of CPU cores to NUMA sockets can be determined by means of " +"``lspci``, for instance:" +msgstr "" +"Pemetaan cores CPU ke soket NUMA dapat ditentukan dengan menggunakan " +"``lspci``, misalnya:" + +msgid "The recommended minimum system requirements for a full deployment are:" +msgstr "" +"Persyaratan sistem minimum yang disarankan untuk penyebaran lengkap adalah:" + +msgid "" +"The script below configures Ceph to use loopback devices created in previous " +"step as backend for ceph osds. To configure a custom block device-based " +"backend, please refer to the ``ceph-osd`` `values.yaml `_." +msgstr "" +"Script di bawah mengkonfigurasi Ceph untuk menggunakan perangkat loopback " +"yang dibuat pada langkah sebelumnya sebagai backend untuk ceph osds. Untuk " +"mengonfigurasi backend berbasis perangkat khusus blokir, silakan merujuk ke " +"``ceph-osd`` `values.yaml `_." + +msgid "" +"The upstream Ceph image repository does not currently pin tags to specific " +"Ceph point releases. This can lead to unpredictable results in long-lived " +"deployments. In production scenarios, we strongly recommend overriding the " +"Ceph images to use either custom built images or controlled, cached images." +msgstr "" +"Repositori image Ceph hulu saat ini tidak pin tag untuk rilis Ceph point " +"tertentu. Hal ini dapat menyebabkan hasil yang tak terduga dalam penempatan " +"jangka panjang. Dalam skenario produksi, kami sangat menyarankan untuk " +"mengganti image Ceph untuk menggunakan apakah image yang dibuat khusus " +"ataupun image yang dikontrol dan di-cache." + +msgid "" +"These commands will restore the environment back to a clean Kubernetes " +"deployment, that can either be manually removed or over-written by " +"restarting the deployment process. It is recommended to restart the host " +"before doing so to ensure any residual state, eg. Network interfaces are " +"removed." +msgstr "" +"Perintah ini akan memulihkan lingkungan kembali ke penyebaran Kubernetes " +"bersih, yang dapat dihapus secara manual atau ditulis berlebihan dengan " +"memulai kembali proses penerapan. Dianjurkan untuk me-restart host sebelum " +"melakukannya untuk memastikan setiap status yang tersisa, misalnya Network " +"interfaces dihapus." + +msgid "These values can be retrieved by running:" +msgstr "Nilai-nilai ini dapat diambil dengan menjalankan:" + +msgid "" +"This guide assumes that users wishing to deploy behind a proxy have already " +"defined the conventional proxy environment variables ``http_proxy``, " +"``https_proxy``, and ``no_proxy``." +msgstr "" +"Panduan ini mengasumsikan bahwa pengguna yang ingin menyebarkan di belakang " +"proxy telah mendefinisikan variabel lingkungan proksi konvensional " +"``http_proxy``, ``https_proxy``, dan ``no_proxy``." + +msgid "This guide covers the minimum number of requirements to get started." +msgstr "Panduan ini mencakup jumlah minimum persyaratan untuk memulai." + +msgid "" +"This guide explains how to deploy tap-as-a-service (TaaS) Neutron plugin and " +"TaaS Dashboard plugin in Neutron and Horizon charts respectively." +msgstr "" +"Panduan ini menjelaskan cara menggunakan plugin Tap-as-a-service (TaaS) " +"Neutron dan plugin TaaS Dashboard di masing-masing chart Neutron dan Horizon." + +msgid "" +"This installation, by default will use Google DNS servers, 8.8.8.8 or " +"8.8.4.4 and updates resolv.conf. These DNS nameserver entries can be changed " +"by updating file ``/opt/openstack-helm-infra/tools/images/kubeadm-aio/assets/" +"opt/playbooks/vars.yaml`` under section ``external_dns_nameservers``. This " +"change must be done on each node in your cluster." +msgstr "" +"Instalasi ini, secara default akan menggunakan server DNS Google, 8.8.8.8 " +"atau 8.8.4.4 dan memperbarui resolv.conf. Entri server nama DNS ini dapat " +"diubah dengan memperbarui file ``/opt/openstack-helm-infra/tools/images/" +"kubeadm-aio/assets/opt/playbooks/vars.yaml`` di bawah bagian " +"``external_dns_nameservers``. Perubahan ini harus dilakukan pada setiap node " +"di kluster Anda." + +msgid "This is a two step process, i.e." +msgstr "Ini adalah proses dua langkah, misal" + +msgid "" +"This script will create two loopback devices for Ceph as one disk for OSD " +"data and other disk for block DB and block WAL. If default devices (loop0 " +"and loop1) are busy in your case, feel free to change them by exporting " +"environment variables(CEPH_OSD_DATA_DEVICE and CEPH_OSD_DB_WAL_DEVICE)." +msgstr "" +"Script ini akan membuat dua perangkat loopback untuk Ceph sebagai satu disk " +"untuk data OSD dan disk lain untuk memblokir DB dan memblokir WAL. Jika " +"perangkat default (loop0 dan loop1) sibuk dalam kasus Anda, jangan ragu " +"untuk mengubahnya dengan mengekspor variabel lingkungan " +"(CEPH_OSD_DATA_DEVICE dan CEPH_OSD_DB_WAL_DEVICE)." + +msgid "" +"This will delete all Kubernetes resources generated when the chart was " +"instantiated. However for OpenStack charts, by default, this will not delete " +"the database and database users that were created when the chart was " +"installed. All OpenStack projects can be configured such that upon deletion, " +"their database will also be removed. To delete the database when the chart " +"is deleted the database drop job must be enabled before installing the " +"chart. There are two ways to enable the job, set the job_db_drop value to " +"true in the chart's ``values.yaml`` file, or override the value using the " +"helm install command as follows:" +msgstr "" +"Ini akan menghapus semua sumber daya Kubernetes yang dihasilkan saat chart " +"dibuat. Namun untuk chart OpenStack, secara default, ini tidak akan " +"menghapus database dan pengguna database yang dibuat ketika chart dipasang. " +"Semua proyek OpenStack dapat dikonfigurasi sedemikian rupa sehingga pada " +"saat penghapusan, database mereka juga akan dihapus. Untuk menghapus " +"database ketika chart dihapus, pekerjaan drop database harus diaktifkan " +"sebelum menginstal chart. Ada dua cara untuk mengaktifkan pekerjaan, " +"mengatur nilai job_db_drop menjadi true dalam file ``values.yaml`` pada " +"chart, atau mengganti nilai menggunakan perintah penginstalan helm seperti " +"berikut:" + +msgid "" +"Throughout this guide the assumption is that the user is: ``ubuntu``. " +"Because this user has to execute root level commands remotely to other " +"nodes, it is advised to add the following lines to ``/etc/sudoers`` for each " +"node:" +msgstr "" +"Sepanjang panduan ini, asumsinya adalah bahwa pengguna adalah: ``ubuntu``. " +"Karena pengguna ini harus mengeksekusi perintah level root dari jarak jauh " +"ke node lain, disarankan untuk menambahkan baris berikut ke ``/etc/sudoers`` " +"untuk setiap node:" + +msgid "" +"To allocate hugepages to NUMA sockets in OVS, ensure that the " +"``socket_memory`` attribute in values.yaml specifies a value for the " +"corresponding NUMA socket. In the following example, OVS will use one 1G " +"hugepage for NUMA socket 0 and socket 1." +msgstr "" +"Untuk mengalokasikan hugepage ke soket NUMA di OVS, pastikan bahwa atribut " +"``socket_memory`` dalam values.yaml menentukan nilai untuk soket NUMA yang " +"sesuai. Dalam contoh berikut, OVS akan menggunakan satu hugepage 1G untuk " +"NUMA socket 0 dan socket 1." + +msgid "" +"To continue to deploy OpenStack on Kubernetes via OSH, see :doc:`Deploy " +"NFS<./deploy-with-nfs>` or :doc:`Deploy Ceph<./deploy-with-ceph>`." +msgstr "" +"Untuk terus menggunakan OpenStack di Kubernetes melalui OSH, lihat :doc:" +"`Deploy NFS<./deploy-with-nfs>` or :doc:`Deploy Ceph<./deploy-with-ceph>`." + +msgid "" +"To copy the ssh key to each node, this can be accomplished with the ``ssh-" +"copy-id`` command, for example: *ssh-copy-id ubuntu@192.168.122.178*" +msgstr "" +"Untuk menyalin kunci ssh ke setiap node, ini dapat diselesaikan dengan " +"perintah ``ssh-copy-id``, misalnya: *ssh-copy-id ubuntu@192.168.122.178*" + +msgid "To delete an installed helm chart, use the following command:" +msgstr "Untuk menghapus helm chart yang terpasang, gunakan perintah berikut:" + +msgid "To generate the key you can use ``ssh-keygen -t rsa``" +msgstr "Untuk menghasilkan kunci yang dapat Anda gunakan ``ssh-keygen -t rsa``" + +msgid "" +"To run further commands from the CLI manually, execute the following to set " +"up authentication credentials::" +msgstr "" +"Untuk menjalankan perintah lebih lanjut dari CLI secara manual, jalankan " +"perintah berikut untuk menyiapkan kredensial otentikasi ::" + +msgid "" +"To tear-down, the development environment charts should be removed first " +"from the 'openstack' namespace and then the 'ceph' namespace using the " +"commands from the `Removing Helm Charts` section. Additionally charts should " +"be removed from the 'nfs' and 'libvirt' namespaces if deploying with NFS " +"backing or bare metal development support. You can run the following " +"commands to loop through and delete the charts, then stop the kubelet " +"systemd unit and remove all the containers before removing the directories " +"used on the host by pods." +msgstr "" +"Untuk meruntuhkan (tear-down), chart lingkungan pengembangan harus dihapus " +"pertama dari namespace 'openstack' dan kemudian namespace 'ceph' menggunakan " +"perintah dari bagian `Removing Helm Charts`. Selain itu, chart harus dihapus " +"dari namespace 'nfs' dan 'libvirt' jika digunakan dengan dukungan dukungan " +"NFS atau bare metal. Anda dapat menjalankan perintah berikut untuk mengulang " +"dan menghapus chart, kemudian menghentikan unit kubelet systemd dan " +"menghapus semua kontainer sebelum menghapus direktori yang digunakan pada " +"host oleh pod." + +msgid "Troubleshooting" +msgstr "Penyelesaian masalah" + +msgid "" +"Tungsten Fabric is the multicloud and multistack network solution which you " +"can use for your OpenStack as a network plugin. This document decribes how " +"you can deploy a single node Open Stack based on Tungsten Fabric using " +"openstack helm for development purpose." +msgstr "" +"Tungsten Fabric adalah solusi jaringan multicloud dan multistack yang dapat " +"Anda gunakan untuk OpenStack Anda sebagai plugin jaringan. Dokumen ini " +"menjelaskan bagaimana Anda bisa menggunakan Open Stack node tunggal " +"berdasarkan Tungsten Fabric menggunakan OpenStack helm untuk tujuan " +"pengembangan." + +msgid "" +"Two similar options exist to set the FQDN overrides for External DNS mapping." +msgstr "" +"Dua opsi serupa ada untuk mengatur FQDN menimpa untuk pemetaan DNS Eksternal." + +msgid "" +"Until the Ubuntu kernel shipped with 16.04 supports CephFS subvolume mounts " +"by default the `HWE Kernel <../troubleshooting/ubuntu-hwe-kernel.html>`__ is " +"required to use CephFS." +msgstr "" +"Sampai kernel Ubuntu yang dikirim dengan 16.04 mendukung CephFS subvolume " +"mount secara default `HWE Kernel <../troubleshooting/ubuntu-hwe-kernel." +"html>`__ diperlukan untuk menggunakan CephFS." + +msgid "" +"Update your lab/environment DNS server with your appropriate host values " +"creating A Records for the edge node IP's and various FQDN's. Alternatively " +"you can test these settings locally by editing your ``/etc/hosts``. Below is " +"an example with a dummy domain ``os.foo.org`` and dummy Ingress IP " +"``1.2.3.4``." +msgstr "" +"Perbarui server DNS lab/environment Anda dengan nilai host yang sesuai Anda " +"membuat A Records untuk node edge IP dan berbagai FQDN. Atau Anda dapat " +"menguji pengaturan ini secara lokal dengan mengedit ``/etc/hosts`` Anda. Di " +"bawah ini adalah contoh dengan dummy domain ``os.foo.org`` dan dummy Ingress " +"IP ``1.2.3.4``." + +msgid "" +"Use above gerrit commits to prepare the LOCI images using following script:" +msgstr "" +"Gunakan komit gerrit di atas untuk menyiapkan image LOCI menggunakan skrip " +"berikut:" + +msgid "" +"Use it as ``docker build --build-arg PROJECT_REF=${REQUIREMENTS_REF_SPEC}`` " +"command argument to build the requirements LOCI image." +msgstr "" +"Gunakan sebagai argumen perintah ``docker build --build-arg PROJECT_REF=" +"${REQUIREMENTS_REF_SPEC}`` untuk membangun image LOCI persyaratan." + +msgid "Using Horizon as an example, find the ``endpoints`` config." +msgstr "" +"Dengan menggunakan Horizon sebagai contoh, cari konfigurasi ``endpoints``." + +msgid "" +"Using the Helm packages previously pushed to the local Helm repository, run " +"the following commands to instruct tiller to create an instance of the given " +"chart. During installation, the helm client will print useful information " +"about resources created, the state of the Helm releases, and whether any " +"additional configuration steps are necessary." +msgstr "" +"Dengan menggunakan paket Helm yang sebelumnya didorong ke repositori Helm " +"setempat, jalankan perintah berikut untuk menginstruksikan tiller untuk " +"membuat instance dari chart yang diberikan. Selama instalasi, klien helm " +"akan mencetak informasi yang berguna tentang sumber daya yang dibuat, " +"keadaan rilis Helm, dan berbagai langkah konfigurasi tambahan diperlukan." + +msgid "Verify the *v1beta1/Ingress* resource has a Host with your FQDN value" +msgstr "" +"Verifikasi sumber daya *v1beta1/Ingress* memiliki Host dengan nilai FQDN Anda" + +msgid "" +"We are going to install Ceph OSDs backed by loopback devices as this will " +"help us not to attach extra disks, in case if you have enough disks on the " +"node then feel free to skip creating loopback devices by exporting " +"CREATE_LOOPBACK_DEVICES_FOR_CEPH to false and export the block devices " +"names as environment variables(CEPH_OSD_DATA_DEVICE and " +"CEPH_OSD_DB_WAL_DEVICE)." +msgstr "" +"Kami akan menginstal OSD Ceph yang didukung oleh perangkat loopback karena " +"ini akan membantu kami untuk tidak memasang disk tambahan, jika Anda " +"memiliki cukup disk pada node, silakan lewati pembuatan perangkat loopback " +"dengan mengekspor CREATE_LOOPBACK_DEVICES_FOR_CEPH ke false dan mengekspor " +"perangkat blok nama sebagai variabel lingkungan (CEPH_OSD_DATA_DEVICE dan " +"CEPH_OSD_DB_WAL_DEVICE)." + +msgid "" +"We want to change the **public** configurations to match our DNS layouts " +"above. In each Chart ``values.yaml`` is a ``endpoints`` configuration that " +"has ``host_fqdn_override``'s for each API that the Chart either produces or " +"is dependent on. `Read more about how Endpoints are developed `__. 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 `__. Catatan sementara Glance Registry sedang mendengarkan " +"pada endpoint http Ingress, Anda tidak perlu mengekspos registri untuk " +"layanan eksternal." + +msgid "" +"While deploying neutron-server and L2 agents, TaaS should be enabled in " +"``conf: neutron`` section to add TaaS as a service plugin; in ``conf: " +"plugins`` section to add TaaS as a L2 agent extension; in ``conf: " +"taas_plugin`` section to configure the ``service_provider`` endpoint used by " +"Neutron TaaS plugin:" +msgstr "" +"Saat menggunakan neutron-server dan agen L2, TaaS harus diaktifkan di bagian " +"``conf: neutron`` untuk menambahkan TaaS sebagai plugin layanan; di bagian " +"`` conf: plugins`` untuk menambahkan TaaS sebagai ekstensi agen L2; di " +"bagian ``conf: taas_plugin`` untuk mengkonfigurasi endpoint " +"``service_provider`` yang digunakan oleh plugin Neutron TaaS:" + +msgid "" +"You can use any Kubernetes deployment tool to bring up a working Kubernetes " +"cluster for use with OpenStack-Helm. For production deployments, please " +"choose (and tune appropriately) a highly-resilient Kubernetes distribution, " +"e.g.:" +msgstr "" +"Anda dapat menggunakan alat penyebaran Kubernetes untuk memunculkan kluster " +"Kubernetes yang berfungsi untuk digunakan dengan OpenStack-Helm. Untuk " +"penyebaran produksi, pilih (dan selaraskan dengan tepat) distribusi " +"Kubernetes yang sangat tangguh (highly-resilient), misalnya:" + +msgid "" +"You can use any Kubernetes deployment tool to bring up a working Kubernetes " +"cluster for use with OpenStack-Helm. This guide describes how to simply " +"stand up a multinode Kubernetes cluster via the OpenStack-Helm gate scripts, " +"which use KubeADM and Ansible. Although this cluster won't be production-" +"grade, it will serve as a quick starting point in a lab or proof-of-concept " +"environment." +msgstr "" +"Anda dapat menggunakan alat penyebaran Kubernetes untuk memunculkan klaster " +"Kubernetes yang berfungsi untuk digunakan dengan OpenStack-Helm. Panduan ini " +"menjelaskan cara untuk hanya berdiri multinode Kubernetes klaster melalui " +"skrip gate OpenStack-Helm, yang menggunakan KubeADM dan Ansible. Meskipun " +"klaster ini tidak akan menjadi kelas produksi (production-grade), ini akan " +"berfungsi sebagai titik awal yang cepat di laboratorium atau lingkungan " +"proof-of-concept." + +msgid "" +"You may now deploy kubernetes, and helm onto your machine, first move into " +"the ``openstack-helm`` directory and then run the following:" +msgstr "" +"Anda sekarang dapat menyebarkan kubernetes, dan helm ke komputer Anda, " +"pertama-tama masuk ke direktori ``openstack-helm`` dan kemudian jalankan " +"yang berikut:" + +msgid "" +"Your changes to `/etc/environment` will not be applied until you source them:" +msgstr "" +"Perubahan Anda ke `/etc/environment` tidak akan diterapkan sampai Anda " +"sumbernya:" + +msgid "" +"`Airship `_, a declarative open cloud infrastructure " +"platform" +msgstr "" +"`Airship `_, platform infrastruktur cloud terbuka " +"deklaratif" + +msgid "" +"`KubeADM `_, the foundation of a number of Kubernetes installation solutions" +msgstr "" +"`KubeADM `_, fondasi sejumlah solusi instalasi Kubernetes" + +msgid "https://review.openstack.org/#/c/597200/" +msgstr "https://review.openstack.org/#/c/597200/" + +msgid "https://review.openstack.org/#/c/607392/" +msgstr "https://review.openstack.org/#/c/607392/" + +msgid "https://review.openstack.org/#/c/621606/" +msgstr "https://review.openstack.org/#/c/621606/" + +msgid "hugepages have been allocated on NUMA socket 1 by OVS, and" +msgstr "hugepage telah dialokasikan pada NUMA socket 1 oleh OVS, dan" + +msgid "" +"if you are rerunning the below script then make sure to skip the loopback " +"device creation by exporting CREATE_LOOPBACK_DEVICES_FOR_CEPH to false." +msgstr "" +"jika Anda menjalankan ulang skrip di bawah ini, pastikan untuk melewati " +"pembuatan perangkat loopback dengan mengekspor " +"CREATE_LOOPBACK_DEVICES_FOR_CEPH ke false." + +msgid "" +"node_one, node_two and node_three below are all worker nodes, children of " +"the master node that the commands below are executed on." +msgstr "" +"node_one, node_two dan node_three di bawah ini adalah semua node pekerja " +"(worker node), anak-anak (children) dari node master dimana perintah di " +"bawah ini dieksekusi." diff --git a/doc/source/locale/id/LC_MESSAGES/doc-specs.po b/doc/source/locale/id/LC_MESSAGES/doc-specs.po new file mode 100644 index 0000000000..16a599b8c1 --- /dev/null +++ b/doc/source/locale/id/LC_MESSAGES/doc-specs.po @@ -0,0 +1,2861 @@ +# suhartono , 2019. #zanata +msgid "" +msgstr "" +"Project-Id-Version: openstack-helm 0.1.1.dev3685\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2022-04-06 21:47+0000\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"PO-Revision-Date: 2019-05-27 04:14+0000\n" +"Last-Translator: suhartono \n" +"Language-Team: Indonesian\n" +"Language: id\n" +"X-Generator: Zanata 4.3.3\n" +"Plural-Forms: nplurals=1; plural=0\n" + +msgid "**Charts in the appropriate project**" +msgstr "**Charts in the appropriate project**" + +msgid "**Combined helm-toolkit**" +msgstr "**Combined helm-toolkit**" + +msgid "**Document Kubernetes requirements**" +msgstr "**Document Kubernetes requirements**" + +msgid "**Document version requirements**" +msgstr "**Document version requirements**" + +msgid "**Helm test for all charts**" +msgstr "**Helm test for all charts**" + +msgid "**Inclusion of all core services**" +msgstr "**Inclusion of all core services**" + +msgid "**LMA Operations Guide**" +msgstr "**LMA Operations Guide**" + +msgid "**OpenStack-Helm release process**" +msgstr "**OpenStack-Helm release process**" + +msgid "**Release notes**" +msgstr "**Release notes**" + +msgid "**Resiliency across reboots**" +msgstr "**Resiliency across reboots**" + +msgid "**Split Ceph chart**" +msgstr "**Split Ceph chart**" + +msgid "**Standardization of manifests**" +msgstr "**Standardization of manifests**" + +msgid "**Standardization of values**" +msgstr "**Standardization of values**" + +msgid "**Upgrades**" +msgstr "**Upgrades**" + +msgid "**Values-driven config files**" +msgstr "**Values-driven config files**" + +msgid "1) Prepare scripts:" +msgstr "1) Siapkan skrip:" + +msgid "" +"1. For each chart, add a new entry ``oci_image_registry:`` under ``endpoints:" +"`` in ``values.yaml``. The entry ``oci_image_registry:`` has the ``auth:`` " +"section which provides the credentials for accessing registry images and an " +"option ``enabled:`` to determine whether images authentication is required " +"or not. The registry basic information would also be included for generating " +"the registry URL by the endpoint lookup functions. Also add a new entry " +"``oci_image_registry:`` under ``secrets:`` to indicate the secret name. In " +"order to create the secret that holds the provided credentials, add a new " +"component ``secret_registry`` in ``manifests:`` section. For example:" +msgstr "" +"1. Untuk setiap chart, tambahkan entri baru ``oci_image_registry:`` di bawah " +"``endpoints:`` di ``values.yaml``. Entri ``oci_image_registry:`` memiliki " +"bagian ``auth:`` yang menyediakan kredensial untuk mengakses image registri " +"dan opsi ``enabled:`` untuk menentukan apakah otentikasi image diperlukan " +"atau tidak. Informasi dasar registri juga akan dimasukkan untuk menghasilkan " +"URL registri oleh fungsi pencarian endpoint. Juga tambahkan entri baru " +"``oci_image_registry:`` di bawah ``secrets:`` untuk menunjukkan nama " +"rahasia. Untuk membuat rahasia yang memegang kredensial yang disediakan, " +"tambahkan komponen baru ``secret_registry`` di bagian ``manifes:``. Sebagai " +"contoh:" + +msgid "2 Replace occurrence of ``ceph.yaml`` with ``tenant-ceph.yaml``" +msgstr "2 Ganti kemunculan ``ceph.yaml`` dengan ``tenant-ceph.yaml``" + +msgid "2) Deploy ingress chart:" +msgstr "2) Menyebarkan ingress chart:" + +msgid "" +"3 For tenant Ceph, no need to deploy ceph-provisioners. Update script to " +"``for CHART in ceph-mon ceph-osd ceph-client; do``" +msgstr "" +"3 untuk tenant Ceph, tidak perlu menggunakan ceph-provisioners. Update skrip " +"ke ``for CHART in ceph-mon ceph-osd ceph-client; do``" + +msgid "3) Deploy Ceph for RBD:" +msgstr "3) Menyebarkan Ceph untuk RBD:" + +msgid "4) Deploy MariaDB, RabbitMQ, Memcached and Keystone:" +msgstr "4) Menyebarkan MariaDB, RabbitMQ, Memcached dan Keystone:" + +msgid "5) Deploy Ceph for Tenant:" +msgstr "5) Menyebarkan Ceph untuk Tenant:" + +msgid "6 VM based hosts (node1, node2, node3, node4, node5, node6)" +msgstr "6 VM based hosts (node1, node2, node3, node4, node5, node6)" + +msgid "6) Enable Openstack namespace to use Tenant Ceph:" +msgstr "6) Aktifkan Openstack namespace untuk menggunakan Tenant Ceph:" + +msgid "7) Tenant Ceph: Deploy Rados Gateway:" +msgstr "7) Tenant Ceph: Deploy Rados Gateway:" + +msgid "8) Deploy Glance:" +msgstr "8) Menyebarkan Glance:" + +msgid "9) Deploy Cinder:" +msgstr "9) Menyebarkan Cinder:" + +msgid "" +"A basic Logging, Monitoring, and Alerting-oriented operations guide must be " +"in place, illustrating for operators (and developers) how to set up and use " +"an example LMA setup for OpenStack and supporting services. It will include " +"instructions on how to perform basic configuration and how to access and use " +"the user interfaces at a high level. It will also link out to more detailed " +"documentation for the LMA tooling itself." +msgstr "" +"Panduan operasi Logging, Monitoring, dan Alerting-oriented dasar harus ada, " +"menggambarkan bagi operator (dan pengembang) bagaimana mengatur dan " +"menggunakan contoh pengaturan LMA untuk OpenStack dan layanan pendukung. Ini " +"akan mencakup instruksi tentang cara melakukan konfigurasi dasar dan cara " +"mengakses dan menggunakan antarmuka pengguna di tingkat tinggi. Ini juga " +"akan menghubungkan ke dokumentasi yang lebih rinci untuk perkakas LMA itu " +"sendiri." + +msgid "" +"A few areas have been identified on changes required. Each of them will be a " +"work item." +msgstr "" +"Beberapa area telah diidentifikasi pada perubahan yang diperlukan. Masing-" +"masing akan menjadi work item." + +msgid "" +"A foundational requirement of 1.0 readiness is the presence of robust gating " +"that will ensure functionality, backward compatibility, and upgradeability. " +"This will allow development to continue and for support for new versions of " +"OpenStack to be added post-1.0. The following gating requirements must be " +"met:" +msgstr "" +"Persyaratan mendasar dari kesiapan 1.0 adalah keberadaan gating yang kuat " +"yang akan memastikan fungsionalitas, kompatibilitas mundur (backward " +"compatibility), dan peningkatan kemampuan. Ini akan memungkinkan " +"pengembangan untuk melanjutkan dan untuk dukungan untuk versi baru OpenStack " +"ditambahkan post-1.0. Persyaratan gating berikut harus dipenuhi:" + +msgid "" +"A gate will be added to OpenStack-Helm that runs through the developer " +"environment deployment process." +msgstr "" +"Gate akan ditambahkan ke OpenStack-Helm yang dijalankan melalui proses " +"penyebaran lingkungan pengembang." + +msgid "" +"A number of in-progress and planned development efforts must be completed " +"prior to 1.0, to ensure a stable OpenStack-Helm interface thereafter." +msgstr "" +"Sejumlah upaya pengembangan yang sedang berlangsung dan yang direncanakan " +"harus diselesaikan sebelum 1.0, untuk memastikan antarmuka OpenStack-Helm " +"yang stabil sesudahnya." + +msgid "" +"A set of scripts will be provided to exercise the deployed environment that " +"checks the basic functionality of the deployed cloud, driven where possible " +"via OpenStack heat:" +msgstr "" +"Seperangkat skrip akan disediakan untuk menjalankan lingkungan yang " +"digunakan yang memeriksa fungsi dasar cloud yang digunakan, didorong jika " +"memungkinkan melalui OpenStack heat:" + +msgid "" +"A specification should precede any broad-reaching technical changes or " +"proposals to OpenStack-Helm. Examples of changes requiring a specification " +"include: a standard format to the values.yaml files, multiple backend " +"support for neutron, and the approach for logging and monitoring in " +"OpenStack-Helm. Some additional features will not need an accompanying " +"specification, but may be tied back to an existing specification. An " +"example of this would be introducing a service in OpenStack-Helm that could " +"be included under the scope of a specification already drafted and approved." +msgstr "" +"Spesifikasi harus mendahului setiap perubahan teknis yang luas atau proposal " +"ke OpenStack-Helm. Contoh perubahan yang memerlukan spesifikasi meliputi: " +"format standar untuk file values.yaml, dukungan backend berganda untuk " +"neutron, dan pendekatan untuk logging dan pemantauan di OpenStack-Helm. " +"Beberapa fitur tambahan tidak memerlukan spesifikasi yang menyertainya, " +"tetapi mungkin terikat kembali ke spesifikasi yang ada. Contohnya adalah " +"memperkenalkan layanan di OpenStack-Helm yang dapat dimasukkan dalam lingkup " +"spesifikasi yang telah disusun dan disetujui." + +msgid "API Deployments" +msgstr "API Deployments" + +msgid "Ability to apply custom metadata and uniform format to logs" +msgstr "" +"Kemampuan untuk menerapkan metadata kustom dan format seragam untuk log" + +msgid "Ability to perform custom queries against metrics collected" +msgstr "" +"Kemampuan untuk melakukan kueri kustom terhadap metrik yang dikumpulkan" + +msgid "Ability to perform custom queries against stored logs" +msgstr "Kemampuan untuk melakukan kueri kustom terhadap log yang tersimpan" + +msgid "" +"Above output shows ``http://ceph-rgw.openstack.svc.cluster.local`` which " +"shows that swift is pointing to tenant-ceph." +msgstr "" +"Output di atas menunjukkan ``http://ceph-rgw.openstack.svc.cluster.local`` " +"yang menunjukkan bahwa swift menunjuk ke tenant-ceph." + +msgid "" +"Above output shows that tenant ceph now has 19 pools including one for " +"Cinder." +msgstr "" +"Output di atas menunjukkan bahwa tenant ceph sekarang memiliki 19 pool " +"termasuk satu untuk Cinder." + +msgid "Add Linux Bridge as first alternative for OVS - separate spec needed." +msgstr "" +"Tambahkan Linux Bridge sebagai alternatif pertama untuk OVS - spesifikasi " +"terpisah diperlukan." + +msgid "Add LinuxBridge daemonset" +msgstr "Tambahkan daemonset LinuxBridge" + +msgid "" +"Add a helm-toolkit function ``helm-toolkit.manifests.secret_registry`` to " +"create a manifest for secret generation. For example:" +msgstr "" +"Tambahkan fungsi helm-toolkit ``helm-toolkit.manifests.secret_registry`` " +"untuk membuat manifes untuk pembuatan rahasia. Sebagai contoh:" + +msgid "" +"Add a template highlighting the updated values ordering for use in chart " +"development" +msgstr "" +"Tambahkan template highlighting urutan nilai yang diperbarui untuk digunakan " +"dalam pengembangan chart" + +msgid "Add documentation on how to use LinuxBridge" +msgstr "Tambahkan dokumentasi tentang cara menggunakan LinuxBridge" + +msgid "Add gate for developer environment" +msgstr "Tambahkan gate untuk lingkungan pengembang" + +msgid "Add gate job testing VM network connectivity" +msgstr "Tambahkan gate job testing konektivitas jaringan VM" + +msgid "" +"Add one SDN to see if proposed change is working OK - separate spec needed." +msgstr "" +"Tambahkan satu SDN untuk melihat apakah perubahan yang diajukan berfungsi " +"dengan baik - pisahkan spesifikasi yang diperlukan." + +msgid "Add or remove nodes depending on utilization" +msgstr "Tambah atau hapus node tergantung pada pemanfaatan" + +msgid "Additional assignees TBD" +msgstr "Additional assignees TBD" + +msgid "" +"Aggregator also send aggregated logs to Kafka for external tools to consume" +msgstr "" +"Aggregator juga mengirim log agregat ke Kafka untuk dikonsumsi oleh alat " +"eksternal" + +msgid "Alerting capabilities to notify operators when thresholds exceeded" +msgstr "" +"Memperingatkan kemampuan untuk memberi tahu operator ketika ambang melebihi" + +msgid "Alertmanager chart" +msgstr "Alertmanager chart" + +msgid "" +"All charts must include sensible configuration values to make the monitoring " +"platform usable by default. These include: static Prometheus " +"configurations for the included exporters, static dashboards for Grafana " +"mounted via configMaps and configurations for Alertmanager out of the box." +msgstr "" +"Semua chart harus menyertakan nilai konfigurasi yang masuk akal untuk " +"membuat platform pemantauan dapat digunakan secara default. Ini termasuk: " +"konfigurasi statis Prometheus untuk eksportir yang disertakan, dasbor statis " +"untuk Grafana yang dipasang melalui configMaps dan konfigurasi untuk " +"Alertmanager di luar kotak." + +msgid "" +"All charts require valid and sensible default values to provide operational " +"value out of the box." +msgstr "" +"Semua chart memerlukan nilai default yang valid dan masuk akal untuk " +"memberikan nilai operasional di luar kotak." + +msgid "" +"All charts should follow design approaches applied to all other OpenStack-" +"Helm charts, including the use of helm-toolkit." +msgstr "" +"Semua chart harus mengikuti pendekatan desain yang diterapkan pada semua " +"chart OpenStack-Helm lainnya, termasuk penggunaan helm-toolkit." + +msgid "All charts should migrate to their appropriate home project as follows:" +msgstr "" +"Semua chart harus bermigrasi ke home project yang sesuai sebagai berikut:" + +msgid "" +"All keys under top-level keys are listed in alphabetical order, with the " +"exception of the conf key. As some configuration files require a strict " +"ordering of their content, excluding this key from any alphabetical " +"organization is required." +msgstr "" +"Semua kunci di bawah top-level keys terdaftar dalam urutan abjad, dengan " +"pengecualian kunci conf. Karena beberapa file konfigurasi memerlukan urutan " +"konten yang ketat, tidak termasuk kunci ini dari organisasi alfabet apa pun " +"diperlukan." + +msgid "All services in OpenStack-Helm log to stdout and stderr by default" +msgstr "" +"Semua layanan di OpenStack-Helm log ke stdout dan stderr secara default" + +msgid "" +"All services running within the platform should be subject to the security " +"practices applied to the other OpenStack-Helm charts." +msgstr "" +"Semua layanan yang berjalan dalam platform harus tunduk pada praktik " +"keamanan yang diterapkan pada grafik OpenStack-Helm lainnya." + +msgid "" +"All services should survive node reboots, and their functionality validated " +"following a reboot by a gate." +msgstr "" +"Semua layanan harus selamat dari reboot node, dan fungsinya divalidasi " +"setelah reboot oleh gate." + +msgid "" +"All three charts must include sensible configuration values to make the " +"logging platform usable by default. These include: proper input " +"configurations for Fluentd, proper metadata and formats applied to the logs " +"via Fluentd, sensible indexes created for Elasticsearch, and proper " +"configuration values for Kibana to query the Elasticsearch indexes " +"previously created." +msgstr "" +"Ketiga grafik harus menyertakan nilai konfigurasi yang masuk akal untuk " +"membuat platform logging dapat digunakan secara default. Ini termasuk: " +"konfigurasi input yang tepat untuk Fluentd, metadata yang tepat dan format " +"yang diterapkan pada log melalui Fluentd, indeks yang masuk akal yang dibuat " +"untuk Elasticsearch, dan nilai konfigurasi yang tepat untuk Kibana untuk " +"menanyakan indeks Elasticsearch yang sebelumnya dibuat." + +msgid "Allow the usage of multiple base images in OSH." +msgstr "Izinkan penggunaan beberapa image dasar dalam OSH." + +msgid "" +"Allows different profiles of apache, should some charts require different " +"args for example for the same kind of images, by using yaml dict merges " +"features." +msgstr "" +"Mengizinkan profil apache yang berbeda, jika beberapa bagan memerlukan " +"argumen yang berbeda misalnya untuk jenis image yang sama, dengan " +"menggunakan fitur penggabungan dict yaml." + +msgid "" +"Alter webserver configuration per distro. Different distros have different " +"expectations in terms of path (including a different series of files " +"required), and it would make the operators' life easier by using their " +"expected distro paths." +msgstr "" +"Ubah konfigurasi server web per distro. Distro yang berbeda memiliki harapan " +"yang berbeda dalam hal path (termasuk serangkaian file yang berbeda " +"diperlukan), dan itu akan membuat hidup para operator lebih mudah dengan " +"menggunakan path distro yang mereka harapkan." + +msgid "Alternatives" +msgstr "Alternatif" + +msgid "" +"Alternatives to decomposable Neutron chart would be to copy whole Neutron " +"chart and create spin-offs with new SDN enabled. This approach has drawbacks " +"of maintaining the whole neutron chart in many places, and copies of " +"standard services may be out of sync with OSH improvements. This implies " +"constant maintenance effort to up to date." +msgstr "" +"Alternatif untuk chart Neutron terurai (decomposable) adalah menyalin " +"seluruh chart Neutron dan membuat spin-off dengan SDN baru diaktifkan. " +"Pendekatan ini memiliki kelemahan dalam mempertahankan bagan neutron " +"keseluruhan di banyak tempat, dan salinan layanan standar mungkin tidak " +"selaras dengan perbaikan OSH. Ini menyiratkan upaya pemeliharaan yang " +"konstan hingga terbaru." + +msgid "Angie Wang (angiewang)" +msgstr "Angie Wang (angiewang)" + +msgid "" +"Another place where Neutron L2 agent should be pointed is dependencies list " +"in other OpenStack projects. Currently, :code:`nova-compute` has dependency " +"for :code:`ovs-agent` in :code:`nova/values.yaml`, it should be changed to:" +msgstr "" +"Tempat lain di mana agen L2 Neutron harus ditunjuk adalah daftar dependensi " +"dalam proyek OpenStack lainnya. Saat ini, :code:`nova-compute` memiliki " +"ketergantungan untuk :code:`ovs-agent` dalam :code:`nova/values.yaml`, " +"harus diubah menjadi:" + +msgid "Any other changes to the external interface of OpenStack-Helm" +msgstr "Perubahan lain apa pun pada antarmuka eksternal OpenStack-Helm" + +msgid "" +"As mentioned before, configuration of L3/DHCP/metadata agent should be " +"adjusted to use LinuxBridge, sample configuration override:" +msgstr "" +"Seperti disebutkan sebelumnya, konfigurasi agen L3/DHCP/metadata harus " +"disesuaikan untuk menggunakan LinuxBridge, konfigurasi sampel diganti:" + +msgid "Assign Floating IP to VM" +msgstr "Tetapkan IP Mengambang (Floating IP) ke VM" + +msgid "Assignee(s)" +msgstr "Assignee(s)" + +msgid "" +"At this point, curated scripts will be used to deploy OpenStack-Helm " +"services on demand as desired, with documentation provided to allow a new " +"developer to quickly set up either a single or multimode deployment of a " +"reference `OpenStack Compute Kit `_ environment with the addition of:" +msgstr "" +"Pada titik ini, skrip yang dikurasi (curated) akan digunakan untuk " +"menggunakan layanan OpenStack-Helm sesuai permintaan seperti yang " +"diinginkan, dengan dokumentasi yang disediakan untuk memungkinkan pengembang " +"baru dengan cepat mengatur penyebaran tunggal atau multimode dari referensi " +"`OpenStack Compute Kit `_ lingkungan dengan penambahan:" + +msgid "" +"Authentication should be enabled for normal users to access Kube API server " +"via either kubectl command or kube REST API call." +msgstr "" +"Otentikasi harus diaktifkan untuk pengguna normal untuk mengakses server API " +"Kube melalui perintah kubectl atau panggilan API REST kube." + +msgid "Backed by highly available storage" +msgstr "Didukung oleh penyimpanan yang sangat tersedia" + +msgid "" +"Before drafting a specification, a blueprint should be filed in Storyboard_ " +"along with any dependencies the blueprint requires. Once the blueprint has " +"been registered, submit the specification as a patch set to the specs/ " +"directory using the supplied template." +msgstr "" +"Sebelum menyusun spesifikasi, blueprint harus diajukan di Storyboard_ " +"bersama dengan setiap dependensi yang diperlukan blueprint. Setelah " +"blueprint terdaftar, kirimkan spesifikasi sebagai patch yang disetel ke " +"direktori spesifikasi menggunakan templat yang disediakan." + +msgid "Before using Openstack-Helm to deploy openstack services," +msgstr "" +"Sebelum menggunakan Openstack-Helm untuk menggunakan layanan openstack," + +msgid "Bin ConfigMaps" +msgstr "Bin ConfigMaps" + +msgid "" +"Blueprint: https://blueprints.launchpad.net/openstack-helm/+spec/nginx-" +"sidecar" +msgstr "" +"Blueprint: https://blueprints.launchpad.net/openstack-helm/+spec/nginx-" +"sidecar" + +msgid "Blueprint: neutron-multiple-sdns_" +msgstr "Blueprint: neutron-multiple-sdns_" + +msgid "Blueprint: support-linux-bridge-on-neutron_" +msgstr "Blueprint: support-linux-bridge-on-neutron_" + +msgid "Blueprint: support-oci-image-registry-with-authentication-turned-on_" +msgstr "Blueprint: support-oci-image-registry-with-authentication-turned-on_" + +msgid "Blueprints: 1. osh-logging-framework_" +msgstr "Cetak Biru: 1. osh-logging-framework_" + +msgid "Blueprints: 1. osh-monitoring_ 2. osh-logging-framework_" +msgstr "Blueprints: 1. osh-monitoring_ 2. osh-logging-framework_" + +msgid "" +"But above alternatives have limitations and security impact. i.e...require " +"root access to configure on all nodes, all pods can read any configured " +"private registries, all pods can use any images cached on a node [1]_" +msgstr "" +"Tetapi alternatif di atas memiliki keterbatasan dan dampak keamanan. i.e ... " +"memerlukan akses root untuk mengkonfigurasi pada semua node, semua pod dapat " +"membaca register pribadi yang dikonfigurasi, semua pod dapat menggunakan " +"image apa pun yang di-cache pada sebuah node [1] _" + +msgid "" +"By default, :code:`daemonset_lb_agent` will be set to false to remain " +"default behaviour of installing OVS as networking agent." +msgstr "" +"Secara default, :code:`daemonset_lb_agent` akan disetel ke false untuk tetap " +"menjadi perilaku default menginstal OVS sebagai agen jaringan." + +msgid "Ceph Clusters:" +msgstr "Ceph Clusters:" + +msgid "Ceph backed Block Storage (cinder)" +msgstr "Object Storage (cinder) yang didukung Ceph" + +msgid "Ceph backed Object Storage" +msgstr "Object Storage yang didukung Ceph" + +msgid "Ceph for RBD:" +msgstr "Ceph for RBD:" + +msgid "Ceph for Tenant:" +msgstr "Ceph untuk Tenant:" + +msgid "Ceph metrics: total pool usage, latency, health, etc" +msgstr "Metrik Ceph: total penggunaan pool, latensi, kesehatan, dll" + +msgid "" +"Change ordering of keys across all charts in openstack-helm, openstack-helm-" +"infra, and openstack-helm-addons" +msgstr "" +"Ubah urutan kunci di semua chart di openstack-helm, openstack-helm-infra, " +"dan openstack-helm-addons" + +msgid "" +"Charts for all core OpenStack services must be present to achieve 1.0 " +"releasability. The only core service outstanding at this time is Swift." +msgstr "" +"Chart untuk semua layanan OpenStack inti harus ada untuk mencapai 1.0 " +"releasability. Satu-satunya layanan inti yang beredar saat ini adalah Swift." + +msgid "" +"Charts for exporters: kube-state-metrics, ceph-exporter, openstack-exporter?" +msgstr "" +"Chart untuk eksportir: kube-state-metrics, ceph-exporter, openstack-exporter?" + +msgid "Code Completion and Refactoring" +msgstr "Code Completion dan Refactoring" + +msgid "Collect logs from the node by Fluentbit" +msgstr "Kumpulkan log dari node dengan Fluentbit" + +msgid "Common method to configure all monitoring targets" +msgstr "Metode umum untuk mengonfigurasi semua target pemantauan" + +msgid "" +"Comprehensive documentation is key to the ability for real-world operators " +"to benefit from OpenStack-Helm, and so it is a requirement for 1.0 " +"releasability. The following outstanding items must be completed from a " +"documentation perspective:" +msgstr "" +"Dokumentasi yang komprehensif adalah kunci kemampuan operator real-world " +"untuk mendapatkan manfaat dari OpenStack-Helm, dan karenanya merupakan " +"persyaratan untuk 1.0 releasability. Barang luar biasa (outstanding) berikut " +"harus diselesaikan dari perspektif dokumentasi:" + +msgid "Configurable log rotation mechanism" +msgstr "Mekanisme rotasi log yang dapat dikonfigurasi" + +msgid "Configuration in :code:`neutron.conf` and :code:`ml2_conf.ini`" +msgstr "Konfigurasi dalam :code:`neutron.conf` and :code:`ml2_conf.ini`" + +msgid "" +"Cover the following logging use cases https://review.openstack.org/#/" +"c/482687/" +msgstr "" +"Cover kasus penggunaan logging berikut https://review.openstack.org/#/" +"c/482687/" + +msgid "Create SSH Key in nova" +msgstr "Buat SSH Key di nova" + +msgid "Create VM on tenant network" +msgstr "Buat VM di jaringan tenant" + +msgid "" +"Create conditionals in the helm charts. This is problematic, as the amount " +"of conditionals will increase and will be harder to maintain. Overrides " +"files are easy to sync between charts." +msgstr "" +"Buat persyaratan di helm chart. Ini bermasalah, karena jumlah persyaratan " +"akan meningkat dan akan lebih sulit untuk dipertahankan. File yang di-" +"overrided mudah disinkronkan di antara chart." + +msgid "Create external network" +msgstr "Buat jaringan eksternal" + +msgid "Create tenant network" +msgstr " Buat jaringan penyewa (tenant)" + +msgid "Create tenant router to link tenant network and external" +msgstr "Buat router tenant untuk menghubungkan jaringan tenant dan eksternal" + +msgid "CronJobs" +msgstr "CronJobs" + +msgid "" +"Currently OpenStack-Helm supports OpenVSwitch as a network virtualization " +"engine. In order to support many possible backends (SDNs), changes are " +"required in neutron chart and in deployment techniques. OpenStack-Helm can " +"support every SDN solution that has Neutron plugin, either core_plugin or " +"mechanism_driver." +msgstr "" +"Saat ini OpenStack-Helm mendukung OpenVSwitch sebagai mesin virtualisasi " +"jaringan. Untuk mendukung banyak kemungkinan backend (SDNs), perubahan " +"diperlukan dalam chart neutron dan teknik penyebaran. OpenStack-Helm dapat " +"mendukung setiap solusi SDN yang memiliki plugin Neutron, baik core_plugin " +"atau mechanism_driver" + +msgid "" +"Currently both OpenStack-Helm and OpenStack-Helm-Infra have their own " +"parallel versions of the Helm-Toolkit library chart. They must be combined " +"into a single chart in OpenStack-Helm-Infra prior to 1.0." +msgstr "" +"Saat ini baik OpenStack-Helm dan OpenStack-Helm-Infra memiliki versi paralel " +"mereka sendiri dari chart pustaka Helm-Toolkit. Mereka harus digabungkan " +"menjadi satu chart tunggal di OpenStack-Helm-Infra sebelum 1.0." + +msgid "DHCP - auto-assign IP address and DNS info" +msgstr "DHCP - auto-assign IP address dan DNS info" + +msgid "Database drop Job" +msgstr "Database drop Job" + +msgid "Deploy Kubernetes via KubeADM, with charts for CNI and DNS services" +msgstr "" +"Menyebarkan Kubernet melalui KubeADM, dengan grafik untuk layanan CNI dan DNS" + +msgid "Deploying multuple Ceph clusters" +msgstr "Menyebarkan multiple cluster Ceph" + +msgid "" +"Develop scripts for bringing up OpenStack-Helm Charts and perform basic " +"interactive tests" +msgstr "" +"Kembangkan skrip untuk memunculkan OpenStack-Helm Charts dan melakukan tes " +"interaktif dasar" + +msgid "Developer Environment" +msgstr "Lingkungan Pengembang" + +msgid "" +"Developers require a simple way of instantiating a working environment for " +"OpenStack-Helm, that allows them to quickly begin development of the " +"project. This is more complex to achieve than many OpenStack Projects that " +"can simply rely upon a devstack plugin to achieve this. This is as OpenStack-" +"Helm is focused on the deployment of OpenStack (and associated) Projects, " +"rather than the development of the projects themselves, and also requires " +"additional supporting infrastructure, e.g. Kubernetes and a CNI." +msgstr "" +"Pengembang membutuhkan cara sederhana untuk membuat contoh lingkungan kerja " +"OpenStack-Helm, yang memungkinkan mereka untuk dengan cepat memulai " +"pengembangan proyek. Ini lebih kompleks untuk dicapai daripada banyak " +"OpenStack Project yang hanya dapat mengandalkan plugin devstack untuk " +"mencapai ini. Ini karena OpenStack-Helm berfokus pada penyebaran OpenStack " +"Project (dan yang terkait), daripada pengembangan proyek itu sendiri, dan " +"juga membutuhkan infrastruktur pendukung tambahan, misal Kubernetes dan CNI." + +msgid "Development of OpenStack-Helm" +msgstr "Perkembangan OpenStack-Helm" + +msgid "Documentation" +msgstr "Dokumentasi" + +msgid "Documentation Impact" +msgstr "Dampak Dokumentasi" + +msgid "" +"Documentation of how new SDN can be enabled, how Neutron should be " +"configured. Also, for each new SDN that would be incorporated, the " +"architecture overview should be provided." +msgstr "" +"Dokumentasi tentang bagaimana SDN baru dapat diaktifkan, bagaimana Neutron " +"harus dikonfigurasi. Juga, untuk setiap SDN baru yang akan dimasukkan, " +"tinjauan arsitektur harus disediakan." + +msgid "Documentation of how to enable the registry secret generation" +msgstr "Dokumentasi cara mengaktifkan pembuatan rahasia registri" + +msgid "Documentation on how to use LinuxBridge with Neutron chart." +msgstr "Dokumentasi tentang cara menggunakan LinuxBridge dengan chart Neutron." + +msgid "" +"Documentation should be included for each of the included charts as well as " +"documentation detailing the requirements for a usable monitoring platform, " +"preferably with sane default values out of the box." +msgstr "" +"Dokumentasi harus disertakan untuk masing-masing grafik termasuk juga " +"dokumentasi yang merinci persyaratan untuk platform pemantauan yang dapat " +"digunakan, lebih disukai dengan default values out of the box yang masuk " +"akal." + +msgid "Duplicate scripts as shows below for later use." +msgstr "" +"Duplikat skrip seperti yang ditunjukkan di bawah ini untuk digunakan nanti." + +msgid "" +"Dynamically alter webserver environment conditionally in the helm chart. For " +"example, for apache, ensure the necessary modules to run openstack are " +"available and loaded at helm chart deploy time. This will leverage the " +"binaries listed in ``values.yaml``. These series of commands are " +"distribution/image dependent, as commands to list modules to load might " +"differ. However with a few parameters, we can get a very distro independent " +"process which would allow us to load all the required apache modules." +msgstr "" +"Secara dinamis mengubah lingkungan server web secara kondisional di helm " +"chart. Sebagai contoh, untuk apache, pastikan modul yang diperlukan untuk " +"menjalankan openstack tersedia dan dimuat pada waktu penggelaran helm chart. " +"Ini akan memanfaatkan binari yang terdaftar di ``values.yaml``. Rangkaian " +"perintah ini bergantung pada distribution/image, karena perintah untuk " +"mendaftar modul yang akan dimuat mungkin berbeda. Namun dengan beberapa " +"parameter, kita bisa mendapatkan proses independen distro yang memungkinkan " +"kita memuat semua modul apache yang diperlukan." + +msgid "" +"Each chart's values.yaml file contains various settings such as docker image " +"definition, chart structure setting, form of the resources being " +"distributed, and process configuration. Currently, the structure of the " +"yaml file is complicated, and finding keys between charts proves difficult " +"due to the lack of uniform values organization across charts." +msgstr "" +"Setiap file values.yaml chart berisi berbagai pengaturan seperti definisi " +"docker image, pengaturan struktur chart, bentuk sumber daya yang " +"didistribusikan, dan konfigurasi proses. Saat ini, struktur file yaml rumit, " +"dan menemukan kunci di antara chart terbukti sulit karena kurangnya nilai " +"seragam organisasi di seluruh chart." + +msgid "" +"Edit all helm charts to remove possible references to image specific " +"elements, replacing them with values overrides or conditionals." +msgstr "" +"Edit semua bagan helm untuk menghapus referensi yang mungkin untuk elemen " +"spesifik image, override dengan nilai yang menimpa atau kondisional." + +msgid "Elasticsearch chart" +msgstr "Elasticsearch chart" + +msgid "" +"Elasticsearch configured in a highly available manner with sane defaults" +msgstr "" +"Elasticsearch dikonfigurasi dengan cara yang sangat tersedia dengan standar " +"yang masuk akal" + +msgid "Elasticsearch configured to prevent memory swapping to disk" +msgstr "Elasticsearch dikonfigurasi untuk mencegah pertukaran memori ke disk" + +msgid "Env Setup:" +msgstr "Env Setup:" + +msgid "Etc ConfigMaps" +msgstr "Etc ConfigMaps" + +msgid "Every Fluentbit send logs to Fluentd with Kubernetes metadata attached" +msgstr "" +"Setiap Fluentbit mengirim log ke Fluentd dengan metadata Kubernetes terlampir" + +msgid "" +"Every Kubernetes manifest inside Neutron chart can be enabled or disabled. " +"That would provide flexibility to the operator, to choose which Neutron " +"components are reusable with different type of SDNs. For example, neutron-" +"server which is serving the API and configuring the database can be used " +"with different types of SDN plugin, and provider of that SDN chart would not " +"need to copy all logic from Neutron base chart to manage the API and " +"database." +msgstr "" +"Setiap manifes Kubernet dalam chart Neutron dapat diaktifkan atau " +"dinonaktifkan. Itu akan memberikan fleksibilitas kepada operator, untuk " +"memilih komponen Neutron mana yang dapat digunakan kembali dengan berbagai " +"jenis SDN. Misalnya, server neutron yang melayani API dan mengonfigurasi " +"basis data dapat digunakan dengan berbagai jenis plugin SDN, dan penyedia " +"chart SDN itu tidak perlu menyalin semua logika dari chart dasar Neutron " +"untuk mengelola API dan basis data." + +msgid "Example OpenStack-Helm metrics requiring monitoring include:" +msgstr "Contoh metrik OpenStack-Helm yang membutuhkan pemantauan meliputi:" + +msgid "Example uses for centralized logging include:" +msgstr "Contoh penggunaan untuk logging terpusat meliputi:" + +msgid "" +"Example uses for centralized logging with Fluentbit and Fluentd include:" +msgstr "" +"Contoh penggunaan untuk logging terpusat dengan Fluentbit dan Fluentd " +"meliputi:" + +msgid "Examples of how these metrics can be used include:" +msgstr "Contoh bagaimana metrik ini dapat digunakan meliputi:" + +msgid "" +"Examples of how to set up the above under KubeADM and KubeSpray-based " +"clusters must be documented as well." +msgstr "" +"Contoh cara mengatur di atas di bawah KubeADM dan cluster berbasis KubeSpray " +"harus didokumentasikan juga." + +msgid "Execute script" +msgstr "Jalankan skrip" + +msgid "Execute script." +msgstr "Jalankan skrip." + +msgid "" +"Exposes security/configuration features of software, allowing deployers to " +"configure software to their needs." +msgstr "" +"Mengekspos fitur security/configuration perangkat lunak, memungkinkan " +"penyebar untuk mengkonfigurasi perangkat lunak sesuai kebutuhan mereka." + +msgid "External charts (Calico)" +msgstr "External charts (Calico)" + +msgid "Find all backtraces for a tenant id's uuid" +msgstr "Temukan semua backtraces untuk uuid id penyewa" + +msgid "" +"Find all logged events that match a pattern (service, pod, behavior, etc)" +msgstr "" +"Temukan semua peristiwa yang dicatat yang cocok dengan pola (layanan, pod, " +"perilaku, dll)" + +msgid "" +"First reasonable testing in gates would be to setup Linux Bridge and check " +"if VM network connectivity is working." +msgstr "" +"Pengujian masuk akal pertama di gate adalah untuk mengatur Linux Bridge dan " +"memeriksa apakah konektivitas jaringan VM berfungsi." + +msgid "" +"Fluentbit, Fluentd meet OpenStack-Helm's logging requirements for gathering, " +"aggregating, and delivering of logged events. Fluntbit runs as a daemonset " +"on each node and mounts the /var/lib/docker/containers directory. The Docker " +"container runtime engine directs events posted to stdout and stderr to this " +"directory on the host. Fluentbit then forward the contents of that directory " +"to Fluentd. Fluentd runs as deployment at the designated nodes and expose " +"service for Fluentbit to forward logs. Fluentd should then apply the " +"Logstash format to the logs. Fluentd can also write Kubernetes and OpenStack " +"metadata to the logs. Fluentd will then forward the results to Elasticsearch " +"and to optionally Kafka. Elasticsearch indexes the logs in a logstash-* " +"index by default. Kafka stores the logs in a 'logs' topic by default. Any " +"external tool can then consume the 'logs' topic." +msgstr "" +"Fluentbit, Fluentd memenuhi persyaratan logging OpenStack-Helm untuk " +"mengumpulkan, mengagregasi, dan mengirimkan peristiwa yang dicatat. Fluntbit " +"berjalan sebagai daemonset pada setiap node dan me-mount direktori /var/lib/" +"docker/containers. Mesin runtime kontainer Docker mengarahkan event yang " +"diposting ke stdout dan stderr ke direktori ini di host. Fluentbit kemudian " +"meneruskan isi direktori itu ke Fluentd. Fluentd berjalan sebagai penyebaran " +"di node yang ditunjuk dan mengekspos layanan untuk Fluentbit untuk " +"meneruskan log. Fluentd kemudian harus menerapkan format Logstash ke log. " +"Fluentd juga dapat menulis metadata Kubernetes dan OpenStack ke log. Fluentd " +"kemudian akan meneruskan hasilnya ke Elasticsearch dan ke opsional Kafka. " +"Elasticsearch mengindeks log dalam logstash-* index secara default. Kafka " +"menyimpan log dalam topik 'log' secara default. Alat eksternal apa pun " +"kemudian dapat menggunakan topik 'log'." + +msgid "Fluentbit-Fluentd logging chart" +msgstr "Fluentbit-Fluentd logging chart" + +msgid "Fluentd chart" +msgstr "Fluentd chart" + +msgid "Fluentd properly filters and categorizes logs" +msgstr "Fluentd memfilter dan mengkategorikan log dengan benar" + +msgid "" +"Fluentd send aggregated logs to Elasticsearch for the internal use cases" +msgstr "" +"Fluentd mengirim log agregat ke Elasticsearch untuk kasus penggunaan internal" + +msgid "Fluentd then attaches Kubernetes and/or OpenStack metadata" +msgstr "Fluentd kemudian melampirkan Kubernetes dan/atau metadata OpenStack" + +msgid "" +"Fluentd, Elasticsearch, and Kibana meet OpenStack-Helm's logging " +"requirements for capture, storage and visualization of logged events. " +"Fluentd runs as a daemonset on each node and mounts the /var/lib/docker/" +"containers directory. The Docker container runtime engine directs events " +"posted to stdout and stderr to this directory on the host. Fluentd should " +"then declare the contents of that directory as an input stream, and use the " +"fluent-plugin-elasticsearch plugin to apply the Logstash format to the " +"logs. Fluentd will also use the fluentd-plugin-kubernetes-metadata plugin " +"to write Kubernetes metadata to the log record. Fluentd will then forward " +"the results to Elasticsearch, which indexes the logs in a logstash-* index " +"by default. The resulting logs can then be queried directly through " +"Elasticsearch, or they can be viewed via Kibana. Kibana offers a dashboard " +"that can create custom views on logged events, and Kibana integrates well " +"with Elasticsearch by default." +msgstr "" +"Fluentd, Elasticsearch, dan Kibana memenuhi persyaratan logging OpenStack-" +"Helm untuk menangkap, menyimpan, dan memvisualisasikan event yang dicatat. " +"Fluentd berjalan sebagai daemonset pada setiap node dan me-mount direktori /" +"var/lib/docker/containers. Mesin runtime kontainer Docker mengarahkan event " +"yang diposting ke stdout dan stderr ke direktori ini di host. Fluentd " +"kemudian harus mendeklarasikan isi direktori itu sebagai aliran input, dan " +"menggunakan plugin fluent-plugin-elasticsearch untuk menerapkan format " +"Logstash ke log. Fluentd juga akan menggunakan plugin fluentd-plugin-" +"kubernetes-metadata untuk menulis metadata Kubernetes ke catatan log. " +"Fluentd kemudian akan meneruskan hasilnya ke Elasticsearch, yang secara " +"default mengindeks log dalam indeks logstash-*. Log yang dihasilkan kemudian " +"dapat ditanyakan langsung melalui Elasticsearch, atau mereka dapat dilihat " +"melalui Kibana. Kibana menawarkan dasbor yang dapat membuat tampilan kustom " +"pada event yang dicatat, dan Kibana terintegrasi dengan baik dengan " +"Elasticsearch secara default." + +msgid "" +"For Tenant Ceph, we will not be provisioning storage classes therefor, " +"update script to not install ceph-provisioners chart as following." +msgstr "" +"Untuk Tenant Ceph, kami tidak akan menyediakan kelas penyimpanan karenanya, " +"update skrip untuk tidak memasang chart ceph-provisioners sebagai berikut." + +msgid "" +"For the ``Category B`` helm charts, an informal testing has been done in the " +"past to ensure image independence. However, there is nothing exercising this " +"independence in gates. Due to that, code of the helm charts might or might " +"not require adapting." +msgstr "" +"Untuk ``Category B`` helm chart, pengujian informal telah dilakukan di masa " +"lalu untuk memastikan independensi image. Namun, tidak ada yang melaksanakan " +"independensi ini di gate. Karena itu, kode helm chart mungkin perlu atau " +"tidak perlu diadaptasi." + +msgid "" +"For this spec, we assume ``imagename1`` and ``imagename2`` are similarly " +"built. This means we do not require any override per image. Instead we " +"require a generic kind of override, per application, usable by all charts." +msgstr "" +"Untuk spek ini, kami mengasumsikan ``imagename1`` dan ``imagename2`` " +"dibangun dengan cara yang sama. Ini berarti kami tidak memerlukan " +"penggantian apa pun per image. Sebagai gantinya, kami memerlukan jenis " +"override umum, per aplikasi, dapat digunakan oleh semua chart." + +msgid "Gate job testing VM network connectivity." +msgstr "Gate job testing konektivitas jaringan VM" + +msgid "Gating" +msgstr "Gating" + +msgid "" +"Gating must prove that upgrades from each supported OpenStack version to the " +"next operate flawlessly, using the default image set (LOCI). Specifically, " +"each OpenStack chart should be upgraded from one release to the next, and " +"each infrastructure service from one minor version to the next. Both the " +"container image and configuration must be modified as part of this upgrade. " +"At minimum, Newton to Ocata upgrade must be validated for the 1.0 release." +msgstr "" +"Gating harus membuktikan bahwa upgrade dari setiap versi OpenStack yang " +"didukung ke operasi selanjutnya dengan sempurna, menggunakan set image " +"default (LOCI). Secara khusus, setiap bagan OpenStack harus ditingkatkan " +"dari satu rilis ke yang berikutnya, dan setiap layanan infrastruktur dari " +"satu versi minor ke yang berikutnya. Baik image kontainer maupun konfigurasi " +"harus dimodifikasi sebagai bagian dari upgrade ini. Minimal, upgrade Newton " +"ke Ocata harus divalidasi untuk rilis 1.0." + +msgid "Grafana chart" +msgstr "Grafana chart" + +msgid "" +"Having services configured, also the services pod dependencies should be " +"updated to reflect the new kind on L2 agent:" +msgstr "" +"Setelah layanan dikonfigurasi, dependensi pod layanan juga harus diperbarui " +"untuk mencerminkan jenis baru pada agen L2:" + +msgid "Helm" +msgstr "Helm" + +msgid "Helm chart for Alertmanager" +msgstr "Helm chart untuk Alertmanager" + +msgid "Helm chart for Elasticsearch" +msgstr "Helm chart untuk Elasticsearch" + +msgid "Helm chart for Fluentbit-Fluentd Combination" +msgstr "Helm chart untuk Fluentbit-Fluentd Combination" + +msgid "Helm chart for Fluentd" +msgstr "Helm chart untuk Fluentd" + +msgid "Helm chart for Grafana" +msgstr "Helm chart untuk Grafana" + +msgid "Helm chart for Kibana" +msgstr "Helm chart untuk Kibana" + +msgid "Helm chart for Prometheus" +msgstr "Helm chart untuk Prometheus" + +msgid "Helm charts for any appropriate Prometheus exporters" +msgstr "Helm chart untuk eksportir Prometheus yang tepat" + +msgid "" +"Helm charts for which we are building images in osh-images. (Called further " +"``Category B`` helm charts)" +msgstr "" +"helm chart dimana kami sedang membangun gambar dalam gambar-osh. (Disebut " +"lebih lanjut ``Category B`` helm chart)" + +msgid "" +"Helm charts for which we use official upstream images. (Called further " +"``Category A`` helm charts)" +msgstr "" +"Helm chart yang kami gunakan menggunakan image hulu resmi. (Disebut lebih " +"lanjut ``Category A`` helm chart)" + +msgid "Helm must be installed" +msgstr "Helm harus dipasang" + +msgid "" +"Helm test is the building block for all gating. Each chart must integrate a " +"helm-test script which validates proper functionality. This is already a " +"merge criterion for new charts, but a handful of older charts still need for " +"helm test functionality to be added. No additional charts will be merged " +"prior to 1.0 unless they meet this requirement (and others in this document)." +msgstr "" +"Tes helm adalah blok bangunan untuk semua gating. Setiap chart harus " +"mengintegrasikan skrip uji coba yang memvalidasi fungsi yang tepat. Ini " +"sudah menjadi kriteria penggabungan untuk chart baru, tetapi beberapa chart " +"lama masih perlu ditambahkan fungsionalitas uji helm. Tidak ada grafik " +"tambahan yang akan digabung sebelum 1.0 kecuali mereka memenuhi persyaratan " +"ini (dan yang lainnya dalam dokumen ini)." + +msgid "Here is a list of the current specs:" +msgstr "Berikut adalah daftar spesifikasi saat ini:" + +msgid "Host utilization: memory usage, CPU usage, disk I/O, network I/O, etc" +msgstr "" +"Pemanfaatan host: penggunaan memori, penggunaan CPU, disk I / O, I / O " +"jaringan, dll" + +msgid "Hosts must use KubeDNS / CoreDNS for resolution" +msgstr "Host harus menggunakan KubeDNS / CoreDNS untuk resolusi" + +msgid "" +"I propose to extend the conf schema with generic software information. For " +"example, for apache2:" +msgstr "" +"Saya mengusulkan untuk memperluas skema conf dengan informasi perangkat " +"lunak umum. Misalnya, untuk apache2:" + +msgid "Identify etcd performance that could lead to cluster instability" +msgstr "" +"Identifikasi kinerja etcd yang dapat menyebabkan ketidakstabilan cluster" + +msgid "" +"Identify issues with Kubernetes components, such as: etcd, CNI, scheduler, " +"etc" +msgstr "" +"Identifikasi masalah dengan komponen Kubernetes, seperti: etcd, CNI, " +"scheduler, dll" + +msgid "" +"Identify issues with infrastructure components, such as RabbitMQ, mariadb, " +"etc" +msgstr "" +"Identifikasi masalah dengan komponen infrastruktur, seperti RabbitMQ, " +"mariadb, dll" + +msgid "Identify opportunities for improving Prometheus's operation over time" +msgstr "" +"Identifikasi peluang untuk meningkatkan operasi Prometheus dari waktu ke " +"waktu" + +msgid "" +"If .Values.endpoints.oci_image_registry.auth.enabled will be set to true, " +"then any containers created with the current service account will have the " +"``imagePullSecrets`` automatically added to their spec and the secret will " +"be passed to kubelet to be used for pulling images." +msgstr "" +"Jika .Values.endpoints.oci_image_registry.auth.enabled akan disetel ke true, " +"maka setiap kontainer yang dibuat dengan akun layanan saat ini akan memiliki " +"``imagePullSecrets`` secara otomatis ditambahkan ke spesifikasi mereka dan " +"rahasia akan diteruskan ke kubelet untuk digunakan untuk menarik image." + +msgid "" +"If :code:`.Values.manifests.daemonset_ovs_agent` will be set to false, " +"neutron ovs agent would not be launched. In that matter, other type of L2 or " +"L3 agent on compute node can be run." +msgstr "" +"If :code:`.Values.manifests.daemonset_ovs_agent` akan disetel ke false, agen " +"neutron ovs tidak akan diluncurkan. Dalam hal ini, agen L2 atau L3 jenis " +"lain pada node komputasi dapat dijalankan." + +msgid "Implement decomposable Neutron chart" +msgstr "Terapkan chart Neutron terurai (decomposable)" + +msgid "Implementation" +msgstr "Pelaksanaan" + +msgid "" +"In a secured deployment, TLS certificates are used to protect the transports " +"amongst the various components. In some cases, this requires additional " +"mechanism to handle TLS offloading and to terminate the connection " +"gracefully:" +msgstr "" +"Dalam penyebaran yang aman, sertifikat TLS digunakan untuk melindungi " +"transportasi di antara berbagai komponen. Dalam beberapa kasus, ini " +"membutuhkan mekanisme tambahan untuk menangani pemuatan TLS dan untuk " +"mengakhiri koneksi dengan lembut:" + +msgid "In above example OVS and Neutron OVS agent are disabled." +msgstr "Dalam contoh di atas agen OVS dan Neutron OVS dinonaktifkan." + +msgid "" +"In all cases, we will need to provide different ``profiles`` (in other " +"words, overrides), to test different image providers use cases in CI." +msgstr "" +"Dalam semua kasus, kami akan perlu memberikan ``profil`` yang berbeda " +"(dengan kata lain, override), untuk menguji berbagai kasus penggunaan " +"penyedia image dalam CI." + +msgid "" +"In order to maximize flexibility for operators, and to help facilitate " +"upgrades to newer versions of containerized software without editing the " +"chart itself, all configuration files will be specified dynamically based on " +"`values.yaml` and overrides. In most cases the config files will be " +"generated based on the YAML values tree itself, and in some cases the config " +"file content will be specified in `values.yaml` as a string literal." +msgstr "" +"Untuk memaksimalkan fleksibilitas bagi operator, dan untuk membantu " +"memfasilitasi upgrade ke versi yang lebih baru dari perangkat lunak " +"containerized tanpa mengedit chart itu sendiri, semua file konfigurasi akan " +"ditentukan secara dinamis berdasarkan pada `values.yaml` dan override. Dalam " +"kebanyakan kasus file config akan dihasilkan berdasarkan pada YAML values " +"tree itu sendiri, dan dalam beberapa kasus konten file config akan " +"ditentukan dalam `values.yaml` sebagai string literal." + +msgid "In particular, these charts must move to OpenStack-Helm-Infra:" +msgstr "Secara khusus, chart ini harus pindah ke OpenStack-Helm-Infra:" + +msgid "" +"In the current openstack-helm, all charts provide an ``images:`` section in " +"their ``values.yaml`` that have the container images references. By default, " +"the container images are all downloaded from a registry hosted by Docker or " +"Quay. However, the image references can be overridden by operators to " +"download images from any OCI image registry. In the case that the OCI image " +"registry has authentication turned on, kubelet would fail to download the " +"images because the current Openstack-Helm does not provide a way to pass the " +"OCI image registry credentials to kubernetes when pulling images." +msgstr "" +"Di openstack-helm saat ini, semua chart menyediakan bagian ``images:`` di " +"``values.yaml`` mereka yang memiliki referensi image kontainer. Secara " +"default, semua image kontainer diunduh dari registri yang diselenggarakan " +"oleh Docker atau Quay. Namun, referensi image dapat diganti oleh operator " +"untuk mengunduh image dari registri image OCI. Jika registry image OCI telah " +"dihidupkan otentikasi, kubelet akan gagal mengunduh image karena Openstack-" +"Helm saat ini tidak menyediakan cara untuk meneruskan kredensial registri " +"image OCI ke kubernet ketika menarik image." + +msgid "Include the URL of your Storyboard RFE:" +msgstr "Sertakan URL RF Storyboard Anda:" + +msgid "" +"Installing OVS requires Kubernetes worker node labeling with tag :code:" +"`openvswitch=enabled`. To mark nodes where LB should be used, new tag will " +"be introduced: :code:`linuxbridge=enabled`." +msgstr "" +"Instalasi OVS membutuhkan pelabelan node Kubernetes worker dengan tag :code:" +"`openvswitch=enabled`. Untuk menandai node tempat LB harus digunakan, tag " +"baru akan diperkenalkan: :code:`linuxbridge=enabled`." + +msgid "Instead of using nginx, haproxy can be used instead." +msgstr "Daripada menggunakan nginx, haproxy dapat digunakan sebagai gantinya." + +msgid "" +"Introducing a new SDN solution should consider how the above services are " +"provided. It may be required to disable the built-in Neutron functionality." +msgstr "" +"Memperkenalkan solusi SDN baru harus mempertimbangkan bagaimana layanan di " +"atas disediakan. Mungkin diperlukan untuk menonaktifkan fungsionalitas " +"Neutron bawaan (built-in)." + +msgid "" +"It is important to notice that the helm charts can be split in two " +"categories for now:" +msgstr "" +"Penting untuk diperhatikan bahwa chart helm dapat dibagi menjadi dua " +"kategori untuk saat ini:" + +msgid "Kibana chart" +msgstr "Kibana chart" + +msgid "Kubernetes" +msgstr "Kubernetes" + +msgid "Kubernetes metrics: pod status, replica availability, job status, etc" +msgstr "" +"Metrik Kubernetes: status pod, ketersediaan replika, status pekerjaan, dll" + +msgid "" +"Kubernetes must enable mount propagation (until it is enabled by default)" +msgstr "" +"Kubernet harus mengaktifkan propagasi mount (sampai diaktifkan secara " +"default)" + +msgid "L3 routing - creation of routers" +msgstr "L3 routing - pembuatan router" + +msgid "Labels assigned to nodes: node1, node2, node3:" +msgstr "Label diberikan ke node: node1, node2, node3:" + +msgid "Labels assigned to nodes: node4, node5, node6:" +msgstr "Label diberikan ke node: node4, node5, node6:" + +msgid "" +"Labels for mon, osd, rgw, mgr and job have been updated for tenant Ceph." +msgstr "" +"Label untuk mon, osd, rgw, mgr dan pekerjaan telah diperbarui untuk tenant " +"Ceph." + +msgid "" +"Let's consider how new SDN can take advantage of disaggregated Neutron " +"services architecture. First assumption is that neutron-server functionality " +"would be common for all SDNs, as it provides networking API, database " +"management and Keystone interaction. Required modifications are:" +msgstr "" +"Mari kita pertimbangkan bagaimana SDN baru dapat memanfaatkan arsitektur " +"layanan Neutron terpilah (disaggregated). Asumsi pertama adalah bahwa " +"fungsionalitas server neutron akan umum untuk semua SDN, karena menyediakan " +"API jaringan, manajemen basis data, dan interaksi Keystone. Modifikasi yang " +"diperlukan adalah:" + +msgid "" +"LinuxBridge installation with neutron chart takes advantaged of decomposable " +"neutron chart in OSH. LinuxBridge agent will be added as daemonset, " +"similarly how OVS is implemented. New value :code:`daemonset_lb_agent` " +"should be added in :code:`neutron/values.yaml` in :code:`manifests` section:" +msgstr "" +"Instalasi LinuxBridge dengan chart neutron mengambil keuntungan dari chart " +"neutron decomposable di OSH. Agen LinuxBridge akan ditambahkan sebagai " +"daemonset, sama seperti bagaimana OVS diimplementasikan. Nilai baru :code:" +"`daemonset_lb_agent` harus ditambahkan dalam :code:`neutron/values.yaml` di " +"hagian :code:`manifests``:" + +msgid "LinuxBridge should be also enabled in :code:`manifests` section:" +msgstr "LinuxBridge juga harus diaktifkan di bagian :code:`manifests` :" + +msgid "" +"LinuxBridge should support external bridge configuration, as well as auto " +"bridge add mechanism implemented for OVS." +msgstr "" +"LinuxBridge harus mendukung konfigurasi jembatan eksternal, serta mekanisme " +"penambahan jembatan otomatis yang diterapkan untuk OVS." + +msgid "Log aggregator deployment runs on a selected node as deployment" +msgstr "" +"Penerapan agregator log berjalan pada node yang dipilih sebagai penyebaran" + +msgid "Log aggregator is able to send data to Elasticsearch and Kafka" +msgstr "Log aggregator dapat mengirim data ke Elasticsearch dan Kafka" + +msgid "Log aggregator should be scalable" +msgstr "Log agregator harus scalable" + +msgid "Log aggregator should have HA capability" +msgstr "Log aggregator harus memiliki kemampuan HA" + +msgid "Log aggregator should have a flexible output capability to choose from" +msgstr "" +"Log aggregator harus memiliki kemampuan output yang fleksibel untuk dipilih" + +msgid "Log collection daemon runs on each node to forward logs to aggregator" +msgstr "" +"Log koleksi daemon berjalan pada setiap node untuk meneruskan log ke " +"aggregator" + +msgid "Log collection daemon runs on each node to forward logs to storage" +msgstr "" +"Log koleksi daemon berjalan pada setiap node untuk meneruskan log ke " +"penyimpanan" + +msgid "Log collection daemon should have a minimal server footprint" +msgstr "Daemon pengumpulan log harus memiliki jejak server minimal" + +msgid "Logging" +msgstr "Logging" + +msgid "Logging Requirements" +msgstr "Persyaratan Logging" + +msgid "Logging Use Cases" +msgstr "Mencatat Penggunaan Kasus (logging use case)" + +msgid "Logical Diagram" +msgstr "Diagram Logika" + +msgid "" +"Make following changes to script: 1 Replace occurrence of ``ceph-fs-uuid." +"txt`` with ``tenant-ceph-fs-uuid.txt``" +msgstr "" +"Buat perubahan berikut pada skrip: 1 Ganti kemunculan ``ceph-fs-uuid.txt`` " +"dengan ``tenant-ceph-fs-uuid.txt``" + +msgid "" +"Make webserver binary path/arguments templated using ``values.yaml``. As " +"expressed above, this allows us to provide different overrides per image/" +"distribution to automatically wire things." +msgstr "" +"Buat path/argument biner webserver templated menggunakan ``values.yaml``. " +"Seperti yang dinyatakan di atas, ini memungkinkan kami untuk memberikan " +"penggantian yang berbeda per image/distribution untuk secara otomatis " +"mentransfer berbagai hal." + +msgid "Metadata- Provide proxy for Nova metadata service" +msgstr "Metadata- Berikan proxy untuk layanan Nova metadata" + +msgid "Monitoring" +msgstr "Pemantauan" + +msgid "Monitoring Requirements" +msgstr "Persyaratan Pemantauan" + +msgid "Monitoring Use Cases" +msgstr "Memonitor Kasus Penggunaan" + +msgid "" +"More information about the blueprint + specification lifecycle can be found " +"here_." +msgstr "" +"Informasi lebih lanjut tentang siklus hidup blueprint + spesifikasi dapat " +"ditemukan here_." + +msgid "Multi-OS Support" +msgstr "Dukungan Multi-OS" + +msgid "Neutron multiple SDNs" +msgstr "Neutron multiple SDNs" + +msgid "New charts" +msgstr "New charts" + +msgid "" +"Next, Neutron services like L3 routing, DHCP and metadata serving should be " +"considered. If SDN provides its own implementation, the Neutron's default " +"one should be disabled:" +msgstr "" +"Selanjutnya, layanan Neutron seperti L3 routing, DHCP dan penyajian metadata " +"harus dipertimbangkan. Jika SDN menyediakan implementasinya sendiri, default " +"Neutron harus dinonaktifkan:" + +msgid "Nginx Sidecar" +msgstr "Nginx Sidecar" + +msgid "No benchmark was done to evaluate:" +msgstr "Tidak ada patokan yang dilakukan untuk mengevaluasi:" + +msgid "" +"No change in testing is required, *per se*. It is expected the new software " +"configuration would be tested with the current practices." +msgstr "" +"Tidak diperlukan perubahan dalam pengujian, *per se*. Diharapkan konfigurasi " +"perangkat lunak baru akan diuji dengan praktik saat ini." + +msgid "" +"No direct impact, as there is no change in the current software/" +"configuration location, merely a templating change." +msgstr "" +"Tidak ada dampak langsung, karena tidak ada perubahan pada lokasi software/" +"configuration saat ini, hanya perubahan templating." + +msgid "No impact" +msgstr "Tidak ada dampak" + +msgid "No performance impact" +msgstr "Tidak ada dampak kinerja" + +msgid "No security impact." +msgstr "Tidak ada dampak keamanan." + +msgid "None" +msgstr "None" + +msgid "" +"None more than this spec, as it should be relatively transparent for the " +"user. However, extra documentation to explain the usage of " +"``value_overrides`` would be welcomed." +msgstr "" +"Tidak lebih dari spesifikasi ini, karena seharusnya relatif transparan untuk " +"pengguna. Namun, dokumentasi tambahan untuk menjelaskan penggunaan " +"``value_overrides`` akan disambut." + +msgid "" +"Not providing a support of multiple images. This leads to ease of " +"maintainance and reduced gate impact, with the risk of having less " +"contributors. For available overrides, users would have to provide many " +"overrides themselves, while this spec proposes a common community approach." +msgstr "" +"Tidak memberikan dukungan multiple image. Ini mengarah pada kemudahan " +"pemeliharaan dan mengurangi dampak gate, dengan risiko memiliki lebih " +"sedikit kontributor. Untuk override yang tersedia, pengguna harus " +"menyediakan sendiri banyak override, sementara spesifikasi ini mengusulkan " +"pendekatan komunitas umum." + +msgid "Note that mon_addr and mon_host have default mon port 6789." +msgstr "Perhatikan bahwa mon_addr dan mon_host memiliki mon port default 6789." + +msgid "OSH Logging, Monitoring, and Alerting" +msgstr "OSH Logging, Monitoring, dan Alerting" + +msgid "" +"OVS is an alternative in Neutron reference architecture. It is already in " +"tree." +msgstr "" +"OVS adalah alternatif dalam arsitektur referensi Neutron. Sudah ada di tree." + +msgid "" +"On top of that, the newly provided `example_values/` must aim for being " +"tested **as soon as possible upon delivery**. Without tests, those examples " +"will decrepit. The changes in CI pipelines for making use of " +"`example_values` is outside the scope of this spec." +msgstr "" +"Selain itu, `example_values/` yang baru disediakan harus bertujuan untuk " +"diuji ***as soon as possible upon delivery**. Tanpa tes, contoh itu akan " +"usang. Perubahan dalam pipeline CI untuk menggunakan `example_values` berada " +"di luar cakupan spec ini." + +msgid "" +"Only provide one way to configure software, and expect to always have the " +"same versions. This is further away from the \"image independent\" contract, " +"with extra burden: We will need to maintain a curated list of versions, deal " +"with the differences of the defaults (selinux/apparmor profiles come to mind " +"as path sensitive for example), and different expectations for operational " +"teams (\"The code is not where I expect it to be in the image\"). Embracing " +"difference could even allow deployers to have different expectations for " +"images, for example: apache+mod_wsgi vs uwsgi standalone or uwsgi + nginx." +msgstr "" +"Hanya menyediakan satu cara untuk mengkonfigurasi perangkat lunak, dan " +"berharap untuk selalu memiliki versi yang sama. Ini lebih jauh dari kontrak " +"\"image independent\", dengan beban tambahan: Kita perlu mempertahankan " +"daftar versi yang dikuratori (curated), menangani perbedaan default (profil " +"selinux/apparmor muncul di pikiran sebagai path sensitif misalnya), dan " +"harapan yang berbeda untuk tim operasional (\"The code is not where I expect " +"it to be in the image\"). Merangkul perbedaan bahkan dapat memungkinkan para " +"deployer untuk memiliki harapan yang berbeda untuk image, misalnya: apache" +"+mod_wsgi vs uwsgi standalone or uwsgi + nginx." + +msgid "" +"OpenStack metrics: tenants, networks, flavors, floating IPs, quotas, etc" +msgstr "" +"Metrik OpenStack: tenants, networks, flavors, floating IPs, quotas, dll" + +msgid "OpenStack-Helm 1.0 Requirements" +msgstr "OpenStack-Helm 1.0 Requirements" + +msgid "" +"OpenStack-Helm currently lacks a centralized mechanism for providing insight " +"into the performance of the OpenStack services and infrastructure " +"components. The log formats of the different components in OpenStack-Helm " +"vary, which makes identifying causes for issues difficult across services. " +"To support operational readiness by default, OpenStack-Helm should include " +"components for logging events in a common format, monitoring metrics at all " +"levels, alerting and alarms for those metrics, and visualization tools for " +"querying the logs and metrics in a single pane view." +msgstr "" +"OpenStack-Helm saat ini tidak memiliki mekanisme terpusat untuk memberikan " +"wawasan tentang kinerja layanan OpenStack dan komponen infrastruktur. Format " +"log dari berbagai komponen di OpenStack-Helm bervariasi, yang membuat " +"mengidentifikasi penyebab masalah sulit di seluruh layanan. Untuk mendukung " +"kesiapan operasional secara default, OpenStack-Helm harus menyertakan " +"komponen untuk mencatat peristiwa dalam format umum, memantau metrik di " +"semua tingkatan, mengingatkan dan alarm untuk metrik tersebut, dan alat " +"visualisasi untuk menanyakan log dan metrik dalam tampilan panel tunggal." + +msgid "" +"OpenStack-Helm defines a centralized logging mechanism to provide insight " +"into the state of the OpenStack services and infrastructure components as " +"well as underlying Kubernetes platform. Among the requirements for a logging " +"platform, where log data can come from and where log data need to be " +"delivered are very variable. To support various logging scenarios, OpenStack-" +"Helm should provide a flexible mechanism to meet with certain operation " +"needs. This spec proposes fast and lightweight log forwarder and full " +"featured log aggregator complementing each other providing a flexible and " +"reliable solution. Especially, Fluentbit is proposed as a log forwarder and " +"Fluentd is proposed as a main log aggregator and processor." +msgstr "" +"OpenStack-Helm mendefinisikan mekanisme logging terpusat untuk memberikan " +"wawasan (insight) tentang status layanan OpenStack dan komponen " +"infrastruktur serta platform Kubernetes yang mendasarinya. Di antara " +"persyaratan untuk platform logging, dari mana data log dapat berasal dan " +"dari mana data log harus dikirim sangat bervariasi. Untuk mendukung berbagai " +"skenario logging, OpenStack-Helm harus menyediakan mekanisme yang fleksibel " +"untuk memenuhi kebutuhan operasi tertentu. Spesifikasi ini mengusulkan log " +"forwarder cepat dan ringan dan agregator log berfitur lengkap yang saling " +"melengkapi memberikan solusi yang fleksibel dan andal. Terutama, Fluentbit " +"diusulkan sebagai log forwarder dan Fluentd diusulkan sebagai agregator dan " +"prosesor log utama." + +msgid "" +"OpenStack-Helm documentation will be updated to indicate the usage of the " +"nginx sidecar." +msgstr "" +"Dokumentasi OpenStack-Helm akan diperbarui untuk menunjukkan penggunaan " +"nginx sidecar." + +msgid "OpenStack-Helm for OpenStack services" +msgstr "OpenStack-Helm untuk layanan OpenStack" + +msgid "" +"OpenStack-Helm has developed a number of conventions around the format and " +"ordering of charts' `values.yaml` file, in support of both reusable Helm-" +"Toolkit functions and ease of developer ramp-up. For 1.0 readiness, " +"OpenStack-Helm must cement these conventions within a spec, as well as the " +"ordering of `values.yaml` keys. These conventions must then be gated to " +"guarantee conformity. The spec in progress can be found here [1]_." +msgstr "" +"OpenStack-Helm telah mengembangkan sejumlah konvensi seputar format dan " +"pemesanan file chart ``values.yaml`, untuk mendukung kedua fungsi Helm-" +"Toolkit yang dapat digunakan kembali dan kemudahan pengembangan pengembang. " +"Untuk kesiapan 1.0, OpenStack-Helm harus menambahkan konvensi ini dalam " +"spesifikasi, serta urutan kunci `values.yaml`. Konvensi ini kemudian harus " +"terjaga keamanannya untuk menjamin kepatuhan. Spesifikasi yang sedang " +"berjalan dapat ditemukan di sini [1] _." + +msgid "" +"OpenStack-Helm has undergone rapid development and maturation over its " +"lifetime, and is nearing the point of real-world readiness. This spec " +"details the functionality that must be implemented in OpenStack-Helm for it " +"to be considered ready for a 1.0 release, as well as for general use." +msgstr "" +"OpenStack-Helm telah mengalami perkembangan dan pematangan yang cepat selama " +"masa hidupnya, dan mendekati titik kesiapan real-world. Spesifikasi ini " +"merinci fungsionalitas yang harus diimplementasikan di OpenStack-Helm agar " +"dianggap siap untuk rilis 1.0, serta untuk penggunaan umum." + +msgid "" +"OpenStack-Helm multinode guide includes scripts which are used to specify " +"overrides and deploy charts." +msgstr "" +"Panduan multinode OpenStack-Helm mencakup skrip yang digunakan untuk " +"menentukan override dan menyebarkan chart." + +msgid "" +"OpenStack-Helm supports a \"bring your own Kubernetes\" paradigm. Any " +"particular k8s configuration or feature requirements must be documented." +msgstr "" +"OpenStack-Helm mendukung paradigma \"bring your own Kubernetes\". " +"Konfigurasi k8 tertentu atau persyaratan fitur harus didokumentasikan." + +msgid "OpenStack-Helm-Addons for ancillary services" +msgstr "OpenStack-Helm-Addons untuk layanan tambahan" + +msgid "OpenStack-Helm-Infra for supporting services" +msgstr "OpenStack-Helm-Infra untuk layanan pendukung" + +msgid "Operating system" +msgstr "Operating system" + +msgid "" +"Operators should be able to use Openstack-Helm to deploy containerized " +"openstack services with a docker registry has authentication turned on." +msgstr "" +"Operator harus dapat menggunakan Openstack-Helm untuk menggunakan layanan " +"openstack containerized dengan registry docker yang telah mengaktifkan " +"otentikasi." + +msgid "Orchestration (heat)" +msgstr "Orchestration (heat)" + +msgid "Organizational auditing needs" +msgstr "Kebutuhan audit organisasi" + +msgid "Other networking services provided by Neutron are:" +msgstr "Layanan jaringan lain yang disediakan oleh Neutron adalah:" + +msgid "" +"Other services inside Neutron reference stack (L3/DHCP/metadata agents) are " +"dependent on L2 connectivity agent. Thus, replacing OVS with LB would cause " +"changes in mentioned services configuration." +msgstr "" +"Layanan lain di dalam stack referensi Neutron (L3/DHCP/metadata agents) " +"bergantung pada agen konektivitas L2. Jadi, mengganti OVS dengan LB akan " +"menyebabkan perubahan dalam konfigurasi layanan yang disebutkan." + +msgid "" +"Our :ref:`images documentation` documentation claims to be independent of " +"the image. However, some helm charts hard code paths of binaries, " +"executables' runtime configurations, etc. Therefore, the image agnostic " +"promise is broken." +msgstr "" +"Dokumentasi kami :ref:`images documentation` mengklaim tidak tergantung dari " +"image. Namun, beberapa helm menunjukkan jalur kode yang sulit dari binari, " +"konfigurasi runtime yang dapat dieksekusi, dll. Oleh karena itu, janji " +"agnostik image rusak." + +msgid "Performance Impact" +msgstr "Dampak Kinerja" + +msgid "Pete Birley " +msgstr "Pete Birley " + +msgid "Platform Requirements" +msgstr "Persyaratan Platform" + +msgid "PoC deployments of OpenStack-Helm" +msgstr "Deployment PoC dari OpenStack-Helm" + +msgid "Port numbers for Ceph_Mon and Ceph_Mgr are different from default." +msgstr "Nomor port untuk Ceph_Mon dan Ceph_Mgr berbeda dari default." + +msgid "Pre-pulling images on all nodes" +msgstr "Pre-pulling image di semua node" + +msgid "Prepare Host(s) for OpenStack-Helm deployment" +msgstr "Mempersiapkan Host untuk penerapan OpenStack-Helm" + +msgid "Primary assignee:" +msgstr "Penugasan utama (primary assignee):" + +msgid "Primary assignees:" +msgstr "Penerima tugas utama (primary assignees):" + +msgid "Proactive monitoring of stack traces across all deployed infrastructure" +msgstr "Pemantauan proaktif stack trace di semua infrastruktur yang digunakan" + +msgid "Problem Description" +msgstr "Deskripsi Masalah" + +msgid "Process and Tooling" +msgstr "Proses dan Tooling" + +msgid "Project Specifications" +msgstr "Spesifikasi Proyek" + +msgid "" +"Prometheus and Grafana meet OpenStack-Helm's monitoring requirements. The " +"Prometheus monitoring tool provides the ability to scrape targets for " +"metrics over HTTP, and it stores these metrics in Prometheus's time-series " +"database. The monitoring targets can be discovered via static configuration " +"in Prometheus or through service discovery. Prometheus includes a querying " +"language that provides meaningful queries against the metrics gathered and " +"supports the creation of rules to measure these metrics against for alerting " +"purposes. It also supports a wide range of Prometheus exporters for " +"existing services, including Ceph and OpenStack. Grafana supports " +"Prometheus as a data source, and provides the ability to view the metrics " +"gathered by Prometheus in a single pane dashboard. Grafana can be " +"bootstrapped with dashboards for each target scraped, or the dashboards can " +"be added via Grafana's web interface directly. To meet OpenStack-Helm's " +"alerting needs, Alertmanager can be used to interface with Prometheus and " +"send alerts based on Prometheus rule evaluations." +msgstr "" +"Prometheus dan Grafana memenuhi persyaratan pemantauan OpenStack-Helm. Alat " +"pemantauan Prometheus menyediakan kemampuan untuk mengikis target (scrape " +"target) untuk metrik melalui HTTP, dan alat ini menyimpan metrik ini dalam " +"basis data seri waktu Prometheus. Sasaran pemantauan dapat ditemukan melalui " +"konfigurasi statis di Prometheus atau melalui penemuan layanan. Prometheus " +"menyertakan bahasa kueri yang menyediakan kueri yang berarti terhadap metrik " +"yang dikumpulkan dan mendukung pembuatan aturan untuk mengukur metrik ini " +"untuk keperluan peringatan. Ini juga mendukung berbagai eksportir Prometheus " +"untuk layanan yang ada, termasuk Ceph dan OpenStack. Grafana mendukung " +"Prometheus sebagai sumber data, dan menyediakan kemampuan untuk melihat " +"metrik yang dikumpulkan oleh Prometheus dalam dasbor panel tunggal. Grafana " +"dapat di-bootstrap dengan dasbor untuk setiap target yang dikorek, atau " +"dasbor dapat ditambahkan melalui antarmuka web Grafana secara langsung. " +"Untuk memenuhi kebutuhan peringatan OpenStack-Helm, Alertmanager dapat " +"digunakan untuk berinteraksi dengan Prometheus dan mengirim peringatan " +"berdasarkan evaluasi aturan Prometheus." + +msgid "Prometheus chart" +msgstr "Prometheus chart" + +msgid "Prometheus exporters" +msgstr "Prometheus exporters" + +msgid "Proper directories mounted to retrieve logs from the node" +msgstr "Direktori yang tepat dipasang untuk mengambil log dari node" + +msgid "Proposed Change" +msgstr "Usulan Perubahan" + +msgid "" +"Proposes a common approach to software configuration, describing the distro/" +"image specific differences for applications." +msgstr "" +"Mengusulkan pendekatan umum untuk konfigurasi perangkat lunak, menjelaskan " +"perbedaan specific distro/image untuk aplikasi." + +msgid "" +"Provide the credentials and add the manifest across all charts in OSH and " +"OSH-infra" +msgstr "" +"Berikan kredensial dan tambahkan manifes di semua chart di OSH dan OSH-infra" + +msgid "Providing the neutron plugin code." +msgstr "Memberikan kode plugin neutron." + +msgid "Provision of those services should be included inside SDN chart." +msgstr "Penyediaan layanan tersebut harus dimasukkan dalam chart SDN." + +msgid "Put .docker/config.json in docker/kubelet root directory on all nodes" +msgstr "" +"Masukkan .docker/config.json di direktori root docker/kubelet di semua node" + +msgid "Record OpenStack service behavior and status" +msgstr "Catat perilaku dan status layanan OpenStack" + +msgid "Record compute instance behavior across nodes and services" +msgstr "Catat perilaku instance komputasi di seluruh node dan layanan" + +msgid "" +"Reference the created secret by adding the ``imagePullSecrets:`` field to " +"ServiceAccount resource template [2]_ in ``helm-toolkit/snippets/" +"_kubernetes_pod_rbac_serviceaccount.tpl``. To handle it as optional, the " +"field is wrapped in a conditional. For example," +msgstr "" +"Referensi rahasia yang dibuat dengan menambahkan field ``imagePullSecrets:" +"`` ke templat sumber daya ServiceAccount [2] _ dalam ``helm-toolkit/snippets/" +"_kubernetes_pod_rbac_serviceaccount.tpl``. Untuk menanganinya sebagai " +"opsional, field dikemas dalam kondisi. Sebagai contoh," + +msgid "References" +msgstr "Referensi" + +msgid "" +"Release notes for the 1.0 release must be prepared, following OpenStack best " +"practices. The criteria for future changes that should be included in " +"release notes in an ongoing fashion must be defined / documented as well." +msgstr "" +"Catatan rilis untuk rilis 1.0 harus disiapkan, mengikuti praktik terbaik " +"OpenStack. Kriteria untuk perubahan di masa depan yang harus dimasukkan " +"dalam catatan rilis dengan cara yang berkelanjutan harus didefinisikan / " +"didokumentasikan juga." + +msgid "" +"Releated Specs: 1. OSH logging monitoring and alerting: https://review." +"openstack.org/#/c/482687/" +msgstr "" +"Spesifikasi yang Diresmikan: 1. Pemantauan dan peringatan logging OSH: " +"https://review.openstack.org/#/c/482687/" + +msgid "Result from Steps 2, 3, 4:" +msgstr "Hasil dari Langkah 2, 3, 4:" + +msgid "Results from Step 5, 6, 7:" +msgstr "Hasil dari Langkah 5, 6, 7:" + +msgid "SSH into VM and check it can access the internet" +msgstr "SSH ke VM dan periksa apakah dapat mengakses internet" + +msgid "Sane defaults for log retention and rotation policies" +msgstr "Sane default untuk penyimpanan retensi dan kebijakan rotasi" + +msgid "Script to update and execute: ``020-ingress.sh``" +msgstr "Skrip untuk update dan menjalankan: ``020-ingress.sh``" + +msgid "Script to update and execute: ``030-ceph.sh``" +msgstr "Skrip untuk update dan menjalankan: ``030-ceph.sh``" + +msgid "Script to update and execute: ``030-tenant-ceph.sh``" +msgstr "Skrip untuk update dan menjalankan: ``030-tenant-ceph.sh``" + +msgid "Script to update and execute: ``040-tenant-ceph-ns-activate.sh``" +msgstr "Skrip untuk update dan menjalankan: ``040-tenant-ceph-ns-activate.sh``" + +msgid "Script to update and execute: ``100-glance.sh``" +msgstr "Skrip untuk update dan menjalankan: ``100-glance.sh``" + +msgid "Script to update and execute: ``110-cinder.sh``" +msgstr "Skrip untuk update dan menjalankan: ``110-cinder.sh``" + +msgid "Script to update: ``090-tenant-ceph-radosgateway.sh``" +msgstr "Skrip untuk update: ``090-tenant-ceph-radosgateway.sh``" + +msgid "Security Impact" +msgstr "Dampak Keamanan" + +msgid "See above for documentation requirements." +msgstr "Lihat di atas untuk persyaratan dokumentasi." + +msgid "See above for gating requirements." +msgstr "Lihat di atas untuk persyaratan gating." + +msgid "See above for the list of work items." +msgstr "Lihat di atas untuk daftar item pekerjaan." + +msgid "Setup access to the external network from the development machine" +msgstr "Atur akses ke jaringan eksternal dari mesin pengembangan" + +msgid "Single pane visualization capabilities" +msgstr "Kemampuan visualisasi panel tunggal" + +msgid "Specifications Process" +msgstr "Spesifikasi Proses" + +msgid "Specifications Purpose" +msgstr "Specifications Purpose (spesifikasi tujuan)" + +msgid "" +"Specifications in this repository represent a consensus on the topics " +"covered within. They should be considered a mandate on the path forward " +"with regards to the content on which they are drafted." +msgstr "" +"Spesifikasi dalam repositori ini mewakili konsensus tentang topik yang " +"dicakup di dalam. Mereka harus dianggap sebagai mandat di jalan ke depan " +"sehubungan dengan konten yang mereka buat." + +msgid "StatefulSets" +msgstr "StatefulSets" + +msgid "Support OCI image registry with authentication turned on" +msgstr "Mendukung OCI image registry dengan otentikasi dihidupkan" + +msgid "Support linux bridge on neutron helm chart" +msgstr "Mendukung linux bridge pada chart helm neutron" + +msgid "TODO - release management spec" +msgstr "TODO - rilis spesifikasi manajemen" + +msgid "Test Steps:" +msgstr "Langkah uji:" + +msgid "Testing" +msgstr "Pengujian" + +msgid "" +"Testing should include Helm tests for each of the included charts as well as " +"an integration test in the gate." +msgstr "" +"Pengujian harus mencakup tes Helm untuk masing-masing chart termasuk juga " +"tes integrasi di gate." + +msgid "" +"The LinuxBridge (LB) is Neutron's L2 agent, using linux kernel bridges as " +"network configuration for VMs. Both OVS and LB are part of Neutron's Modular " +"Layer 2 (ML2) framework, allowing to simultaneously utilize the variety of " +"layer 2 networking technologies." +msgstr "" +"LinuxBridge (LB) adalah agen L2 Neutron, menggunakan jembatan kernel Linux " +"sebagai konfigurasi jaringan untuk VM. Baik OVS dan LB adalah bagian dari " +"kerangka kerja Modular Layer 2 (ML2) Neutron, memungkinkan untuk secara " +"bersamaan memanfaatkan berbagai teknologi jaringan layer 2." + +msgid "" +"The Neutron reference architecture provides mechanism_drivers OpenVSwitch " +"(OVS) and linuxbridge (LB) with ML2 core_plugin framework." +msgstr "" +"Arsitektur referensi Neutron menyediakan mechanism_drivers OpenVSwitch (OVS) " +"dan linuxbridge (LB) dengan ML2 core_plugin framework." + +msgid "" +"The OpenStack-Helm Zuulv2 gates were written to allow use outside of " +"OpenStack-Infra, to quickly set up a Kubernetes cluster, with the adoption " +"of Zuulv3 underway it is logical to extend this paradigm to the Zuulv3 " +"Playbooks. This will be driven via a ``Makefile`` that will allow developers " +"to perform the following actions:" +msgstr "" +"Gate OpenStack-Helm Zuulv2 ditulis untuk memungkinkan penggunaan di luar " +"OpenStack-Infra, untuk dengan cepat membuat kluster Kubernetes, dengan " +"adopsi Zuulv3 yang sedang berjalan, logis untuk memperluas paradigma ini ke " +"Playbook Zuulv3. Ini akan didorong melalui ``Makefile`` yang akan " +"memungkinkan pengembang untuk melakukan tindakan berikut:" + +msgid "" +"The OpenStack-Helm release process will be somewhat orthogonal to the " +"OpenStack release process, and the differences and relationship between the " +"two must be documented in a spec. This will help folks quickly understand " +"why OpenStack-Helm is a Release-Independent project from an OpenStack " +"perspective." +msgstr "" +"Proses rilis OpenStack-Helm akan sedikit ortogonal untuk proses rilis " +"OpenStack, dan perbedaan dan hubungan antara keduanya harus didokumentasikan " +"dalam sebuah spec. Ini akan membantu orang dengan cepat memahami mengapa " +"OpenStack-Helm adalah proyek Release-Independent dari perspektif OpenStack." + +msgid "" +"The ``profiles`` yaml files (for example ``centos_7``, ``opensuse_15``) will " +"be provided in each chart's ``example_values/`` directory. This folder will " +"be masked to helm through a helmignore file. Its content is only for user " +"consumption, not for inclusion in helm charts through the File directive. In " +"other words, this is a user interface given for convenience merely using the " +"abilities of the existing helm charts." +msgstr "" +"File ``profile`` yaml (misalnya ``centos_7``, ``opensuse_15``) akan " +"disediakan di setiap direktori ``example_values/`` chart. Folder ini akan " +"ditutup untuk dikunci melalui file helmignore. Kontennya hanya untuk " +"konsumsi pengguna, bukan untuk dimasukkan dalam helm chart melalui arahan " +"File. Dengan kata lain, ini adalah antarmuka pengguna yang diberikan untuk " +"kenyamanan hanya menggunakan kemampuan helm chart yang ada." + +msgid "" +"The above chart must include sensible configuration values to make the " +"logging platform usable by default. These include: proper input " +"configurations for both Fluentbit and Fluentd, proper output configurations " +"for both Fluentbit and Fluentd, proper metadata and formats applied to the " +"logs via Fluentd." +msgstr "" +"Bagan di atas harus menyertakan nilai konfigurasi yang masuk akal untuk " +"membuat platform logging dapat digunakan secara default. Ini termasuk: " +"konfigurasi input yang tepat untuk Fluentbit dan Fluentd, konfigurasi output " +"yang tepat untuk Fluentbit dan Fluentd, metadata yang tepat dan format yang " +"diterapkan pada log melalui Fluentd." + +msgid "" +"The alternative is to provide no organization layout for charts across all " +"openstack-helm repositories." +msgstr "" +"Alternatifnya adalah tidak menyediakan tata letak organisasi untuk chart di " +"semua repositori openstack-helm." + +msgid "" +"The alternative would be to continue supporting the current bash driven " +"containerized KubeADM and Kubelet approach, though this has the following " +"issues:" +msgstr "" +"Alternatifnya adalah untuk terus mendukung pendekatan Kubelet dan bash " +"driven containerized KubeADM saat ini, meskipun ini memiliki masalah sebagai " +"berikut:" + +msgid "" +"The bash scripts are largely undocumented and have grown to the point where " +"they are very hard for a new developer to work on." +msgstr "" +"Script bash sebagian besar tidak berdokumen dan telah berkembang ke titik di " +"mana mereka sangat sulit untuk dikembangkan oleh pengembang baru." + +msgid "" +"The code can be supplied as modified neutron server image, or plugin can be " +"mounted to original image. The :code:`manifests` section in :code:`neutron/" +"values.yaml` should be enabled for below components:" +msgstr "" +"Kode dapat diberikan sebagai image server neutron yang dimodifikasi, atau " +"plugin dapat dipasang ke image asli. Bagian :code:`manifests` dalam :code:" +"`neutron/values.yaml` harus diaktifkan untuk komponen di bawah ini:" + +msgid "" +"The containerized Kubelet cannot survive a restart, as it does not setup " +"mounts correctly." +msgstr "" +"Kubelet containerized tidak dapat selamat dari restart, karena ia tidak " +"memasang mount dengan benar." + +msgid "" +"The credentials for the registry could be exposed by running the kubectl " +"command: kubectl get secret --output=\"jsonpath={.data.\\." +"dockerconfigjson}\" | base64 --decode" +msgstr "" +"Kredensial untuk registri dapat diekspos dengan menjalankan perintah " +"kubectl: kubectl get secret --output=\"jsonpath={.data.\\." +"dockerconfigjson}\" | base64 --decode" + +msgid "" +"The default ``values.yaml`` need to expose those abilities, by adding a new " +"series of keys/values to add the necessary features." +msgstr "" +"Default ``values.yaml`` perlu mengekspos kemampuan itu, dengan menambahkan " +"serangkaian keys/values baru untuk menambahkan fitur yang diperlukan." + +msgid "The detailed proposes change are described as following:" +msgstr "Usulan perubahan yang rinci dijelaskan sebagai berikut:" + +msgid "" +"The developer documentation in OpenStack-Helm should be updated to guide key " +"ordering on value files." +msgstr "" +"Dokumentasi pengembang di OpenStack-Helm harus diperbarui untuk memandu " +"pengurutan kunci pada file nilai." + +msgid "" +"The developer documentation in OpenStack-Helm should be updated to match the " +"gated developer deploy process." +msgstr "" +"Dokumentasi pengembang di OpenStack-Helm harus diperbarui agar sesuai dengan " +"proses penerapan pengembang yang terjaga keamanannya." + +msgid "The existing schema for images is the following:" +msgstr "Skema yang ada untuk image adalah sebagai berikut:" + +msgid "" +"The following work items need to be completed for this Specification to be " +"implemented." +msgstr "" +"Item pekerjaan berikut ini perlu diselesaikan agar Spesifikasi ini dapat " +"diimplementasikan." + +msgid "" +"The following work items need to be completed for this specification to be " +"implemented." +msgstr "" +"Item pekerjaan berikut ini perlu diselesaikan agar spesifikasi ini dapat " +"diimplementasikan." + +msgid "" +"The last thing to be considered is VM network virtualization. What engine " +"does SDN use? It is OpenVSwitch, Linux Bridges or l3 routing (no l2 " +"connectivity). If SDN is using the OpenVSwitch, it can take advantage of " +"existing OVS daemonsets. Any modification that would be required to OVS " +"manifests can be included in base Neutron chart as a configurable option. In " +"that way, the features of OVS can be shared between different SDNs. When " +"using the OVS, default Neutron L2 agent should be disabled, but OVS-DB and " +"OVS-vswitchd can be left enabled." +msgstr "" +"Hal terakhir yang harus dipertimbangkan adalah VM network virtualization. " +"Mesin apa yang SDN gunakan? Ini adalah OpenVSwitch, Linux Bridges atau l3 " +"routing (tanpa konektivitas l2). Jika SDN menggunakan OpenVSwitch, ia dapat " +"memanfaatkan daemonset OVS yang ada. Setiap modifikasi yang akan diperlukan " +"untuk manifes OVS dapat dimasukkan dalam chart Neutron dasar sebagai opsi " +"yang dapat dikonfigurasi. Dengan cara itu, fitur OVS dapat dibagi antara SDN " +"yang berbeda. Saat menggunakan OVS, agen Neutron L2 default harus " +"dinonaktifkan, tetapi OVS-DB dan OVS-vswitchd dapat dibiarkan aktif." + +msgid "" +"The monolithic Ceph chart does not allow for following Ceph upgrade best " +"practices, namely to upgrade Mons, OSDs, and client services in that order. " +"The Ceph chart must therefore be split into at least three charts (one for " +"each of the above upgrade phases) prior to 1.0 to ensure smooth in-place " +"upgradability." +msgstr "" +"Chart Ceph monolitik tidak memungkinkan untuk mengikuti praktik terbaik " +"upgrade Ceph, yaitu untuk upgrade Mons, OSD, dan layanan klien dalam urutan " +"itu. Oleh karena itu, Ceph chart harus dibagi menjadi setidaknya tiga chart " +"(satu untuk masing-masing fase peningkatan di atas) sebelum 1.0 untuk " +"memastikan kelancaran upgrade in-place." + +msgid "" +"The move to Zuulv3 native operation of the OpenStack-Helm gates mean there " +"would be no code reuse between the gate and developer environments, so " +"supporting the existing code for Zuulv2 will incur significant tech-debt." +msgstr "" +"Perpindahan ke operasi asli Zuulv3 dari gate OpenStack-Helm berarti tidak " +"akan ada kode yang digunakan kembali antara gate dan lingkungan pengembang, " +"sehingga mendukung kode yang ada untuk Zuulv2 akan menimbulkan tech-debt " +"yang signifikan." + +msgid "" +"The option ``enabled:`` under ``auth:`` and the manifest ``secret_registry:" +"`` provide the ability for operator to determine whether they would like to " +"have secrets generated and passed to kubernetes for pulling images." +msgstr "" +"Opsi ``enabled:`` di bawah ``auth:`` dan manifes ``secret_registry:`` " +"memberikan kemampuan bagi operator untuk menentukan apakah mereka ingin " +"memiliki rahasia yang dihasilkan dan diteruskan ke kubernetes untuk menarik " +"image." + +msgid "" +"The performance aspect of these point are restricted to deployment, and have " +"no performance impact on operations." +msgstr "" +"Aspek kinerja point ini dibatasi untuk penggunaan, dan tidak memiliki dampak " +"kinerja pada operasi." + +msgid "The proposal includes the following:" +msgstr "Proposal tersebut meliputi:" + +msgid "The proposed requirements for a 1.0 release are as follows:" +msgstr "Persyaratan yang diusulkan untuk rilis 1.0 adalah sebagai berikut:" + +msgid "" +"The proposes change would be to add in :code:`neutron/values.yaml` new " +"section with boolean values describing which Neutron's Kubernetes resources " +"should be enabled:" +msgstr "" +"Perubahan yang diajukan adalah menambahkan :code:`neutron/values.yaml` " +"bagian baru dengan nilai boolean yang menggambarkan sumber daya Kubernet " +"Neutron mana yang harus diaktifkan:" + +msgid "The requirements for a logging collector/aggregator include:" +msgstr "Persyaratan untuk kolektor/agregator logging meliputi:" + +msgid "The requirements for a logging platform include:" +msgstr "Persyaratan untuk platform logging meliputi:" + +msgid "The requirements for a monitoring platform include:" +msgstr "Persyaratan untuk platform pemantauan meliputi:" + +msgid "" +"The secret would not be created with the default option ``enabled: false`` " +"and ``secret_registry: true``. To enable secret creation, operator should " +"override ``enabled:`` to true. The above example shows the default " +"credentials, operator should override the ``username:`` and ``password:`` " +"under ``auth:`` section to provide their own credentials." +msgstr "" +"Rahasia tidak akan dibuat dengan opsi default ``enabled: false`` dan " +"``secret_registry: true``. Untuk mengaktifkan pembuatan rahasia, operator " +"harus mengganti ``enabled:`` menjadi true. Contoh di atas menunjukkan " +"kredensial default, operator harus mengganti ``username:`` and ``password:" +"`` di bawah bagian ``auth:`` untuk memberikan kredensial mereka sendiri." + +msgid "" +"The testing will be performed by the OpenStack-Helm gate to demonstrate the " +"sidecar container correctly routes traffic to the correct services." +msgstr "" +"Pengujian akan dilakukan oleh gate OpenStack-Helm untuk mendemonstrasikan " +"sidecar container dengan benar mengarahkan lalu lintas ke layanan yang benar." + +msgid "" +"The top-level keys are based on the organizational keys common to all charts " +"in the openstack-helm repositories. The top-level keys are strictly ordered " +"according to function, which creates a common organization pattern between " +"all charts." +msgstr "" +"Top-level keys didasarkan pada kunci organisasi yang umum untuk semua chart " +"di repositori openstack-helm. Top-level keys diatur secara ketat sesuai " +"dengan fungsinya, yang menciptakan pola organisasi yang sama di antara semua " +"chart." + +msgid "" +"Then, add manifest ``secret-registry.yaml`` in ``templates/`` to leverage " +"the function that will be added in helm-toolkit to create the secret. For " +"example:" +msgstr "" +"Kemudian, tambahkan manifes ``secret-registry.yaml`` di ``templates/`` untuk " +"meningkatkan fungsi yang akan ditambahkan dalam helm-toolkit untuk membuat " +"rahasia. Sebagai contoh:" + +msgid "" +"Then, inside Kubernetes manifests, add global if statement, deciding if " +"given manifest should be declared on Kubernetes API, for example :code:" +"`neutron/templates/daemonset-ovs-agent.yaml`:" +msgstr "" +"Kemudian, di dalam manifes Kubernetes, tambahkan global if statement, " +"putuskan jika manifes yang diberikan harus dideklarasikan pada API " +"Kubernetes, misalnya :code:`neutron/templates/daemonset-ovs-agent.yaml`:" + +msgid "" +"There is no significant performance impact as the traffic will be locally " +"routed (via 127.0.0.1) and may potentially improve performance for services " +"whose native TLS handling is inefficient." +msgstr "" +"Tidak ada dampak kinerja yang signifikan karena lalu lintas akan dirutekan " +"secara lokal (melalui 127.0.0.1) dan berpotensi meningkatkan kinerja untuk " +"layanan yang penanganan TLS native tidak efisien." + +msgid "" +"There will be no security impact, as it will deploy the charts in OpenStack-" +"Helm[-infra/-addons] upon a reference KubeADM administered cluster." +msgstr "" +"Tidak akan ada dampak keamanan, karena akan menyebarkan grafik di OpenStack-" +"Helm[-infra/-addons] pada cluster yang dikelola KubeADM referensi" + +msgid "This Ceph cluster will be used by Cinder and Glance as storage backend." +msgstr "" +"Cluster Ceph ini akan digunakan oleh Cinder dan Glance sebagai backend " +"penyimpanan." + +msgid "" +"This Ceph cluster will be used for k8s RBD storage (pvc). This can be used " +"by entire Kubernetes cluster." +msgstr "" +"Cluster Ceph ini akan digunakan k8s RBD storage (pvc). Ini dapat digunakan " +"oleh seluruh cluster Kubernetes." + +msgid "This approach:" +msgstr "Pendekatan ini:" + +msgid "" +"This deployment process will be gated, to ensure that the development the " +"environment is consistently working against ``master`` for the OpenStack-" +"Helm repositories." +msgstr "" +"Proses deployment ini akan terjaga keamanannya, untuk memastikan bahwa " +"pengembangan lingkungan bekerja secara konsisten terhadap ``master`` untuk " +"repositori OpenStack-Helm." + +msgid "" +"This enhances the system's security design by allowing pods with services " +"that cannot natively manage TLS to secure the traffic to the service pod." +msgstr "" +"Ini meningkatkan desain keamanan sistem dengan memungkinkan pod dengan " +"layanan yang tidak dapat mengelola TLS untuk mengamankan lalu lintas ke pod " +"layanan." + +msgid "This feature will not affect the performance of OpenStack-Helm." +msgstr "Fitur ini tidak akan mempengaruhi kinerja OpenStack-Helm." + +msgid "" +"This guide shows how to setup multiple Ceph clusters. One Ceph cluster will " +"be used for k8s RBD storage and while other Ceph cluster will be for tenant " +"facing storage backend for Cinder and Glance." +msgstr "" +"Panduan ini menunjukkan cara mengatur multiple cluster Ceph. Satu cluster " +"Ceph akan digunakan untuk penyimpanan RBD k8s dan sementara cluster Ceph " +"lainnya akan untuk penyewa menghadapi backend penyimpanan untuk Cinder dan " +"Glance." + +msgid "" +"This spec describes a point-in-time readiness for OpenStack-Helm 1.0, after " +"which it will be for historical reference only." +msgstr "" +"Spesifikasi ini menggambarkan kesiapan point-in-time untuk OpenStack-Helm " +"1.0, setelah itu hanya untuk referensi sejarah." + +msgid "" +"This spec describes a wide variety of self-contained work efforts, which " +"will be implemented individually by the whole OpenStack-Helm team." +msgstr "" +"Spesifikasi ini menjelaskan berbagai upaya kerja mandiri, yang akan " +"dilaksanakan secara individual oleh seluruh tim OpenStack-Helm." + +msgid "" +"This spec lays out the criteria for a stable and reliable 1.0 release, which " +"can serve as the basis for real-world use as well as ongoing development. " +"The alternative approaches would be to either iterate indefinitely without " +"defining a 1.0 release, which would fail to signal to operators the point at " +"which the platform is ready for real-world use; or, to define a 1.0 release " +"which fails to satisfy key features which real-world operators need." +msgstr "" +"Spesifikasi ini menjabarkan kriteria untuk rilis 1.0 yang stabil dan andal, " +"yang dapat berfungsi sebagai dasar untuk penggunaan di real-world serta " +"pengembangan yang berkelanjutan. Pendekatan alternatif adalah untuk " +"melakukan iterate tanpa batas tanpa mendefinisikan rilis 1.0, yang akan " +"gagal memberi sinyal kepada operator, titik di mana platform siap untuk " +"penggunaan real-world; atau, untuk menentukan rilis 1.0 yang gagal memenuhi " +"fitur utama yang dibutuhkan operator real-world." + +msgid "" +"This spec will be worked helm chart by helm chart, starting with keystone." +msgstr "" +"Spesifikasi ini akan dikerjakan helm chart dengan helm chart, dimulai dengan " +"keystone." + +msgid "" +"This specification also proposes to restrict the addition of any new top-" +"level keys in charts across all OpenStack-Helm repositories, in order to " +"maintain the common structure the ordering creates. The addition of a new " +"top-level key shall be agreed upon by the OpenStack-Helm team on a case-by-" +"case basis. The addition of any new top-level keys should be documented, " +"and this specification shall be amended to account for any added keys." +msgstr "" +"Spesifikasi ini juga mengusulkan untuk membatasi penambahan top-level keys " +"baru dalam chart di semua repositori OpenStack-Helm, untuk menjaga struktur " +"umum yang dibuat oleh pengurutan. Penambahan top-level key yang baru harus " +"disetujui oleh tim OpenStack-Helm berdasarkan kasus per kasus. Penambahan " +"top-level key yang baru harus didokumentasikan, dan spesifikasi ini harus " +"diubah untuk memperhitungkan setiap kunci yang ditambahkan." + +msgid "" +"This specification proposes defining entries in the values.yaml file into " +"two categories: top-level keys, and their children (sub-level) keys." +msgstr "" +"Spesifikasi ini mengusulkan pendefinisian entri dalam file values.yaml ke " +"dalam dua kategori: top-level keys, dan their children (sub-level) keys." + +msgid "" +"This specification proposes introducing a uniform values.yaml structure " +"across all charts in openstack-helm, openstack-helm-infra, and openstack-" +"helm-addons, with the goal of reducing the complexities of working across " +"multiple charts and reducing the effort for creating new charts." +msgstr "" +"Spesifikasi ini mengusulkan untuk memperkenalkan nilai yang seragam. " +"Struktur yaml di semua chart di openstack-helm, openstack-helm-infra, dan " +"openstack-helm-addons, dengan tujuan mengurangi kompleksitas bekerja di " +"berbagai chart dan mengurangi upaya untuk menciptakan chart yang baru." + +msgid "" +"This specification proposes to add a nginx sidecar container to the pod for " +"service that requires the tls offloading. The nginx can be used to handle " +"the TLS offoading and terminate the TLS connection, and routes the traffic " +"to the service via localhost (127.0.0.1)." +msgstr "" +"Spesifikasi ini mengusulkan untuk menambahkan kontainer sidecar nginx ke pod " +"untuk layanan yang memerlukan pembongkaran tls. Nginx dapat digunakan untuk " +"menangani pemutusan TLS dan mengakhiri koneksi TLS, dan merutekan (route) " +"lalu lintas ke layanan melalui localhost (127.0.0.1)." + +msgid "" +"This specification will address enablement of LinuxBridge network " +"virtualization for OpenStack Helm (OSH). LinuxBridge is second available " +"networking technology in Neutron's reference architecture. The first one is " +"OVS, that is already implemented in OSH." +msgstr "" +"Spesifikasi ini akan membahas pemberlakuan virtualisasi jaringan LinuxBridge " +"untuk OpenStack Helm (OSH). LinuxBridge adalah teknologi jaringan kedua yang " +"tersedia dalam arsitektur referensi Neutron. Yang pertama adalah OVS, yang " +"sudah diimplementasikan dalam OSH." + +msgid "Time-series database for collected metrics" +msgstr "Database time-serie untuk metrik yang dikumpulkan" + +msgid "Time-series database for logs collected" +msgstr "Database time-series untuk log dikumpulkan" + +msgid "" +"To be able to install Neutron with multiple possible SDNs as networking " +"plugin, Neutron chart should be modified to enable installation of base " +"services with decomposable approach. This means that operator can define " +"which components from base Neutron chart should be installed, and which " +"should not. This plus proper configuration of Neutron chart would enable " +"operator to flexibly provision OpenStack with chosen SDN." +msgstr "" +"Untuk dapat menginstal Neutron dengan beberapa kemungkinan SDN sebagai " +"plugin jaringan, chart Neutron harus dimodifikasi untuk memungkinkan " +"instalasi layanan dasar dengan pendekatan yang dapat didekomposisi. Ini " +"berarti bahwa operator dapat menentukan komponen mana dari chart Neutron " +"dasar yang harus dipasang, dan mana yang tidak. Konfigurasi chart Neutron " +"plus yang tepat ini akan memungkinkan operator untuk secara fleksibel " +"menyediakan OpenStack dengan SDN yang dipilih." + +msgid "" +"To be able to pull images from an OCI image registry which has the " +"authentication turned on, kubernetes needs credentials. For each chart, a " +"new ``endpoints:`` entry could be added in ``values.yaml`` to provide image " +"credentials, a secret needs to be generated to hold the credentials and the " +"``imagePullSecrets:`` field should be added in each service account to " +"specify which secret should be used to get the credentials from when pulling " +"images by kubelet." +msgstr "" +"Untuk dapat menarik image dari registri image OCI yang otentikasi " +"dihidupkan, kubernetes memerlukan kredensial. Untuk setiap chart, entri " +"``endpoints:`` baru dapat ditambahkan dalam ``values.yaml`` untuk memberikan " +"kredensial image, rahasia perlu dibuat untuk memegang kredensial dan field " +"``imagePullSecrets:`` harus berupa ditambahkan di setiap akun layanan untuk " +"menentukan rahasia mana yang harus digunakan untuk mendapatkan kredensial " +"mulai saat menarik image dengan kubelet." + +msgid "" +"To enable new SDN solution, there should be separate chart created, which " +"would handle the deployment of service, setting up the database and any " +"related networking functionality that SDN is providing." +msgstr "" +"Untuk mengaktifkan solusi SDN baru, harus ada chart terpisah yang dibuat, " +"yang akan menangani penyebaran layanan, pengaturan basis data dan segala " +"fungsi jaringan terkait yang disediakan oleh SDN." + +msgid "" +"To facilitate effective collaboration and communication across the OpenStack-" +"Helm community team, work items for the enhancements above will be captured " +"in Storyboard. Therefore, migration from Launchpad to Storyboard must be " +"accomplished prior to the 1.0 release. Going forward, Storyboard will be " +"leveraged as a tool to collaboratively define and communicate the OpenStack-" +"Helm roadmap." +msgstr "" +"Untuk memfasilitasi kolaborasi dan komunikasi yang efektif di seluruh tim " +"komunitas OpenStack-Helm, item pekerjaan untuk peningkatan di atas akan " +"ditangkap di Storyboard. Oleh karena itu, migrasi dari Launchpad ke " +"Storyboard harus diselesaikan sebelum rilis 1.0. Ke depan, Storyboard akan " +"dimanfaatkan sebagai alat untuk secara kolaboratif mendefinisikan dan " +"mengkomunikasikan roadmap OpenStack-Helm." + +msgid "" +"To minimize the performance impacts, the following should be considered:" +msgstr "" +"Untuk meminimalkan dampak kinerja, hal-hal berikut harus dipertimbangkan:" + +msgid "" +"To successfully enforce the ordering defined here, our gates need a method " +"for validating the ordering and the schema of all values.yaml files. " +"Without such a mechanism, the overhead associated with properly reviewing " +"and validating any changes to the structure will be substantial. A tool, " +"such as yamllint, would provide this functionality and remove the need to " +"write a custom validation tool" +msgstr "" +"Untuk berhasil menegakkan pengurutan yang ditentukan di sini, gate kami " +"memerlukan metode untuk memvalidasi pengurutan dan skema semua file values." +"yaml. Tanpa mekanisme seperti itu, overhead yang terkait dengan meninjau dan " +"memvalidasi setiap perubahan pada struktur akan menjadi substansial. Alat, " +"seperti yamllint, akan menyediakan fungsi ini dan menghapus kebutuhan untuk " +"menulis alat validasi kustom." + +msgid "Top-level keys are placed in this order:" +msgstr "Top-level keys ditempatkan dalam urutan ini:" + +msgid "Topic: osh-1.0-requirements_" +msgstr "Topic: osh-1.0-requirements_" + +msgid "Trigger alerts when desired replicas fall below required number" +msgstr "" +"Peringatan pemicu ketika replika yang diinginkan berada di bawah angka yang " +"dibutuhkan" + +msgid "Trigger alerts when services become unavailable or unresponsive" +msgstr "" +"Pemicu peringatan ketika layanan menjadi tidak tersedia atau tidak responsif" + +msgid "Under storage: mon directory have been updated." +msgstr "Di bawah penyimpanan: direktori mon telah diperbarui." + +msgid "" +"Under storageclass section, values for following have been updated: " +"ceph_configmap_name, admin_secret_name, admin_secret_namespace, " +"user_secret_name" +msgstr "" +"Di bawah bagian storageclass, nilai untuk yang berikut telah diperbarui: " +"ceph_configmap_name, admin_secret_name, admin_secret_namespace, " +"user_secret_name" + +msgid "" +"Update ``helm toolkit`` to provide snippet to create the nginx sidecar " +"container for the services that require it." +msgstr "" +"Perbarui ``helm toolkit`` untuk memberikan cuplikan untuk membuat nginx " +"sidecar container untuk layanan yang membutuhkannya." + +msgid "" +"Update helm-toolkit serviceaccount template to pass the secret in a " +"conditional" +msgstr "" +"Update templat akun layanan helm-toolkit untuk memberikan rahasia secara " +"bersyarat" + +msgid "" +"Update helm-toolkit to provide manifest to create secret for registry " +"authentication" +msgstr "" +"Update helm-toolkit untuk menyediakan manifes untuk membuat rahasia untuk " +"otentikasi registri" + +msgid "Update of Developer Documentation" +msgstr "Update Dokumentasi Pengembang" + +msgid "" +"Update of Makefile for OpenStack-Helm-Infra to allow modular deployment of " +"components" +msgstr "" +"Update Makefile untuk OpenStack-Helm-Infra sehingga memungkinkan penempatan " +"komponen secara modular" + +msgid "Update of developer documentation" +msgstr "Update dokumentasi pengembang" + +msgid "Update relevant Documentation." +msgstr "Update Dokumentasi yang relevan." + +msgid "Update script as following:" +msgstr "Update skrip sebagai berikut:" + +msgid "Update script overrides as following:" +msgstr "Update override skrip sebagai berikut:" + +msgid "Update script to include namespace ``tenant-ceph`` as shown below." +msgstr "" +"Update skrip untuk memasukkan namespace ``tenant-ceph`` seperti yang " +"ditunjukkan di bawah ini." + +msgid "Update script with following overrides:" +msgstr "Update skrip dengan override berikut:" + +msgid "Update script's override section with following:" +msgstr "Update bagian override skrip dengan yang berikut:" + +msgid "Update service charts to use the updated ``helm toolkit``." +msgstr "" +"Perbarui chart layanan untuk menggunakan yang diperbarui ``helm toolkit``." + +msgid "Use Cases" +msgstr "Use Case" + +msgid "Use case" +msgstr "Use case" + +msgid "Use cases" +msgstr "Gunakan kasus" + +msgid "" +"Use default overrides and execute following scripts as per OSH guide steps:" +msgstr "" +"Gunakan override default dan jalankan skrip berikut sesuai langkah panduan " +"OSH:" + +msgid "VM networking performance would be dependent of SDN used." +msgstr "Kinerja jaringan VM akan tergantung pada SDN yang digunakan." + +msgid "" +"VM networking performance would be dependent on linux bridge implementation." +msgstr "Kinerja jaringan VM akan tergantung pada implementasi jembatan linux." + +msgid "Values File Ordering" +msgstr "Nilai Pengurutan File" + +msgid "" +"Version requirements for the following must be documented and maintained:" +msgstr "" +"Persyaratan versi untuk yang berikut ini harus didokumentasikan dan " +"dipelihara:" + +msgid "" +"Visualize logged events to determine if an event is recurring or an outlier" +msgstr "" +"Visualisasikan event yang dicatat untuk menentukan apakah suatu event " +"berulang atau outlier" + +msgid "" +"Visualize performance to identify trends in traffic or utilization over time" +msgstr "" +"Visualisasikan kinerja untuk mengidentifikasi tren lalu lintas atau " +"pemanfaatan seiring waktu" + +msgid "We are disabling rbd and cephfs provisioners." +msgstr "Kami menonaktifkan provisioner rbd dan cephfs." + +msgid "" +"We need to adapt all the helm charts to remove the hard-coded bits, be image " +"agnostic, to allow users to bring their own images." +msgstr "" +"Kita perlu mengadaptasi semua bagan helm untuk menghapus bit yang dikodekan, " +"menjadi agnostik image, untuk memungkinkan pengguna membawa image mereka " +"sendiri." + +msgid "Web UI (horizon)" +msgstr "Web UI (horizon)" + +msgid "" +"When possible, ``values_overrides/`` will refer to existing ``helm-toolkit`` " +"functions to avoid repeating ourselves." +msgstr "" +"Jika memungkinkan, ``values_overrides/`` akan merujuk ke fungsi ``helm-" +"toolkit`` yang ada untuk menghindari pengulangan diri." + +msgid "Work Items" +msgstr "Work Items" + +msgid "" +"Work is underway to refactor common manifest patterns into reusable snippets " +"in Helm-Toolkit. The following manifests have yet to be combined:" +msgstr "" +"Pekerjaan sedang dilakukan untuk memperbaiki pola manifes umum menjadi " +"potongan yang dapat digunakan kembali di Helm-Toolkit. Manifes berikut belum " +"digabungkan:" + +msgid "Worker Deployments" +msgstr "Worker Deployments" + +msgid "``040-ceph-ns-activate.sh``" +msgstr "``040-ceph-ns-activate.sh``" + +msgid "``050-mariadb.sh``" +msgstr "``050-mariadb.sh``" + +msgid "``060-rabbitmq.sh``" +msgstr "``060-rabbitmq.sh``" + +msgid "``070-memcached.sh``" +msgstr "``070-memcached.sh``" + +msgid "``080-keystone.sh``" +msgstr "``080-keystone.sh``" + +msgid "``Ceph ConfigMaps``" +msgstr "``Ceph ConfigMaps``" + +msgid "``Ceph Pods``" +msgstr "``Ceph Pods``" + +msgid "``Ceph Status``" +msgstr "``Ceph Status``" + +msgid "``Ceph endpoints``" +msgstr "``Ceph endpoints``" + +msgid "``Ceph for RBD related labels:``" +msgstr "``Ceph for RBD related labels:``" + +msgid "``Ceph for Tenant related labels:``" +msgstr "``Ceph for Tenant related labels:``" + +msgid "``Ceph secrets``" +msgstr "``Ceph secrets``" + +msgid "``Ceph services``" +msgstr "``Ceph services``" + +msgid "``Openstack PV list``" +msgstr "``Openstack PV list``" + +msgid "``Openstack Pods:``" +msgstr "``Openstack Pods:``" + +msgid "``Openstack endpoints``" +msgstr "``Openstack endpoints``" + +msgid "``Openstack secrets``" +msgstr "``Openstack secrets``" + +msgid "``Openstack services``" +msgstr "``Openstack services``" + +msgid "``Storage on node1, node2, node3:``" +msgstr "``Storage on node1, node2, node3:``" + +msgid "``Storage on node4, node5, node6:``" +msgstr "``Storage on node4, node5, node6:``" + +msgid "``ceph-mon-etc (ceph.conf)``" +msgstr "``ceph-mon-etc (ceph.conf)``" + +msgid "" +"``cephfs_provisioner: false`` and ``provision_storage_class: false`` are set " +"to false to disable cephfs. ``deployment_mds: false`` is set to disable ceph-" +"mds" +msgstr "" +"``cephfs_provisioner: false`` dan ``provision_storage_class: false`` disetel " +"ke false untuk menonaktifkan cephfs. ``deployment_mds: false`` diatur untuk " +"menonaktifkan ceph-mds." + +msgid "``for CHART in ceph-mon ceph-osd ceph-client; do``" +msgstr "``for CHART in ceph-mon ceph-osd ceph-client; do``" + +msgid "" +"``k8s node list with labels`` After applying above labels, node labels " +"should look like following." +msgstr "" +"``k8s node list with labels`` Setelah menerapkan label di atas, label node " +"akan terlihat seperti berikut." + +msgid "``k8s storageclass``" +msgstr "``k8s storageclass``" + +msgid "``netstat ceph mon port``" +msgstr "``netstat ceph mon port``" + +msgid "`values.yaml` changes" +msgstr "`values.yaml` changes" + +msgid "bootstrap * sub-keys (alphabetical order)" +msgstr "bootstrap * sub-keys (sesuai abjad)" + +msgid "ceph" +msgstr "ceph" + +msgid "conf * sub-keys (up-to-chart-developer)" +msgstr "conf * sub-keys (up-to-chart-developer)" + +msgid "dependencies * sub-keys (alphabetical order)" +msgstr "dependencies * sub-keys (sesuai abjad)" + +msgid "" +"diagram link: https://github.com/sktelecom-oslab/docs/blob/master/images/" +"fluentbit-fluentd-diagram.png" +msgstr "" +"diagram link: https://github.com/sktelecom-oslab/docs/blob/master/images/" +"fluentbit-fluentd-diagram.png" + +msgid "endpoints * sub-keys (alphabetical order)" +msgstr "endpoints * sub-keys (sesuai abjad)" + +msgid "etcd" +msgstr "etcd" + +msgid "evrardjp" +msgstr "evrardjp" + +msgid "fluentbit-fluentd logging architecture" +msgstr "arsitektur logging fluentbit-fluentd" + +msgid "" +"https://blueprints.launchpad.net/openstack-helm/+spec/developer-environment" +msgstr "" +"https://blueprints.launchpad.net/openstack-helm/+spec/developer-environment" + +msgid "https://kubernetes.io/docs/concepts/containers/images" +msgstr "https://kubernetes.io/docs/concepts/containers/images" + +msgid "" +"https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-" +"account/#add-imagepullsecrets-to-a-service-account" +msgstr "" +"https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-" +"account/#add-imagepullsecrets-to-a-service-account" + +msgid "https://review.openstack.org/#/c/552485/" +msgstr "https://review.openstack.org/#/c/552485/" + +msgid "https://storyboard.openstack.org/#!/story/2005130" +msgstr "https://storyboard.openstack.org/#!/story/2005130" + +msgid "images * sub-keys (alphabetical order)" +msgstr "images * sub-keys (sesuai abjad)" + +msgid "ingress" +msgstr "ingress" + +msgid "k8s namespace: ceph" +msgstr "k8s namespace: ceph" + +msgid "k8s namespace: tenant-ceph" +msgstr "k8s namespace: tenant-ceph" + +msgid "k8s node labels:" +msgstr "k8s node labels:" + +msgid "korzen (Artur Korzeniewski)" +msgstr "korzen (Artur Korzeniewski)" + +msgid "labels * sub-keys (alphabetical order)" +msgstr "labels * sub-keys (sesuai abjad)" + +msgid "ldap" +msgstr "ldap" + +msgid "libvirt" +msgstr "libvirt" + +msgid "manifests * sub-keys (alphabetical order)" +msgstr "manifests * sub-keys (sesuai abjad)" + +msgid "mariadb" +msgstr "mariadb" + +msgid "mattmceuen (Matt McEuen ) for coordination" +msgstr "mattmceuen (Matt McEuen ) untuk koordinasi" + +msgid "memcached" +msgstr "memcached" + +msgid "metric port: 9283" +msgstr "metric port: 9283" + +msgid "metric port: 9284" +msgstr "metric port: 9284" + +msgid "mgr endpoint port: 7000" +msgstr "mgr endpoint port: 7000" + +msgid "mgr endpoint port: 7001" +msgstr "mgr endpoint port: 7001" + +msgid "mon endpoint port: 6789" +msgstr "mon endpoint port: 6789" + +msgid "mon endpoint port: 6790" +msgstr "mon endpoint port: 6790" + +msgid "mon_addr and mon_host have non default mon port 6790." +msgstr "mon_addr and mon_host memiliki port mon standar 6790." + +msgid "mongodb" +msgstr "mongodb" + +msgid "monitoring * sub-keys (alphabetical order)" +msgstr "monitoring * sub-keys (sesuai abjad)" + +msgid "network * sub-keys (alphabetical order)" +msgstr "network * sub-keys (sesuai abjad)" + +msgid "no ceph-mds" +msgstr "no ceph-mds" + +msgid "no ceph-mds and ceph-rgw" +msgstr "no ceph-mds dan ceph-rgw" + +msgid "no storage classes" +msgstr "no storage classes" + +msgid "" +"openstack-control-plane=enabled, ceph-mon=enabled, ceph-mgr=enabled, ceph-" +"rgw=enabled, ceph-mds=enabled, ceph-osd=enabled" +msgstr "" +"openstack-control-plane=enabled, ceph-mon=enabled, ceph-mgr=enabled, ceph-" +"rgw=enabled, ceph-mds=enabled, ceph-osd=enabled" + +msgid "" +"openstack-data-plane=enabled, openstack-compute-node=enabled, ceph-osd-" +"tenant=enabled, openstack-data-plane=enabled" +msgstr "" +"openstack-data-plane=enabled, openstack-compute-node=enabled, ceph-osd-" +"tenant=enabled, openstack-data-plane=enabled" + +msgid "openvswitch" +msgstr "openvswitch" + +msgid "pod * sub-keys (alphabetical order)" +msgstr "pod * sub-keys (sesuai abjad)" + +msgid "" +"portdirect (Pete Birley ) for the release management spec " +"[2]_" +msgstr "" +"portdirect (Pete Birley ) untuk spesifikasi manajemen " +"rilis [2] _" + +msgid "portdirect (Pete Birley)" +msgstr "portdirect (Pete Birley)" + +msgid "postgresql" +msgstr "postgresql" + +msgid "" +"powerds (DaeSeong Kim ) for the `values.yaml` ordering " +"spec [1]_" +msgstr "" +"powerds (DaeSeong Kim ) untuk `values.yaml` ordering " +"spec [1]_" + +msgid "" +"powerds0111 (DaeSeong Kim ) srwilkers (Steve Wilkerson " +")" +msgstr "" +"powerds0111 (DaeSeong Kim ) srwilkers (Steve Wilkerson " +")" + +msgid "rabbitmq" +msgstr "rabbitmq" + +msgid "" +"randeep.jalli (Randeep Jalli ) and renmak (Renis Makadia " +") for splitting up the Ceph chart" +msgstr "" +"randeep.jalli (Randeep Jalli ) dan renmak (Renis Makadia " +") untuk membagi chart Ceph" + +msgid "" +"rwellum (Rich Wellum ) for coordination of Storyboard " +"adoption" +msgstr "" +"rwellum (Rich Wellum ) untuk koordinasi adopsi " +"Storyboard" + +msgid "secrets * sub-keys (alphabetical order)" +msgstr "secrets * sub-keys (sesuai abjad)" + +msgid "services do not handle TLS offloading and termination," +msgstr "layanan tidak menangani pemuatan dan pemutusan TLS," + +msgid "" +"services whose native handling of TLS offloading and termination cause major " +"performance impact, for example, eventlet." +msgstr "" +"layanan dengan penanganan native pemuatan dan pemutusan TLS menyebabkan " +"dampak kinerja utama, misalnya, eventlet." + +msgid "" +"srwilker (Steve Wilkerson) portdirect (Pete Birley) lr699s (Larry Rensing)" +msgstr "" +"srwilker (Steve Wilkerson) portdirect (Pete Birley) lr699s (Larry Rensing)" + +msgid "storage classes: general (rbd based for pvc)" +msgstr "storage classes: general (rbd based for pvc)" + +msgid "sungil (Sungil Im) jayahn (Jaesuk Ahn)" +msgstr "sungil (Sungil Im) jayahn (Jaesuk Ahn)" + +msgid "" +"tenant-ceph-control-plane=enabled, ceph-mon-tenant=enabled, ceph-mgr-" +"tenant=enabled, ceph-rgw-tenant=enabled" +msgstr "" +"tenant-ceph-control-plane=enabled, ceph-mon-tenant=enabled, ceph-mgr-" +"tenant=enabled, ceph-rgw-tenant=enabled" + +msgid "" +"the impact of adding extra conditionals in the helm charts, to deal with " +"multi-distro aspect (if not using the approach above, or when using an " +"alternative approach)" +msgstr "" +"dampak dari penambahan persyaratan extra di helm chart, untuk menangani " +"aspek multi-distro (jika tidak menggunakan pendekatan di atas, atau ketika " +"menggunakan pendekatan alternatif)" + +msgid "" +"the impact of adding functionality in the ``helm-toolkit`` to deal with a " +"common multi-distro aspect (could possibly increase helm chart rendering " +"time)" +msgstr "" +"dampak dari penambahan fungsionalitas dalam ``helm-toolkit`` untuk menangani " +"aspek multi-distro yang umum (mungkin dapat meningkatkan waktu rendering " +"chart helm)" + +msgid "" +"the impact of exposing extra key/values in the helm chart ``values.yaml`` " +"file (could possibly have a deployment speed/ram usage increase)." +msgstr "" +"dampak dari mengekspos key/value tambahan dalam file helm ``values.yaml`` " +"(mungkin bisa memiliki kecepatan deployment / peningkatan penggunaan ram)." diff --git a/doc/source/locale/id/LC_MESSAGES/doc-testing.po b/doc/source/locale/id/LC_MESSAGES/doc-testing.po new file mode 100644 index 0000000000..268abeb58b --- /dev/null +++ b/doc/source/locale/id/LC_MESSAGES/doc-testing.po @@ -0,0 +1,1032 @@ +# suhartono , 2018. #zanata +# suhartono , 2019. #zanata +msgid "" +msgstr "" +"Project-Id-Version: openstack-helm 0.1.1.dev3685\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2022-04-06 21:47+0000\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"PO-Revision-Date: 2019-05-28 12:08+0000\n" +"Last-Translator: suhartono \n" +"Language-Team: Indonesian\n" +"Language: id\n" +"X-Generator: Zanata 4.3.3\n" +"Plural-Forms: nplurals=1; plural=0\n" + +msgid "" +"1) Initial Ceph and OpenStack deployment: Install Ceph and OpenStack charts " +"on 3 nodes (mnode1, mnode2 and mnode3). Capture Ceph cluster status as well " +"as K8s PODs status." +msgstr "" +"1) Penyebaran Ceph dan OpenStack awal: Pasang bagan Ceph dan OpenStack pada " +"3 node (mnode1, mnode2 dan mnode3). Capture Ceph cluster status serta status " +"PODs K8s." + +msgid "" +"1) Node reduction: Shutdown 1 of 3 nodes to simulate node failure. Capture " +"effect of node failure on Ceph as well as other OpenStack services that are " +"using Ceph." +msgstr "" +"1) Node reduction: Shutdown 1 dari 3 node untuk mensimulasikan kegagalan " +"node. Menangkap efek kegagalan node pada Ceph serta layanan OpenStack lain " +"yang menggunakan Ceph." + +msgid "1) Remove out of quorum MON:" +msgstr "1) Hapus dari quorum MON:" + +msgid "" +"2) Node expansion: Apply Ceph and OpenStack related labels to another unused " +"k8 node. Node expansion should provide more resources for k8 to schedule " +"PODs for Ceph and OpenStack services." +msgstr "" +"2) Ekspansi Node: Menerapkan label terkait Ceph dan OpenStack ke nodus k8 " +"yang tidak digunakan lainnya. Perluasan node harus menyediakan lebih banyak " +"sumber daya untuk k8 untuk menjadwalkan POD untuk layanan Ceph dan OpenStack." + +msgid "" +"2) Node reduction (failure): Shutdown 1 of 3 nodes (mnode3) to test node " +"failure. This should cause Ceph cluster to go in HEALTH_WARN state as it has " +"lost 1 MON and 1 OSD. Capture Ceph cluster status as well as K8s PODs status." +msgstr "" +"2) Pengurangan Node (kegagalan): Shutdown 1 dari 3 node (mnode3) untuk " +"menguji kegagalan node. Ini harus menyebabkan Ceph cluster masuk dalam " +"kondisi HEALTH_WARN karena telah kehilangan 1 MON dan 1 OSD. Capture Ceph " +"cluster status serta status PODs K8s." + +msgid "2) Remove down OSD from Ceph cluster:" +msgstr "2) Hapus OSD dari Ceph cluster:" + +msgid "3 Node (VM based) env." +msgstr "3 Node (VM based) env." + +msgid "" +"3) Fix Ceph Cluster: After node expansion, perform maintenance on Ceph " +"cluster to ensure quorum is reached and Ceph is HEALTH_OK." +msgstr "" +"3) Perbaiki Ceph Cluster: Setelah perluasan node, lakukan perawatan pada " +"cluster Ceph untuk memastikan kuorum tercapai dan Ceph adalah HEALTH_OK." + +msgid "" +"3) Node expansion: Add Ceph and OpenStack related labels to 4th node " +"(mnode4) for expansion. Ceph cluster would show new MON and OSD being added " +"to cluster. However Ceph cluster would continue to show HEALTH_WARN because " +"1 MON and 1 OSD are still missing." +msgstr "" +"3) Node ekspansi: Tambahkan Ceph dan OpenStack terkait label ke 4 node " +"(mnode4) untuk ekspansi. Ceph cluster akan menunjukkan MON baru dan OSD yang " +"ditambahkan ke cluster. Namun cluster Ceph akan terus menunjukkan " +"HEALTH_WARN karena 1 MON dan 1 OSD masih hilang." + +msgid "" +"4) Ceph cluster recovery: Perform Ceph maintenance to make Ceph cluster " +"HEALTH_OK. Remove lost MON and OSD from Ceph cluster." +msgstr "" +"4) Ceph cluster recovery: Lakukan Ceph maintenance untuk membuat Ceph " +"cluster HEALTH_OK. Hapus MON dan OSD yang hilang dari cluster Ceph." + +msgid "" +"4. Replace the failed disk with a new one. If you repair (not replace) the " +"failed disk, you may need to run the following:" +msgstr "" +"4. Ganti disk yang gagal dengan yang baru. Jika Anda memperbaiki (bukan " +"mengganti) disk yang gagal, Anda mungkin perlu menjalankan yang berikut:" + +msgid "6 Nodes (VM based) env" +msgstr "6 Nodes (VM based) env" + +msgid "" +"A Ceph Monitor running on voyager3 (whose Monitor database is destroyed) " +"becomes out of quorum, and the mon-pod's status stays in ``Running`` -> " +"``Error`` -> ``CrashLoopBackOff`` while keeps restarting." +msgstr "" +"Monitor Ceph yang berjalan di voyager3 (yang database Monitor-nya dimatikan) " +"menjadi tidak di quorum, dan status mon-pod tetap dalam ``Running`` -> " +"``Error`` -> ``CrashLoopBackOff`` sementara terus restart." + +msgid "" +"Above output shows Ceph cluster in HEALTH_OK with all OSDs and MONs up and " +"running." +msgstr "" +"Output di atas menunjukkan Ceph cluster di HEALTH_OK dengan semua OSD dan " +"MONS aktif dan berjalan." + +msgid "Above output shows that ``osd.1`` is down." +msgstr "Output di atas menunjukkan bahwa ``osd.1`` sedang down." + +msgid "Adding Tests" +msgstr "Menambahkan Tes" + +msgid "" +"Additional information on Helm tests for OpenStack-Helm and how to execute " +"these tests locally via the scripts used in the gate can be found in the " +"gates_ directory." +msgstr "" +"Informasi tambahan tentang tes Helm untuk OpenStack-Helm dan cara melakukan " +"tes ini secara lokal melalui skrip yang digunakan di gate dapat ditemukan di " +"direktori gates_." + +msgid "" +"After 10+ miniutes, Ceph starts rebalancing with one node lost (i.e., 6 osds " +"down) and the status stablizes with 18 osds." +msgstr "" +"Setelah 10+ menit, Ceph mulai menyeimbangkan kembali dengan satu node yang " +"hilang (yaitu, 6 osds turun) dan statusnya stabil dengan 18 osds." + +msgid "After applying labels, let's check status" +msgstr "Setelah menerapkan label, mari periksa status" + +msgid "After reboot (node voyager3), the node status changes to ``NotReady``." +msgstr "" +"Setelah reboot (node voyager3), status node berubah menjadi ``NotReady``." + +msgid "" +"After the host is down (node voyager3), the node status changes to " +"``NotReady``." +msgstr "" +"Setelah host mati (node voyager3), status node berubah menjadi ``NotReady``." + +msgid "All PODs are in running state." +msgstr "Semua POD dalam keadaan berjalan." + +msgid "" +"All tests should be added to the gates during development, and are required " +"for any new service charts prior to merging. All Helm tests should be " +"included as part of the deployment script. An example of this can be seen " +"in this script_." +msgstr "" +"Semua tes harus ditambahkan ke gate selama pengembangan, dan diperlukan " +"untuk chart layanan baru sebelum penggabungan. Semua tes Helm harus " +"dimasukkan sebagai bagian dari skrip pemasangan. Contoh ini dapat dilihat " +"dalam skrip ini_." + +msgid "" +"Also, the pod status of ceph-mon and ceph-osd changes from ``NodeLost`` back " +"to ``Running``." +msgstr "" +"Juga, status pod ceph-mon dan ceph-osd berubah dari ``NodeLost`` kembali ke " +"``Running``." + +msgid "Any Helm tests associated with a chart can be run by executing:" +msgstr "" +"Tes Helm apa pun yang terkait dengan chart dapat dijalankan dengan " +"mengeksekusi:" + +msgid "" +"Any templates for Helm tests submitted should follow the philosophies " +"applied in the other templates. These include: use of overrides where " +"appropriate, use of endpoint lookups and other common functionality in helm-" +"toolkit, and mounting any required scripting templates via the configmap-bin " +"template for the service chart. If Rally tests are not appropriate or " +"adequate for a service chart, any additional tests should be documented " +"appropriately and adhere to the same expectations." +msgstr "" +"Setiap template untuk tes Helm yang diajukan harus mengikuti filosofi yang " +"diterapkan dalam template lain. Ini termasuk: penggunaan menimpa di mana " +"yang sesuai, penggunaan pencarian endpoint dan fungsi umum lainnya dalam " +"helm-toolkit, dan pemasangan semua scripting template yang diperlukan " +"melalui template configmap-bin untuk chart layanan. Jika pengujian Rally " +"tidak sesuai atau memadai untuk chart layanan, pengujian tambahan apa pun " +"harus didokumentasikan dengan tepat dan mematuhi harapan yang sama." + +msgid "" +"As shown above, Ceph status is now HEALTH_OK and shows 3 MONs available." +msgstr "" +"Seperti yang ditunjukkan di atas, status Ceph sekarang HEALTH_OK dan " +"menunjukkan 3 MON tersedia." + +msgid "" +"As shown in Ceph status above, ``osd: 4 osds: 3 up, 3 in`` 1 of 4 OSDs is " +"still down. Let's remove that OSD." +msgstr "" +"Seperti yang ditunjukkan dalam status Ceph di atas, ``osd: 4 osds: 3 up, 3 " +"in`` 1 dari 4 OSDs masih turun. Mari hapus OSD itu." + +msgid "Capture Ceph pods statuses." +msgstr "Capture Ceph pods statuses." + +msgid "Capture Openstack pods statuses." +msgstr "Capture Openstack pods statuses." + +msgid "Capture final Ceph pod statuses:" +msgstr "Capture final Ceph pod statuses:" + +msgid "Capture final Openstack pod statuses:" +msgstr "Capture final Openstack pod statuses:" + +msgid "Case: 1 out of 3 Monitor Processes is Down" +msgstr "Kasus: 1 dari 3 Proses Monitor Sedang Turun" + +msgid "Case: 2 out of 3 Monitor Processes are Down" +msgstr "Kasus: 2 dari 3 Proses Monitor Sedang Turun" + +msgid "Case: 3 out of 3 Monitor Processes are Down" +msgstr "Kasus: 3 dari 3 Proses Monitor Sedang Turun" + +msgid "Case: A OSD pod is deleted" +msgstr "Kasus: Pod OSD dihapus" + +msgid "Case: A disk fails" +msgstr "Kasus: Disk gagal" + +msgid "Case: A host machine where ceph-mon is running is down" +msgstr "Kasus: Mesin host di mana ceph-mon sedang bekerja sedang mati" + +msgid "Case: Monitor database is destroyed" +msgstr "Kasus: Database monitor dimusnahkan" + +msgid "Case: OSD processes are killed" +msgstr "Kasus: Proses OSD dimatikan" + +msgid "Case: One host machine where ceph-mon is running is rebooted" +msgstr "Kasus: Satu mesin host di mana ceph-mon sedang dijalankan di-reboot" + +msgid "Caveats:" +msgstr "Caveats:" + +msgid "Ceph - Node Reduction, Expansion and Ceph Recovery" +msgstr "Ceph - Node Reduction, Expansion, dan Ceph Recovery" + +msgid "Ceph Cephfs provisioner docker images." +msgstr "Ceph Cephfs provisioner docker images." + +msgid "Ceph Luminous point release images for Ceph components" +msgstr "Ceph Luminous point melepaskan image untuk komponen Ceph" + +msgid "Ceph MON and OSD PODs got scheduled on mnode4 node." +msgstr "Ceph MON dan OSD POD dijadwalkan pada node mnode4." + +msgid "Ceph RBD provisioner docker images." +msgstr "Ceph RBD provisioner docker images." + +msgid "Ceph Resiliency" +msgstr "Ceph Resiliency" + +msgid "Ceph Upgrade" +msgstr "Ceph Upgrade" + +msgid "" +"Ceph can be upgraded without downtime for Openstack components in a " +"multinode env." +msgstr "" +"Ceph dapat ditingkatkan tanpa downtime untuk komponen OpenStack dalam " +"multinode env." + +msgid "Ceph cluster is in HEALTH_OK state with 3 MONs and 3 OSDs." +msgstr "Ceph cluster dalam keadaan HEALTH_OK dengan 3 MON dan 3 OSD." + +msgid "Ceph status shows 1 Ceph MON and 1 Ceph OSD missing." +msgstr "Status Ceph menunjukkan 1 Ceph MON dan 1 Ceph OSD hilang." + +msgid "Ceph status shows HEALTH_WARN as expected" +msgstr "Status Ceph menunjukkan HEALTH_WARN seperti yang diharapkan" + +msgid "Ceph status shows that MON and OSD count has been increased." +msgstr "Status Ceph menunjukkan bahwa jumlah MON dan OSD telah ditingkatkan." + +msgid "" +"Ceph status shows that ceph-mon running on ``voyager3`` becomes out of " +"quorum. Also, 6 osds running on ``voyager3`` are down (i.e., 18 out of 24 " +"osds are up). Some placement groups become degraded and undersized." +msgstr "" +"Status Ceph menunjukkan bahwa ceph-mon yang berjalan pada ``voyager3`` " +"menjadi tidak dapat digunakan. Juga, 6 osds yang berjalan pada ``voyager3`` " +"sedang down (yaitu, 18 dari 24 osds naik). Beberapa kelompok penempatan " +"menjadi terdegradasi dan berukuran kecil." + +msgid "" +"Ceph status shows that ceph-mon running on ``voyager3`` becomes out of " +"quorum. Also, six osds running on ``voyager3`` are down; i.e., 18 osds are " +"up out of 24 osds." +msgstr "" +"Status Ceph menunjukkan bahwa ceph-mon yang berjalan pada ``voyager3`` " +"menjadi tidak dapat digunakan. Juga, enam osds yang berjalan di ``voyager3`` " +"turun; yaitu, 18 osds naik dari 24 osds." + +msgid "Ceph status still shows HEALTH_WARN as one MON and OSD are still down." +msgstr "" +"Status Ceph masih menunjukkan HEALTH_WARN sebagai satu MON dan OSD masih " +"dalam keadaan down." + +msgid "Ceph version: 12.2.3" +msgstr "Ceph versi: 12.2.3" + +msgid "Check Ceph Pods" +msgstr "Periksa Ceph Pods" + +msgid "Check version of each Ceph components." +msgstr "Periksa versi setiap komponen Ceph." + +msgid "Check which images Provisionors and Mon-Check PODs are using" +msgstr "Periksa image mana yang digunakan Provisionors dan Mon-Check PODs" + +msgid "Cluster size: 4 host machines" +msgstr "Ukuran cluster: 4 mesin host" + +msgid "Conclusion:" +msgstr "Kesimpulan:" + +msgid "Confirm Ceph component's version." +msgstr "Konfirmasi versi komponen Ceph." + +msgid "Continue with OSH multinode guide to install other Openstack charts." +msgstr "" +"Lanjutkan dengan panduan multinode OSH untuk menginstal chart Openstack " +"lainnya." + +msgid "Deploy and Validate Ceph" +msgstr "Menyebarkan dan Memvalidasi Ceph" + +msgid "Disk Failure" +msgstr "Kegagalan Disk" + +msgid "Docker Images:" +msgstr "Docker Images:" + +msgid "" +"Every OpenStack-Helm chart should include any required Helm tests necessary " +"to provide a sanity check for the OpenStack service. Information on using " +"the Helm testing framework can be found in the Helm repository_. Currently, " +"the Rally testing framework is used to provide these checks for the core " +"services. The Keystone Helm test template can be used as a reference, and " +"can be found here_." +msgstr "" +"Setiap OpenStack-Helm chart harus menyertakan tes Helm yang diperlukan untuk " +"memberikan pemeriksaan (sanity check) kewarasan untuk layanan OpenStack. " +"Informasi tentang menggunakan kerangka pengujian Helm dapat ditemukan di " +"repositori Helm. Saat ini, kerangka pengujian Rally digunakan untuk " +"menyediakan pemeriksaan ini untuk layanan inti. Kerangka uji Keystone Helm " +"dapat digunakan sebagai referensi, dan dapat ditemukan di sini_." + +msgid "Find that Ceph is healthy with a lost OSD (i.e., a total of 23 OSDs):" +msgstr "Temukan bahwa Ceph sehat dengan OSD yang hilang (yaitu, total 23 OSD):" + +msgid "First, run ``ceph osd tree`` command to get list of OSDs." +msgstr "" +"Pertama, jalankan perintah ``ceph osd tree`` untuk mendapatkan daftar OSD." + +msgid "Follow all steps from OSH multinode guide with below changes." +msgstr "" +"Ikuti semua langkah dari panduan multinode OSH dengan perubahan di bawah ini." + +msgid "" +"Followed OSH multinode guide steps to install Ceph and OpenStack charts up " +"to Cinder." +msgstr "" +"Mengikuti panduan langkah multinode OSH untuk menginstal grafik Ceph dan " +"OpenStack hingga Cinder." + +msgid "" +"Followed OSH multinode guide steps to setup nodes and install K8s cluster" +msgstr "" +"Mengikuti langkah-langkah panduan multinode OSH untuk mengatur node dan " +"menginstal K8s cluster" + +msgid "Followed OSH multinode guide steps upto Ceph install" +msgstr "Mengikuti panduan multinode OSH langkah-langkah upto Ceph menginstal" + +msgid "Following is a partial part from script to show changes." +msgstr "" +"Berikut ini adalah bagian parsial dari skrip untuk menunjukkan perubahan." + +msgid "" +"From the Kubernetes cluster, remove the failed OSD pod, which is running on " +"``voyager4``:" +msgstr "" +"Dari kluster Kubernetes, hapus pod OSD yang gagal, yang berjalan di " +"``voyager4``:" + +msgid "Hardware Failure" +msgstr "Kegagalan perangkat keras" + +msgid "Helm Tests" +msgstr "Tes Helm" + +msgid "Host Failure" +msgstr "Host Failure" + +msgid "" +"In the mean time, we monitor the status of Ceph and noted that it takes " +"about 30 seconds for the 6 OSDs to recover from ``down`` to ``up``. The " +"reason is that Kubernetes automatically restarts OSD pods whenever they are " +"killed." +msgstr "" +"Sementara itu, kami memantau status Ceph dan mencatat bahwa dibutuhkan " +"sekitar 30 detik untuk 6 OSD untuk memulihkan dari ``down`` ke ``up``. " +"Alasannya adalah Kubernetes secara otomatis merestart pod OSD setiap kali " +"mereka dimatikan." + +msgid "" +"In the mean time, we monitored the status of Ceph and noted that it takes " +"about 24 seconds for the killed Monitor process to recover from ``down`` to " +"``up``. The reason is that Kubernetes automatically restarts pods whenever " +"they are killed." +msgstr "" +"Sementara itu, kami memantau status Ceph dan mencatat bahwa dibutuhkan " +"sekitar 24 detik untuk proses Monitor yang mati untuk memulihkan dari " +"``down`` ke ``up``. Alasannya adalah Kubernetes secara otomatis me-restart " +"pod setiap kali mereka dimatikan." + +msgid "" +"In this test env, MariaDB chart is deployed with only 1 replica. In order to " +"test properly, the node with MariaDB server POD (mnode2) should not be " +"shutdown." +msgstr "" +"Dalam test env, tabel MariaDB dikerahkan hanya dengan 1 replika. Untuk " +"menguji dengan benar, node dengan server POD MariaDB (mnode2) tidak boleh " +"dimatikan." + +msgid "In this test env, ``mnode3`` is out of quorum." +msgstr "Dalam tes env ini, `` mnode3`` keluar dari quorum." + +msgid "" +"In this test env, each node has Ceph and OpenStack related PODs. Due to " +"this, shutting down a Node will cause issue with Ceph as well as OpenStack " +"services. These PODs level failures are captured following subsequent " +"screenshots." +msgstr "" +"Dalam tes env ini, setiap node memiliki POD yang terkait dengan Ceph dan " +"OpenStack. Karena ini, mematikan Node akan menyebabkan masalah dengan Ceph " +"serta layanan OpenStack. Tingkat kegagalan PODs ini ditangkap setelah " +"screenshot berikutnya." + +msgid "In this test env, let's shutdown ``mnode3`` node." +msgstr "Dalam tes ini env, mari kita mematikan node `` mnode3``." + +msgid "" +"In this test env, let's use ``mnode4`` and apply Ceph and OpenStack related " +"labels." +msgstr "" +"Dalam tes env ini, mari kita gunakan ``mnode4`` dan menerapkan label terkait " +"Ceph dan OpenStack." + +msgid "" +"In this test env, since out of quorum MON is no longer available due to node " +"failure, we can processed with removing it from Ceph cluster." +msgstr "" +"Dalam test env ini, sejak quorum MON tidak lagi tersedia karena kegagalan " +"node, kami dapat memprosesnya dengan menghapusnya dari cluster Ceph." + +msgid "Install Ceph charts (12.2.4) by updating Docker images in overrides." +msgstr "" +"Instal Ceph charts (12.2.4) dengan memperbarui Docker images di overrides." + +msgid "Install Ceph charts (version 12.2.4)" +msgstr "Pasang chart Ceph (versi 12.2.4)" + +msgid "Install OSH components as per OSH multinode guide." +msgstr "Instal komponen OSH sesuai panduan multinode OSH." + +msgid "Install Openstack charts" +msgstr "Pasang chart Openstack" + +msgid "" +"It takes longer (about 1 minute) for the killed Monitor processes to recover " +"from ``down`` to ``up``." +msgstr "" +"Diperlukan waktu lebih lama (sekitar 1 menit) untuk proses Monitor yang mati " +"untuk memulihkan dari ``down`` ke ``up``." + +msgid "Kubernetes version: 1.10.5" +msgstr "Kubernetes versi: 1.10.5" + +msgid "Kubernetes version: 1.9.3" +msgstr "Kubernetes version: 1.9.3" + +msgid "Let's add more resources for K8s to schedule PODs on." +msgstr "" +"Mari tambahkan lebih banyak sumber daya untuk K8 untuk menjadwalkan POD." + +msgid "" +"Make sure only 3 nodes (mnode1, mnode2, mnode3) have Ceph and OpenStack " +"related labels. K8s would only schedule PODs on these 3 nodes." +msgstr "" +"Pastikan hanya 3 node (mnode1, mnode2, mnode3) yang memiliki label terkait " +"Ceph dan OpenStack. K8 hanya akan menjadwalkan POD pada 3 node ini." + +msgid "Mission" +msgstr "Misi" + +msgid "Monitor Failure" +msgstr "Memantau Kegagalan" + +msgid "" +"Note: To find the daemonset associated with a failed OSD, check out the " +"followings:" +msgstr "" +"Catatan: Untuk menemukan daemon yang terkait dengan OSD yang gagal, periksa " +"yang berikut:" + +msgid "" +"Now that we have added new node for Ceph and OpenStack PODs, let's perform " +"maintenance on Ceph cluster." +msgstr "" +"Sekarang kita telah menambahkan node baru untuk Ceph dan OpenStack PODs, " +"mari kita melakukan pemeliharaan pada cluster Ceph." + +msgid "Number of disks: 24 (= 6 disks per host * 4 hosts)" +msgstr "Jumlah disk: 24 (= 6 disk per host * 4 host)" + +msgid "OSD Failure" +msgstr "Kegagalan OSD" + +msgid "OSD count is set to 3 based on env setup." +msgstr "Penghitungan OSD diatur ke 3 berdasarkan pada env setup." + +msgid "" +"Only 3 nodes will have Ceph and OpenStack related labels. Each of these 3 " +"nodes will have one MON and one OSD running on them." +msgstr "" +"Hanya 3 node yang memiliki label terkait Ceph dan OpenStack. Masing-masing " +"dari 3 node ini akan memiliki satu MON dan satu OSD yang berjalan pada " +"mereka." + +msgid "OpenStack PODs that were scheduled mnode3 also shows NodeLost/Unknown." +msgstr "" +"OpenStack PODs yang dijadwalkan mnode3 juga menunjukkan NodeLost / Unknown." + +msgid "OpenStack-Helm commit: 25e50a34c66d5db7604746f4d2e12acbdd6c1459" +msgstr "OpenStack-Helm commit: 25e50a34c66d5db7604746f4d2e12acbdd6c1459" + +msgid "OpenStack-Helm commit: 28734352741bae228a4ea4f40bcacc33764221eb" +msgstr "OpenStack-Helm commit: 28734352741bae228a4ea4f40bcacc33764221eb" + +msgid "" +"Our focus lies on resiliency for various failure scenarios but not on " +"performance or stress testing." +msgstr "" +"Fokus kami terletak pada ketahanan untuk berbagai skenario kegagalan tetapi " +"tidak pada kinerja atau stress testing." + +msgid "PODs that were scheduled on mnode3 node has status of NodeLost/Unknown." +msgstr "" +"POD yang dijadwalkan pada node mnode3 memiliki status NodeLost / Unknown." + +msgid "Plan:" +msgstr "Rencana:" + +msgid "Recovery:" +msgstr "Pemulihan:" + +msgid "" +"Remove the entire ceph-mon directory on voyager3, and then Ceph will " +"automatically recreate the database by using the other ceph-mons' database." +msgstr "" +"Hapus seluruh direktori ceph-mon di voyager3, dan kemudian Ceph akan secara " +"otomatis membuat ulang database dengan menggunakan database ceph-mons " +"lainnya." + +msgid "" +"Remove the failed OSD (OSD ID = 2 in this example) from the Ceph cluster:" +msgstr "Hapus OSD yang gagal (OSD ID = 2 dalam contoh ini) dari kluster Ceph:" + +msgid "Resiliency Tests for OpenStack-Helm/Ceph" +msgstr "Tes Ketahanan untuk OpenStack-Helm/Ceph" + +msgid "Run ``ceph osd purge`` command to remove OSD from ceph cluster." +msgstr "" +"Jalankan perintah ``ceph osd purge`` untuk menghapus OSD dari ceph cluster." + +msgid "Running Tests" +msgstr "Menjalankan Tes" + +msgid "Setup:" +msgstr "Mempersiapkan:" + +msgid "" +"Showing partial output from kubectl describe command to show which image is " +"Docker container is using" +msgstr "" +"Menampilkan sebagian output dari kubectl menggambarkan perintah untuk " +"menunjukkan image mana yang digunakan oleh container Docker" + +msgid "" +"Shutdown 1 of 3 nodes (mnode1, mnode2, mnode3) to simulate node failure/lost." +msgstr "" +"Shutdown 1 dari 3 node (mnode1, mnode2, mnode3) untuk mensimulasikan " +"kegagalan node / lost." + +msgid "" +"Since the node that was shutdown earlier had both Ceph and OpenStack PODs, " +"mnode4 should get Ceph and OpenStack related labels as well." +msgstr "" +"Karena node yang shutdown sebelumnya memiliki Ceph dan OpenStack PODs, " +"mnode4 harus mendapatkan label terkait Ceph dan OpenStack juga." + +msgid "Software Failure" +msgstr "Kegagalan Perangkat Lunak" + +msgid "Solution:" +msgstr "Solusi:" + +msgid "Start a new OSD pod on ``voyager4``:" +msgstr "Mulai pod LED baru pada ``voyager 4``:" + +msgid "Step 1: Initial Ceph and OpenStack deployment" +msgstr "Langkah 1: Penyebaran Ceph dan OpenStack awal" + +msgid "Step 2: Node reduction (failure):" +msgstr "Langkah 2: Pengurangan nodus (kegagalan):" + +msgid "Step 3: Node Expansion" +msgstr "Langkah 3: Ekspansi Node" + +msgid "Step 4: Ceph cluster recovery" +msgstr "Langkah 4: Ceph cluster recovery" + +msgid "Steps:" +msgstr "Langkah:" + +msgid "Symptom:" +msgstr "Gejala:" + +msgid "Test Environment" +msgstr "Uji Lingkungan" + +msgid "Test Scenario:" +msgstr "Test Scenario:" + +msgid "Test Scenarios:" +msgstr "Skenario Uji:" + +msgid "Testing" +msgstr "Pengujian" + +msgid "Testing Expectations" +msgstr "Menguji Ekspektasi" + +msgid "" +"The goal of our resiliency tests for `OpenStack-Helm/Ceph `_ is to show symptoms of " +"software/hardware failure and provide the solutions." +msgstr "" +"Tujuan dari uji ketahanan kami untuk `OpenStack-Helm/Ceph `_ adalah untuk menunjukkan " +"gejala kegagalan perangkat lunak/perangkat keras dan memberikan solusi." + +msgid "" +"The logs of the failed mon-pod shows the ceph-mon process cannot run as ``/" +"var/lib/ceph/mon/ceph-voyager3/store.db`` does not exist." +msgstr "" +"Log dari mon-pod gagal menunjukkan proses ceph-mon tidak dapat berjalan " +"karena ``/var/lib/ceph/mon/ceph-voyager3/store.db`` tidak ada." + +msgid "" +"The node status of ``voyager3`` changes to ``Ready`` after the node is up " +"again. Also, Ceph pods are restarted automatically. Ceph status shows that " +"the monitor running on ``voyager3`` is now in quorum." +msgstr "" +"Status node ``voyager3`` berubah menjadi ``Ready`` setelah node naik lagi. " +"Juga, Ceph pod di-restart secara otomatis. Status Ceph menunjukkan bahwa " +"monitor yang dijalankan pada ``voyager3`` sekarang dalam kuorum." + +msgid "" +"The node status of ``voyager3`` changes to ``Ready`` after the node is up " +"again. Also, Ceph pods are restarted automatically. The Ceph status shows " +"that the monitor running on ``voyager3`` is now in quorum and 6 osds gets " +"back up (i.e., a total of 24 osds are up)." +msgstr "" +"Status node ``voyager3`` berubah menjadi ``Ready`` setelah node naik lagi. " +"Juga, Ceph pod di-restart secara otomatis. Status Ceph menunjukkan bahwa " +"monitor yang berjalan pada ``voyager3`` sekarang berada di kuorum dan 6 osds " +"akan kembali (yaitu, total 24 osds naik)." + +msgid "" +"The output of the Helm tests can be seen by looking at the logs of the pod " +"created by the Helm tests. These logs can be viewed with:" +msgstr "" +"Output dari tes Helm dapat dilihat dengan melihat log dari pod yang dibuat " +"oleh tes Helm. Log ini dapat dilihat dengan:" + +msgid "The pod status of ceph-mon and ceph-osd shows as ``NodeLost``." +msgstr "Status pod ceph-mon dan ceph-osd ditampilkan sebagai ``NodeLost``." + +msgid "" +"The status of the pods (where the three Monitor processes are killed) " +"changed as follows: ``Running`` -> ``Error`` -> ``CrashLoopBackOff`` -> " +"``Running`` and this recovery process takes about 1 minute." +msgstr "" +"Status pod (di mana ketiga proses Monitor dimatikan) diubah sebagai berikut: " +"``Running`` -> ``Error`` -> ``CrashLoopBackOff`` -> ``Running`` dan proses " +"pemulihan ini memakan waktu sekitar 1 menit." + +msgid "" +"The status of the pods (where the two Monitor processes are killed) changed " +"as follows: ``Running`` -> ``Error`` -> ``CrashLoopBackOff`` -> ``Running`` " +"and this recovery process takes about 1 minute." +msgstr "" +"Status pod (di mana kedua proses Monitor mati) diubah sebagai berikut: " +"``Running`` -> ``Error`` -> ``CrashLoopBackOff`` -> ``Running`` dan proses " +"pemulihan ini memakan waktu sekitar 1 menit." + +msgid "" +"This document captures steps and result from node reduction and expansion as " +"well as ceph recovery." +msgstr "" +"Dokumen ini menangkap (capture) langkah dan hasil dari pengurangan dan " +"perluasan node serta pemulihan ceph." + +msgid "" +"This guide documents steps showing Ceph version upgrade. The main goal of " +"this document is to demostrate Ceph chart update without downtime for OSH " +"components." +msgstr "" +"Panduan ini mendokumentasikan langkah-langkah yang menunjukkan upgrade versi " +"Ceph. Tujuan utama dari dokumen ini adalah untuk mendemonstrasikan pembaruan " +"Ceph chart tanpa downtime untuk komponen OSH." + +msgid "" +"This is for the case when a host machine (where ceph-mon is running) is down." +msgstr "" +"Ini untuk kasus ketika mesin host (di mana ceph-mon sedang berjalan) sedang " +"mati." + +msgid "This is to test a scenario when 1 out of 3 Monitor processes is down." +msgstr "Ini untuk menguji skenario ketika 1 dari 3 proses Monitor mati." + +msgid "" +"This is to test a scenario when 2 out of 3 Monitor processes are down. To " +"bring down 2 Monitor processes (out of 3), we identify two Monitor processes " +"and kill them from the 2 monitor hosts (not a pod)." +msgstr "" +"Ini untuk menguji skenario ketika 2 dari 3 proses Monitor sedang down. Untuk " +"menurunkan 2 proses Monitor (dari 3), kami mengidentifikasi dua proses " +"Monitor dan mematikannya dari 2 monitor host (bukan pod)." + +msgid "" +"This is to test a scenario when 3 out of 3 Monitor processes are down. To " +"bring down 3 Monitor processes (out of 3), we identify all 3 Monitor " +"processes and kill them from the 3 monitor hosts (not pods)." +msgstr "" +"Ini untuk menguji skenario ketika 3 dari 3 proses Monitor sedang down. Untuk " +"menurunkan 3 proses Monitor (dari 3), kami mengidentifikasi semua 3 proses " +"Monitor dan mematikannya dari 3 monitor host (bukan pod)." + +msgid "" +"This is to test a scenario when a disk failure happens. We monitor the ceph " +"status and notice one OSD (osd.2) on voyager4 which has ``/dev/sdh`` as a " +"backend is down." +msgstr "" +"Ini untuk menguji skenario ketika terjadi kegagalan disk. Kami memonitor " +"status ceph dan melihat satu OSD (osd.2) di voyager4 yang memiliki ``/dev/" +"sdh`` sebagai backend sedang down (mati)." + +msgid "" +"This is to test a scenario when an OSD pod is deleted by ``kubectl delete " +"$OSD_POD_NAME``. Meanwhile, we monitor the status of Ceph and note that it " +"takes about 90 seconds for the OSD running in deleted pod to recover from " +"``down`` to ``up``." +msgstr "" +"Ini untuk menguji skenario ketika pod OSD dihapus oleh ``kubectl delete $ " +"OSD_POD_NAME``. Sementara itu, kami memantau status Ceph dan perhatikan " +"bahwa dibutuhkan sekitar 90 detik untuk OSD yang berjalan di pod yang " +"dihapus untuk memulihkan dari ``down`` ke ``up``." + +msgid "This is to test a scenario when some of the OSDs are down." +msgstr "Ini untuk menguji skenario ketika beberapa OSD turun." + +msgid "" +"To bring down 1 Monitor process (out of 3), we identify a Monitor process " +"and kill it from the monitor host (not a pod)." +msgstr "" +"Untuk menurunkan 1 proses Monitor (dari 3), kami mengidentifikasi proses " +"Monitor dan mematikannya dari host monitor (bukan pod)." + +msgid "" +"To bring down 6 OSDs (out of 24), we identify the OSD processes and kill " +"them from a storage host (not a pod)." +msgstr "" +"Untuk menurunkan 6 OSD (dari 24), kami mengidentifikasi proses OSD dan " +"mematikannya dari host penyimpanan (bukan pod)." + +msgid "To replace the failed OSD, execute the following procedure:" +msgstr "Untuk mengganti OSD yang gagal, jalankan prosedur berikut:" + +msgid "Update Ceph Client chart with new overrides:" +msgstr "Perbarui Ceph Client chart dengan override baru:" + +msgid "Update Ceph Mon chart with new overrides" +msgstr "Perbarui Ceph Mon chart dengan override baru" + +msgid "Update Ceph OSD chart with new overrides:" +msgstr "Perbarui Ceph OSD chart dengan override baru:" + +msgid "Update Ceph Provisioners chart with new overrides:" +msgstr "Perbarui Ceph Provisioners chart dengan override baru:" + +msgid "" +"Update ceph install script ``./tools/deployment/multinode/030-ceph.sh`` to " +"add ``images:`` section in overrides as shown below." +msgstr "" +"Perbarui ceph install script ``./tools/deployment/multinode/030-ceph.sh`` " +"untuk menambahkan bagian ``images:`` di override seperti yang ditunjukkan di " +"bawah ini." + +msgid "" +"Update, image section in new overrides ``ceph-update.yaml`` as shown below" +msgstr "" +"Pembaruan, bagian image di overrides baru ``ceph-update.yaml`` seperti yang " +"ditunjukkan di bawah ini" + +msgid "Upgrade Ceph charts to update version" +msgstr "Tingkatkan Ceph charts untuk memperbarui versi" + +msgid "" +"Upgrade Ceph charts to version 12.2.5 by updating docker images in overrides." +msgstr "" +"Tingkatkan Ceph chart ke versi 12.2.5 dengan memperbarui image docker di " +"overrides." + +msgid "" +"Upgrade Ceph component version from ``12.2.4`` to ``12.2.5`` without " +"downtime to OSH components." +msgstr "" +"Upgrade versi komponen Ceph dari ``12.2.4`` ke ``12.2.5`` tanpa waktu henti " +"ke komponen OSH." + +msgid "" +"Use Ceph override file ``ceph.yaml`` that was generated previously and " +"update images section as below" +msgstr "" +"Gunakan Ceph override file ``ceph.yaml`` yang telah dibuat sebelumnya dan " +"perbarui bagian image seperti di bawah ini" + +msgid "" +"Using ``ceph mon_status`` and ``ceph -s`` commands, confirm ID of MON that " +"is out of quorum." +msgstr "" +"Dengan menggunakan perintah ``ceph mon_status`` dan ``ceph -s``, " +"konfirmasikan ID MON yang keluar dari quorum." + +msgid "" +"Validate the Ceph status (i.e., one OSD is added, so the total number of " +"OSDs becomes 24):" +msgstr "" +"Validasi status Ceph (yaitu satu OSD ditambahkan, sehingga jumlah total OSD " +"menjadi 24):" + +msgid "" +"We also monitored the pod status through ``kubectl get pods -n ceph`` during " +"this process. The deleted OSD pod status changed as follows: ``Terminating`` " +"-> ``Init:1/3`` -> ``Init:2/3`` -> ``Init:3/3`` -> ``Running``, and this " +"process takes about 90 seconds. The reason is that Kubernetes automatically " +"restarts OSD pods whenever they are deleted." +msgstr "" +"Kami juga memantau status pod melalui ``kubectl get pods -n ceph`` selama " +"proses ini. Status pod OSD yang dihapus diubah sebagai berikut: " +"``Terminating`` -> ``Init:1/3`` -> ``Init:2/3`` -> ``Init:3/3`` -> " +"``Running``, dan proses ini membutuhkan waktu sekitar 90 detik. Alasannya " +"adalah Kubernetes secara otomatis merestart pod OSD setiap kali dihapus." + +msgid "" +"We also monitored the status of the Monitor pod through ``kubectl get pods -" +"n ceph``, and the status of the pod (where a Monitor process is killed) " +"changed as follows: ``Running`` -> ``Error`` -> ``Running`` and this " +"recovery process takes about 24 seconds." +msgstr "" +"Kami juga memantau status pod Monitor melalui ``kubectl get pods -n ceph``, " +"dan status pod (di mana proses Monitor mati) berubah sebagai berikut: " +"``Running`` -> ``Error`` -> ``Running`` dan proses pemulihan ini membutuhkan " +"waktu sekitar 24 detik." + +msgid "" +"We have 3 Monitors in this Ceph cluster, one on each of the 3 Monitor hosts." +msgstr "" +"Kami memiliki 3 Monitor di cluster Ceph ini, satu di masing-masing dari 3 " +"host Monitor." + +msgid "" +"We intentionlly destroy a Monitor database by removing ``/var/lib/openstack-" +"helm/ceph/mon/mon/ceph-voyager3/store.db``." +msgstr "" +"Kami bermaksud menghancurkan database Monitor dengan menghapus ``/var/lib/" +"openstack-helm/ceph/mon/mon/ceph-voyager3/store.db``." + +msgid "" +"We monitored the status of Ceph Monitor pods and noted that the symptoms are " +"similar to when 1 or 2 Monitor processes are killed:" +msgstr "" +"Kami memantau status pod Ceph Monitor dan mencatat bahwa gejalanya mirip " +"dengan ketika 1 atau 2 proses Monitor dimatikan:" + +msgid "" +"We monitored the status of Ceph when the Monitor processes are killed and " +"noted that the symptoms are similar to when 1 Monitor process is killed:" +msgstr "" +"Kami memantau status Ceph ketika proses Monitor dimatikan dan mencatat bahwa " +"gejala mirip dengan ketika 1 Proses monitor dimatikan:" + +msgid "`Disk failure <./disk-failure.html>`_" +msgstr "`Disk failure <./disk-failure.html>`_" + +msgid "`Host failure <./host-failure.html>`_" +msgstr "`Host failure <./host-failure.html>`_" + +msgid "`Monitor failure <./monitor-failure.html>`_" +msgstr "`Monitor failure <./monitor-failure.html>`_" + +msgid "`OSD failure <./osd-failure.html>`_" +msgstr "`OSD failure <./osd-failure.html>`_" + +msgid "``Ceph MON Status:``" +msgstr "``Ceph MON Status:``" + +msgid "``Ceph MON Status``" +msgstr "``Ceph MON Status``" + +msgid "``Ceph PODs:``" +msgstr "``Ceph PODs:``" + +msgid "``Ceph PODs``" +msgstr "``Ceph PODs``" + +msgid "``Ceph Status:``" +msgstr "``Ceph Status:``" + +msgid "``Ceph quorum status:``" +msgstr "``Ceph quorum status:``" + +msgid "``Ceph quorum status``" +msgstr "``Ceph quorum status``" + +msgid "``Ceph status:``" +msgstr "``Ceph status:``" + +msgid "``Ceph status``" +msgstr "``Ceph status``" + +msgid "``Check node status:``" +msgstr "``Check node status:``" + +msgid "``Following are PODs scheduled on mnode3 before shutdown:``" +msgstr "``Following are PODs scheduled on mnode3 before shutdown:``" + +msgid "``OpenStack PODs:``" +msgstr "``OpenStack PODs:``" + +msgid "``OpenStack PODs``" +msgstr "``OpenStack PODs``" + +msgid "``Remove MON from Ceph cluster``" +msgstr "``Remove MON from Ceph cluster``" + +msgid "``Result/Observation:``" +msgstr "``Result/Observation:``" + +msgid "" +"``Results:`` All provisioner pods got terminated at once (same time). Other " +"ceph pods are running. No interruption to OSH pods." +msgstr "" +"``Results:`` Semua pod penyedia dihentikan sekaligus (saat yang sama). Ceph " +"pod lainnya sedang berjalan. Tidak ada gangguan pada pod OSH." + +msgid "" +"``Results:`` Mon pods got updated one by one (rolling updates). Each Mon pod " +"got respawn and was in 1/1 running state before next Mon pod got updated. " +"Each Mon pod got restarted. Other ceph pods were not affected with this " +"update. No interruption to OSH pods." +msgstr "" +"``Results:`` Mon pod mendapat pembaruan satu per satu (pembaruan bergulir). " +"Setiap Mon pod mendapat respawn dan berada dalam 1/1 keadaan sebelum Mon pod " +"berikutnya diperbarui. Setiap Mon pod mulai dihidupkan ulang. Ceph pod " +"lainnya tidak terpengaruh dengan pembaruan ini. Tidak ada gangguan pada pod " +"OSH." + +msgid "" +"``Results:`` Rolling updates (one pod at a time). Other ceph pods are " +"running. No interruption to OSH pods." +msgstr "" +"``Results:`` Bergulir pembaruan (satu pod dalam satu waktu). Ceph pod " +"lainnya sedang berjalan. Tidak ada gangguan pada pod OSH." + +msgid "" +"``ceph_bootstrap``, ``ceph-config_helper`` and ``ceph_rbs_pool`` images are " +"used for jobs. ``ceph_mon_check`` has one script that is stable so no need " +"to upgrade." +msgstr "" +"Image ``ceph_bootstrap``, ``ceph-config_helper`` and ``ceph_rbs_pool`` " +"digunakan untuk pekerjaan. ``ceph_mon_check`` memiliki satu skrip yang " +"stabil sehingga tidak perlu melakukan upgrade." + +msgid "``cp /tmp/ceph.yaml ceph-update.yaml``" +msgstr "``cp /tmp/ceph.yaml ceph-update.yaml``" + +msgid "``helm upgrade ceph-client ./ceph-client --values=ceph-update.yaml``" +msgstr "``helm upgrade ceph-client ./ceph-client --values=ceph-update.yaml``" + +msgid "``helm upgrade ceph-mon ./ceph-mon --values=ceph-update.yaml``" +msgstr "``helm upgrade ceph-mon ./ceph-mon --values=ceph-update.yaml``" + +msgid "``helm upgrade ceph-osd ./ceph-osd --values=ceph-update.yaml``" +msgstr "``helm upgrade ceph-osd ./ceph-osd --values=ceph-update.yaml``" + +msgid "" +"``helm upgrade ceph-provisioners ./ceph-provisioners --values=ceph-update." +"yaml``" +msgstr "" +"``helm upgrade ceph-provisioners ./ceph-provisioners --values=ceph-update." +"yaml``" + +msgid "``series of console outputs:``" +msgstr "``series of console outputs:``" diff --git a/doc/source/locale/id/LC_MESSAGES/doc-troubleshooting.po b/doc/source/locale/id/LC_MESSAGES/doc-troubleshooting.po new file mode 100644 index 0000000000..577fc59c31 --- /dev/null +++ b/doc/source/locale/id/LC_MESSAGES/doc-troubleshooting.po @@ -0,0 +1,207 @@ +# suhartono , 2018. #zanata +# suhartono , 2020. #zanata +msgid "" +msgstr "" +"Project-Id-Version: openstack-helm 0.1.1.dev3685\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2022-04-06 21:47+0000\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"PO-Revision-Date: 2020-05-08 08:25+0000\n" +"Last-Translator: suhartono \n" +"Language-Team: Indonesian\n" +"Language: id\n" +"X-Generator: Zanata 4.3.3\n" +"Plural-Forms: nplurals=1; plural=0\n" + +msgid "Backing up a PVC" +msgstr "Mencadangkan PVC" + +msgid "" +"Backing up a PVC stored in Ceph, is fairly straigthforward, in this example " +"we use the PVC ``mysql-data-mariadb-server-0`` as an example, but this will " +"also apply to any other services using PVCs eg. RabbitMQ, Postgres." +msgstr "" +"Mencadangkan PVC yang disimpan di Ceph, cukup ketat, dalam contoh ini kita " +"menggunakan PVC ``mysql-data-mariadb-server-0`` sebagai contoh, tetapi ini " +"juga akan berlaku untuk layanan lain yang menggunakan PVC misalnya. " +"RabbitMQ, Postgres." + +msgid "" +"Before proceeding, it is important to ensure that you have deployed a client " +"key in the namespace you wish to fulfill ``PersistentVolumeClaims``. To " +"verify that your deployment namespace has a client key:" +msgstr "" +"Sebelum melanjutkan, penting untuk memastikan bahwa Anda telah menggunakan " +"kunci klien di ruang nama (namespace) yang ingin Anda penuhi " +"``PersistentVolumeClaims``. Untuk memverifikasi bahwa namespace penyebaran " +"Anda memiliki kunci klien:" + +msgid "Bugs and Feature requests" +msgstr "Permintaan Bug dan Fitur" + +msgid "Ceph" +msgstr "Ceph" + +msgid "Ceph Deployment Status" +msgstr "Status Penerapan Ceph" + +msgid "Ceph Validating PVC Operation" +msgstr "Ceph Memvalidasi Operasi PVC" + +msgid "Ceph Validating StorageClass" +msgstr "Ceph Validating StorageClass" + +msgid "Channels" +msgstr "Channels" + +msgid "Database Deployments" +msgstr "Database Deployments" + +msgid "" +"First, we want to validate that Ceph is working correctly. This can be done " +"with the following Ceph command:" +msgstr "" +"Pertama, kami ingin memvalidasi bahwa Ceph berfungsi dengan benar. Ini dapat " +"dilakukan dengan perintah Ceph berikut:" + +msgid "Galera Cluster" +msgstr "Galera Cluster" + +msgid "Getting help" +msgstr "Mendapatkan bantuan" + +msgid "Installation" +msgstr "Instalasi" + +msgid "Join us on `Slack `_ - #openstack-helm" +msgstr "" +"Bergabunglah dengan kami `Slack `_ - #openstack-helm" + +msgid "" +"Next we can look at the storage class, to make sure that it was created " +"correctly:" +msgstr "" +"Selanjutnya kita dapat melihat kelas penyimpanan, untuk memastikan bahwa itu " +"dibuat dengan benar:" + +msgid "" +"Note: This step is not relevant for PVCs within the same namespace Ceph was " +"deployed." +msgstr "" +"Catatan: Langkah ini tidak relevan untuk PVC dalam ruang nama (namespace) " +"yang sama Ceph dikerahkan." + +msgid "Once this has been done the workload can be restarted." +msgstr "Setelah ini selesai, beban kerja (workload) dapat dimulai kembali." + +msgid "PVC Preliminary Validation" +msgstr "Validasi Pendahuluan PVC" + +msgid "Persistent Storage" +msgstr "Penyimpanan Persisten" + +msgid "" +"Please, refer to `Contribution guidelines <../contributor/contributing." +"html>`_." +msgstr "" +"Silakan merujuk `Contribution guidelines <../contributor/contributing." +"html>`_." + +msgid "" +"Restoring is just as straightforward. Once the workload consuming the device " +"has been stopped, and the raw RBD device removed the following will import " +"the back up and create a device:" +msgstr "" +"Memulihkan sama mudahnya. Setelah beban kerja yang memakan perangkat telah " +"dihentikan, dan perangkat RBD mentah yang dihapus berikut ini akan mengimpor " +"cadangan dan membuat perangkat:" + +msgid "" +"Sometimes things go wrong. These guides will help you solve many common " +"issues with the following:" +msgstr "" +"Terkadang ada yang salah. Panduan ini akan membantu Anda memecahkan banyak " +"masalah umum dengan hal-hal berikut:" + +msgid "" +"The parameters are what we're looking for here. If we see parameters passed " +"to the StorageClass correctly, we will see the ``ceph-mon.ceph.svc.cluster." +"local:6789`` hostname/port, things like ``userid``, and appropriate secrets " +"used for volume claims." +msgstr "" +"Parameternya adalah apa yang kami cari di sini. Jika kita melihat parameter " +"yang dikirimkan ke StorageClass dengan benar, kita akan melihat hostname/" +"port ``ceph-mon.ceph.svc.cluster.local: 6789``, hal-hal seperti ``userid``, " +"dan rahasia yang sesuai digunakan untuk klaim volume ." + +msgid "" +"This guide is to help users debug any general storage issues when deploying " +"Charts in this repository." +msgstr "" +"Panduan ini untuk membantu pengguna mendebug masalah penyimpanan umum apa " +"pun saat menerapkan Charts dalam repositori ini." + +msgid "" +"This guide is to help users debug any general storage issues when deploying " +"charts in this repository." +msgstr "" +"Panduan ini untuk membantu pengguna mendebug masalah penyimpanan umum apa " +"pun saat menerapkan grafik di repositori ini." + +msgid "" +"To deploy the HWE kernel, prior to deploying Kubernetes and OpenStack-Helm " +"the following commands should be run on each node:" +msgstr "" +"Untuk menyebarkan kernel HWE, sebelum menyebarkan Kubernetes dan OpenStack-" +"Helm, perintah berikut harus dijalankan pada setiap node:" + +msgid "" +"To make use of CephFS in Ubuntu the HWE Kernel is required, until the issue " +"described `here `_ is fixed." +msgstr "" +"Untuk menggunakan CephFS di Ubuntu, Kernel HWE diperlukan, sampai masalah " +"tersebut dijelaskan `here `_ telah diperbaiki." + +msgid "To test MariaDB, do the following:" +msgstr "Untuk menguji MariaDB, lakukan hal berikut:" + +msgid "" +"To validate persistent volume claim (PVC) creation, we've placed a test " +"manifest `here `_. Deploy this manifest and verify the job " +"completes successfully." +msgstr "" +"Untuk memvalidasi pembuatan persistent volume claim (PVC, kami menempatkan " +"manifes tes `here `_. Gunakan manifes ini dan verifikasi bahwa " +"pekerjaan telah selesai dengan sukses." + +msgid "Troubleshooting" +msgstr "Penyelesaian masalah" + +msgid "Ubuntu HWE Kernel" +msgstr "Ubuntu HWE Kernel" + +msgid "" +"Use one of your Ceph Monitors to check the status of the cluster. A couple " +"of things to note above; our health is `HEALTH\\_OK`, we have 3 mons, we've " +"established a quorum, and we can see that all of our OSDs are up and in the " +"OSD map." +msgstr "" +"Gunakan salah satu Ceph Monitors Anda untuk memeriksa status cluster. " +"Beberapa hal yang perlu diperhatikan di atas; kesehatan kita adalah `HEALTH" +"\\_OK`, kita memiliki 3 mons, kita telah membentuk kuorum, dan kita dapat " +"melihat bahwa semua OSD kita sudah naik dan di peta OSD." + +msgid "" +"Without this, your RBD-backed PVCs will never reach the ``Bound`` state. " +"For more information, see how to `activate namespace for ceph <../install/" +"multinode.html#activating-control-plane-namespace-for-ceph>`_." +msgstr "" +"Tanpa ini, RBD-backed PVCs Anda tidak akan pernah mencapai status ``Bound``. " +"Untuk informasi lebih lanjut, lihat caranya `activate namespace for ceph <../" +"install/multinode.html#activating-control-plane-namespace-for-ceph>`_." diff --git a/doc/source/locale/id/LC_MESSAGES/doc.po b/doc/source/locale/id/LC_MESSAGES/doc.po new file mode 100644 index 0000000000..3547cd2ded --- /dev/null +++ b/doc/source/locale/id/LC_MESSAGES/doc.po @@ -0,0 +1,397 @@ +# suhartono , 2018. #zanata +# suhartono , 2019. #zanata +# suhartono , 2020. #zanata +msgid "" +msgstr "" +"Project-Id-Version: openstack-helm 0.1.1.dev3685\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2022-04-06 21:47+0000\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"PO-Revision-Date: 2020-05-08 08:23+0000\n" +"Last-Translator: suhartono \n" +"Language-Team: Indonesian\n" +"Language: id\n" +"X-Generator: Zanata 4.3.3\n" +"Plural-Forms: nplurals=1; plural=0\n" + +msgid ":ref:`genindex`" +msgstr ":ref:`genindex`" + +msgid ":ref:`search`" +msgstr ":ref:`search`" + +msgid "Adding Services" +msgstr "Menambahkan Layanan" + +msgid "Adding Tests" +msgstr "Menambahkan Tes" + +msgid "" +"Any additional functions required for testing new charts or improving the " +"gate workflow should be placed in the appropriate location." +msgstr "" +"Setiap fungsi tambahan yang diperlukan untuk menguji chart baru atau " +"meningkatkan gate workflow harus ditempatkan di lokasi yang tepat." + +msgid "" +"Any tests that do not use the Rally testing framework would need to be " +"handled in the appropriate manner in launch script. This would ideally " +"result in new functions that could be reused, or expansion of the gate " +"scripts to include scenarios beyond basic service launches." +msgstr "" +"Setiap tes yang tidak menggunakan kerangka pengujian Rally harus ditangani " +"dengan cara yang sesuai dalam skrip peluncuran. Ini idealnya menghasilkan " +"fungsi baru yang dapat digunakan kembali, atau perluasan skrip gate untuk " +"memasukkan skenario di luar peluncuran layanan dasar." + +msgid "" +"As charts for additional services are added to OpenStack-Helm, they should " +"be included in the gates. Adding new services to the gates allows a chart " +"developer and the review team to identify any potential issues associated " +"with a new service. All services are currently launched in the gate via a " +"series of launch scripts of the format ``NNN-service-name.sh`` where ``NNN`` " +"dictates the order these scripts are launched. The script should contain an " +"installation command like:" +msgstr "" +"Karena chart untuk layanan tambahan ditambahkan ke OpenStack-Helm, mereka " +"harus dimasukkan ke dalam gate. Menambahkan layanan baru ke gate " +"memungkinkan pengembang chart dan tim peninjau untuk mengidentifikasi setiap " +"potensi masalah yang terkait dengan layanan baru. Semua layanan saat ini " +"diluncurkan di gate melalui serangkaian skrip peluncuran format ``NNN-" +"service-name.sh`` dimana ``NNN`` mendikte perintah skrip ini diluncurkan. " +"Skrip harus berisi perintah pemasangan seperti:" + +msgid "" +"As new charts are developed and the services are added to the gate, an " +"associated Helm test should be introduced to the gates. The appropriate " +"place for executing these tests is in the respective service's launch " +"script, and must be placed after the entry for installing the service and " +"any associated overrides. Any tests that use the Rally testing framework " +"should leverage the helm_test_deployment function in the aforementioned " +"funcs/helm.sh file. For example, a Helm test for Mistral might look like:" +msgstr "" +"Ketika chart baru dikembangkan dan layanan ditambahkan ke gate, tes Helm " +"yang terkait harus diperkenalkan ke gate. Tempat yang tepat untuk " +"mengeksekusi tes ini adalah di skrip peluncuran layanan masing-masing, dan " +"harus ditempatkan setelah entri untuk menginstal layanan dan menimpa yang " +"terkait. Setiap tes yang menggunakan kerangka pengujian Rally harus " +"memanfaatkan fungsi helm_test_deployment di file funcs/helm.sh yang " +"disebutkan di atas. Misalnya, tes Helm untuk Mistral mungkin terlihat " +"seperti:" + +msgid "" +"Bugs and enhancements are tracked via OpenStack-Helm's `Storyboard `_." +msgstr "" +"Bug dan perangkat tambahan dilacak via OpenStack-Helm's `Storyboard `_." + +msgid "Communication" +msgstr "Komunikasi" + +msgid "Contents:" +msgstr "Isi:" + +msgid "Contributing" +msgstr "Berkontribusi" + +msgid "" +"Developers wishing to work on the OpenStack-Helm project should always base " +"their work on the latest code, available from the OpenStack-Helm git " +"repository." +msgstr "" +"Pengembang yang ingin bekerja pada proyek OpenStack-Helm harus selalu " +"mendasarkan pekerjaan mereka pada kode terbaru, tersedia dari repositori git " +"OpenStack-Helm." + +msgid "" +"Functions for Helm specific operations, found in helm.sh. These functions " +"include: installing Helm, serving a Helm repository locally, linting and " +"building all Helm charts, running Helm tests on a release, installing the " +"helm template plugin, and running the helm template plugin against a chart." +msgstr "" +"Fungsi untuk operasi khusus Helm, ditemukan di helm.sh. Fungsi-fungsi ini " +"meliputi: memasang Helm, melayani repositori Helm secara lokal, membuat " +"linting dan membangun semua Helm chart, menjalankan tes Helm pada rilis, " +"menginstal plugin template kemudi, dan menjalankan plugin template helm " +"terhadap chart." + +msgid "" +"Functions for Kubernetes specific operations, found in kube.sh. These " +"functions include: waiting for pods in a specific namespace to register as " +"ready, waiting for all nodes to register as ready, install the requirements " +"for the kubeadm-aio container used in the gates, building the kubeadm-aio " +"container, launching the kubeadm-aio container, and replacing the kube-" +"controller-manager with a specific image necessary for ceph functionality." +msgstr "" +"Fungsi untuk Kubernetes operasi spesifik, ditemukan di kube.sh. Fungsi-" +"fungsi ini meliputi: menunggu pod dalam namespace tertentu untuk mendaftar " +"sebagai siap (ready), menunggu semua node untuk mendaftar sebagai siap, " +"menginstal persyaratan untuk kontainer kubeadm-aio yang digunakan di gate, " +"membangun kontainer kubeadm-aio, meluncurkan kontainer kubeadm- aio, dan " +"mengganti kube-controller-manager dengan image spesifik yang diperlukan " +"untuk fungsi ceph." + +msgid "" +"Functions for OpenStack specific operations, found in openstack.sh. These " +"functions include: waiting for a successful ping, and waiting for a booted " +"virtual machine's status to return as ACTIVE." +msgstr "" +"Fungsi untuk operasi spesifik OpenStack, ditemukan di openstack.sh. Fungsi-" +"fungsi ini meliputi: menunggu ping yang berhasil, dan menunggu status mesin " +"virtual boot untuk kembali sebagai AKTIF." + +msgid "Functions for common host preparation operations, found in common.sh" +msgstr "Fungsi untuk operasi persiapan host umum, ditemukan di common.sh" + +msgid "" +"Functions for network specific operations, found in network.sh. These " +"functions include: creating a backup of the host's resolv.conf file before " +"deploying the kubeadm environments, restoring the original resolv.conf " +"settings, creating a backup of the host's /etc/hosts file before adding the " +"hosts interface and address, and restoring the original /etc/hosts file." +msgstr "" +"Fungsi untuk operasi spesifik jaringan, ditemukan di network.sh. Fungsi-" +"fungsi ini meliputi: membuat cadangan file resolv.conf host sebelum " +"menyebarkan lingkungan kubeadm, memulihkan pengaturan resolv.conf asli, " +"membuat cadangan file /etc/hosts milik host sebelum menambahkan antarmuka " +"dan alamat host, dan memulihkan file /etc/hosts asli." + +msgid "Gate Checks" +msgstr "Gate Checks (pemeriksaan gate)" + +msgid "Gate Functions" +msgstr "Gate Functions (fungsi gate)" + +msgid "Gate Output" +msgstr "Gate Output" + +msgid "Indices and Tables" +msgstr "Indeks dan Tabel" + +msgid "Installation and Development" +msgstr "Instalasi dan Pengembangan" + +msgid "" +"Join us on `Slack `_ - " +"#openstack-helm" +msgstr "" +"Bergabunglah dengan kami `Slack `_ - #openstack-helm" + +msgid "" +"Meeting Agenda Items: `Agenda `_" +msgstr "" +"Item Agenda Rapat: `Agenda `_" + +msgid "Mission" +msgstr "Misi" + +msgid "OpenStack-Helm" +msgstr "OpenStack-Helm" + +msgid "OpenStack-Helm Gates" +msgstr "OpenStack-Helm Gates" + +msgid "OpenStack-Helm currently checks the following scenarios:" +msgstr "OpenStack-Helm saat ini memeriksa skenario berikut:" + +msgid "" +"OpenStack-Helm's single node and multinode gates leverage the kubeadm-aio " +"environment created and maintained for use as a development environment. " +"All information regarding the kubeadm-aio environment can be found here_." +msgstr "" +"Node tunggal OpenStack-Helm dan gate multinode memanfaatkan lingkungan " +"kubeadm-aio yang dibuat dan dipelihara untuk digunakan sebagai lingkungan " +"pengembangan. Semua informasi mengenai lingkungan kubeadm-aio dapat " +"ditemukan di sini_." + +msgid "" +"Please review our `documentation `_. For quick installation, evaluation, and convenience, we have a " +"kubeadm based all-in-one solution that runs in a Docker container. The " +"Kubeadm-AIO set up can be found `here `_." +msgstr "" +"Harap tinjau kami `documentation `_. Untuk instalasi cepat, evaluasi, dan kenyamanan, kami memiliki " +"solusi all-in-one berbasis kubeadm yang berjalan dalam kontainer Docker. " +"Pengaturan Kubeadm-AIO dapat ditemukan `here `_." + +msgid "" +"Provisioning a multi-node Ubuntu-1604 cluster and deploying the OpenStack " +"services. This check is provided for both a two node cluster and a three " +"node cluster." +msgstr "" +"Menyediakan multi-node klaster Ubuntu-1604 dan menyebarkan layanan " +"OpenStack. Pemeriksaan ini disediakan untuk dua klaster node dan tiga " +"klaster node." + +msgid "" +"Provisioning a single node cluster and deploying the OpenStack services. " +"This check is provided for: Ubuntu-1604, CentOS-7, and Fedora-25." +msgstr "" +"Menyediakan satu klaster node dan menyebarkan layanan OpenStack. Pemeriksaan " +"ini disediakan untuk: Ubuntu-1604, CentOS-7, dan Fedora-25." + +msgid "Repository" +msgstr "Repository (repositori)" + +msgid "" +"Running Make on each chart, which lints and packages the charts. This gate " +"does not stand up a Kubernetes cluster." +msgstr "" +"Menjalankan Make pada setiap chart, yang lint dan package chart. Gate ini " +"tidak memiliki kluster Kubernetes." + +msgid "" +"Some services in the gate require specific overrides to the default values " +"in the chart's values.yaml file. If a service requires multiple overrides " +"to function in the gate, the service should include a separate values.yaml " +"file placed in the tools/overrides/mvp directory. The .yaml MVP " +"files provide a configuration file to use for overriding default " +"configuration values in the chart's values.yaml as an alternative to " +"overriding individual values during installation. A chart that requires a " +"MVP overrides file requires the following format:" +msgstr "" +"Beberapa layanan di gate memerlukan pengunggahan spesifik ke nilai default " +"di file values.yaml chart. Jika suatu layanan memerlukan beberapa override " +"untuk berfungsi di gate, layanan harus menyertakan file values.yaml yang " +"terpisah yang ditempatkan di direktori tools/overrides/mvp. File MVP " +".yaml menyediakan file konfigurasi yang digunakan untuk " +"mengesampingkan nilai konfigurasi default di values.yaml milik chart sebagai " +"alternatif untuk menimpa nilai individual selama instalasi. Sebuah chart " +"yang membutuhkan file menimpa MVP membutuhkan format berikut:" + +msgid "Storyboard" +msgstr "Storyboard (papan cerita)" + +msgid "Testing any documentation changes and impacts." +msgstr "Menguji perubahan dan dampak dokumentasi apa pun." + +msgid "" +"The K8s directory contains the logs and output of the Kubernetes objects. " +"It includes: pods, nodes, secrets, services, namespaces, configmaps, " +"deployments, daemonsets, and statefulsets. Descriptions for the state of " +"all resources during execution are found here, and this information can " +"prove valuable when debugging issues raised during a check. When a single " +"node or multi-node check fails, this is the first place to look. The logs " +"found here are helpful when the templates render correctly, but the services " +"are not functioning correctly, whether due to service configuration issues " +"or issues with the pods themselves." +msgstr "" +"Direktori K8s berisi log dan output dari objek Kubernetes. Ini termasuk: " +"pod, node, rahasia, layanan, namespace, configaps, penyebaran, daemon, dan " +"statefulset. Deskripsi untuk keadaan semua sumber daya selama eksekusi " +"ditemukan di sini, dan informasi ini dapat terbukti bermanfaat ketika " +"masalah debug dinaikkan selama pemeriksaan. Ketika pemeriksaan node tunggal " +"atau multi-node gagal, ini adalah tempat pertama untuk melihat. Log yang " +"ditemukan di sini bermanfaat ketika template dirender dengan benar, tetapi " +"layanan tidak berfungsi dengan benar, baik karena masalah konfigurasi " +"layanan atau masalah dengan pod itu sendiri." + +msgid "" +"The dry-runs directory contains the rendered output of Helm dry-run installs " +"on each of the OpenStack service charts. This gives visibility into the " +"manifests created by the templates with the supplied values. When the dry-" +"run gate fails, the reason should be apparent in the dry-runs output. The " +"logs found here are helpful in identifying issues resulting from using helm-" +"toolkit functions incorrectly or other rendering issues with gotpl." +msgstr "" +"Direktori dry-run berisi output yang diberikan dari pemasangan Helm dry-run " +"pada masing-masing chart layanan OpenStack. Ini memberikan visibilitas ke " +"manifes yang dibuat oleh template dengan nilai yang disediakan. Ketika gate " +"dry-run gagal, alasannya harus jelas dalam output dry-run. Log ditemukan di " +"sini sangat membantu dalam mengidentifikasi masalah yang dihasilkan dari " +"penggunaan fungsi-fungsi helm-toolkit yang salah atau masalah rendering " +"lainnya dengan gotpl." + +msgid "" +"The goal of OpenStack-Helm is to provide a collection of Helm charts that " +"simply, resiliently, and flexibly deploy OpenStack and related services on " +"Kubernetes." +msgstr "" +"Tujuan OpenStack-Helm adalah untuk menyediakan koleksi grafik Helm yang " +"sederhana, tangguh, dan secara fleksibel menggunakan OpenStack dan layanan " +"terkait di Kubernetes." + +msgid "" +"The nodes directory contains information about the node the gate tests are " +"running on in openstack-infra. This includes: the network interfaces, the " +"contents of iptables, the host's resolv.conf, and the kernel IP routing " +"table. These logs can be helpful when trying to identify issues with host " +"networking or other issues at the node level." +msgstr "" +"Direktori node berisi informasi tentang node dimana gate test sedang " +"berjalan di openstack-infra. Ini termasuk: antarmuka jaringan, isi iptables, " +"resolv.conf host, dan tabel routing IP kernel. Log ini dapat membantu ketika " +"mencoba mengidentifikasi masalah dengan jaringan host atau masalah lain di " +"tingkat node." + +msgid "" +"This project is under active development. We encourage anyone interested in " +"OpenStack-Helm to review our `Installation `_ documentation. Feel free to ask " +"questions or check out our current `Storyboard backlog `_." +msgstr "" +"Proyek ini sedang dalam pengembangan aktif. Kami mendorong siapa pun yang " +"tertarik dengan OpenStack-Helm untuk meninjau dokumentasi kami `Installation " +"`_. " +"Jangan ragu untuk bertanya atau memeriksa saat ini `Storyboard backlog " +"`_." + +msgid "This results in the gate running the following:" +msgstr "Ini menghasilkan gate menjalankan berikut:" + +msgid "" +"To evaluate a multinode installation, follow the `Bare Metal `_ install guide." +msgstr "" +"Untuk mengevaluasi instalasi multinode, ikuti panduan pemasangan `Bare Metal " +"` _." + +msgid "" +"To facilitate ease of testing and debugging, information regarding gates and " +"their functionality can be found here." +msgstr "" +"Untuk memfasilitasi kemudahan pengujian dan debugging, informasi mengenai " +"gate dan fungsinya dapat ditemukan di sini." + +msgid "" +"To provide meaningful output from the gates, all information pertaining to " +"the components of the cluster and workflow are output to the logs directory " +"inside each gate. The contents of the log directory are as follows:" +msgstr "" +"Untuk memberikan output yang berarti dari gate, semua informasi yang " +"berkaitan dengan komponen cluster dan alur kerja adalah output ke direktori " +"log di dalam setiap gate. Isi dari direktori log adalah sebagai berikut:" + +msgid "" +"To provide reusable components for gate functionality, functions have been " +"provided in the gates/funcs directory. These functions include:" +msgstr "" +"Untuk menyediakan komponen yang dapat digunakan kembali untuk fungsi gate, " +"fungsi telah disediakan di direktori gates/funcs. Fungsi-fungsi ini termasuk:" + +msgid "" +"We welcome contributions. Check out `this `_ document if " +"you would like to get involved." +msgstr "" +"Kami menyambut kontribusi. Lihatlah dokumen `CONTRIBUTING.rst>` _ ini jika " +"Anda ingin terlibat." + +msgid "Welcome to OpenStack-Helm's documentation!" +msgstr "Selamat datang di dokumentasi OpenStack-Helm!" + +msgid "" +"`OpenStack-Helm git repository `_" +msgstr "" +"`OpenStack-Helm git repository `_" diff --git a/doc/source/locale/ko_KR/LC_MESSAGES/doc-install.po b/doc/source/locale/ko_KR/LC_MESSAGES/doc-install.po index 72913c0e2a..28340b59f7 100644 --- a/doc/source/locale/ko_KR/LC_MESSAGES/doc-install.po +++ b/doc/source/locale/ko_KR/LC_MESSAGES/doc-install.po @@ -6,9 +6,9 @@ # Jongwon Lee , 2021. #zanata msgid "" msgstr "" -"Project-Id-Version: openstack-helm 0.1.1.dev3631\n" +"Project-Id-Version: openstack-helm 0.1.1.dev3685\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2022-02-23 21:11+0000\n" +"POT-Creation-Date: 2022-04-06 21:47+0000\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" @@ -201,11 +201,6 @@ msgstr "" "DNS 네임서버 항목은 이 파일에서 ``external_dns_nameservers`` 항목을 업데이트" "하여 변경할 수 있습니다." -msgid "" -"Cinder deployment is not tested in the OSH development environment community " -"gates" -msgstr "Cinder 배포는 OSH 개발 환경 커뮤니티 게이트에서 테스트되지 않았습니다." - msgid "Cleaning the Deployment" msgstr "배포 정리" @@ -445,12 +440,6 @@ msgstr "Chart에서 ``helm status`` 를 가져옵니다." msgid "Helm Chart Installation" msgstr "Helm Chart 설치" -msgid "" -"Horizon deployment is not tested in the OSH development environment " -"community gates" -msgstr "" -"Horizon 배포는 OSH 개발 환경 커뮤니티 게이트에서 테스트되지 않았습니다." - msgid "Host Configuration" msgstr "호스트 구성" @@ -1004,17 +993,6 @@ msgstr "" msgid "These values can be retrieved by running:" msgstr "이 값들은 실행함으로써 조회 될 수 있습니다:" -msgid "" -"This command will deploy a single node KubeADM administered cluster. This " -"will use the parameters in ``${OSH_INFRA_PATH}/playbooks/vars.yaml`` to " -"control the deployment, which can be over-ridden by adding entries to ``" -"${OSH_INFRA_PATH}/tools/gate/devel/local-vars.yaml``." -msgstr "" -"이 명령은 단일 노드 KubeADM 관리 클러스터를 배포할 것입니다. 이것은 ``" -"${OSH_INFRA_PATH}/tools/gate/devel/local-vars.yaml`` 에 항목들을 추가하여 오" -"버라이드한 ``${OSH_INFRA_PATH}/playbooks/vars.yaml`` 에 있는 매개변수를 사용" -"하여 배포를 제어합니다." - msgid "" "This guide assumes that users wishing to deploy behind a proxy have already " "defined the conventional proxy environment variables ``http_proxy``, "