openstack-ansible/releasenotes/source/locale/id/LC_MESSAGES/releasenotes.po

# suhartono <cloudsuhartono@gmail.com>, 2018. #zanata
# suhartono <cloudsuhartono@gmail.com>, 2019. #zanata
# suhartono <cloudsuhartono@gmail.com>, 2020. #zanata
msgid ""
msgstr ""
"Project-Id-Version: OpenStack-Ansible\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-10-09 14:44+0000\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"PO-Revision-Date: 2020-10-10 04:21+0000\n"
"Last-Translator: suhartono <cloudsuhartono@gmail.com>\n"
"Language-Team: Indonesian\n"
"Language: id\n"
"X-Generator: Zanata 4.3.3\n"
"Plural-Forms: nplurals=1; plural=0\n"

msgid ""
"**NOTE:** This fix is partially applied for existing OpenStack-Ansible "
"deployments. See the upgrade section of the release notes for the work "
"required to fully apply the fix."
msgstr ""
"**NOTE:*** Perbaikan ini sebagian diterapkan untuk penerapan OpenStack-"
"Ansible yang ada. Lihat bagian upgrade dari catatan rilis untuk pekerjaan "
"yang diperlukan untuk menerapkan perbaikan sepenuhnya."

msgid ""
"**This is a breaking change for existing CentOS deployments.** The ``yum`` "
"package manager will have errors when it finds that certain packages that it "
"installed from EPEL are no longer available.  Deployers may need to rebuild "
"container or reinstall packages to complete this change."
msgstr ""
"**This is a breaking change for existing CentOS deployments.**  Manajer "
"paket ``yum`` akan memiliki kesalahan ketika menemukan bahwa paket tertentu "
"yang diinstal dari EPEL tidak lagi tersedia. Deployer mungkin perlu "
"membangun kembali kontainer atau menginstal ulang paket untuk menyelesaikan "
"perubahan ini."

msgid ""
"**lxc_cache_validate_certs**: Removed because the Ansible ``get_url`` module "
"is no longer used."
msgstr ""
"**lxc_cache_validate_certs **: Dihapus karena modul ``get_url`` Ansible "
"tidak lagi digunakan."

msgid ""
"**lxc_container_base_delete**: Removed because the cache will be refreshed "
"upon role execution."
msgstr ""
"**lxc_container_base_delete **: Dihapus karena cache akan di-refresh setelah "
"eksekusi peran."

msgid ""
"**lxc_container_caches**: Removed because the container create process will "
"build a cached image based on the host OS."
msgstr ""
"**lxc_container_caches **: Dihapus karena proses pembuatan kontainer akan "
"membangun image yang di-cache berdasarkan OS host."

msgid ""
"**lxc_container_release**: Removed because image is now tied with the host "
"operating system."
msgstr ""
"**lxc_container_release **: Dihapus karena image sekarang diikat dengan "
"sistem operasi host."

msgid ""
"**lxc_container_template**: Removed because the template option is now "
"contained within the operating system specific variable file loaded at "
"runtime."
msgstr ""
"**lxc_container_template**: Dihapus karena opsi templat sekarang terdapat "
"dalam file variabel sistem operasi spesifik yang dimuat saat runtime."

msgid ""
"**lxc_container_template_main_apt_repo**: Removed because this option is now "
"being set within the cache creation process and is no longer needed here."
msgstr ""
"** lxc_container_template_main_apt_repo **: Dihapus karena opsi ini sekarang "
"sedang diatur dalam proses pembuatan cache dan tidak lagi diperlukan di sini."

msgid ""
"**lxc_container_template_options**: This option was renamed to "
"*lxc_cache_download_template_options*. The deprecation filter was not used "
"because the values provided from this option have been fundamentally changed "
"and potentially old overrides will cause problems."
msgstr ""
"**lxc_container_template_options**: Opsi ini diubah namanya menjadi "
"*lxc_cache_download_template_options*. Filter penghentian tidak digunakan "
"karena nilai yang disediakan dari opsi ini telah diubah secara mendasar dan "
"berpotensi penggantian yang lama akan menyebabkan masalah."

msgid ""
"**lxc_container_template_options**: This option was renamed to "
"*lxc_container_download_template_options*. The deprecation filter was not "
"used because the values provided from this option have been fundamentally "
"changed and old overrides will cause problems."
msgstr ""
"**lxc_container_template_options**: Opsi ini diubah namanya menjadi "
"*lxc_container_download_template_options*. Filter penghentian tidak "
"digunakan karena nilai yang disediakan dari opsi ini telah diubah secara "
"mendasar dan penggantian yang lama akan menyebabkan masalah."

msgid ""
"**lxc_container_template_security_apt_repo**: Removed because this option is "
"now being set within the cache creation process and is no longer needed here."
msgstr ""
"**lxc_container_template_security_apt_repo**: Dihapus karena opsi ini "
"sekarang sedang diatur dalam proses pembuatan cache dan tidak lagi "
"diperlukan di sini."

msgid ""
"**lxc_container_user_name**: Removed because the default users are no longer "
"created when the cached image is created."
msgstr ""
"**lxc_container_user_name**: Dihapus karena pengguna default tidak lagi "
"dibuat ketika image yang di-cache dibuat."

msgid ""
"**lxc_container_user_password**: Removed because the default lxc container "
"user is no longer created by the lxc container template."
msgstr ""
"**lxc_container_user_password**: Dihapus karena pengguna kontainer lxc "
"default tidak lagi dibuat oleh template kontainer lxc."

msgid ""
"**lxc_container_user_password**: Removed because the default users are no "
"longer created when the cached image is created."
msgstr ""
"**lxc_container_user_password**: Dihapus karena pengguna default tidak lagi "
"dibuat ketika image yang di-cache dibuat."

msgid "12.0.10"
msgstr "12.0.10"

msgid "12.0.11"
msgstr "12.0.11"

msgid "12.0.12"
msgstr "12.0.12"

msgid "12.0.13"
msgstr "12.0.13"

msgid "12.0.14"
msgstr "12.0.14"

msgid "12.0.15"
msgstr "12.0.15"

msgid "12.0.16"
msgstr "12.0.16"

msgid "12.0.6"
msgstr "12.0.6"

msgid "12.0.7"
msgstr "12.0.7"

msgid "12.0.8"
msgstr "12.0.8"

msgid "12.0.9"
msgstr "12.0.9"

msgid "12.1.0"
msgstr "12.1.0"

msgid "12.2.0"
msgstr "12.2.0"

msgid "12.2.2"
msgstr "12.2.2"

msgid "12.2.4"
msgstr "12.2.4"

msgid "12.2.5"
msgstr "12.2.5"

msgid "13.0.0"
msgstr "13.0.0"

msgid "13.0.1"
msgstr "13.0.1"

msgid "13.1.0"
msgstr "13.1.0"

msgid "13.1.1"
msgstr "13.1.1"

msgid "13.1.2"
msgstr "13.1.2"

msgid "13.1.3"
msgstr "13.1.3"

msgid "13.1.4"
msgstr "13.1.4"

msgid "13.2.0"
msgstr "13.2.0"

msgid "13.3.0"
msgstr "13.3.0"

msgid "13.3.1"
msgstr "13.3.1"

msgid "13.3.13"
msgstr "13.3.13"

msgid "13.3.2"
msgstr "13.3.2"

msgid "13.3.3"
msgstr "13.3.3"

msgid "13.3.4"
msgstr "13.3.4"

msgid "13.3.5"
msgstr "13.3.5"

msgid "13.3.6"
msgstr "13.3.6"

msgid "13.3.7"
msgstr "13.3.7"

msgid "13.3.8"
msgstr "13.3.8"

msgid "13.3.9"
msgstr "13.3.9"

msgid "14.0.0"
msgstr "14.0.0"

msgid "14.0.2"
msgstr "14.0.2"

msgid "14.0.3"
msgstr "14.0.3"

msgid "14.0.5"
msgstr "14.0.5"

msgid "14.0.6"
msgstr "14.0.6"

msgid "14.0.7"
msgstr "14.0.7"

msgid "14.0.8"
msgstr "14.0.8"

msgid "14.1.0"
msgstr "14.1.0"

msgid "14.1.1"
msgstr "14.1.1"

msgid "14.2.0"
msgstr "14.2.0"

msgid "14.2.1"
msgstr "14.2.1"

msgid "14.2.10"
msgstr "14.2.10"

msgid "14.2.11"
msgstr "14.2.11"

msgid "14.2.12"
msgstr "14.2.12"

msgid "14.2.15"
msgstr "14.2.15"

msgid "14.2.16"
msgstr "14.2.16"

msgid "14.2.16-7"
msgstr "14.2.16-7"

msgid "14.2.2"
msgstr "14.2.2"

msgid "14.2.3"
msgstr "14.2.3"

msgid "14.2.4"
msgstr "14.2.4"

msgid "14.2.5"
msgstr "14.2.5"

msgid "14.2.6"
msgstr "14.2.6"

msgid "14.2.7"
msgstr "14.2.7"

msgid "14.2.8"
msgstr "14.2.8"

msgid "14.2.9"
msgstr "14.2.9"

msgid "15.0.0"
msgstr "15.0.0"

msgid "15.1.0"
msgstr "15.1.0"

msgid "15.1.1"
msgstr "15.1.1"

msgid "15.1.10"
msgstr "15.1.10"

msgid "15.1.11"
msgstr "15.1.11"

msgid "15.1.12"
msgstr "15.1.12"

msgid "15.1.13"
msgstr "15.1.13"

msgid "15.1.14"
msgstr "15.1.14"

msgid "15.1.15"
msgstr "15.1.15"

msgid "15.1.16"
msgstr "15.1.16"

msgid "15.1.17"
msgstr "15.1.17"

msgid "15.1.2"
msgstr "15.1.2"

msgid "15.1.20"
msgstr "15.1.20"

msgid "15.1.21"
msgstr "15.1.21"

msgid "15.1.22"
msgstr "15.1.22"

msgid "15.1.23"
msgstr "15.1.23"

msgid "15.1.28-8"
msgstr "15.1.28-8"

msgid "15.1.3"
msgstr "15.1.3"

msgid "15.1.4"
msgstr "15.1.4"

msgid "15.1.5"
msgstr "15.1.5"

msgid "15.1.6"
msgstr "15.1.6"

msgid "15.1.7"
msgstr "15.1.7"

msgid "15.1.8"
msgstr "15.1.8"

msgid "15.1.9"
msgstr "15.1.9"

msgid "16.0.0"
msgstr "16.0.0"

msgid "16.0.1"
msgstr "16.0.1"

msgid "16.0.10"
msgstr "16.0.10"

msgid "16.0.11"
msgstr "16.0.11"

msgid "16.0.12"
msgstr "16.0.12"

msgid "16.0.13"
msgstr "16.0.13"

msgid "16.0.14"
msgstr "16.0.14"

msgid "16.0.15"
msgstr "16.0.15"

msgid "16.0.16"
msgstr "16.0.16"

msgid "16.0.19"
msgstr "16.0.19"

msgid "16.0.2"
msgstr "16.0.2"

msgid "16.0.24"
msgstr "16.0.24"

msgid "16.0.25"
msgstr "16.0.25"

msgid "16.0.3"
msgstr "16.0.3"

msgid "16.0.4"
msgstr "16.0.4"

msgid "16.0.5"
msgstr "16.0.5"

msgid "16.0.6"
msgstr "16.0.6"

msgid "16.0.7"
msgstr "16.0.7"

msgid "16.0.8"
msgstr "16.0.8"

msgid "16.0.9"
msgstr "16.0.9"

msgid "17.0.0"
msgstr "17.0.0"

msgid "17.0.1"
msgstr "17.0.1"

msgid "17.0.2"
msgstr "17.0.2"

msgid "17.0.3"
msgstr "17.0.3"

msgid "17.0.4"
msgstr "17.0.4"

msgid "17.0.5"
msgstr "17.0.5"

msgid "17.0.6"
msgstr "17.0.6"

msgid "17.0.7"
msgstr "17.0.7"

msgid "17.0.8"
msgstr "17.0.8"

msgid "17.1.0"
msgstr "17.1.0"

msgid "17.1.1"
msgstr "17.1.1"

msgid "17.1.11"
msgstr "17.1.11"

msgid "17.1.4"
msgstr "17.1.4"

msgid "17.1.5"
msgstr "17.1.5"

msgid "17.1.6"
msgstr "17.1.6"

msgid "17.1.7"
msgstr "17.1.7"

msgid "17.1.8"
msgstr "17.1.8"

msgid "17.1.9"
msgstr "17.1.9"

msgid "18.0.0"
msgstr "18.0.0"

msgid "18.1.0"
msgstr "18.1.0"

msgid "18.1.1"
msgstr "18.1.1"

msgid "18.1.15"
msgstr "18.1.15"

msgid "18.1.3"
msgstr "18.1.3"

msgid "18.1.4"
msgstr "18.1.4"

msgid "18.1.5"
msgstr "18.1.5"

msgid "18.1.6"
msgstr "18.1.6"

msgid "18.1.8"
msgstr "18.1.8"

msgid "19.0.0"
msgstr "19.0.0"

msgid "19.0.10"
msgstr "19.0.10"

msgid "19.0.2"
msgstr "19.0.2"

msgid "19.0.4"
msgstr "19.0.4"

msgid "19.0.7"
msgstr "19.0.7"

msgid "19.1.1"
msgstr "19.1.1"

msgid "19.1.2"
msgstr "19.1.2"

msgid "20.0.0"
msgstr "20.0.0"

msgid "20.0.2"
msgstr "20.0.2"

msgid "20.1.0"
msgstr "20.1.0"

msgid "20.1.1"
msgstr "20.1.1"

msgid "20.1.2"
msgstr "20.1.2"

msgid "21.0.0"
msgstr "21.0.0"

msgid "21.0.0.0rc1"
msgstr "21.0.0.0rc1"

msgid "21.0.0.0rc1-87"
msgstr "21.0.0.0rc1-87"

msgid ""
"A bug that caused the Keystone credential keys to be lost when the playbook "
"is run during a rebuild of the first Keystone container has been fixed. "
"Please see launchpad bug 1667960 for more details."
msgstr ""
"Bug yang menyebabkan kunci kredensial (credential key) Keystone hilang saat "
"playbook dijalankan selama pembangunan kembali kontainer Keystone pertama "
"telah diperbaiki. Silakan lihat launchpad bug 1667960 untuk lebih jelasnya."

msgid ""
"A conditional has been added to the ``_local_ip`` settings used in the "
"``neutron_local_ip`` which removes the hard requirement for an overlay "
"network to be set within a deployment. If no overlay network is set within "
"the deployment the ``local_ip`` will be set to the value of "
"\"ansible_ssh_host\"."
msgstr ""
"Sebuah kondisional telah ditambahkan ke pengaturan ``_local_ip`` yang "
"digunakan dalam ``neutron_local_ip`` yang menghilangkan persyaratan sulit "
"untuk jaringan overlay yang akan diatur dalam penyebaran. Jika tidak ada "
"jaringan overlay yang diatur dalam penyebaran, ``local_ip`` akan ditetapkan "
"ke nilai \"ansible_ssh_host\"."

msgid ""
"A new LXC container template has been added which will allow us to better "
"manage containers on the host machines we support. The new template uses the "
"`machinectl` command to create container rootfs using the existing cache. "
"This in-turn will provide easier management of container images, faster "
"build times, and the ability to instantly clone a container (or a given "
"variant) without impacting a containers state. This new lxc container create "
"template, and the features it provides, will only impact new containers "
"created allowing deployers to safely adopt this change in any existing "
"environment."
msgstr ""
"Template kontainer LXC baru telah ditambahkan yang akan memungkinkan kami "
"untuk mengelola kontainer dengan lebih baik pada mesin host yang kami "
"dukung. Template baru menggunakan perintah `machinectl` untuk membuat rootfs "
"kontainer menggunakan cache yang ada. Pada gilirannya ini akan memberikan "
"pengelolaan image kontainer yang lebih mudah, waktu pembuatan yang lebih "
"cepat, dan kemampuan untuk mengkloning kontainer secara kesetika (atau "
"varian yang diberikan) tanpa memengaruhi keadaan kontainer.  Kontainer lxc "
"baru ini membuat template, dan fitur-fitur yang disediakannya, hanya akan "
"berdampak pada kontainer baru yang dibuat yang memungkinkan penyebar untuk "
"secara aman mengadopsi perubahan ini di lingkungan yang ada."

msgid ""
"A new ``heat_api`` container is created with all heat services running in "
"it. The previously implemented ``heat_apis_container`` and "
"``heat_engine_container`` can be removed."
msgstr ""
"Kontainer ``heat_api`` baru dibuat dengan semua layanan heat berjalan di "
"dalamnya. ``heat_apis_container`` dan ``heat_engine_container` yang "
"sebelumnya dijalankan dapat dihapus."

msgid ""
"A new configuration parameter ``security_ntp_bind_local_interfaces`` was "
"added to the security role to restrict the network interface to which "
"chronyd will listen for NTP requests."
msgstr ""
"Parameter konfigurasi baru ``security_ntp_bind_local_interfaces`` telah "
"ditambahkan ke peran keamanan untuk membatasi antarmuka jaringan yang "
"chronyd akan mendengarkan permintaan NTP."

msgid ""
"A new database called `nova_api` has been created. This database has its own "
"user credentials and nova-manage db sync process. For the database password "
"there is a new variable entry in `user_secrets.yml` called "
"``nova_api_container_mysql_password``."
msgstr ""
"Database baru bernama `nova_api` telah dibuat. Database ini memiliki "
"kredensial pengguna sendiri dan proses sinkronisasi db nova-manage. Untuk "
"kata sandi basis data ada entri variabel baru di `user_secrets.yml` yang "
"disebut ``nova_api_container_mysql_password``."

msgid ""
"A new debug flag has been added to ``dynamic_inventory.py``. This should "
"make it easier to understand what's happening with the inventory script, and "
"provide a way to gather output for more detailed bug reports. See the "
"developer docs for more details."
msgstr ""
"Flag debug baru telah ditambahkan ke ``dynamic_inventory.py``. Ini akan "
"membuatnya lebih mudah untuk memahami apa yang terjadi dengan skrip "
"inventaris, dan menyediakan cara untuk mengumpulkan output untuk laporan bug "
"yang lebih rinci. Lihat dokumen pengembang untuk detail lebih lanjut."

msgid ""
"A new global option to control all package install states has been "
"implemented. The default action for all distribution package installations "
"is to ensure that the latest package is installed. This may be changed to "
"only verify if the package is present by setting ``package_state`` to "
"``present``."
msgstr ""
"Opsi global baru untuk mengontrol semua status instalasi paket telah "
"diterapkan. Tindakan default untuk semua instalasi paket distribusi adalah "
"untuk memastikan bahwa paket terbaru diinstal. Ini dapat diubah menjadi "
"hanya memverifikasi jika paket hadir dengan mengatur ``package_state`` ke "
"``present``."

msgid ""
"A new global variable has been created named ``openstack_domain``. This "
"variable has a default value of \"openstack.local\"."
msgstr ""
"Variabel global baru telah dibuat bernama ``openstack_domain``. Variabel ini "
"memiliki nilai default \"openstack.local\"."

msgid ""
"A new nova admin endpoint will be registered with the suffix ``/v2.1/"
"%(tenant_id)s``. The nova admin endpoint with the suffix ``/v2/"
"%(tenant_id)s`` may be manually removed."
msgstr ""
"Endpoint admin nova baru akan didaftarkan dengan akhiran ``/v2.1/"
"%(tenant_id)s``. Endpoint admin nova dengan akhiran  ``/v2/%(tenant_id)s`` "
"dapat dihapus secara manual."

msgid ""
"A new option `swift_pypy_archive` has been added to allow a pre-built pypy "
"archive to be downloaded and moved into place to support swift running under "
"pypy. This option is a dictionary and contains the URL and SHA256 as keys."
msgstr ""
"Opsi baru `swift_pypy_archive` telah ditambahkan untuk memungkinkan arsip "
"pypy yang sudah ada untuk diunduh dan dipindahkan ke tempatnya untuk "
"mendukung swift yang berjalan di bawah pypy. Opsi ini adalah kamus dan "
"berisi URL dan SHA256 sebagai kunci."

msgid ""
"A new option `swift_pypy_enabled` has been added to enable or disable the "
"pypy interpreter for swift. The default is \"false\"."
msgstr ""
"Opsi baru `swift_pypy_enabled` telah ditambahkan untuk mengaktifkan atau "
"menonaktifkan penerjemah pypy untuk swift. Nilai defaultnya \"false\"."

msgid ""
"A new option has been added allowing deployers to disable any and all "
"containers on a given host. The option `no_containers` is a boolean which, "
"if undefined, will default to *false*. This option can be added to any host "
"in the `openstack_user_config.yml` or via an override in `conf.d`. When this "
"option is set to *true* the given host will be treated as a baremetal "
"machine. The new option mirrors the existing environmental option `is_metal` "
"but allows deployers to target specific hosts instead of entire groups."
msgstr ""
"Opsi baru telah ditambahkan yang memungkinkan penelepon menonaktifkan "
"sebagian dan semua kontainer pada host tertentu. Opsi `no_containers` adalah "
"boolean dimana, jika tidak terdefinisi, akan default ke *false *. Opsi ini "
"dapat ditambahkan ke host mana saja di `openstack_user_config.yml` atau "
"melalui override di `conf.d`. Ketika opsi ini disetel ke *true * host yang "
"diberikan akan diperlakukan sebagai mesin baremetal. Opsi baru ini "
"mencerminkan opsi lingkungan yang ada `is_metal` tetapi memungkinkan "
"deployer untuk menargetkan host tertentu daripada seluruh grup."

msgid ""
"A new option has been added to ``bootstrap-ansible.sh`` to set the role "
"fetch mode. The environment variable ``ANSIBLE_ROLE_FETCH_MODE`` sets how "
"role dependencies are resolved."
msgstr ""
"Opsi baru telah ditambahkan ke ``bootstrap-ansible.sh`` untuk mengatur mode "
"pengambilan peran. Variabel lingkungan ``ANSIBLE_ROLE_FETCH_MODE`` mengatur "
"bagaimana dependensi peran diselesaikan."

msgid ""
"A new optional file /etc/openstack_deploy/user-role-requirements.yml is now "
"available for a deployer to override individual entries in the upstream "
"ansible-role-requirements file. This can be used to point to alternative "
"repos containing local fixes, or to add supplementary ansible roles that are "
"not specified in the standard ansible-role-requirements."
msgstr ""
"File opsional baru /etc/openstack_deploy/user-role-requirements.yml sekarang "
"tersedia untuk seorang penyebar untuk menimpa entri individual di file "
"upstream ansible-role-requirements. Ini dapat digunakan untuk menunjuk ke "
"repo alternatif yang berisi perbaikan lokal, atau untuk menambahkan peran "
"tambahan yang mungkin tidak ditentukan dalam standard ansible-role-"
"requirements."

msgid ""
"A new playbook ``infra-journal-remote.yml`` to ship journals has been added. "
"Physical hosts will now ship the all available systemd journals to the "
"logging infrastructure. The received journals will be split up by host and "
"stored in the `/var/log/journal/remote` directory. This feature will give "
"deployers greater access/insight into how the cloud is functioning requiring "
"nothing more that the systemd built-ins."
msgstr ""
"Playbook baru ``infra-jurnal-remote.yml`` untuk mengirim jurnal telah "
"ditambahkan. Host fisik sekarang akan mengirimkan semua jurnal systemd yang "
"tersedia ke infrastruktur logging. Jurnal yang diterima akan dibagi oleh "
"host dan disimpan di direktori `/var/log/journal/remote`. Fitur ini akan "
"memberikan akses/wawasan (access/insight) yang lebih luas kepada pengawas "
"tentang bagaimana cloud berfungsi, tidak memerlukan apa-apa lagi selain "
"systemd built-in."

msgid ""
"A new playbook ``os-zun-install.yml`` has been added which will deploy the "
"zun service to hosts assigned to the host group ``zun-infra_hosts``."
msgstr ""
"Playbook baru `` os-zun-install.yml`` telah ditambahkan yang akan "
"menyebarkan layanan zun ke host yang ditugaskan ke grup host ``zun-"
"infra_hosts``."

msgid ""
"A new repository for installing modern erlang from ESL (erlang solutions) "
"has been added giving us the ability to install and support modern stable "
"erlang over numerous operating systems."
msgstr ""
"Sebuah repositori baru untuk menginstal erlang modern dari ESL (solusi "
"erlang) telah ditambahkan memberi kami kemampuan untuk menginstal dan "
"mendukung erlang stabil modern di berbagai sistem operasi."

msgid ""
"A new switch ``pip_install_build_packages`` is introduced to allow toggling "
"compiler and development library installation. The legacy behavior of "
"installing the compiler and development libraries is maintained as the "
"switch is enabled by default."
msgstr ""
"Switch baru ``pip_install_build_packages`` diperkenalkan untuk memungkinkan "
"pengubahan kompilasi dan pengembangan pustaka pengembangan. Perilaku lama "
"menginstal kompiler dan perpustakaan pengembangan dipertahankan sebagai "
"switch diaktifkan secara default."

msgid ""
"A new task has been added to the \"os-lxc-container-setup.yml\" common-tasks "
"file. This new task will allow for additional configurations to be added "
"without having to restart the container. This change is helpful in cases "
"where non-impacting config needs to be added or updated to a running "
"containers."
msgstr ""
"Tugas baru telah ditambahkan ke file tugas umum \"os-lxc-container-setup.yml"
"\". Tugas baru ini akan memungkinkan konfigurasi tambahan ditambahkan tanpa "
"harus memulai ulang (restart) kontainer. Perubahan ini bermanfaat dalam "
"kasus di mana konfigurasi yang tidak berdampak perlu ditambahkan atau "
"diperbarui ke kontainer yang sedang berjalan."

msgid ""
"A new task was added to disable ICMPv6 redirects per the requirements in "
"V-38548. However, since this change can cause problems in running OpenStack "
"environments, it is disabled by default. Deployers who wish to enable this "
"task (and disable ICMPv6 redirects) should set "
"``security_disable_icmpv6_redirects`` to ``yes``."
msgstr ""
"Tugas baru ditambahkan untuk menonaktifkan pengalihan ICMPv6 sesuai "
"persyaratan dalam V-38548. Namun, karena perubahan ini dapat menyebabkan "
"masalah dalam menjalankan lingkungan OpenStack, itu dinonaktifkan secara "
"default. Penyebar yang ingin mengaktifkan tugas ini (dan menonaktifkan "
"pengalihan ICMPv6) harus menetapkan ``security_disable_icmpv6_redirects`` ke "
"``yes``."

msgid ""
"A new value ``epel_gpg_keys`` can be overridden to use a different GPG key "
"for the EPEL-7 RPM package repo instead of the vendored key used by default."
msgstr ""
"Nilai baru ``epel_gpg_keys`` dapat diganti untuk menggunakan kunci GPG yang "
"berbeda untuk repo paket EPEL-7 RPM, bukan kunci yang dibatalkan yang "
"digunakan secara default."

msgid ""
"A new variable called ``ceph_extra_components`` is available for the "
"ceph_client role. Extra components, packages, and services that are not "
"shipped by default by OpenStack-Ansible can be defined here."
msgstr ""
"Variabel baru yang disebut ``ceph_extra_components`` tersedia untuk peran "
"ceph_client. Komponen, paket, dan layanan tambahan yang tidak dikirimkan "
"secara default oleh OpenStack-Ansible dapat didefinisikan di sini."

msgid ""
"A new variable called ``lxc_container_cache_files`` has been implemented "
"which contains a list of dictionaries that specify files on the deployment "
"host which should be copied into the LXC container cache and what attributes "
"to assign to the copied file."
msgstr ""
"Variabel baru yang disebut ``lxc_container_cache_files`` telah "
"diimplementasikan yang berisi daftar kamus yang menentukan file pada host "
"penyebaran yang harus disalin ke dalam cache kontainer LXC dan atribut apa "
"yang ditugaskan untuk file yang disalin."

msgid ""
"A new variable has been added to allow a deployer to control the restart of "
"containers from common-tasks/os-lxc-container-setup.yml. This new option is "
"``lxc_container_allow_restarts`` and has a default of ``true``. If a "
"deployer wishes to disable the auto-restart functionality they can set this "
"value to ``false`` and automatic container restarts will be disabled. This "
"is a complement to the same option already present in the "
"lxc_container_create role. This option is useful to avoid uncoordinated "
"restarts of galera or rabbitmq containers if the LXC container configuration "
"changes in a way that requires a restart."
msgstr ""
"Variabel baru telah ditambahkan untuk memungkinkan deployer untuk mengontrol "
"restart kontainer dari common-tasks/os-lxc-container-setup.yml. Opsi baru "
"ini adalah ``lxc_container_allow_restarts`` dan memiliki standar ``true``. "
"Jika seorang deployer ingin menonaktifkan fungsi restart otomatis, mereka "
"dapat mengatur nilai ini menjadi ``false`` dan restart kontainer otomatis "
"akan dinonaktifkan. Ini adalah pelengkap dari opsi yang sama yang sudah ada "
"dalam peran lxc_container_create. Opsi ini berguna untuk menghindari restart "
"galera atau rabbitmq yang tidak terkoordinasi jika konfigurasi kontainer LXC "
"berubah dengan cara yang membutuhkan restart."

msgid ""
"A new variable has been added to allow a deployer to control the restart of "
"containers via the handler. This new option is "
"``lxc_container_allow_restarts`` and has a default of ``true``. If a "
"deployer wishes to disable the auto-restart functionality they can set this "
"value to ``false`` and automatic container restarts that are not absolutely "
"required will be disabled."
msgstr ""
"Variabel baru telah ditambahkan untuk memungkinkan seorang deployer untuk "
"mengontrol restart kontainer melalui handler. Opsi baru ini adalah "
"``lxc_container_allow_restarts`` dan memiliki standar ``true``. Jika seorang "
"deployer ingin menonaktifkan fungsi restart otomatis mereka dapat menetapkan "
"nilai ini menjadi ``false`` dan restart kontainer otomatis yang tidak mutlak "
"diperlukan akan dinonaktifkan."

msgid ""
"A new variable has been added to allow a deployer to control the restart of "
"containers via the handler. This new option is "
"``lxc_container_allow_restarts`` and has a default of ``yes``. If a deployer "
"wishes to disable the auto-restart functionality they can set this value to "
"``no`` and automatic container restarts that are not absolutely required "
"will be disabled."
msgstr ""
"Variabel baru telah ditambahkan untuk memungkinkan seorang deployer untuk "
"mengontrol restart kontainer melalui handler. Opsi baru ini adalah `` "
"lxc_container_allow_restarts`` dan memiliki default ``yes``. Jika seorang "
"deployer ingin menonaktifkan fungsionalitas restart otomatis, mereka dapat "
"mengatur nilai ini menjadi ``no`` dan restart kontainer otomatis yang tidak "
"mutlak diperlukan akan dinonaktifkan."

msgid ""
"A new variable has been added which allows deployers to set the container "
"technology OSA will use when running a deployment in containers. This new "
"variable is ``container_tech`` which has a default value of \"lxc\"."
msgstr ""
"Variabel baru telah ditambahkan yang memungkinkan deployer untuk mengatur "
"teknologi kontainer yang akan digunakan OSA saat menjalankan penyebaran "
"dalam kontainer. Variabel baru ini adalah ``container_tech`` yang memiliki "
"nilai default \"lxc\"."

msgid ""
"A new variable has been introduced into the ``os_tempest`` role named "
"``tempest_image_downloader``. When set to ``deployment-host`` (which is the "
"default) it uses the deployment host to handle the download of images to be "
"used for tempest testing. The images are then uploaded to the target host "
"for uploading into Glance."
msgstr ""
"Variabel baru telah diperkenalkan ke peran ``os_tempest`` bernama "
"``tempest_image_downloader``. Ketika diatur ke ``deployment-host`` (yang "
"merupakan default), ia menggunakan host penyebaran untuk menangani unduhan "
"image yang akan digunakan untuk pengujian prahara. Image tersebut kemudian "
"diunggah ke host target untuk diunggah ke Glance."

msgid ""
"A new variable is supported in the ``neutron_services`` dictionary called "
"``service_conf_path``. This variable enables services to deploy their config "
"templates to paths outside of /etc/neutron by specifying a directory using "
"the new variable."
msgstr ""
"Variabel baru didukung dalam kamus ``neutron_services`` yang disebut "
"``service_conf_path``. Variabel ini memungkinkan layanan untuk menyebarkan "
"template konfigurasi mereka ke jalur di luar /etc/neutron dengan menetapkan "
"direktori menggunakan variabel baru."

msgid ""
"A new variable, ``tempest_flavors``, has been added to the os_tempest role "
"allowing users to define nova flavors to be during tempest testing."
msgstr ""
"Variabel baru, ``tempest_flavours``, telah ditambahkan ke peran os_tempest "
"yang memungkinkan pengguna untuk menentukan rasa nova selama pengujian "
"prahara."

msgid ""
"A new variable, ``tempest_roles``, has been added to the os_tempest role "
"allowing users to define keystone roles to be during tempest testing."
msgstr ""
"Variabel baru, ``tempest_roles``, telah ditambahkan ke peran os_tempest yang "
"memungkinkan pengguna untuk menentukan peran keystone selama pengujian "
"prahara."

msgid ""
"A new version of keepalived will be installed on the haproxy nodes if the "
"variable ``keepalived_use_latest_stable`` is set to ``True`` and more than "
"one haproxy node is configured. The update of the package will cause "
"keepalived to restart and therefore will cause the virtual IP addresses "
"managed by keepalived to be briefly unconfigured, then reconfigured."
msgstr ""
"Versi baru keepalived akan diinstal pada node haproxy jika variabel "
"``keepalived_use_latest_stable`` diatur ke ``True`` dan lebih dari satu node "
"haproxy dikonfigurasi. Pembaruan (update) paket akan menyebabkan keepalived "
"untuk memulai kembali dan oleh karena itu akan menyebabkan alamat IP virtual "
"yang dikelola oleh keepalived secara singkat tidak terkonfigurasi, kemudian "
"dikonfigurasi ulang."

msgid ""
"A self-signed certificate will now be generated by default when HAproxy is "
"used as a load balancer. This certificate is used to terminate the public "
"endpoint for Horizon and all OpenStack API services."
msgstr ""
"Sertifikat yang ditandatangani sendiri sekarang akan dihasilkan secara "
"default ketika HAproxy digunakan sebagai penyeimbang beban (load balancer). "
"Sertifikat ini digunakan untuk mengakhiri endpoint publik untuk Horizon dan "
"semua layanan OpenStack API."

msgid ""
"A sudoers entry has been added to the repo_servers in order to allow the "
"nginx user to stop and start nginx via the init script. This is implemented "
"in order to ensure that the repo sync process can shut off nginx while "
"synchronising data from the master to the slaves."
msgstr ""
"Entri sudoer telah ditambahkan ke repo_servers untuk memungkinkan pengguna "
"nginx berhenti dan mulai nginx melalui skrip init. Ini diterapkan untuk "
"memastikan bahwa proses sinkronisasi repo dapat mematikan nginx saat "
"menyinkronkan data dari master ke slave."

msgid ""
"A sudoers entry is added to the repo_servers to allow the nginx user to stop "
"and start NGINX from the init script. This ensures that the repo sync "
"process can shut off NGINX while synchronizing data from master to slaves."
msgstr ""
"Entri sudoers ditambahkan ke repo_servers untuk memungkinkan pengguna nginx "
"berhenti dan memulai NGINX dari skrip init. Ini memastikan bahwa proses "
"sinkronisasi repo dapat mematikan NGINX sambil menyinkronkan data dari "
"master ke slave."

msgid ""
"A task was added that restricts ICMPv4 redirects to meet the requirements of "
"V-38524 in the STIG. This configuration is disabled by default since it "
"could cause issues with LXC in some environments."
msgstr ""
"Sebuah tugas ditambahkan yang membatasi pengalihan ICMPv4 untuk memenuhi "
"persyaratan V-38524 di STIG. Konfigurasi ini dinonaktifkan secara default "
"karena dapat menyebabkan masalah dengan LXC di beberapa lingkungan."

msgid ""
"A task was added to disable secure ICMP redirects per the requirements in "
"V-38526. This change can cause problems in some environments, so it is "
"disabled by default. Deployers can enable the task (which disables secure "
"ICMP redirects) by setting ``security_disable_icmpv4_redirects_secure`` to "
"``yes``."
msgstr ""
"Tugas ditambahkan untuk menonaktifkan pengalihan ICMP aman sesuai "
"persyaratan di V-38526. Perubahan ini dapat menyebabkan masalah di beberapa "
"lingkungan, sehingga dinonaktifkan secara default. Deployer dapat "
"mengaktifkan tugas (yang menonaktifkan pengalihan ICMP aman) dengan mengatur "
"``security_disable_icmpv4_redirects_secure`` ke ``yes``."

msgid ""
"A typical OSA install will put the neutron and octavia queues on different "
"vhosts thus preventing the event streamer from working While octavia is "
"streaming to its own queue the consumer on the neutron side listens to the "
"neutron queue. With a recent octavia enhancement a separate queue for the "
"event streamer can be configured. This patch will set up the event streamer "
"to post into the neutron queue using neutron's credentials. Thus reaching "
"the consumer on the neutron-lbaas side and allowing for streaming."
msgstr ""
"Instalasi OSA tipikal akan menempatkan antrian neutron dan octavia pada "
"vhost yang berbeda sehingga mencegah event streamer bekerja. Sementara "
"octavia mengalir ke antriannya sendiri, konsumen di sisi neutron "
"mendengarkan antrian neutron. Dengan peningkatan octavia baru-baru ini, "
"antrian terpisah untuk event streamer dapat dikonfigurasi. Patch ini akan "
"mengatur event streamer untuk mengirim ke antrian neutron menggunakan "
"kredensial neutron. Sehingga menjangkau konsumen di sisi neutron-lbaas dan "
"memungkinkan untuk streaming."

msgid ""
"A variable named ``bootstrap_user_variables_template`` has been added to the "
"bootstrap-host role so the user can define the user variable template "
"filename for AIO deployments"
msgstr ""
"Variabel bernama ``bootstrap_user_variables_template`` telah ditambahkan ke "
"peran bootstrap-host sehingga pengguna dapat menentukan nama file template "
"variabel pengguna untuk penyebaran AIO"

msgid ""
"AIDE initialization is now always run on subsequent playbook runs when "
"``initialize_aide`` is set to ``yes``. The initialization will be skipped if "
"AIDE isn't installed or if the AIDE database already exists."
msgstr ""
"Inisialisasi AIDE sekarang selalu dijalankan pada playbook berikutnya yang "
"berjalan ketika ``initialize_aide`` diatur ke ``yes``. Inisialisasi akan "
"dilewati jika AIDE tidak diinstal atau jika database AIDE sudah ada."

msgid ""
"AIDE initialization is now always run on subsequent playbook runs when "
"``security_initialize_aide`` is set to ``yes``. The initialization will be "
"skipped if AIDE isn't installed or if the AIDE database already exists."
msgstr ""
"Inisialisasi AIDE sekarang selalu dijalankan pada playbook berikutnya yang "
"berjalan ketika ``security_initialize_aide`` diatur ke ``yes``. Inisialisasi "
"akan dilewati jika AIDE tidak diinstal atau jika database AIDE sudah ada."

msgid ""
"AIDE is configured to skip the entire ``/var`` directory when it does the "
"database initialization and when it performs checks. This reduces disk I/O "
"and allows these jobs to complete faster."
msgstr ""
"AIDE dikonfigurasikan untuk melewati seluruh direktori  ``/var`` ketika "
"melakukan inisialisasi database dan ketika melakukan pemeriksaan. Ini "
"mengurangi I/O disk dan memungkinkan pekerjaan ini untuk menyelesaikan lebih "
"cepat."

msgid ""
"Add ``get_networks`` command to the neutron library. This will return "
"network information for all networks, and fail if the specified ``net_name`` "
"network is not present. If no ``net_name`` is specified network information "
"will for all networks will be returned without performing a check on an "
"existing ``net_name`` network."
msgstr ""
"Tambahkan perintah ``get_networks`` ke perpustakaan neutron. Ini akan "
"mengembalikan informasi jaringan untuk semua jaringan, dan gagal jika "
"jaringan ``net_name`` yang ditentukan tidak ada. Jika tidak ada ``net_name`` "
"yang ditentukan, informasi jaringan untuk semua jaringan akan dikembalikan "
"tanpa melakukan pemeriksaan pada jaringan ``net_name`` yang ada."

msgid ""
"Add architecture-specific locations for percona-xtrabackup and qpress, with "
"alternate locations provided for ppc64el due to package inavailability from "
"the current provider."
msgstr ""
"Tambahkan lokasi architecture-specific untuk percona-xtrabackup dan qpress, "
"dengan lokasi alternatif disediakan untuk ppc64el karena tidak tersedianya "
"paket dari provider saat ini."

msgid "Add support for Ubuntu on IBM z Systems (s390x)."
msgstr "Tambahkan dukungan untuk Ubuntu pada IBM z Systems (s390x)."

msgid "Add support for ``neutron`` as an ``enabled_network_interface``."
msgstr ""
"Tambahkan dukungan untuk ``neutron`` sebagai ``enabled_network_interface``."

msgid ""
"Add support for the cinder v3 api. This is enabled by default, but can be "
"disabled by setting the ``cinder_enable_v3_api`` variable to ``false``."
msgstr ""
"Tambahkan dukungan untuk api cinder v3. Ini diaktifkan secara default, "
"tetapi dapat dinonaktifkan dengan mengatur variabel ``cinder_enable_v3_api`` "
"menjadi ``false``."

msgid ""
"Add the launchpad and bugzilla keys in tempest_test_blacklist ansible "
"variable. Developers must have a way to trackdown why a test was inserted in "
"the skiplist, and one of the ways is through bugs. This feature add the "
"information regarding it in the list of skipped tests on os_tempest"
msgstr ""
"Tambahkan launchpad dan kunci bugzilla di tempest_test_blacklist variabel "
"ansible. Pengembang harus memiliki cara untuk melacak mengapa tes dimasukkan "
"dalam daftar kosong, dan salah satu caranya adalah melalui bug. Fitur ini "
"menambahkan informasi mengenai hal ini dalam daftar tes yang dilewati pada "
"os_tempest"

msgid ""
"Add the possibility to disable openrc v2 download in the dashboard. new var "
"``horizon_show_keystone_v2_rc`` can be set to ``False`` to remove the entry "
"for the openrc v2 download."
msgstr ""
"Tambahkan kemungkinan untuk menonaktifkan unduhan openrc v2 di dasbor. var "
"baru ``horizon_show_keystone_v2_rc`` dapat diatur ke ``False`` untuk "
"menghapus entri untuk unduhan openrc v2."

msgid ""
"Add the possibility to use python-tempestconf tool to generate tempest.conf "
"file, rather than use the role template."
msgstr ""
"Tambahkan kemungkinan untuk menggunakan alat python-tempestconf untuk "
"menghasilkan file tempest.conf, daripada menggunakan templat peran."

msgid ""
"Added 2 new varibles for all groups - `oslomsg_notify_policies` and "
"`oslomsg_rpc_policies`. These variables contain default rabbitmq policies, "
"which will be applied for every rabbitmq vhost. As for now they will enable "
"[HA mode](https://www.rabbitmq.com/ha.html) for all vhosts. If you would "
"like to disable HA mode just set these variables to empty lists inside your "
"`user_config.yml`"
msgstr ""
"Menambahkan 2 variabel baru untuk semua grup - `oslomsg_notify_policies` dan "
"`oslomsg_rpc_policies`. Variabel ini mengandung kebijakan rabbitmq default, "
"yang akan diterapkan untuk setiap rabbitmq vhost. Adapun saat ini mereka "
"akan mengaktifkan [mode HA](https://www.rabbitmq.com/ha.html) untuk semua "
"vhosts. Jika Anda ingin menonaktifkan mode HA, cukup atur variabel ini ke "
"daftar kosong di dalam `user_config.yml` Anda"

msgid ""
"Added ``cinder_auth_strategy`` variable to configure Cinder's auth strategy "
"since Cinder can work in noauth mode as well."
msgstr ""
"Menambahkan variabel ``cinder_auth_strategy`` untuk mengkonfigurasi strategi "
"autentikasi Cinder karena Cinder juga dapat bekerja dalam mode noauth."

msgid ""
"Added ``horizon_apache_custom_log_format`` tunable to the os-horizon role "
"for changing CustomLog format. Default is \"combined\"."
msgstr ""
"Menambahkan ``horizon_apache_custom_log_format`` yang dapat disetel ke peran "
"os-horizon untuk mengubah format CustomLog. Default adalah \"combined\"."

msgid ""
"Added a boolean var `haproxy_service_enabled` to the "
"`haproxy_service_configs` dict to support toggling haproxy endpoints on/off."
msgstr ""
"Menambahkan boolean var `haproxy_service_enabled` ke perintah "
"`haproxy_service_configs` untuk mendukung pengalihan on/off  endpoint "
"haproxy."

msgid ""
"Added a function in dynamic_inventory.py to improve the identification of "
"incorrect settings inside the user config files."
msgstr ""
"Menambahkan fungsi di dynamic_inventory.py untuk meningkatkan identifikasi "
"pengaturan yang salah di dalam file konfigurasi pengguna."

msgid ""
"Added a new ``haproxy_extra_services`` var which will allow extra haproxy "
"endpoint additions."
msgstr ""
"Menambahkan var ``haproxy_extra_services`` baru yang akan memungkinkan "
"penambahan  endpoint haproxy tambahan."

msgid ""
"Added keystone_apache_custom_log_format tunable for changing CustomLog "
"format. Default is \"combined\"."
msgstr ""
"Menambahkan keystone_apache_custom_log_format tunable untuk mengubah format "
"CustomLog. Default adalah \"combined\"."

msgid ""
"Added new parameter ```cirros_img_disk_format`` to support disk formats "
"other than qcow2."
msgstr ""
"Menambahkan parameter baru ```cirros_img_disk_format`` untuk mendukung "
"format disk selain qcow2."

msgid ""
"Added new parameter ``tempest_services`` for setting "
"tempest_service_available_{service_name} var automatically."
msgstr ""
"Menambahkan parameter baru ``tempest_services`` untuk pengaturan "
"tempest_service_available_ {service_name} var secara otomatis."

msgid ""
"Added new variable ``tempest_image_file``. This variable replaces the hard-"
"coded value for the ``img_file`` setting in tempest.conf.j2.  This will "
"allow users to specify images other than cirros."
msgstr ""
"Menambahkan variabel baru ``tempest_image_file``. Variabel ini menggantikan "
"nilai hard-coded untuk pengaturan ``img_file`` di tempest.conf.j2. Ini akan "
"memungkinkan pengguna untuk menentukan image selain cirro."

msgid ""
"Added new variable ``tempest_img_disk_format``. This variable replaces "
"``cirros_img_disk_format``."
msgstr ""
"Menambahkan variabel baru ``tempest_img_disk_format``. Variabel ini "
"menggantikan ``cirros_img_disk_format``."

msgid "Added new variable ``tempest_img_name``."
msgstr "Menambahkan variabel baru ``tempest_img_name``."

msgid ""
"Added new variable ``tempest_img_url``. This variable replaces "
"``cirros_tgz_url`` and ``cirros_img_url``."
msgstr ""
"Menambahkan variabel baru ``tempest_img_url``. Variabel ini menggantikan "
"``cirros_tgz_url`` dan ``cirros_img_url``."

msgid ""
"Added new variable ``tempest_volume_backend_names`` and updated templates/"
"tempest.conf.j2 to point ``backend_names`` at this variable"
msgstr ""
"Menambahkan variabel baru ``tempest_volume_backend_names`` dan templates/"
"tempest.conf.j2  yang diperbarui ke point ``backend_names`` pada variabel ini"

msgid "Added playbook for deploying Rally in the utility containers"
msgstr "Menambahkan playbook untuk menyebarkan Rally dalam kontainer utilitas"

msgid ""
"Added possibility to override ceph.conf partially by defining "
"`ceph_client_ceph_conf_overrides` variable. It uses regular format of "
"OpenStack-Ansible overrides. From now on, config_template plugin should be "
"present for ansible."
msgstr ""
"Menambahkan kemungkinan untuk menimpa ceph.conf sebagian dengan "
"mendefinisikan variabel `ceph_client_ceph_conf_overrides`. Ini menggunakan "
"format reguler dari menimpa OpenStack-Ansible. Mulai sekarang, "
"config_template plugin harus ada untuk ansible."

msgid ""
"Added storage policy so that deployers can override how to store the logs. "
"``per_host`` stores logs in a sub-directory per host. ``per_program`` stores "
"logs in a single file per application which facilitates troubleshooting easy."
msgstr ""
"Menambahkan kebijakan penyimpanan sehingga pengalih dapat menimpa cara "
"menyimpan log. ``per_host`` menyimpan log di sub-direktori per host. "
"``per_program`` menyimpan log dalam satu file per aplikasi yang memudahkan "
"pemecahan masalah."

msgid ""
"Added support for ironic-OneView drivers. Check the documentation on how to "
"enable them."
msgstr ""
"Dukungan tambahan untuk driver ironic-OneView. Periksa dokumentasi tentang "
"cara mengaktifkannya."

msgid ""
"Added support for specifying GID and UID for cinder system user by defining "
"``cinder_system_user_uid`` and ``cinder_system_group_gid``. This setting is "
"optional."
msgstr ""
"Menambahkan dukungan untuk menentukan GID dan UID untuk pengguna sistem "
"cinder dengan mendefinisikan ``cinder_system_user_uid`` dan "
"``cinder_system_group_gid``. Pengaturan ini opsional."

msgid ""
"Added support for using mod_auth_openidc instead of shibboleth as a service "
"provider for supporting users who have a preference to use OIDC for "
"federation. Mod_auth_openidc is the apache module that is recommended in the "
"keystone documentation for implementing openidc. Added a variable to called "
"apache_mod to keystone_sp, if left undefined shibboleth will continue to be "
"installed by default provided keystone_sp is not empty. Mod_auth_openidc "
"will not be installed unless it is spelled correctly, any misspellings will "
"result in a shibboleth install. Note that installing shibboleth on Debian "
"based metal distro deployments may break services that depend on libcurl4, "
"as shib2 requires libcurl3, and they are unable to coexist. This can be "
"resolved when there is a shib3 package available in a future release of "
"Ubuntu/Debian. There is currently no support for simultaneous use of "
"shibboleth2 and mod_auth_openidc."
msgstr ""
"Menambahkan dukungan untuk menggunakan mod_auth_openidc bukan shibboleth "
"sebagai penyedia layanan untuk mendukung pengguna yang memiliki preferensi "
"untuk menggunakan OIDC untuk federasi. Mod_auth_openidc adalah modul apache "
"yang direkomendasikan dalam dokumentasi keystone untuk mengimplementasikan "
"openidc. Menambahkan variabel yang disebut apache_mod ke keystone_sp, jika "
"dibiarkan shibboleth yang tidak terdefinisi akan terus diinstal secara "
"default asalkan keystone_sp tidak kosong. Mod_auth_openidc tidak akan "
"diinstal kecuali jika dieja dengan benar, kesalahan ejaan akan menghasilkan "
"pemasangan shibboleth. Perhatikan bahwa menginstal shibboleth pada "
"penyebaran distro berbasis logam Debian dapat memutuskan layanan yang "
"bergantung pada libcurl4, karena shib2 membutuhkan libcurl3, dan mereka "
"tidak dapat hidup berdampingan. Ini dapat diatasi ketika ada paket shib3 "
"yang tersedia dalam rilis Ubuntu/Debian di masa mendatang. Saat ini tidak "
"ada dukungan untuk penggunaan simultan shibboleth2 dan mod_auth_openidc."

msgid ""
"Added the ``lxc_container_recreate`` option, which will destroy then "
"recreate LXC containers. The container names and IP addresses will remain "
"the same, as will the MAC addresses of any containers using the "
"``lxc_container_fixed_mac`` setting."
msgstr ""
"Menambahkan opsi ``lxc_container_recreate``, yang akan menghancurkan "
"kemudian membuat ulang kontainer LXC. Nama kontainer dan alamat IP akan "
"tetap sama, seperti halnya alamat MAC dari kontainer apa pun menggunakan "
"pengaturan ``lxc_container_fixed_mac``."

msgid ""
"Added the ability to configure vendor data for Nova in order to be able to "
"push things via the metadata service or config drive."
msgstr ""
"Menambahkan kemampuan untuk mengonfigurasikan data vendor untuk Nova agar "
"dapat mendorong berbagai hal melalui layanan metadata atau drive konfigurasi."

msgid ""
"Added variable `horizon_bind_address` which defines IP address where Apache "
"will listen on `horizon_listen_ports`"
msgstr ""
"Menambahkan variabel `horizon_bind_address` yang menentukan alamat IP tempat "
"Apache akan mendengarkan di `horizon_listen_ports`"

msgid ""
"Added variables `cinder_active_active_cluster` and "
"`cinder_active_active_cluster_name` that allow to explicitly enable or "
"disable active/active feature, and set cluster name."
msgstr ""
"Menambahkan variabel `cinder_active_active_cluster` "
"dan`cinder_active_active_cluster_name` yang memungkinkan untuk mengaktifkan "
"atau menonaktifkan fitur aktif/aktif secara eksplisit, dan menetapkan nama "
"kluster."

msgid ""
"Added variables `horizon_session_engine` and `horizon_session_caches` which "
"can be used to configure horizon session engine and a backend for it."
msgstr ""
"Menambahkan variabel `horizon_session_engine` dan`horizon_session_caches` "
"yang dapat digunakan untuk mengkonfigurasi mesin sesi horizon dan backend "
"untuk itu."

msgid ""
"Added variables `magnum_cluster_templates` and `magnum_flavors` which allow "
"deployers to define coe cluster template and nova flavors creation during "
"role execution. These variables may contain list of resources to add. All "
"keys supported by appropriate ansible modules may be passed as items in the "
"list."
msgstr ""
"Variabel yang ditambahkan `magnum_cluster_templates` dan` magnum_flavours` "
"yang memungkinkan para deployer untuk mendefinisikan coe cluster template "
"dan pembuatan flavors nova selama eksekusi peran. Variabel-variabel ini "
"mungkin berisi daftar sumber daya untuk ditambahkan. Semua kunci yang "
"didukung oleh ansible modules yang sesuai dapat diteruskan sebagai item "
"dalam daftar."

msgid ""
"Adding a new nova.conf entry, live_migration_uri. This entry will default to "
"a ``qemu-ssh://`` uri, which uses the ssh keys that have already been "
"distributed between all of the compute hosts."
msgstr ""
"Menambahkan entri nova.conf baru, live_migration_uri. Entri ini akan secara "
"default menjadi ``qemu-ssh://`` uri,  yang menggunakan kunci ssh yang telah "
"didistribusikan antara semua host komputasi."

msgid ""
"Adding support for Mistral to be built as part of the repo build process."
msgstr ""
"Menambahkan dukungan untuk Mistral untuk dibangun sebagai bagian dari proses "
"pembuatan repo."

msgid ""
"Adding the ``os-mistral-install.yml`` file to deploy mistral to hosts tagged "
"with hostgroup ``mistral_all``"
msgstr ""
"Menambahkan file ``os-mistral-install.yml`` untuk menyebarkan mistral ke "
"host yang ditandai dengan hostgroup ``mistral_all``"

msgid ""
"Additional libvirt ceph client secrets can be defined to support attaching "
"volumes from different ceph clusters."
msgstr ""
"Rahasia klien libvirt ceph tambahan dapat didefinisikan untuk mendukung "
"pelampiran (attaching) volume dari berbagai cluster ceph."

msgid ""
"Additional volume-types can be created by defining a list named "
"``extra_volume_types`` in the desired backend of the variable(s) "
"``cinder_backends``"
msgstr ""
"Tipe volume tambahan dapat dibuat dengan mendefinisikan daftar yang bernama "
"``extra_volume_types`` di backend variabel yang diinginkan "
"``cinder_backends``"

msgid ""
"Adds a new flag to enable Octavia V2 API (disabled by default) to facilitate "
"to run Octavia stand alone (without Neutron)"
msgstr ""
"Menambahkan flag baru untuk mengaktifkan Octavia V2 API (dinonaktifkan "
"secara default) untuk memfasilitasi menjalankan Octavia berdiri sendiri "
"(tanpa Neutron)"

msgid ""
"Adds a new flag to toggle Octavia V1 API (the API needed to run in "
"conjunction with Neutron) and enables it by default."
msgstr ""
"Menambahkan flag baru untuk mengaktifkan Octavia V1 API (API yang diperlukan "
"untuk berjalan bersama dengan Neutron) dan mengaktifkannya secara default."

msgid ""
"Adds a way for the system to automatically create the Octavia management "
"network if octavia_service_net_setup is enabled (DEFAULT). Additional "
"parameters can control the setup."
msgstr ""
"Menambahkan cara bagi sistem untuk secara otomatis membuat jaringan "
"manajemen Octavia jika octavia_service_net_setup diaktifkan (DEFAULT). "
"Parameter tambahan dapat mengontrol pengaturan."

msgid ""
"Adds iptables rules to block taffic from the octavia managment network to "
"the octavia container for both ipv4 and ipv6."
msgstr ""
"Menambahkan aturan iptables untuk memblokir lalu lintas dari jaringan "
"manajemen octavia ke kontainer octavia untuk ipv4 dan ipv6."

msgid ""
"Adds new variable `tempest_tempestconf_profile_extras` which allows to "
"extend `tempest_tempestconf_profile` dictionary without need to override all "
"existing keys. `tempest_tempestconf_profile_extras` has presedence over "
"`tempest_tempestconf_profile`. For example, it may be used to define extra "
"image or it's format."
msgstr ""
"Menambahkan variabel baru `tempest_tempestconf_profile_extras` yang "
"memungkinkan untuk diperpanjang `tempest_tempestconf_profile` dictionary "
"tanpa perlu mengganti semua kunci yang ada. "
"`tempest_tempestconf_profile_extras` lebih diutamakan "
"`tempest_tempestconf_profile`. Misalnya, ini dapat digunakan untuk "
"menentukan image ekstra atau formatnya."

msgid ""
"Adds support for glance-image-id and automatic uploading of the image if "
"octavia_amp_image_upload_enabled is True (Default is False). This is mostly "
"tp work around the limitations of Ansible's OpenStack support and should not "
"be used in prodcution settings. Instead refer to the documentation to upload "
"images yourself."
msgstr ""
"Menambahkan dukungan untuk glance-image-id dan mengunggah otomatis image "
"jika octavia_amp_image_upload_enabled adalah True (Default is False). Ini "
"sebagian besar adalah untuk mengatasi keterbatasan dukungan OpenStack "
"Ansible dan tidak boleh digunakan dalam pengaturan produksi. Alih-alih "
"merujuk pada dokumentasi untuk mengunggah image sendiri."

msgid ""
"Adds support for the horizon ironic-ui dashboard. The dashboard will be "
"automatically enabled if any ironic hosts are defined."
msgstr ""
"Menambahkan dukungan untuk dasbor ironic-ui horizon. Dasbor akan diaktifkan "
"secara otomatis jika ada host ironis ditentukan."

msgid ""
"Adds support for the horizon magnum-ui dashboard. The dashboard will be "
"automatically enabled if any magnum hosts are defined."
msgstr ""
"Menambahkan dukungan untuk dashboard horizon magnum-ui. Dasbor akan "
"diaktifkan secara otomatis jika ada host magnum yang ditentukan."

msgid ""
"Adds support for the horizon octavia-ui dashboard. The dashboard will be "
"automatically enabled if any octavia hosts are defined. If both Neutron "
"LBaaSv2 and Octavia are enabled, two Load Balancer panels will be visible in "
"Horizon."
msgstr ""
"Menambahkan dukungan untuk dasbor horizon octavia-ui. Dasbor akan diaktifkan "
"secara otomatis jika ada host octavia yang ditentukan. Jika Neutron LBaaSv2 "
"dan Octavia diaktifkan, dua panel Load Balancer akan terlihat di Horizon."

msgid ""
"Adds support for the horizon trove-ui dashboard. The dashboard will be "
"automatically enabled if any trove hosts are defined."
msgstr ""
"Menambahkan dukungan untuk dasbor trove-ui horizon. Dasbor akan diaktifkan "
"secara otomatis jika ada trove host yang ditentukan."

msgid ""
"All OSA releases earlier than 17.0.5, 16.0.4, and 15.1.22 will fail to build "
"the rally venv due to the release of the new cmd2-0.9.0 python library. "
"Deployers are encouraged to update to the latest OSA release which pins to "
"an appropriate version which is compatible with python2."
msgstr ""
"Semua rilis OSA lebih awal dari 17.0.5, 16.0.4, dan 15.1.22 akan gagal "
"membangun rally venv karena rilis python library cmd2-0.9.0 baru. Deployer "
"didorong untuk memperbarui ke rilis OSA terbaru yang menyematkan (pin) ke "
"versi yang sesuai yang kompatibel dengan python2."

msgid ""
"All cinder container services are consolidated into a single "
"``cinder_api_container``. The previously implemented "
"``cinder_scheduler_container`` can be removed."
msgstr ""
"Semua layanan kontainer cinder dikonsolidasikan ke dalam "
"``cinder_api_container`` tunggal. ``cinder_scheduler_container`` yang "
"sebelumnya diterapkan dapat dihapus."

msgid ""
"All nova services are consolidated into the ``nova_api_container`` and the "
"rest of the nova containers can be removed."
msgstr ""
"Semua layanan nova dikonsolidasikan ke dalam ``nova_api_container`` dan sisa "
"kontainer nova dapat dihapus."

msgid ""
"All of the database and database user creates have been removed from the "
"roles into the playbooks. This allows the roles to be tested independently "
"of the deployed database and also allows the roles to be used independently "
"of infrastructure choices made by the integrated OSA project."
msgstr ""
"Semua database dan database yang dibuat pengguna telah dihapus dari peran ke "
"dalam playbook. Hal ini memungkinkan peran untuk diuji secara independen "
"dari database yang digunakan dan juga memungkinkan peran untuk digunakan "
"secara independen dari pilihan infrastruktur yang dibuat oleh proyek OSA "
"terintegrasi."

msgid ""
"All of the discretionary access control (DAC) auditing is now disabled by "
"default. This reduces the amount of logs generated during deployments and "
"minor upgrades.  The following variables are now set to ``no``:"
msgstr ""
"Semua audit discretionary access control (DAC) sekarang dinonaktifkan secara "
"default. Ini mengurangi jumlah log yang dihasilkan selama penerapan dan "
"upgrade kecil. Variabel berikut sekarang disetel ke ``no``:"

msgid ""
"All roles always checks whether the latest package is installed when "
"executed. If a deployer wishes to change the check to only validate the "
"presence of the package, the option ``package_state`` should be set to "
"``present``."
msgstr ""
"Semua peran selalu memeriksa apakah paket terbaru diinstal ketika "
"dijalankan. Jika seorang deployer ingin mengubah tanda centang untuk hanya "
"memvalidasi keberadaan paket, opsi ``package_state`` harus diatur ke "
"``present``."

msgid ""
"All roles are migrated from usage of regular log files to systemd-journald"
msgstr ""
"Semua roles dimigrasikan dari penggunaan file log biasa ke systemd-journald"

msgid ""
"All the ocata versions 15.1.15 and before use mariadb-server 10.1 with no "
"minor version frozen. The latest version, 10.1.31, has presented problems "
"with the state transfer for multi-node environments when the variable "
"``galera_wsrep_sst_method`` is set to ``xtrabackup-v2`` (the default value). "
"This causes a new cluster to fail, or an existing cluster to be unable to "
"transfer state when a node is rebooted."
msgstr ""
"Semua versi ocata 15.1.15 dan sebelum menggunakan mariadb-server 10.1 tanpa "
"versi minor dibekukan. Versi terbaru, 10.1.31, telah menyajikan masalah "
"dengan transfer status untuk lingkungan multi-node ketika variabel "
"``galera_wsrep_sst_method`` diatur ke ``xtrabackup-v2`` (nilai default). Ini "
"menyebabkan cluster baru gagal, atau cluster yang ada tidak dapat "
"mentransfer status saat sebuah node di-boot ulang."

msgid ""
"All the pike versions 16.0.7 and before use mariadb-server 10.1 with no "
"minor version frozen. The latest version, 10.1.31, has presented problems "
"with the state transfer for multi-node environments when the variable "
"``galera_wsrep_sst_method`` is set to ``xtrabackup-v2`` (the default value). "
"This causes a new cluster to fail, or an existing cluster to be unable to "
"transfer state when a node is rebooted."
msgstr ""
"Semua versi pike 16.0.7 dan sebelum menggunakan mariadb-server 10.1 tanpa "
"versi minor dibekukan. Versi terbaru, 10.1.31, telah menyajikan masalah "
"dengan transfer status untuk lingkungan multi-node ketika variabel "
"``galera_wsrep_sst_method`` diatur ke ``xtrabackup-v2`` (nilai default). Ini "
"menyebabkan cluster baru gagal, atau cluster yang ada tidak dapat "
"mentransfer status saat sebuah simpul di-boot ulang."

msgid ""
"All trove services have been consolidated into the ``trove_api_container``. "
"The previously implemented ``trove_conductor_container`` and "
"``trove_taskmanager_container`` can be removed."
msgstr ""
"Semua layanan trove telah dikonsolidasikan ke dalam ``trove_api_container``. "
"``trove_conductor_container`` dan sebelumnya diimplementasikan "
"``trove_taskmanager_container`` dapat dihapus."

msgid ""
"All variables in the security role are now prepended with ``security_`` to "
"avoid collisions with variables in other roles. All deployers who have used "
"the security role in previous releases will need to prepend all security "
"role variables with ``security_``."
msgstr ""
"Semua variabel dalam peran keamanan sekarang diawali dengan ``security_`` "
"untuk menghindari tabrakan dengan variabel di peran lain. Semua deployer "
"yang telah menggunakan peran keamanan dalam rilis sebelumnya perlu "
"menambahkan semua variabel peran keamanan dengan ``security_``."

msgid ""
"Allow the default section in an ini file to be specified using the "
"``default_section`` variable when calling a ``config_template`` task. This "
"defaults to ``DEFAULT``."
msgstr ""
"Izinkan bagian default dalam file ini ditentukan menggunakan variabel "
"``default_section`` saat memanggil tugas ``config_template``. Ini default ke "
"``DEFAULT``."

msgid ""
"Allow the fallocate_reserve option to be set (in bytes) for Swift, to help "
"prevent disks from filling up and prevent a situation where Swift is unable "
"to remove objects due to a lack of disk space. The fallocate_reserve value "
"to is set to a default of 10GB."
msgstr ""
"Izinkan opsi fallocate_reserve diatur (dalam byte) untuk Swift, untuk "
"membantu mencegah pengisian disk dan mencegah situasi di mana Swift tidak "
"dapat menghapus objek karena kurangnya ruang disk. Nilai fallocate_reserve "
"ke diatur ke default 10GB."

msgid ""
"Allows SSL connection to Galera with SSL support. ``galera_use_ssl`` option "
"has to be set to ``true``, in this case self-signed CA cert or user-provided "
"CA cert will be delivered to the container/host."
msgstr ""
"Mengizinkan koneksi SSL ke Galera dengan dukungan SSL. Opsi "
"``galera_use_ssl`` harus disetel ke ``true``, dalam hal ini  self-signed CA "
"cert atau user-provided CA cert  akan dikirimkan ke container/host."

msgid ""
"Although the STIG requires martian packets to be logged, the logging is now "
"disabled by default. The logs can quickly fill up a syslog server or make a "
"physical console unusable."
msgstr ""
"Meskipun STIG membutuhkan paket Mars untuk dicatat, pencatatan log sekarang "
"dinonaktifkan secara default. Log dapat dengan cepat mengisi server syslog "
"atau membuat konsol fisik tidak dapat digunakan."

msgid ""
"Although the ``ceph-rgw`` playbooks do enable Swift object versioning, "
"support in radosgw is currently limited to setting ``X-Versions-Location`` "
"on a container. ``X-History-Location``, understood by native Swift, is "
"currently not supported by radosgw (although the feature is `pending "
"<https://github.com/ceph/ceph/pull/15020>`_ upstream)."
msgstr ""
"Meskipun playbook ``ceph-rgw`` memungkinkan pengubahan versi objek Swift, "
"dukungan di radosgw saat ini terbatas pada pengaturan ``X-Version-Location`` "
"pada sebuah kontainer. ``X-History-Location``, dipahami oleh Swift asli, "
"saat ini tidak didukung oleh radosgw (walaupun fitur ini `pending <https://"
"github.com/ceph/ceph/pull/15020>`_ upstream)."

msgid ""
"An Ansible task was added to disable the ``netconsole`` service on CentOS "
"systems if the service is installed on the system."
msgstr ""
"Tugas Ansible ditambahkan untuk menonaktifkan layanan ``netconsole`` pada "
"sistem CentOS jika layanan diinstal pada sistem."

msgid ""
"An Ansible was added to disable the ``rdisc`` service on CentOS systems if "
"the service is installed on the system."
msgstr ""
"Ansible ditambahkan untuk menonaktifkan layanan ``rdisc`` pada sistem CentOS "
"jika layanan diinstal pada sistem."

msgid ""
"An export flag has been added to the ``inventory-manage.py`` script. This "
"flag allows exporting of host and network information from an OpenStack-"
"Ansible inventory for import into another system, or an alternate view of "
"the existing data. See the developer docs for more details."
msgstr ""
"Flag ekspor telah ditambahkan ke skrip ``inventory-manage.py``. Flag ini "
"memungkinkan ekspor informasi host dan jaringan dari inventaris yang "
"dimungkinkan OpenStack untuk diimpor ke sistem lain, atau tampilan "
"alternatif dari data yang ada. Lihat dokumen pengembang untuk detail lebih "
"lanjut."

msgid ""
"An opportunistic Ansible execution strategy has been implemented. This "
"allows the Ansible linear strategy to skip tasks with conditionals faster by "
"never queuing the task when the conditional is evaluated to be false."
msgstr ""
"Strategi eksekusi oportunistik yang mungkin telah dilaksanakan. Hal ini "
"memungkinkan strategi linier yang dimungkinkan untuk melewati tugas dengan "
"persyaratan lebih cepat dengan tidak pernah mengantri tugas ketika kondisi "
"dievaluasi salah."

msgid ""
"An option has been added allowing the user to define the `user_group` "
"LBaaSv2 uses. The new option is ``neutron_lbaasv2_user_group`` and is set "
"within the OS specific value by default."
msgstr ""
"Opsi telah ditambahkan yang memungkinkan pengguna untuk menentukan "
"penggunaan `user_group` LBaaSv2. Opsi baru adalah "
"``neutron_lbaasv2_user_group`` dan diatur dalam nilai spesifik OS secara "
"default."

msgid ""
"An option to disable the ``machinectl`` quota system has been added. The "
"variable ``lxc_host_machine_quota_disabled`` is a Boolean with a default of "
"**true**. When this option is set to **true** it will disable the "
"``machinectl`` quota system."
msgstr ""
"Opsi untuk menonaktifkan sistem kuota ``machinectl`` telah ditambahkan. "
"Variabel ``lxc_host_machine_quota_disabled`` adalah Boolean dengan default "
"**true**. Ketika opsi ini disetel ke **true**, opsi ini akan menonaktifkan "
"sistem kuota ``machinectl``."

msgid ""
"An option to disable the ``machinectl`` quota system has been changed. The "
"variable ``lxc_host_machine_quota_disabled`` is a Boolean with a default of "
"**false**. When this option is set to **true** it will disable the "
"``machinectl`` quota system."
msgstr ""
"Opsi untuk menonaktifkan sistem kuota ``machinectl`` telah diubah. Variabel "
"``lxc_host_machine_quota_disabled`` adalah Boolean dengan default ** false "
"**. Ketika opsi ini disetel ke ** true **, opsi ini akan menonaktifkan "
"sistem kuota ``machinectl``."

msgid ""
"Any ceph infrastructure components (OSDs, MONs etc) deployed using the OSA/"
"ceph-ansible tooling will be upgraded to the Ceph Nautilus release. "
"Deployers should verify that this upgrade is suitable for their environment "
"before commencing a major upgrade to Train, and consult the ceph-ansible and "
"ceph release notes for Nautilus. For integration with external ceph clusters "
"where OSA does not deploy any of the ceph cluster infrastructure, overrides "
"can be used to select the specific version of ceph repositories used by the "
"OSA ceph_client ansible role."
msgstr ""
"Setiap komponen infrastruktur ceph (OSD, MONs dll) yang dikerahkan "
"menggunakan OSA/ceph-ansible tooling akan ditingkatkan ke rilis Ceph "
"Nautilus. Deployers harus memverifikasi bahwa pemutakhiran ini cocok untuk "
"lingkungan mereka sebelum memulai pemutakhiran besar-besaran ke Train, dan "
"berkonsultasi dengan catatan ceph-ansible dan ceph untuk Nautilus. Untuk "
"integrasi dengan cluster ceph eksternal di mana OSA tidak deploy "
"infrastruktur cluster ceph, override dapat digunakan untuk memilih versi "
"spesifik dari repositori ceph yang digunakan oleh  OSA ceph_client ansible "
"role."

msgid ""
"Any tooling using the Designate v1 API needs to be reworked to use the v2 API"
msgstr ""
"Perkakas (tooling) apa pun yang menggunakan API Designate v1 perlu "
"dikerjakan ulang untuk menggunakan API v2"

msgid ""
"Any user that is coming from Pike or below on Ubuntu should modify its "
"``user_external_repos_list``, switching its ubuntu cloud archive repository "
"from ``state: present`` to ``state: absent``. From now on, UCA will be "
"defined with the filename ``uca``. If the deployer wants to use its mirror, "
"he can still override the variable ``uca_repo`` to point to its mirror. "
"Alternatively, the deployer can completely define which repos to add and "
"remove, ignoring our defaults, by overriding "
"``openstack_hosts_package_repos``."
msgstr ""
"Setiap pengguna yang berasal dari Pike atau di bawahnya di Ubuntu harus "
"memodifikasi ``user_external_repos_list`` -nya, mengalihkan repositori arsip "
"cloud ubuntu dari ``state: present`` ke ``state: absent``. Mulai sekarang, "
"UCA akan ditentukan dengan nama file ``uca``. Jika deployer ingin "
"menggunakan mirrornya, ia masih bisa mengganti variabel ``uca_repo`` untuk "
"menunjuk ke mirrornya. Sebagai alternatif, deployer dapat sepenuhnya "
"menentukan repo mana yang akan ditambahkan dan dihapus, mengabaikan standar "
"kami, dengan mengesampingkan ``openstack_hosts_package_repos``."

msgid ""
"Aodh has deprecated support for NoSQL storage (MongoDB and Cassandra) in "
"Mitaka with removal scheduled for the O* release. This causes warnings in "
"the logs. The default of using MongoDB storage for Aodh is replaced with the "
"use of Galera. Continued use of MongoDB will require the use of vars to "
"specify a correct ``aodh_connection_string`` and add pymongo to the "
"``aodh_pip_packages`` list."
msgstr ""
"Aodh telah mencabut dukungan untuk penyimpanan NoSQL (MongoDB dan Cassandra) "
"di Mitaka dengan penghapusan dijadwalkan untuk rilis O*. Ini menyebabkan "
"peringatan di log. Default menggunakan penyimpanan MongoDB untuk Aodh "
"diganti dengan penggunaan Galera. Terus menggunakan MongoDB akan membutuhkan "
"penggunaan vars untuk menentukan ``aodh_connection_string`` yang benar dan "
"menambahkan pymongo ke daftar ``aodh_pip_packages``."

msgid ""
"Apache MPM tunable support has been added to the os-keystone role in order "
"to allow MPM thread tuning. Default values reflect the current Ubuntu "
"default settings:"
msgstr ""
"Dukungan Apache MPM yang dapat diubah telah ditambahkan ke peran os-keystone "
"untuk memungkinkan penyetelan thread MPM. Nilai default mencerminkan "
"pengaturan default Ubuntu saat ini:"

msgid ""
"Application credentials are now enabled by default as a keystone "
"authentication method. If deployments do not wish to enable application "
"credentials then the existing keystone_auth_methods variable can be "
"overidden with the required set of authentication methods."
msgstr ""
"Kredensial aplikasi sekarang diaktifkan secara default sebagai metode "
"otentikasi keystone. Jika penyebaran tidak ingin mengaktifkan kredensial "
"aplikasi maka variabel keystone_auth_methods yang ada dapat ditimpa dengan "
"set metode otentikasi yang diperlukan."

msgid ""
"As described in the `Mitaka release notes <http://docs.openstack.org/"
"releasenotes/neutron/mitaka.html>`_ Neutron now correctly calculates for and "
"advertises the MTU to instances. As such the ``neutron_network_device_mtu`` "
"variable has been removed and the hard-coded values in the templates for "
"``advertise_mtu``, ``path_mtu``, and ``segment_mtu`` have been removed to "
"allow upstream defaults to operate as intended."
msgstr ""
"Seperti dijelaskan dalam `Mitaka release notes <http://docs.openstack.org/"
"releasenotes/neutron/mitaka.html>`_ Neutron sekarang menghitung dengan benar "
"dan mengiklankan MTU ke instance. Dengan demikian variabel "
"``neutron_network_device_mtu`` telah dihapus dan nilai-nilai hard-coded di "
"templat untuk ``advertise_mtu``, ``path_mtu``, dan ``segment_mtu`` telah "
"dihapus untuk memungkinkan default upstream untuk beroperasi sebagaimana "
"dimaksud."

msgid ""
"As described in the `Mitaka release notes <http://docs.openstack.org/"
"releasenotes/neutron/mitaka.html>`_ Neutron now correctly calculates for and "
"advertises the MTU to instances. The default DHCP configuration to advertise "
"an MTU to instances has therefore been removed from the variable "
"``neutron_dhcp_config``."
msgstr ""
"Seperti dijelaskan dalam `Mitaka release notes <http://docs.openstack.org/"
"releasenotes/neutron/mitaka.html>`_ Neutron sekarang menghitung dengan benar "
"dan mengiklankan MTU ke instance. Konfigurasi DHCP default untuk "
"mengiklankan MTU ke instance karenanya telah dihapus dari variabel "
"``neutron_dhcp_config``."

msgid ""
"Assigning multiple IP addresses to the same host name will now result in an "
"inventory error before running any playbooks."
msgstr ""
"Menetapkan beberapa alamat IP ke nama host yang sama sekarang akan "
"menghasilkan kesalahan inventory sebelum menjalankan playbook apa pun."

msgid ""
"Avoid setting the quotas too high for your cloud since this can impact the "
"performance of other servcies and lead to a potential Denial-of-Service "
"attack if Loadbalancer quotas are not set properly or RBAC is not properly "
"set up."
msgstr ""
"Hindari menetapkan kuota terlalu tinggi untuk cloud Anda karena hal ini "
"dapat berdampak pada kinerja servcies lain dan menyebabkan potensi serangan "
"Denial-of-Service jika kuota Loadbalancer tidak disetel dengan benar atau "
"RBAC tidak diatur dengan benar."

msgid ""
"Based on documentation from RabbitMQ [ https://www.rabbitmq.com/which-erlang."
"html ] this change ensures the version of erlang we're using across distros "
"is consistent and supported by RabbitMQ."
msgstr ""
"Berdasarkan dokumentasi dari RabbitMQ [https://www.rabbitmq.com/which-erlang."
"html] perubahan ini memastikan versi erlang yang kami gunakan di seluruh "
"distro konsisten dan didukung oleh RabbitMQ."

msgid "Bug Fixes"
msgstr "Perbaikan Bug"

msgid ""
"Capping the default value for the variable ``aodh_wsgi_processes`` to 16 "
"when the user doesn't configure this variable. Default value is twice the "
"number of vCPUs available on the machine with a capping value of 16."
msgstr ""
"Pembatasan nilai default untuk variabel ``aodh_wsgi_processes`` hingga 16 "
"saat pengguna tidak mengonfigurasi variabel ini. Nilai default adalah dua "
"kali jumlah vCPU yang tersedia di mesin dengan nilai pembatasan 16."

msgid ""
"Capping the default value for the variable ``cinder_osapi_volume_workers`` "
"to 16 when the user doesn't configure this variable. Default value is half "
"the number of vCPUs available on the machine with a capping value of 16."
msgstr ""
"Pembatasan nilai default untuk variabel ``cinder_osapi_volume_workers`` "
"hingga 16 saat pengguna tidak mengonfigurasi variabel ini. Nilai default "
"adalah setengah dari jumlah vCPU yang tersedia di mesin dengan nilai "
"pembatasan 16."

msgid ""
"Capping the default value for the variable ``galera_max_connections`` to "
"1600 when the user doesn't configure this variable. Default value is 100 "
"times the number of vCPUs available on the machine with a capping value of "
"1600."
msgstr ""
"Pembatasan nilai default untuk variabel ``galera_max_connections`` hingga "
"1600 ketika pengguna tidak mengonfigurasi variabel ini. Nilai default adalah "
"100 kali jumlah vCPU yang tersedia di mesin dengan nilai pembatasan 1600."

msgid ""
"Capping the default value for the variable ``galera_wsrep_slave_threads`` to "
"16 when the user doesn't configure this variable. Default value is the "
"number of vCPUs available on the machine with a capping value of 16."
msgstr ""
"Pembatasan nilai default untuk variabel ``galera_wsrep_slave_threads`` "
"hingga 16 saat pengguna tidak mengonfigurasi variabel ini. Nilai default "
"adalah jumlah vCPU yang tersedia di mesin dengan nilai pembatasan 16."

msgid ""
"Capping the default value for the variable ``gnocchi_wsgi_processes`` to 16 "
"when the user doesn't configure this variable. Default value is twice the "
"number of vCPUs available on the machine with a capping value of 16."
msgstr ""
"Pembatasan nilai default untuk variabel ``gnocchi_wsgi_processes`` hingga 16 "
"saat pengguna tidak mengonfigurasi variabel ini. Nilai default adalah dua "
"kali jumlah vCPU yang tersedia di mesin dengan nilai pembatasan 16."

msgid ""
"Capping the default value for the variable ``ironic_wsgi_processes`` to 16 "
"when the user doesn't configure this variable. Default value is one fourth "
"the number of vCPUs available on the machine with a capping value of 16."
msgstr ""
"Pembatasan nilai default untuk variabel ``ironic_wsgi_processes`` hingga 16 "
"saat pengguna tidak mengonfigurasi variabel ini. Nilai default adalah "
"seperempat jumlah vCPU yang tersedia di mesin dengan nilai pembatasan 16."

msgid ""
"Capping the default value for the variable ``keystone_wsgi_processes`` to 16 "
"when the user doesn't configure this variable. Default value is half the "
"number of vCPUs available on the machine with a capping value of 16."
msgstr ""
"Pembatasan nilai default untuk variabel ``keystone_wsgi_processes`` hingga "
"16 saat pengguna tidak mengonfigurasi variabel ini. Nilai default adalah "
"setengah dari jumlah vCPU yang tersedia di mesin dengan nilai pembatasan 16."

msgid ""
"Capping the default value for the variable ``repo_nginx_workers`` to 16 when "
"the user doesn't configure this variable. Default value is half the number "
"of vCPUs available on the machine with a capping value of 16."
msgstr ""
"Pembatasan nilai default untuk variabel ``repo_nginx_workers`` hingga 16 "
"saat pengguna tidak mengonfigurasi variabel ini. Nilai default adalah "
"setengah dari jumlah vCPU yang tersedia di mesin dengan nilai pembatasan 16."

msgid ""
"Capping the default value for the variable ``sahara_api_workers`` to 16 when "
"the user doesn't configure this variable. Default value is half the number "
"of vCPUs available on the machine with a capping value of 16."
msgstr ""
"Pembatasan nilai default untuk variabel ``sahara_api_workers`` hingga 16 "
"saat pengguna tidak mengonfigurasi variabel ini. Nilai default adalah "
"setengah dari jumlah vCPU yang tersedia di mesin dengan nilai pembatasan 16."

msgid ""
"Capping the default value for the variable ``swift_proxy_server_workers`` to "
"16 when the user doesn't configure this variable and if the swift proxy is "
"in a container. Default value is half the number of vCPUs available on the "
"machine if the swift proxy is not in a container. Default value is half the "
"number of vCPUs available on the machine with a capping value of 16 if the "
"proxy is in a container."
msgstr ""
"Pembatasan nilai default untuk variabel ``swift_proxy_server_workers`` "
"hingga 16 saat pengguna tidak mengonfigurasi variabel ini dan jika proxy "
"swift berada dalam container. Nilai default adalah setengah dari jumlah vCPU "
"yang tersedia pada mesin jika proksi cepat tidak dalam sebuah container. "
"Nilai default adalah setengah dari jumlah vCPU yang tersedia di mesin dengan "
"nilai pembatasan 16 jika proxy ada di dalam container."

msgid ""
"Capping the default value for the variables ``ceilometer_api_workers`` and "
"``ceilometer_notification_workers`` to 16 when the user doesn't configure "
"these variables. Default value is half the number of vCPUs available on the "
"machine with a capping value of 16."
msgstr ""
"Pembatasan nilai default untuk variabel ``ceilometer_api_workers`` dan "
"``ceilometer_notification_workers`` hingga 16 saat pengguna tidak "
"mengonfigurasi variabel ini. Nilai default adalah setengah dari jumlah vCPU "
"yang tersedia di mesin dengan nilai pembatasan 16."

msgid ""
"Capping the default value for the variables ``glance_api_workers`` and "
"``glance_registry_workers`` to 16 when the user doesn't configure these "
"variables. Default value is half the number of vCPUs available on the "
"machine with a capping value of 16."
msgstr ""
"Pembatasan nilai default untuk variabel ``glance_api_workers`` dan `` "
"glance_registry_workers`` hingga 16 ketika pengguna tidak mengkonfigurasi "
"variabel ini. Nilai default adalah setengah dari jumlah vCPU yang tersedia "
"di mesin dengan nilai pembatasan 16."

msgid ""
"Capping the default value for the variables ``heat_api_workers`` and "
"``heat_engine_workers`` to 16 when the user doesn't configure these "
"variables. Default value is half the number of vCPUs available on the "
"machine with a capping value of 16."
msgstr ""
"Pembatasan nilai default untuk variabel ``heat_api_workers`` dan "
"``heat_engine_workers`` hingga 16 ketika pengguna tidak mengkonfigurasi "
"variabel ini. Nilai default adalah setengah dari jumlah vCPU yang tersedia "
"di mesin dengan nilai pembatasan 16."

msgid ""
"Capping the default value for the variables ``horizon_wsgi_processes`` and "
"``horizon_wsgi_threads`` to 16 when the user doesn't configure these "
"variables. Default value is half the number of vCPUs available on the "
"machine with a capping value of 16."
msgstr ""
"Pembatasan nilai default untuk variabel ``horizon_wsgi_processes`` dan "
"``horizon_wsgi_threads`` hingga 16 saat pengguna tidak mengonfigurasi "
"variabel ini. Nilai default adalah setengah dari jumlah vCPU yang tersedia "
"di mesin dengan nilai pembatasan 16."

msgid ""
"Capping the default value for the variables ``neutron_api_workers``, "
"``neutron_num_sync_threads`` and ``neutron_metadata_workers`` to 16 when the "
"user doesn't configure these variables. Default value is half the number of "
"vCPUs available on the machine with a capping value of 16."
msgstr ""
"Pembatasan nilai default untuk variabel ``neutron_api_workers``, "
"``neutron_num_sync_threads`` dan ``neutron_metadata_workers`` ke 16 ketika "
"pengguna tidak mengkonfigurasi variabel ini. Nilai default adalah setengah "
"dari jumlah vCPU yang tersedia di mesin dengan nilai pembatasan 16."

msgid ""
"Capping the default value for the variables ``nova_wsgi_processes``, "
"``nova_osapi_compute_workers``, ``nova_metadata_workers`` and "
"``nova_conductor_workers`` to 16 when the user doesn't configure these "
"variables. Default value is half the number of vCPUs available on the "
"machine with a capping value of 16."
msgstr ""
"Pembatasan nilai default untuk variabel ``nova_wsgi_processes``, "
"``nova_osapi_compute_workers``, ``nova_metadata_workers`` dan "
"``nova_conductor_workers`` ke 16 saat pengguna tidak mengkonfigurasi "
"variabel ini. Nilai default adalah setengah dari jumlah vCPU yang tersedia "
"di mesin dengan nilai pembatasan 16."

msgid ""
"Ceilometer can now use Gnocchi for storage. By default this is disabled. To "
"enable the service, set ``ceilometer_gnocchi_enabled: yes``. See the Gnocchi "
"role documentation for more details."
msgstr ""
"Ceilometer sekarang dapat menggunakan Gnocchi untuk penyimpanan. Secara "
"default ini dinonaktifkan. Untuk mengaktifkan layanan, atur "
"``ceilometer_gnocchi_enabled: yes``. Lihat dokumentasi peran Gnocchi untuk "
"lebih jelasnya."

msgid ""
"Ceilometer does not support V3 endpoints in Liberty, which are the flavor "
"created by OSA. To deploy Ceilometer some endpoints in the Keystone service "
"catalog must be removed and replaced with V2 endpoints. This is neccessary, "
"for example, to use the Swift pollster to collect metrics for Swift storage "
"use the Swift endpoint. For detailed instructions on the steps for these "
"changes to the service catalog see the `OpenStack Liberty Install Guide "
"<http://docs.openstack.org/liberty>`."
msgstr ""
"Ceilometer tidak mendukung titik akhir V3 di Liberty, yang merupakan flavor "
"yang diciptakan oleh OSA. Untuk menggunakan Ceilometer, beberapa endpoint "
"dalam katalog layanan Keystone harus dihapus dan diganti dengan endpoint V2. "
"Ini diperlukan, misalnya, untuk menggunakan jajak pendapat Swift untuk "
"mengumpulkan metrik untuk penyimpanan Swift menggunakan endpoint Swift. "
"Untuk petunjuk terperinci tentang langkah-langkah untuk perubahan ini pada "
"katalog layanan, lihat `OpenStack Liberty Install Guide <http://docs."
"openstack.org/liberty>`."

msgid ""
"Ceilometer no longer manages alarm storage when Aodh is enabled. It now "
"redirects alarm-related requests to the Aodh API. This is now auto-enabled "
"when Aodh is deployed."
msgstr ""
"Ceilometer tidak lagi mengelola penyimpanan alarm ketika Aodh diaktifkan. "
"Sekarang pengalihan permintaan terkait alarm ke Aodh API. Ini sekarang "
"diaktifkan secara otomatis ketika Aodh digunakan."

msgid ""
"Ceilometer now uses the Keystone v3 endpoint. The 'identity_uri' directive "
"has been removed since it's unused. 'region_name' has been added. The "
"directives under 'service_credentials' have been updated to support the "
"keystoneauth library"
msgstr ""
"Ceilometer sekarang menggunakan endpoint Keystone v3. Arahan 'identity_uri' "
"telah dihapus karena tidak digunakan. 'region_name' telah ditambahkan. "
"Arahan di bawah 'service_credentials' telah diperbarui untuk mendukung "
"perpustakaan keystoneauth"

msgid ""
"CentOS 7 and Ubuntu 16.04 support have been added to the ``haproxy`` role."
msgstr ""
"Dukungan CentOS 7 dan Ubuntu 16.04 telah ditambahkan ke role ``haproxy``."

msgid "CentOS 7 support has been added to the ``galera_client`` role."
msgstr "Dukungan CentOS 7 telah ditambahkan ke role ``galera_client``."

msgid "CentOS 7 support has been added to the ``galera_server`` role."
msgstr "Dukungan CentOS 7 telah ditambahkan ke role ``galera_server``."

msgid ""
"CentOS deployments require a special COPR repository for modern LXC "
"packages. The COPR repository is not mirrored at this time and this causes "
"failed gate tests and production deployments."
msgstr ""
"Deployment CentOS memerlukan repositori COPR khusus untuk paket LXC modern. "
"Repositori COPR tidak dicerminkan pada saat ini dan ini menyebabkan tes gate "
"gagal dan deployment produksi."

msgid "CentOS7 support has been added to the ``rsyslog_client`` role."
msgstr "Dukungan CentOS 7 telah ditambahkan ke role ``rsyslog client``."

msgid "CentOS7/RHEL support has been added to the ceph_client role."
msgstr "Dukungan CentOS7/RHEL telah ditambahkan ke role ceph_client."

msgid "CentOS7/RHEL support has been added to the os_aodh role."
msgstr "Dukungan CentOS7/RHEL telah ditambahkan ke peran os_aodh."

msgid "CentOS7/RHEL support has been added to the os_ceilometer role."
msgstr "Dukungan CentOS7/RHEL telah ditambahkan ke role os_ceilometer."

msgid "CentOS7/RHEL support has been added to the os_cinder role."
msgstr "Dukungan CentOS7/RHEL telah ditambahkan ke role os_cinder."

msgid "CentOS7/RHEL support has been added to the os_designate role."
msgstr "Dukungan CentOS7/RHEL telah ditambahkan ke role os_designate."

msgid "CentOS7/RHEL support has been added to the os_glance role."
msgstr "Dukungan CentOS7/RHEL telah ditambahkan ke role os_glance."

msgid "CentOS7/RHEL support has been added to the os_gnocchi role."
msgstr "Dukungan CentOS7/RHEL telah ditambahkan ke role os_gnocchi."

msgid "CentOS7/RHEL support has been added to the os_heat role."
msgstr "Dukungan CentOS7/RHEL telah ditambahkan ke role os_heat."

msgid "CentOS7/RHEL support has been added to the os_horizon role."
msgstr "Dukungan CentOS7/RHEL telah ditambahkan ke role os_horizon."

msgid "CentOS7/RHEL support has been added to the os_keystone role."
msgstr "Dukungan CentOS7/RHEL telah ditambahkan ke role os_keystone."

msgid "CentOS7/RHEL support has been added to the os_neutron role."
msgstr "Dukungan CentOS7/RHEL telah ditambahkan ke peran os_neutron."

msgid "CentOS7/RHEL support has been added to the os_nova role."
msgstr "Dukungan CentOS7 / RHEL telah ditambahkan ke role os_nova."

msgid "CentOS7/RHEL support has been added to the os_swift role."
msgstr "Dukungan CentOS7 / RHEL telah ditambahkan ke role os_swift."

msgid ""
"Ceph storage backend is known not to work on openSUSE Leap 42.X yet. This is "
"due to missing openSUSE support in the upstream Ceph Ansible playbooks."
msgstr ""
"Backend penyimpanan Ceph diketahui belum bekerja pada openSUSE Leap 42.X. "
"Ini karena tidak adanya dukungan openSUSE di playbook Ceph Ansible hulu."

msgid ""
"Change the ``ansible-role-requirements.yml`` file to include the URL and git "
"SHA for your patched fork of the os_neutron role."
msgstr ""
"Ubah file ``ansible-role-requirement.yml`` untuk memasukkan URL dan git SHA "
"untuk fork patched Anda dari role os_neutron."

msgid ""
"Change the ``ansible-role-requirements.yml`` file to include the URL and git "
"SHA for your patched fork of the repo_build role."
msgstr ""
"Ubah file ``ansible-role-requirement.yml`` untuk memasukkan URL dan git SHA "
"untuk patched fork Anda dari role repo_build."

msgid ""
"Change the port for devices in the ring by adjusting the port value for "
"services, hosts, or devices. This will not involve a rebalance of the ring."
msgstr ""
"Ubah port untuk device di atas ring dengan menyesuaikan nilai port untuk "
"layanan, host, atau device. Ini tidak akan melibatkan rebalance the ring."

msgid ""
"Changed the default NTP server options in ``chrony.conf``. The ``offline`` "
"option has been removed, ``minpoll``/``maxpoll`` have been removed in favour "
"of the upstream defaults, while the ``iburst`` option was added to speed up "
"initial time synchronization."
msgstr ""
"Mengubah opsi server NTP default di ``chrony.conf``. Opsi ``offline`` telah "
"dihapus,``minpoll``/``maxpoll``  telah dihapus karena standar upstream, "
"sementara opsi ``iburst`` ditambahkan untuk mempercepat sinkronisasi waktu "
"awal."

msgid ""
"Changed the way we name host containers groups in dynamic_inventory.py for a "
"hostname from hostname_containers to hostname-host_containers to prevent "
"failing in the case where containers groups have the same name as host "
"containers when choosing hostnames inspired from containers group names. "
"This change fixes the following bugs https://bugs.launchpad.net/openstack-"
"ansible/+bug/1512883 and https://bugs.launchpad.net/openstack-ansible/"
"+bug/1528953."
msgstr ""
"Mengubah cara kami memberi nama grup container host di dynamic_inventory.py "
"untuk nama host dari hostname_containers menjadi hostname-host_containers "
"untuk mencegah kegagalan dalam kasus di mana grup kontainer memiliki nama "
"yang sama dengan container host ketika memilih nama host yang terinspirasi "
"dari nama grup kontainer. Perubahan ini memperbaiki bug berikut https://bugs."
"launchpad.net/openstack-ansible/+bug/1512883 dan  https://bugs.launchpad.net/"
"openstack-ansible/+bug/1528953."

msgid ""
"Changing the port for a device, or group of devices, carries a brief period "
"of downtime to the swift storage services for those devices. The devices "
"will be unavailable during period between when the storage service restarts "
"after the port update, and the ring updates to match the new port."
msgstr ""
"Mengubah port untuk device, atau grup device, membawa periode singkat "
"downtime ke layanan penyimpanan cepat untuk device tersebut. Device tidak "
"akan tersedia selama periode antara saat layanan penyimpanan restart setelah "
"update port, dan update ring untuk mencocokkan port baru."

msgid ""
"Changing to the ESL repos has no upgrade impact. The version of erlang "
"provided by ESL is newer than that what is found in the distro repos. "
"Furthermore, a pin has been added to ensure that APT always uses the ESL "
"repos as it's preferred source which has been done to simply ensure APT is "
"always pointed at ESL."
msgstr ""
"Mengubah ke repo ESL tidak memiliki dampak upgrade. Versi erlang yang "
"disediakan oleh ESL lebih baru daripada yang ditemukan di repro distro. "
"Selain itu, pin telah ditambahkan untuk memastikan bahwa APT selalu "
"menggunakan repo ESL sebagai sumber pilihan yang telah dilakukan untuk "
"memastikan bahwa APT selalu diarahkan ke ESL."

msgid ""
"Cherry-pick https://review.openstack.org/557757 into the fork on that branch."
msgstr "Cherry-pick https://review.openstack.org/557757 ke fork di branch itu."

msgid ""
"Chrony got a new configuration option to synchronize the system clock back "
"to the RTC using the ``security_ntp_sync_rtc`` variable. Disabled by default."
msgstr ""
"Chrony mendapat opsi konfigurasi baru untuk menyinkronkan jam sistem kembali "
"ke RTC menggunakan variabel ``security_ntp_sync_rtc``. Dinonaktifkan secara "
"default."

msgid ""
"Cinder is deployed with Active-Active enabled by default if you are using "
"Ceph as a backend storage."
msgstr ""
"Cinder dikerahkan dengan Active-Active diaktifkan secara default jika Anda "
"menggunakan Ceph sebagai penyimpanan backend."

msgid ""
"Cleanup tasks are added to remove the nova console git directories ``/usr/"
"share/novnc`` and ``/usr/share/spice-html5``, prior to cloning these inside "
"the nova vnc and spice console playbooks. This is necessary to guarantee "
"that local modifications do not break git clone operations, especially "
"during upgrades."
msgstr ""
"Tugas pembersihan ditambahkan untuk menghapus direktori  ``/usr/share/"
"novnc`` dan  ``/usr/share/spice-html5``, sebelum mengkloningnya di dalam "
"nova vnc dan spice console playbooks. Ini diperlukan untuk menjamin bahwa "
"modifikasi lokal tidak merusak operasi git clone, terutama selama upgrade."

msgid ""
"Code which added 'Acquire::http:No-Cache true' to the host and container apt "
"preferences when http proxy environment variables were set has been removed. "
"This setting is only required when working around issues introduced by badly "
"configured http proxies. In some cases proxies can improperly cache the apt "
"Releases and Packages files leading to package installation errors. If a "
"deployment is behind a badly configured proxy, the deployer can add the "
"necessary apt config fragment as part of host provisioning. OSA will "
"replicate that config into any containers that are created. This setting can "
"be removed from existing deployments if required by manually deleting the "
"file ``/etc/apt/apt.conf.d/00apt-no-cache`` from all host and containers."
msgstr ""
"Kode yang menambahkan 'Acquire::http:No-Cache true' ke host dan preferensi "
"apt container  ketika variabel lingkungan proxy http disetel telah dihapus. "
"Pengaturan ini hanya diperlukan saat mengatasi masalah yang diperkenalkan "
"oleh proxy http yang tidak dikonfigurasi dengan benar. Dalam beberapa kasus, "
"proxy dapat melakukan cache yang tidak tepat pada file Rilis dan Paket yang "
"mengarah ke kesalahan instalasi paket. Jika penyebaran berada di belakang "
"proxy yang dikonfigurasi dengan buruk, deployer dapat menambahkan fragmen "
"apt config yang diperlukan sebagai bagian dari penyediaan host. OSA akan "
"mereplikasi konfigurasi itu ke dalam container apa pun yang dibuat. "
"Pengaturan ini dapat dihapus dari deployment yang ada jika diperlukan dengan "
"menghapus file ``/etc/apt/apt.conf.d/00apt-no-cache``  secara manual dari "
"semua host dan container."

msgid ""
"Compare dict vars of before and after configuration to determine whether the "
"config keys or values have changed so a configuration file will not be "
"incorrectly marked as changed when only the ordering has changed."
msgstr ""
"Bandingkan vct dict sebelum dan sesudah konfigurasi untuk menentukan apakah "
"kunci atau nilai konfigurasi telah berubah sehingga file konfigurasi tidak "
"akan salah ditandai sebagai diubah ketika hanya pemesanan yang telah berubah."

msgid ""
"Configurations using the ``ceph-ansible`` role (that is, those applying the "
"``ceph-install.yml`` or ``ceph-rgw-install.yml`` playbooks) should be very "
"carefully reviewed if you are upgrading from prior ``stable/rocky`` "
"releases. Those releases shipped a pre-release version of ``ceph-ansible`` "
"that was unintentionally included in ``ansible-role-requirements.yml``."
msgstr ""
"Konfigurasi yang menggunakan peran ``ceph-ansible`` (yaitu, yang menerapkan "
"playbook ``ceph-install.yml`` atau ``ceph-rgw-install.yml``) harus ditinjau "
"dengan sangat hati-hati jika Anda memutakhirkan dari rilis  ``stable/rocky`` "
"sebelumnya. Rilis itu mengirimkan versi pra-rilis dari ``ceph-ansible`` yang "
"secara tidak sengaja termasuk dalam ``ansible-role-requirements.yml``."

msgid ""
"Container boot ordering has been implemented on container types where it "
"would be beneficial. This change ensures that stateful systems running "
"within a container are started ahead of non-stateful systems. While this "
"change has no impact on a running deployment it will assist with faster "
"recovery should any node hosting container go down or simply need to be "
"restarted."
msgstr ""
"Pemesanan boot kontainer telah diterapkan pada jenis kontainer di mana itu "
"akan bermanfaat. Perubahan ini memastikan bahwa sistem stateful yang "
"berjalan dalam suatu container dimulai di depan sistem non-stateful. "
"Meskipun perubahan ini tidak berdampak pada penyebaran yang berjalan, itu "
"akan membantu dengan pemulihan lebih cepat jika setiap container hosting "
"node turun atau hanya perlu di-restarted."

msgid ""
"Containers might fail to retrieve packages from the repo server when "
"connecting to a slave repo server that has not finished synchronizing. For "
"more information, see https://bugs.launchpad.net/openstack-ansible/"
"+bug/1543146. This is addressed by adding pre and post hooks into lsyncd to "
"connect to the slave repo servers and disable NGINX for the duration for the "
"sync."
msgstr ""
"Kontainer mungkin gagal untuk mengambil paket dari server repo saat "
"menghubungkan ke server repo slave yang belum selesai menyinkronkan. Untuk "
"informasi lebih lanjut, lihat https://bugs.launchpad.net/openstack-ansible/"
"+bug/1543146. Ini diatasi dengan menambahkan kait sebelum dan sesudah ke "
"lsyncd untuk menyambung ke server repo slave dan menonaktifkan NGINX selama "
"durasi sinkronisasi."

msgid ""
"Containers will now bind mount all logs to the physical host machine in the "
"\"/openstack/log/{{ inventory_hostname }}\" location. This change will "
"ensure containers using a block backed file system (lvm, zfs, bfrfs) do not "
"run into issues with full file systems due to logging."
msgstr ""
"Kontainer sekarang akan mengikat mount semua log ke mesin host fisik di "
"lokasi \"/openstack/log/{{ inventory_hostname }}\". Perubahan ini akan "
"memastikan kontainer menggunakan sistem file yang didukung blok (lvm, zfs, "
"bfrfs) tidak mengalami masalah dengan sistem file lengkap karena logging."

msgid ""
"Copy the logs from the container's filesystem to ``/openstack/log/"
"{{ inventory_hostname }}`` on the host filesystem"
msgstr ""
"Salin log dari sistem file wadah ke  ``/openstack/log/"
"{{ inventory_hostname }}``  pada sistem file host"

msgid ""
"Create a ``stable/newton`` branch in the fork based on the ``newton-eol`` "
"tag."
msgstr "Buat cabang  ``stable/newton`` di fork berdasarkan tag ``newton-eol``."

msgid "Critical Issues"
msgstr "Critical Issue (masalah kritis)"

msgid "Current Series Release Notes"
msgstr "Catatan Rilis Seri Saat Ini"

msgid ""
"Data structure for ``tempest_test_blacklist`` has been updated to add "
"launchpad and/or bugzilla linked with the test being skipped."
msgstr ""
"Struktur data untuk ``tempest_test_blacklist`` telah diperbarui untuk "
"menambahkan launchpad dan/atau bugzilla yang ditautkan dengan tes yang "
"dilewati."

msgid "Database migration tasks have been added for the FWaaS neutron plugin."
msgstr "Tugas migrasi database telah ditambahkan untuk plugin neutron FWaaS."

msgid "Database migration tasks have been added for the LBaaS neutron plugin."
msgstr "Tugas migrasi database telah ditambahkan untuk plugin neutron LBaaS."

msgid ""
"Database migration tasks have been added for the dynamic routing neutron "
"plugin."
msgstr ""
"Tugas migrasi database telah ditambahkan untuk plugin neutron routing "
"dinamis."

msgid ""
"Default quotas were bumped for the following resources: networks (from 10 to "
"100), subnets (from 10 to 100), ports (from 50 to 500) to match upstream "
"defaults."
msgstr ""
"Kuota default berbenturan dengan sumber daya berikut: jaringan (dari 10 "
"hingga 100), subnet (dari 10 hingga 100), port (dari 50 hingga 500) untuk "
"mencocokkan default hulu."

msgid ""
"Deleting variable entries from the ``global_overrides`` dictionary in "
"``openstack_user_config.yml`` now properly removes those variables from the "
"``openstack_inventory.json`` file. See Bug"
msgstr ""
"Menghapus entri variabel dari kamus ``global_overrides`` di "
"``openstack_user_config.yml`` sekarang dengan benar menghapus variabel-"
"variabel itu dari file ``openstack_inventory.json``. Lihat Bug"

msgid ""
"Depending on when the initial Kilo deployment was done it is possible the "
"repository servers have a pip.conf locking down the environment which limits "
"the packages available to to install. If this file is present it will cause "
"build failures as the repository server attempts to build Liberty packages."
msgstr ""
"Bergantung pada kapan deployment Kilo awal dilakukan, ada kemungkinan server "
"repositori memiliki pip.conf mengunci lingkungan yang membatasi paket yang "
"tersedia untuk diinstal. Jika file ini ada, itu akan menyebabkan kegagalan "
"build karena server repositori mencoba membangun paket Liberty."

msgid ""
"Deployers can `galera_disable_privatedevices` to `yes` to set "
"`PrivateDevices=false` in the systemd unit file for MariaDB on CentOS 7. The "
"default is `no`, which keeps the default systemd unit file settings from the "
"MariaDB package."
msgstr ""
"Deployer dapat `galera_disable_privatedevices` ke `yes` untuk mengatur "
"`PrivateDevices = false` dalam file systemd unit untuk MariaDB pada CentOS "
"7. Standarnya adalah `no`, yang menyimpan pengaturan file systemd unit "
"standar dari paket MariaDB."

msgid ""
"Deployers can `memcached_disable_privatedevices` to `yes` to set "
"`PrivateDevices=false` in the systemd unit file for MariaDB on CentOS 7. The "
"default is `no`, which keeps the default systemd unit file settings from the "
"MemcacheD package."
msgstr ""
"Deployer dapat `memcached_disable_privatedevices` ke `yes` untuk mengatur "
"`PrivateDevices = false` dalam file systemd unit untuk MariaDB pada CentOS "
"7. Standarnya adalah `no`, yang menyimpan pengaturan file systemd unit "
"standar dari paket MemcacheD."

msgid ""
"Deployers can also shut down and power on galera containers **one at a "
"time** manually if that method is preferred."
msgstr ""
"Penyebar juga dapat mematikan dan menyalakan container galera **one at a "
"time** secara manual jika metode itu lebih disukai."

msgid "Deployers can enable this configuration by setting an Ansible variable:"
msgstr ""
"Deployer dapat mengaktifkan konfigurasi ini dengan menetapkan variabel "
"Ansible:"

msgid ""
"Deployers can now blacklist certain Nova extensions by providing a list of "
"such extensions in ``horizon_nova_extensions_blacklist`` variable, for "
"example:"
msgstr ""
"Deployer sekarang dapat membuat blacklist ekstensi Nova tertentu dengan "
"memberikan daftar ekstensi tersebut dalam variabel "
"``horizon_nova_extensions_blacklist``, misalnya:"

msgid ""
"Deployers can now configure tempest public and private networks by setting "
"the following variables, 'tempest_private_net_provider_type' to either vxlan "
"or vlan and 'tempest_public_net_provider_type' to flat or vlan. Depending on "
"what the deployer sets these variables to, they may also need to update "
"other variables accordingly, this mainly involves "
"'tempest_public_net_physical_type' and 'tempest_public_net_seg_id'. Please "
"refer to http://docs.openstack.org/mitaka/networking-guide/intro-basic-"
"networking.html for more neutron networking information."
msgstr ""
"Deployer sekarang dapat mengkonfigurasi tempest jaringan publik dan pribadi "
"dengan mengatur variabel berikut, 'tempest_private_net_provider_type' ke "
"vxlan atau vlan dan 'tempest_public_net_provider_type' ke flat atau vlan. "
"Bergantung pada apa yang digunakan setel variabel ini, mereka mungkin juga "
"perlu memperbarui variabel lain yang sesuai, ini terutama melibatkan "
"'tempest_public_net_physical_type' dan 'tempest_public_net_seg_id'. Silakan "
"merujuk ke http://docs.openstack.org/mitaka/networking-guide/intro-basic-"
"networking.html untuk informasi jaringan neutron lainnya."

msgid ""
"Deployers can now define a cinder-backend volume type explicitly private or "
"public with option ``public`` set to true or false."
msgstr ""
"Deployer sekarang dapat menentukan jenis volume cinder-backend secara "
"eksplisit privat atau publik dengan opsi ``publik`` disetel ke true atau "
"false."

msgid ""
"Deployers can now define the override "
"``cinder_rpc_executor_thread_pool_size`` which defaults to 64"
msgstr ""
"Deployer sekarang dapat mendefinisikan override "
"``cinder_rpc_executor_thread_pool_size`` yang secara default adalah 64"

msgid ""
"Deployers can now define the override ``cinder_rpc_response_timeout`` which "
"defaults to 60"
msgstr ""
"Deployer sekarang dapat menentukan override ``cinder_rpc_response_timeout`` "
"yang secara default menjadi 60"

msgid ""
"Deployers can now define the varible ``cinder_qos_specs`` to create qos "
"specs and assign those specs to desired cinder volume types."
msgstr ""
"Deployer sekarang dapat mendefinisikan variabel ``cinder_qos_specs`` untuk "
"membuat spesifikasi qos dan menetapkan spesifikasi tersebut ke tipe volume "
"cinder yang diinginkan."

msgid ""
"Deployers can now set the ``container_tech`` to **nspawn** when deploying "
"OSA within containers. When making the decision to deploy container types "
"the deployer only needs to define the desired ``container_tech`` and "
"continue the deployment as normal."
msgstr ""
"Deployer sekarang dapat mengatur ``container_tech`` ke **nspawn** saat "
"menggunakan OSA di dalam kontainer. Saat membuat keputusan untuk menggunakan "
"tipe kontainer, deployer hanya perlu mendefinisikan ``container_tech`` yang "
"diinginkan dan melanjutkan deployment  seperti biasa."

msgid ""
"Deployers can now set the ``install_method`` to either ``source`` (default) "
"or ``distro`` to choose the method for installing OpenStack services on the "
"hosts. This only applies to *new* deployments.  Existing deployments which "
"are source based, cannot be converted to the new ``distro`` method. For more "
"information, please refer to the `Deployment Guide <https://docs.openstack."
"org/project-deploy-guide/openstack-ansible>`_."
msgstr ""
"Deployer sekarang dapat mengatur ``install_method`` menjadi ``source`` "
"(default) atau ``distro`` untuk memilih metode untuk menginstal layanan "
"OpenStack pada host. Ini hanya berlaku untuk deployment *new*  Deployment "
"yang ada yang berbasis sumber, tidak dapat dikonversi ke metode ``distro`` "
"yang baru. Untuk informasi lebih lanjut, silakan merujuk ke `Deployment "
"Guide <https://docs.openstack.org/project-deploy-guide/openstack-ansible>`_."

msgid ""
"Deployers can now specify a custom package name or URL for an EPEL release "
"package. CentOS systems use ``epel-release`` by default, but some deployers "
"have a customized package that redirects servers to internal mirrors."
msgstr ""
"Deployer sekarang dapat menentukan nama paket kustom atau URL untuk paket "
"rilis EPEL. Sistem CentOS menggunakan ``epel-release`` secara default, "
"tetapi beberapa deployer memiliki paket khusus yang mengarahkan ulang "
"(redirect) server ke mirror internal."

msgid ""
"Deployers can opt out of this change by setting "
"``openstack_host_keep_journals`` to ``no``."
msgstr ""
"Deployer dapat menyisih dari perubahan ini dengan mengatur "
"``openstack_host_keep_journals`` ke ``no``."

msgid "Deployers can opt-out of the change entirely by setting a variable:"
msgstr ""
"Deployer dapat menyisih dari perubahan sepenuhnya dengan menetapkan variabel:"

msgid ""
"Deployers can opt-out of this change by setting "
"``security_disable_netconsole`` to ``no``."
msgstr ""
"Deployer dapat menyisih dari perubahan ini dengan mengatur "
"``security_disable_netconsole`` ke ``no``."

msgid ""
"Deployers can opt-out of this change by setting ``security_disable_rdisc`` "
"to ``no``."
msgstr ""
"Deployer dapat menyisih dari perubahan ini dengan mengatur "
"``security_disable_rdisc`` ke ``no``."

msgid ""
"Deployers can optionally remove the Keystone v2 endpoints from the "
"database.  Those endpoints will not be removed by the upgrade process."
msgstr ""
"Deployer secara opsional dapat menghapus endpoint Keystone v2 dari "
"database.  Endpoint tersebut tidak akan dihapus oleh proses upgrade."

msgid ""
"Deployers can optionally set a UID and/or GID for the nova user and group. "
"This is helpful for environments with shared storage."
msgstr ""
"Deployer secara opsional dapat mengatur UID dan/atau GID untuk pengguna dan "
"grup nova. Ini bermanfaat untuk lingkungan dengan penyimpanan bersama."

msgid ""
"Deployers can provide a customized login banner via a new Ansible variable: "
"``security_login_banner_text``. This banner text is used for non-graphical "
"logins, which includes console and ssh logins."
msgstr ""
"Deployer dapat memberikan banner login khusus melalui variabel Ansible baru: "
"``security_login_banner_text``. Teks banner ini digunakan untuk non-"
"graphical login, yang mencakup login ssh dan konsol."

msgid ""
"Deployers can set ``heat_cinder_backups_enabled`` to enable or disable the "
"cinder backups feature in heat. If heat has cinder backups enabled, but "
"cinder's backup service is disabled, newly built stacks will be undeletable."
msgstr ""
"Deployer dapat mengatur ``heat_cinder_backups_enabled`` untuk mengaktifkan "
"atau menonaktifkan fitur cinder backup di heat. Jika heat memiliki cinder "
"backup diaktifkan, tetapi layanan cinder backup dinonaktifkan, stack yang "
"baru dibangun akan tidak terhapus."

msgid ""
"Deployers can set ``lxc_hosts_opensuse_mirror_url`` to use their preferred "
"mirror for the openSUSE repositories. They can also set the "
"``lxc_hosts_opensuse_mirror_obs_url`` if they want to set a different mirror "
"for the OBS repositories. If they want to use the same mirror in both cases "
"then they can leave the latter variable to its default value. The full list "
"of mirrors and their capabilities can be obtained at http://mirrors.opensuse."
"org/"
msgstr ""
"Deployer dapat mengatur ``lxc_hosts_opensuse_mirror_url`` untuk menggunakan "
"mirror pilihan mereka untuk repositori openSUSE. Mereka juga dapat mengatur "
"``lxc_hosts_opensuse_mirror_obs_url`` jika mereka ingin mengatur mirror lain "
"untuk repositori OBS. Jika mereka ingin menggunakan mirror yang sama dalam "
"kedua kasus maka mereka dapat membiarkan variabel yang terakhir ke nilai "
"default. Daftar lengkap cermin dan kemampuannya dapat diperoleh di http://"
"mirrors.opensuse.org/"

msgid ""
"Deployers can set ``openstack_host_nf_conntrack_max`` to control the maximum "
"size of the netfilter connection tracking table. The default of ``262144`` "
"should be increased if virtual machines will be handling large amounts of "
"concurrent connections."
msgstr ""
"Deployer dapat mengatur ``openstack_host_nf_conntrack_max`` untuk mengontrol "
"ukuran maksimum tabel pelacakan koneksi netfilter. Default ``262144`` harus "
"ditingkatkan jika mesin virtual akan menangani sejumlah besar koneksi "
"konkuren."

msgid ""
"Deployers can set ``pip_install_centos_mirror_url`` to use their preferred "
"mirror for the RDO repositories."
msgstr ""
"Deployer dapat mengatur ``pip_install_centos_mirror_url`` untuk menggunakan "
"mirror pilihan mereka untuk repositori RDO."

msgid ""
"Deployers can set ``pip_install_opensuse_mirror_url`` to use their preferred "
"mirror for the openSUSE repositories. They can also set the "
"``pip_install_opensuse_mirror_obs_url`` if they want to set a different "
"mirror for the OBS repositories. If they want to use the same mirror in both "
"cases then they can leave the latter variable to its default value. The full "
"list of mirrors and their capabilities can be obtained at http://mirrors."
"opensuse.org/"
msgstr ""
"Deployer dapat mengatur ``pip_install_opensuse_mirror_url`` untuk "
"menggunakan mirror pilihan mereka untuk repositori openSUSE. Mereka juga "
"dapat mengatur ``pip_install_opensuse_mirror_obs_url`` jika mereka ingin "
"mengatur mirror lain untuk repositori OBS. Jika mereka ingin menggunakan "
"mirror yang sama dalam kedua kasus maka mereka dapat membiarkan variabel "
"yang terakhir ke nilai default. Daftar lengkap cermin dan kemampuannya dapat "
"diperoleh di http://mirrors.opensuse.org/"

msgid ""
"Deployers can set a default availability zone (AZ) for new instance builds "
"which do not provide an AZ. The value is ``None`` by default, but it can be "
"changed with the ``nova_default_schedule_zone`` Ansible variable."
msgstr ""
"Deployer dapat mengatur zona ketersediaan default (AZ) untuk bangunan "
"instance baru yang tidak menyediakan AZ. Nilai secara default adalah "
"``None``, tetapi dapat diubah dengan variabel ``nova_default_schedule_zone``."

msgid ""
"Deployers can set a refresh interval for haproxy's stats page by setting the "
"``haproxy_stats_refresh_interval`` variable. The default value is ``60``, "
"which causes haproxy to refresh the stats page every 60 seconds."
msgstr ""
"Deployer dapat mengatur interval penyegaran untuk halaman statistik haproxy "
"dengan mengatur variabel ``haproxy_stats_refresh_interval``. Nilai "
"defaultnya adalah ``60``, yang menyebabkan haproxy me-refresh halaman "
"statistik setiap 60 detik."

msgid ""
"Deployers can specify the authentication credentials to be used with wsrep "
"by configuring ``galera_wsrep_sst_auth_user`` and "
"``galera_wsrep_sst_auth_password``."
msgstr ""
"Deployer dapat menentukan kredensial otentikasi untuk digunakan dengan wsrep "
"dengan mengkonfigurasi ``galera_wsrep_sst_auth_user`` dan "
"``galera_wsrep_sst_auth_password``."

msgid ""
"Deployers can still set a specific keymap using a nova configuration "
"override if necessary."
msgstr ""
"Deployer masih dapat mengatur keymap spesifik menggunakan konfigurasi nova "
"override jika perlu."

msgid ""
"Deployers can use the rolling restart functionality provided in the upgrade "
"playbook within the main `OpenStack-Ansible repository <https://github.com/"
"openstack/openstack-ansible/blob/stable/mitaka/scripts/upgrade-utilities/"
"playbooks/galera-cluster-rolling-restart.yml>`_."
msgstr ""
"Deployer dapat menggunakan fungsionalitas rolling restart yang disediakan "
"dalam playbook upgrade dalam file main `OpenStack-Ansible repository "
"<https://github.com/openstack/openstack-ansible/blob/stable/mitaka/scripts/"
"upgrade-utilities/playbooks/galera-cluster-rolling-restart.yml>`_."

msgid ""
"Deployers how have the option to set the the wsrep method via the "
"``galera_wsrep_sst_method``."
msgstr ""
"Deployer memiliki opsi cara untuk mengatur metode wsrep melalui "
"``galera_wsrep_sst_method``."

msgid ""
"Deployers may opt-in for the change without automatically updating the "
"active ``grub.cfg`` file by setting the following Ansible variables:"
msgstr ""
"Deployer dapat memilih ikut serta dalam perubahan tanpa secara otomatis "
"updating file ``grub.cfg`` yang aktif dengan mengatur variabel Ansible "
"berikut ini:"

msgid ""
"Deployers may provide a list of custom haproxy template files to copy from "
"the deployment host through the ``octavia_user_haproxy_templates`` variable "
"and configure Octavia to make use of a custom haproxy template file with "
"with ``octavia_haproxy_amphora_template`` variable."
msgstr ""
"Deployer dapat memberikan daftar file templat haproxy khusus untuk disalin "
"dari host penyebaran melalui variabel ``octavia_user_haproxy_templates`` dan "
"mengkonfigurasi Octavia untuk menggunakan file template haproxy khusus "
"dengan variabel ``octavia_haproxy_amphora_template``."

msgid ""
"Deployers may require custom CA certificates installing on their openstack "
"hosts or service containers. A new variable openstack_host_ca_certificates "
"is added which is a list of certificates that should be copied from the "
"deploy host to the target hosts. Certificates may be selectively deployed by "
"defining the variable either in user_variables.yml or via host/group vars."
msgstr ""
"Deployers mungkin memerlukan sertifikat CA khusus yang dipasang di host "
"openstack atau containers layanan mereka. Variabel "
"openstack_host_ca_certificates baru ditambahkan yang merupakan daftar "
"sertifikat yang harus disalin dari deploy host ke host target. Sertifikat "
"dapat digunakan secara selektif dengan mendefinisikan variabel baik di "
"user_variables.yml atau melalui host/group vars."

msgid ""
"Deployers now have the option to prevent the EPEL repository from being "
"installed by the role. Setting ``security_epel_install_repository`` to "
"``no`` prevents EPEL from being installed. This setting may prevent certain "
"packages from installing, such as ClamAV."
msgstr ""
"Deployer sekarang memiliki opsi untuk mencegah repositori EPEL diinstal oleh "
"peran tersebut. Mengatur ``security_epel_install_repository`` ke ``no`` "
"mencegah EPEL diinstal. Pengaturan ini dapat mencegah pemasangan paket "
"tertentu, seperti ClamAV."

msgid ""
"Deployers of CentOS 7 environments can use the "
"``openstack_hosts_enable_yum_fastestmirror`` variable to enable or disable "
"yum's fastestmirror plugin. The default setting of ``yes`` ensures that "
"fastestmirror is enabled."
msgstr ""
"Deployer lingkungan CentOS 7 dapat menggunakan variabel "
"``openstack_hosts_enable_yum_fastestmirror`` untuk mengaktifkan atau "
"menonaktifkan plugin fastestmirror yum. Pengaturan default ``yes`` "
"memastikan bahwa fastestmirror diaktifkan."

msgid ""
"Deployers should review the defaults provided in ``playbooks/os_keystone/"
"defaults/main.yml`` and adjust any variables in ``user_variables.yml`` if "
"they exist there."
msgstr ""
"Deployer harus meninjau default yang disediakan di ``playbooks/os_keystone/"
"defaults/main.yml`` dan menyesuaikan variabel apa pun di ``user_variables."
"yml`` jika ada di sana."

msgid ""
"Deployers should review the new RHEL 7 STIG variables in ``defaults/main."
"yml`` to provide custom configuration for the Ansible tasks."
msgstr ""
"Deployer harus meninjau variabel RHEL 7 STIG baru di ``defaults/main.yml`` "
"untuk memberikan konfigurasi khusus untuk tugas Ansible."

msgid ""
"Deployers that need a graphical interface will need to set the following "
"Ansible variable:"
msgstr ""
"Deployer yang membutuhkan antarmuka grafis perlu mengatur variabel Ansible "
"berikut:"

msgid ""
"Deployers that need this logging enabled will need to set the following "
"Ansible variable:"
msgstr ""
"Deployer yang membutuhkan  logging ini diaktifkan perlu mengatur variabel "
"Ansible berikut:"

msgid ""
"Deployments on ppc64le are limited to Ubuntu 16.04 for the Newton release of "
"OpenStack-Ansible."
msgstr ""
"Penerapan pada ppc64le terbatas pada Ubuntu 16.04 untuk rilis Newton dari "
"OpenStack-Ansible."

msgid ""
"Deployments will now default to using python3 when a python3 interpreter is "
"present in the operating system. Each openstack-ansible role has a new "
"variable for the form <role>_venv_python_executable which defaults to "
"python2 but a global variable openstack_venv_python_executable in the "
"openstack-ansible group variables sets this to python3 on supporting "
"operating systems. This enables a deployer is to selectively use python2 or "
"python3 on a per service basis if required. The ansible-runtime venv is also "
"created using python3 on the deploy host if possible."
msgstr ""
"Penyebaran sekarang akan default untuk menggunakan python3 ketika python3 "
"interpreter hadir dalam sistem operasi. Setiap peran yang dimungkinkan "
"openstack memiliki variabel baru untuk bentuk <role>_venv_python_executable "
"yang default ke python2 tetapi variabel global "
"openstack_venv_python_executable dalam variabel-variabel kelompok openstack-"
"ansible mengatur ini ke python3 pada sistem operasi pendukung. Hal ini "
"memungkinkan penggelar untuk secara selektif menggunakan python2 atau "
"python3 berdasarkan layanan jika diperlukan. The ansible-runtime venv juga "
"dibuat menggunakan python3 pada host deploy jika memungkinkan."

msgid "Deprecation Notes"
msgstr "Catatan Depresiasi"

msgid ""
"Developers can specify additional python packages for the repo build process "
"by creating YAML files within ``/etc/openstack_deploy/``. Refer to the "
"`documentation on adding packages <http://docs.openstack.org/developer/"
"openstack-ansible/developer-docs/extending.html#build-the-environment-with-"
"additional-python-packages>`_ for more details."
msgstr ""
"Pengembang dapat menentukan paket python tambahan untuk proses repo build "
"dengan membuat file YAML di dalam ``/etc/openstack_deploy/``.  Lihat "
"`documentation on adding packages <http://docs.openstack.org/developer/"
"openstack-ansible/developer-docs/extending.html#build-the-environment-with-"
"additional-python-packages>` _ untuk  keterangan lebih lanjut."

msgid ""
"Disable HTTPS entirely by setting ``haproxy_ssl: no`` (which will also "
"disable https on haproxy. This setting is inherited by the new "
"``horizon_enable_ssl`` variable by default. This is a new option."
msgstr ""
"Nonaktifkan HTTPS seluruhnya dengan mengatur ``haproxy_ssl: no`` (yang juga "
"akan menonaktifkan https di haproxy. Pengaturan ini diwarisi (inherited) "
"oleh variabel ``horizon_enable_ssl`` yang baru secara default. Ini adalah "
"opsi baru."

msgid ""
"Download and install the neutron-fwaas-dashboard if being enabled within the "
"os_horizon role by the ``horizon_enable_neutron_fwaas`` var."
msgstr ""
"Unduh dan pasang dasbor neutron-fwaas jika diaktifkan di dalam peran "
"os_horizon oleh var `` horizon_enable_neutron_fwaas``."

msgid ""
"Downloading and unarchiving a .tar.gz has been removed.  The related tempest "
"options ``ami_img_file``, ``aki_img_file``, and ``ari_img_file`` have been "
"removed from tempest.conf.j2."
msgstr ""
"Mengunduh dan membatalkan pengarsipan .tar.gz telah dihapus. Opsi tempest "
"terkait ``ami_img_file``, ``aki_img_file``, dan ``ari_img_file`` telah "
"dihapus dari tempest.conf.j2."

msgid ""
"Dragonflow is no longer maintained as an OpenStack project and has therefore "
"been removed from OpenStack-Ansible as a supported ML2 driver for neutron."
msgstr ""
"Dragonflow tidak lagi dipertahankan sebagai proyek OpenStack dan karenanya "
"telah dihapus dari OpenStack-Ansible sebagai driver ML2 yang didukung untuk "
"neutron."

msgid ""
"Due to a change in how backend_host is defined when using Ceph, all the "
"Cinder volumes will restart under the same backend name.  This will mean "
"that any volumes which previously were assigned to the host or container "
"that hosted the volume will no longer be managable.  The workaround for this "
"is to use the `cinder-manage volume update_host` command to move those "
"volumes to the new backend host.  This known issue will be resolved soon "
"with an upgrade playbook."
msgstr ""
"Karena perubahan dalam cara backend_host didefinisikan saat menggunakan "
"Ceph, semua volume Cinder akan memulai kembali dengan nama backend yang "
"sama. Ini berarti bahwa volume apa pun yang sebelumnya ditugaskan ke host "
"atau container yang menampung volume tidak lagi dapat dikelola. Solusi untuk "
"ini adalah dengan menggunakan perintah `cinder-manage volume update_host`  "
"untuk memindahkan volume tersebut ke host backend baru. Masalah yang "
"diketahui ini akan segera teratasi dengan playbook pemutakhiran."

msgid ""
"Due to a change in how backend_host is defined when using Ceph, all the "
"Cinder volumes will restart under the same backend name.  This will mean "
"that any volumes which previously were assigned to the host or container "
"that hosted the volume will no longer be manageable.  The workaround for "
"this is to use the `cinder-manage volume update_host` command to move those "
"volumes to the new backend host.  This known issue will be resolved soon "
"with an upgrade playbook."
msgstr ""
"Karena perubahan dalam cara backend_host didefinisikan saat menggunakan "
"Ceph, semua volume Cinder akan memulai kembali dengan nama backend yang "
"sama. Ini berarti bahwa volume apa pun yang sebelumnya ditugaskan ke host "
"atau kontainer yang menampung volume tidak lagi dapat dikelola. Solusi untuk "
"ini adalah dengan menggunakan perintah `cinder-manage volume update_host` "
"untuk memindahkan volume tersebut ke host backend baru. Masalah yang "
"diketahui ini akan segera teratasi dengan playbook pemutakhiran."

msgid ""
"Due to a new bind mount at \"/var/log\" all containers will be restarted. "
"This is a required restart. It is recommended that deployers run the "
"container restarts in serial to not impact production workloads."
msgstr ""
"Karena bind mount baru di \"/var/log\" semua kontainer akan di-restart. Ini "
"adalah restart yang diperlukan. Direkomendasikan agar para penyalur "
"menjalankan kontainer restart secara serial untuk tidak memengaruhi beban "
"kerja produksi."

msgid ""
"Due to the smart-reources implementation, variables, related to custom git "
"path of exact config files were removed. Now all config files are taken from "
"upstream git repo, but overrides and client configs are still supported. The "
"following variables are not supported now: * "
"ceilometer_git_config_lookup_location * ceilometer_data_meters_git_file_path "
"* ceilometer_event_definitions_git_file_path * "
"ceilometer_gnocchi_resources_git_file_path * "
"ceilometer_loadbalancer_v2_meter_definitions_git_file_path * "
"ceilometer_osprofiler_event_definitions_git_file_path * "
"ceilometer_polling_git_file_path If you are maintaining custom ceilometer "
"git repository, you still may use ``ceilometer_git_repo`` variable, to "
"provide url to your git repository."
msgstr ""
"Karena implementasi smart-reource, variabel, yang terkait dengan jalur git "
"kustom dari file konfigurasi yang tepat telah dihapus. Sekarang semua file "
"config diambil dari repo git hulu, tetapi penggantian dan konfigurasi klien "
"masih didukung. Variabel berikut tidak didukung sekarang: * "
"ceilometer_git_config_lookup_location * ceilometer_data_meters_git_file_path "
"* ceilometer_event_definitions_git_file_path * "
"ceilometer_gnocchi_resources_git_file_path * "
"ceilometer_loadbalancer_v2_meter_definitions_git_file_path * "
"ceilometer_osprofiler_event_definitions_git_file_path * "
"ceilometer_polling_git_file_path Jika Anda memelihara kebiasaan ceilometer "
"git repositori, Anda masih dapat menggunakan variabel  "
"``ceilometer_git_repo``, untuk memberikan url ke repositori git Anda."

msgid ""
"Due to usage of systemd-journald mapping of /openstack/log/ to /var/log/"
"$SERVICE is not present anymore. Also rsyslog_client role is not called for "
"projects since logs are stored in journald. Also variables like "
"service_log_dir are not supported anymore and have no effect."
msgstr ""
"Karena penggunaan pemetaan systemd-journald dari /openstack/log/ to /var/log/"
"$SERVICE tidak ada lagi. Peran rsyslog_client juga tidak dipanggil untuk "
"proyek karena log disimpan di journald. Juga variabel seperti "
"service_log_dir tidak didukung lagi dan tidak berpengaruh."

msgid ""
"During a kilo to liberty upgrade, container and service restarts for the "
"mariadb/galera cluster were being triggered multiple times and causing the "
"cluster to become unstable and often unrecoverable. This situation has been "
"improved immensely, and we now have tight control such that restarts of the "
"galera containers only need to happen once, and are done so in a controlled, "
"predictable and repeatable way."
msgstr ""
"Selama dari kilo ke upgrade liberty, kontainer dan restart layanan untuk "
"cluster mariadb/galera sedang dipicu beberapa kali dan menyebabkan cluster "
"menjadi tidak stabil dan sering tidak dapat dipulihkan. Situasi ini telah "
"sangat ditingkatkan, dan kami sekarang memiliki kontrol ketat sehingga me-"
"restart kontainer galera hanya perlu terjadi sekali, dan dilakukan dengan "
"cara yang terkendali, dapat diprediksi, dan dapat diulang (repeatable way)."

msgid ""
"During an upgrade using the run-upgrade script, the neutron agents will now "
"automatically be migrated from the neutron_agents containers on to the "
"network_hosts. The neutron_agents containers will be deleted as they are no "
"longer necessary. Any environments which previously upgraded to Queens can "
"make use of the same playbooks to handle to migration, or inspect the "
"playbooks to determine how to do it by hand if preferred."
msgstr ""
"Selama upgrade menggunakan skrip run-upgrade, agen neutron sekarang akan "
"secara otomatis dimigrasikan dari kontainer neutron_agents ke network_hosts. "
"Kontainer neutron_agents akan dihapus karena tidak perlu lagi. Setiap "
"lingkungan yang sebelumnya upgraded ke Queens dapat menggunakan playbook "
"yang sama untuk menangani migrasi, atau memeriksa playbook untuk menentukan "
"bagaimana melakukannya dengan tangan jika diinginkan."

msgid ""
"During the keepalived role upgrade the keepalived process will restart and "
"introduce a brief service disruption."
msgstr ""
"Selama upgrade role keepalived, proses keepalived akan restart dan "
"memperkenalkan gangguan layanan singkat."

msgid ""
"During the upgrade from Kilo to Liberty, this change deletes the repo "
"containers and recreates them to fix an upgrade issue with dependencies."
msgstr ""
"Selama upgrade dari Kilo ke Liberty, perubahan ini menghapus kontainer repo "
"dan membuatnya kembali untuk memperbaiki masalah upgrade dengan dependensi."

msgid ""
"During the upgrade process new secrets, such as passwords and keys, will be "
"generated and added to ``/etc/openstack_deploy/user_secrets.yml``. Existing "
"values will not be changed."
msgstr ""
"Selama proses upgrade, rahasia baru, seperti kata sandi dan kunci, akan "
"dihasilkan dan ditambahkan ke ``/etc/openstack_deploy/user_secrets.yml``. "
"Nilai yang ada tidak akan diubah."

msgid ""
"During upgrade process role will drop `gnocchi_service_port` from apache "
"listeners (ports.conf) and gnocchi virtualhost, which by default means "
"misconfigured apache service (since it won't have any listeners) unless it's "
"aio build and this apache server is in use by other role/service. Apache "
"server won't be dropped from gnocchi_api hosts, so deployers are encoureged "
"to remove it manually."
msgstr ""
"Selama proses pemutakhiran, role akan melepaskan `gnocchi_service_port` dari "
"apache listeners (ports.conf) dan gnocchi virtualhost, yang secara default "
"berarti apache service  yang tidak terkonfigurasi (karena tidak akan "
"memiliki listeners) kecuali itu membangun dan server apache ini digunakan "
"oleh role/service lain. Server Apache tidak akan di-drop dari host "
"gnocchi_api, jadi deployer disarankan untuk menghapusnya secara manual."

msgid ""
"During upgrade process role will drop `panko_service_port` from apache "
"listeners (ports.conf) and panko virtualhost, which by default means "
"misconfigured apache service (since it won't have any listeners) unless it's "
"aio build and this apache server is in use by other role/service. Apache "
"server won't be dropped from panko_api hosts, so deployers are encoureged to "
"remove it manually."
msgstr ""
"Selama proses pemutakhiran, role akan menurunkan `panko_service_port` dari "
"apache listeners (ports.conf) dan panko virtualhost, yang secara default "
"berarti apache service yang tidak terkonfigurasi (karena tidak akan memiliki "
"listeners) kecuali itu aio build dan server apache ini digunakan oleh role/"
"service lain. Server Apache tidak akan di-drop dari host panko_api, jadi "
"deployer disarankan untuk menghapusnya secara manual."

msgid ""
"During upgrades, container and service restarts for the mariadb/galera "
"cluster were being triggered multiple times and causing the cluster to "
"become unstable and often unrecoverable. This situation has been improved "
"immensely, and we now have tight control such that restarts of the galera "
"containers only need to happen once, and are done so in a controlled, "
"predictable and repeatable way."
msgstr ""
"Selama upgrade, kontainer dan restart layanan untuk klaster mariadb/galera "
"dipicu beberapa kali dan menyebabkan kluster menjadi tidak stabil dan sering "
"tidak dapat dipulihkan. Situasi ini telah sangat ditingkatkan, dan kami "
"sekarang memiliki kontrol ketat sehingga me-restart kontainer galera hanya "
"perlu terjadi sekali, dan dilakukan dengan cara yang terkendali, dapat "
"diprediksi, dan dapat diulang ((repeatable way)."

msgid ""
"Each openstack service role has a new variable <role>_bind_address which "
"defaults to 0.0.0.0. A global override openstack_service_bind_address may be "
"used by a deployer either in group_vars or user_variables to define an "
"alternative IP address for services to bind to. This feature allows a "
"deployer to bind all of the services to a specific network, for example the "
"openstack management network. In this release the default binding remains "
"0.0.0.0, and future releases may default the binding to the management "
"network."
msgstr ""
"Setiap peran layanan openstack memiliki variabel baru <role>_bind_address "
"yang standarnya adalah 0,0.0.0. Openstack_service_service_bind_address "
"global dapat digunakan oleh deployer baik dalam group_vars atau "
"user_variables untuk menentukan alamat IP alternatif untuk mengikat layanan. "
"Fitur ini memungkinkan penyebar untuk mengikat semua layanan ke jaringan "
"tertentu, misalnya jaringan manajemen openstack. Dalam rilis ini pengikatan "
"default tetap 0.0.0.0, dan rilis di masa depan mungkin default pengikatan ke "
"jaringan manajemen."

msgid "Each service using RabbitMQ now has a separate vhost and user."
msgstr ""
"Setiap layanan yang menggunakan RabbitMQ sekarang memiliki vhost dan "
"pengguna yang terpisah."

msgid ""
"Each service using RabbitMQ now has a separate vhost and user. The shared / "
"vhost is cleaned up so that it contains only the default data. The shared "
"user 'openstack' is removed."
msgstr ""
"Setiap layanan yang menggunakan RabbitMQ sekarang memiliki vhost dan "
"pengguna yang terpisah. Shared/vhost dibersihkan sehingga hanya berisi data "
"default. 'openstack' pengguna bersama dihapus."

msgid ""
"Enable HTTPS on the horizon host without a load balancer. This is the role's "
"default behaviour which matches what it always has been."
msgstr ""
"Aktifkan HTTPS di horison host tanpa penyeimbang beban. Ini adalah perilaku "
"default peran yang cocok dengan yang selalu ada."

msgid ""
"Enable Kernel Shared Memory support by setting ``nova_compute_ksm_enabled`` "
"to ``True``."
msgstr ""
"Aktifkan dukungan Kernel Shared Memory dengan mengatur "
"``nova_compute_ksm_enabled`` ke ``True``."

msgid ""
"Enable networking-bgpvpn ml2 neutron driver to make ``OpenDaylight SDN "
"Controller`` to support BGPVPN for external network connectivity. You can "
"set the ``neutron_plugin_type`` to ``ml2.opendaylight`` and "
"``neutron_plugin_base`` to ``odl-router_v2`` and ``bgpvpn`` to enable BGPVPN "
"on the OpenDaylight."
msgstr ""
"Enable networking-bgpvpn ml2 neutron driver to make ``OpenDaylight SDN "
"Controller`` to support BGPVPN for external network connectivity. You can "
"set the ``neutron_plugin_type`` to ``ml2.opendaylight`` and "
"``neutron_plugin_base`` to ``odl-router_v2`` and ``bgpvpn`` to enable BGPVPN "
"on the OpenDaylight."

msgid ""
"Enable rsync module per object server drive by setting the "
"``swift_rsync_module_per_drive`` setting to ``True``. Set this to configure "
"rsync and swift to utilise individual configuration per drive. This is "
"required when disabling rsyncs to individual disks. For example, in a disk "
"full scenario."
msgstr ""
"Aktifkan modul rsync per drive server objek dengan mengatur pengaturan "
"``swift_rsync_module_per_drive`` ke ``True``. Setel ini untuk "
"mengkonfigurasi rsync dan cepat untuk menggunakan konfigurasi individual per "
"drive. Ini diperlukan saat menonaktifkan rsyncs ke disk individual. "
"Misalnya, dalam skenario disk penuh."

msgid ""
"Errors relating to groups containing both hosts and other groups as children "
"now raise a more descriptive error. See inventory documentation for more "
"details. Fixes bug"
msgstr ""
"Kesalahan yang berkaitan dengan grup yang anggotanya host dan grup lain "
"ketika turunannya menimbulkan kesalahan yang lebih deskriptif. Lihat "
"dokumentasi inventaris untuk lebih jelasnya. Memperbaiki bug"

msgid "Example, for an override like:"
msgstr "Contoh, untuk override seperti:"

msgid ""
"Existing LBaaS v1 load balancers and agents will not be altered by the new "
"OpenStack-Ansible release."
msgstr ""
"Agent dan penyeimbang beban LBaaS v1 yang ada tidak akan diubah oleh rilis "
"OpenStack-Ansible yang baru."

msgid ""
"Experimental support has been added to allow the deployment of the OpenStack "
"Bare Metal Service (Ironic). Details for how to set it up are available in "
"the `OpenStack-Ansible Install Guide for Ironic <http://docs.openstack.org/"
"developer/openstack-ansible/install-guide/configure-ironic.html>`_."
msgstr ""
"Dukungan eksperimental telah ditambahkan untuk memungkinkan penyebaran "
"OpenStack Bare Metal Service (Ironic). Rincian cara mengaturnya tersedia di "
"`OpenStack-Ansible Install Guide for Ironic <http://docs.openstack.org/"
"developer/openstack-ansible/install-guide/configure-ironic.html>`_."

msgid ""
"Experimental support has been added to allow the deployment of the OpenStack "
"Bare Metal Service (Ironic). Details for how to set it up are available in "
"the `OpenStack-Ansible Install Guide for Ironic <http://docs.openstack.org/"
"developer/openstack-ansible/mitaka/install-guide/configure-ironic.html>`_."
msgstr ""
"Dukungan eksperimental telah ditambahkan untuk memungkinkan penyebaran "
"OpenStack Bare Metal Service (Ironic). Rincian cara mengaturnya tersedia di "
"`OpenStack-Ansible Install Guide for Ironic <http://docs.openstack.org/"
"developer/openstack-ansible/mitaka/install-guide/configure-ironic.html>`_."

msgid ""
"Experimental support has been added to allow the deployment of the OpenStack "
"Designate service when hosts are present in the host group ``dnsaas_hosts``."
msgstr ""
"Dukungan eksperimental telah ditambahkan untuk memungkinkan penyebaran "
"layanan OpenStack Designate ketika host ada di grup host ``dnsaas_hosts``."

msgid ""
"Experimental support has been added to allow the deployment of the OpenStack "
"Magnum service when hosts are present in the host group ``magnum-"
"infra_hosts``."
msgstr ""
"Dukungan eksperimental telah ditambahkan untuk memungkinkan penyebaran "
"layanan OpenStack Magnum ketika host ada di grup host ``magnum-infra_hosts``."

msgid ""
"Experimental support has been added to allow the deployment of the OpenStack "
"Masakari service when hosts are present in the host group ``masakari-"
"infra_hosts``."
msgstr ""
"Dukungan eksperimental telah ditambahkan untuk memungkinkan penyebaran "
"layanan OpenStack Masakari ketika host ada di grup host ``masakari-"
"infra_hosts``."

msgid ""
"Experimental support has been added to allow the deployment of the OpenStack "
"Octavia Load Balancing service when hosts are present in the host group "
"``octavia-infra_hosts``."
msgstr ""
"Dukungan eksperimental telah ditambahkan untuk memungkinkan penyebaran "
"layanan OpenStack Octavia Load Balancing ketika host hadir dalam grup host "
"``octavia-infra_hosts``."

msgid ""
"Experimental support has been added to allow the deployment of the OpenStack "
"Senlin service when hosts are present in the host group ``senlin-"
"infra_hosts``."
msgstr ""
"Dukungan eksperimental telah ditambahkan untuk memungkinkan deployment "
"layanan OpenStack Senlin ketika host ada di grup host ``senlin-infra_hosts``."

msgid ""
"Experimental support has been added to allow the deployment of the OpenStack "
"trove service when hosts are present in the host group ``trove-infra_hosts``."
msgstr ""
"Dukungan eksperimental telah ditambahkan untuk memungkinkan penyebaran "
"layanan OpenStack trove ketika host ada di grup host ``trove-infra_hosts``."

msgid ""
"Experimental support has been added to allow the deployment of the Sahara "
"data-processing service. To deploy sahara hosts should be present in the "
"host group ``sahara-infra_hosts``."
msgstr ""
"Dukungan eksperimental telah ditambahkan untuk memungkinkan penyebaran "
"layanan pemrosesan data Sahara. Untuk menggunakan host sahara harus ada di "
"grup host ``sahara-infra_hosts``."

msgid ""
"Extra headers can be added to Keystone responses by adding items to "
"``keystone_extra_headers``. Example:"
msgstr ""
"Header tambahan dapat ditambahkan ke respons Keystone dengan menambahkan "
"item ke ``keystone_extra_headers``. Contoh:"

msgid ""
"FWaaS V2 has been added to neutron. To enable this service simply add "
"\"firewall_v2\" to the \"neutron_plugin_base\" list."
msgstr ""
"FWaaS V2 telah ditambahkan ke neutron. Untuk mengaktifkan layanan ini cukup "
"tambahkan \"firewall_v2\" ke daftar \"neutron_plugin_base\"."

msgid ""
"Failed access logging is now disabled by default and can be enabled by "
"changing ``security_audit_failed_access`` to ``yes``. The rsyslog daemon "
"checks for the existence of log files regularly and this audit rule was "
"triggered very frequently, which led to very large audit logs."
msgstr ""
"Pencatatan akses yang gagal sekarang dinonaktifkan secara default dan dapat "
"diaktifkan dengan mengubah ``security_audit_failed_access`` menjadi ``yes``. "
"Daemon rsyslog memeriksa keberadaan file log secara teratur dan aturan audit "
"ini dipicu sangat sering, yang menyebabkan log audit sangat besar."

msgid "Fedora 25 support is deprecated and no longer tested on each commit."
msgstr "Dukungan Fedora 25 sudah usang dan tidak lagi diuji pada setiap komit."

msgid "Fedora 26 is now supported."
msgstr "Fedora 26 sekarang didukung."

msgid "Fedora is no longer tested in CI for each commit."
msgstr "Fedora tidak lagi diuji dalam CI untuk setiap komit."

msgid ""
"Fix bug https://bugs.launchpad.net/openstack-ansible/+bug/1553796 by "
"ensuring that the --insecure flag is passed to the cinder CLI tool during "
"task execution"
msgstr ""
"Perbaiki bug https://bugs.launchpad.net/openstack-ansible/+bug/1553796 "
"dengan memastikan bahwa the --insecure flag  diteruskan ke CLI cinder tool "
"selama pelaksanaan tugas"

msgid ""
"Fix run-upgrade.sh so that it correctly calls nova-flavor-migration.yml and "
"no longer fails due to the non-existent playbook nova-extra-migrations.yml."
msgstr ""
"Perbaiki run-upgrade.sh sehingga benar memanggil nova-flavor-migration.yml "
"dan tidak lagi gagal karena playbook tidak ada nova-extra-migrations.yml."

msgid ""
"Fixes bug https://bugs.launchpad.net/openstack-ansible/+bug/1778098 where "
"playbook failed, if ``horizon_custom_themes`` is specified, and directory "
"for theme is not provided"
msgstr ""
"Memperbaiki bug https://bugs.launchpad.net/openstack-ansible/+bug/1778098 "
"ketika playbook gagal, jika ``horizon_custom_themes`` ditentukan, dan "
"direktori untuk tema tidak disediakan"

msgid ""
"Fixes neutron HA routers, by enabling ``neutron-l3-agent`` to invoke the "
"required helper script."
msgstr ""
"Memperbaiki router HA neutron, dengan mengaktifkan ``neutron-l3-agent`` "
"untuk memanggil skrip pembantu yang diperlukan."

msgid ""
"For OpenStack-Ansible Liberty releases earlier than 12.2.2 the default "
"container apt source used was ``https://mirror.rackspace.com/ubuntu``. This "
"mirror seems to sometimes have broken package indexes or missing packages. "
"The default package source has therefore been changed to make use of "
"``http://archive.ubuntu.com/ubuntu`` for packages and ``http://security."
"ubuntu.com/ubuntu`` for security packages."
msgstr ""
"Untuk rilis OpenStack-Ansible Liberty lebih awal dari 12.2.2 sumber apt "
"container default yang digunakan adalah ``https://mirror.rackspace.com/"
"ubuntu``. Cermin ini tampaknya terkadang memiliki indeks paket rusak atau "
"paket yang hilang. Sumber paket default karenanya telah diubah untuk "
"menggunakan ``http://archive.ubuntu.com/ubuntu`` untuk paket dan ``http://"
"security.ubuntu.com/ubuntu`` untuk paket keamanan."

msgid ""
"For OpenStack-Ansible Liberty versions <12.0.9 and Kilo versions <11.2.12 "
"the package ``pywbem`` will fail to build due to the update to v0.8.0 "
"including new requirements which are not met by the repo server. This issue "
"has been resolved in 12.0.9. A workaround for this is to set "
"``pywbem<0.8.0`` in the file ``global-requirement-pins.txt``."
msgstr ""
"Untuk versi OpenStack-Ansible Liberty <12.0.9 dan Kilo versi <11.2.12 paket "
"``pywbem`` akan gagal dibangun karena pembaruan ke v0.8.0 termasuk "
"persyaratan baru yang tidak dipenuhi oleh server repo. Masalah ini telah "
"diatasi dalam 12.0.9. Solusi untuk ini adalah dengan menetapkan ``pywbem "
"<0.8.0`` dalam file ``global-requirement-pins.txt``."

msgid ""
"For OpenStack-Ansible Liberty versions >12.0.7,<12.0.9 the wheel version "
"pinned in OpenStack-Ansible (0.29.0) is higher that the OpenStack upper-"
"constraint (0.26.0). This causes an issue where the repo-server install may "
"fail because it cannot find a version of wheel to install that meets the "
"requirements of <0.26.0 and ==0.29.0. A workaround for this issue is to "
"change the wheel package pin in the following files ``wheel==0.26.0``."
msgstr ""
"Untuk versi OpenStack-Ansible Liberty> 12.0.7, <12.0.9 versi roda (wheel "
"version) yang disematkan di OpenStack-Ansible (0.29.0) lebih tinggi daripada "
"batasan atas (upper-constraint) OpenStack (0.26.0). Ini menyebabkan masalah "
"di mana instalasi repo-server mungkin gagal karena tidak dapat menemukan "
"versi untuk menginstal yang memenuhi persyaratan <0.26.0 dan == 0.29.0. "
"Solusi untuk masalah ini adalah mengubah pin paket roda (wheel package pin) "
"dalam file berikut ``wheel == 0.26.0``."

msgid ""
"For OpenStack-Ansible Mitaka releases earlier than 13.3.1 the default "
"container apt source used was ``http://mirror.rackspace.com/ubuntu``. This "
"mirror seems to sometimes have broken package indexes or missing packages. "
"The default package source has therefore been changed to make use of "
"``http://archive.ubuntu.com/ubuntu/`` for packages and ``http://security."
"ubuntu.com/ubuntu`` for security packages."
msgstr ""
"Untuk rilis OpenStack-Ansible Mitaka lebih awal dari 13.3.1 sumber apt "
"container default yang digunakan adalah``http://mirror.rackspace.com/"
"ubuntu``. Cermin ini tampaknya terkadang memiliki indeks paket rusak atau "
"paket yang hilang. Sumber paket default karenanya telah diubah untuk "
"menggunakan ``http://archive.ubuntu.com/ubuntu/`` untuk paket dan ``http://"
"security.ubuntu.com/ubuntu`` untuk paket keamanan."

msgid "For additional information, refer to the following bugs:"
msgstr "Untuk informasi tambahan, lihat bug berikut:"

msgid ""
"For all newton releases up to 14.2.14 when executing the os-nova-install.yml "
"playbook the ``nova-novncproxy`` and ``nova-spicehtml5proxy`` services will "
"fail. The workaround to resolve this issue is to restart the services."
msgstr ""
"Untuk semua rilis newton hingga 14.2.14 ketika menjalankan playbook os-nova-"
"install.yml ``nova-novncproxy`` dan ``nova-spicehtml5proxy`` layanan akan "
"gagal. Solusi untuk menyelesaikan masalah ini adalah memulai kembali layanan."

msgid ""
"For all ocata releases prior to OpenStack-Ansible 15.1.16, several of the "
"magnum requirements were not constrained. This resulted in the kubernetes "
"version changing over time unexpectedly, rather than by intention. Most "
"recently this lack of constraint causes the repo build to fail when trying "
"to build the magnum venv due to incompatible requirements."
msgstr ""
"Untuk semua rilis ocata sebelum OpenStack-Ansible 15.1.16, beberapa "
"persyaratan magnum tidak dibatasi. Ini mengakibatkan versi kubernet berubah "
"dari waktu ke waktu secara tak terduga, bukan karena niat. Baru-baru ini "
"kurangnya pembatasan ini menyebabkan repo build gagal ketika mencoba "
"membangun magnum venv karena persyaratan yang tidak kompatibel."

msgid ""
"For all ocata releases up to 15.1.16 when executing the os-nova-install.yml "
"playbook the ``nova-novncproxy`` and ``nova-spicehtml5proxy`` services will "
"fail. The workaround to resolve this issue is to restart the services."
msgstr ""
"Untuk semua rilis ocata hingga 15.1.16 ketika menjalankan playbook os-nova-"
"install.yml, ``nova-novncproxy`` dan `` nova-spicehtml5proxy`` layanan akan "
"gagal. Solusi untuk menyelesaikan masalah ini adalah memulai kembali "
"(restart) layanan."

msgid ""
"For all pike releases up to 16.0.7 when executing the os-nova-install.yml "
"playbook the ``nova-novncproxy`` and ``nova-spicehtml5proxy`` services will "
"fail. The workaround to resolve this issue is to restart the services."
msgstr ""
"Untuk semua rilis pike hingga 16.0.7 saat menjalankan playbook os-nova-"
"install.yml, ``nova-novncproxy`` dan ``nova-spicehtml5proxy`` layanan akan "
"gagal. Solusi untuk menyelesaikan masalah ini adalah memulai kembali layanan."

msgid ""
"For example, a deployer could have disabled direct root ssh logins with the "
"following variable:"
msgstr ""
"Sebagai contoh, seorang deployer bisa menonaktifkan login ssh root langsung "
"dengan variabel berikut:"

msgid ""
"For example, to enable the `InstanceLocalityFilter` in addition to the "
"normally enabled scheduler filters, use the following variable."
msgstr ""
"Misalnya, untuk mengaktifkan `InstanceLocalityFilter` di samping filter "
"penjadwal yang diaktifkan secara normal, gunakan variabel berikut ini."

msgid "For more information about SFC in Neutron, refer to the following:"
msgstr ""
"Untuk informasi lebih lanjut tentang SFC di Neutron, lihat yang berikut ini:"

msgid ""
"For newton releases 14.2.14 and earlier, we recommend pinning the LXD "
"version for all newton deployments at a version less than 2.0.11. For newton "
"releases 14.2.15 onwards, the newer release of LXD should be usable again."
msgstr ""
"Untuk rilis newton 14.2.14 dan sebelumnya, kami sarankan menyematkan versi "
"LXD untuk semua penyebaran newton pada versi kurang dari 2.0.11. Untuk rilis "
"newton 14.2.15 dan seterusnya, rilis LXD yang lebih baru harus dapat "
"digunakan kembali."

msgid ""
"For systems using the APT package manager, the sources file for the MariaDB "
"repo now has a consistent name, 'MariaDB.list'."
msgstr ""
"Untuk sistem yang menggunakan manajer paket APT, file sumber untuk repo "
"MariaDB sekarang memiliki nama yang konsisten, 'MariaDB.list'."

msgid ""
"For systems using the APT package manager, the sources files for the MariaDB "
"and Percona repos now have consistent names, 'MariaDB.list' and 'Percona."
"list'."
msgstr ""
"Untuk sistem yang menggunakan manajer paket APT, file sumber untuk repo "
"MariaDB dan Percona sekarang memiliki nama yang konsisten, 'MariaDB.list' "
"dan 'Percona.list'."

msgid ""
"For the ``os_aodh`` role, the systemd unit ``TimeoutSec`` value which "
"controls the time between sending a SIGTERM signal and a SIGKILL signal when "
"stopping or restarting the service has been reduced from 300 seconds to 120 "
"seconds. This provides 2 minutes for long-lived sessions to drain while "
"preventing new ones from starting before a restart or a stop. The "
"``RestartSec`` value which controls the time between the service stop and "
"start when restarting has been reduced from 150 seconds to 2 seconds to make "
"the restart happen faster. These values can be adjusted by using the "
"``aodh_*_init_config_overrides`` variables which use the ``config_template`` "
"task to change template defaults."
msgstr ""
"Untuk peran ``os_aodh``, nilai unit sistemd ``TimeoutSec`` yang mengontrol "
"waktu antara pengiriman sinyal SIGTERM dan sinyal SIGKILL saat menghentikan "
"atau memulai kembali layanan telah berkurang dari 300 detik menjadi 120 "
"detik. Ini memberikan waktu 2 menit untuk sesi long-lived untuk dikeringkan "
"(drain) sekaligus mencegah yang baru dimulai sebelum restart atau berhenti. "
"Nilai ``RestartSec`` yang mengontrol waktu antara berhenti layanan dan mulai "
"ketika memulai ulang telah berkurang dari 150 detik menjadi 2 detik untuk "
"membuat restart terjadi lebih cepat. Nilai ini dapat disesuaikan dengan "
"menggunakan variabel ``aodh_*_init_config_overrides`` yang menggunakan tugas "
"``config_template`` untuk mengubah default templat."

msgid ""
"For the ``os_barbican`` role, the systemd unit ``TimeoutSec`` value which "
"controls the time between sending a SIGTERM signal and a SIGKILL signal when "
"stopping or restarting the service has been reduced from 300 seconds to 120 "
"seconds. This provides 2 minutes for long-lived sessions to drain while "
"preventing new ones from starting before a restart or a stop. The "
"``RestartSec`` value which controls the time between the service stop and "
"start when restarting has been reduced from 150 seconds to 2 seconds to make "
"the restart happen faster. These values can be adjusted by using the "
"``barbican_*_init_config_overrides`` variables which use the "
"``config_template`` task to change template defaults."
msgstr ""
"Untuk peran ``os_barbican``, nilai unit sistemd ``TimeoutSec`` yang "
"mengontrol waktu antara pengiriman sinyal SIGTERM dan sinyal SIGKILL saat "
"menghentikan atau memulai kembali layanan telah berkurang dari 300 detik "
"menjadi 120 detik. Ini memberikan waktu 2 menit untuk sesi long-lived untuk "
"dikeringkan (drain) sekaligus mencegah yang baru dimulai sebelum restart "
"atau berhenti. Nilai ``RestartSec`` yang mengontrol waktu antara berhenti "
"layanan dan mulai ketika memulai ulang telah berkurang dari 150 detik "
"menjadi 2 detik untuk membuat restart terjadi lebih cepat. Nilai ini dapat "
"disesuaikan dengan menggunakan variabel ``barbican_*_init_config_overrides`` "
"yang menggunakan tugas ``config_template`` untuk mengubah default templat."

msgid ""
"For the ``os_ceilometer`` role, the systemd unit ``TimeoutSec`` value which "
"controls the time between sending a SIGTERM signal and a SIGKILL signal when "
"stopping or restarting the service has been reduced from 300 seconds to 120 "
"seconds. This provides 2 minutes for long-lived sessions to drain while "
"preventing new ones from starting before a restart or a stop. The "
"``RestartSec`` value which controls the time between the service stop and "
"start when restarting has been reduced from 150 seconds to 2 seconds to make "
"the restart happen faster. These values can be adjusted by using the "
"``ceilometer_*_init_config_overrides`` variables which use the "
"``config_template`` task to change template defaults."
msgstr ""
"Untuk peran ``os_ceilometer``, nilai unit sistemd ``TimeoutSec`` yang "
"mengontrol waktu antara pengiriman sinyal SIGTERM dan sinyal SIGKILL saat "
"menghentikan atau memulai kembali layanan telah berkurang dari 300 detik "
"menjadi 120 detik. Ini memberikan waktu 2 menit untuk sesi long-lived untuk "
"dikeringkan (drain) sekaligus mencegah yang baru dimulai sebelum restart "
"atau berhenti. Nilai ``RestartSec`` yang mengontrol waktu antara berhenti "
"layanan dan mulai ketika memulai ulang telah berkurang dari 150 detik "
"menjadi 2 detik untuk membuat restart terjadi lebih cepat. Nilai ini dapat "
"disesuaikan dengan menggunakan variabel "
"``ceilometer_*_init_config_overrides`` yang menggunakan tugas "
"``config_template`` untuk mengubah default templat."

msgid ""
"For the ``os_cinder`` role, the systemd unit ``TimeoutSec`` value which "
"controls the time between sending a SIGTERM signal and a SIGKILL signal when "
"stopping or restarting the service has been reduced from 300 seconds to 120 "
"seconds. This provides 2 minutes for long-lived sessions to drain while "
"preventing new ones from starting before a restart or a stop. The "
"``RestartSec`` value which controls the time between the service stop and "
"start when restarting has been reduced from 150 seconds to 2 seconds to make "
"the restart happen faster. These values can be adjusted by using the "
"``cinder_*_init_config_overrides`` variables which use the "
"``config_template`` task to change template defaults."
msgstr ""
"Untuk peran ``os_cinder``, nilai unit sistemd ``TimeoutSec`` yang mengontrol "
"waktu antara pengiriman sinyal SIGTERM dan sinyal SIGKILL saat menghentikan "
"atau memulai kembali layanan telah berkurang dari 300 detik menjadi 120 "
"detik. Ini memberikan waktu 2 menit untuk sesi long-lived untuk dikeringkan "
"(drain) sekaligus mencegah yang baru dimulai sebelum restart atau berhenti. "
"Nilai ``RestartSec`` yang mengontrol waktu antara berhenti layanan dan mulai "
"ketika memulai ulang telah berkurang dari 150 detik menjadi 2 detik untuk "
"membuat restart terjadi lebih cepat. Nilai ini dapat disesuaikan dengan "
"menggunakan variabel ``cinder_*_init_config_overrides`` yang menggunakan "
"tugas ``config_template`` untuk mengubah default templat."

msgid ""
"For the ``os_cloudkitty`` role, the systemd unit ``TimeoutSec`` value which "
"controls the time between sending a SIGTERM signal and a SIGKILL signal when "
"stopping or restarting the service has been reduced from 300 seconds to 120 "
"seconds. This provides 2 minutes for long-lived sessions to drain while "
"preventing new ones from starting before a restart or a stop. The "
"``RestartSec`` value which controls the time between the service stop and "
"start when restarting has been reduced from 150 seconds to 2 seconds to make "
"the restart happen faster. These values can be adjusted by using the "
"``cloudkitty_*_init_config_overrides`` variables which use the "
"``config_template`` task to change template defaults."
msgstr ""
"Untuk peran ``os_cloudkitty``, nilai unit systemd ``TimeoutSec`` yang "
"mengontrol waktu antara pengiriman sinyal SIGTERM dan sinyal SIGKILL saat "
"menghentikan atau memulai kembali layanan telah berkurang dari 300 detik "
"menjadi 120 detik. Ini memberikan waktu 2 menit untuk sesi yang tahan lama "
"untuk dikeringkan sekaligus mencegah yang baru dimulai sebelum restart atau "
"berhenti. Nilai ``RestartSec`` yang mengontrol waktu antara berhenti layanan "
"dan mulai ketika memulai ulang telah berkurang dari 150 detik menjadi 2 "
"detik untuk membuat restart terjadi lebih cepat. Nilai-nilai ini dapat "
"disesuaikan dengan menggunakan variabel "
"``cloudkitty_*_init_config_overrides`` yang menggunakan tugas "
"``config_template`` untuk mengubah default templat."

msgid ""
"For the ``os_designate`` role, the systemd unit ``TimeoutSec`` value which "
"controls the time between sending a SIGTERM signal and a SIGKILL signal when "
"stopping or restarting the service has been reduced from 300 seconds to 120 "
"seconds. This provides 2 minutes for long-lived sessions to drain while "
"preventing new ones from starting before a restart or a stop. The "
"``RestartSec`` value which controls the time between the service stop and "
"start when restarting has been reduced from 150 seconds to 2 seconds to make "
"the restart happen faster. These values can be adjusted by using the "
"``designate_*_init_config_overrides`` variables which use the "
"``config_template`` task to change template defaults."
msgstr ""
"Untuk peran ``os_designate``, nilai unit sistemd ``TimeoutSec`` yang "
"mengontrol waktu antara pengiriman sinyal SIGTERM dan sinyal SIGKILL saat "
"menghentikan atau memulai kembali layanan telah berkurang dari 300 detik "
"menjadi 120 detik. Ini memberikan waktu 2 menit untuk sesi long-lived untuk "
"dikeringkan sekaligus mencegah yang baru dimulai sebelum restart atau "
"berhenti. Nilai ``RestartSec`` yang mengontrol waktu antara berhenti layanan "
"dan mulai ketika memulai ulang telah berkurang dari 150 detik menjadi 2 "
"detik untuk membuat restart terjadi lebih cepat. Nilai ini dapat disesuaikan "
"dengan menggunakan variabel ``designate_*_init_config_overrides`` yang "
"menggunakan tugas ``config_template`` untuk mengubah default templat."

msgid ""
"For the ``os_glance`` role, the systemd unit ``RestartSec`` value which "
"controls the time between the service stop and start when restarting has "
"been reduced from 150 seconds to 2 seconds to make the restart happen "
"faster. This value can be adjusted by using the "
"``glance_*_init_config_overrides`` variables which use the "
"``config_template`` task to change template defaults."
msgstr ""
"Untuk peran ``os_glance``, nilai systemd unit ``RestartSec`` yang mengontrol "
"waktu antara penghentian layanan dan mulai ketika memulai ulang telah "
"dikurangi dari 150 detik menjadi 2 detik untuk membuat restart terjadi lebih "
"cepat. Nilai ini dapat disesuaikan dengan menggunakan variabel "
"``glance_*_init_config_overrides`` yang menggunakan tugas "
"``config_template`` untuk mengubah default templat."

msgid ""
"For the ``os_gnocchi`` role, the systemd unit ``TimeoutSec`` value which "
"controls the time between sending a SIGTERM signal and a SIGKILL signal when "
"stopping or restarting the service has been reduced from 300 seconds to 120 "
"seconds. This provides 2 minutes for long-lived sessions to drain while "
"preventing new ones from starting before a restart or a stop. The "
"``RestartSec`` value which controls the time between the service stop and "
"start when restarting has been reduced from 150 seconds to 2 seconds to make "
"the restart happen faster. These values can be adjusted by using the "
"``gnocchi_*_init_config_overrides`` variables which use the "
"``config_template`` task to change template defaults."
msgstr ""
"Untuk peran ``os_gnocchi``, nilai unit sistemd ``TimeoutSec`` yang "
"mengontrol waktu antara pengiriman sinyal SIGTERM dan sinyal SIGKILL saat "
"menghentikan atau memulai kembali layanan telah berkurang dari 300 detik "
"menjadi 120 detik. Ini memberikan waktu 2 menit untuk sesi long-lived untuk "
"dikeringkan (drain) sekaligus mencegah yang baru dimulai sebelum restart "
"atau berhenti. Nilai ``RestartSec`` yang mengontrol waktu antara berhenti "
"layanan dan mulai ketika memulai ulang telah berkurang dari 150 detik "
"menjadi 2 detik untuk membuat restart terjadi lebih cepat. Nilai ini dapat "
"disesuaikan dengan menggunakan variabel ``gnocchi_*_init_config_overrides`` "
"yang menggunakan tugas ``config_template`` untuk mengubah default templat."

msgid ""
"For the ``os_heat`` role, the systemd unit ``TimeoutSec`` value which "
"controls the time between sending a SIGTERM signal and a SIGKILL signal when "
"stopping or restarting the service has been reduced from 300 seconds to 120 "
"seconds. This provides 2 minutes for long-lived sessions to drain while "
"preventing new ones from starting before a restart or a stop. The "
"``RestartSec`` value which controls the time between the service stop and "
"start when restarting has been reduced from 150 seconds to 2 seconds to make "
"the restart happen faster. These values can be adjusted by using the "
"``heat_*_init_config_overrides`` variables which use the ``config_template`` "
"task to change template defaults."
msgstr ""
"Untuk peran ``os_heat``, nilai unit sistemd ``TimeoutSec`` yang mengontrol "
"waktu antara pengiriman sinyal SIGTERM dan sinyal SIGKILL saat menghentikan "
"atau memulai kembali layanan telah berkurang dari 300 detik menjadi 120 "
"detik. Ini memberikan waktu 2 menit untuk sesi long-lived untuk dikeringkan "
"(drain) sekaligus mencegah yang baru dimulai sebelum restart atau berhenti. "
"Nilai ``RestartSec`` yang mengontrol waktu antara berhenti layanan dan mulai "
"ketika memulai ulang telah berkurang dari 150 detik menjadi 2 detik untuk "
"membuat restart terjadi lebih cepat. Nilai ini dapat disesuaikan dengan "
"menggunakan variabel  ``heat_*_init_config_overrides``  yang menggunakan "
"tugas ``config_template`` untuk mengubah default templat."

msgid ""
"For the ``os_ironic`` role, the systemd unit ``TimeoutSec`` value which "
"controls the time between sending a SIGTERM signal and a SIGKILL signal when "
"stopping or restarting the service has been reduced from 300 seconds to 120 "
"seconds. This provides 2 minutes for long-lived sessions to drain while "
"preventing new ones from starting before a restart or a stop. The "
"``RestartSec`` value which controls the time between the service stop and "
"start when restarting has been reduced from 150 seconds to 2 seconds to make "
"the restart happen faster. These values can be adjusted by using the "
"``ironic_*_init_config_overrides`` variables which use the "
"``config_template`` task to change template defaults."
msgstr ""
"Untuk peran ``os_ironic``, nilai unit sistemd ``TimeoutSec`` yang mengontrol "
"waktu antara pengiriman sinyal SIGTERM dan sinyal SIGKILL saat menghentikan "
"atau memulai kembali layanan telah berkurang dari 300 detik menjadi 120 "
"detik. Ini memberikan waktu 2 menit untuk sesi long-lived untuk dikeringkan "
"(drain) sekaligus mencegah yang baru dimulai sebelum restart atau berhenti. "
"Nilai `` RestartSec`` yang mengontrol waktu antara berhenti layanan dan "
"mulai ketika memulai ulang telah berkurang dari 150 detik menjadi 2 detik "
"untuk membuat restart terjadi lebih cepat. Nilai ini dapat disesuaikan "
"dengan menggunakan variabel ``ironis _*_ init_config_overrides`` yang "
"menggunakan tugas ``config_template`` untuk mengubah default templat."

msgid ""
"For the ``os_keystone`` role, the systemd unit ``TimeoutSec`` value which "
"controls the time between sending a SIGTERM signal and a SIGKILL signal when "
"stopping or restarting the service has been reduced from 300 seconds to 120 "
"seconds. This provides 2 minutes for long-lived sessions to drain while "
"preventing new ones from starting before a restart or a stop. The "
"``RestartSec`` value which controls the time between the service stop and "
"start when restarting has been reduced from 150 seconds to 2 seconds to make "
"the restart happen faster. These values can be adjusted by using the "
"``keystone_*_init_config_overrides`` variables which use the "
"``config_template`` task to change template defaults."
msgstr ""
"Untuk peran ``os_keystone``, nilai unit sistemd ``TimeoutSec`` yang "
"mengontrol waktu antara pengiriman sinyal SIGTERM dan sinyal SIGKILL saat "
"menghentikan atau memulai kembali layanan telah berkurang dari 300 detik "
"menjadi 120 detik. Ini memberikan waktu 2 menit untuk sesi long-lived untuk "
"dikeringkan (drain) sekaligus mencegah yang baru dimulai sebelum restart "
"atau berhenti. Nilai ``RestartSec`` yang mengontrol waktu antara berhenti "
"layanan dan mulai ketika memulai ulang telah berkurang dari 150 detik "
"menjadi 2 detik untuk membuat restart terjadi lebih cepat. Nilai ini dapat "
"disesuaikan dengan menggunakan variabel ``keystone _*_ "
"init_config_overrides`` yang menggunakan tugas ``config_template`` untuk "
"mengubah default templat."

msgid ""
"For the ``os_magnum`` role, the systemd unit ``TimeoutSec`` value which "
"controls the time between sending a SIGTERM signal and a SIGKILL signal when "
"stopping or restarting the service has been reduced from 300 seconds to 120 "
"seconds. This provides 2 minutes for long-lived sessions to drain while "
"preventing new ones from starting before a restart or a stop. The "
"``RestartSec`` value which controls the time between the service stop and "
"start when restarting has been reduced from 150 seconds to 2 seconds to make "
"the restart happen faster. These values can be adjusted by using the "
"``magnum_*_init_config_overrides`` variables which use the "
"``config_template`` task to change template defaults."
msgstr ""
"Untuk peran ``os_magnum``, nilai unit sistemd ``TimeoutSec`` yang mengontrol "
"waktu antara pengiriman sinyal SIGTERM dan sinyal SIGKILL saat menghentikan "
"atau memulai kembali layanan telah berkurang dari 300 detik menjadi 120 "
"detik. Ini memberikan waktu 2 menit untuk sesi long-lived untuk dikeringkan "
"sekaligus mencegah yang baru dimulai sebelum restart atau berhenti. Nilai "
"``RestartSec`` yang mengontrol waktu antara berhenti layanan dan mulai "
"ketika memulai ulang telah berkurang dari 150 detik menjadi 2 detik untuk "
"membuat restart terjadi lebih cepat. Nilai ini dapat disesuaikan dengan "
"menggunakan variabel ``magnum _*_ init_config_overrides`` yang menggunakan "
"tugas ``config_template`` untuk mengubah default templat."

msgid ""
"For the ``os_neutron`` role, the systemd unit ``TimeoutSec`` value which "
"controls the time between sending a SIGTERM signal and a SIGKILL signal when "
"stopping or restarting the service has been reduced from 300 seconds to 120 "
"seconds. This provides 2 minutes for long-lived sessions to drain while "
"preventing new ones from starting before a restart or a stop. The "
"``RestartSec`` value which controls the time between the service stop and "
"start when restarting has been reduced from 150 seconds to 2 seconds to make "
"the restart happen faster. These values can be adjusted by using the "
"``neutron_*_init_config_overrides`` variables which use the "
"``config_template`` task to change template defaults."
msgstr ""
"Untuk peran ``os_neutron``, nilai unit sistemd ``TimeoutSec`` yang "
"mengontrol waktu antara pengiriman sinyal SIGTERM dan sinyal SIGKILL saat "
"menghentikan atau memulai kembali layanan telah berkurang dari 300 detik "
"menjadi 120 detik. Ini memberikan waktu 2 menit untuk sesi long-lived untuk "
"dikeringkan (drain) sekaligus mencegah yang baru dimulai sebelum restart "
"atau berhenti. Nilai ``RestartSec`` yang mengontrol waktu antara berhenti "
"layanan dan mulai ketika memulai ulang telah berkurang dari 150 detik "
"menjadi 2 detik untuk membuat restart terjadi lebih cepat. Nilai ini dapat "
"disesuaikan dengan menggunakan variabel ``neutron _*_ "
"init_config_overrides`` yang menggunakan tugas ``config_template`` untuk "
"mengubah default templat."

msgid ""
"For the ``os_nova`` role, the systemd unit ``TimeoutSec`` value which "
"controls the time between sending a SIGTERM signal and a SIGKILL signal when "
"stopping or restarting the service has been reduced from 300 seconds to 120 "
"seconds. This provides 2 minutes for long-lived sessions to drain while "
"preventing new ones from starting before a restart or a stop. The "
"``RestartSec`` value which controls the time between the service stop and "
"start when restarting has been reduced from 150 seconds to 2 seconds to make "
"the restart happen faster. These values can be adjusted by using the "
"``nova_*_init_config_overrides`` variables which use the ``config_template`` "
"task to change template defaults."
msgstr ""
"Untuk peran ``os_nova``, nilai unitd unit ``TimeoutSec`` yang mengontrol "
"waktu antara pengiriman sinyal SIGTERM dan sinyal SIGKILL saat menghentikan "
"atau memulai kembali layanan telah berkurang dari 300 detik menjadi 120 "
"detik. Ini memberikan waktu 2 menit untuk sesi long-lived untuk dikeringkan "
"sekaligus mencegah yang baru dimulai sebelum restart atau berhenti. Nilai "
"``RestartSec`` yang mengontrol waktu antara berhenti layanan dan mulai "
"ketika memulai ulang telah berkurang dari 150 detik menjadi 2 detik untuk "
"membuat restart terjadi lebih cepat. Nilai ini dapat disesuaikan dengan "
"menggunakan variabel ``nova_*_init_config_overrides`` yang menggunakan tugas "
"``config_template`` untuk mengubah default templat."

msgid ""
"For the ``os_octavia`` role, the systemd unit ``TimeoutSec`` value which "
"controls the time between sending a SIGTERM signal and a SIGKILL signal when "
"stopping or restarting the service has been reduced from 300 seconds to 120 "
"seconds. This provides 2 minutes for long-lived sessions to drain while "
"preventing new ones from starting before a restart or a stop. The "
"``RestartSec`` value which controls the time between the service stop and "
"start when restarting has been reduced from 150 seconds to 2 seconds to make "
"the restart happen faster. These values can be adjusted by using the "
"``octavia_*_init_overrides`` variables which use the ``config_template`` "
"task to change template defaults."
msgstr ""
"Untuk peran ``os_octavia``, nilai unit sistemd ``TimeoutSec`` yang "
"mengontrol waktu antara pengiriman sinyal SIGTERM dan sinyal SIGKILL saat "
"menghentikan atau memulai kembali layanan telah berkurang dari 300 detik "
"menjadi 120 detik. Ini memberikan waktu 2 menit untuk sesi long-lived untuk "
"dikeringkan sekaligus mencegah yang baru dimulai sebelum restart atau "
"berhenti. Nilai ``RestartSec`` yang mengontrol waktu antara berhenti layanan "
"dan mulai ketika memulai ulang telah berkurang dari 150 detik menjadi 2 "
"detik untuk membuat restart terjadi lebih cepat. Nilai ini dapat disesuaikan "
"dengan menggunakan variabel ``octavia_*_init_overrides`` yang menggunakan "
"tugas ``config_template`` untuk mengubah default templat."

msgid ""
"For the ``os_sahara`` role, the systemd unit ``TimeoutSec`` value which "
"controls the time between sending a SIGTERM signal and a SIGKILL signal when "
"stopping or restarting the service has been reduced from 300 seconds to 120 "
"seconds. This provides 2 minutes for long-lived sessions to drain while "
"preventing new ones from starting before a restart or a stop. The "
"``RestartSec`` value which controls the time between the service stop and "
"start when restarting has been reduced from 150 seconds to 2 seconds to make "
"the restart happen faster. These values can be adjusted by using the "
"``sahara_*_init_config_overrides`` variables which use the "
"``config_template`` task to change template defaults."
msgstr ""
"Untuk peran ``os_sahara``, nilai unit sistemd ``TimeoutSec`` yang mengontrol "
"waktu antara pengiriman sinyal SIGTERM dan sinyal SIGKILL saat menghentikan "
"atau memulai kembali layanan telah berkurang dari 300 detik menjadi 120 "
"detik. Ini memberikan waktu 2 menit untuk sesi long-lived untuk dikeringkan "
"sekaligus mencegah yang baru dimulai sebelum restart atau berhenti. Nilai "
"``RestartSec`` yang mengontrol waktu antara berhenti layanan dan mulai "
"ketika memulai ulang telah berkurang dari 150 detik menjadi 2 detik untuk "
"membuat restart terjadi lebih cepat. Nilai ini dapat disesuaikan dengan "
"menggunakan variabel ``sahara_*_init_config_overrides`` yang menggunakan "
"tugas ``config_template`` untuk mengubah default templat."

msgid ""
"For the ``os_swift`` role, the systemd unit ``TimeoutSec`` value which "
"controls the time between sending a SIGTERM signal and a SIGKILL signal when "
"stopping or restarting the service has been reduced from 300 seconds to 120 "
"seconds. This provides 2 minutes for long-lived sessions to drain while "
"preventing new ones from starting before a restart or a stop. The "
"``RestartSec`` value which controls the time between the service stop and "
"start when restarting has been reduced from 150 seconds to 2 seconds to make "
"the restart happen faster. These values can be adjusted by using the "
"``swift_*_init_config_overrides`` variables which use the "
"``config_template`` task to change template defaults."
msgstr ""
"Untuk peran ``os_swift``, nilai unit sistemd ``TimeoutSec`` yang mengontrol "
"waktu antara pengiriman sinyal SIGTERM dan sinyal SIGKILL saat menghentikan "
"atau memulai kembali layanan telah berkurang dari 300 detik menjadi 120 "
"detik. Ini memberikan waktu 2 menit untuk sesi long-lived untuk dikeringkan "
"sekaligus mencegah yang baru dimulai sebelum restart atau berhenti. Nilai "
"``RestartSec`` yang mengontrol waktu antara berhenti layanan dan mulai "
"ketika memulai ulang telah berkurang dari 150 detik menjadi 2 detik untuk "
"membuat restart terjadi lebih cepat. Nilai ini dapat disesuaikan dengan "
"menggunakan variabel ``swift_*_init_config_overrides`` yang menggunakan "
"tugas ``config_template`` untuk mengubah default templat."

msgid ""
"For the ``os_trove`` role, the systemd unit ``TimeoutSec`` value which "
"controls the time between sending a SIGTERM signal and a SIGKILL signal when "
"stopping or restarting the service has been reduced from 300 seconds to 120 "
"seconds. This provides 2 minutes for long-lived sessions to drain while "
"preventing new ones from starting before a restart or a stop. The "
"``RestartSec`` value which controls the time between the service stop and "
"start when restarting has been reduced from 150 seconds to 2 seconds to make "
"the restart happen faster. These values can be adjusted by using the "
"``trove_*_init_config_overrides`` variables which use the "
"``config_template`` task to change template defaults."
msgstr ""
"Untuk peran ``os_trove``, nilai unit sistemd ``TimeoutSec`` yang mengontrol "
"waktu antara pengiriman sinyal SIGTERM dan sinyal SIGKILL saat menghentikan "
"atau memulai kembali layanan telah berkurang dari 300 detik menjadi 120 "
"detik. Ini memberikan waktu 2 menit untuk sesi long-lived untuk dikeringkan "
"sekaligus mencegah yang baru dimulai sebelum restart atau berhenti. Nilai "
"``RestartSec`` yang mengontrol waktu antara berhenti layanan dan mulai "
"ketika memulai ulang telah berkurang dari 150 detik menjadi 2 detik untuk "
"membuat restart terjadi lebih cepat. Nilai ini dapat disesuaikan dengan "
"menggunakan variabel ``trove_*_init_config_overrides`` yang menggunakan "
"tugas ``config_template`` untuk mengubah default templat."

msgid "Fork the ``openstack/openstack-ansible-os_neutron`` git repository."
msgstr "Fork repositori git  ``openstack/openstack-ansible-os_neutron``."

msgid "Fork the ``openstack/openstack-ansible-repo_build`` git repository."
msgstr "Fork repositori git  ``openstack/openstack-ansible-repo_build``."

msgid "Fork the ``openstack/openstack-ansible`` git repository."
msgstr "Fork repositori git `` openstack / openstack-ansible``."

msgid ""
"From 15.1.16 onwards, these values are set as defaults and will be updated "
"from time to time after verifying that the new versions work. As such, "
"setting these overrides is not required for 15.1.16 onwards."
msgstr ""
"Dari 15.1.16 dan seterusnya, nilai-nilai ini ditetapkan sebagai default dan "
"akan diperbarui dari waktu ke waktu setelah memverifikasi bahwa versi baru "
"berfungsi. Dengan demikian, pengaturan override ini tidak diperlukan untuk "
"15.1.16 dan seterusnya."

msgid ""
"From 16.0.8 onwards, these values are set as defaults and will be updated "
"from time to time after verifying that the new versions work. As such, "
"setting these overrides is not required for 16.0.8 onwards."
msgstr ""
"Dari 16.0.8 dan selanjutnya, nilai-nilai ini ditetapkan sebagai default dan "
"akan diperbarui dari waktu ke waktu setelah memverifikasi bahwa versi baru "
"berfungsi. Dengan demikian, pengaturan override ini tidak diperlukan untuk "
"16.0.8 dan seterusnya."

msgid ""
"From now on, a deployer can override any group_var in userspace, by creating "
"a folder ``/etc/openstack_deploy/group_vars/``. This folder has precedence "
"over OpenStack-Ansible default group_vars, and the merge behavior is similar "
"to Ansible merge behavior. The group_vars folder precedence can still be "
"changed with the GROUP_VARS_PATH. Same applies for host vars."
msgstr ""
"Mulai sekarang, deployer dapat menimpa group_var apa pun di userspace, "
"dengan membuat folder ``/etc/openstack_deploy/group_vars/``. Folder ini "
"lebih diutamakan daripada OpenStack-Ansible default group_vars, dan perilaku "
"gabungan mirip dengan perilaku gabungan Ansible. Diutamakan folder "
"group_vars masih dapat diubah dengan GROUP_VARS_PATH. Hal yang sama berlaku "
"untuk host vars."

msgid ""
"From now on, external repo management (in use for RDO/UCA for example) will "
"be done inside the pip-install role, not in the repo_build role."
msgstr ""
"Mulai sekarang, manajemen repo eksternal (digunakan untuk RDO/UCA misalnya) "
"akan dilakukan di dalam peran pip-install, bukan dalam peran repo_build."

msgid ""
"Functionality to support Ubuntu Trusty (14.04) has been removed from the "
"code base."
msgstr ""
"Fungsi untuk mendukung Ubuntu Trusty (14.04) telah dihapus dari basis kode."

msgid ""
"Galera healthcheck has been improved, and relies on an xinetd service. By "
"default, the service is unaccessible (filtered with the no_access "
"directive). You can override the directive by setting any xinetd valid value "
"to ``galera_monitoring_allowed_source``."
msgstr ""
"Galera healthcheck telah ditingkatkan, dan bergantung pada layanan xinetd. "
"Secara default, layanan tidak dapat diakses (difilter dengan arahan "
"no_access). Anda dapat mengganti arahan dengan mengatur nilai xinetd yang "
"valid ke ``galera_monitoring_allowed_source``."

msgid ""
"Generating and validating checksums for all files installed by packages is "
"now disabled by default. The check causes delays in playbook runs and it can "
"consume a significant amount of CPU and I/O resources. Deployers can re-"
"enable the check by setting ``security_check_package_checksums`` to ``yes``."
msgstr ""
"Membuat dan memvalidasi checksum untuk semua file yang diinstal oleh paket "
"sekarang dinonaktifkan secara default. Pemeriksaan menyebabkan keterlambatan "
"dalam menjalankan playbook dan dapat mengkonsumsi sejumlah besar sumber daya "
"CPU and I/O. Deployer dapat mengaktifkan kembali pemeriksaan dengan mengatur "
"``security_check_package_checksums`` ke ``yes``."

msgid ""
"Generation of records for `/etc/hosts` is now made with blockinfile ansible "
"module. During upgrade you will have records doubled in yours `/etc/hosts` "
"as we don't drop previously created records for safety reasons if "
"`openstack_host_manage_hosts_file` is set to true."
msgstr ""
"Pembuatan catatan untuk `/etc/hosts` sekarang dibuat dengan modul "
"blockinfile ansible. Selama upgrade, Anda akan memiliki catatan dua kali "
"lipat di milik Anda `/etc/hosts` karena kami tidak menjatuhkan catatan yang "
"dibuat sebelumnya untuk alasan keamanan "
"jika`openstack_host_manage_hosts_file` disetel ke true."

msgid ""
"Get ceph keyrings from files, if variable``ceph_keyrings_dir`` is defined "
"the keyrings will be extracted from files. All files in the directory must "
"have ``.keyring`` extention and be named with its corresponding "
"``ceph_client`` name. For example, if ``cinder_ceph_client`` is ``cinder`` "
"the cinder keyring file must be named ``cinder.keyring``. Each file must "
"contain username and the key and nothing more, below an example for cinder."
"keyring content."
msgstr ""
"Dapatkan key ceph dari file, jika variabel``ceph_keyrings_dir`` "
"didefinisikan, keyrings akan diekstraksi dari file. Semua file dalam "
"direktori harus memiliki ekstensi ``.keyring`` dan dinamai dengan nama "
"``ceph_client`` yang sesuai. Sebagai contoh, jika ``cinder_ceph_client`` "
"adalah `` cinder`` file keyring cinder harus dinamai `` cinder.keyring``. "
"Setiap file harus mengandung nama pengguna dan kunci dan tidak lebih, di "
"bawah contoh untuk konten cinder.keyring."

msgid ""
"Glance containers will be rebooted to add the glance cache bind mount if "
"glance_default_store is set to file and nfs is not in use."
msgstr ""
"Glance container akan di-boot ulang untuk menambahkan glance cache mengikat "
"mount direktorinya jika glance_default_store diatur ke file dan nfs tidak "
"digunakan."

msgid ""
"Glance containers will now bind mount the default glance cache directory "
"from the host when glance_default_store is set to file and nfs is not in "
"use.  With this change, the glance file cache size is no longer restricted "
"to the size of the container file system."
msgstr ""
"Glance container sekarang akan mengikat mount direktori cache glance default "
"dari host ketika glance_default_store diatur ke file dan nfs tidak "
"digunakan. Dengan perubahan ini, ukuran cache file glance tidak lagi "
"terbatas pada ukuran sistem file kontainer."

msgid "Glance registry service has been finally removed"
msgstr "Layanan pendaftaran Glance akhirnya telah dihapus"

msgid ""
"Gnocchi is available for deploy as a metrics storage service. At this time "
"it does not integrate with Aodh or Ceilometer. To deploy Aodh or Ceilometer "
"to use Gnocchi as a storage / query API, each must be configured "
"appropriately with the use of overrides as described in the configuration "
"guides for each of these services."
msgstr ""
"Gnocchi tersedia untuk digunakan sebagai layanan penyimpanan metrik. Pada "
"saat ini tidak terintegrasi dengan Aodh atau Ceilometer. Untuk menerapkan "
"Aodh atau Ceilometer untuk menggunakan Gnocchi sebagai storage/query API, "
"masing-masing harus dikonfigurasikan dengan tepat dengan menggunakan "
"override seperti yang dijelaskan dalam panduan konfigurasi untuk masing-"
"masing layanan ini."

msgid "Gnocchi is now used as the default publisher."
msgstr "Gnocchi sekarang digunakan sebagai penerbit default."

msgid ""
"Gnocchi migrated from usage of Apache mod_wsgi or native daemon to uWSGI "
"daemon. This means, that some variables are not available and has no effect "
"anymore, specifically * `gnocchi_use_mod_wsgi` * `gnocchi_apache_*` * "
"`gnocchi_ssl*` (except `gnocchi_ssl_external` - it's still in place) * "
"`gnocchi_user_ssl_*`"
msgstr ""
"Gnocchi bermigrasi dari penggunaan Apache mod_wsgi atau daemon asli ke "
"daWSGI daemon. Ini berarti, bahwa beberapa variabel tidak tersedia dan tidak "
"berpengaruh lagi, khususnya * `gnocchi_use_mod_wsgi` * `gnocchi_apache_*` * "
"`gnocchi_ssl*` (except `gnocchi_ssl_external` - it's still in place) * "
"`gnocchi_user_ssl_*`"

msgid ""
"Gnocchi service endpoint variables were not named correctly. Renamed "
"variables to be consistent with other roles."
msgstr ""
"Variabel endpoint layanan Gnocchi tidak diberi nama dengan benar. Mengganti "
"nama (renamed) variabel agar konsisten dengan peran lain."

msgid ""
"HAProxy services that use backend nodes that are not in the Ansible "
"inventory can now be specified manually by setting ``haproxy_backend_nodes`` "
"to a list of ``name`` and ``ip_addr`` settings."
msgstr ""
"Layanan HAProxy yang menggunakan node backend yang tidak ada dalam "
"inventaris yang dimungkinkan sekarang dapat ditentukan secara manual dengan "
"mengatur ``haproxy_backend_nodes`` ke daftar pengaturan ``name`` dan "
"``ip_addr``."

msgid ""
"Haproxy has a new backend to support using the repo server nodes as a git "
"server. The new backend is called \"repo_git\" and uses port \"9418\". "
"Default ACLs have been created to lock down the port's availability to only "
"internal networks originating from an RFC1918 address."
msgstr ""
"Haproxy memiliki backend baru untuk didukung menggunakan node server repo "
"sebagai server git. Backend baru disebut \"repo_git\" dan menggunakan port "
"\"9418\". ACL default telah dibuat untuk mengunci ketersediaan port hanya "
"untuk jaringan internal yang berasal dari alamat RFC1918."

msgid ""
"Haproxy has a new backend to support using the repo server nodes as a "
"package manager cache. The new backend is called \"repo_cache\" and uses "
"port \"3142\" and a single active node. All other nodes within the pool are "
"backups and will be promoted if the active node goes down. Default ACLs have "
"been created to lock down the port's availability to only internal networks "
"originating from an RFC1918 address."
msgstr ""
"Haproxy memiliki backend baru untuk didukung menggunakan node server repo "
"sebagai cache manajer paket. Backend baru disebut \"repo_cache\" dan "
"menggunakan port \"3142\" dan satu node aktif. Semua node lain di dalam "
"kumpulan adalah cadangan dan akan dipromosikan jika node aktif turun. ACL "
"default telah dibuat untuk mengunci ketersediaan port hanya untuk jaringan "
"internal yang berasal dari alamat RFC1918."

msgid ""
"Haproxy-server role allows to set up tunable parameters. For doing that it "
"is necessary to set up a dictionary of options in the config files, "
"mentioning those which have to be changed (defaults for the remaining ones "
"are programmed in the template). Also \"maxconn\" global option made to be "
"tunable."
msgstr ""
"Peran Haproxy-server memungkinkan untuk mengatur parameter yang bisa "
"disetel. Untuk melakukan itu perlu mengatur kamus opsi dalam file "
"konfigurasi, menyebutkan yang harus diubah (default untuk parameter lainnya "
"diprogram dalam templat). Juga opsi global \"maxconn\" dibuat agar bisa "
"ditala (tunable)."

msgid ""
"Horizon deployment now supports an operator provided customization module "
"which can be configured using the ``horizon_customization_module`` variable. "
"Please see `the Horizon documentation <http://docs.openstack.org/developer/"
"openstack-ansible/mitaka/install-guide/configure-horizon.html>`_ for more "
"information."
msgstr ""
"Deployment Horizon sekarang mendukung modul kustomisasi yang disediakan "
"operator yang dapat dikonfigurasi menggunakan variabel "
"``horizon_customization_module``. Silakan lihat  `the Horizon documentation "
"<http://docs.openstack.org/developer/openstack-ansible/mitaka/install-guide/"
"configure-horizon.html>` _ untuk informasi lebih lanjut."

msgid ""
"Horizon deployments were broken due to an incorrect hostname setting being "
"placed in the apache ServerName configuration. This caused Horizon startup "
"failure any time debug was disabled."
msgstr ""
"Deployment Horizon rusak karena pengaturan nama host yang salah ditempatkan "
"di konfigurasi ServerName apache. Ini menyebabkan kegagalan startup Horizon "
"setiap kali debug dinonaktifkan."

msgid ""
"Horizon disables password autocompletion in the browser by default, but "
"deployers can now enable autocompletion by setting "
"``horizon_enable_password_autocomplete`` to ``True``."
msgstr ""
"Horizon menonaktifkan pelengkapan otomatis kata sandi di browser secara "
"default, tetapi deployer sekarang dapat mengaktifkan pelengkapan otomatis "
"dengan mengatur ``horizon_enable_password_autocomplete`` ke ``True``."

msgid ""
"Horizon has, since OSA's inception, been deployed with HTTPS access enabled, "
"and has had no way to turn it off. Some use-cases may want to access via "
"HTTP instead, so this patch enables the following."
msgstr ""
"Horizon, sejak awal OSA, telah dikerahkan dengan akses HTTPS diaktifkan, dan "
"tidak memiliki cara untuk mematikannya. Beberapa kasus penggunaan mungkin "
"ingin diakses melalui HTTP, jadi patch ini memungkinkan yang berikut ini."

msgid ""
"Horizon now has a boolean variable named ``horizon_enable_ha_router`` to "
"enable Neutron HA router management."
msgstr ""
"Horizon sekarang memiliki variabel boolean bernama "
"``horizon_enable_ha_router`` untuk mengaktifkan manajemen router HA Neutron."

msgid ""
"Horizon now has the ability to set arbitrary configuration options using "
"global option ``horizon_config_overrides`` in YAML format. The overrides "
"follow the same pattern found within the other OpenStack service overrides. "
"`General documentation on overrides can be found here <http://docs.openstack."
"org/developer/openstack-ansible/install-guide/configure-openstack."
"html#overriding-openstack-configuration-defaults>`_."
msgstr ""
"Horizon sekarang memiliki kemampuan untuk mengatur opsi konfigurasi acak "
"menggunakan opsi global ``horizon_config_overrides`` dalam format YAML. "
"Override mengikuti pola yang sama dengan yang ditemukan pada override "
"layanan OpenStack lainnya. `General documentation on overrides can be found "
"here <http://docs.openstack.org/developer/openstack-ansible/install-guide/"
"configure-openstack.html#overriding-openstack-configuration-defaults>` _."

msgid ""
"Horizon's IPv6 support is now configurable with Ansible variables. Deployers "
"can enable IPv6 support in Horizon by setting the following variable:"
msgstr ""
"Dukungan Horizon IPv6 sekarang dapat dikonfigurasi dengan variabel Ansible. "
"Deployer dapat mengaktifkan dukungan IPv6 di Horizon dengan menetapkan "
"variabel berikut:"

msgid ""
"Horizon's IPv6 support is now enabled by default. This allows users to "
"manage subnets with IPv6 addresses within the Horizon interface. Deployers "
"can disable IPv6 support in Horizon by setting the following variable:"
msgstr ""
"Dukungan Horizon IPv6 sekarang diaktifkan secara default. Ini memungkinkan "
"pengguna untuk mengelola subnet dengan alamat IPv6 dalam antarmuka Horizon. "
"Deployer dapat menonaktifkan dukungan IPv6 di Horizon dengan mengatur "
"variabel berikut:"

msgid ""
"Host security hardening is now applied by default using the ``openstack-"
"ansible-security`` role. Developers can opt out by setting the "
"``apply_security_hardening`` Ansible variable to ``false``. For more "
"information about the role and the changes it makes, refer to the `openstack-"
"ansible-security documentation <http://docs.openstack.org/developer/"
"openstack-ansible-security/>`_."
msgstr ""
"Pengerasan keamanan host sekarang diterapkan secara default menggunakan "
"peran ``openstack-ansible-security``. Pengembang dapat memilih keluar dengan "
"mengatur ``apply_security_hardening`` Variabel yang mungkin ke ``false``. "
"Untuk informasi lebih lanjut tentang peran dan perubahan yang dibuatnya, "
"lihat `openstack-ansible-security documentation <http://docs.openstack.org/"
"developer/openstack-ansible-security/>`_."

msgid ""
"Hosts running LXC on Ubuntu 14.04 will now need to enable the \"trusty-"
"backports\" repository. The backports repo on Ubuntu 14.04 is now required "
"to ensure LXC is updated to the latest stable version."
msgstr ""
"Host yang menjalankan LXC di Ubuntu 14.04 sekarang harus mengaktifkan "
"repositori \"trusty-backports\". Repo backports di Ubuntu 14.04 sekarang "
"diperlukan untuk memastikan LXC diperbarui ke versi stabil terbaru."

msgid ""
"IPv6 support has been added for the LXC bridge network. This can be "
"configured using ``lxc_net6_address``, ``lxc_net6_netmask``, and "
"``lxc_net6_nat``."
msgstr ""
"Dukungan IPv6 telah ditambahkan untuk jaringan jembatan LXC. Ini dapat "
"dikonfigurasi menggunakan `` lxc_net6_address``, `` lxc_net6_netmask``, dan "
"`` lxc_net6_nat``."

msgid ""
"If HAProxy is used as the loadbalancer for a deployment it will generate a "
"self-signed certificate by default. If HAProxy is NOT used, an SSL "
"certificate should be installed on the external loadbalancer. The "
"installation of an SSL certificate on an external load balancer is not "
"covered by the deployment tooling."
msgstr ""
"Jika HAProxy digunakan sebagai loadbalancer untuk penempatan, HAProxy akan "
"menghasilkan sertifikat yang ditandatangani sendiri secara default. Jika "
"HAProxy TIDAK digunakan, sertifikat SSL harus dipasang pada loadbalancer "
"eksternal. Pemasangan sertifikat SSL pada penyeimbang beban eksternal tidak "
"dicakup oleh perkakas deployment."

msgid ""
"If Horizon dashboard of OSA installation has a public FQDN, is it now "
"possible to use LetsEncrypt certification service. Certificate will be "
"generated within HAProxy installation and a cron entry to renew the "
"certificate daily will be setup. Note that there is no certificate "
"distribution implementation at this time, so this will only work for a "
"single haproxy-server environment."
msgstr ""
"Jika Horizon dashboard instalasi OSA memiliki FQDN publik, apakah sekarang "
"mungkin untuk menggunakan layanan sertifikasi LetsEncrypt. Sertifikat akan "
"dihasilkan dalam instalasi HAProxy dan entri cron untuk memperbarui "
"sertifikat setiap hari akan diatur. Perhatikan bahwa tidak ada implementasi "
"distribusi sertifikat saat ini, jadi ini hanya akan berfungsi untuk "
"lingkungan server haproxy tunggal."

msgid ""
"If defined in applicable host or group vars the variable "
"``container_extra_networks`` will be merged with the existing "
"``container_networks`` from the dynamic inventory. This allows a deployer to "
"specify special interfaces which may be unique to an indivdual container. An "
"example use for this feature would be applying known fixed IP addresses to "
"public interfaces on BIND servers for designate."
msgstr ""
"Jika didefinisikan dalam host atau grup vars yang berlaku, variabel "
"``container_extra_networks`` akan digabungkan dengan ``container_networks`` "
"yang ada dari inventaris dinamis. Ini memungkinkan penyebar untuk menentukan "
"antarmuka khusus yang mungkin unik untuk container individual. Contoh "
"penggunaan untuk fitur ini adalah menerapkan alamat IP tetap yang dikenal ke "
"antarmuka publik pada server BIND yang ditunjuk."

msgid ""
"If newton is still in use and a new build is executed, the repo-build "
"process will fail due to a new PBR library release which was issued after "
"newton was declared end-of-life (EOL). This issue will show up if gnocchi is "
"being used in the environment and may also show up as a venv build failure "
"for other services. This issue can be resolved either by upgrading the "
"environment to a recent OpenStack-Ansible Ocata release, or by doing the "
"following."
msgstr ""
"Jika newton masih digunakan dan build baru dieksekusi, proses repo-build "
"akan gagal karena rilis perpustakaan PBR baru yang dikeluarkan setelah "
"newton dinyatakan sebagai end-of-life (EOL). Masalah ini akan muncul jika "
"gnocchi digunakan di lingkungan dan mungkin juga muncul sebagai kegagalan "
"pembangunan untuk layanan lain. Masalah ini dapat diatasi dengan "
"memutakhirkan lingkungan ke rilis terbaru OpenStack-Ansible Ocata, atau "
"dengan melakukan hal berikut."

msgid ""
"If the `galera_server` role is deployed on a bare metal host, the MariaDB "
"default is maintained (`PrivateDevices=true`). If the `galera_server` role "
"is deployed within a container, the `PrivateDevices` configuration is set to "
"`true` to work around a systemd bug with a bind mounted `/dev/ptmx`."
msgstr ""
"Jika peran `galera_server` digunakan pada bare metal host, standar MariaDB "
"dipertahankan (`PrivateDevices = true`). Jika peran `galera_server` "
"dikerahkan dalam sebuah container, konfigurasi `PrivateDevices` diatur ke "
"`true` untuk mengatasi bug systemd dengan bind di-mount `/dev/ptmx`."

msgid ""
"If the `memcached_server` role is deployed on a bare metal host, the default "
"is maintained (`PrivateDevices=true`). If the role is deployed within a "
"container, the `PrivateDevices` configuration is set to `true` to work "
"around a systemd bug with a bind mounted `/dev/ptmx`."
msgstr ""
"Jika peran `memcached_server` digunakan pada bare metal host, standarnya "
"dipertahankan (`PrivateDevices = true`). Jika peran ditempatkan dalam "
"container, konfigurasi `PrivateDevices` diatur ke `true` untuk mengatasi bug "
"systemd dengan bind di-mount `/dev/ptmx`."

msgid ""
"If the cinder backup service is enabled with "
"``cinder_service_backup_program_enabled: True``, then heat will be "
"configured to use the cinder backup service. The "
"``heat_cinder_backups_enabled`` variable will automatically be set to "
"``True``."
msgstr ""
"Jika layanan pencadangan cinder diaktifkan dengan "
"``cinder_service_backup_program_enabled: True``, maka heat akan "
"dikonfigurasikan untuk menggunakan layanan pencadangan cinder. Variabel "
"``heat_cinder_backups_enabled`` akan secara otomatis diatur ke ``True``."

msgid ""
"If the protocol of either the keystone admin or internal endpoints is "
"'https' and SSL is being terminated at a load balancer, tasks which verify "
"that services are responsive and perform the initial service setup through "
"through the keystone hosts' web server ports may fail."
msgstr ""
"Jika protokol admin keystone atau endpoint internal adalah 'https' dan SSL "
"dihentikan di load balancer, tugas yang memverifikasi bahwa layanan "
"responsif dan melakukan pengaturan layanan awal melalui port server web host "
"keystone mungkin gagal."

msgid ""
"If there are swift hosts in the environment, then the value for "
"``cinder_service_backup_program_enabled`` will automatically be set to "
"``True``. This negates the need to set this variable in ``user_variables."
"yml``, but the value may still be overridden at the deployer discretion."
msgstr ""
"Jika ada swift host di lingkungan, maka nilai untuk "
"``cinder_service_backup_program_enabled`` akan secara otomatis diatur ke "
"``True``. Ini meniadakan kebutuhan untuk mengatur variabel ini dalam "
"``user_variables.yml``, tetapi nilainya mungkin masih akan ditimpa atas "
"kebijakan deployer."

msgid ""
"If there are swift hosts in the environment, then the value for "
"``glance_default_store`` will automatically be set to ``swift``. This "
"negates the need to set this variable in ``user_variables.yml``, but the "
"value may still be overridden at the deployer discretion."
msgstr ""
"Jika ada swift host di lingkungan, maka nilai untuk ``glance_default_store`` "
"akan secara otomatis diatur ke ``swift``. Ini meniadakan kebutuhan untuk "
"mengatur variabel ini dalam ``user_variables.yml``, tetapi nilainya mungkin "
"masih akan ditimpa atas kebijakan deployer."

msgid ""
"If you do not make this change, the Cinder backup service will refuse to "
"start properly."
msgstr ""
"Jika Anda tidak melakukan perubahan ini, layanan cadangan Cinder akan "
"menolak untuk memulai dengan benar."

msgid ""
"If you had your own keepalived configuration file, please rename and move it "
"to the openstack-ansible user space, for example by moving it to ```/etc/"
"openstack_deploy/keepalived/keepalived.yml```. Our haproxy playbook does not "
"load an external variable files anymore. The keepalived variable override "
"system has been standardised to the same method used elsewhere."
msgstr ""
"Jika Anda memiliki file konfigurasi keepalived Anda sendiri, silakan ganti "
"nama dan pindahkan ke ruang pengguna openstack-ansible, misalnya dengan "
"memindahkannya ke ```/etc/openstack_deploy/keepalived/keepalived.yml```. "
"Playbook haproxy kami tidak memuat file variabel eksternal lagi. Sistem "
"penggantian variabel keepalived telah distandarisasi untuk metode yang sama "
"yang digunakan di tempat lain."

msgid ""
"If you have overriden your ``openstack_host_specific_kernel_modules``, "
"please remove its group matching, and move that override directly to the "
"appropriate group."
msgstr ""
"Jika Anda mengganti ``openstack_host_specific_kernel_modules`` Anda, harap "
"hapus pencocokan grupnya, dan pindahkan override itu langsung ke grup yang "
"sesuai."

msgid ""
"If your configuration previously set the ``libvirt/cpu_model`` and/or "
"``libvirt/cpu_model_extra_flags`` variables in a "
"``nova_nova_conf_overrides`` dictionary, you should consider moving those to "
"``nova_cpu_model`` and ``nova_cpu_model_extra_flags`` in the appropriate "
"entry (normally ``kvm``) in the ``nova_virt_types`` dictionary."
msgstr ""
"Jika konfigurasi Anda sebelumnya mengatur variabel ``libvirt / cpu_model`` "
"dan/atau `libvirt/cpu_model_extra_flags``` dalam kamus "
"``nova_nova_conf_overrides``, Anda harus mempertimbangkan untuk "
"memindahkannya ke ``nova_cpu_model`` dan "
"``nova_cpu_model_model_model_model_teks_paket_model_flags`` dalam entri yang "
"sesuai (biasanya ``kvm``) dalam kamus ``nova_virt_types``."

msgid ""
"Implemented support for Ubuntu 16.04 Xenial.  percona-xtrabackup packages "
"will be installed from distro repositories, instead of upstream percona "
"repositories due to lack of available packages upstream at the time of "
"implementing this feature."
msgstr ""
"Dukungan yang diimplementasikan untuk Ubuntu 16.04 Xenial.  Paket percona-"
"xtrabackup akan diinstal dari repositori distro, bukan repositori hulu "
"percona karena kurangnya paket yang tersedia di hulu pada saat menerapkan "
"fitur ini."

msgid ""
"Implements SSL connection ability to MySQL. ``galera_use_ssl`` option has to "
"be set to ``true`` (default), in this case playbooks create self-signed SSL "
"bundle and sets up MySQL configs to use it or distributes user-provided "
"bundle throughout Galera nodes."
msgstr ""
"Menerapkan kemampuan koneksi SSL ke MySQL. Opsi ``galera_use_ssl`` harus "
"disetel ke ``true`` (default), dalam hal ini playbook membuat bundel SSL "
"yang ditandatangani sendiri dan mengatur konfigurasi MySQL untuk "
"menggunakannya atau mendistribusikan bundel yang disediakan pengguna di "
"seluruh node Galera."

msgid ""
"In OSA deployments prior to Queens, if ``repo_git_cache_dir`` was set to a "
"folder which existed on a repo container host then that folder would be "
"symlinked to the repo container bind mount instead of synchronising its "
"contents to the repo container. This functionality is deprecated in Queens "
"and will be removed in Rocky. The ability to make use of the git cache still "
"exists, but the folder contents will be synchronised from the deploy host to "
"the repo container. If you have made use of the symlink functionality "
"previously, please move the contents to a standard folder and remove the "
"symlink."
msgstr ""
"Dalam deployment OSA sebelum Queens, jika ``repo_git_cache_dir`` disetel ke "
"folder yang ada pada repo container host maka folder itu akan disinkronkan "
"ke repo container bind mount daripada menyinkronkan isinya ke repo "
"container. Fungsi ini sudah usang di Queens dan akan dihapus di Rocky. "
"Kemampuan untuk menggunakan cache git masih ada, tetapi konten folder akan "
"disinkronkan dari host penyebaran ke repo container.  Jika Anda telah "
"menggunakan fungsionalitas symlink sebelumnya, silakan pindahkan konten ke "
"folder standar dan hapus symlink."

msgid ""
"In Stein, Cinder stopped supporting configuring backup drivers without the "
"full class path.  This means that you must now use the following values for "
"``cinder_service_backup_driver``."
msgstr ""
"Di Stein, Cinder berhenti mendukung konfigurasi driver cadangan tanpa full "
"class path.  Ini berarti bahwa Anda sekarang harus menggunakan nilai berikut "
"untuk ``cinder_service_backup_driver``."

msgid ""
"In Ubuntu the ``dnsmasq`` package actually includes init scripts and service "
"configuration which conflict with LXC and are best not included. The actual "
"dependent package is ``dnsmasq-base``. The package list has been adjusted "
"and a task added to remove the ``dnsmasq`` package and purge the related "
"configuration files from all LXC hosts."
msgstr ""
"Di Ubuntu paket ``dnsmasq`` sebenarnya termasuk skrip init dan konfigurasi "
"layanan yang bertentangan dengan LXC dan yang terbaik tidak termasuk. Paket "
"dependen aktual adalah ``dnsmasq-base``. Daftar paket telah disesuaikan dan "
"tugas ditambahkan untuk menghapus paket ``dnsmasq`` dan membersihkan file "
"konfigurasi terkait dari semua host LXC."

msgid ""
"In addition, this should speed up playbook runs since ``yum`` can check a "
"locally-hosted repository instead of a remote repository with availability "
"and performance challenges."
msgstr ""
"Selain itu, ini harus mempercepat playbook berjalan karena ``yum`` dapat "
"memeriksa repositori yang di-host secara lokal daripada repositori jarak "
"jauh dengan ketersediaan dan tantangan kinerja."

msgid ""
"In https://review.openstack.org/582633 an adjustment was made to the "
"``openstack-ansible`` wrapper which mistakenly changed the intended "
"behaviour. The wrapper is only meant to include the extra-vars and invoke "
"the inventory if ``ansible-playbook`` was executed from inside the "
"``openstack-ansible`` repository clone (typically ``/opt/openstack-"
"ansible``), but the change made the path irrelevant. This has now been fixed "
"- ``ansible-playbook`` and ``ansible`` will only invoke the inventory and "
"include extra vars if it is invoked from inside the git clone path."
msgstr ""
"Di https://review.openstack.org/582633 penyesuaian dibuat ke wrapper "
"``openstack-ansible`` yang secara keliru mengubah perilaku yang dimaksud. "
"Wrapper hanya dimaksudkan untuk memasukkan extra-vars dan memanggil "
"inventaris jika ``ansible-playbook`` dijalankan dari dalam klon repositori "
"``openstack-ansible`` (biasanya ``/opt/openstack-ansible``)) , tetapi "
"perubahan itu membuat jalan itu tidak relevan. Ini sekarang telah diperbaiki "
"- ``ansible-playbook`` dan ``ansible`` hanya akan memanggil inventaris dan "
"memasukkan vars tambahan jika itu dipanggil dari dalam git clone path."

msgid ""
"In order to ensure that the appropriate data is delivered to requesters from "
"the repo servers, the slave repo_server web servers are taken offline during "
"the synchronisation process. This ensures that the right data is always "
"delivered to the requesters through the load balancer."
msgstr ""
"Untuk memastikan bahwa data yang sesuai dikirimkan kepada pemohon dari "
"server repo, server web repo_server slave diambil offline selama proses "
"sinkronisasi. Ini memastikan bahwa data yang tepat selalu dikirimkan ke "
"pemohon melalui load balancer."

msgid ""
"In order to make use of the latest stable keepalived version, the variable "
"``keepalived_use_latest_stable`` must be set to ``True``"
msgstr ""
"Untuk menggunakan versi stabil keepalived terbaru, variabel "
"``keepalived_use_latest_stable`` harus disetel ke ``True``"

msgid ""
"In order to prevent further issues with a libvirt and python-libvirt version "
"mismatch, KVM-based compute nodes will now use the distribution package "
"python library for libvirt. This should resolve the issue seen with pike "
"builds on CentOS 7.5."
msgstr ""
"Untuk mencegah masalah lebih lanjut dengan ketidakcocokan libvirt dan versi "
"python-libvirt, node komputasi berbasis KVM sekarang akan menggunakan paket "
"distribusi python library untuk libvirt. Ini harus menyelesaikan masalah "
"yang terlihat dengan pike build di CentOS 7.5."

msgid ""
"In order to reduce the time taken for fact gathering, the default subset "
"gathered has been reduced to a smaller set than the Ansible default. This "
"may be changed by the deployer by setting the ``ANSIBLE_GATHER_SUBSET`` "
"variable in the bash environment prior to executing any ansible commands."
msgstr ""
"Untuk mengurangi waktu yang dibutuhkan untuk pengumpulan fakta, subset "
"default yang dikumpulkan telah dikurangi menjadi set yang lebih kecil dari "
"default Ansible. Ini dapat diubah oleh deployer dengan mengatur variabel "
"``ANSIBLE_GATHER_SUBSET`` di lingkungan bash sebelum menjalankan perintah "
"ansible."

msgid ""
"In previous releases connections to Horizon originally terminated SSL at the "
"Horizon container. While that is still an option, SSL is now assumed to be "
"terminated at the load balancer. If you wish to terminate SSL at the horizon "
"node change the ``horizon_external_ssl`` option to **false**."
msgstr ""
"Dalam rilis sebelumnya koneksi ke Horizon awalnya dihentikan SSL di "
"kontainer Horizon. Sementara itu masih merupakan opsi, SSL sekarang "
"diasumsikan dihentikan di load balancer. Jika Anda ingin mengakhiri SSL di "
"node horizon, ubah opsi ``horizon_external_ssl`` menjadi **false **."

msgid ""
"In the Ocata release, Trove added support for encrypting the rpc "
"communication between the guest DBaaS instances and the control plane. The "
"default values for ``trove_taskmanager_rpc_encr_key`` and "
"``trove_inst_rpc_key_encr_key`` should be overridden to specify installation "
"specific values."
msgstr ""
"Dalam rilis Ocata, Trove menambahkan dukungan untuk mengenkripsi komunikasi "
"rpc antara instance DBaaS guest dan control plane. Nilai default untuk "
"``trove_taskmanager_rpc_encr_key`` dan ``trove_inst_rpc_key_encr_key`` harus "
"diganti untuk menentukan nilai spesifik instalasi."

msgid ""
"In the ``ceph_client`` role, the only valid values for ``ceph_pkg_source`` "
"are now ``ceph`` and ``distro``. For Ubuntu, the Ubuntu Cloud Archive apt "
"source is already setup by the ``openstack_hosts`` role, so there is no need "
"for it to also be setup by the ``ceph_client`` role."
msgstr ""
"Dalam peran ``ceph_client``, satu-satunya nilai yang valid untuk "
"``ceph_pkg_source`` sekarang menjadi ``ceph`` dan ``distro``. Untuk Ubuntu, "
"sumber apt Ubuntu Cloud Archive sudah diatur oleh peran ``openstack_hosts``, "
"jadi tidak perlu untuk itu juga diatur oleh peran ``ceph_client``."

msgid ""
"In the ``lxc_hosts`` role execution, we make use of the images produced on a "
"daily basis by images.linuxcontainers.org. Recent changes in the way those "
"images are produced have resulted in changes to the default ``/etc/resolve."
"conf`` in that default image. As such, when executing the cache preparation "
"it fails. For all newton queens releases the workaround to get past the "
"error is to add the following to the ``/etc/openstack_deploy/user_variables."
"yml`` file."
msgstr ""
"Dalam eksekusi peran ``lxc_hosts``, kami menggunakan image yang dihasilkan "
"setiap hari oleh images.linuxcontainers.org. Perubahan terbaru dalam cara "
"image itu dihasilkan telah mengakibatkan perubahan ke default ``/etc/resolve."
"conf`` di image default itu. Karena itu, ketika menjalankan persiapan cache "
"gagal. Untuk semua newton queen melepaskan solusinya untuk melewati "
"kesalahan adalah dengan menambahkan berikut ke file  ``/etc/openstack_deploy/"
"user_variables.yml``."

msgid ""
"In the ``lxc_hosts`` role execution, we make use of the images produced on a "
"daily basis by images.linuxcontainers.org. Recent changes in the way those "
"images are produced have resulted in changes to the default ``/etc/resolve."
"conf`` in that default image. As such, when executing the cache preparation "
"it fails. For ocata releases prior to 15.1.21 the workaround to get past the "
"error is to add the following to the ``/etc/openstack_deploy/user_variables."
"yml`` file."
msgstr ""
"Dalam eksekusi peran ``lxc_hosts``, kami menggunakan image yang dihasilkan "
"setiap hari oleh images.linuxcontainers.org. Perubahan terbaru dalam cara "
"image itu dihasilkan telah mengakibatkan perubahan ke default ``/etc/resolve."
"conf`` di image default itu. Karena itu, ketika menjalankan persiapan cache "
"gagal. Untuk rilis ocata sebelum 15.1.21 solusi untuk melewati kesalahan "
"adalah dengan menambahkan yang berikut ke file ``/etc/openstack_deploy/"
"user_variables.yml``."

msgid ""
"In the ``lxc_hosts`` role execution, we make use of the images produced on a "
"daily basis by images.linuxcontainers.org. Recent changes in the way those "
"images are produced have resulted in changes to the default ``/etc/resolve."
"conf`` in that default image. As such, when executing the cache preparation "
"it fails. For pike releases prior to 16.0.13 the workaround to get past the "
"error is to add the following to the ``/etc/openstack_deploy/user_variables."
"yml`` file."
msgstr ""
"Dalam eksekusi peran ``lxc_hosts``, kami menggunakan image yang dihasilkan "
"setiap hari oleh images.linuxcontainers.org. Perubahan terbaru dalam cara "
"image itu dihasilkan telah mengakibatkan perubahan ke default  ``/etc/"
"resolve.conf`` di image default itu. Karena itu, ketika menjalankan "
"persiapan cache gagal. Untuk rilis pike sebelum 16.0.13 solusi untuk "
"melewati kesalahan adalah dengan menambahkan yang berikut ke file ``/etc/"
"openstack_deploy/user_variables.yml``."

msgid ""
"In the ``lxc_hosts`` role execution, we make use of the images produced on a "
"daily basis by images.linuxcontainers.org. Recent changes in the way those "
"images are produced have resulted in changes to the default ``/etc/resolve."
"conf`` in that default image. As such, when executing the cache preparation "
"it fails. For queens releases prior to 17.0.4 the workaround to get past the "
"error is to add the following to the ``/etc/openstack_deploy/user_variables."
"yml`` file."
msgstr ""
"Dalam eksekusi peran ``lxc_hosts``, kami menggunakan image yang dihasilkan "
"setiap hari oleh images.linuxcontainers.org. Perubahan terbaru dalam cara "
"image itu dihasilkan telah mengakibatkan perubahan ke default  ``/etc/"
"resolve.conf`` di image default itu. Karena itu, ketika menjalankan "
"persiapan cache gagal. Untuk rilis ratu sebelum 17.0.4 solusi untuk melewati "
"kesalahan adalah dengan menambahkan berikut ke file ``/etc/openstack_deploy/"
"user_variables.yml``."

msgid ""
"In the ``rsyslog_client`` role, the variable ``rsyslog_client_repos`` has "
"been removed as it is no longer used."
msgstr ""
"Dalam peran ``rsyslog_client``, variabel ``rsyslog_client_repos`` telah "
"dihapus karena tidak lagi digunakan."

msgid ""
"In the latest stable version of keepalived there is a problem with the "
"priority calculation when a deployer has more than five keepalived nodes. "
"The problem causes the whole keepalived cluster to fail to work. To work "
"around this issue it is recommended that deployers limit the number of "
"keepalived nodes to no more than five or that the priority for each node is "
"set as part of the configuration (cf. ``haproxy_keepalived_vars_file`` "
"variable)."
msgstr ""
"Di versi stabil terbaru dari keepalived ada masalah dengan perhitungan "
"prioritas ketika seorang deployer memiliki lebih dari lima node keepalived. "
"Masalahnya menyebabkan seluruh cluster yang disimpan tetap gagal bekerja. "
"Untuk mengatasi masalah ini, disarankan bahwa deployer membatasi jumlah node "
"yang disimpan tidak lebih dari lima atau bahwa prioritas untuk setiap node "
"ditetapkan sebagai bagian dari konfigurasi (cf. "
"``haproxy_keepalived_vars_file`` variable)."

msgid ""
"In the lxc_container_create role, the keys ``preup``, ``postup``, "
"``predown``, and ``postdown`` are now supported in the "
"``container_networks`` dict for Ubuntu systems. This allows operators to "
"configure custom scripts to be run by Ubuntu's ifupdown system when network "
"interface states are changed."
msgstr ""
"Dalam peran lxc_container_create, tombol ``preup``, ``postup``, ``predown``, "
"dan ``postdown`` sekarang didukung dalam ``container_networks`` dict untuk "
"sistem Ubuntu. Ini memungkinkan operator untuk mengkonfigurasi skrip khusus "
"untuk dijalankan oleh sistem ifupdown Ubuntu ketika status antarmuka "
"jaringan diubah."

msgid ""
"Installation of Ansible on the root system, outside of a virtual "
"environment, will no longer be supported."
msgstr ""
"Instalasi Ansible di sistem root, di luar lingkungan virtual, tidak akan "
"lagi didukung."

msgid ""
"Installation of aodh and its dependent pip packages will now only occur "
"within a Python virtual environment. The ``aodh_venv_enabled`` and "
"``aodh_venv_bin`` variables have been removed."
msgstr ""
"Instalasi aodh dan paket pip dependennya sekarang hanya akan terjadi dalam "
"lingkungan virtual Python. Variabel ``aodh_venv_enabled`` dan "
"``aodh_venv_bin`` telah dihapus."

msgid ""
"Installation of ceilometer and its dependent pip packages will now only "
"occur within a Python virtual environment. The ``ceilometer_venv_enabled`` "
"and ``ceilometer_venv_bin`` variables have been removed."
msgstr ""
"Instalasi ceilometer dan paket pip yang tergantung sekarang hanya akan "
"terjadi dalam lingkungan virtual Python. Variabel "
"``ceilometer_venv_enabled`` dan ``ceilometer_venv_bin`` telah dihapus."

msgid ""
"Installation of cinder and its dependent pip packages will now only occur "
"within a Python virtual environment. The ``cinder_venv_enabled`` and "
"``cinder_venv_bin`` variables have been removed."
msgstr ""
"Instalasi cinder dan paket pip yang tergantung sekarang hanya akan terjadi "
"dalam lingkungan virtual Python. Variabel ``cinder_venv_enabled`` dan "
"``cinder_venv_bin`` telah dihapus."

msgid ""
"Installation of cloudkitty and its dependent pip packages will now only "
"occur within a Python virtual environment. The ``cloudkitty_venv_bin`` and "
"``cloudkitty_venv_enabled`` variables have been removed."
msgstr ""
"Instalasi cloudkitty dan paket-paket pip yang tergantung sekarang hanya akan "
"terjadi dalam lingkungan virtual Python. Variabel ``cloudkitty_venv_bin`` "
"dan ``cloudkitty_venv_enabled`` telah dihapus."

msgid ""
"Installation of designate and its dependent pip packages will now only occur "
"within a Python virtual environment. The ``designate_venv_enabled``, "
"``designate_venv_bin``, ``designate_venv_etc_dir`` and "
"``designate_non_venv_etc_dir`` variables have been removed."
msgstr ""
"Instalasi yang ditunjuk dan paket pip yang tergantung sekarang hanya akan "
"terjadi dalam lingkungan virtual Python. Variabel "
"``designate_venv_enabled``, ``designate_venv_bin``, "
"``designate_venv_etc_dir`` dan ``designate_non_venv_etc_dir`` telah dihapus."

msgid ""
"Installation of glance and its dependent pip packages will now only occur "
"within a Python virtual environment. The ``glance_venv_bin``, "
"``glance_venv_enabled``, ``glance_venv_etc_dir``, and "
"``glance_non_venv_etc_dir`` variables have been removed."
msgstr ""
"Instalasi sekilas dan paket pip dependennya sekarang hanya akan terjadi "
"dalam lingkungan virtual Python. Variabel ``glance_venv_bin``, "
"``glance_venv_enabled``, ``glance_venv_etc_dir``, dan "
"``glance_non_venv_etc_dir`` telah dihapus."

msgid ""
"Installation of glance and its dependent pip packages will now only occur "
"within a Python virtual environment. The ``gnocchi_venv_bin``, "
"``gnocchi_venv_enabled``, ``gnocchi_venv_etc_dir``, and "
"``gnocchi_non_venv_etc_dir`` variables have been removed."
msgstr ""
"Instalasi glance dan paket pip dependennya sekarang hanya akan terjadi dalam "
"lingkungan virtual Python. Variabel ``gnocchi_venv_bin``, "
"``gnocchi_venv_enabled``, ``gnocchi_venv_etc_dir``, dan "
"``gnocchi_non_venv_etc_dir`` telah dihapus."

msgid ""
"Installation of heat and its dependent pip packages will now only occur "
"within a Python virtual environment. The ``heat_venv_bin`` and "
"``heat_venv_enabled`` variables have been removed."
msgstr ""
"Instalasi heat dan paket pip yang tergantung sekarang hanya akan terjadi "
"dalam lingkungan virtual Python. Variabel ``heat_venv_bin`` dan "
"``heat_venv_enabled`` telah dihapus."

msgid ""
"Installation of horizon and its dependent pip packages will now only occur "
"within a Python virtual environment. The ``horizon_venv_bin``, "
"``horizon_venv_enabled``, ``horizon_venv_lib_dir``, and "
"``horizon_non_venv_lib_dir`` variables have been removed."
msgstr ""
"Instalasi horizon dan paket pip dependennya sekarang hanya akan terjadi "
"dalam lingkungan virtual Python. Variabel ``horizon_venv_bin``, "
"``horizon_venv_enabled``, ``horizon_venv_lib_dir``, dan "
"``horizon_non_venv_lib_dir`` telah dihapus."

msgid ""
"Installation of ironic and its dependent pip packages will now only occur "
"within a Python virtual environment. The ``ironic_venv_bin`` and "
"``ironic_venv_enabled`` variables have been removed."
msgstr ""
"Instalasi ironic dan paket pip dependennya sekarang hanya akan terjadi dalam "
"lingkungan virtual Python. Variabel ``ironic_venv_bin`` dan "
"``ironic_venv_enabled`` telah dihapus."

msgid ""
"Installation of keystone and its dependent pip packages will now only occur "
"within a Python virtual environment. The ``keystone_venv_enabled`` variable "
"has been removed."
msgstr ""
"Instalasi keystone dan paket pip dependennya sekarang hanya akan terjadi "
"dalam lingkungan virtual Python. Variabel ``keystone_venv_enabled`` telah "
"dihapus."

msgid ""
"Installation of magnum and its dependent pip packages will now only occur "
"within a Python virtual environment. The ``magnum_venv_bin``, "
"``magnum_venv_enabled`` variables have been removed."
msgstr ""
"Instalasi magnum dan paket pip dependennya sekarang hanya akan terjadi dalam "
"lingkungan virtual Python. Variabel ``magnum_venv_bin``, "
"``magnum_venv_enabled`` telah dihapus."

msgid ""
"Installation of neutron and its dependent pip packages will now only occur "
"within a Python virtual environment. The ``neutron_venv_enabled``, "
"``neutron_venv_bin``, ``neutron_non_venv_lib_dir`` and "
"``neutron_venv_lib_dir`` variables have been removed."
msgstr ""
"Instalasi neutron dan paket pip dependennya sekarang hanya akan terjadi "
"dalam lingkungan virtual Python. Variabel ``neutron_venv_enabled``, "
"``neutron_venv_bin``, ``neutron_non_venv_lib_dir`` dan "
"``neutron_venv_lib_dir`` telah dihapus."

msgid ""
"Installation of nova and its dependent pip packages will now only occur "
"within a Python virtual environment. The ``nova_venv_enabled``, "
"``nova_venv_bin`` variables have been removed."
msgstr ""
"Instalasi nova dan paket pip dependennya sekarang hanya akan terjadi dalam "
"lingkungan virtual Python. Variabel ``nova_venv_enabled``, ``nova_venv_bin`` "
"telah dihapus."

msgid ""
"Installation of rally and its dependent pip packages will now only occur "
"within a Python virtual environment. The ``rally_venv_bin``, "
"``rally_venv_enabled`` variables have been removed."
msgstr ""
"Instalasi rally dan paket pip dependennya sekarang hanya akan terjadi dalam "
"lingkungan virtual Python. Variabel ``rally_venv_bin``, "
"``rally_venv_enabled`` telah dihapus."

msgid ""
"Installation of sahara and its dependent pip packages will now only occur "
"within a Python virtual environment. The ``sahara_venv_bin``, "
"``sahara_venv_enabled``, ``sahara_venv_etc_dir``, and "
"``sahara_non_venv_etc_dir`` variables have been removed."
msgstr ""
"Instalasi sahara dan paket pip ketergantungannya sekarang hanya akan terjadi "
"dalam lingkungan virtual Python. Variabel ``sahara_venv_bin``, "
"``sahara_venv_enabled``, ``sahara_venv_etc_dir``, dan variabel "
"``sahara_non_venv_etc_dir`` telah dihapus."

msgid ""
"Installation of swift and its dependent pip packages will now only occur "
"within a Python virtual environment. The ``swift_venv_enabled``, "
"``swift_venv_bin`` variables have been removed."
msgstr ""
"Instalasi swift dan paket pip dependennya sekarang hanya akan terjadi dalam "
"lingkungan virtual Python. Variabel ``swift_venv_enabled``, "
"``swift_venv_bin`` telah dihapus."

msgid ""
"Instead of downloading images to the magnum API servers, the images will now "
"download to the ``magnum_service_setup_host`` to the folder set in "
"``magnum_image_path`` owned by ``magnum_image_path_owner``."
msgstr ""
"Sebagai ganti mengunduh image ke server API magnum, image sekarang akan "
"mengunduh ke ``magnum_service_setup_host`` ke folder yang diatur dalam "
"``magnum_image_path`` yang dimiliki oleh ``magnum_image_path_owner``."

msgid ""
"Introduced option to deploy Keystone behind Nginx. A new variable "
"``keystone_apache_enabled`` is introduced to toggle this behavior.  The "
"default is ``true`` which continues to deploy with Apache. Additional "
"configuration can be delivered to Nginx through the use of the "
"``keystone_nginx_extra_conf`` list variable. Federation features are not "
"supported with this configuration at this time. Use of this option requires "
"``keystone_mod_wsgi_enabled`` to be set to ``false`` which will deploy "
"Keystone under Uwsgi."
msgstr ""
"Opsi yang diperkenalkan untuk menggunakan Keystone di belakang Nginx. "
"Variabel baru ``keystone_apache_enabled`` diperkenalkan untuk mengganti "
"perilaku ini. Standarnya adalah ``true`` yang terus digunakan dengan Apache. "
"Konfigurasi tambahan dapat dikirim ke Nginx melalui penggunaan variabel "
"daftar ``keystone_nginx_extra_conf``. Fitur Federasi tidak didukung dengan "
"konfigurasi ini saat ini. Penggunaan opsi ini memerlukan "
"``keystone_mod_wsgi_enabled`` untuk diatur ke ``false`` yang akan "
"menggunakan Keystone di bawah Uwsgi."

msgid ""
"Introduced option to deploy Keystone under Uwsgi. A new variable "
"``keystone_mod_wsgi_enabled`` is introduced to toggle this behavior. The "
"default is ``true`` which continues to deploy with mod_wsgi for Apache. The "
"ports used by Uwsgi for socket and http connection for both public and admin "
"Keystone services are configurable (see also the ``keystone_uwsgi_ports`` "
"dictionary variable). Other Uwsgi configuration can be overridden by using "
"the ``keystone_uwsgi_ini_overrides`` variable as documented under "
"\"Overriding OpenStack configuration defaults\" in the OpenStack-Ansible "
"Install Guide. Federation features should be considered _experimental_ with "
"this configuration at this time."
msgstr ""
"Opsi yang diperkenalkan untuk menggunakan Keystone di bawah Uwsgi. Variabel "
"baru ``keystone_mod_wsgi_enabled`` diperkenalkan untuk mengganti perilaku "
"ini. Standarnya adalah ``true`` yang terus digunakan dengan mod_wsgi untuk "
"Apache. Port yang digunakan oleh Uwsgi untuk koneksi soket dan http untuk "
"layanan publik dan admin Keystone dapat dikonfigurasi (lihat juga variabel "
"kamus ``keystone_uwsgi_ports``). Konfigurasi Uwsgi lain dapat diganti dengan "
"menggunakan variabel ``keystone_uwsgi_ini_overrides`` seperti yang "
"didokumentasikan dalam \"Overriding OpenStack configuration defaults\" di "
"OpenStack-Ansible Install Guide.  Fitur federasi harus dianggap "
"_eksperimental_ dengan konfigurasi ini saat ini."

msgid ""
"It is commonly considered bad practice to downlaod random images from the "
"Internet expecially the test images the Octavia team provides which could "
"potentially include unpatched operating system packages - so for any "
"production deploy adjust the download url to an artifact storage your "
"organization controls. The system also does not authenticate the image (e.g. "
"with an md5) so should only be used on networks your organization controls."
msgstr ""
"Biasanya dianggap praktik buruk untuk menurunkan image acak dari Internet, "
"terutama image uji yang disediakan oleh tim Octavia yang berpotensi mencakup "
"paket sistem operasi yang tidak ditambal (unpatched) - jadi untuk setiap "
"penyebaran produksi sesuaikan url unduhan ke penyimpanan artefak yang "
"dikendalikan organisasi Anda. Sistem juga tidak mengautentikasi image (misal "
"dengan md5) sehingga hanya boleh digunakan pada jaringan yang dikontrol "
"organisasi Anda."

msgid ""
"It is not possible to override the ceph client credential for nova and "
"cinder with ansible 1.9.4."
msgstr ""
"Tidak mungkin untuk menimpa kredensial klien ceph untuk nova dan cinder "
"dengan ansible 1.9.4."

msgid ""
"It is now possible for deployers to enable or disable the `mysqlcheck` "
"capability. The Boolean option `galera_monitoring_check_enabled` has been "
"added which has a default value of **true**."
msgstr ""
"Sekarang memungkinkan bagi para deployer untuk mengaktifkan atau "
"menonaktifkan kemampuan `mysqlcheck`. Opsi Boolean "
"`galera_monitoring_check_enabled` telah ditambahkan yang memiliki nilai "
"default **true**."

msgid ""
"It is now possible to change the port used by `mysqlcheck`. The integer "
"option `galera_monitoring_check_port` has been added with the default value "
"of **9200**."
msgstr ""
"Sekarang dimungkinkan untuk mengubah port yang digunakan oleh `mysqlcheck`. "
"Opsi integer `galera_monitoring_check_port` telah ditambahkan dengan nilai "
"default **9200 **."

msgid ""
"It is now possible to customise the location of the configuration file "
"source for the All-In-One (AIO) bootstrap process using the "
"``bootstrap_host_aio_config_path`` variable."
msgstr ""
"Sekarang dimungkinkan untuk menyesuaikan lokasi sumber file konfigurasi "
"untuk proses bootstrap All-In-One (AIO) menggunakan variabel "
"``bootstrap_host_aio_config_path``."

msgid ""
"It is now possible to customise the location of the scripts used in the All-"
"In-One (AIO) boostrap process using the ``bootstrap_host_aio_script_path`` "
"variable."
msgstr ""
"Sekarang dimungkinkan untuk menyesuaikan lokasi skrip yang digunakan dalam "
"proses boostrap All-In-One (AIO) menggunakan variabel "
"``bootstrap_host_aio_script_path``."

msgid ""
"It is now possible to customise the name of the ``user_secrets.yml`` file "
"created by the All-In-One (AIO) bootstrap process using the "
"``bootstrap_host_user_secrets_filename`` variable."
msgstr ""
"Sekarang dimungkinkan untuk menyesuaikan nama file ``user_secrets.yml`` yang "
"dibuat oleh proses bootstrap All-In-One (AIO) menggunakan variabel "
"``bootstrap_host_user_secrets_filename``."

msgid ""
"It is now possible to customise the name of the ``user_variables.yml`` file "
"created by the All-In-One (AIO) bootstrap process using the "
"``bootstrap_host_user_variables_filename`` variable."
msgstr ""
"Sekarang mungkin untuk menyesuaikan nama file ``user_variables.yml`` yang "
"dibuat oleh proses bootstrap All-In-One (AIO) menggunakan variabel "
"``bootstrap_host_user_variables_filename``."

msgid ""
"It is now possible to modify the NTP server options in chrony using "
"``security_ntp_server_options``."
msgstr ""
"Sekarang dimungkinkan untuk mengubah opsi server NTP dalam kroni menggunakan "
"``security_ntp_server_options``."

msgid ""
"It is now possible to specify a list of tests for tempest to blacklist when "
"executing using the ``tempest_test_blacklist`` list variable."
msgstr ""
"Sekarang dimungkinkan untuk menentukan daftar tes untuk tempest ke daftar "
"hitam ketika mengeksekusi menggunakan variabel daftar "
"``tempest_test_blacklist``."

msgid ""
"It is now possible to use NFS mountpoints with the role by using the "
"nova_nfs_client variable, which is useful for using NFS for instance data "
"and saves."
msgstr ""
"Sekarang dimungkinkan untuk menggunakan NFS mountpoint dengan peran dengan "
"menggunakan variabel nova nfs_client, yang berguna untuk menggunakan NFS "
"untuk data instance dan menyimpan."

msgid ""
"It is now possible to use the horizon_launch_instance_defaults variable that "
"allows customizing the default values for properties found in the Launch "
"Instance modal, using the LAUNCH_INSTANCE_DEFAULTS config option. See "
"https://docs.openstack.org/developer/horizon/install/settings.html#launch-"
"instance-defaults"
msgstr ""
"Sekarang dimungkinkan untuk menggunakan variabel "
"horizon_launch_instance_defaults yang memungkinkan penyesuaian nilai default "
"untuk properti yang ditemukan dalam modal Instance Launch, menggunakan opsi "
"konfigurasi LAUNCH_INSTANCE_DEFAULTS config. Lihat https://docs.openstack."
"org/developer/horizon/install/settings.html#launch-instance-defaults"

msgid ""
"It is possible that you may need to use the cinder-manage command to migrate "
"volumes to a specific host.  In addition, you will have to remove the old "
"``rbd:volumes`` service which will be stale."
msgstr ""
"Mungkin saja Anda perlu menggunakan perintah cinder-manage untuk memigrasi "
"volume ke host tertentu. Selain itu, Anda harus menghapus layanan ``rbd: "
"volumes`` lama yang akan basi."

msgid ""
"It is possible to configure Glance to allow cross origin requests by "
"specifying the allowed origin address using the "
"``glance_cors_allowed_origin`` variable. By default, this will be the load "
"balancer address."
msgstr ""
"Dimungkinkan untuk mengkonfigurasi Glance untuk mengizinkan permintaan asal "
"silang (cross origin request)  dengan menentukan alamat asal yang diizinkan "
"menggunakan variabel ``glance_cors_allowed_origin``. Secara default, ini "
"akan menjadi alamat penyeimbang beban."

msgid ""
"It is recommended for deployers to clean up the **neutron_agents** "
"container(s) after an upgrade is complete and the cluster has been verified "
"as stable. This can be done by simply disabling the neutron agents running "
"in the **neutron_agent** container(s), re-balancing the agent services "
"targeting the new baremetal agents, deleting the container(s), and finally "
"removing the container(s) from inventory."
msgstr ""
"Direkomendasikan bagi para deployer untuk membersihkan **neutron_agents** "
"container(s)  setelah upgrade selesai dan cluster telah diverifikasi sebagai "
"stabil. Ini dapat dilakukan dengan hanya menonaktifkan agen neutron yang "
"berjalan di ***neutron_agent** container(s), re-balancing layanan agen "
"menargetkan agen baremetal baru, menghapus container, dan akhirnya menghapus "
"container (s) dari persediaan."

msgid ""
"It is recommended that the certificate generation is always reviewed by "
"security professionals since algorithms and key-lengths considered secure "
"change all the time."
msgstr ""
"Direkomendasikan bahwa pembuatan sertifikat selalu ditinjau oleh para "
"profesional keamanan karena algoritma dan panjang kunci dianggap perubahan "
"yang aman sepanjang waktu."

msgid ""
"It's now possible to change the behavior of ``DISALLOW_IFRAME_EMBED`` by "
"defining the variable ``horizon_disallow_iframe_embed`` in the user "
"variables."
msgstr ""
"Sekarang mungkin untuk mengubah perilaku ``DISALLOW_IFRAME_EMBED`` dengan "
"mendefinisikan variabel ``horizon_disallow_iframe_embed`` dalam variabel "
"pengguna."

msgid ""
"It's now possible to disable heat stack password field in horizon. "
"``horizon_enable_heatstack_user_pass`` variable has been added and default "
"to True."
msgstr ""
"Sekarang dimungkinkan untuk menonaktifkan field password heat stack  di "
"horizon. Variabel ``horizon_enable_heatstack_user_pass`` telah ditambahkan "
"dan default ke True."

msgid ""
"KSM configuration is changed to disabled by default on Ubuntu. If you "
"overcommit the RAM on your hypervisor it's a good idea to set "
"``nova_compute_ksm_enabled`` to ``True``."
msgstr ""
"Konfigurasi KSM diubah menjadi dinonaktifkan secara default di Ubuntu. Jika "
"Anda terlalu berkomitmen pada RAM pada hypervisor Anda, sebaiknya atur "
"``nova_compute_ksm_enabled`` menjadi ``True``."

msgid ""
"Keystone can now be configured for multiple LDAP or Active Directory "
"identity back-ends. Configuration of this feature is documented in the "
"`Keystone Configuration <http://docs.openstack.org/developer/openstack-"
"ansible/install-guide/configure-keystone.html>`_ section of the `Install "
"Guide <http://docs.openstack.org/developer/openstack-ansible/install-guide/"
">`_."
msgstr ""
"Keystone sekarang dapat dikonfigurasi untuk beberapa LDAP atau Active "
"Directory identity back-ends. Konfigurasi fitur ini didokumentasikan di "
"bagian `Keystone Configuration <http://docs.openstack.org/developer/"
"openstack-ansible/install-guide/configure-keystone.html>` _ dari `Install "
"Guide <http://docs.openstack.org/developer/openstack-ansible/install-guide/"
">`_."

msgid ""
"Keystone can now be configured for multiple LDAP or Active Directory "
"identity back-ends. Configuration of this feature is documented in the "
"`Keystone Configuration <http://docs.openstack.org/developer/openstack-"
"ansible/mitaka/install-guide/configure-keystone.html>`_ section of the "
"`Install Guide <http://docs.openstack.org/developer/openstack-ansible/mitaka/"
"install-guide/>`_."
msgstr ""
"Keystone sekarang dapat dikonfigurasi untuk beberapa LDAP atau Active "
"Directory identity back-ends. Konfigurasi fitur ini didokumentasikan dalam "
"bagian `Konfigurasi Keystone <http://docs.openstack.org/developer/openstack-"
"ansible/mitaka/install-guide/configure-keystone.html>` _ dari `Install Guide "
"<http://docs.openstack.org/developer/openstack-ansible/mitaka/install-guide/"
">`_."

msgid ""
"Keystone now uses uWSGI exclusively (instead of Apache with mod_wsgi) and "
"has the web server acting as a reverse proxy. The default web server is now "
"set to Nginx instead of Apache, but Apache will automatically used if "
"federation is configured."
msgstr ""
"Keystone sekarang menggunakan uWSGI secara eksklusif (bukan Apache dengan "
"mod_wsgi) dan memiliki server web yang bertindak sebagai proxy terbalik. "
"Server web default sekarang diatur ke Nginx bukan Apache, tetapi Apache akan "
"secara otomatis digunakan jika federasi dikonfigurasi."

msgid "Keystone's v3 API is now the default for all services."
msgstr "API v3 Keystone sekarang menjadi standar untuk semua layanan."

msgid "Known Issues"
msgstr "Masalah Dikenal"

msgid ""
"LBaaS v2 is available for deployment in addition to LBaaS v1. Both versions "
"are mutually exclusive and cannot be running at the same time. Deployers "
"will need to re-create any existing load balancers if they switch between "
"LBaaS versions. Switching to LBaaS v2 will stop any existing LBaaS v1 load "
"balancers."
msgstr ""
"LBaaS v2 tersedia untuk deployment selain LBaaS v1. Kedua versi ini saling "
"eksklusif dan tidak dapat berjalan pada saat bersamaan. Pemberi kerja perlu "
"membuat kembali penyeimbang beban yang ada jika mereka beralih di antara "
"versi LBaaS. Beralih ke LBaaS v2 akan menghentikan penyeimbang beban LBaaS "
"v1 yang ada."

msgid ""
"LBaaS v2 is available for deployment in addition to LBaaS v1. Both versions "
"are mutually exclusive and cannot be running at the the same time. Deployers "
"will need to re-create any existing load balancers if they switch between "
"LBaaS versions. Switching to LBaaS v2 will stop any existing LBaaS v1 load "
"balancers."
msgstr ""
"LBaaS v2 tersedia untuk deployment selain LBaaS v1. Kedua versi ini saling "
"eksklusif dan tidak dapat berjalan pada saat bersamaan. Pemberi kerja perlu "
"membuat kembali penyeimbang beban yang ada jika mereka beralih di antara "
"versi LBaaS. Beralih ke LBaaS v2 akan menghentikan penyeimbang beban LBaaS "
"v1 yang ada."

msgid ""
"LBaaS v2 panels in Horizon will automatically be enabled when LBaaS v2 is "
"included in ``neutron_plugin_base``."
msgstr ""
"Panel LBaaS v2 di Horizon akan secara otomatis diaktifkan ketika LBaaS v2 "
"dimasukan  dalam ``neutron_plugin_base``."

msgid ""
"LBaaSv1 has been removed from the ``neutron-lbaas`` project in the Newton "
"release and it has been removed from OpenStack-Ansible as well."
msgstr ""
"LBaaSv1 telah dihapus dari proyek ``neutron-lbaas`` di rilis Newton dan "
"telah dihapus dari OpenStack-Ansible juga."

msgid "LBaaSv2 is now enabled by default in all-in-one (AIO) deployments."
msgstr ""
"LBaaSv2 sekarang diaktifkan secara default di deployment all-in-one (AIO)."

msgid ""
"LXC containers will have their TZ data sync with their physical host "
"machines. This is being done because containers have been assumed to use UTC "
"while a host could be using something else. This causes issues in some "
"services like celiometer and can result in general time differences in "
"logging."
msgstr ""
"Kontainer LXC akan memiliki sinkronisasi data TZ mereka dengan mesin host "
"fisik mereka. Ini sedang dilakukan karena kontainer diasumsikan menggunakan "
"UTC sedangkan host  dapat menggunakan sesuatu yang lain. Ini menyebabkan "
"masalah di beberapa layanan seperti celiometer dan dapat menghasilkan "
"perbedaan waktu secara umum dalam pencatatan."

msgid ""
"LXC containers will now generate a fixed mac address on all network "
"interfaces when the option `lxc_container_fixed_mac` is set to **true**. "
"This feature was implemented to resolve issues with dynamic mac addresses in "
"containers generally experienced at scale with network intensive services."
msgstr ""
"Kontainer LXC sekarang akan menghasilkan alamat mac tetap pada semua "
"antarmuka jaringan ketika opsi `lxc_container_fixed_mac` diatur ke **true "
"**. Fitur ini diterapkan untuk menyelesaikan masalah dengan alamat mac "
"dinamis dalam kontainer yang umumnya dialami pada skala dengan layanan "
"intensif jaringan."

msgid ""
"LXC containers will now have a proper RFC1034/5 hostname set during post "
"build tasks. A localhost entry for 127.0.1.1 will be created by converting "
"all of the \"_\" in the ``inventory_hostname`` to \"-\". Containers will be "
"created with a default domain of *openstack.local*. This domain name can be "
"customized to meet your deployment needs by setting the option "
"``lxc_container_domain``."
msgstr ""
"Kontainer LXC sekarang akan memiliki set hostname RFC1034/5 yang tepat "
"selama tugas post build. Entri localhost untuk 127.0.1.1 akan dibuat dengan "
"mengonversi semua \"_\" di ``inventory_hostname`` ke \"-\". Kontainer akan "
"dibuat dengan domain default *openstack.local*. Nama domain ini dapat "
"disesuaikan untuk memenuhi kebutuhan deployment Anda dengan mengatur opsi "
"``lxc_container_domain``."

msgid ""
"LXC containers will now have the ability to use a fixed mac address on all "
"network interfaces when the option `lxc_container_fixed_mac` is set "
"**true**. This change will assist in resolving a long standing issue where "
"network intensive services, such as neutron and rabbitmq, can enter a "
"confused state for long periods of time and require rolling restarts or "
"internal system resets to recover."
msgstr ""
"Kontainer LXC sekarang akan memiliki kemampuan untuk menggunakan alamat mac "
"tetap pada semua antarmuka jaringan ketika opsi `lxc_container_fixed_mac` "
"diatur **true**. Perubahan ini akan membantu dalam menyelesaikan masalah "
"lama di mana layanan intensif jaringan, seperti neutron dan rabbitmq, dapat "
"memasuki keadaan bingung untuk jangka waktu yang lama dan membutuhkan "
"restart bergulir atau reset sistem internal untuk pulih."

msgid ""
"LXC on CentOS is now installed via package from a COPR repository rather "
"than installed from the upstream source."
msgstr ""
"LXC pada CentOS sekarang diinstal melalui paket dari repositori COPR "
"daripada diinstal dari sumber hulu."

msgid ""
"LXC package installation and cache preparation will now occur by default "
"only on hosts which will actually implement containers."
msgstr ""
"Instalasi paket LXC dan persiapan cache sekarang akan terjadi secara default "
"hanya pada host yang benar-benar akan mengimplementasikan kontainer."

msgid ""
"LXD 2.0.11 grew a new feature ('description' tag for a container) and this "
"has been added to the stable Ubuntu Xenial 16.04 release. Unfortunately, "
"pylxd 2.0.5 can't handle this extra attribute and crashes out."
msgstr ""
"LXD 2.0.11 mengembangkan fitur baru (tag 'description' untuk sebuah "
"kontainer) dan ini telah ditambahkan ke rilis Ubuntu Xenial 16.04 yang "
"stabil. Sayangnya, pylxd 2.0.5 tidak dapat menangani atribut tambahan ini "
"dan lumpuh."

msgid "Liberty Series Release Notes"
msgstr "Catatan Rilis Seri Liberty"

msgid ""
"Listen via HTTPS on a load balancer, but via HTTP on the horizon host and "
"have the load balancer forward the correct headers. It will do this by "
"default in the integrated build due to the presence of the load balancer, so "
"the current behaviour is retained."
msgstr ""
"Dengarkan melalui HTTPS pada load balancer, tetapi melalui HTTP pada host "
"horizon dan minta load balancer meneruskan header yang benar. Ini akan "
"melakukan ini secara default di build terintegrasi karena adanya penyeimbang "
"beban, sehingga perilaku saat ini dipertahankan."

msgid ""
"Logging within the container has been bind mounted to the hosts this reslves "
"issue `1588051 <https://bugs.launchpad.net/openstack-ansible/+bug/1588051>_`"
msgstr ""
"Logging di dalam kontainer telah diikat ke host untuk mengatasi masalah ini "
"`1588051 <https://bugs.launchpad.net/openstack-ansible/+bug/1588051>_`"

msgid ""
"Logs for haproxy can now be found in ``/openstack/log/<haproxy host name>-"
"haproxy/`` on the container host (if haproxy is in a container), or ``/var/"
"log/haproxy/`` if haproxy is installed directly on a host."
msgstr ""
"Log untuk haproxy sekarang dapat ditemukan di  ``/openstack/log/<haproxy "
"host name>-haproxy/`` pada host kontainer (jika haproxy berada dalam sebuah "
"kontainer), atau ``/var/log/haproxy/`` jika haproxy dipasang langsung pada "
"host."

msgid ""
"MAC addresses for containers with a fixed MAC (`lxc_container_fixed_mac` "
"variable) are now saved to the ``/etc/ansible/facts.d/mac.fact`` file. "
"Should such a container be destroyed but not removed from inventory, the "
"interfaces will be recreated with the same MAC address when the container is "
"recreated."
msgstr ""
"Alamat MAC untuk kontainer dengan variabel MAC tetap (variabel "
"`lxc_container_fixed_mac`) sekarang disimpan ke file ``/etc/ansible/facts.d/"
"mac.fact``. Jika kontainer seperti itu dihancurkan tetapi tidak dihapus dari "
"inventaris, antarmuka akan dibuat kembali dengan alamat MAC yang sama ketika "
"kontainer dibuat kembali."

msgid "Main: Officially supported software."
msgstr "Utama: Perangkat lunak yang didukung secara resmi."

msgid ""
"MariaDB 10.0.32 released on Aug 17 which, when configured to use xtrabackup "
"for the SST, requires percona xtrabackup version 2.3.5 or higher. As "
"xtrabackup is the default SST mechanism in the ``galera_server`` role, the "
"version used has been updated from 2.2.13 to 2.3.5 for the x86_64 hardware "
"architecture. See `the percona release notes for 2.3.2 <https://www.percona."
"com/doc/percona-xtrabackup/LATEST/release-notes/2.3/2.3.2.html#new-"
"features>`_ for more details of what was included in the fix."
msgstr ""
"MariaDB 10.0.32 dirilis pada 17 Agustus, ketika dikonfigurasi untuk "
"menggunakan xtrabackup untuk SST, memerlukan percona xtrabackup versi 2.3.5 "
"atau lebih tinggi. Karena xtrabackup adalah mekanisme SST default dalam role "
"``galera_server``, versi yang digunakan telah diperbarui dari 2.2.13 ke "
"2.3.5 untuk arsitektur perangkat keras x86_64. Lihat 'the percona release "
"notes for 2.3.2 <https://www.percona.com/doc/percona-xtrabackup/LATEST/"
"release-notes/2.3/2.3.2.html#new-features>` _ untuk detail lebih lanjut "
"tentang yang termasuk dalam perbaikan."

msgid ""
"MariaDB 10.1+ includes `PrivateDevices=true` in its systemd unit files to "
"add extra security around mount namespaces for MariaDB. While this is useful "
"when running MariaDB on a bare metal host with other services, it is less "
"useful when MariaDB is already in a container with its own namespaces. In "
"addition, LXC 2.0.8 presents `/dev/ptmx` as a bind mount within the "
"container and systemd 219 (on CentOS 7) cannot make an additional bind mount "
"of `/dev/ptmx` when `PrivateDevices` is enabled."
msgstr ""
"MariaDB 10.1+ termasuk `PrivateDevices = true` dalam file unit systemd untuk "
"menambah keamanan tambahan di sekitar mount namespaces untuk MariaDB. "
"Meskipun ini berguna ketika menjalankan MariaDB pada host bare metal dengan "
"layanan lain, itu kurang berguna ketika MariaDB sudah berada dalam kontainer "
"dengan ruang namanya sendiri. Selain itu, LXC 2.0.8 menyajikan `/dev/ptmx` "
"sebagai bind mount di dalam kontainer dan systemd 219 (pada CentOS 7) tidak "
"dapat membuat bind mount tambahan dari `/dev/ptmx` ketika `PrivateDevices` "
"diaktifkan."

msgid "MariaDB version 10.x is now the default in OpenStack-Ansible."
msgstr "MariaDB versi 10.x sekarang menjadi default di OpenStack-Ansible."

msgid "Mariadb version upgrade gate checks removed."
msgstr "Pemeriksaan gate upgrade versi Mariadb dihapus."

msgid ""
"MemcacheD sets `PrivateDevices=true` in its systemd unit file to add extra "
"security around mount namespaces. While this is useful when running "
"MemcacheD on a bare metal host with other services, it is less useful when "
"MemcacheD is already in a container with its own namespaces. In addition, "
"LXC 2.0.8 presents `/dev/ptmx` as a bind mount within the container and "
"systemd 219 (on CentOS 7) cannot make an additional bind mount of `/dev/"
"ptmx` when `PrivateDevices` is enabled."
msgstr ""
"MemcacheD menetapkan `PrivateDevices = true` dalam file unit systemd untuk "
"menambah keamanan tambahan di sekitar mount namespaces. Meskipun ini berguna "
"ketika menjalankan MemcacheD pada host bare metal dengan layanan lain, itu "
"kurang berguna ketika MemcacheD sudah berada dalam kontainer dengan ruang "
"nama sendiri. Selain itu, LXC 2.0.8 menyajikan  `/dev/ptmx` sebagai bind "
"mount di dalam kontainer dan systemd 219 (pada CentOS 7) tidak dapat membuat "
"bind mount tambahan dari `/dev/ptmx` ketika `PrivateDevices` diaktifkan."

msgid ""
"Metal hosts were being inserted into the ``lxc_hosts`` group, even if they "
"had no containers (Bug 1660996). This is now corrected for newly configured "
"hosts. In addition, any hosts that did not belong in ``lxc_hosts`` will be "
"removed on the next inventory run or playbook call."
msgstr ""
"Metal host sedang dimasukkan ke dalam grup ``lxc_hosts``, bahkan jika mereka "
"tidak memiliki kontainer (Bug 1660996). Ini sekarang diperbaiki untuk host "
"yang baru dikonfigurasi. Selain itu, semua host yang tidak termasuk dalam "
"``lxc_hosts`` akan dihapus pada inventory berikutnya atau panggilan playbook."

msgid "Mitaka Series Release Notes"
msgstr "Catatan Rilis Seri Mitaka"

msgid ""
"Modify the handler named ``Reload systemd daemon`` and all references to it "
"in the role to something else (e.g. ``os_neutron Reload systemd daemon``)."
msgstr ""
"Memodifikasi handler yang bernama ``Reload systemd daemon`` dan semua "
"referensi untuknya di peran ke sesuatu yang lain (misal ``Os_neutron Reload "
"systemd daemon``)."

msgid ""
"Moved ``haproxy_service_configs`` var to ``haproxy_default_service_configs`` "
"so that ``haproxy_service_configs`` can be modified and added to without "
"overriding the entire default service dict."
msgstr ""
"Pindah ``haproxy_service_configs`` var ke "
"``haproxy_default_service_configs`` sehingga ``haproxy_service_configs`` "
"dapat dimodifikasi dan ditambahkan ke tanpa mengesampingkan seluruh dict "
"layanan default."

msgid ""
"Multiple HAProxy nodes can now be deployed in an HA configuration with "
"keepalived and LetsEncrypt certificates. Certbot can be treated as a backend "
"service for haproxy and acme-challenge requests from LetsEncrypt can be "
"directed to whichever HAProxy server is running a certificate renewal. New "
"variables are defined for frontend ACLs and options to be passed to Certbot "
"which enable this new feature, but the majority of the required "
"configuration is done via the existing HAProxy service setup. An example is "
"provided in the documentation."
msgstr ""
"Beberapa node HAProxy sekarang dapat digunakan dalam konfigurasi HA dengan "
"sertifikat keepalived dan LetsEncrypt. Certbot dapat diperlakukan sebagai "
"layanan backend untuk permintaan haproxy dan acme-challenge dari LetsEncrypt "
"dapat diarahkan ke server HAProxy mana pun yang menjalankan pembaruan "
"sertifikat. Variabel baru didefinisikan untuk ACL frontend dan opsi untuk "
"diteruskan ke Certbot yang memungkinkan fitur baru ini, tetapi sebagian "
"besar konfigurasi yang diperlukan dilakukan melalui pengaturan layanan "
"HAProxy yang ada. Contoh disediakan dalam dokumentasi."

msgid "Multiverse: Software that is not free."
msgstr "Multiverse: Perangkat lunak yang tidak gratis."

msgid ""
"Mysql cnf files can now be properly overridden. The config_template module "
"has been extended to support valueless options, such as those that are found "
"in the my.cnf file(i.e. `quick` under the `mysqldump` section). To use "
"valueless options, use the `ignore_none_type` attribute of the "
"config_template module."
msgstr ""
"File cnf Mysql sekarang dapat diganti dengan benar. Modul config_template "
"telah diperluas untuk mendukung opsi yang tidak berharga, seperti yang "
"ditemukan di file my.cnf (misal  `quick` di bawah bagian `mysqldump`). Untuk "
"menggunakan opsi yang tidak bernilai, gunakan atribut `ignore_none_type` "
"dari modul config_template."

msgid ""
"Neutron BGP dynamic routing plugin can now optionally be deployed and "
"configured. Please see `OpenStack Networking Guide: BGP dynamic routing "
"<http://docs.openstack.org/networking-guide/config-bgp-dynamic-routing."
"html>`_ for details about what the service is and what it provides."
msgstr ""
"Plugin routing dinamis BGP Neutron sekarang dapat secara opsional digunakan "
"dan dikonfigurasi. Tolong lihat `OpenStack Networking Guide: BGP dynamic "
"routing <http://docs.openstack.org/networking-guide/config-bgp-dynamic-"
"routing.html>`_ untuk perincian tentang apa layanan itu dan apa yang "
"disediakannya."

msgid ""
"Neutron DHCP options have been set to allow a DHCP server running dnsmasq to "
"coexist with other DHCP servers within the same network. This works by "
"instructing dnsmasq to ignore any clients which are not specified in dhcp-"
"host files."
msgstr ""
"Opsi DHCP Neutron telah diatur untuk memungkinkan server DHCP yang "
"menjalankan dnsmasq untuk hidup berdampingan dengan server DHCP lain dalam "
"jaringan yang sama. Ini bekerja dengan menginstruksikan dnsmasq untuk "
"mengabaikan klien yang tidak ditentukan dalam file dhcp-host."

msgid ""
"Neutron DHCP options have been set to provide for logging which makes "
"debugging DHCP and connectivity issues easier by default."
msgstr ""
"Opsi DHCP Neutron telah diatur untuk menyediakan logging yang membuat "
"debugging DHCP dan masalah konektivitas lebih mudah secara default."

msgid ""
"Neutron Firewall as a Service (FWaaS) can now optionally be deployed and "
"configured. Please see the `FWaaS Configuration Reference <http://docs."
"openstack.org/admin-guide-cloud/networking_introduction.html#firewall-as-a-"
"service-fwaas-overview>`_ for details about the what the service is and what "
"it provides. See the `FWaaS Install Guide <http://docs.openstack.org/"
"developer/openstack-ansible/install-guide/configure-fwaas.html>`_ for "
"implementation details."
msgstr ""
"Neutron Firewall as a Service (FWaaS) sekarang dapat digunakan dan "
"dikonfigurasi secara opsional. Silakan lihat  `FWaaS Configuration Reference "
"<http://docs.openstack.org/admin-guide-cloud/networking_introduction."
"html#firewall-as-a-service-fwaas-overview>`_ untuk detail tentang layanan "
"apa yang dimaksud dan apa yang disediakannya. Lihat  `FWaaS Install Guide "
"<http://docs.openstack.org/developer/openstack-ansible/install-guide/"
"configure-fwaas.html>`_  untuk detail implementasi."

msgid ""
"Neutron HA router capabilities in Horizon will be enabled automatically if "
"the neutron plugin type is ML2 and environment has >=2 L3 agent nodes."
msgstr ""
"Kemampuan router Neutron HA di Horizon akan diaktifkan secara otomatis jika "
"jenis plugin neutron adalah ML2 dan lingkungan memiliki >= 2 node agen L3."

msgid ""
"Neutron SR-IOV can now be optionally deployed and configured. For details "
"about the what the service is and what it provides, see the `SR-IOV "
"Installation Guide <http://docs.openstack.org/developer/openstack-ansible-"
"os_neutron/configure-network-services.html#sr--iov-support-optional>`_ for "
"more information."
msgstr ""
"Neutron SR-IOV sekarang dapat digunakan dan dikonfigurasi secara opsional. "
"Untuk perincian tentang apa layanan itu dan apa yang disediakannya, lihat "
"`SR-IOV Installation Guide <http://docs.openstack.org/developer/openstack-"
"ansible-os_neutron/configure-network-services.html#sr--iov-support-"
"optional>`_ untuk informasi lebih lanjut."

msgid ""
"Neutron VPN as a Service (VPNaaS) can now optionally be deployed and "
"configured. Please see the `OpenStack Networking Guide <http://docs."
"openstack.org/mitaka/networking-guide/>`_ for details about the what the "
"service is and what it provides. See the `VPNaaS Install Guide <http://docs."
"openstack.org/developer/openstack-ansible/install-guide/configure-network-"
"services.html#virtual-private-network-service-optional>`_ for implementation "
"details."
msgstr ""
"Neutron VPN as a Service (VPNaaS) kini dapat digunakan dan dikonfigurasi "
"secara opsional. Silakan lihat `OpenStack Networking Guide <http://docs."
"openstack.org/mitaka/networking-guide/>`_ untuk perincian tentang apa "
"layanan ini dan apa yang disediakannya. Lihat `VPNaaS Install Guide <http://"
"docs.openstack.org/developer/openstack-ansible/install-guide/configure-"
"network-services.html#virtual-private-network-service-optional>`_ untuk "
"detail implementasi."

msgid ""
"Neutron connectivity agents will now be deployed on baremetal within the "
"\"network_hosts\" defined within the ``openstack_user_config.yml``."
msgstr ""
"Agen konektivitas Neutron sekarang akan digunakan pada baremetal dalam "
"\"network_hosts\" yang didefinisikan dalam ``openstack_user_config.yml``."

msgid ""
"Neutron currently does not support enabling the ``port_security`` extension "
"driver cleanly for existing networks. If networks are created and the plugin "
"is enabled afterwards, VMs connected to those networks will not start. See "
"bug https://bugs.launchpad.net/neutron/+bug/1509312"
msgstr ""
"Neutron saat ini tidak mendukung pengaktifan driver ekstensi "
"``port_security`` secara bersih untuk jaringan yang ada. Jika jaringan "
"dibuat dan plugin diaktifkan setelahnya, VM yang terhubung ke jaringan "
"tersebut tidak akan mulai. Lihat bug https://bugs.launchpad.net/neutron/"
"+bug/1509312"

msgid ""
"Neutron notifications to nova will now use the internal API endpoint instead "
"of the public endpoint."
msgstr ""
"Notifikasi Neutron ke nova sekarang akan menggunakan internal API endpoint "
"daripada  public endpoint."

msgid ""
"Neutron now makes use of Ubuntu Cloud Archive by default. This can be "
"disabled by setting ``neutron_uca_enable`` to ``False``."
msgstr ""
"Neutron sekarang menggunakan Ubuntu Cloud Archive secara default. Ini dapat "
"dinonaktifkan dengan mengatur ``neutron_uca_enable`` ke ``False``."

msgid "New Features"
msgstr "Fitur baru"

msgid ""
"New hypervisor groups have been added allowing deployers to better define "
"their compute workloads. While the generic \"compute_hosts\" group will "
"still work explicit definitions for compute hosts can now be defined using "
"the `ironic-compute_hosts`, `kvm-compute_hosts`, `lxd-compute_hosts`, `qemu-"
"compute_hosts`, and `powervm-compute_hosts` groups accordingly"
msgstr ""
"Grup hypervisor baru telah ditambahkan yang memungkinkan deployer untuk "
"lebih mendefinisikan beban kerja komputasi mereka. Sementara grup "
"\"compute_hosts\" generik masih akan bekerja definisi eksplisit untuk host "
"komputasi sekarang dapat didefinisikan menggunakan grup  `ironic-"
"compute_hosts`, `kvm-compute_hosts`, `lxd-compute_hosts`, `qemu-"
"compute_hosts`, dan `powervm-compute_hosts` yang sesuai."

msgid ""
"New overrides are provided to allow for better customization around logfile "
"retention and rate limiting for UDP/TCP sockets. "
"``rsyslog_server_logrotation_window`` defaults to 14 days "
"``rsyslog_server_ratelimit_interval`` defaults to 0 seconds "
"``rsyslog_server_ratelimit_burst`` defaults to 10000"
msgstr ""
"Override baru disediakan untuk memungkinkan penyesuaian yang lebih baik di "
"sekitar penyimpanan file log dan pembatasan tingkat untuk soket UDP/TCP. "
"``rsyslog_server_logrotation_window`` secara default menjadi 14 hari "
"``rsyslog_server_ratelimit_interval`` menjadi 0 detik, "
"``rsyslog_server_ratelimit_burst`` default ke 10000"

msgid ""
"New rabbitmq-server role override rabbitmq_async_threads defaults to 128 "
"threads for IO operations inside the RabbitMQ erlang VM. This setting "
"doubled the threads for IO operations."
msgstr ""
"Role baru rabbitmq-server menggantikan rabbitmq_async_threads default "
"menjadi 128 thread untuk operasi IO di dalam RabbitMQ erlang VM. Pengaturan "
"ini menggandakan thread untuk operasi IO."

msgid ""
"New rabbitmq-server role override rabbitmq_process_limit defaults to 1048576 "
"for number of concurrent processes inside the erlang VM. Each network "
"connection and file handle does need its own process inside erlang."
msgstr ""
"Role rabbitmq-server baru menimpa default rabbitmq_process_limit menjadi "
"1048576 untuk jumlah proses bersamaan di dalam erlang VM. Setiap koneksi "
"jaringan dan file handle memang perlu prosesnya sendiri di dalam erlang."

msgid ""
"New variable ``ceph_extra_confs`` may be defined to support deployment of "
"extra Ceph config files.  This is useful for cinder deployments that utilize "
"multiple Ceph clusters as cinder backends."
msgstr ""
"Variabel baru ``ceph_extra_confs`` dapat didefinisikan untuk mendukung "
"penyebaran file konfigurasi Ceph tambahan. Ini berguna untuk penyebaran "
"cinder yang menggunakan beberapa cluster Ceph sebagai backend cinder."

msgid ""
"New variables have been added to allow a deployer to customize a aodh "
"systemd unit file to their liking."
msgstr ""
"Variabel baru telah ditambahkan untuk memungkinkan deployer untuk "
"menyesuaikan file unit systemd aodh sesuai keinginan mereka."

msgid ""
"New variables have been added to allow a deployer to customize a barbican "
"systemd unit file to their liking."
msgstr ""
"Variabel baru telah ditambahkan untuk memungkinkan deployer untuk "
"menyesuaikan file unit systemd barbican sesuai dengan keinginan mereka."

msgid ""
"New variables have been added to allow a deployer to customize a ceilometer "
"systemd unit file to their liking."
msgstr ""
"Variabel baru telah ditambahkan untuk memungkinkan deployer untuk "
"menyesuaikan file unit ceilometer systemd sesuai keinginan mereka."

msgid ""
"New variables have been added to allow a deployer to customize a cinder "
"systemd unit file to their liking."
msgstr ""
"Variabel baru telah ditambahkan untuk memungkinkan deployer untuk "
"menyesuaikan file unit cinder systemd sesuai dengan keinginan mereka."

msgid ""
"New variables have been added to allow a deployer to customize a designate "
"systemd unit file to their liking."
msgstr ""
"Variabel baru telah ditambahkan untuk memungkinkan deployer untuk "
"menyesuaikan file unit systemd designate systemd dengan keinginan mereka."

msgid ""
"New variables have been added to allow a deployer to customize a glance "
"systemd unit file to their liking."
msgstr ""
"Variabel baru telah ditambahkan untuk memungkinkan deployer untuk "
"menyesuaikan file unit glance systemd sesuai keinginan mereka."

msgid ""
"New variables have been added to allow a deployer to customize a gnocchi "
"systemd unit file to their liking."
msgstr ""
"Variabel baru telah ditambahkan untuk memungkinkan deployer untuk "
"menyesuaikan file unit gnocchi systemd sesuai dengan keinginan mereka."

msgid ""
"New variables have been added to allow a deployer to customize a heat "
"systemd unit file to their liking."
msgstr ""
"Variabel baru telah ditambahkan untuk memungkinkan deployer untuk "
"menyesuaikan file unit heat systemd sesuai dengan keinginan mereka."

msgid ""
"New variables have been added to allow a deployer to customize a ironic "
"systemd unit file to their liking."
msgstr ""
"Variabel baru telah ditambahkan untuk memungkinkan deployer untuk "
"menyesuaikan file unit ironic systemd sesuai dengan keinginan mereka."

msgid ""
"New variables have been added to allow a deployer to customize a keystone "
"systemd unit file to their liking."
msgstr ""
"Variabel baru telah ditambahkan untuk memungkinkan deployer untuk "
"menyesuaikan file unit keystone systemd sesuai dengan keinginan mereka."

msgid ""
"New variables have been added to allow a deployer to customize a magnum "
"systemd unit file to their liking."
msgstr ""
"Variabel baru telah ditambahkan untuk memungkinkan deployer untuk "
"menyesuaikan file unit magnum systemd sesuai dengan keinginan mereka."

msgid ""
"New variables have been added to allow a deployer to customize a neutron "
"systemd unit file to their liking."
msgstr ""
"Variabel baru telah ditambahkan untuk memungkinkan deployer untuk "
"menyesuaikan file unit neutron systemd sesuai keinginan mereka."

msgid ""
"New variables have been added to allow a deployer to customize a nova "
"systemd unit file to their liking."
msgstr ""
"Variabel baru telah ditambahkan untuk memungkinkan deployer untuk "
"menyesuaikan file unit nova systemd sesuai keinginan mereka."

msgid ""
"New variables have been added to allow a deployer to customize a octavia "
"systemd unit file to their liking."
msgstr ""
"Variabel baru telah ditambahkan untuk memungkinkan deployer untuk "
"menyesuaikan file unit octavia systemd sesuai keinginan mereka."

msgid ""
"New variables have been added to allow a deployer to customize a sahara "
"systemd unit file to their liking."
msgstr ""
"Variabel baru telah ditambahkan untuk memungkinkan deployer untuk "
"menyesuaikan file unit sahara systemd sesuai dengan keinginan mereka."

msgid ""
"New variables have been added to allow a deployer to customize a swift "
"systemd unit file to their liking."
msgstr ""
"Variabel baru telah ditambahkan untuk memungkinkan deployer untuk "
"menyesuaikan file unit swift systemd sesuai dengan keinginan mereka."

msgid ""
"New variables have been added to allow a deployer to customize a trove "
"systemd unit file to their liking."
msgstr ""
"Variabel baru telah ditambahkan untuk memungkinkan deployer untuk "
"menyesuaikan file unit trove systemd sesuai dengan keinginan mereka."

msgid ""
"New variables have been added to the glance role allowing a deployer to set "
"the UID and GID of the glance user. The new options are, "
"``glance_system_user_uid`` and ``glance_system_group_uid``. These options "
"are useful when deploying glance with shared storage as the back-end for "
"images and will only set the UID and GID of the glance user when defined."
msgstr ""
"Variabel baru telah ditambahkan ke peran glance yang memungkinkan seorang "
"penggelar untuk mengatur UID dan GID dari pengguna glance. Opsi baru adalah, "
"``glance_system_user_uid`` dan ``glance_system_group_uid``. Opsi ini berguna "
"saat menggunakan glance dengan penyimpanan bersama sebagai back-end untuk "
"images dan hanya akan mengatur UID dan GID pengguna glance saat ditentukan."

msgid ""
"New virtual environments will be created using python3, giving a "
"straightforward transition from python2 to python3 during the major upgrade. "
"The ansible-runtime virtual environment on the deployment host will also be "
"upgraded from python2 to python3 where the operating system allows."
msgstr ""
"Lingkungan virtual baru akan dibuat menggunakan python3, memberikan transisi "
"langsung dari python2 ke python3 selama upgrade utama. Lingkungan virtual "
"ansible-runtime pada host penyebaran juga akan ditingkatkan dari python2 ke "
"python3 dimana sistem operasi memungkinkan."

msgid ""
"Newer releases of CentOS ship a version of libnss that depends on the "
"existance of /dev/random and /dev/urandom in the operating system in order "
"to run.  This causes a problem during the cache preparation process which "
"runs inside chroot that does not contain this, resulting in errors with the "
"following message."
msgstr ""
"Rilis CentOS yang lebih baru menghadirkan versi libnss yang tergantung pada "
"keberadaan /dev/random and /dev/urandom dalam sistem operasi untuk "
"menjalankannya. Ini menyebabkan masalah selama proses persiapan cache yang "
"berjalan di dalam chroot yang tidak mengandung ini, menghasilkan kesalahan "
"dengan pesan berikut."

msgid ""
"Newer releases of CentOS ship a version of libnss that depends on the "
"existance of /dev/random and /dev/urandom in the operating system in order "
"to run.  This causes a problem during the cache preparation process which "
"runs inside chroot that does not contain this, resulting in errors with the "
"following message:"
msgstr ""
"Rilis CentOS yang lebih baru menghadirkan versi libnss yang tergantung pada "
"keberadaan /dev/random and /dev/urandom dalam sistem operasi untuk "
"menjalankannya. Ini menyebabkan masalah selama proses persiapan cache yang "
"berjalan di dalam chroot yang tidak mengandung ini, mengakibatkan kesalahan "
"dengan pesan berikut:"

msgid "Newton Series Release Notes"
msgstr "Catatan Rilis Seri Newton"

msgid ""
"Note that the value for ``openstack_distrib_release`` will be taken from the "
"variable ``openstack_release`` if it is set."
msgstr ""
"Perhatikan bahwa nilai untuk ``openstack_distrib_release`` akan diambil dari "
"variabel ``openstack_release`` jika diatur."

msgid ""
"Nova UCA repository support is implemented by default. This will allow the "
"users to benefit from the updated packages for KVM. The ``nova_uca_enable`` "
"variable controls the install source for the KVM packages. By default this "
"value is set to ``True`` to make use of UCA repository. User can set to "
"``False`` to disable."
msgstr ""
"Dukungan repositori Nova UCA diimplementasikan secara default. Ini akan "
"memungkinkan pengguna mendapat manfaat dari paket yang diperbarui untuk KVM. "
"Variabel ``nova_uca_enable`` mengontrol sumber instal untuk paket KVM. "
"Secara default, nilai ini diatur ke ``True`` untuk memanfaatkan repositori "
"UCA. Pengguna dapat mengatur ke ``False`` untuk menonaktifkan."

msgid ""
"Nova cell_v2 support has been added. The default cell is ``cell1`` which can "
"be overridden by the ``nova_cell1_name``. Support for multiple cells is not "
"yet available."
msgstr ""
"Dukungan Nova cell_v2 telah ditambahkan. Sel default adalah ``cell1`` yang "
"dapat ditimpa oleh ``nova_cell1_name``. Dukungan untuk banyak sel belum "
"tersedia."

msgid ""
"Nova features that use libguestfs (libvirt password/key injection) now work "
"on compute hosts running Ubuntu. When Nova is deployed to Ubuntu compute "
"hosts and either ``nova_libvirt_inject_key`` or "
"``nova_libvirt_inject_password`` are set to True, then kernels stored in /"
"boot/vmlinuz-* will be made readable to nova user. See launchpad bug 1507915."
msgstr ""
"Fitur Nova yang menggunakan libguestfs (libvirt password/key injection) "
"sekarang berfungsi pada host komputasi yang menjalankan Ubuntu. Ketika Nova "
"dikerahkan ke host komputasi Ubuntu dan ``nova_libvirt_inject_key`` atau "
"``nova_libvirt_inject_password`` disetel ke True, maka kernel yang disimpan "
"di /boot/vmlinuz-* akan dapat dibaca oleh pengguna nova. Lihat bug launchpad "
"1507915."

msgid ""
"Nova may now use an encrypted database connection. This is enabled by "
"setting ``nova_galera_use_ssl`` to ``True``."
msgstr ""
"Nova sekarang dapat menggunakan koneksi database terenkripsi. Ini diaktifkan "
"dengan mengatur ``nova_galera_use_ssl`` ke ``True``."

msgid ""
"Nova now utilizes version 2 of the Cinder API. Tempest is now configured to "
"use the v2 Cinder API as well."
msgstr ""
"Nova sekarang menggunakan versi 2 dari Cinder API. Tempest sekarang "
"dikonfigurasi untuk menggunakan API Cinder v2 juga."

msgid "Ocata Series Release Notes"
msgstr "Catatan Rilis Seri Ocata"

msgid ""
"Octavia is creating vms, securitygroups, and other things in its project. In "
"most cases the default quotas are not big enough. This will adjust them to "
"(configurable) reasonable values."
msgstr ""
"Octavia membuat vms, grup keamanan, dan hal lain dalam proyeknya. Dalam "
"kebanyakan kasus, kuota default tidak cukup besar. Ini akan menyesuaikannya "
"dengan nilai wajar (dapat dikonfigurasi)."

msgid ""
"Octavia requires SSL certificates for communication with the amphora. This "
"adds the automatic creation of self signed certificates for this purpose. It "
"uses different certificate authorities for amphora and control plane thus "
"insuring maximum security."
msgstr ""
"Octavia membutuhkan sertifikat SSL untuk komunikasi dengan amphora. Ini "
"menambahkan pembuatan otomatis sertifikat yang ditandatangani sendiri untuk "
"tujuan ini. Ini menggunakan otoritas sertifikat yang berbeda untuk amphora "
"dan control plane sehingga menjamin keamanan maksimum."

msgid ""
"On OpenStack-Ansible Train release you should upgrade your Debian from 9 "
"(stretch) to 10 (buster). Debian 9 support will be deprecated during the "
"next release of OpenStack-Ansible (Ussuri)."
msgstr ""
"Pada rilis OpenStack-Ansible Train Anda harus meningkatkan versi Debian Anda "
"dari 9 (stretch) ke 10 (buster). Dukungan Debian 9 akan dihentikan selama "
"rilis OpenStack-Ansible (Ussuri) berikutnya."

msgid ""
"Once this is done, the repo build process should complete as it did before "
"and the updated software can now be deployed."
msgstr ""
"Setelah ini selesai, proses pembuatan repo harus selesai seperti sebelumnya "
"dan perangkat lunak yang diperbarui sekarang dapat digunakan."

msgid ""
"Once this is done, the upgrade process for neutron services will work "
"properly."
msgstr ""
"Setelah ini selesai, proses upgrade untuk layanan neutron akan bekerja "
"dengan baik."

msgid "Only Ceph repos are supported for now."
msgstr "Hanya repo Ceph yang didukung untuk saat ini."

msgid ""
"Open vSwitch dataplane with NSH support has been implemented. This feature "
"may be activated by setting ``ovs_nsh_support: True`` in ``/etc/"
"openstack_deploy/user_variables.yml``."
msgstr ""
"Buka dataplane vSwitch dengan dukungan NSH telah diterapkan. Fitur ini dapat "
"diaktifkan dengan mengatur `` ovs_nsh_support: ``/etc/openstack_deploy/"
"user_variables.yml``."

msgid ""
"Open vSwitch driver support has been implemented. This includes the "
"implementation of the appropriate Neutron configuration and package "
"installation. This feature may be activated by setting "
"``neutron_plugin_type: ml2.ovs`` in ``/etc/openstack_deploy/user_variables."
"yml``."
msgstr ""
"Buka dukungan driver vSwitch telah diterapkan. Ini termasuk implementasi "
"konfigurasi Neutron yang sesuai dan instalasi paket. Fitur ini dapat "
"diaktifkan dengan mengatur ``neutron_plugin_type: ml2.ovs`` di ``/etc/"
"openstack_deploy/user_variables.yml``."

msgid ""
"OpenStack services have been set to communicate with RabbitMQ using SSL by "
"default. This feature may be disabled by setting ``rabbit_use_ssl`` to "
"``false`` in ``/etc/openstack_deploy/user_variables.yml``. The default "
"behaviour will be to use a self-signed certificate for communications. This "
"can be changed by the procedure referred to in `the SSL documentation "
"<http://docs.openstack.org/developer/openstack-ansible/mitaka/install-guide/"
"configure-sslcertificates.html>`_."
msgstr ""
"Layanan OpenStack telah diatur untuk berkomunikasi dengan RabbitMQ "
"menggunakan SSL secara default. Fitur ini dapat dinonaktifkan dengan "
"mengatur ``rabbit_use_ssl`` ke ``false`` di `` ``/etc/openstack_deploy/"
"user_variables.yml``. Perilaku default adalah menggunakan sertifikat yang "
"ditandatangani sendiri untuk komunikasi. Ini dapat diubah dengan prosedur "
"sebagaimana dimaksud dalam `the SSL documentation <http://docs.openstack.org/"
"developer/openstack-ansible/mitaka/install-guide/configure-sslcertificates."
"html>`_."

msgid "OpenStack-Ansible Release Notes"
msgstr "Catatan Rilis OpenStack-Ansible"

msgid ""
"OpenStack-Ansible now provided corosync and pacemaker cluster setup as part "
"of the os-masakari-install playbook. Corosync/pacemaker cluster is required "
"for the proper work of masakari hostmonitors, as they identify hosts state "
"with help of corosync."
msgstr ""
"OpenStack-Ansible sekarang menyediakan konfigurasi cluster corosync dan "
"pacemaker sebagai bagian dari playbook os-masakari-install. Cluster Corosync/"
"pacemaker diperlukan untuk pekerjaan hostmonitors masakari yang benar, "
"karena mereka mengidentifikasi status host dengan bantuan corosync."

msgid "OpenStack-Ansible now support deployments on Debian 10 (buster)"
msgstr "OpenStack-Ansible sekarang mendukung penyebaran di Debian 10 (buster)"

msgid ""
"OpenStack-Ansible now supports the openSUSE Leap 42.X distributions mainly "
"targeting the latest 42.3 release."
msgstr ""
"OpenStack-Ansible sekarang mendukung distribusi openSUSE Leap 42.X terutama "
"menargetkan rilis 42.3 terbaru."

msgid ""
"OpenStack-Ansible sets a new variable, `galera_disable_privatedevices`, that "
"controls whether the `PrivateDevices` configuration in MariaDB's systemd "
"unit file is enabled."
msgstr ""
"OpenStack-Ansible menetapkan variabel baru, `galera_disable_privatedevices`, "
"yang mengontrol apakah konfigurasi `PrivateDevices` dalam file unit systemd "
"MariaDB diaktifkan."

msgid ""
"OpenStack-Ansible sets a new variable, `memcached_disable_privatedevices`, "
"that controls whether the `PrivateDevices` configuration in MemcacheD's "
"systemd unit file is enabled."
msgstr ""
"OpenStack-Ansible menetapkan variabel baru, "
"`memcached_disable_privatedevices`, yang mengontrol apakah konfigurasi "
"`PrivateDevices` dalam file unit systemd MemcacheD diaktifkan."

msgid ""
"Openstack services and infrastructure such as galera, rabbitmq and memcached "
"already have defaults in their ansible roles to control the IP address which "
"those services bind to. Prior to this release the default of 0.0.0.0 was "
"used. A global setting in the openstack-ansible group variables now "
"overrides those default bind address to be the local address on the "
"openstack management network (typically br-mgmt) for the relevant host or "
"container."
msgstr ""
"Layanan dan infrastruktur openstack seperti galera, rabbitmq, dan memcache "
"sudah memiliki default dalam perannya yang memungkinkan untuk mengontrol "
"alamat IP tempat layanan tersebut terikat. Sebelum rilis ini default 0.0.0.0 "
"digunakan. Pengaturan global dalam variabel grup openstack-ansible sekarang "
"mengganti alamat mengikat default tersebut menjadi alamat lokal di jaringan "
"manajemen openstack (typically br-mgmt) untuk host atau container yang "
"relevan."

msgid "Other Notes"
msgstr "Catatan lain"

msgid ""
"Our general config options are now stored in an \"/usr/local/bin/openstack-"
"ansible.rc\" file and will be sourced when the \"openstack-ansible\" wrapper "
"is invoked. The RC file will read in BASH environment variables and should "
"any Ansible option be set that overlaps with our defaults the provided value "
"will be used."
msgstr ""
"Opsi konfigurasi umum kami sekarang disimpan dalam file \"/usr/local/bin/"
"openstack-ansible.rc\" dan akan diambil dari sumber ketika pembungkus "
"\"openstack-ansible\" dipanggil. File RC akan membaca dalam variabel "
"lingkungan BASH dan jika ada opsi Ansible diatur yang tumpang tindih dengan "
"default kami, nilai yang disediakan akan digunakan."

msgid ""
"Overrides for ceilometer ``aodh_connection_string`` will no longer work. "
"Specifying an Aodh connection string in Ceilometer was deprecated within "
"Ceilometer in a prior release so this option has been removed."
msgstr ""
"Override untuk ceilometer ``aodh_connection_string`` tidak akan berfungsi "
"lagi. Menentukan string koneksi Aodh di Ceilometer tidak digunakan lagi "
"dalam Ceilometer dalam rilis sebelumnya sehingga opsi ini telah dihapus."

msgid ""
"Panko migrated from usage of Apache mod_wsgi or native daemon to uWSGI "
"daemon. This means, that `panko_apache_*` variables are not available and "
"has no effect anymore."
msgstr ""
"Panko bermigrasi dari penggunaan Apache mod_wsgi atau native daemon ke uWSGI "
"daemon. Ini berarti, bahwa variabel `panko_apache_ *` tidak tersedia dan "
"tidak berpengaruh lagi."

msgid ""
"Paramiko version 2.0 Python requires the Python cryptography library. New "
"system packages must be installed for this library. For OpenStack-Ansible "
"versions <12.0.12, <11.2.15, <13.0.2 the system packages must be installed "
"on the **deployment host** manually by executing ``apt-get install -y build-"
"essential libssl-dev libffi-dev``."
msgstr ""
"Paramiko versi 2.0 Python membutuhkan pustaka kriptografi Python. Paket "
"sistem baru harus diinstal untuk perpustakaan ini. Untuk versi OpenStack-"
"Ansible <12.0.12, <11.2.15, <13.0.2 paket sistem harus diinstal pada "
"**deployment host** secara manual dengan menjalankan ``apt-get install -y "
"build-essential libssl-dev libffi-dev``."

msgid ""
"Passed --extra-vars flag to the openstack-ansible should have precedence "
"over the user-variables*.yml now."
msgstr ""
"Passed --extra-vars flag ke openstack-ansible seharusnya didahulukan dari "
"user-variables*.yml  sekarang."

msgid ""
"Per https://review.openstack.org/#/c/413920/20, the ceilometer-collector "
"service is now deprecated and its respective container is no longer deployed "
"by default. Gnocchi is now used as the default publisher."
msgstr ""
"Per https://review.openstack.org/#/c/413920/20, layanan ceilometer-collector "
"sekarang tidak digunakan lagi dan kontainernya masing-masing tidak lagi "
"digunakan secara default. Gnocchi sekarang digunakan sebagai penerbit "
"default."

msgid "Percona Xtrabackup has been removed from the Galera client role."
msgstr "Percona Xtrabackup telah dihapus dari peran klien Galera."

msgid ""
"Persistent systemd journals are now enabled. This allows deployers to keep "
"older systemd journals on disk for review. The disk space requirements are "
"extremely low since the journals are stored in binary format. The default "
"location for persistent journals is in ``/var/log/journal``."
msgstr ""
"Jurnal systemd persisten sekarang diaktifkan. Hal ini memungkinkan "
"pengerahkan untuk menyimpan jurnal systemd yang lebih lama pada disk untuk "
"ditinjau. Persyaratan ruang disk sangat rendah karena jurnal disimpan dalam "
"format biner. Lokasi default untuk jurnal persisten ada di ``/var/log/"
"journal``."

msgid "Pike Series Release Notes"
msgstr "Catatan Rilis Seri Pike"

msgid ""
"Playbooks for `ceph-ansible <https://github.com/ceph/ceph-ansible/>`_ have "
"been added to facilitate gate testing of the OpenStack-Ansible integration "
"with Ceph clusters, and can be used to integrate the two projects so that "
"OpenStack-Ansible can deploy and consume its own Ceph installation using "
"ceph-ansible. This should be considered an experimental integration until "
"further testing is been completed by deployers and the OpenStack-Ansible "
"gate to fine tune its stability and completeness. The ceph-install playbook "
"can be activated by adding hosts to the ``ceph-mon_hosts`` and ``ceph-"
"osd_hosts`` in the OSA inventory. A variety of ceph-ansible specific "
"variables will likely need to be configured in ``user_variables.yml`` to "
"configure ceph-ansible for your environment. Please reference the `ceph-"
"ansible repo <https://github.com/ceph/ceph-ansible/blob/master/group_vars/"
"all.yml.sample>`_ for a list of variables the project supports."
msgstr ""
"Playbook untuk `ceph-ansible <https://github.com/ceph/ceph-ansible/>`_ telah "
"ditambahkan untuk memfasilitasi pengujian gerbang integrasi OpenStack-"
"Ansible dengan cluster Ceph, dan dapat digunakan untuk mengintegrasikan "
"kedua proyek sehingga OpenStack-Ansible dapat menggunakan dan menggunakan "
"instalasi Ceph sendiri menggunakan ceph-ansible. Ini harus dianggap sebagai "
"integrasi eksperimental sampai pengujian lebih lanjut diselesaikan oleh para "
"deployer dan gate OpenStack-Ansible untuk menyempurnakan stabilitas dan "
"kelengkapannya. Playbook ceph-install dapat diaktifkan dengan menambahkan "
"host ke ``ceph-mon_hosts`` dan ``ceph-osd_hosts`` dalam OSA inventory. "
"Berbagai variabel spesifik yang dimungkinkan mungkin perlu dikonfigurasikan "
"di ``user_variables.yml`` untuk mengonfigurasi yang mungkin untuk lingkungan "
"Anda. Silakan rujuk `ceph-ansible repo <https://github.com/ceph/ceph-ansible/"
"blob/master/group_vars/all.yml.sample>`_ untuk daftar variabel yang didukung "
"proyek."

msgid ""
"Playbooks have been added to facilitate this process through automation. "
"Please see the ``Major upgrades`` chapter in the Operations Guide."
msgstr ""
"Playbook telah ditambahkan untuk memfasilitasi proses ini melalui "
"otomatisasi. Silakan lihat bab ``Major upgrades`` idalam Operations Guide."

msgid ""
"Please note: Horizon will still display IPv6 addresses in various panels "
"with IPv6 support disabled. However, it will not allow any direct management "
"of IPv6 configuration."
msgstr ""
"Harap dicatat: Horizon masih akan menampilkan alamat IPv6 di berbagai panel "
"dengan dukungan IPv6 dinonaktifkan. Namun, itu tidak akan mengizinkan "
"manajemen langsung konfigurasi IPv6."

msgid "Power off one Galera container"
msgstr "Matikan satu kontainer Galera"

msgid "Power on the Galera container"
msgstr "Nyalakan kontainer Galera"

msgid "Prelude"
msgstr "Prelude (pendahuluan)"

msgid ""
"Previously, the ``ansible_managed`` var was being used to insert a header "
"into the ``swift.conf`` that contained date/time information. This meant "
"that swift.conf across different nodes did not have the same MD5SUM, causing "
"``swift-recon --md5`` to break. We now insert a piece of static text instead "
"to resolve this issue."
msgstr ""
"Sebelumnya, var ``ansible_managed`` sedang digunakan untuk memasukkan header "
"ke dalam ``swift.conf`` yang berisi informasi tanggal/waktu. Ini berarti "
"bahwa swift.conf di seluruh node yang berbeda tidak memiliki MD5SUM yang "
"sama, menyebabkan ``swift-recon --md5`` rusak. Kami sekarang menyisipkan "
"selembar teks statis sebagai gantinya untuk menyelesaikan masalah ini."

msgid ""
"Properly distrubute client keys to nova hypervisors when extra ceph clusters "
"are being deployed."
msgstr ""
"Sebarkan kunci klien dengan benar ke hypervisor nova ketika cluster ceph "
"ekstra sedang digunakan."

msgid ""
"Properly remove temporary files used to transfer ceph client keys from the "
"deploy host and hypervisors."
msgstr ""
"Hapus file sementara yang digunakan untuk mentransfer kunci klien ceph "
"dengan benar dari host dan hypervisor."

msgid ""
"Public endpoints will need to be updated using the Keystone admin API to "
"support secure endpoints. The Keystone ansible module will not recreate the "
"endpoints automatically. Documentation on the `Keystone service catalog can "
"be found here <http://docs.openstack.org/developer/keystone/configuration."
"html#service-catalog>`_."
msgstr ""
"Endpoint publik perlu diperbarui menggunakan Keystone admin API untuk "
"mendukung endpoint yang aman. Modul Keystone ansible tidak akan membuat "
"ulang endpoint secara otomatis. Dokumentasi tentang `Keystone service "
"catalog can be found here <http://docs.openstack.org/developer/keystone/"
"configuration.html#service-catalog>`_."

msgid ""
"Python 2.7 support has been dropped. Last release of openstack ansible to "
"support python 2.7 is OpenStack Train."
msgstr ""
"Dukungan Python 2.7 telah dijatuhkan. Rilis terakhir dari openstack yang "
"dapat digunakan untuk mendukung python 2.7 adalah OpenStack Train."

msgid ""
"Python-tempestconf is a tool that generates a tempest.conf file, based only "
"on the credentials from an openstack installation. It uses the discoverable "
"api from openstack to check for services, features, etc."
msgstr ""
"Python-tempestconf adalah alat yang menghasilkan file tempest.conf, hanya "
"berdasarkan pada kredensial dari instalasi openstack. Ia menggunakan api "
"yang dapat ditemukan dari openstack untuk memeriksa layanan, fitur, dll."

msgid "Queens Series Release Notes"
msgstr "Catatan Rilis Seri Queens"

msgid ""
"RabbitMQ Server can now be installed from different methods: a deb file "
"(default), from standard repository package and from external repository. "
"Current behavior is unchanged. Please define ``rabbitmq_install_method: "
"distro`` to use packages provided by your distribution or "
"``rabbitmq_install_method: external_repo`` to use packages stored in an "
"external repo. In the case ``external_repo`` is used, the process will "
"install RabbitMQ from the packages hosted by packagecloud.io, as recommended "
"by RabbitMQ."
msgstr ""
"RabbitMQ Server sekarang dapat diinstal dari berbagai metode: file deb "
"(default), dari paket repositori standar dan dari repositori eksternal. "
"Perilaku saat ini tidak berubah. Silakan tentukan `` "
"rabbitmq_install_method: distro`` untuk menggunakan paket yang disediakan "
"oleh distribusi Anda atau `` rabbitmq_install_method: external_repo`` untuk "
"menggunakan paket yang disimpan dalam repo eksternal. Jika `` "
"external_repo`` digunakan, proses akan menginstal RabbitMQ dari paket yang "
"di-host oleh packagecloud.io, seperti yang direkomendasikan oleh RabbitMQ."

msgid ""
"RabbitMQ is now installed via an RPM repository provided by RabbitMQ "
"developers. The version is kept constant via yum's versionlock plugin. This "
"allows the tasks to lock the RabbitMQ version to a particular revision and "
"prevent changes to that version."
msgstr ""
"RabbitMQ sekarang diinstal melalui repositori RPM yang disediakan oleh "
"pengembang RabbitMQ. Versi ini dijaga konstan melalui plugin versionlock "
"yum. Ini memungkinkan tugas untuk mengunci versi RabbitMQ ke revisi tertentu "
"dan mencegah perubahan ke versi itu."

msgid ""
"Rather than a hard-coded set of projects and users, tempest can now be "
"configured with a custom list with the variables ``tempest_projects`` and "
"``tempest_users``."
msgstr ""
"Dari sekumpulan proyek hard-coded dan pengguna , tempest sekarang dapat "
"dikonfigurasi dengan daftar kustom dengan variabel ``tempest_projects`` dan "
"``tempest_users``."

msgid ""
"Recently the spice-html5 git repository was entirely moved from ``https://"
"github.com/SPICE/spice-html5`` to ``https://gitlab.freedesktop.org/spice/"
"spice-html5``. This results in a failure in the git clone stage of the "
"``repo-build.yml`` playbook for OSA ocata releases earlier than ``15.1.22``. "
"To fix the issue, deployers may upgrade to the most recent release, or may "
"implement the following override in ``user_variables.yml``."
msgstr ""
"Baru-baru ini repositori git spice-html5 sepenuhnya dipindahkan dari "
"```https://github.com/SPICE/spice-html5`` ke ``https://gitlab.freedesktop."
"org/spice/spice-html5``. Ini menghasilkan kegagalan pada tahap git clone "
"dari ``repo-build.yml`` playbook untuk OSA rilis ocata lebih awal dari "
"``15.1.22``. Untuk memperbaiki masalah ini, para deployer dapat upgrade ke "
"rilis terbaru, atau dapat menerapkan override berikut di ``user_variables."
"yml``."

msgid ""
"Recently the spice-html5 git repository was entirely moved from ``https://"
"github.com/SPICE/spice-html5`` to ``https://gitlab.freedesktop.org/spice/"
"spice-html5``. This results in a failure in the git clone stage of the "
"``repo-build.yml`` playbook for OSA pike releases earlier than ``16.0.14``. "
"To fix the issue, deployers may upgrade to the most recent release, or may "
"implement the following override in ``user_variables.yml``."
msgstr ""
"Baru-baru ini repositori git spice-html5 sepenuhnya dipindahkan dari "
"``https://github.com/SPICE/spice-html5`` ke ``https://gitlab.freedesktop.org/"
"spice/spice-html5``. Ini menghasilkan kegagalan pada tahap git clone dari "
"``repo-build.yml`` playbook untuk rilis OSA pike lebih awal dari "
"``16.0.14``. Untuk memperbaiki masalah ini, para deployer dapat upgrade ke "
"rilis terbaru, atau dapat menerapkan override berikut di ``user_variables."
"yml``."

msgid ""
"Recently the spice-html5 git repository was entirely moved from ``https://"
"github.com/SPICE/spice-html5`` to ``https://gitlab.freedesktop.org/spice/"
"spice-html5``. This results in a failure in the git clone stage of the "
"``repo-build.yml`` playbook for OSA queens releases earlier than ``17.0.5``. "
"To fix the issue, deployers may upgrade to the most recent release, or may "
"implement the following override in ``user_variables.yml``."
msgstr ""
"Baru-baru ini repositori git spice-html5 sepenuhnya dipindahkan dari "
"``https://github.com/SPICE/spice-html5`` ke ``https://gitlab.freedesktop.org/"
"spice/spice-html5``.  Ini menghasilkan kegagalan pada tahap git klon dari "
"``repo-build.yml`` playbook untuk rilis ratu OSA lebih awal dari ``17.0.5``. "
"Untuk memperbaiki masalah ini, para deployer dapat upgrade ke rilis terbaru, "
"atau dapat menerapkan override berikut di ``user_variables.yml``."

msgid "Related-Bugs:"
msgstr "Bug terkait:"

msgid ""
"Removal of the magnum module. Please use the ansible native module "
"'os_coe_cluster_template'. More information: https://docs.ansible.com/"
"ansible/latest/modules/os_coe_cluster_template_module.html This module was "
"not used in the openstack repos therefore no updates were required."
msgstr ""
"Penghapusan modul magnum. Silakan gunakan modul asli "
"'os_coe_cluster_template'. Informasi lebih lanjut: https://docs.ansible.com/"
"ansible/latest/modules/os_coe_cluster_template_module.html Modul ini tidak "
"digunakan dalam repo openstack sehingga tidak diperlukan pembaruan."

msgid ""
"Removal of the netloc, netloc_no_port and netorigin filters. Please use the "
"urlsplit filter instead. All usages of the deprecated filters in openstack "
"repos have been updated."
msgstr ""
"Penghapusan filter netloc, netloc_no_port dan netorigin. Silakan gunakan "
"filter urlsplit sebagai gantinya. Semua penggunaan filter usang dalam repo "
"openstack telah diperbarui."

msgid ""
"Remove ``CONF.scenario.img_dir`` option as it is being removed from Tempest "
"after ~4 year deprecation period. ``CONF.scenario.img_file`` option needs to "
"contain the full path to an image to upload to glance."
msgstr ""
"Hapus opsi ``CONF.scenario.img_dir '' karena sedang dihapus dari Tempest "
"setelah ~ periode penghentian 4 tahun. ``CONF.scenario.img_file`` opsi "
"tersebut harus berisi full path ke image untuk diunggah untuk dilihat glance."

msgid ""
"Remove ``cinder_glance_api_version`` option due to deprecation of "
"glance_api_version option in Cinder."
msgstr ""
"Hapus opsi ``cinder_glance_api_version`` karena penghentian opsi "
"glance_api_version di Cinder."

msgid ""
"Remove ``cinder_rpc_backend`` option due to deprecation of rpc_backend "
"option in oslo.messaging."
msgstr ""
"Hapus opsi ``cinder_rpc_backend`` karena penghentian opsi rpc_backend di "
"oslo.messaging."

msgid ""
"Remove ``cloudkitty_rpc_backend`` option due to deprecation of rpc_backend "
"option in oslo.messaging."
msgstr ""
"Hapus opsi ``cloudkitty_rpc_backend`` karena penghentian opsi rpc_backend di "
"oslo.messaging."

msgid ""
"Remove ``designate_rpc_backend`` option due to deprecation of rpc_backend "
"option in oslo.messaging."
msgstr ""
"Hapus opsi ``designate_rpc_backend`` karena penghentian opsi rpc_backend di "
"oslo.messaging."

msgid ""
"Remove ``glance_rpc_backend`` option due to deprecation of rpc_backend "
"option in oslo.messaging."
msgstr ""
"Hapus opsi ``glance_rpc_backend`` karena penghentian opsi rpc_backend di "
"oslo.messaging."

msgid ""
"Remove ``heat_rpc_backend`` option due to deprecation of rpc_backend option "
"in oslo.messaging."
msgstr ""
"Hapus opsi ``heat_rpc_backend`` karena penghentian opsi rpc_backend di oslo."
"messaging."

msgid ""
"Remove ``keystone_rpc_backend`` option due to deprecation of rpc_backend "
"option in oslo.messaging."
msgstr ""
"Hapus opsi ``keystone_rpc_backend`` karena penghentian opsi rpc_backend di "
"oslo.messaging."

msgid ""
"Remove ``magnum_rpc_backend`` option due to deprecation of rpc_backend "
"option in oslo.messaging."
msgstr ""
"Hapus opsi ``magnum_rpc_backend`` karena penghentian opsi rpc_backend di "
"oslo.messaging."

msgid ""
"Remove ``neutron_rpc_backend`` option due to deprecation of rpc_backend "
"option in oslo.messaging."
msgstr ""
"Hapus opsi ``neutron_rpc_backend`` karena penghentian opsi rpc_backend di "
"oslo.messaging."

msgid ""
"Remove ``octavia_rpc_backend`` option due to deprecation of rpc_backend "
"option in oslo.messaging."
msgstr ""
"Hapus opsi ``octavia_rpc_backend`` karena penghentian opsi rpc_backend di "
"oslo.messaging."

msgid ""
"Remove ``sahara_rpc_backend`` option due to deprecation of rpc_backend "
"option in oslo.messaging."
msgstr ""
"Hapus opsi ``sahara_rpc_backend`` karena penghentian opsi rpc_backend di "
"oslo.messaging."

msgid ""
"Remove ``trove_rpc_backend`` option due to deprecation of rpc_backend option "
"in oslo.messaging."
msgstr ""
"Hapus opsi ``trove_rpc_backend`` karena penghentian opsi rpc_backend di oslo."
"messaging."

msgid "Removed PKI token support and the ``cloudkitty_signing_dir`` parameter."
msgstr ""
"Dukungan token PKI yang dihapus dan parameter ``cloudkitty_signing_dir``."

msgid ""
"Removed ``cirros_img_url`` and in most places replaced with "
"``tempest_img_url``."
msgstr ""
"``cirros_img_url`` yang dihapus dan di sebagian besar tempat diganti dengan "
"``tempest_img_url``."

msgid ""
"Removed ``cirros_tgz_url`` and in most places replaced with "
"``tempest_img_url``."
msgstr ""
"``cirros_tgz_url`` dihapus dan di sebagian besar tempat diganti dengan "
"``tempest_img_url``."

msgid ""
"Removed ``tempest_volume_backend1_name`` and "
"``tempest_volume_backend1_name`` since ``backend1_name`` and "
"``backend2_name`` were removed from tempest in commit 27905cc (merged "
"26/04/2016)"
msgstr ""
"``tempest_volume_backend1_name`` dan ``tempest_volume_backend1_name`` yang "
"dihapus karena ``backend1_name`` dan ``backend2_name`` telah dihapus dari "
"tempest di commit 27905cc (digabung 26/04/2016)"

msgid ""
"Removed dependency for ``cinder_backends_rbd_inuse`` in nova.conf when "
"setting ``rbd_user`` and ``rbd_secret_uuid`` variables. Cinder delivers all "
"necessary values via RPC when attaching the volume, so those variables are "
"only necessary for ephemeral disks stored in Ceph. These variables are "
"required to be set up on cinder-volume side under backend section."
msgstr ""
"Dependency dihapus untuk ``cinder_backends_rbd_inuse`` di nova.conf ketika "
"mengatur variabel ``rbd_user`` dan ``rbd_secret_uuid``. Cinder memberikan "
"semua nilai yang diperlukan melalui RPC saat melampirkan volume, sehingga "
"variabel itu hanya diperlukan untuk disk sementara yang disimpan di Ceph. "
"Variabel ini harus diatur pada sisi volume cinder di bawah bagian backend."

msgid "Removed deprecated variable ``tempest_compute_image_alt_ssh_password``"
msgstr "Variabel usang yang dihapus ``tempest_compute_image_alt_ssh_password``"

msgid "Removed deprecated variable ``tempest_compute_image_alt_ssh_user``"
msgstr "Variabel usang yang dihapus ``tempest_compute_image_alt_ssh_user``"

msgid "Removed deprecated variable ``tempest_compute_image_ssh_password``"
msgstr "Variabel usang yang dihapus ``tempest_compute_image_ssh_password``"

msgid ""
"Removed various deprecated / no longer supported features from tempest.conf."
"j2.  Some variables have been moved to their new sections in the config."
msgstr ""
"Menghapus berbagai fitur usang / tidak didukung lagi dari tempest.conf.j2. "
"Beberapa variabel telah dipindahkan ke bagian baru di config."

msgid "Renamed ``cirros_img_disk_format`` to ``tempest_img_disk_format``"
msgstr ""
"Berganti nama ``cirros_img_disk_format`` menjadi ``tempest_img_disk_format``"

msgid "Repeat for the other Galera containers"
msgstr "Ulangi untuk kontainer Galera lainnya"

msgid ""
"Repeatable deployments are now easier since the manifest files for OpenStack "
"software uses the exact content from an upstream repository. Specific "
"commits or tags can be referenced within the manifest.  The ``yaprt`` "
"package is no longer used to build the repo."
msgstr ""
"Deployment yang dapat diulang sekarang lebih mudah karena file manifes untuk "
"perangkat lunak OpenStack menggunakan konten yang tepat dari repositori "
"hulu. Komit atau tag tertentu dapat dirujuk dalam manifes. Paket ``yaprt`` "
"tidak lagi digunakan untuk membangun repo."

msgid ""
"Restricted: Supported software that is not available under a completely free "
"license."
msgstr ""
"Restricted: Perangkat lunak yang didukung yang tidak tersedia di bawah "
"lisensi sepenuhnya gratis."

msgid "Rocky Series Release Notes"
msgstr "Catatan Rilis Seri Rocky"

msgid ""
"SELinux policy for neutron on CentOS 7 is now provided to fix SELinux AVCs "
"that occur when neutron's agents attempt to start daemons such as haproxy "
"and dnsmasq."
msgstr ""
"Kebijakan SELinux untuk neutron pada CentOS 7 sekarang disediakan untuk "
"memperbaiki SELinux AVC yang terjadi ketika agen neutron berusaha memulai "
"daemon seperti haproxy dan dnsmasq."

msgid ""
"SSL termination is assumed enabled for all public endpoints by default. If "
"this is not needed it can be disabled by setting the "
"``openstack_external_ssl`` option to **false** and the "
"``openstack_service_publicuri_proto`` to **http**."
msgstr ""
"Pengakhiran SSL diasumsikan diaktifkan untuk semua endpoint publik secara "
"default. Jika ini tidak diperlukan, itu dapat dinonaktifkan dengan mengatur "
"opsi ``openstack_external_ssl`` ke **false** dan "
"``openstack_service_publicuri_proto`` ke **http**."

msgid "SSLv3 is now disabled in the haproxy daemon configuration by default."
msgstr ""
"SSLv3 sekarang dinonaktifkan di konfigurasi daemon haproxy secara default."

msgid ""
"Searching for world-writable files is now disabled by default. The search "
"causes delays in playbook runs and it can consume a significant amount of "
"CPU and I/O resources. Deployers can re-enable the search by setting "
"``security_find_world_writable_dirs`` to ``yes``."
msgstr ""
"Mencari file world-writable sekarang dinonaktifkan secara default. Pencarian "
"menyebabkan keterlambatan dalam menjalankan playbook dan dapat mengkonsumsi "
"sejumlah besar sumber daya CPU dan I/O. Deployer dapat mengaktifkan kembali "
"pencarian dengan mengatur ``security_find_world_writable_dirs`` ke ``yes``."

msgid "Security Issues"
msgstr "Masalah keamanan"

msgid ""
"See `Bug 1702167 <https://bugs.launchpad.net/openstack-ansible/"
"+bug/1702167>`_ for more details."
msgstr ""
"Lihat `Bug 1702167 <https://bugs.launchpad.net/openstack-ansible/"
"+bug/1702167>`_ untuk lebih jelasnya."

msgid ""
"See `Launchpad Bug 1697531 <https://bugs.launchpad.net/openstack-ansible/"
"+bug/1697531>`_ for more details."
msgstr ""
"Lihat `Launchpad Bug 1697531 <https://bugs.launchpad.net/openstack-ansible/"
"+bug/1697531>`_ untuk lebih jelasnya."

msgid ""
"See `Launchpad Bug 1699191 <https://bugs.launchpad.net/openstack-ansible/"
"+bug/1699191>`_ for more details."
msgstr ""
"Lihat `Launchpad Bug 1699191 <https://bugs.launchpad.net/openstack-ansible/"
"+bug/1699191>`_ untuk lebih jelasnya."

msgid ""
"See `bug 1605302 <https://launchpad.net/bugs/1605302>`_ for more details."
msgstr ""
"Lihat `bug 1605302 <https://launchpad.net/bugs/1605302>`_ untuk lebih "
"jelasnya."

msgid ""
"See `bug 1616281 <https://launchpad.net/bugs/1616281>`_ for more details."
msgstr ""
"Lihat `bug 1616281 <https://launchpad.net/bugs/1616281>`_ untuk lebih "
"jelasnya."

msgid ""
"Services deploy into virtual environments by default when the service relies "
"on Python. Find the virtualenv for each service under ``/openstack/venvs/`` "
"on the host or in the container where the service is deployed. Disable the "
"use of virtualenv by overriding the service-specific variable (for example "
"``cinder_venv_enabled``) which defaults to ``True``."
msgstr ""
"Layanan menyebar ke lingkungan virtual secara default ketika layanan "
"bergantung pada Python. Temukan virtualenv untuk setiap layanan di bawah  ``/"
"openstack/venvs/`` pada host atau dalam kontainer tempat layanan tersebut "
"digunakan. Nonaktifkan penggunaan virtualenv dengan mengesampingkan variabel "
"service-specific (misalnya ``cinder_venv_enabled``) yang secara default "
"adalah ``True``."

msgid ""
"Services deploy into virtual environments by default when the service relies "
"on Python. On upgrade any Python packages installed on the host or container "
"are not upgraded with the release unless the virtualenv for that service is "
"disabled. There might be older and possibly broken packages left on the "
"system outside of the virtualenv, which can cause confusion for those who "
"attempt to use Python-based tools or services without using the virtualenv. "
"These left over packages can be manually removed at the operator's "
"discretion."
msgstr ""
"Layanan menyebar ke lingkungan virtual secara default ketika layanan "
"bergantung pada Python. Saat memutakhirkan paket Python apa pun yang "
"diinstal pada host atau kontainer tidak upgraded dengan rilis kecuali jika "
"virtualenv untuk layanan itu dinonaktifkan. Mungkin ada paket yang lebih tua "
"dan mungkin rusak yang tersisa di sistem di luar virtualenv, yang dapat "
"menyebabkan kebingungan bagi mereka yang mencoba menggunakan alat atau "
"layanan berbasis Python tanpa menggunakan virtualenv. Paket yang tersisa ini "
"dapat dihapus secara manual atas kebijakan operator."

msgid ""
"Set ``keystone_mod_wsgi_enabled`` to ``false`` to deploy Keystone under "
"Uwsgi and allow the web server to be bypassed during these tasks."
msgstr ""
"Setel ``keystone_mod_wsgi_enabled`` menjadi ``false`` untuk menggunakan "
"Keystone di bawah Uwsgi dan memungkinkan server web untuk dilewati selama "
"tugas ini."

msgid "Set diff return variable to a dict of changes applied."
msgstr "Setel variabel pengembalian diff ke dict perubahan yang diterapkan."

msgid ""
"Set the ``glance_swift_store_auth_insecure`` variable to override the "
"``swift_store_auth_inscure`` value in ``/etc/glance/glance-api.conf``. Set "
"this value when using an external Swift store that does not have the same "
"``insecure`` setting as the local Keystone."
msgstr ""
"Setel variabel ``glance_swift_store_auth_insecure`` untuk mengganti nilai "
"``swift_store_auth_inscure`` dalam ``/etc/glance/glance-api.conf``. Tetapkan "
"nilai ini saat menggunakan external Swift store yang tidak memiliki "
"pengaturan ``insecure`` yang sama dengan Keystone lokal."

msgid ""
"Setting the haproxy_bind list on a service is now used as an override to the "
"other VIPs defined in the environment. Previously it was being treated as an "
"append to the other VIPs so there was no path to override the VIP binds for "
"a service. For example, haproxy_bind could be used to bind a service to the "
"internal VIP only."
msgstr ""
"Menyetel daftar haproxy_bind pada layanan sekarang digunakan sebagai "
"pengganti bagi VIP lain yang didefinisikan di lingkungan. Sebelumnya itu "
"diperlakukan sebagai tambahan untuk VIP lain sehingga tidak ada jalan untuk "
"mengganti VIP mengikat untuk layanan. Misalnya, haproxy_bind dapat digunakan "
"untuk mengikat layanan ke VIP internal saja."

msgid ""
"Settings related to nginx and the placement will no longer serve any "
"purpose, and should be removed. Those settings are as follows - "
"``nova_placement_nginx_access_log_format_extras``, "
"``nova_placement_nginx_access_log_format_combined``, "
"``nova_placement_nginx_extra_conf``, ``nova_placement_uwsgi_socket_port``, "
"and ``nova_placement_pip_packages``."
msgstr ""
"Pengaturan yang terkait dengan nginx dan penempatan tidak akan lagi melayani "
"tujuan apa pun, dan harus dihapus. Pengaturan tersebut adalah sebagai "
"berikut - ``nova_placement_nginx_access_log_format_extras``, "
"``nova_placement_nginx_access_log_format_combined``, "
"``nova_placement_nginx_extra_conf``, ``nova_placement_uwsgi_socket_port``, "
"dan ``nova_placement_pip_packages``."

msgid ""
"Setup for the PowerVM driver was not properly configuring the system to "
"support RMC configuration for client instances. This fix introduces an "
"interface template for PowerVM that properly supports mixed IPV4/IPV6 "
"deploys and adds documentation for PowerVM RMC. For more information see bug "
"1643988."
msgstr ""
"Pengaturan untuk driver PowerVM tidak mengkonfigurasi sistem dengan benar "
"untuk mendukung konfigurasi RMC untuk instance klien. Perbaikan ini "
"memperkenalkan templat antarmuka untuk PowerVM yang benar mendukung "
"penyebaran IPV4/IPV6 campuran dan menambahkan dokumentasi untuk PowerVM RMC. "
"Untuk informasi lebih lanjut lihat bug 1643988."

msgid ""
"Several ``nova.conf`` options that were deprecated have been removed from "
"the ``os_nova`` role. The following OpenStack-Ansible variables are no "
"longer used and should be removed from any variable override files. * "
"``nova_dhcp_domain`` * ``nova_quota_fixed_ips`` * "
"``nova_quota_floating_ips`` * ``nova_quota_security_group_rules`` * "
"``nova_quota_security_groups``"
msgstr ""
"Beberapa opsi ``nova.conf`` yang sudah usang telah dihapus dari peran "
"``os_nova``. Variabel OpenStack-Ansible berikut tidak lagi digunakan dan "
"harus dihapus dari file override variabel apa pun. * ``nova_dhcp_domain`` * "
"``nova_quota_fixed_ips`` * ``nova_quota_floating_ips`` * "
"``nova_quota_security_group_rules`` * ``nova_quota_security_groups``"

msgid ""
"Several configuration files that were not templated for the "
"``os_ceilometer`` role are now retrieved from git. The git repository used "
"can be changed using the ``ceilometer_git_config_lookup_location`` variable. "
"By default this points to ``git.openstack.org``. These files can still be "
"changed using the ``ceilometer_x_overrides`` variables."
msgstr ""
"Beberapa file konfigurasi yang tidak di-templated untuk role "
"``os_ceilometer`` sekarang diambil dari git. Repositori git yang digunakan "
"dapat diubah menggunakan variabel ``ceilometer_git_config_lookup_location``. "
"Secara default ini menunjuk ke ``git.openstack.org``. File ini masih dapat "
"diubah menggunakan variabel ``ceilometer_x_overrides``."

msgid ""
"Several configuration files that were not templated for the ``os_gnocchi` "
"role are now retrieved from git. The git repository used can be changed "
"using the ``gnocchi_git_config_lookup_location`` variable. By default this "
"points to ``git.openstack.org``. These files can still be changed using the "
"``gnocchi_x_overrides`` variables."
msgstr ""
"Beberapa file konfigurasi yang tidak di-templated untuk role ``os_gnocchi` "
"sekarang diambil dari git. Repositori git yang digunakan dapat diubah "
"menggunakan variabel ``gnocchi_git_config_lookup_location``. Secara default "
"ini menunjuk ke ``git.openstack.org``. File ini masih dapat diubah "
"menggunakan variabel ``gnocchi_x_overrides``."

msgid ""
"Several environment variables have been added in the bootstrapping functions "
"used by the gate-check-commit script. These variables can be used to skip "
"various phases of the bootstrap during the gate-check-commit or bootstrap-"
"ansible script execution."
msgstr ""
"Beberapa variabel lingkungan telah ditambahkan dalam fungsi bootstrap yang "
"digunakan oleh skrip gate-check-commit. Variabel-variabel ini dapat "
"digunakan untuk melewati berbagai fase bootstrap selama eksekusi skrip gate-"
"check-commit atau bootstrap-ansible."

msgid "Simplifies configuration of lbaas-mgmt network."
msgstr "Menyederhanakan konfigurasi jaringan lbaas-mgmt."

msgid ""
"Since we use neutron's credentials to access the queue, security conscious "
"people might want to set up an extra user for octavia on the neutron queue "
"restricted to the topics octavia posts to."
msgstr ""
"Karena kami menggunakan kredensial neutron untuk mengakses queue, orang yang "
"sadar akan keamanan mungkin ingin mengatur pengguna tambahan octavia pada "
"queue neutron terbatas (restricted) pada topik posting octavia"

msgid ""
"Some variables names have been changed to reflect upstream design decisions "
"(such as Nova's default API version), or to provide clarity. These require "
"updating in ``/etc/openstack_deploy/user_*.yml`` for any overrides to "
"continue to work. See the `upgrade documentation <http://docs.openstack.org/"
"developer/openstack-ansible/liberty/upgrade-guide/scripts.html#migrate-"
"openstack-vars-py>` for details."
msgstr ""
"Beberapa nama variabel telah diubah untuk mencerminkan keputusan desain hulu "
"(seperti Nova's default API version),  atau untuk memberikan kejelasan. Ini "
"membutuhkan updating  di ``/etc/openstack_deploy/user_*.yml`` untuk setiap "
"override untuk terus bekerja. Lihat `upgrade documentation <http://docs."
"openstack.org/developer/openstack-ansible/liberty/upgrade-guide/scripts."
"html#migrate-openstack-vars-py>` untuk detailnya."

msgid ""
"Specify the ``gnocchi_auth_mode`` var to set the ``auth_mode`` for gnocchi. "
"This defaults to ``basic`` which has changed from ``noauth`` to match "
"upstream. If ``gnocchi_keystone_auth`` is ``true`` or ``yes`` this value "
"will default to ``keystone``."
msgstr ""
"Tentukan var ``gnocchi_auth_mode`` untuk mengatur ``auth_mode`` untuk "
"gnocchi. Ini default ke ``basic`` yang telah berubah dari ``noauth`` untuk "
"mencocokkan dengan upstream. Jika ``gnocchi_keystone_auth`` menjadi ``true`` "
"atau ``yes`` nilai ini akan default ke ``keystone``."

msgid ""
"Specify the ``gnocchi_git_config_lookup_location`` value to specify the git "
"repository where the ``gnocchi`` config files can be retrieved. The ``api-"
"paste.ini`` and ``policy.json`` files are now retrieved from the specified "
"git repository and are not carried in the ``os_gnocchi`` role."
msgstr ""
"Tentukan nilai ``gnocchi_git_config_lookup_location`` untuk menentukan "
"repositori git di mana file konfigurasi ``gnocchi`` dapat diambil. File "
"``api-paste.ini`` dan ``policy.json`` sekarang diambil dari repositori git "
"yang ditentukan dan tidak dijalankan dalam role ``os_gnocchi``."

msgid ""
"Static route information for provider networks now *must* include the `cidr` "
"and `gateway` information. If either key is missing, an error will be raised "
"and the dynamic_inventory.py script will halt before any Ansible action is "
"taken. Previously, if either key was missing, the inventory script would "
"continue silently without adding the static route information to the "
"networks. Note that this check does not validate the CIDR or gateway values, "
"just just that the values are present."
msgstr ""
"Informasi rute statis untuk jaringan penyedia sekarang  *must* menyertakan "
"informasi `cidr` dan `gateway`. Jika salah satu kunci tidak ada, kesalahan "
"akan dimunculkan dan skrip dynamic_inventory.py akan berhenti sebelum "
"tindakan yang mungkin dilakukan. Sebelumnya, jika salah satu kunci tidak "
"ada, skrip inventaris akan terus diam tanpa menambahkan informasi rute "
"statis ke jaringan. Perhatikan bahwa pemeriksaan ini tidak memvalidasi nilai "
"CIDR atau gateway, hanya saja nilainya ada."

msgid "Stein Series Release Notes"
msgstr "Catatan Rilis Seri Stein"

msgid ""
"Support added to allow deploying on ppc64le architecture using the Ubuntu "
"distributions."
msgstr ""
"Dukungan ditambahkan untuk memungkinkan penggunaan arsitektur ppc64le "
"menggunakan distribusi Ubuntu."

msgid ""
"Support for Neutron distributed virtual routing has been added to the "
"``os_neutron`` role. This includes the implementation of Networking Guide's "
"suggested agent configuration. This feature may be activated by setting "
"``neutron_plugin_type: ml2.ovs.dvr`` in ``/etc/openstack_deploy/"
"user_variables.yml``."
msgstr ""
"Dukungan untuk perutean virtual terdistribusi Neutron telah ditambahkan ke "
"role  ``os_neutron``. Ini termasuk penerapan konfigurasi agen yang "
"disarankan Networking Guide. Fitur ini dapat diaktifkan dengan menetapkan "
"``neutron_plugin_type: ml2.ovs.dvr`` di ``/etc/openstack_deploy/"
"user_variables.yml``."

msgid ""
"Support for openSUSE in Ussuri is moved from fully supported to experimental "
"due to insufficient resources to maintain reliable CI jobs. The zuul jobs "
"are moved to be non-voting. Support will be removed entirely in the Victoria "
"cycle."
msgstr ""
"Dukungan untuk openSUSE di Ussuri dipindahkan dari didukung penuh ke "
"eksperimental karena sumber daya yang tidak mencukupi untuk mempertahankan "
"pekerjaan CI yang andal. Pekerjaan zuul dipindahkan menjadi tidak memilih. "
"Dukungan akan dihapus seluruhnya dalam siklus Victoria."

msgid ""
"Support for the deployment of Unbound caching DNS resolvers has been added "
"as an optional replacement for /etc/hosts management across all hosts in the "
"environment. To enable the Unbound DNS containers, add ``unbound_hosts`` "
"entries to the environment."
msgstr ""
"Dukungan untuk penyebaran resolusi DNS caching tidak terikat telah "
"ditambahkan sebagai pengganti opsional untuk /etc/hosts management di semua "
"host di lingkungan. Untuk mengaktifkan kontainer Unbound DNS, tambahkan "
"entri ``unbound_hosts`` ke lingkungan."

msgid ""
"Support for the networking-generic-switch mechanism driver has been "
"implemented. This allows Ironic to interface with Neutron when the "
"``neutron`` network interface has been configured. This feature may be "
"enabled by adding ``ml2.genericswitch`` to the ``neutron_plugin_types`` list "
"in ``/etc/openstack_deploy/user_variables.yml``."
msgstr ""
"Dukungan untuk driver networking-generic-switch mechanism telah diterapkan. "
"Ini memungkinkan Ironic untuk berinteraksi dengan Neutron ketika antarmuka "
"jaringan ``neutron`` telah dikonfigurasi. Fitur ini dapat diaktifkan dengan "
"menambahkan ``ml2.genericswitch`` ke daftar ``neutron_plugin_types`` di ``/"
"etc/openstack_deploy/user_variables.yml``."

msgid ""
"Support had been added to allow the functional tests to pass when deploying "
"on ppc64le architecture using the Ubuntu distributions."
msgstr ""
"Dukungan telah ditambahkan untuk memungkinkan tes fungsional untuk lulus "
"ketika menggunakan arsitektur ppc64le menggunakan distribusi Ubuntu."

msgid ""
"Support had been added to install the ceph_client packages and dependencies "
"from Ceph.com, Ubuntu Cloud Archive (UCA), or the operating system's default "
"repository."
msgstr ""
"Dukungan telah ditambahkan untuk menginstal paket dan dependensi ceph_client "
"dari Ceph.com, Ubuntu Cloud Archive (UCA), atau repositori default sistem "
"operasi."

msgid ""
"Support has been added for deploying on Ubuntu 18.04 LTS hosts. The most "
"significant change is a major version increment of LXC from 2.x to 3.x which "
"deprecates some previously used elements of the container configuration file."
msgstr ""
"Dukungan telah ditambahkan untuk penggunaan pada host Ubuntu 18.04 LTS. "
"Perubahan paling signifikan adalah peningkatan versi utama LXC dari 2.x "
"menjadi 3.x yang mencela (deprecate) beberapa elemen yang sebelumnya "
"digunakan dari file konfigurasi kontainer."

msgid ""
"Support has been added for the horizon designate-ui dashboard. The dashboard "
"will be automatically enabled if any hosts are in the ``dnsaas_hosts`` "
"inventory group."
msgstr ""
"Dukungan telah ditambahkan untuk dasbor horizon designate-ui. Dasbor akan "
"diaktifkan secara otomatis jika ada host di grup inventory ``dnsaas_hosts``."

msgid ""
"Support has been added for the horizon trove-ui dashboard. The dashboard "
"will be automatically enabled if any hosts are defined in the ``trove-"
"infra_hosts`` inventory group."
msgstr ""
"Dukungan telah ditambahkan untuk dasbor horizon trove-ui. Dasbor akan "
"diaktifkan secara otomatis jika ada host yang ditentukan dalam grup "
"inventory ``trove-infra_hosts``."

msgid ""
"Support has been added to allow the deployment of the OpenStack barbican "
"service when hosts are present in the host group ``key-manager_hosts``."
msgstr ""
"Dukungan telah ditambahkan untuk memungkinkan penyebaran layanan barbican "
"OpenStack ketika host hadir dalam grup host ``key-manager_hosts``."

msgid ""
"Support is added for deploying OpenStack on CentOS 8 with source and distro "
"based installs. However, nspawn support can't be offered, as machinectl "
"relies on btrfs which has been dropped by CentOS."
msgstr ""
"Dukungan ditambahkan untuk menyebarkan OpenStack pada CentOS 8 dengan "
"instalasi berbasis sumber dan distro. Namun, dukungan nspawn tidak dapat "
"ditawarkan, karena machinectl bergantung pada btrf yang telah dijatuhkan "
"oleh CentOS."

msgid ""
"Support is added for deploying OpenStack on Ubuntu Focal (20.04) with source "
"based installs. Ubuntu Cloud Archive is not available for Focal at this "
"point so it is not possible to offer distro package based installs for Focal."
msgstr ""
"Dukungan ditambahkan untuk menyebarkan OpenStack pada Ubuntu Focal (20.04) "
"dengan instalasi berbasis sumber (source based installs). Ubuntu Cloud "
"Archive tidak tersedia untuk Focal pada saat ini sehingga tidak mungkin "
"untuk menawarkan instalasi berbasis paket distro untuk Focal."

msgid ""
"Support of the legacy neutron L3 tool has been dropped. Deployers are "
"appreciated to use built-in l3-agent options for configuring HA."
msgstr ""
"Dukungan legacy neutron L3 tool telah dijatuhkan. Deployers diapresiasi "
"untuk menggunakan opsi built-in l3-agent untuk mengonfigurasi HA."

msgid ""
"Support separate oslo.messaging services for RPC and Notifications to enable "
"operation of separate and different messaging backend servers in aodh."
msgstr ""
"Mendukung layanan oslo.messaging terpisah untuk RPC dan Notification untuk "
"mengaktifkan operasi server backend messaging yang berbeda dan terpisah di "
"aodh."

msgid ""
"Support separate oslo.messaging services for RPC and Notifications to enable "
"operation of separate and different messaging backend servers in barbican."
msgstr ""
"Mendukung layanan oslo.messaging terpisah untuk RPC dan Notification untuk "
"mengaktifkan operasi server backend messaging yang berbeda dan terpisah di "
"barbican."

msgid ""
"Support separate oslo.messaging services for RPC and Notifications to enable "
"operation of separate and different messaging backend servers in ceilometer."
msgstr ""
"Mendukung layanan oslo.messaging terpisah untuk RPC dan Notification untuk "
"mengaktifkan operasi server backend messaging yang berbeda dan terpisah di "
"ceilometer."

msgid ""
"Support separate oslo.messaging services for RPC and Notifications to enable "
"operation of separate and different messaging backend servers in cinder."
msgstr ""
"Mendukung layanan oslo.messaging terpisah untuk RPC dan Notification untuk "
"mengaktifkan operasi server backend messaging yang berbeda dan terpisah di "
"cinder."

msgid ""
"Support separate oslo.messaging services for RPC and Notifications to enable "
"operation of separate and different messaging backend servers in designate."
msgstr ""
"Mendukung layanan oslo.messaging terpisah untuk RPC dan Notification untuk "
"mengaktifkan operasi server backend messaging yang berbeda dan terpisah di "
"designate."

msgid ""
"Support separate oslo.messaging services for RPC and Notifications to enable "
"operation of separate and different messaging backend servers in glance."
msgstr ""
"Mendukung layanan oslo.messaging terpisah untuk RPC dan Notification untuk "
"mengaktifkan operasi server backend messaging yang berbeda dan terpisah di "
"glance."

msgid ""
"Support separate oslo.messaging services for RPC and Notifications to enable "
"operation of separate and different messaging backend servers in heat."
msgstr ""
"Mendukung layanan oslo.messaging terpisah untuk RPC dan Notification untuk "
"mengaktifkan operasi server backend messaging yang berbeda dan terpisah di "
"heat."

msgid ""
"Support separate oslo.messaging services for RPC and Notifications to enable "
"operation of separate and different messaging backend servers in ironic."
msgstr ""
"Mendukung layanan oslo.messaging terpisah untuk RPC dan Notification untuk "
"mengaktifkan operasi server backend messaging yang berbeda dan terpisah di "
"ironic."

msgid ""
"Support separate oslo.messaging services for RPC and Notifications to enable "
"operation of separate and different messaging backend servers in keystone."
msgstr ""
"Mendukung layanan oslo.messaging terpisah untuk RPC dan Notification untuk "
"mengaktifkan operasi server backend messaging yang berbeda dan terpisah di "
"keystone."

msgid ""
"Support separate oslo.messaging services for RPC and Notifications to enable "
"operation of separate and different messaging backend servers in magnum."
msgstr ""
"Mendukung layanan oslo.messaging terpisah untuk RPC dan Notification untuk "
"mengaktifkan operasi server backend messaging yang berbeda dan terpisah di "
"magnum."

msgid ""
"Support separate oslo.messaging services for RPC and Notifications to enable "
"operation of separate and different messaging backend servers in neutron."
msgstr ""
"Mendukung layanan oslo.messaging terpisah untuk RPC dan Notification untuk "
"mengaktifkan operasi server backend messaging yang berbeda dan terpisah di "
"neutron."

msgid ""
"Support separate oslo.messaging services for RPC and Notifications to enable "
"operation of separate and different messaging backend servers in nova."
msgstr ""
"Mendukung layanan oslo.messaging terpisah untuk RPC dan Notification untuk "
"mengaktifkan operasi server backend messaging yang berbeda dan terpisah di "
"nova."

msgid ""
"Support separate oslo.messaging services for RPC and Notifications to enable "
"operation of separate and different messaging backend servers in octavia."
msgstr ""
"Mendukung layanan oslo.messaging terpisah untuk RPC dan Notification untuk "
"mengaktifkan operasi server backend messaging yang berbeda dan terpisah di "
"octavia."

msgid ""
"Support separate oslo.messaging services for RPC and Notifications to enable "
"operation of separate and different messaging backend servers in sahara."
msgstr ""
"Mendukung layanan oslo.messaging terpisah untuk RPC dan Notification untuk "
"mengaktifkan operasi server backend messaging yang berbeda dan terpisah di "
"sahara."

msgid ""
"Support separate oslo.messaging services for RPC and Notifications to enable "
"operation of separate and different messaging backend servers in swift."
msgstr ""
"Mendukung layanan oslo.messaging terpisah untuk RPC dan Notification untuk "
"mengaktifkan operasi server backend messaging yang berbeda dan terpisah di "
"swift."

msgid ""
"Support separate oslo.messaging services for RPC and Notifications to enable "
"operation of separate and different messaging backend servers in trove."
msgstr ""
"Mendukung layanan oslo.messaging terpisah untuk RPC dan Notification untuk "
"mengaktifkan operasi server backend messaging yang berbeda dan terpisah di "
"trove."

msgid ""
"Support separate oslo.messaging services for RPC and Notifications to enable "
"operation of separate and different messaging backend servers."
msgstr ""
"Mendukung layanan oslo.messaging terpisah untuk RPC dan Notifications untuk "
"mengaktifkan operasi messaging backend servers yang terpisah dan berbeda."

msgid ""
"Swift ``versioned_writes`` middleware is added to the pipeline by default. "
"Additionally the ``allow_versioned_writes`` settings in the middleware "
"configuration is set to ``True``. This follows the Swift defaults, and "
"enables the use of the ``X-History-Location`` metadata Header."
msgstr ""
"Middleware Swift ``versioned_writes`` ditambahkan ke pipeline secara "
"default. Selain itu pengaturan ``allow_versioned_writes`` dalam konfigurasi "
"middleware diatur ke ``True``. Ini mengikuti default Swift, dan memungkinkan "
"penggunaan Header metadata ``X-History-Location``."

msgid ""
"Swift container-sync has been updated to use ``internal-client``. This means "
"a new configuration file ``internal-client.conf`` has been added. "
"Configuration can be overridden using the variable "
"``swift_internal_client_conf_overrides``."
msgstr ""
"Sinkronisasi kontainer Swift telah diperbarui untuk menggunakan ``internal-"
"client``. Ini berarti file konfigurasi baru ``internal-client.conf`` telah "
"ditambahkan. Konfigurasi dapat diganti menggunakan variabel "
"``swift_internal_client_conf_overrides``."

msgid ""
"Swift tempauth users now be specified. The ``swift_tempauth_users`` variable "
"can be defined as a list of tempauth users, and their permissions. You will "
"still need to specify the appropriate Swift middleware using the "
"``swift_middleware_list`` variable, in order to utilise tempauth."
msgstr ""
"Pengguna swift tempauth sekarang akan terinci. Variabel "
"``swift_tempauth_users`` dapat didefinisikan sebagai daftar pengguna "
"tempauth, dan izin mereka. Anda masih perlu menentukan middleware Swift yang "
"sesuai menggunakan variabel ``swift_middleware_list``, untuk dapat "
"menggunakan tempauth."

msgid ""
"Systems using systemd (like Ubuntu Xenial) were incorrectly limited to a low "
"amount of open files. This was causing issues when restarting galera. A "
"deployer can still define the maximum number of open files with the variable "
"``galera_file_limits`` (Defaults to 65536)."
msgstr ""
"Sistem yang menggunakan systemd (seperti Ubuntu Xenial) secara tidak benar "
"terbatas pada jumlah file terbuka yang rendah. Ini menyebabkan masalah saat "
"restarting galera. Penyebar masih dapat menentukan jumlah maksimum file "
"terbuka dengan variabel ``galera_file_limits`` (Default ke 65536)."

msgid ""
"TLS certificate chain verification during the download of LXC cached images "
"can now be toggled using the configuration variable "
"'lxc_cache_validate_certs'. The default behavior is to validate the "
"certificate chain."
msgstr ""
"Verifikasi rantai sertifikat TLS selama pengunduhan image yang di-cache LXC "
"sekarang dapat diubah menggunakan variabel konfigurasi "
"'lxc_cache_validate_certs'. Perilaku default adalah untuk memvalidasi rantai "
"sertifikat."

msgid ""
"Tacker role now uses default systemd_service role. Due to this upstart is "
"not supported anymore. Was added variable tacker_init_config_overrides, with "
"wich deployer may override predifined options. Also variable "
"program_override has no effect now, and tacker_service_names was removed in "
"favor of tacker_service_name."
msgstr ""
"Tacker role sekarang menggunakan peran systemd_service default. Karena "
"pemula (upstart) ini tidak didukung lagi. Telah ditambahkan variabel "
"tacker_init_config_overrides, dimana deployer dapat mengganti opsi yang "
"telah ditentukan. Variabel program_override juga tidak berpengaruh sekarang, "
"dan tacker_service_names telah dihapus karena adanya tacker_service_name."

msgid ""
"Tags have been added to all of the common tags with the prefix \"common-\". "
"This has been done to allow a deployer to rapidly run any of the common on a "
"need basis without having to rerun an entire playbook."
msgstr ""
"Tag telah ditambahkan ke semua tag umum dengan awalan \"common-\". Ini telah "
"dilakukan untuk memungkinkan seorang penyebar menjalankan dengan cepat salah "
"satu kesamaan berdasarkan kebutuhan tanpa harus memutarkan kembali seluruh "
"playbook."

msgid ""
"Tasks were added to search for any device files without a proper SELinux "
"label on CentOS systems. If any of these device labels are found, the "
"playbook execution will stop with an error message."
msgstr ""
"Tugas ditambahkan untuk mencari file perangkat apa pun tanpa label SELinux "
"yang tepat pada sistem CentOS. Jika salah satu dari label perangkat ini "
"ditemukan, eksekusi playbook akan berhenti dengan pesan kesalahan."

msgid "That variable would become:"
msgstr "Variabel itu akan menjadi:"

msgid ""
"The 'container_cidr' key has been restored back to openstack_inventory.json "
"The fix to remove deleted global override keys mistakenly deleted the "
"'container_cidr' key, as well. This was used by downstream consumers, and "
"cannot be reconstructed with other information inside the inventory file. "
"Regression tests were also added."
msgstr ""
"Kunci 'container_cidr' telah dipulihkan kembali ke openstack_inventory.json. "
"Perbaikan untuk menghapus kunci global override yang dihapus dengan keliru "
"juga menghapus kunci 'container_cidr'. Ini digunakan oleh konsumen hilir, "
"dan tidak dapat direkonstruksi dengan informasi lain di dalam file "
"inventory. Tes regresi juga ditambahkan."

msgid ""
"The **openstack_hosts** role will setup an RFC1034/5 hostname and create an "
"alias for all hosts in inventory."
msgstr ""
"Peran **openstack_hosts** akan menyiapkan hostname RFC1034/5 dan membuat "
"alias untuk semua host dalam inventaris."

msgid ""
"The Ansible SSH plugin has been modified to support running commands within "
"containers without having to directly ssh into them. The change will detect "
"presence of a container. If a container is found the physical host will be "
"used as the SSH target and commands will be run directly. This will improve "
"system reliability and speed while also opening up the possibility for SSH "
"to be disabled from within the container itself."
msgstr ""
"Plugin SSH Ansible telah dimodifikasi untuk mendukung perintah yang berjalan "
"di dalam kontainer tanpa harus langsung melihatnya. Perubahan akan "
"mendeteksi keberadaan kontainer. Jika sebuah kontainer ditemukan, host fisik "
"akan digunakan sebagai target SSH dan perintah akan dijalankan secara "
"langsung. Ini akan meningkatkan keandalan dan kecepatan sistem sementara "
"juga membuka kemungkinan SSH dinonaktifkan dari dalam kontainer itu sendiri."

msgid ""
"The Aodh data migration script should be run to migrate alarm data from "
"MongoDB storage to Galera due to the pending removal of MongoDB support."
msgstr ""
"Skrip migrasi data Aodh harus dijalankan untuk memigrasi data alarm dari "
"penyimpanan MongoDB ke Galera karena penghentian dukungan MongoDB yang "
"tertunda."

msgid ""
"The COPR repository for installing LXC on CentOS 7 is now set to a higher "
"priority than the default to ensure that LXC packages always come from the "
"COPR repository."
msgstr ""
"Repositori COPR untuk menginstal LXC pada CentOS 7 sekarang diatur ke "
"prioritas yang lebih tinggi daripada default untuk memastikan bahwa paket "
"LXC selalu berasal dari repositori COPR."

msgid ""
"The Ceilometer API is no longer available in the Queens release of "
"OpenStack, this patch removes all references to API related configurations "
"as they are no longer needed."
msgstr ""
"Ceilometer API tidak lagi tersedia dalam rilis OpenStack Queens, patch ini "
"menghapus semua referensi untuk konfigurasi terkait API karena mereka tidak "
"lagi diperlukan."

msgid ""
"The Ceph stable release used by openstack-ansible and its ceph-ansible "
"integration has been changed to the recent `Ceph LTS <http://ceph.com/"
"releases/v12-2-0-luminous-released/>`_ Luminous release."
msgstr ""
"Rilis stabil Ceph yang digunakan oleh openstack-ansible dan integrasi ceph-"
"ansible telah diubah ke yang terbaru `Ceph LTS <http://ceph.com/releases/"
"v12-2-0-luminous-released/>`_ Luminous release."

msgid ""
"The Datagram Congestion Control Protocol (DCCP) kernel module is now "
"disabled by default, but a reboot is required to make the change effective."
msgstr ""
"Modul kernel Datagram Congestion Control Protocol (DCCP) sekarang "
"dinonaktifkan secara default, tetapi reboot diperlukan untuk membuat "
"perubahan efektif."

msgid "The Designate V1 API has been removed, and cannot be enabled."
msgstr "Designate V1 API telah dihapus, dan tidak dapat diaktifkan."

msgid ""
"The Designate pools.yaml file can now be generated via the "
"designate_pools_yaml attribute, if desired. This ability is toggled by the "
"designate_use_pools_yaml_attr attribute. In the future this behavior may "
"become default and designate_pools_yaml may become a required variable."
msgstr ""
"File pools.yaml Designate sekarang dapat dihasilkan melalui atribut "
"designate_pools_yaml, jika diinginkan. Kemampuan ini diaktifkan oleh atribut "
"designate_use_pools_yaml_attr. Di masa depan perilaku ini dapat menjadi "
"default dan designate_pools_yaml dapat menjadi variabel yang diperlukan."

msgid ""
"The Designate pools.yaml file can now be generated via the "
"designate_pools_yaml attribute, if desired. This allows users to populate "
"the Designate DNS server configuration using attributes from other plays and "
"obviates the need to manage the file outside of the Designate role."
msgstr ""
"File pools.yaml Designate sekarang dapat dihasilkan melalui atribut "
"designate_pools_yaml, jika diinginkan. Hal ini memungkinkan pengguna untuk "
"mengisi konfigurasi server Designate DNS menggunakan atribut dari play lain "
"dan meniadakan kebutuhan untuk mengelola file di luar peran Designate."

msgid "The EPEL repository is now removed in favor of the RDO repository."
msgstr "Repositori EPEL sekarang dihapus demi repositori RDO."

msgid ""
"The EPEL repository is only installed and configured when the deployer sets "
"``security_enable_virus_scanner`` to ``yes``. This allows the ClamAV "
"packages to be installed. If ``security_enable_virus_scanner`` is set to "
"``no`` (the default), the EPEL repository will not be added."
msgstr ""
"Repositori EPEL hanya diinstal dan dikonfigurasikan ketika deployer "
"menetapkan ``security_enable_virus_scanner`` menjadi ``yes``. Ini "
"memungkinkan paket ClamAV diinstal. Jika ``security_enable_virus_scanner`` "
"diatur ke ``no`` (default), repositori EPEL tidak akan ditambahkan."

msgid ""
"The GPG key checks for package verification in V-38476 are now working for "
"Red Hat Enterprise Linux 7 in addition to CentOS 7. The checks only look for "
"GPG keys from Red Hat and any other GPG keys, such as ones imported from the "
"EPEL repository, are skipped."
msgstr ""
"Pemeriksaan kunci GPG untuk verifikasi paket di V-38476 sekarang berfungsi "
"untuk Red Hat Enterprise Linux 7 selain CentOS 7. Pemeriksaan hanya mencari "
"kunci GPG dari Red Hat dan kunci GPG lainnya, seperti yang diimpor dari "
"repositori EPEL , dilewati."

msgid ""
"The Galera client role now has a dependency on the apt package pinning role."
msgstr ""
"Peran klien Galera sekarang memiliki ketergantungan pada peran menyematkan "
"(pinning)  paket apt."

msgid ""
"The Galera installation process has been optimized and takes less time to "
"complete."
msgstr ""
"Proses instalasi Galera telah dioptimalkan dan membutuhkan waktu lebih "
"sedikit untuk menyelesaikannya."

msgid ""
"The HAProxy role provided by OpenStack-Ansible now terminates SSL using a "
"self-signed certificate by default. While this can be disabled the inclusion "
"of SSL services on all public endpoints as a default will help make "
"deployments more secure without any additional user interaction. More "
"information on SSL and certificate generation can be `found here <http://"
"docs.openstack.org/developer/openstack-ansible/install-guide/configure-"
"haproxy.html#securing-haproxy-communication-with-ssl-certificates>`_."
msgstr ""
"Peran HAProxy yang disediakan oleh OpenStack-Ansible sekarang mengakhiri SSL "
"menggunakan sertifikat yang ditandatangani sendiri secara default. Meskipun "
"hal ini dapat dinonaktifkan, dimasukkannya layanan SSL di semua endpoint "
"publik sebagai standar akan membantu membuat penyebaran lebih aman tanpa "
"interaksi pengguna tambahan. Informasi lebih lanjut tentang SSL dan "
"pembuatan sertifikat dapat `found here <http://docs.openstack.org/developer/"
"openstack-ansible/install-guide/configure-haproxy.html#securing-haproxy-"
"communication-with-ssl-certificates>`_."

msgid ""
"The Keystone configuration has been updated for liberty. Several variables "
"that may appear in the ``user_config.yml`` file may need to be updated.  "
"Those variables include:"
msgstr ""
"Konfigurasi Keystone telah diperbarui untuk kebebasan. Beberapa variabel "
"yang mungkin muncul dalam file ``user_config.yml`` mungkin perlu diperbarui. "
"Variabel tersebut meliputi:"

msgid ""
"The Kilo upgrade playbook `glance-db-storage-url-fix.yml` to Liberty will "
"migrate all existing Swift backed Glance images inside the image_locations "
"database table from a Keystone v2 API URL to a v3 URL. This will force the "
"Swift client to operate against a v3 Keystone URL. A backup of the old "
"image_locations table is stored inside a new database table "
"`image_locations_keystone_v3_mig_pre_liberty` and can be safely removed "
"after a successfull upgrade to Liberty."
msgstr ""
"Playbook upgrade Kilo `glance-db-storage-url-fix.yml` ke Liberty akan "
"memigrasikan semua image Glance yang didukung Swift di dalam tabel database "
"image_locations dari Keystone v2 API URL ke v3 URL. Ini akan memaksa klien "
"Swift untuk beroperasi melawan URL v3 Keystone. Cadangan tabel "
"image_locations lama disimpan di dalam tabel database baru "
"`image_locations_keystone_v3_mig_pre_liberty` dan dapat dihapus dengan aman "
"setelah upgrade yang berhasil ke Liberty."

msgid ""
"The LBaaSv2 device driver is now set by the Ansible variable "
"``neutron_lbaasv2_device_driver``. The default is set to use the "
"``HaproxyNSDriver``, which allows for agent-based load balancers."
msgstr ""
"Driver perangkat LBaaSv2 sekarang diatur oleh variabel Ansible "
"``neutron_lbaasv2_device_driver``.   Default diatur untuk menggunakan "
"``HaproxyNSDriver``, yang memungkinkan penyeimbang beban berbasis agen."

msgid ""
"The LBaaSv2 service provider configuration can now be adjusted with the "
"``neutron_lbaasv2_service_provider`` variable. This allows a deployer to "
"choose to deploy LBaaSv2 with Octavia in a future version."
msgstr ""
"Konfigurasi penyedia layanan LBaaSv2 sekarang dapat disesuaikan dengan "
"variabel ``neutron_lbaasv2_service_provider``. Ini memungkinkan seorang "
"penggelar untuk memilih untuk menggunakan LBaaSv2 dengan Octavia di versi "
"masa depan."

msgid ""
"The LVM configuration tasks and ``lvm.conf`` template have been removed from "
"the ``openstack_hosts`` role since they are no longer needed. All of the LVM "
"configuration is properly handled in the ``os_cinder`` role."
msgstr ""
"Tugas konfigurasi LVM dan template ``lvm.conf`` telah dihapus dari peran "
"``openstack_hosts`` karena tidak lagi diperlukan. Semua konfigurasi LVM "
"ditangani dengan benar dalam peran ``os_cinder``."

msgid ""
"The LXC container cache preparation process now copies DNS resolution "
"configuration from the host instead of implementing its own configuration. "
"The ``lxc_cache_resolvers`` variable is therefore unnecessary and has been "
"removed."
msgstr ""
"Proses persiapan cache kontainer LXC sekarang menyalin konfigurasi resolusi "
"DNS dari host daripada mengimplementasikan konfigurasinya sendiri. Variabel "
"``lxc_cache_resolvers`` karena itu tidak perlu dan telah dihapus."

msgid ""
"The LXC container cache preparation process now copies package repository "
"configuration from the host instead of implementing its own configuration. "
"The following variables are therefore unnecessary and have been removed:"
msgstr ""
"Proses persiapan cache kontainer LXC sekarang menyalin konfigurasi "
"repositori paket dari host daripada mengimplementasikan konfigurasinya "
"sendiri. Karena itu variabel berikut ini tidak perlu dan telah dihapus:"

msgid ""
"The LXC container create option `lxc_container_backing_store` is now defined "
"by default and has a value of \"dir\". Prior to this release the backend "
"store option was using several auto-detection methods to try and guess the "
"store type based on facts fed into the role and derived from the physical "
"host. While the auto-detection methods worked, they created a cumbersome set "
"of conditionals and limited our ability to leverage additional container "
"stores. Having this option be a default allows deployers to mix and match "
"container stores to suit the needs of the deployment. Existing deployments "
"should set this option within group or user variables to ensure there's no "
"change in the backend store when new container be provisioned."
msgstr ""
"LXC container create option `lxc_container_backing_store` sekarang "
"didefinisikan secara default dan memiliki nilai \"dir\". Sebelum rilis ini "
"opsi backend store menggunakan beberapa metode deteksi otomatis untuk "
"mencoba dan menebak jenis store berdasarkan fakta dimasukkan ke dalam peran "
"dan berasal dari host fisik. Sementara metode deteksi otomatis bekerja, "
"mereka menciptakan serangkaian persyaratan dan membatasi kemampuan kami "
"untuk memanfaatkan store kontainer tambahan. Dengan menetapkan opsi ini "
"sebagai bawaan, memungkinkan para penyebar untuk mencampur dan mencocokkan "
"store kontainer agar sesuai dengan kebutuhan penyebaran. Penempatan yang ada "
"harus menetapkan opsi ini dalam variabel grup atau pengguna untuk memastikan "
"tidak ada perubahan di penyimpanan backend ketika kontainer baru disediakan."

msgid ""
"The LXC container create role will now check for the LXC volume group if the "
"option `lxc_container_backing_store` is set to \"lvm\". If this volume group "
"is not found, the role will halt and instruct the deployer to update their "
"configuration options and inspect their host setup."
msgstr ""
"LXC container create role sekarang akan memeriksa grup volume LXC jika opsi "
"`lxc_container_backing_store` diatur ke \"lvm\". Jika grup volume ini tidak "
"ditemukan, role akan berhenti dan menginstruksikan penyebar untuk "
"memperbarui opsi konfigurasi mereka dan memeriksa pengaturan host mereka."

msgid ""
"The LXC container creation and modification process now supports online "
"network additions. This ensures a container remains online when additional "
"networks are added to a system."
msgstr ""
"Proses pembuatan dan modifikasi kontainer LXC sekarang mendukung penambahan "
"jaringan online. Ini memastikan wadah tetap online ketika jaringan ekstra "
"ditambahkan ke sistem."

msgid ""
"The LXC container creation process now has a configurable delay for the task "
"which waits for the container to start. The variable "
"``lxc_container_ssh_delay`` can be set to change the default delay of five "
"seconds."
msgstr ""
"Proses pembuatan kontainer LXC sekarang memiliki penundaan yang dapat "
"dikonfigurasi untuk tugas yang menunggu kontainer untuk memulai. Variabel "
"``lxc_container_ssh_delay`` dapat diatur untuk mengubah penundaan default "
"lima detik."

msgid ""
"The Linux Security Module (LSM) that is appropriate for the Linux "
"distribution in use will be automatically enabled by the security role by "
"default. Deployers can opt out of this change by setting the following "
"Ansible variable:"
msgstr ""
"Linux Security Module (LSM) yang sesuai untuk distribusi Linux yang "
"digunakan akan secara otomatis diaktifkan oleh peran keamanan secara "
"default. Deployer dapat menyisih dari perubahan ini dengan mengatur variabel "
"Ansible berikut:"

msgid ""
"The LinuxBridge configuration that was in ``plugins/ml2/ml2_conf.ini`` is "
"now found in ``plugins/ml2/linuxbridge_agent.ini``."
msgstr ""
"Konfigurasi LinuxBridge yang ada di ``plugins/ml2/ml2_conf.ini`` sekarang "
"ditemukan di``plugins/ml2/linuxbridge_agent.ini``."

msgid "The MariaDB version has been bumped to 10.2"
msgstr "Versi MariaDB telah dinaikkan ke 10.2"

msgid ""
"The MariaDB wait_timeout setting is decreased to 1h to match the SQL Alchemy "
"pool recycle timeout, in order to prevent unnecessary database session "
"buildups."
msgstr ""
"Pengaturan wait_timeout MariaDB dikurangi menjadi 1 jam agar sesuai dengan "
"batas waktu daur ulang kumpulan (pool) Alchemy SQL, untuk mencegah "
"penumpukan (buildup)  sesi basis data yang tidak perlu."

msgid ""
"The Neutron HA tool written by AT&T has been deprecated and will be removed "
"in the Ocata release."
msgstr ""
"Alat Neutron HA yang ditulis oleh AT&T telah ditinggalkan dan akan dihapus "
"dalam rilis Ocata."

msgid ""
"The Neutron HA tool written by AT&T is no longer enabled by default. This "
"tool was providing HA capabilities for networks and routers that were not "
"using the native Neutron L3HA. Because native Neutron L3HA is stable, "
"compatible with the Linux Bridge Agent, and is a better means of enabling HA "
"within a deployment this tool is no longer being setup by default. If legacy "
"L3HA is needed within a deployment the deployer can set "
"`neutron_legacy_ha_tool_enabled` to **true** to enable the legacy tooling."
msgstr ""
"Alat Neutron HA yang ditulis oleh AT&T tidak lagi diaktifkan secara default. "
"Alat ini menyediakan kemampuan HA untuk jaringan dan router yang tidak "
"menggunakan Neutron L3HA asli (native). Karena Neutron L3HA asli stabil, "
"kompatibel dengan Linux Bridge Agent, dan merupakan cara yang lebih baik "
"untuk mengaktifkan HA dalam penyebaran, alat ini tidak lagi diatur secara "
"default. Jika legacy L3HA diperlukan dalam penyebaran, maka deployer dapat "
"mengatur `neutron_legacy_ha_tool_enabled` ke **true** untuk mengaktifkan "
"tool legacy."

msgid ""
"The Neutron L3 Agent configuration for the handle_internal_only_routers "
"variable is removed in order to use the Neutron upstream default setting. "
"The current default for handle_internal_only_routers is True, which does "
"allow Neutron L3 router without external networks attached (as discussed per "
"https://bugs.launchpad.net/neutron/+bug/1572390)."
msgstr ""
"Konfigurasi Neutron L3 Agent untuk variabel handle_internal_only_routers "
"dihapus untuk menggunakan pengaturan default hulu Neutron. Default saat ini "
"untuk handle_internal_only_routers adalah True, yang memungkinkan router "
"Neutron L3 tanpa jaringan eksternal terpasang (seperti yang dibahas per "
"https://bugs.launchpad.net/neutron/+bug/1572390)."

msgid ""
"The Neutron Service Function Chaining Extension (SFC) can optionally be "
"deployed and configured by defining the following service plugins:"
msgstr ""
"Service Function Chaining Extension (SFC) Neutron dapat secara opsional "
"digunakan dan dikonfigurasikan dengan mendefinisikan plugin layanan berikut:"

msgid ""
"The Nova 2.1 variables (``nova_v21_<variable>``), Heat name variables "
"( ``heat_project_domain_name``, ``heat_user_domain``) and Galera SST Method "
"(``galera_sst_method``) variables have changed. See the `upgrade "
"documentation <http://docs.openstack.org/developer/openstack-ansible/liberty/"
"upgrade-guide/scripts.html#migrate-openstack-vars-py>` for details."
msgstr ""
"Variabel Nova 2.1 (``nova_v21_<variable>``), variabel nama heat "
"(``heat_project_domain_name``, ``heat_user_domain``) dan variabel Galera SST "
"Method (``galera_sst_method``) telah berubah. Lihat `upgrade documentation "
"<http://docs.openstack.org/developer/openstack-ansible/liberty/upgrade-guide/"
"scripts.html#migrate-openstack-vars-py>` untuk detailnya."

msgid ""
"The Nova project has set the v2.1 API as the default and those configuration "
"variables have changed.  Variables that began with ``nova_v21_*`` in the "
"Kilo release are now renamed to ``nova_*``. All new Liberty deployments will "
"have only the v2.1 API registered in the service catalog."
msgstr ""
"Proyek Nova telah menetapkan API v2.1 sebagai default dan variabel "
"konfigurasi tersebut telah berubah. Variabel yang dimulai dengan "
"``nova_v21_*`` dalam rilis Kilo sekarang diubah namanya menjadi ``nova_*``. "
"Semua penyebaran Liberty baru hanya akan memiliki API v2.1 terdaftar di "
"katalog layanan."

msgid ""
"The PATH environment variable that is configured on the remote system can "
"now be set using the ``openstack_host_environment_path`` list variable."
msgstr ""
"Variabel lingkungan PATH yang dikonfigurasi pada sistem jarak jauh sekarang "
"dapat diatur menggunakan variabel daftar ``openstack_host_environment_path``."

msgid ""
"The PKI-based authentication checks for RHEL-07-040030, RHEL-07-040040, and "
"RHEL-07-040050 are no longer included in the RHEL 7 STIG. The tasks and "
"documentation for these outdated configurations are removed."
msgstr ""
"Otentikasi berbasis PKI memeriksa RHEL-07-040030, RHEL-07-040040, dan "
"RHEL-07-040050 tidak lagi termasuk dalam RHEL 7 STIG. Tugas dan dokumentasi "
"untuk konfigurasi yang lama ini dihapus."

msgid ""
"The PermitRootLogin in sshd_config changed from 'yes' to 'prohibit-password' "
"in the containers. By default there is no password set in the containers but "
"the ssh pub key from the deployment host is injected in the targets nodes "
"authorized_keys."
msgstr ""
"PermitRootLogin di sshd_config berubah dari 'yes' menjadi  'prohibit-"
"password' di kontainer. Secara default tidak ada password yang diatur dalam "
"kontainer tetapi kunci ssh pub dari deployment host disuntikkan dalam node "
"target authorized_keys."

msgid ""
"The PowerVM driver has been removed as it is not tested and it has been "
"broken since late 2016 due to the driver name being renamed to powervm_ext "
"instead of powervm."
msgstr ""
"Driver PowerVM telah dihapus karena tidak diuji dan telah rusak sejak akhir "
"2016 karena nama driver diubah namanya menjadi powervm_ext bukan powervm."

msgid ""
"The Project Calico Neutron networking plugin is now integrated into the "
"``os_neutron`` role. This can be activated using the instructions located in "
"the role documentation."
msgstr ""
"Plugin jaringan Project Calico Neutron sekarang terintegrasi ke dalam peran "
"``os_neutron``. Ini dapat diaktifkan menggunakan instruksi yang ada di "
"dokumentasi peran."

msgid ""
"The Project Calico Neutron networking plugin is now integrated into the "
"deployment. For setup instructions please see ``os_neutron`` role "
"documentation."
msgstr ""
"Plugin jaringan Project Calico Neutron sekarang terintegrasi ke dalam "
"deployment. Untuk instruksi pengaturan silakan lihat dokumentasi peran "
"``os_neutron``."

msgid ""
"The RabbitMQ Management UI is now available through HAProxy on port 15672. "
"The default userid is ``monitoring``. This user can be modified by changing "
"the parameter ``rabbitmq_monitoring_userid`` in the file ``user_variables."
"yml``. Please note that ACLs have been added to this HAProxy service by "
"default, such that it may only be accessed by common internal clients.  "
"Reference ``playbooks/vars/configs/haproxy_config.yml``"
msgstr ""
"RabbitMQ Management UI sekarang tersedia melalui HAProxy pada port 15672. "
"Userid default adalah ``monitoring``. User ini dapat dimodifikasi dengan "
"mengubah parameter ``rabbitmq_monitoring_userid`` dalam file "
"``user_variables.yml``. Harap dicatat bahwa ACL telah ditambahkan ke layanan "
"HAProxy ini secara default, sehingga hanya dapat diakses oleh klien internal "
"umum. Referensi ``playbooks/vars/configs/haproxy_config.yml``"

msgid ""
"The Red Hat Enteprise Linux 6 STIG content has been deprecated. The tasks "
"and variables for the RHEL 6 STIG will be removed in a future release."
msgstr ""
"Konten Red Hat Enterprise Linux 6 STIG telah ditinggalkan. Tugas dan "
"variabel untuk RHEL 6 STIG akan dihapus dalam rilis mendatang."

msgid ""
"The Red Hat Enterprise Linux (RHEL) 7 STIG content is now deployed by "
"default. Deployers can continue using the RHEL 7 STIG content by setting the "
"following Ansible variable:"
msgstr ""
"Konten Red Hat Enterprise Linux (RHEL) 7 STIG sekarang digunakan secara "
"default. Deployer dapat terus menggunakan konten RHEL 7 STIG dengan mengatur "
"variabel Ansible berikut:"

msgid ""
"The RyuBgpDriver is no longer available and replaced by the OsKenBgpDriver "
"of the neutron_dynamic_routing project."
msgstr ""
"RyuBgpDriver tidak lagi tersedia dan digantikan oleh OsKenBgpDriver dari "
"proyek neutron_dynamic_routing."

msgid ""
"The S3, v3, and EC2 API's have been deprecated by the Nova project in the "
"liberty release.  Those variables have been removed.  They include variables "
"that begin with ``nova_s3_*``, ``nova_ec2_*``, and ``nova_v3_*``."
msgstr ""
"API S3, v3, dan EC2 telah ditinggalkan oleh proyek Nova dalam rilis liberty. "
"Variabel itu telah dihapus. Mereka termasuk variabel yang dimulai dengan "
"``nova_s3_*``, ``nova_ec2_*``, dan ``nova_v3_*``."

msgid ""
"The Sahara dashboard is available in Horizon. Deployers can enable the panel "
"by setting the following Ansible variable:"
msgstr ""
"Dasbor Sahara tersedia di Horizon. Deployer dapat mengaktifkan panel dengan "
"mengatur variabel Ansible berikut:"

msgid ""
"The Trove dashboard is available in Horizon. Deployers can enable the panel "
"by setting the following Ansible variable:"
msgstr ""
"Dasbor Trove tersedia di Horizon. Deployer dapat mengaktifkan panel dengan "
"mengatur variabel Ansible berikut:"

msgid ""
"The URL of NovaLink uses 'ftp' protocol to provision apt key. It causes "
"apt_key module to fail to retrieve NovaLink gpg public key file. Therefore, "
"change the protocol of URL to 'http'. For more information, see bug 1637348."
msgstr ""
"URL NovaLink menggunakan protokol 'ftp' untuk menyediakan kunci apt. Itu "
"menyebabkan modul apt_key gagal mengambil file kunci publik NovaLink gpg. "
"Karena itu, ubah protokol URL menjadi 'http'. Untuk informasi lebih lanjut, "
"lihat bug 1637348."

msgid ""
"The XFS filesystem is excluded from the daily mlocate crond job in order to "
"conserve disk IO for large IOPS bursts due to updatedb/mlocate file indexing."
msgstr ""
"Sistem file XFS dikecualikan dari mlocate crond job harian untuk menghemat "
"disk IOPS untuk semburan (burst) IOPS besar karena pengindeksan file "
"updatedb/mlocate."

msgid ""
"The ``--check`` parameter for ``dynamic_inventory.py`` will now raise "
"warnings if there are any groups defined in the user configuration that are "
"not also found in the environment definition."
msgstr ""
"Parameter ``--check`` untuk ``dynamic_inventory.py`` sekarang akan "
"memunculkan peringatan jika ada grup yang ditentukan dalam konfigurasi "
"pengguna yang tidak juga ditemukan dalam definisi lingkungan."

msgid ""
"The ``--compact`` flag has been removed from xtrabackup options. This had "
"been shown to cause crashes in some SST situations"
msgstr ""
"Flag ``--compact`` telah dihapus dari opsi xtrabackup. Ini telah terbukti "
"menyebabkan crash dalam beberapa situasi SST"

msgid ""
"The ``/run`` directory is excluded from AIDE checks since the files and "
"directories there are only temporary and often change when services start "
"and stop."
msgstr ""
"Direktori ``/run`` dikecualikan dari pemeriksaan AIDE karena file dan "
"direktori hanya ada sementara dan sering berubah ketika layanan mulai dan "
"berhenti."

msgid ""
"The ``/var/lib/libvirt/qemu/save`` directory is now a symlink to "
"``{{ nova_system_home_folder }}/save`` to resolve an issue where the default "
"location used by the libvirt managed save command can result with the root "
"partitions on compute nodes becoming full when ``nova image-create`` is run "
"on large instances."
msgstr ""
"Direktori  ``/var/lib/libvirt/qemu/save`` sekarang menjadi symlink ke "
"``{{ nova_system_home_folder }}/save`` untuk menyelesaikan masalah di mana "
"lokasi default yang digunakan oleh perintah libvirt managed save dapat "
"dihasilkan dengan partisi root pada compute nodes menjadi penuh ketika "
"``nova image-create`` dijalankan pada instance besar."

msgid ""
"The ``[boto]`` section of tempest.conf.j2 has been removed.  These tests "
"have been completely removed from tempest for some time."
msgstr ""
"Bagian ``[boto]`` dari tempest.conf.j2 telah dihapus. Tes ini telah "
"sepenuhnya dihapus dari tempest selama beberapa waktu."

msgid ""
"The ``ansible-role-requirements.yml`` reference to the ``ceph-ansible`` role "
"has been fixed to refer to the current ``HEAD`` of that role's "
"``stable-3.1`` branch. It previously pointed to the pre-release 3.2.0beta1 "
"version."
msgstr ""
"Referensi ``ansible-role-requirements.yml`` untuk peran ``ceph-ansible`` "
"telah diperbaiki untuk merujuk ke ``HEAD`` saat ini dari branch "
"``stable-3.1`` peran itu. Ini sebelumnya menunjuk ke versi 3.2.0beta1 pra-"
"rilis."

msgid ""
"The ``aodh_keystone_auth_plugin`` variable has been deprecated. "
"``aodh_keystone_auth_type`` should be used instead to configure "
"authentication type."
msgstr ""
"Variabel ``aodh_keystone_auth_plugin`` telah ditinggalkan. "
"``aodh_keystone_auth_type`` harus digunakan sebagai gantinya untuk "
"mengkonfigurasi tipe otentikasi."

msgid ""
"The ``ca-certificates`` package has been included in the LXC container build "
"process in order to prevent issues related to trying to connect to public "
"websites which make use of newer certificates than exist in the base CA "
"certificate store."
msgstr ""
"Paket ``ca-certificates`` telah dimasukkan dalam proses pembuatan kontainer "
"LXC untuk mencegah masalah yang terkait dengan mencoba terhubung ke situs "
"web publik yang menggunakan sertifikat yang lebih baru daripada yang ada di "
"store sertifikat CA dasar."

msgid ""
"The ``ceilometer-api`` init service is removed since ``ceilometer-api`` is "
"deployed as an apache ``mod_wsgi`` service."
msgstr ""
"Layanan ``ceilometer-api`` init dihapus karena ``ceilometer-api`` digunakan "
"sebagai layanan apache ``mod_wsgi``."

msgid ""
"The ``ceilometer_gnocci_resources_yaml_overrides`` variable is deprecated "
"and scheduled for removal in the Pike cycle. This is replaced with the "
"correctly spelled variable, which should now be used "
"``ceilometer_gnocchi_resources_yaml_overrides``."
msgstr ""
"Variabel ``ceilometer_gnocci_resources_yaml_overrides`` sudah usang dan "
"dijadwalkan untuk dihapus dalam siklus Pike. Ini diganti dengan variabel "
"yang dieja dengan benar, yang sekarang harus digunakan "
"``ceilometer_gnocchi_resources_yaml_overrides``."

msgid ""
"The ``ceilometer_keystone_auth_plugin`` variable has been deprecated. "
"``ceilometer_keystone_auth_type`` should be used instead to configure "
"authentication type."
msgstr ""
"Variabel ``ceilometer_keystone_auth_plugin`` telah ditinggalkan. "
"``ceilometer_keystone_auth_type`` harus digunakan sebagai gantinya untuk "
"mengkonfigurasi tipe otentikasi."

msgid ""
"The ``ceph-ansible`` individual role repositories were all removed from "
"github on around 16 January 2019, causing the bootstrap-ansible script to "
"fail for any new deployments, or during upgrades for environments which had "
"these roles previously. To replace them, the ``ceph-ansible`` git repository "
"is used instead."
msgstr ""
"Repositori peran individu ``ceph-ansible`` semua dihapus dari github pada "
"sekitar 16 Januari 2019, menyebabkan skrip yang memungkinkan bootstrap gagal "
"untuk penyebaran apa pun, atau selama peningkatan untuk lingkungan yang "
"memiliki peran ini sebelumnya. Untuk menggantinya, repositori git ``ceph-"
"ansible`` digunakan sebagai gantinya."

msgid ""
"The ``ceph-ansible`` individual role repositories were all removed from "
"github on around 16 January 2019, causing the bootstrap-ansible script to "
"fail for any new deployments, or during upgrades for environments which had "
"these roles previously. To replace them, the ``ceph-ansible`` git repository "
"is used instead. In order to prevent clashes between the old and new roles, "
"the existing ``/etc/ansible/roles/ceph*`` folders should be removed prior to "
"running ``scripts/bootstrap-ansible.sh`` during the minor upgrade process."
msgstr ""
"Repositori peran individu ``ceph-ansible`` semua dihapus dari github pada "
"sekitar 16 Januari 2019, menyebabkan skrip yang memungkinkan bootstrap gagal "
"untuk penyebaran apa pun, atau selama peningkatan untuk lingkungan yang "
"memiliki peran ini sebelumnya. Untuk menggantinya, repositori git ``ceph-"
"ansible`` digunakan sebagai gantinya. Untuk mencegah bentrokan antara peran "
"lama dan baru, folder  ``/etc/ansible/roles/ceph*`` yang ada harus dihapus "
"sebelum menjalankan ``scripts/bootstrap-ansible.sh`` selama proses "
"peningkatan minor. ."

msgid ""
"The ``ceph-rgw`` playbooks now include the ``AUTH_%(tenant_id)s`` suffix in "
"the Keystone ``object-store`` endpoint. This aligns radosgw's behavior with "
"that of native Swift. It also enables radosgw to support public read ACLs on "
"containers, and temporary URLs on objects, in the same way that Swift does "
"(`bug 1800637 <https://bugs.launchpad.net/openstack-ansible/+bug/1800637>`_)."
msgstr ""
"Playbook ``ceph-rgw`` sekarang menyertakan akhiran ``AUTH_%(tenant_id)s``` "
"di endpoint ``object-store`` Keystone. Ini menyelaraskan perilaku radosgw "
"dengan perilaku Swift native. Ini juga memungkinkan radosgw untuk mendukung "
"ACL membaca publik pada kontainer, dan URL sementara pada objek, dengan cara "
"yang sama seperti yang dilakukan Swift (`bug 1800637 <https://bugs.launchpad."
"net/openstack-ansible/+bug/1800637>` _)."

msgid ""
"The ``ceph-rgw`` playbooks now set ``rgw_swift_account_in_url = true`` and "
"update the corresponding Keystone service catalog entry accordingly. "
"Applications (such as monitoring scripts) that do *not* rely on service "
"catalog lookup must be updated with the new endpoint URL that includes "
"``AUTH_%(tenant_id)s`` just like native Swift does --- or, alternatively, "
"should be updated to honor the service catalog after all."
msgstr ""
"Playbook ``ceph-rgw`` sekarang menetapkan ``rgw_swift_account_in_url = "
"true`` dan update entri katalog layanan Keystone yang sesuai. Aplikasi "
"(seperti monitoring script) yang *not* mengandalkan pencarian katalog "
"layanan harus diperbarui dengan URL endpoint baru yang mencakup  ``AUTH_"
"%(tenant_id)s`` seperti halnya yang dilakukan swift native --- atau, jika "
"tidak, harus diperbarui untuk menghormati katalog layanan bagaimanapun."

msgid ""
"The ``ceph-rgw`` playbooks now set ``rgw_swift_versioning_enabled = true``, "
"adding support for object versioning for the ``object-store`` service."
msgstr ""
"Playbook ``ceph-rgw`` sekarang mengatur ``rgw_swift_versioning_enabled = "
"true``, menambahkan dukungan object versioning untuk layanan ``object-"
"store``."

msgid ""
"The ``ceph_pkg_source`` variable controls the install source for the Ceph "
"packages. Valid values include:"
msgstr ""
"Variabel ``ceph_pkg_source`` mengontrol sumber instal untuk paket Ceph. "
"Nilai yang valid meliputi:"

msgid ""
"The ``cinder-api`` service has moved to run as a uWSGI application. You can "
"set the max number of WSGI processes, the number of processes, threads, and "
"buffer size utilizing the ``cinder_wsgi_processes_max``, "
"``cinder_wsgi_processes``, ``cinder_wsgi_threads``, and "
"``cinder_wsgi_buffer_size``. Additionally, you can override any settings in "
"the uWSGI ini configuration file using the "
"``cinder_api_uwsgi_ini_overrides`` setting. The uWSGI application will "
"listen on the address specified by ``cinder_uwsgi_bind_address`` which "
"defaults to ``0.0.0.0``."
msgstr ""
"Layanan ``cinder-api`` telah dipindahkan untuk berjalan sebagai aplikasi "
"uWSGI. Anda dapat mengatur jumlah maksimum proses WSGI, jumlah proses, "
"thread, dan ukuran buffer menggunakan ``cinder_wsgi_processes_max``, "
"``cinder_wsgi_processes``, ``cinder_wsgi_threads``, dan "
"``cinder_wsgi_buffer_si``. Selain itu, Anda dapat mengabaikan pengaturan apa "
"pun di file konfigurasi uWSGI ini menggunakan pengaturan "
"``cinder_api_uwsgi_ini_overrides``. Aplikasi uWSGI akan mendengarkan alamat "
"yang ditentukan oleh ``cinder_uwsgi_bind_address`` yang secara default "
"adalah ``0.0.0.0``."

msgid ""
"The ``cinder_keystone_auth_plugin`` variable has been deprecated. "
"``cinder_keystone_auth_type`` should be used instead to configure "
"authentication type."
msgstr ""
"Variabel ``cinder_keystone_auth_plugin`` telah ditinggalkan. "
"``cinder_keystone_auth_type`` harus digunakan sebagai gantinya untuk "
"mengkonfigurasi tipe otentikasi."

msgid ""
"The ``cinder`` project removed the ``shred`` value for the ``volume_clear`` "
"option. The default for the ``os_cinder`` OpenStack-Ansible role has changed "
"to ``zero``."
msgstr ""
"Proyek ``cinder`` menghapus nilai ``shred`` untuk opsi ``volume_clear``. "
"Default untuk peran ``os_cinder`` OpenStack-Ansible telah berubah menjadi "
"``zero``."

msgid ""
"The ``cn_map`` permissions and ownership adjustments included as part of "
"RHEL-07-040070 and RHEL-07-040080 has been removed. This STIG configuration "
"was removed in the most recent release of the RHEL 7 STIG."
msgstr ""
"Izin ``cn_map`` dan penyesuaian kepemilikan termasuk sebagai bagian dari "
"RHEL-07-040070 dan RHEL-07-040080 telah dihapus. Konfigurasi STIG ini telah "
"dihapus dalam rilis terbaru RHEL 7 STIG."

msgid ""
"The ``config_template`` action module has now been moved into its own git "
"repository (``openstack/ansible-config_template``). This has been done to "
"simplify the ability to use the plugin in other non OpenStack-Ansible "
"projects."
msgstr ""
"Modul aksi ``config_template`` sekarang telah dipindahkan ke repositori "
"gitnya sendiri (``openstack/ansible-config_template``). Ini telah dilakukan "
"untuk menyederhanakan kemampuan untuk menggunakan plugin dalam proyek non-"
"OpenStack-Ansible lainnya."

msgid ""
"The ``container_cidr`` key has been restored back to ``openstack_inventory."
"json``."
msgstr ""
"Kunci ``container_cidr`` telah dikembalikan ke ``openstack_inventory.json``."

msgid ""
"The ``container_interface`` provider network option is no longer required "
"for Neutron provider network definitions when related agents or OVN "
"controllers are deployed on bare metal."
msgstr ""
"Opsi jaringan penyedia ``container_interface`` tidak lagi diperlukan untuk "
"definisi jaringan penyedia Neutron ketika agen terkait atau pengontrol OVN "
"digunakan pada bare metal."

msgid ""
"The ``dragonflow`` plugin for neutron is now available. You can set the "
"``neutron_plugin_type`` to ``ml2.dragonflow`` to utilize this code path. The "
"``dragonflow`` code path is currently experimental."
msgstr ""
"Plugin ``dragonflow`` untuk neutron sekarang tersedia. Anda dapat mengatur "
"``neutron_plugin_type`` ke ``ml2.dragonflow`` untuk memanfaatkan jalur kode "
"ini. Jalur kode ``dragonflow`` saat ini sedang dalam percobaan."

msgid ""
"The ``dynamic_inventory.py`` script now takes a ``--config`` argument rather "
"than a ``--file`` argument."
msgstr ""
"Skrip ``dynamic_inventory.py`` sekarang mengambil argumen ``--config`` "
"sebagai ganti argumen ``--file``."

msgid ""
"The ``fallocate_reserve` option can now be set (in bytes or as a percentage) "
"for swift by using the ``swift_fallocate_reserve`` variable in ``/etc/"
"openstack_deploy/user_variables.yml``. This value is the amount of space to "
"reserve on a disk to prevent a situation where swift is unable to remove "
"objects due to a lack of available disk space to work with. The default "
"value is 1% of the total disk size."
msgstr ""
"Opsi ``fallocate_reserve` sekarang dapat disetel (dalam byte atau sebagai "
"persentase) untuk swift dengan menggunakan variabel "
"``swift_fallocate_reserve`` dalam ``/etc/openstack_deploy/user_variables."
"yml``. Nilai ini adalah jumlah ruang untuk cadangan pada disk untuk mencegah "
"situasi dimana swift tidak dapat menghapus objek karena kurangnya ruang disk "
"yang tersedia untuk bekerja. Nilai default adalah 1% dari total ukuran disk."

msgid ""
"The ``galera_apt_repo_url`` and ``galera_yum_repo_url`` variables have been "
"renamed to ``galera_repo_url``."
msgstr ""
"Variabel ``galera_apt_repo_url`` dan ``galera_yum_repo_url`` telah diubah "
"namanya menjadi ``galera_repo_url``."

msgid ""
"The ``galera_client_opensuse_mirror_obs_url`` variable has been removed "
"since the OBS repository is no longer used to install the MariaDB packages."
msgstr ""
"Variabel ``galera_client_opensuse_mirror_obs_url`` telah dihapus karena "
"repositori OBS tidak lagi digunakan untuk menginstal paket MariaDB."

msgid ""
"The ``galera_client_package_install`` option can now be specified to handle "
"whether packages are installed as a result of the ``openstack-ansible-"
"galera_client`` role running. This will default to ``true``, but can be set "
"to ``false`` to prevent package installs. This is useful when deploying the "
"``my.cnf`` client configuration file on hosts that already have Galera "
"installed."
msgstr ""
"Opsi ``galera_client_package_install`` sekarang dapat ditentukan untuk "
"menangani apakah paket diinstal sebagai hasil dari peran ``openstack-ansible-"
"galera_client`` berjalan. Ini akan secara default menjadi ``true``, tetapi "
"dapat diatur ke ``false`` untuk mencegah instalasi paket. Ini berguna ketika "
"menggunakan file konfigurasi klien ``my.cnf`` pada host yang sudah "
"menginstal Galera."

msgid ""
"The ``galera_client`` role will default to using the ``galera_repo_url`` URL "
"if the value for it is set. This simplifies using an alternative mirror for "
"the MariaDB server and client as only one variable needs to be set to cover "
"them both."
msgstr ""
"Peran ``galera_client`` akan menjadi default untuk menggunakan URL "
"``galera_repo_url`` jika nilai untuk itu ditetapkan. Ini menyederhanakan "
"menggunakan mirror alternatif untuk server dan klien MariaDB karena hanya "
"satu variabel yang perlu diatur untuk mencakup keduanya."

msgid ""
"The ``galera_mariadb_apt_server_package`` and "
"``galera_mariadb_yum_server_package`` variables have been renamed to "
"``galera_mariadb_server_package``."
msgstr ""
"Variabel ``galera_mariadb_apt_server_package`` dan "
"``galera_mariadb_yum_server_package`` telah diubah namanya menjadi "
"``galera_mariadb_server_package``."

msgid ""
"The ``galera_percona_xtrabackup_repo_url`` variable which was used on Ubuntu "
"distributions to select the upstream Percona repository has been dropped and "
"the default upstream repository is always used from now on."
msgstr ""
"Variabel ``galera_percona_xtrabackup_repo_url`` yang digunakan pada "
"distribusi Ubuntu untuk memilih repositori upstream Percona telah dihapus "
"dan repositori upstream default selalu digunakan mulai sekarang."

msgid ""
"The ``galera_server`` role now ships with the latest MariaDB release of "
"10.3.13."
msgstr ""
"Peran ``galera_server`` sekarang dikirim dengan rilis MariaDB terbaru dari "
"10.3.13."

msgid ""
"The ``galera_server`` role now uses mariabackup in order to complete SST "
"operations due to the fact that this is the recommended choice from MariaDB."
msgstr ""
"Peran ``galera_server`` sekarang menggunakan mariabackup untuk menyelesaikan "
"operasi SST karena fakta bahwa ini adalah pilihan yang disarankan dari "
"MariaDB."

msgid ""
"The ``galera_upgrade`` variable is now provided to allow the MariaDB role to "
"update existing installs."
msgstr ""
"Variabel ``galera_upgrade`` sekarang disediakan untuk memungkinkan peran "
"MariaDB memperbarui pemasangan yang ada."

msgid ""
"The ``get_gested`` filter has been removed, as it is not used by any roles/"
"plays."
msgstr ""
"Filter ``get_gested`` telah dihapus, karena tidak digunakan oleh roles/plays "
"apa pun."

msgid ""
"The ``glance-api`` service has moved to run as a uWSGI application. You can "
"set the max number of WSGI processes, the number of processes, threads, and "
"buffer size utilizing the ``glance_wsgi_processes_max``, "
"``glance_wsgi_processes``, ``glance_wsgi_threads``, and "
"``glance_wsgi_buffer_size``. Additionally, you can override any settings in "
"the uWSGI ini configuration file using the "
"``glance_api_uwsgi_ini_overrides`` setting."
msgstr ""
"Layanan ``glance-api`` telah dipindahkan untuk berjalan sebagai aplikasi "
"uWSGI. Anda dapat mengatur jumlah maksimum proses WSGI, jumlah proses, "
"thread, dan ukuran buffer menggunakan ``glance_wsgi_processes_max``, "
"``glance_wsgi_processes``, ``glance_wsgi_threads``, dan "
"``glance_wsgi_buffer_si``. Selain itu, Anda dapat mengabaikan pengaturan apa "
"pun di file konfigurasi uWSGI ini menggunakan pengaturan "
"``glance_api_uwsgi_ini_overrides``."

msgid ""
"The ``glance_apt_packages`` variable has been renamed to "
"``glance_distro_packages`` so that it applies to multiple operating systems."
msgstr ""
"Variabel ``glance_apt_packages`` telah diubah namanya menjadi "
"``glance_distro_packages`` sehingga variabel ini berlaku untuk beberapa "
"sistem operasi."

msgid ""
"The ``glance_digest_algorithm`` has changed from ``sha1`` to ``sha256`` and "
"this improves integrity verification of stored images."
msgstr ""
"``glance_digest_algorithm`` telah berubah dari ``sha1`` menjadi ``sha256`` "
"dan ini meningkatkan verifikasi integritas image yang disimpan."

msgid ""
"The ``glance_enable_v1_registry`` variable has been removed. When using the "
"glance v1 API the registry service is required, so having a variable to "
"disable it makes little sense. The service is now enabled/disabled for the "
"v1 API using the ``glance_enable_v1_api`` variable."
msgstr ""
"Variabel ``glance_enable_v1_registry`` telah dihapus. Saat menggunakan "
"glance v1 API layanan registri diperlukan, sehingga memiliki variabel untuk "
"menonaktifkannya tidak masuk akal. Layanan sekarang diaktifkan/dinonaktifkan "
"untuk API v1 menggunakan variabel ``glance_enable_v1_api``."

msgid ""
"The ``glance`` library has been removed from OpenStack-Ansible's plugins. "
"Upstream Ansible modules for managing OpenStack image resources should be "
"used instead."
msgstr ""
"Pustaka ``glance`` telah dihapus dari plugins OpenStack-Ansible's. Modul "
"Upstream Ansible untuk mengelola sumber daya image OpenStack harus digunakan "
"sebagai gantinya."

msgid ""
"The ``gnocchi_keystone_auth_plugin`` variable has been deprecated. "
"``gnocchi_keystone_auth_type`` should be used instead to configure "
"authentication type."
msgstr ""
"Variabel ``gnocchi_keystone_auth_plugin`` telah ditinggalkan. "
"``gnocchi_keystone_auth_type`` harus digunakan sebagai gantinya untuk "
"mengkonfigurasi tipe otentikasi."

msgid ""
"The ``gnocchi_keystone_auth`` is deprecated, and will be removed in the "
"``Queen`` cycle. Setting ``gnocchi_auth_mode`` to ``keystone`` will achieve "
"the same result."
msgstr ""
"``gnocchi_keystone_auth`` sudah usang, dan akan dihapus dalam siklus "
"``Queen``. Mengatur ``gnocchi_auth_mode`` ke ``keystone`` akan mencapai "
"hasil yang sama."

msgid ""
"The ``haproxy_bufsize`` variable has been removed and made a part of the "
"``haproxy_tuning_params`` dictionary."
msgstr ""
"Variabel ``haproxy_bufsize`` telah dihapus dan menjadi bagian dari kamus "
"``haproxy_tuning_params``."

msgid ""
"The ``haproxy`` role installs *hatop* from source to ensure that the same "
"operator tooling is available across all supported distributions. The "
"download URL for the source can be set using the variable "
"``haproxy_hatop_download_url``."
msgstr ""
"Peran ``haproxy`` menginstal *hatop * dari sumber untuk memastikan bahwa "
"operator tooling yang sama tersedia di semua distribusi yang didukung. URL "
"unduhan untuk sumber dapat diatur dengan menggunakan variabel "
"``haproxy_hatop_download_url``."

msgid ""
"The ``heat-api``, ``heat-api-cfn``, and ``heat-api-cloudwatch`` services "
"have moved to run as a uWSGI applications. You can set the max number of "
"WSGI processes, the number of processes, threads, and buffer size utilizing "
"the ``heat_wsgi_processes_max``, ``heat_wsgi_processes``, "
"``heat_wsgi_threads``, and ``heat_wsgi_buffer_size``. Additionally, you can "
"override any settings in the uWSGI ini configuration file using the "
"``heat_api_uwsgi_ini_overrides``, ``heat_api_cfn_uwsgi_ini_overrides``, and "
"``heat_api_cloudwatch_uwsgi_ini_overrides`` settings. The uWSGI applications "
"will listen on the addresses specified by ``heat_api_uwsgi_bind_address``, "
"``heat_api_cfn_uwsgi_bind_address``, and "
"``heat_api_cloudwatch_uwsgi_bind_address`` respectively. Which all default "
"to ``0.0.0.0``."
msgstr ""
"Layanan ``heat-api``, ``heat-api-cfn``, dan ``heat-api-cloudwatch`` telah "
"berpindah untuk dijalankan sebagai aplikasi uWSGI. Anda dapat mengatur "
"jumlah maksimum proses WSGI, jumlah proses, thread, dan ukuran buffer "
"menggunakan ``heat_wsgi_processes_max``, ``heat_wsgi_processes``, "
"``heat_wsgi_threads``, dan ``heat_wsgi_buffer_size``. Selain itu, Anda dapat "
"mengabaikan pengaturan apa pun di file konfigurasi uWSGI ini menggunakan "
"pengaturan ``heat_api_uwsgi_ini_overrides``, "
"``heat_api_cfn_uwsgi_ini_overrides``, dan "
"``heat_api_cloudwatch_uwsgi_ini_overrides``. Aplikasi uWSGI akan "
"mendengarkan pada alamat yang ditentukan oleh masing-masing "
"``heat_api_uwsgi_bind_address``, ``heat_api_cfn_uwsgi_bind_address``, dan "
"``heat_api_cloudwatch_uwsgi_bind_address``. Yang semuanya default ke "
"``0.0.0.0``."

msgid ""
"The ``heat_cinder_backups_enabled`` variable is set to ``false`` by default."
msgstr ""
"Variabel ``heat_cinder_backups_enabled`` diatur ke ``false`` secara default."

msgid ""
"The ``horizon_images_allow_location`` variable is added to support the "
"``IMAGES_ALLOW_LOCATION`` setting in the horizon_local_settings.py file to "
"allow to specify and external location during the image creation."
msgstr ""
"Variabel ``horizon_images_allow_location`` ditambahkan untuk mendukung "
"pengaturan ``IMAGES_ALLOW_LOCATION`` dalam file horizon_local_settings.py "
"untuk memungkinkan menentukan dan lokasi eksternal selama pembuatan gambar "
"image"

msgid ""
"The ``horizon_keystone_admin_roles`` variable is added to support the "
"``OPENSTACK_KEYSTONE_ADMIN_ROLES`` list in the horizon_local_settings.py "
"file."
msgstr ""
"Variabel ``horizon_keystone_admin_roles`` ditambahkan untuk mendukung daftar "
"``OPENSTACK_KEYSTONE_ADMIN_ROLES`` dalam file horizon_local_settings.py."

msgid ""
"The ``infra_hosts`` and ``infra_containers`` inventory groups have been "
"removed. No containers or services were assigned to these groups "
"exclusively, and the usage of the groups has been supplanted by the ``shared-"
"infra_*`` and ``os-infra_*`` groups for some time. Deployers who were using "
"the groups should adjust any custom configuration in the ``env.d`` directory "
"to assign containers and/or services to other groups."
msgstr ""
"Grup inventory ``infra_hosts`` dan ``infra_containers`` telah dihapus. Tidak "
"ada kontainer atau layanan yang ditugaskan untuk grup ini secara eksklusif, "
"dan penggunaan grup telah digantikan oleh grup ``shared-infra_*`` and ``os-"
"infra_*`` untuk beberapa waktu. Deployer yang menggunakan grup harus "
"menyesuaikan konfigurasi kustom apa pun di direktori ``env.d`` untuk "
"menetapkan kontainer dan/atau layanan ke grup lain."

msgid ""
"The ``ironic_neutron_provisioning_network_name`` and "
"``ironic_neutron_cleaning_network_name`` variable can be set to the name of "
"the neutron network to use for provisioning and cleaning. The ansible tasks "
"will determine the appropriate UUID for that network. Alternatively, "
"``ironic_neutron_provisioning_network_uuid`` or "
"``ironic_neutron_cleaning_network`` can be used to directly specify the UUID "
"of the networks. If both ``ironic_neutron_provisioning_network_name`` and "
"``ironic_neutron_provisioning_network_uuid`` are specified, the specified "
"UUID will be used. If only the provisioning network is specified, the "
"cleaning network will default to the same network."
msgstr ""
"Variabel ``ironic_neutron_provisioning_network_name`` dan "
"``ironic_neutron_cleaning_network_name`` dapat diatur ke nama jaringan "
"neutron yang digunakan untuk provisioning dan cleaning. Tugas yang "
"dimungkinkan akan menentukan UUID yang sesuai untuk jaringan itu. Atau, "
"``ironic_neutron_provisioning_network_uuid`` atau "
"``ironic_neutron_cleaning_network`` dapat digunakan untuk secara langsung "
"menentukan UUID jaringan. Jika ``ironic_neutron_provisioning_network_name`` "
"dan ``ironic_neutron_provisioning_network_uuid`` ditentukan, UUID yang "
"ditentukan akan digunakan. Jika hanya jaringan provisioning yang ditentukan, "
"jaringan cleaning akan secara default ke jaringan yang sama."

msgid "The ``ironic`` role now supports Ubuntu 16.04 and SystemD."
msgstr "Peran ``ironis`` sekarang mendukung Ubuntu 16.04 dan SystemD."

msgid ""
"The ``keystone_ldap_identity_driver`` variable has been removed. The driver "
"for an LDAP back-end in Keystone now simply uses the value 'ldap'. There are "
"no other back-end options for Keystone at this time."
msgstr ""
"Variabel ``keystone_ldap_identity_driver`` telah dihapus. Driver untuk back-"
"end LDAP di Keystone sekarang hanya menggunakan nilai 'ldap'. Tidak ada opsi "
"back-end lain untuk Keystone saat ini."

msgid ""
"The ``lxc-container-create`` role now consumes the variable "
"``lxc_container_bind_mounts`` which should contain a list of bind mounts to "
"apply to a newly created container. The appropriate host and container "
"directory will be created and the configuration applied to the container "
"config. This feature is designed to be used in group_vars to ensure that "
"containers are fully prepared at the time they are created, thus cutting "
"down the number of times containers are restarted during deployments and "
"upgrades."
msgstr ""
"Peran ``lxc-container-create`` sekarang mengkonsumsi variabel "
"``lxc_container_bind_mounts`` yang harus berisi daftar mount mengikat untuk "
"diterapkan ke kontainer yang baru dibuat. Direktori host dan kontainer yang "
"sesuai akan dibuat dan konfigurasi diterapkan pada konfigurasi kontainer. "
"Fitur ini dirancang untuk digunakan dalam group_vars untuk memastikan bahwa "
"kontainer sepenuhnya disiapkan pada saat mereka dibuat, sehingga mengurangi "
"berapa kali kontainer di-restart selama deployment dan upgrade."

msgid ""
"The ``lxc-container-create`` role now consumes the variable "
"``lxc_container_commands`` which should contain any shell commands that "
"should be executed in a newly created container. This feature is designed to "
"be used in group_vars to ensure that containers are fully prepared at the "
"time they are created, thus cutting down the number of times containers are "
"restarted during deployments and upgrades."
msgstr ""
"Peran ``lxc-container-create`` sekarang mengkonsumsi variabel "
"``lxc_container_commands`` yang harus berisi perintah shell yang harus "
"dijalankan dalam kontainer yang baru dibuat. Fitur ini dirancang untuk "
"digunakan dalam group_vars untuk memastikan bahwa kontainer sepenuhnya "
"disiapkan pada saat mereka dibuat, sehingga mengurangi berapa kali kontainer "
"di-restart selama deployment dan upgrade."

msgid ""
"The ``lxc-container-create`` role now consumes the variable "
"``lxc_container_config_list`` which should contain a list of the entries "
"which should be added to the LXC container config file when the container is "
"created. This feature is designed to be used in group_vars to ensure that "
"containers are fully prepared at the time they are created, thus cutting "
"down the number of times containers are restarted during deployments and "
"upgrades."
msgstr ""
"Peran ``lxc-container-create`` sekarang mengkonsumsi variabel "
"``lxc_container_config_list`` yang harus berisi daftar entri yang harus "
"ditambahkan ke file konfigurasi kontainer LXC ketika kontainer dibuat. Fitur "
"ini dirancang untuk digunakan dalam group_vars untuk memastikan bahwa "
"kontainer sepenuhnya disiapkan pada saat mereka dibuat, sehingga mengurangi "
"berapa kali kontainer di-restart selama deployment dan upgrade."

msgid ""
"The ``lxc_container_create`` role no longer uses the distro specific lxc "
"container create template."
msgstr ""
"Peran ``lxc_container_create`` tidak lagi menggunakan templat membuat "
"kontainer lxc spesifik distro."

msgid ""
"The ``lxc_container_create`` role now supports Ubuntu 14.04, 16.04, and RHEL/"
"CentOS 7"
msgstr ""
"Peran ``lxc_container_create`` sekarang mendukung Ubuntu 14.04, 16.04, dan "
"RHEL/CentOS 7"

msgid ""
"The ``lxc_container_create`` role will now build a container based on the "
"distro of the host OS."
msgstr ""
"Peran ``lxc_container_create`` sekarang akan membangun sebuah wadah "
"berdasarkan distro OS host."

msgid ""
"The ``lxc_host`` cache prep has been updated to use the LXC download "
"template. This removes the last remaining dependency the project has on the "
"`rpc-trusty-container.tgz image <http://rpc-repo.rackspace.com/"
"container_images/rpc-trusty-container.tgz>`_."
msgstr ""
"Persiapan cache ``lxc_host`` telah diperbarui untuk menggunakan templat "
"unduhan LXC. Ini menghapus dependensi terakhir yang tersisa dari proyek pada "
"image `rpc-trusty-container.tgz <http://rpc-repo.rackspace.com/"
"container_images/rpc-trusty-container.tgz>` _."

msgid ""
"The ``lxc_host`` role introduces support for CentOS 7 and Ubuntu 16.04 "
"container types."
msgstr ""
"Peran ``lxc_host`` memperkenalkan dukungan untuk jenis kontainer CentOS 7 "
"dan Ubuntu 16.04."

msgid ""
"The ``lxc_host`` role no longer uses the distro specific lxc container "
"create template."
msgstr ""
"Peran ``lxc_host`` tidak lagi menggunakan templat pembuatan kontainer lxc "
"spesifik distro."

msgid ""
"The ``lxc_host`` role will build lxc cache using the download template built "
"from `images found here <https://images.linuxcontainers.org>`_. These images "
"are upstream builds from the greater LXC/D community."
msgstr ""
"Peran ``lxc_host`` akan membangun cache lxc menggunakan templat unduhan yang "
"dibuat dari `images found here <https://images.linuxcontainers.org>` _. "
"Image ini adalah bangunan hulu dari komunitas LXC/D yang lebih besar."

msgid ""
"The ``lxcbr0`` bridge now allows NetworkManager to control it, which allows "
"for networks to start in the correct order when the system boots. In "
"addition, the ``NetworkManager-wait-online.service`` is enabled to ensure "
"that all services that require networking to function, such as "
"``keepalived``, will only start when network configuration is complete. "
"These changes are only applied if a deployer is actively using "
"NetworkManager in their environment."
msgstr ""
"Jembatan ``lxcbr0`` sekarang memungkinkan NetworkManager untuk "
"mengontrolnya, yang memungkinkan jaringan untuk memulai dalam urutan yang "
"benar ketika sistem melakukan booting. Selain itu, ``NetworkManager-wait-"
"online.service`` diaktifkan untuk memastikan bahwa semua layanan yang "
"membutuhkan jaringan berfungsi, seperti ``keepalived``, hanya akan dimulai "
"ketika konfigurasi jaringan selesai. Perubahan ini hanya diterapkan jika "
"penyebar secara aktif menggunakan NetworkManager di lingkungan mereka."

msgid ""
"The ``main`` function in ``dynamic_inventory.py`` now takes named arguments "
"instead of dictionary. This is to support future code changes that will move "
"construction logic into separate files."
msgstr ""
"Fungsi ``main`` dalam ``dynamic_inventory.py`` sekarang menggunakan argumen "
"yang dinamai daripada kamus. Ini untuk mendukung perubahan kode di masa "
"depan yang akan memindahkan logika konstruksi ke file terpisah."

msgid ""
"The ``molteniron`` service is no longer included in the OSA integrated "
"build. Any deployers wishing to use it may still use the playbook and "
"configuration examples from the ``os_molteniron`` role."
msgstr ""
"Layanan ``molteniron`` tidak lagi termasuk dalam OSA integrated build. "
"Penyebar apa pun yang ingin menggunakannya masih dapat menggunakan playbook "
"dan contoh konfigurasi dari peran ``os_molteniron``."

msgid ""
"The ``net.bridge.bridge-nf-call-*`` kernel parameters were set to ``0`` in "
"previous releases to improve performance and it was left up to neutron to "
"adjust these parameters when security groups are applied. This could cause "
"situations where bridge traffic was not sent through iptables and this "
"rendered security groups ineffective. This could allow unexpected ingress "
"and egress traffic within the cloud."
msgstr ""
"Parameter kernel ``net.bridge.bridge-nf-call-*`` disetel ke ``0`` dalam "
"rilis sebelumnya untuk meningkatkan kinerja dan diserahkan ke neutron untuk "
"menyesuaikan parameter ini ketika grup keamanan diterapkan. Ini dapat "
"menyebabkan situasi di mana lalu lintas jembatan tidak dikirim melalui "
"iptables dan ini membuat kelompok keamanan tidak efektif. Ini dapat "
"memungkinkan masuknya lalu lintas yang tidak terduga dan keluar di dalam "
"cloud."

msgid ""
"The ``neutron_driver_network_scheduler`` variable default has changed from "
"ChanceScheduler to WeightScheduler to match the new Neutron defaults."
msgstr ""
"Default variabel ``neutron_driver_network_scheduler`` telah berubah dari "
"ChanceScheduler ke WeightScheduler agar sesuai dengan default Neutron yang "
"baru."

msgid ""
"The ``neutron_driver_quota`` variable default has changed slightly to match "
"the new upstream driver paths."
msgstr ""
"Default variabel ``neutron_driver_quota`` telah berubah sedikit agar sesuai "
"dengan jalur driver hulu yang baru."

msgid ""
"The ``neutron_keystone_auth_plugin`` variable has been deprecated. "
"``neutron_keystone_auth_type`` should be used instead to configure "
"authentication type."
msgstr ""
"Variabel ``neutron_keystone_auth_plugin`` telah ditinggalkan. "
"``neutron_keystone_auth_type`` harus digunakan sebagai gantinya untuk "
"mengkonfigurasi tipe otentikasi."

msgid ""
"The ``neutron_plugin_base`` variable has been modifed to use the friendly "
"names. Deployers should change any customisations to this variable to ensure "
"that the customisation makes use of the short names instead of the full "
"class path."
msgstr ""
"Variabel ``neutron_plugin_base`` telah dimodifikasi untuk menggunakan nama "
"yang ramah. Penyebar harus mengubah penyesuaian apa pun ke variabel ini "
"untuk memastikan bahwa penyesuaian tersebut menggunakan nama pendek daripada "
"full class path."

msgid ""
"The ``neutron`` library has been removed from OpenStack-Ansible's plugins. "
"Upstream Ansible modules for managing OpenStack network resources should be "
"used instead."
msgstr ""
"Pustaka ``neutron`` telah dihapus dari plugin OpenStack-Ansible. Modul "
"Upstream Ansible untuk mengelola sumber daya jaringan OpenStack harus "
"digunakan sebagai gantinya."

msgid ""
"The ``nova-api``, and ``nova-metadata``  services have moved to run as uWSGI "
"applications. You can override their uwsgi configuration files using the "
"``nova_api_os_compute_uwsgi_ini_overrides``, and "
"``nova_api_metadata_uwsgi_ini_overrides`` settings."
msgstr ""
"Layanan ``nova-api``, dan ``nova-metadata`` telah dipindahkan untuk berjalan "
"sebagai aplikasi uWSGI. Anda dapat mengganti file konfigurasi uwsgi mereka "
"menggunakan pengaturan ``nova_api_os_compute_uwsgi_ini_overrides``, dan "
"``nova_api_metadata_uwsgi_ini_overrides``."

msgid ""
"The ``nova-placement`` api service will run as its own ansible group "
"``nova_api_placement``."
msgstr ""
"Layanan api ``nova-placement``  akan berjalan sebagai grup sendiri yang "
"dapat dilakukan ``nova_api_placement``."

msgid ""
"The ``nova-placement`` service is now configured by default. "
"``nova_placement_service_enabled`` can be set to ``False`` to disable the "
"``nova-placement`` service."
msgstr ""
"Layanan ``nova-placement``` sekarang dikonfigurasi secara default. "
"``nova_placement_service_enabled`` dapat diatur ke ``False`` untuk "
"menonaktifkan layanan ``nova-placement``."

msgid ""
"The ``nova-placement`` service now runs as a uWSGI application that is not "
"fronted by an nginx web-server by default. After upgrading, if the ``nova-"
"placement`` service was running on a host or container without any other "
"services requiring nginx, you should manually remove nginx."
msgstr ""
"Layanan ``nova-placement`` sekarang berjalan sebagai aplikasi uWSGI yang "
"tidak digawangi oleh server web nginx secara default. Setelah memutakhirkan, "
"jika layanan ``nova-placement`` dijalankan pada host atau kontainer tanpa "
"layanan lain yang membutuhkan nginx, Anda harus menghapus nginx secara "
"manual."

msgid ""
"The ``nova.conf`` template still includes these variables and it sets the "
"keymap configuration option. Deployers who have customized this setting will "
"not see a change in their ``nova.conf``."
msgstr ""
"Templat ``nova.conf`` masih menyertakan variabel ini dan ia menetapkan opsi "
"konfigurasi keymap. Penyebar yang telah menyesuaikan pengaturan ini tidak "
"akan melihat perubahan pada ``nova.conf`` mereka."

msgid ""
"The ``nova_cpu_mode`` Ansible variable has been removed by default, to allow "
"Nova to detect the default value automatically. Hard-coded values can cause "
"problems. You can still set ``nova_cpu_mode`` to enforce a ``cpu_mode`` for "
"Nova. Additionally, the default value for the ``qemu`` ``libvirt_type`` is "
"set to ``none`` to avoid issues caused with ``qemu`` 2.6.0."
msgstr ""
"Variabel Ansible ``nova_cpu_mode`` telah dihapus secara default, untuk "
"memungkinkan Nova mendeteksi nilai default secara otomatis. Nilai hard-coded "
"dapat menyebabkan masalah. Anda masih dapat mengatur ``nova_cpu_mode`` untuk "
"memberlakukan ``cpu_mode`` untuk Nova. Selain itu, nilai default untuk "
"``qemu`` `` libvirt_type`` diatur ke ``none`` untuk menghindari masalah yang "
"disebabkan oleh ``qemu`` 2.6.0."

msgid ""
"The ``octavia-api`` service has moved to run as a uWSGI application. You can "
"set the max number of WSGI processes, the number of processes, threads, and "
"buffer size utilizing the ``octavia_wsgi_processes_max``, "
"``octavia_wsgi_processes``, ``octavia_wsgi_threads``, and "
"``octavia_wsgi_buffer_size``. Additionally, you can override any settings in "
"the uWSGI ini configuration file using the "
"``octavia_api_uwsgi_ini_overrides`` setting. The uWSGI application will "
"listen on the address specified by ``octavia_uwsgi_bind_address`` which "
"defaults to ``0.0.0.0``."
msgstr ""
"Layanan ``octavia-api`` telah dipindahkan untuk berjalan sebagai aplikasi "
"uWSGI. Anda dapat mengatur jumlah maksimum proses WSGI, jumlah proses, "
"thread, dan ukuran buffer menggunakan ``octavia_wsgi_processes_max``, "
"``octavia_wsgi_processes``, ``octavia_wsgi_threads``, dan "
"``octavia_wsgi_buffer_si``. Selain itu, Anda dapat mengabaikan pengaturan "
"apa pun di file konfigurasi uWSGI ini menggunakan pengaturan "
"``octavia_api_uwsgi_ini_overrides``. Aplikasi uWSGI akan mendengarkan alamat "
"yang ditentukan oleh ``octavia_uwsgi_bind_address`` yang secara default "
"adalah ``0.0.0.0``."

msgid ""
"The ``octavia_keystone_auth_plugin`` variable has been deprecated. "
"``octavia_keystone_auth_type`` should be used instead to configure "
"authentication type."
msgstr ""
"Variabel ``octavia_keystone_auth_plugin`` telah ditinggalkan. "
"``octavia_keystone_auth_type`` harus digunakan sebagai gantinya untuk "
"mengkonfigurasi tipe otentikasi."

msgid ""
"The ``openstack-ansible-galera_server`` role will now prevent deployers from "
"changing the ``galera_cluster_name`` variable on clusters that already have "
"a value set in a running galera cluster. You can set the new "
"``galera_force_change_cluster_name`` variable to ``True`` to force the "
"``galera_cluster_name`` variable to be changed. We recommend setting this by "
"running the galera-install.yml playbook with ``-e "
"galera_force_change_cluster_name=True``, to avoid changing the "
"``galera_cluster_name`` variable unintentionally. Use with caution, changing "
"the ``galera_cluster_name`` value can cause your cluster to fail, as the "
"nodes won't join if restarted sequentially."
msgstr ""
"Peran ``openstack-ansible-galera_server`` sekarang akan mencegah penyebaran "
"mengubah variabel ``galera_cluster_name`` pada kluster yang sudah memiliki "
"nilai yang ditetapkan dalam kluster galera yang sedang berjalan. Anda dapat "
"mengatur variabel ``galera_force_change_cluster_name`` baru menjadi ``True`` "
"untuk memaksa variabel ``galera_cluster_name`` diubah. Kami menyarankan "
"pengaturan ini dengan menjalankan playbook galera-install.yml dengan ``-e "
"galera_force_change_cluster_name = True``, untuk menghindari mengubah "
"variabel ``galera_cluster_name`` secara tidak sengaja. Gunakan dengan hati-"
"hati, mengubah nilai ``galera_cluster_name`` dapat menyebabkan kluster Anda "
"gagal, karena node tidak akan bergabung jika dimulai ulang secara berurutan."

msgid ""
"The ``openstack-ansible-os_swift`` role will now prevent deployers from "
"changing the ``swift_hash_path_prefix`` and ``swift_hash_path_suffix`` "
"variables on clusters that already have a value set in ``/etc/swift/swift."
"conf``. You can set the new ``swift_force_change_hashes`` variable to "
"``True`` to force the ``swift_hash_path_`` variables to be changed. We "
"recommend setting this by running the os-swift.yml playbook with ``-e "
"swift_force_change_hashes=True``, to avoid changing the ``swift_hash_path_`` "
"variables unintentionally. Use with caution, changing the "
"``swift_hash_path_`` values causes end-user impact."
msgstr ""
"Peran ``openstack-ansible-os_swift`` sekarang akan mencegah penyebaran "
"mengubah ``swift_hash_path_prefix`` dan variabel ``swift_hash_path_suffix`` "
"pada kluster yang sudah memiliki nilai yang ditetapkan di ``/etc/swift/swift."
"conf``. Anda dapat mengatur variabel ``swift_force_change_hashes`` baru "
"menjadi ``True`` untuk memaksa variabel ``swift_hash_path_`` diubah. Kami "
"merekomendasikan pengaturan ini dengan menjalankan os-swift.yml playbook "
"dengan ``-e swift_force_change_hash = True``, untuk menghindari mengubah "
"variabel ``swift_hash_path_`` secara tidak sengaja. Gunakan dengan hati-"
"hati, mengubah nilai ``swift_hash_path_`` menyebabkan dampak end-user."

msgid ""
"The ``openstack_host_apt_packages`` variable has been deprecated. "
"``openstack_host_packages`` should be used instead to override packages "
"required to install on all OpenStack hosts."
msgstr ""
"Variabel ``openstack_host_apt_packages`` telah ditinggalkan. "
"``openstack_host_packages`` harus digunakan sebagai gantinya untuk menimpa "
"paket yang diperlukan untuk menginstal pada semua host OpenStack."

msgid ""
"The ``openstack_tempest_gate.sh`` script has been removed as it requires the "
"use of the ``run_tempest.sh`` script which has been deprecated in Tempest. "
"In order to facilitate the switch, the default for the variable "
"``tempest_run`` has been set to ``yes``, forcing the role to execute tempest "
"by default. This default can be changed by overriding the value to ``no``. "
"The test whitelist may be set through the list variable "
"``tempest_test_whitelist``."
msgstr ""
"Skrip ``openstack_tempest_gate.sh`` telah dihapus karena membutuhkan "
"penggunaan skrip ``run_tempest.sh`` yang telah ditinggalkan dalam Tempest. "
"Untuk memfasilitasi switch, default untuk variabel ``tempest_run`` telah "
"disetel ke ``yes``, yang memaksa peran untuk mengeksekusi tempest secara "
"default. Default ini dapat diubah dengan mengganti nilainya menjadi ``no``. "
"Daftar putih (whitelist) pengujian dapat ditetapkan melalui variabel daftar "
"``tempest_test_whitelist``."

msgid ""
"The ``os-cinder-install.yml`` playbook will now execute a rolling upgrade of "
"cinder including database migrations (both schema and online) as per the "
"procedure described in the `cinder documentation <https://docs.openstack.org/"
"developer/cinder/upgrade.html>`_. When haproxy is used as the load balancer, "
"the backend being changed will be drained before changes are made, then "
"added back to the pool once the changes are complete."
msgstr ""
"Playbook ``os-cinder-install.yml`` sekarang akan menjalankan rolling upgrade "
"cinder termasuk migrasi basis data (baik skema dan online) sesuai prosedur "
"yang dijelaskan dalam `cinder documentation <https://docs.openstack.org /"
"developer/cinder/upgrade.html>`_. Ketika haproxy digunakan sebagai "
"penyeimbang beban, backend yang diubah akan dikeringkan (drained) sebelum "
"perubahan dilakukan, kemudian ditambahkan kembali ke pool setelah perubahan "
"selesai."

msgid "The ``os-designate`` role now supports Ubuntu 16.04 and SystemD."
msgstr "Peran ``os-designate`` sekarang mendukung Ubuntu 16.04 dan SystemD."

msgid ""
"The ``os-neutron-install.yml`` playbook will now execute a rolling upgrade "
"of neutron including database migrations (both expand and contract) as per "
"the procedure described in the `neutron documentation <https://docs."
"openstack.org/developer/neutron/devref/upgrade.html>`_."
msgstr ""
"Playbook ``os-neutron-install.yml`` sekarang akan menjalankan upgrade "
"neutron secara bergulir termasuk migrasi basis data (keduanya diperluas dan "
"dikontrak) sesuai prosedur yang dijelaskan dalam `neutron documentation "
"<https://docs.openstack.org/developer/neutron/devref/upgrade.html>`_."

msgid ""
"The ``os-nova-install.yml`` playbook will now execute a rolling upgrade of "
"nova including database migrations as per the procedure described in the "
"`nova documentation <https://docs.openstack.org/developer/nova/upgrade."
"html>`_."
msgstr ""
"Playbook ``os-nova-install.yml`` sekarang akan menjalankan upgrade nova "
"termasuk migrasi basis data sesuai prosedur yang dijelaskan dalam `nova "
"documentation <https://docs.openstack.org/developer/nova/upgrade.html>`_."

msgid ""
"The ``os_barbican`` role now supports deployment on Ubuntu 16.04 using "
"SystemD."
msgstr ""
"Peran ``os_barbican`` sekarang mendukung penyebaran di Ubuntu 16.04 "
"menggunakan SystemD."

msgid ""
"The ``os_ceilometer`` role now includes a facility where you can place your "
"own templates in ``/etc/openstack_deploy/ceilometer`` (by default) and it "
"will be deployed to the target host after being interpreted by the template "
"engine. If no file is found there, the fallback of the git sourced template "
"is used."
msgstr ""
"Peran ``os_ceilometer`` sekarang termasuk fasilitas tempat Anda dapat "
"menempatkan templat Anda sendiri di ``/etc/openstack_deploy/ceilometer`` "
"(secara default) dan akan digunakan untuk host target setelah "
"diinterpretasikan oleh mesin templat. Jika tidak ada file yang ditemukan di "
"sana, fallback dari template bersumber git digunakan."

msgid ""
"The ``os_cinder`` role now provides for doing online data migrations once "
"the db sync has been completed. The data migrations will not be executed "
"until the boolean variable ``cinder_all_software_updated`` is true. This "
"variable will need to be set by the playbook consuming the role."
msgstr ""
"Peran ``os_cinder`` sekarang menyediakan untuk melakukan migrasi data online "
"setelah sinkronisasi db selesai. Migrasi data tidak akan dieksekusi sampai "
"variabel boolean ``cinder_all_software_updated`` menjadi true. Variabel ini "
"perlu diatur oleh playbook yang menggunakan peran tersebut."

msgid "The ``os_cinder`` role now supports Ubuntu 16.04."
msgstr "Peran ``os_cinder`` sekarang mendukung Ubuntu 16.04."

msgid "The ``os_glance`` role now supports Ubuntu 16.04 and SystemD."
msgstr "Peran ``os_glance`` sekarang mendukung Ubuntu 16.04 dan SystemD."

msgid ""
"The ``os_gnocchi`` role now includes a facility where you can place your own "
"default ``api-paste.ini`` or ``policy.json`` file in ``/etc/openstack_deploy/"
"gnocchi`` (by default) and it will be deployed to the target host after "
"being interpreted by the template engine."
msgstr ""
"Peran ``os_gnocchi`` sekarang termasuk fasilitas tempat Anda dapat "
"menempatkan file ``api-paste.ini`` atau file ``policy.json`` default Anda di "
"``/etc/openstack_deploy/gnocchi``  (secara default ) dan itu akan digunakan "
"untuk host target setelah ditafsirkan oleh mesin template."

msgid ""
"The ``os_horizon`` role now supports configuration of custom themes. "
"Deployers can use the new ``horizon_custom_themes`` and "
"``horizon_default_theme`` variables to configure the dashboard with custom "
"themes and default to a specific theme respectively."
msgstr ""
"Peran ``os_horizon`` sekarang mendukung konfigurasi tema kustom. Penyebar "
"dapat menggunakan variabel ``horizon_custom_themes`` dan "
"``horizon_default_theme`` yang baru untuk mengkonfigurasi dasbor dengan tema "
"kustom dan default ke masing-masing tema spesifik."

msgid ""
"The ``os_horizon`` role now supports distribution of user custom themes. "
"Deployers can use the new key ``theme_src_archive`` of "
"``horizon_custom_themes`` dictionary to provide absolute path to the "
"archived theme. Only .tar.gz, .tgz, .zip, .tar.bz, .tar.bz2, .tbz, .tbz2 "
"archives are supported. Structure inside archive should be as a standard "
"theme, without any leading folders."
msgstr ""
"Peran ``os_horizon`` sekarang mendukung distribusi tema kustom pengguna. "
"Penyebar dapat menggunakan kunci baru ``theme_src_archive`` dari kamus "
"``horizon_custom_themes`` untuk memberikan jalur absolut ke tema yang "
"diarsipkan. Hanya arsip .tar.gz, .tgz, .zip, .tar.bz, .tar.bz2, .tbz, .tbz2 "
"yang didukung. Struktur di dalam arsip harus sebagai tema standar, tanpa "
"folder utama."

msgid ""
"The ``os_keystone`` role will now (by default) source the ``keystone-paste."
"ini``, ``policy.json`` and ``sso_callback_template.html`` templates from the "
"service git source instead of from the role. It also now includes a facility "
"where you can place your own templates in ``/etc/openstack_deploy/keystone`` "
"(by default) and it will be deployed to the target host after being "
"interpreted by the template engine."
msgstr ""
"Peran ``os_keystone`` sekarang akan (secara default) sumber ``keystone-paste."
"ini``, ``policy.json`` dan ``sso_callback_template.html`` templat dari "
"sumber layanan git daripada  dari peran. Sekarang juga termasuk fasilitas di "
"mana Anda dapat menempatkan templat Anda sendiri di ``/etc/openstack_deploy/"
"keystone`` (secara default) dan itu akan digunakan untuk host target setelah "
"ditafsirkan oleh mesin templat."

msgid ""
"The ``os_magnum`` role now supports deployment on Ubuntu 16.04 using systemd."
msgstr ""
"Peran ``os_magnum`` sekarang mendukung penyebaran di Ubuntu 16.04 "
"menggunakan systemd."

msgid ""
"The ``os_masakari`` role now covers the monitors installation and "
"configuration, completing the full service configuration."
msgstr ""
"Peran ``os_masakari`` sekarang mencakup pemasangan dan konfigurasi monitor, "
"menyelesaikan konfigurasi layanan lengkap."

msgid ""
"The ``os_neutron`` role now configures neutron ml2 to load the "
"``l2_population`` mechanism driver by default based on the value of "
"``neutron_l2_population``. Deployers may directly control the neutron ml2 "
"mechanism drivers list by overriding the ``mechanisms`` variable in the "
"``neutron_plugins`` dictionary."
msgstr ""
"Peran ``os_neutron`` sekarang mengkonfigurasi neutron ml2 untuk memuat "
"driver mekanisme ``l2_population`` secara default berdasarkan nilai "
"``neutron_l2_population``. Deployer dapat langsung mengontrol daftar driver "
"mekanisme ml2 neutron dengan mengesampingkan variabel ``mechanisms`` dalam "
"kamus ``neutron_plugins``."

msgid ""
"The ``os_neutron`` role now determines the default configuration for "
"openvswitch-agent ``tunnel_types`` and the presence or absence of "
"``local_ip`` configuration based on the value of "
"``neutron_ml2_drivers_type``. Deployers may directly control this "
"configuration by overriding the ``neutron_tunnel_types`` variable ."
msgstr ""
"Peran ``os_neutron`` sekarang menentukan konfigurasi default untuk agen "
"openvswitch ``tunnel_types`` dan ada atau tidaknya konfigurasi ``local_ip`` "
"berdasarkan nilai ``neutron_ml2_drivers_type``. Deployer dapat secara "
"langsung mengontrol konfigurasi ini dengan mengganti variabel "
"``neutron_tunnel_types``."

msgid ""
"The ``os_neutron`` role will now default to the OVS firewall driver when "
"``neutron_plugin_type`` is ``ml2.ovs`` and the host is running Ubuntu 16.04 "
"on PowerVM. To override this default behavior, deployers should define "
"``neutron_ml2_conf_ini_overrides`` and "
"'neutron_openvswitch_agent_ini_overrides' in 'user_variables.yml'. Example "
"below"
msgstr ""
"Peran ``os_neutron`` sekarang akan default ke driver firewall OVS ketika "
"``neutron_plugin_type`` adalah ``ml2.ovs`` dan host menjalankan Ubuntu 16.04 "
"di PowerVM. Untuk mengesampingkan perilaku default ini, para deployer harus "
"mendefinisikan ``neutron_ml2_conf_ini_overrides`` dan "
"'neutron_openvswitch_agent_ini_overrides' di 'user_variables.yml'. Contoh di "
"bawah ini"

msgid ""
"The ``os_nova`` role now provides for doing online data migrations once the "
"db sync has been completed. The data migrations will not be executed until "
"the boolean variable ``nova_all_software_updated`` is true. This variable "
"will need to be set by the playbook consuming the role."
msgstr ""
"Peran ``os_nova`` sekarang menyediakan untuk melakukan migrasi data online "
"setelah sinkronisasi db selesai. Migrasi data tidak akan dieksekusi sampai "
"variabel boolean ``nova_all_software_updated`` menjadi true. Variabel ini "
"perlu diatur oleh playbook yang menggunakan peran tersebut."

msgid ""
"The ``os_swift`` role has 3 new variables that will allow a deployer to "
"change the hard, soft and fs.file-max limits. the hard and soft limits are "
"being added to the limits.conf file for the swift system user. The fs.file-"
"max settings are added to storage hosts via kernel tuning. The new options "
"are ``swift_hard_open_file_limits`` with a default of 10240 "
"``swift_soft_open_file_limits`` with a default of 4096 "
"``swift_max_file_limits`` with a default of 24 times the value of "
"``swift_hard_open_file_limits``."
msgstr ""
"Peran ``os_swift`` memiliki 3 variabel baru yang akan memungkinkan deployer "
"mengubah batas hard, soft, dan fs.file-max. Batas hard dan soft sedang "
"ditambahkan ke file limit.conf untuk pengguna sistem yang cepat. Pengaturan "
"fs.file-max ditambahkan ke host penyimpanan melalui penyetelan kernel. Opsi "
"baru adalah ``swift_hard_open_file_limits`` dengan default 10240  "
"``swift_soft_open_file_limits`` dengan default 4096   "
"``swift_max_file_limits`` dengan default 24 kali nilai "
"``swift_hard_open_file``."

msgid ""
"The ``os_swift`` role will now include the swift \"staticweb\" middleware by "
"default."
msgstr ""
"Peran ``os_swift`` sekarang akan menyertakan middleware swift \"staticweb\" "
"secara default."

msgid ""
"The ``os_tempest`` role now has the ability to install from distribution "
"packages by setting ``tempest_install_method`` to ``distro``."
msgstr ""
"Peran ``os_tempest`` sekarang memiliki kemampuan untuk menginstal dari paket "
"distribusi dengan mengatur ``tempest_install_method`` ke ``distro``."

msgid ""
"The ``os_tempest`` tempest role was downloading images twice - once "
"arbitrarily, and once to use for testing. This has been consolidated into a "
"single download to a consistent location."
msgstr ""
"Peran ``os_tempest`` sedang mengunduh image dua kali - sekali secara acak, "
"dan satu kali untuk digunakan untuk pengujian. Ini telah dikonsolidasikan ke "
"dalam satu unduhan ke lokasi yang konsisten."

msgid ""
"The ``pip_get_pip_options`` override has been removed from group_vars, "
"resulting in the empty default being used. Previously this method was used "
"to lock the pip install source appropriately, but this has been handled "
"through the pip_lock_down role for several cycles. If a deployer has "
"implemented an override in user_variables based on the previous group_vars "
"settings then the settings should be reviewed. This override may now be used "
"for catering to situations where the pip installation requires extra options "
"set to allow installing through a proxy, or disabling certificate validation."
msgstr ""
"Override ``pip_get_pip_options`` telah dihapus dari group_vars, menghasilkan "
"default kosong yang digunakan. Sebelumnya metode ini digunakan untuk "
"mengunci sumber pemasangan pip dengan tepat, tetapi ini telah ditangani "
"melalui peran pip_lock_down untuk beberapa siklus. Jika seorang deployer "
"telah mengimplementasikan override dalam user_variables berdasarkan pada "
"pengaturan group_vars sebelumnya maka pengaturan harus ditinjau. Override "
"ini sekarang dapat digunakan untuk memenuhi situasi di mana pemasangan pip "
"memerlukan opsi tambahan yang diatur untuk memungkinkan pemasangan melalui "
"proxy, atau menonaktifkan validasi sertifikat."

msgid ""
"The ``pip_packages_tmp`` variable has been renamed ``pip_tmp_packages`` to "
"avoid unintended processing by the py_pkgs lookup plugin."
msgstr ""
"Variabel ``pip_packages_tmp`` telah diubah namanya menjadi "
"``pip_tmp_packages`` untuk menghindari pemrosesan yang tidak diinginkan oleh "
"plugin pencarian py_pkgs."

msgid ""
"The ``pretend_min_part_hours_passed`` option can now be passed to swift-ring-"
"builder prior to performing a rebalance. This is set by the "
"``swift_pretend_min_part_hours_passed`` boolean variable. The default for "
"this variable is False. We recommend setting this by running the os-swift."
"yml playbook with ``-e swift_pretend_min_part_hours_passed=True``, to avoid "
"resetting ``min_part_hours`` unintentionally on every run. Setting "
"``swift_pretend_min_part_hours_passed`` to True will reset the clock on the "
"last time a rebalance happened, thus circumventing the min_part_hours check. "
"This should only be used with extreme caution. If you run this command and "
"deploy rebalanced rings before a replication pass completes, you may "
"introduce unavailability in your cluster. This has an end-user imapct."
msgstr ""
"Opsi ``pretend_min_part_hours_passed`` sekarang dapat diteruskan ke swift-"
"ring-builder sebelum melakukan penyeimbangan kembali. Ini diatur oleh "
"variabel boolean ``swift_pretend_min_part_hours_passed``. Default untuk "
"variabel ini adalah False. Kami menyarankan pengaturan ini dengan "
"menjalankan os-swift.yml playbook dengan ``-e "
"swift_pretend_min_part_hours_passed=True``, untuk menghindari pengaturan "
"ulang ``min_part_hours`` secara tidak sengaja pada setiap proses. Mengatur "
"``swift_pretend_min_part_hours_passed`` ke True akan mengatur ulang jam saat "
"terakhir kali penyeimbangan kembali terjadi, sehingga menghindari "
"pemeriksaan min_part_hours. Ini hanya digunakan dengan sangat hati-hati. "
"Jika Anda menjalankan perintah ini dan menggunakan cincin rebalanced "
"(rebalanced rings) sebelum lulus replikasi selesai, Anda dapat "
"memperkenalkan tidak tersedianya di cluster Anda. Ini memiliki dampak end-"
"user."

msgid ""
"The ``provider_networks`` library has been updated to support the definition "
"of network interfaces that can automatically be added as ports to OVS "
"provider bridges setup during a deployment. As a result, the "
"``network_interface`` value applied to the ``neutron_provider_networks`` "
"override in ``user_variables.yml``, as described in previous Open vSwitch "
"deployment guides, is no longer effective. If overrides are necessary, use "
"``network_interface_mappings`` within the provider network override and "
"specify the respective bridge-to-interface mapping (e.g. \"br-provider:"
"bond1\"). For more information, refer to the latest Open vSwitch deployment "
"guide."
msgstr ""
"Pustaka ``provider_networks`` telah diperbarui untuk mendukung definisi "
"antarmuka jaringan yang secara otomatis dapat ditambahkan sebagai port ke "
"pengaturan jembatan penyedia OVS selama penyebaran. Akibatnya, nilai "
"``network_interface`` yang diterapkan pada ``neutron_provider_networks`` "
"menggantikan dalam ``user_variables.yml``, seperti dijelaskan dalam panduan "
"penyebaran Open vSwitch sebelumnya, tidak lagi efektif. Jika perlu "
"mengganti, gunakan ``network_interface_mappings`` di dalam jaringan penyedia "
"dan timpa pemetaan masing-masing jembatan ke antarmuka (mis. \"Br-provider: "
"bond1\"). Untuk informasi lebih lanjut, lihat panduan penyebaran Open "
"vSwitch terbaru."

msgid ""
"The ``provider_networks`` library has been updated to support the definition "
"of network interfaces that can automatically be added as ports to OVS "
"provider bridges setup during a deployment. To activate this feature, add "
"the ``network_interface`` key to the respective flat and/or vlan provider "
"network definition in ``openstack_user_config.yml``. For more information, "
"refer to the latest Open vSwitch deployment guide."
msgstr ""
"Pustaka ``provider_networks`` telah diperbarui untuk mendukung definisi "
"antarmuka jaringan yang secara otomatis dapat ditambahkan sebagai port ke "
"pengaturan jembatan penyedia OVS selama penyebaran. Untuk mengaktifkan fitur "
"ini, tambahkan kunci ``network_interface`` ke definisi jaringan flat dan/"
"atau penyedia vlan masing-masing di ``openstack_user_config.yml``. Untuk "
"informasi lebih lanjut, lihat panduan penyebaran Open vSwitch terbaru."

msgid ""
"The ``py_pkgs`` and ``packages_file`` Ansible lookups are no longer used in "
"OSA and have been removed from the plugins repository."
msgstr ""
"Pencarian ``py_pkgs`` dan ``packages_file`` tidak lagi digunakan dalam OSA "
"dan telah dihapus dari repositori plugins."

msgid ""
"The ``py_pkgs`` lookup plugin now has strict ordering for requirement files "
"discovered. These files are used to add additional requirements to the "
"python packages discovered. The order is defined by the constant, "
"``REQUIREMENTS_FILE_TYPES`` which contains the following entries, 'test-"
"requirements.txt', 'dev-requirements.txt', 'requirements.txt', 'global-"
"requirements.txt', 'global-requirement-pins.txt'. The items in this list are "
"arranged from least to most priority."
msgstr ""
"Plugin pencarian ``py_pkgs`` sekarang memiliki pemesanan ketat untuk file "
"persyaratan yang ditemukan. File-file ini digunakan untuk menambahkan "
"persyaratan tambahan untuk paket python yang ditemukan. Urutan ditentukan "
"oleh konstanta, ``REQUIREMENTS_FILE_TYPES`` yang berisi entri berikut, 'test-"
"requirements.txt', 'dev-requirements.txt', 'requirements.txt', 'global-"
"requirements.txt', 'global-requirement-pins.txt'. Item dalam daftar ini "
"disusun dari prioritas paling rendah hingga paling tinggi."

msgid ""
"The ``rabbitmq_apt_packages`` variable has been deprecated. "
"``rabbitmq_dependencies`` should be used instead to override additional "
"packages to install alongside rabbitmq-server."
msgstr ""
"Variabel ``rabbitmq_apt_packages`` telah ditinggalkan. "
"``rabbitmq_dependencies`` harus digunakan sebagai gantinya untuk mengganti "
"paket tambahan untuk diinstal bersama rabbitmq-server."

msgid ""
"The ``rabbitmq_server`` now supports a configurable inventory host group. "
"Deployers can override the ``rabbitmq_host_group`` variable if they wish to "
"use the role to create additional RabbitMQ clusters on a custom host group."
msgstr ""
"``Rabbitmq_server`` sekarang mendukung grup host persediaan yang dapat "
"dikonfigurasi. Deployer dapat mengganti variabel ``rabbitmq_host_group`` "
"jika mereka ingin menggunakan peran tersebut untuk membuat cluster RabbitMQ "
"tambahan pada grup host kustom."

msgid ""
"The ``rabbitmq_server`` role now supports configuring HiPE compilation of "
"the RabbitMQ server Erlang code. This configuration option may improve "
"server performance for some workloads and hardware. Deployers can override "
"the ``rabbitmq_hipe_compile`` variable, setting a value of ``True`` if they "
"wish to enable this feature."
msgstr ""
"Peran ``rabbitmq_server`` sekarang mendukung konfigurasi kompilasi HiPE dari "
"kode Erlang server RabbitMQ. Opsi konfigurasi ini dapat meningkatkan kinerja "
"server untuk beberapa beban kerja dan perangkat keras. Deployer dapat "
"mengganti variabel ``rabbitmq_hipe_compile``, menetapkan nilai ``True`` jika "
"mereka ingin mengaktifkan fitur ini."

msgid ""
"The ``rabbitmq_server`` role now supports deployer override of the RabbitMQ "
"policies applied to the cluster. Deployers can override the "
"``rabbitmq_policies`` variable, providing a list of desired policies."
msgstr ""
"Peran ``rabbitmq_server`` sekarang mendukung override deployer dari "
"kebijakan RabbitMQ yang diterapkan pada cluster. Deployer dapat mengganti "
"variabel ``rabbitmq_policies``, memberikan daftar kebijakan yang diinginkan."

msgid ""
"The ``rabbitmq_server`` role now supports disabling listeners that do not "
"use TLS. Deployers can override the ``rabbitmq_disable_non_tls_listeners`` "
"variable, setting a value of ``True`` if they wish to enable this feature."
msgstr ""
"Peran ``rabbitmq_server`` sekarang mendukung menonaktifkan pendengar yang "
"tidak menggunakan TLS. Penyebar dapat menimpa variabel "
"``rabbitmq_disable_non_tls_listeners``, mengatur nilai ``True`` jika mereka "
"ingin mengaktifkan fitur ini."

msgid ""
"The ``repo-clone-mirror.yml`` play has been removed as it is no longer used "
"by the project."
msgstr ""
"Play ``repo-clone-mirror.yml`` telah dihapus karena tidak lagi digunakan "
"oleh proyek."

msgid ""
"The ``repo-store-source.yml`` playbook has been removed as it is no longer "
"needed."
msgstr ""
"Playbook ``repo-store-source.yml`` telah dihapus karena tidak lagi "
"diperlukan."

msgid ""
"The ``repo_build_apt_packages`` variable has been renamed. "
"``repo_build_distro_packages`` should be used instead to override packages "
"required to build Python wheels and venvs."
msgstr ""
"Variabel ``repo_build_apt_packages`` telah diganti namanya. "
"``repo_build_distro_packages`` harus digunakan sebagai gantinya untuk "
"menimpa paket yang diperlukan untuk membuat (build) Python wheel dan venv."

msgid ""
"The ``repo_build`` role now correctly applies OpenStack requirements upper-"
"constraints when building Python wheels. This resolves https://bugs."
"launchpad.net/openstack-ansible/+bug/1605846"
msgstr ""
"Peran ``repo_build`` sekarang dengan benar menerapkan persyaratan OpenStack "
"dengan batasan atas saat membuat Python wheel. Ini menyelesaikan https://"
"bugs.launchpad.net/openstack-ansible/+bug/1605846"

msgid ""
"The ``repo_build`` role now makes use of Ubuntu Cloud Archive by default. "
"This can be disabled by setting ``repo_build_uca_enable`` to ``False``."
msgstr ""
"Peran ``repo_build`` sekarang menggunakan Ubuntu Cloud Archive secara "
"default. Ini dapat dinonaktifkan dengan mengatur `` repo_build_uca_enable`` "
"ke `` False``."

msgid ""
"The ``repo_build`` role now provides the ability to override the upper-"
"constraints applied which are sourced from OpenStack and from the global-"
"requirements-pins.txt file. The variable "
"``repo_build_upper_constraints_overrides`` can be populated with a list of "
"upper constraints. This list will take the highest precedence in the "
"constraints process, with the exception of the pins set in the git source "
"SHAs."
msgstr ""
"Peran ``repo_build`` sekarang menyediakan kemampuan untuk menimpa batasan "
"atas yang diterapkan yang bersumber dari OpenStack dan dari file global-"
"requirement-pins.txt. Variabel ``repo_build_upper_constraints_overrides`` "
"dapat diisi dengan daftar batasan atas. Daftar ini akan didahulukan dalam "
"proses kendala, dengan pengecualian pin yang diatur dalam SHA sumber git."

msgid "The ``rsyslog_server`` role now has support for CentOS 7."
msgstr "Peran ``syslog server`` sekarang memiliki dukungan untuk CentOS 7."

msgid ""
"The ``run-playbooks.sh`` script has been refactored to run all playbooks "
"using our core tool set and run order. The refactor work updates the old "
"special case script to a tool that simply runs the integrated playbooks as "
"they've been designed."
msgstr ""
"Skrip ``run-playbooks.sh`` telah di-refactored untuk menjalankan semua "
"playbook menggunakan set tool inti (core tool) kami dan menjalankan order. "
"Pekerjaan refactor memperbarui skrip kasus spesial lama ke alat yang hanya "
"menjalankan playbook terintegrasi seperti yang telah dirancang."

msgid ""
"The ``sahara-api`` service has moved to run as a uWSGI application. You can "
"set the max number of WSGI processes, the number of processes, threads, and "
"buffer size utilizing the ``sahara_wsgi_processes_max``, "
"``sahara_wsgi_processes``, ``sahara_wsgi_threads``, and "
"``sahara_wsgi_buffer_size``. Additionally, you can override any settings in "
"the uWSGI ini configuration file using the "
"``sahara_api_uwsgi_ini_overrides`` setting. The uWSGI application will "
"listen on the address specified by ``sahara_uwsgi_bind_address`` which "
"defaults to ``0.0.0.0``."
msgstr ""
"Layanan ``sahara-api`` telah dipindahkan untuk berjalan sebagai aplikasi "
"uWSGI. Anda dapat mengatur jumlah maksimum proses WSGI, jumlah proses, "
"thread, dan ukuran buffer menggunakan ``sahara_wsgi_processes_max``, "
"``sahara_wsgi_processes``, ``sahara_wsgi_threads``, and "
"``sahara_wsgi_buffer_size``. Selain itu, Anda dapat mengabaikan pengaturan "
"apa pun di file konfigurasi uWSGI ini menggunakan pengaturan "
"``sahara_api_uwsgi_ini_overrides``. Aplikasi uWSGI akan mendengarkan alamat "
"yang ditentukan oleh ``sahara_uwsgi_bind_address`` yang secara default "
"adalah ``0.0.0.0``."

msgid ""
"The ``security_sshd_permit_root_login`` setting can now be set to change the "
"``PermitRootLogin`` setting in ``/etc/ssh/sshd_config`` to any of the "
"possible options. Set ``security_sshd_permit_root_login`` to one of "
"``without-password``, ``prohibit-password``, ``forced-commands-only``, "
"``yes`` or ``no``."
msgstr ""
"Pengaturan ``security_sshd_permit_root_login`` sekarang dapat diatur untuk "
"mengubah pengaturan ``PermitRootLogin`` di ``/etc/ssh/sshd_config`` ke salah "
"satu opsi yang memungkinkan. Setel ``security_sshd_permit_root_login`` "
"menjadi salah satu dari ``without-password``, ``prohibit-password``, "
"``forced-commands-only``, ``yes`` atau ``no``."

msgid ""
"The ``signing_dir`` configuration option has changed from ``/var/cache/"
"heat`` to ``/var/lib/heat/cache/heat``. This only applies to heat "
"deployments that use PKI tokens."
msgstr ""
"Opsi konfigurasi ``signature_dir`` telah berubah dari ``/var/cache/heat`` "
"menjadi  ``/var/lib/heat/cache/heat``. Ini hanya berlaku untuk deployment "
"heat yang menggunakan token PKI."

msgid ""
"The ``swift_fallocate_reserve`` default value has changed from 10737418240 "
"(10GB) to 1% in order to match the OpenStack swift default setting."
msgstr ""
"Nilai default ``swift_fallocate_reserve`` telah berubah dari 10737418240 "
"(10GB) menjadi 1% agar sesuai dengan pengaturan default swift OpenStack."

msgid ""
"The ``swift_keystone_auth_plugin`` variable has been deprecated. "
"``swift_keystone_auth_type`` should be used instead to configure "
"authentication type."
msgstr ""
"Variabel ``swift_keystone_auth_plugin`` telah ditinggalkan. "
"``swift_keystone_auth_type`` harus digunakan sebagai gantinya untuk "
"mengkonfigurasi tipe otentikasi."

msgid ""
"The ``swift_max_rsync_connections`` default value has changed from 2 to 4 in "
"order to match the OpenStack swift documented value."
msgstr ""
"Nilai default ``swift_max_rsync_connections`` telah berubah dari 2 menjadi 4 "
"agar sesuai dengan nilai yang terdokumentasi OpenStack swift."

msgid ""
"The ``swift_rsync_reverse_lookup`` option has been added. This setting will "
"handle whether rsync performs reverse lookups on client IP addresses, and "
"will default to ``False``. We recommend leaving this option at ``False``, "
"unless DNS or host entries exist for each swift host's replication address."
msgstr ""
"Opsi ``swift_rsync_reverse_lookup`` telah ditambahkan. Pengaturan ini akan "
"menangani apakah rsync melakukan pencarian terbalik pada alamat IP klien, "
"dan akan secara default ke ``False``. Kami menyarankan untuk membiarkan opsi "
"ini di ``False``, kecuali jika DNS atau entri host ada untuk setiap alamat "
"replikasi host swift."

msgid ""
"The ``sysctl`` parameter ``kernel.randomize_va_space`` is now set to ``2`` "
"by default. This matches the default of most modern Linux distributions and "
"it ensures that Address Space Layout Randomization (ASLR) is enabled."
msgstr ""
"The ``sysctl`` parameter ``kernel.randomize_va_space`` sekarang diatur ke "
"``2`` secara default. Ini cocok dengan standar distribusi Linux paling "
"modern dan memastikan bahwa Address Space Layout Randomization (ASLR) "
"diaktifkan."

msgid ""
"The ``sysstat`` package was installed on all distributions, but it was only "
"configured to run on Ubuntu and OpenSUSE. It would not run on CentOS due to "
"bad SELinux contexts and file permissions on ``/etc/cron.d/sysstat``. This "
"has been fixed and ``sysstat`` now runs properly on CentOS."
msgstr ""
"Paket ``sysstat`` diinstal pada semua distribusi, tetapi hanya "
"dikonfigurasikan untuk berjalan di Ubuntu dan OpenSUSE. Itu tidak akan "
"berjalan pada CentOS karena konteks SELinux yang buruk dan izin file pada ``/"
"etc/cron.d/sysstat``. Ini telah diperbaiki dan ``sysstat`` sekarang berjalan "
"dengan baik di CentOS."

msgid ""
"The ``tempest_images`` data structure for the ``os_tempest`` role now "
"expects the values for each image to include ``name`` (optionally) and "
"``format`` (the disk format). Also, the optional variable ``checksum`` may "
"be used to set the checksum expected for the file in the format "
"``<algorithm>:<checksum>``."
msgstr ""
"Struktur data ``tempest_images`` untuk peran ``os_tempest`` sekarang "
"mengharapkan nilai untuk setiap image untuk menyertakan ``name`` (opsional) "
"dan ``format`` (format disk). Juga, variabel opsional ``checksum`` dapat "
"digunakan untuk mengatur checksum yang diharapkan untuk file dalam format  "
"``<algorithm>:<checksum>``."

msgid ""
"The ``trove_keystone_auth_plugin`` variable has been deprecated. "
"``trove_keystone_auth_type`` should be used instead to configure "
"authentication type."
msgstr ""
"Variabel ``trove_keystone_auth_plugin`` telah ditinggalkan. "
"``trove_keystone_auth_type`` harus digunakan sebagai gantinya untuk "
"mengkonfigurasi tipe otentikasi."

msgid ""
"The ``update`` state for the ``ensure_endpoint`` method of the ``keystone`` "
"module is now deprecated, and will be removed in the Queens cycle. Setting "
"state to ``present`` will achieve the same result."
msgstr ""
"Status ``update`` untuk metode ``ensure_endpoint`` dari modul ``keystone`` "
"sekarang sudah tidak digunakan lagi, dan akan dihapus dalam siklus Queens. "
"Menyetel status ke ``present`` akan mencapai hasil yang sama."

msgid ""
"The ``utility-all.yml`` playbook will no longer distribute the deployment "
"host's root user's private ssh key to all utility containers. Deployers who "
"desire this behavior should set the ``utility_ssh_private_key`` variable."
msgstr ""
"Playbook ``utility-all.yml`` tidak akan lagi mendistribusikan private ssh "
"key pengguna root dari host deployment ke semua kontainer utilitas. Deployer "
"yang menginginkan perilaku ini harus menetapkan variabel "
"``utility_ssh_private_key``."

msgid ""
"The `dynamic_inventory.py` file now takes a new argument, ``--check``, which "
"will run the inventory build without writing any files to the file system. "
"This is useful for checking to make sure your configuration does not contain "
"known errors prior to running Ansible commands."
msgstr ""
"File `dynamic_inventory.py` sekarang mengambil argumen baru, ``--check``,  "
"yang akan menjalankan inventory build tanpa menulis file apa pun ke sistem "
"file. Ini berguna untuk memeriksa untuk memastikan konfigurasi Anda tidak "
"mengandung kesalahan yang diketahui sebelum menjalankan perintah Ansible."

msgid ""
"The `get_nested` filter has been added, allowing for simplified value "
"lookups inside of nested dictionaries. `ansible_local|"
"get_nested('openstack_ansible.swift')`, for example, will look 2 levels down "
"and return the result."
msgstr ""
"Filter `get_nested` telah ditambahkan, memungkinkan pencarian nilai yang "
"disederhanakan di dalam kamus bersarang (nested).  `ansible_local|"
"get_nested('openstack_ansible.swift')`,  misalnya, akan melihat 2 level ke "
"bawah dan mengembalikan hasilnya."

msgid ""
"The `max_fail_percentage` playbook option has been used with the default "
"playbooks since the first release of the playbooks back in **Icehouse**. "
"While the intention was to allow large-scale deployments to succeed in cases "
"where a single node fails due to transient issues, this option has produced "
"more problems that it solves. If a failure occurs that is transient in "
"nature but is under the set failure percentage the playbook will report a "
"success, which can cause silent failures depending on where the failure "
"happened. If a deployer finds themselves in this situation the problems are "
"are then compounded because the tools will report there are no known issues. "
"To ensure deployers have the best deployment experience and the most "
"accurate information a change has been made to remove the "
"`max_fail_percentage` option from all of the default playbooks. The removal "
"of this option has the side effect of requiring the deploy to skip specific "
"hosts should one need to be omitted from a run, but has the benefit of "
"eliminating silent, hard to track down, failures. To skip a failing host for "
"a given playbook run use the `--limit '!$HOSTNAME'` CLI switch for the "
"specific run. Once the issues have been resolved for the failing host rerun "
"the specific playbook without the `--limit` option to ensure everything is "
"in sync."
msgstr ""
"Opsi playbook `max_fail_percentage` telah digunakan dengan playbook default "
"sejak rilis pertama playbook kembali di **Icehouse**.  Sementara maksudnya "
"adalah untuk memungkinkan penyebaran skala besar untuk berhasil dalam kasus "
"di mana satu node gagal karena masalah sementara, opsi ini telah "
"menghasilkan lebih banyak masalah yang dipecahkan. Jika terjadi kegagalan "
"yang bersifat sementara tetapi berada di bawah persentase kegagalan yang "
"ditetapkan, playbook akan melaporkan keberhasilan, yang dapat menyebabkan "
"kegagalan diam (silent failure) tergantung di mana kegagalan itu terjadi. "
"Jika seorang deployer menemukan diri mereka dalam situasi ini masalahnya "
"kemudian diperparah karena alat akan melaporkan tidak ada masalah yang "
"diketahui. Untuk memastikan bahwa deployer memiliki pengalaman penerapan "
"terbaik dan informasi paling akurat telah dilakukan perubahan untuk "
"menghapus opsi `max_fail_percentage` dari semua playbook default. "
"Penghapusan opsi ini memiliki efek samping yang mengharuskan penyebaran "
"untuk melewati host tertentu jika seseorang harus dihilangkan dari run, "
"tetapi memiliki manfaat menghilangkan kegagalan diam, sulit dilacak, "
"kegagalan. Untuk melewati host yang gagal untuk menjalankan playbook "
"tertentu gunakan `--limit '!$HOSTNAME'` CLI switch  untuk menjalankan "
"tertentu. Setelah masalah terselesaikan untuk host yang gagal jalankan "
"kembali playbook tertentu tanpa opsi `--limit` untuk memastikan semuanya "
"tersinkronisasi."

msgid ""
"The `openstack-ansible-security role <http://docs.openstack.org/developer/"
"openstack-ansible-security/>`_ is now integrated with OpenStack-Ansible.  "
"Refer to the `Security Hardening <http://docs.openstack.org/developer/"
"openstack-ansible/mitaka/install-guide/configure-initial.html#security-"
"hardening>`_ section of the OpenStack-Ansible documentation for details on "
"how to deploy host security hardening along with OpenStack-Ansible."
msgstr ""
"The `openstack-ansible-security role <http://docs.openstack.org/developer/"
"openstack-ansible-security/>`_ sekarang terintegrasi dengan OpenStack-"
"Ansible. Lihat bagian `Security Hardeninn <http://docs.openstack.org/"
"developer/openstack-ansible/mitaka/install-guide/configure-initial."
"html#security-hardening>` _ pada dokumentasi OpenStack-Ansible untuk "
"perincian tentang cara menggunakan pengerasan keamanan host bersama dengan "
"OpenStack-Ansible."

msgid ""
"The ability to disable the certificate validation when checking and "
"interacting with the internal cinder endpoint has been implemented. In order "
"to do so, set the following in ``/etc/openstack_deploy/user_variables.yml``."
msgstr ""
"Kemampuan untuk menonaktifkan validasi sertifikat ketika memeriksa dan "
"berinteraksi dengan endpoint cinder internal telah diterapkan. Untuk "
"melakukannya, tetapkan yang berikut ini di ``/etc/openstack_deploy/"
"user_variables.yml``."

msgid ""
"The ability to set the RabbitMQ repo URL for both erlang and RabbitMQ itself "
"has been added. This has been done to allow deployers to define the location "
"of a given repo without having to fully redefine the entire set of "
"definitions for a specific repository. The default variables "
"`rabbitmq_gpg_keys`, `rabbitmq_repo_url`, and `rabbitmq_erlang_repo_url` "
"have been created to facilitate this capability."
msgstr ""
"Kemampuan untuk mengatur URL repo RabbitMQ untuk erlang dan RabbitMQ sendiri "
"telah ditambahkan. Ini telah dilakukan untuk memungkinkan deployer "
"menentukan lokasi repo yang diberikan tanpa harus mendefinisikan ulang "
"seluruh set definisi untuk repositori spesifik. Variabel default "
"`rabbitmq_gpg_keys`,` rabbitmq_repo_url`, dan `rabbitmq_erlang_repo_url` "
"telah dibuat untuk memfasilitasi kemampuan ini."

msgid ""
"The ability to support MultiStrOps has been added to the config_template "
"action plugin. This change updates the parser to use the ``set()`` type to "
"determine if values within a given key are to be rendered as "
"``MultiStrOps``. If an override is used in an INI config file the set type "
"is defined using the standard yaml construct of \"?\" as the item marker."
msgstr ""
"Kemampuan untuk mendukung MultiStrOps telah ditambahkan ke plugin aksi "
"config_template. Perubahan ini memperbarui parser untuk menggunakan tipe "
"``set()`` untuk menentukan apakah nilai dalam kunci yang diberikan akan "
"diberikan sebagai ``MultiStrOps``. Jika override digunakan dalam file "
"konfigurasi INI, tipe set didefinisikan menggunakan konstruksi yaml standar "
"\"?\" sebagai penanda item."

msgid ""
"The ability to support login user domain and login project domain has been "
"added to the keystone module."
msgstr ""
"Kemampuan untuk mendukung domain pengguna masuk dan domain proyek masuk "
"telah ditambahkan ke modul keystone."

msgid ""
"The ability to support login user domain and login project domain has been "
"added to the keystone module. This resolves https://bugs.launchpad.net/"
"openstack-ansible/+bug/1574000"
msgstr ""
"Kemampuan untuk mendukung domain pengguna masuk dan domain proyek masuk "
"telah ditambahkan ke modul keystone. Ini teratasi (resolves)  https://bugs."
"launchpad.net/openstack-ansible/+bug/1574000"

msgid ""
"The addition of multi-domain LDAP configuration support left behind a "
"configuration file for the default domain that causes problems with "
"Keystone. This file will automatically be removed if the deployer is not "
"using the Default domain with an LDAP back end. (`Bug 1547542 <https://bugs."
"launchpad.net/openstack-ansible/+bug/1547542>`_)"
msgstr ""
"Penambahan dukungan konfigurasi LDAP multi-domain meninggalkan file "
"konfigurasi untuk domain default yang menyebabkan masalah dengan Keystone. "
"File ini akan secara otomatis dihapus jika deployer tidak menggunakan domain "
"Default dengan back end  LDAP. (`Bug 1547542 <https://bugs.launchpad.net/"
"openstack-ansible/+bug/1547542>` _)"

msgid ""
"The addition of the ``container_tech`` option and the inclusion of "
"**nspawn** support deployers now have the availability to define a desired "
"containerization strategy globally or on specific hosts."
msgstr ""
"Penambahan opsi ``container_tech`` dan dimasukkannya **nspawn** dukungan "
"deployers sekarang memiliki ketersediaan untuk menentukan strategi "
"containerization yang diinginkan secara global atau pada host tertentu."

msgid ""
"The admin_token_auth middleware presents a potential security risk and will "
"be removed in a future release of keystone. Its use can be removed by "
"setting the ``keystone_keystone_paste_ini_overrides`` variable."
msgstr ""
"Middleware admin_token_auth menyajikan risiko keamanan potensial dan akan "
"dihapus dalam rilis keystone di masa mendatang. Penggunaannya dapat dihapus "
"dengan mengatur variabel ``keystone_keystone_paste_ini_overrides``."

msgid ""
"The ansible version used by OSA is updated from the 2.7 to the 2.8 series. "
"This requires an upgrade of ceph-ansible to 4.0 and this in turn requires an "
"upgrade of ceph from Mimic to Nautilus. This version dependancy applies "
"where OSA uses ceph-ansible directly to deploy the ceph infrastructure, but "
"not when OSA is integrated with an externally provisioned ceph cluster."
msgstr ""
"Versi ansible yang digunakan oleh OSA diperbarui dari seri 2.7 ke 2.8. Ini "
"membutuhkan pembaruan ceph-ansible untuk 4.0 dan ini pada gilirannya "
"memerlukan pembaruan ceph dari Mimic ke Nautilus. Ketergantungan versi ini "
"berlaku di mana OSA menggunakan ceph-ansible secara langsung untuk "
"menggunakan infrastruktur ceph, tetapi tidak ketika OSA terintegrasi dengan "
"ceph cluster yang disediakan secara eksternal."

msgid ""
"The ansible-hardening role supports the application of the Red Hat "
"Enterprise Linux 6 STIG configurations to systems running CentOS 7 and "
"Ubuntu 16.04 LTS."
msgstr ""
"Peran ansible-hardening mendukung aplikasi konfigurasi Red Hat Enterprise "
"Linux 6 STIG untuk sistem yang menjalankan CentOS 7 dan Ubuntu 16.04 LTS."

msgid ""
"The aodh-api init service is removed since aodh-api is deployed as an apache "
"mod_wsgi service."
msgstr ""
"Layanan init aodh-api dihapus karena aodh-api digunakan sebagai layanan "
"mod_wsgi apache."

msgid ""
"The apt-cacher-ng daemon does not use the proxy server specified in "
"environment variables. The proxy server specified in the ``proxy_env_url`` "
"variable is now set inside the apt-cacher-ng configuration file."
msgstr ""
"Daemon apt-cacher-ng tidak menggunakan server proxy yang ditentukan dalam "
"variabel lingkungan. Server proxy yang ditentukan dalam variabel "
"``proxy_env_url`` sekarang diatur di dalam file konfigurasi apt-cacher-ng."

msgid ""
"The audit rules added by the security role now have key fields that make it "
"easier to link the audit log entry to the audit rule that caused it to "
"appear."
msgstr ""
"Aturan audit yang ditambahkan oleh peran keamanan sekarang memiliki key "
"field yang membuatnya lebih mudah untuk menghubungkan entri log audit dengan "
"aturan audit yang menyebabkannya muncul."

msgid ""
"The auditd rules for auditing V-38568 (filesystem mounts) were incorrectly "
"labeled in the auditd logs with the key of ``export-V-38568``. They are now "
"correctly logged with the key ``filesystem_mount-V-38568``."
msgstr ""
"Aturan auditd untuk audit V-38568 (mount filesystem) salah diberi label "
"dalam log auditd dengan kunci ``export-V-38568``. Mereka sekarang dicatat "
"dengan benar dengan kunci ``filesystem_mount-V-38568``."

msgid ""
"The auditd rules template included a rule that audited changes to the "
"AppArmor policies, but the SELinux policy changes were not being audited. "
"Any changes to SELinux policies in ``/etc/selinux`` are now being logged by "
"auditd."
msgstr ""
"Templat aturan auditd menyertakan aturan yang mengaudit perubahan kebijakan "
"AppArmor, tetapi perubahan kebijakan SELinux tidak diaudit. Setiap perubahan "
"pada kebijakan SELinux di ``/etc/selinux`` sekarang sedang dicatat oleh "
"auditd."

msgid ""
"The bind mount for logs on the galera container was found to be broken in "
"`bug 1609862 <https://launchpad.net/bugs/1609862>` and it has been fixed."
msgstr ""
"Mount mengikat untuk log pada kontainer galera ditemukan rusak di `bug "
"1609862 <https://launchpad.net/bugs/1609862>` dan telah diperbaiki."

msgid ""
"The blazar dashboard is available in Horizon. Deployers can enable the panel "
"by setting the following Ansible variable:"
msgstr ""
"Dasbor blazar tersedia di Horizon. Deployer dapat mengaktifkan panel dengan "
"mengatur variabel Ansible berikut:"

msgid ""
"The bootstrap-ansible script may fail with an incompatible requirement when "
"installing OpenStack-Ansible 13.3.12 and before. See https://bugs.launchpad."
"net/openstack-ansible/+bug/1658948 for more details."
msgstr ""
"Script bootstrap-ansible mungkin gagal dengan persyaratan yang tidak "
"kompatibel saat menginstal OpenStack-Ansible 13.3.12 dan sebelumnya. Lihat "
"https://bugs.launchpad.net/openstack-ansible/+bug/1658948 untuk rincian "
"lebih lanjut."

msgid ""
"The bootstrap-ansible script may fail with an incompatible requirement when "
"installing OpenStack-Ansible 14.0.6 and before. See https://bugs.launchpad."
"net/openstack-ansible/+bug/1658948 for more details."
msgstr ""
"Script bootstrap-ansible mungkin gagal dengan persyaratan yang tidak "
"kompatibel ketika menginstal OpenStack-Ansible 14.0.6 dan sebelumnya. Lihat "
"https://bugs.launchpad.net/openstack-ansible/+bug/1658948 untuk rincian "
"lebih lanjut."

msgid ""
"The ceilometer API service is now deprecated. OpenStack-Ansible no longer "
"deploys this service. To make queries against metrics, alarms, and/or "
"events, please use the the gnocchi, aodh, and panko APIs, respectively."
msgstr ""
"Layanan ceilometer API sekarang sudah tidak digunakan lagi. OpenStack-"
"Ansible tidak lagi menyebarkan layanan ini. Untuk membuat kueri terhadap "
"metrik, alarm, dan/atau event, silakan gunakan API gnocchi, aodh, dan panko, "
"masing-masing."

msgid ""
"The ceilometer alarming functionality has been moved into aodh. The "
"``ceilometer_alarm_notifier`` and ``ceilometer_alarm_evaluator`` entries are "
"removed from the ``/etc/openstack_deploy/env.d/ceilometer.yml`` file."
msgstr ""
"Fungsi mengkhawatirkan ceilometer telah dipindahkan ke aodh. Entri "
"``ceilometer_alarm_notifier`` dan ``ceilometer_alarm_evaluator`` dihapus "
"dari file ``/etc/openstack_deploy/env.d/ceilometer.yml``."

msgid ""
"The ceilometer configuration files other than ``ceilometer.conf`` are now "
"retrieved from upstream. You can override the repository from which these "
"are retrieved by setting the ``ceilometer_git_config_lookup_location`` "
"variable which defaults to the git.openstack.org."
msgstr ""
"File konfigurasi ceilometer selain ``ceilometer.conf`` sekarang diambil dari "
"hulu. Anda dapat mengganti repositori dari mana ini diambil dengan mengatur "
"variabel ``ceilometer_git_config_lookup_location`` yang default ke git."
"openstack.org."

msgid ""
"The ceilometer-api service/container can be removed as part of O->P "
"upgrades. A ceilometer-central container will be created to contain the "
"central ceilometer agents."
msgstr ""
"Layanan/kontainer ceilometer-api dapat dilepas sebagai bagian dari upgrade O-"
"> P. Kontainer ceilometer-central akan dibuat untuk berisi agen ceilometer "
"central."

msgid ""
"The ceph-ansible common roles are no longer namespaced with a galaxy-style "
"'.' (ie. ``ceph.ceph-common`` is now cloned as ``ceph-common``), due to a "
"change in the way upstream meta dependencies are handled in the ceph roles. "
"The roles will be cloned according to the new naming, and an upgrade "
"playbook ``ceph-galaxy-removal.yml`` has been added to clean up the stale "
"galaxy-named roles."
msgstr ""
"Peran umum yang dimungkinkan tidak lagi diberi nama dengan galaxy-style "
"'.' (misal ``ceph.ceph-common`` sekarang dikloning sebagai ``ceph-common``), "
"karena perubahan dalam cara ketergantungan meta hulu ditangani dalam peran "
"ceph. Peran tersebut akan dikloning sesuai dengan penamaan yang baru, dan "
"playbook pemutakhiran ``ceph-galaxy-removal.yml`` telah ditambahkan untuk "
"membersihkan peran yang dinamai galaksi basi (stale galaxy-named role)."

msgid ""
"The ceph-ansible integration has been updated to support the ceph-ansible "
"v3.0 series tags. The new v3.0 series brings a significant refactoring of "
"the ceph-ansible roles and vars, so it is strongly recommended to consult "
"the upstream `ceph-ansible documentation <http://docs.ceph.com/ceph-ansible/"
"master/>`_ to perform any required vars migrations before you upgrade."
msgstr ""
"Integrasi ceph-ansible telah diperbarui untuk mendukung tag seri ceph-"
"ansible v3.0. Seri v3.0 baru membawa refactoring yang signifikan dari peran "
"dan var ceph-ansible, sehingga sangat disarankan untuk berkonsultasi dengan "
"bagian hulu `ceph-ansible documentation <http://docs.ceph.com/ceph-ansible/"
"master/>`_ untuk melakukan migrasi vars yang diperlukan sebelum Anda "
"memutakhirkan."

msgid ""
"The ceph_client role always checks whether the latest package is installed "
"when executed. If a deployer wishes to change the check to only validate the "
"presence of the package, the option ``ceph_client_package_state`` should be "
"set to ``present``."
msgstr ""
"Peran ceph_client selalu memeriksa apakah paket terbaru diinstal ketika "
"dieksekusi. Jika seorang deployer ingin mengubah tanda centang untuk hanya "
"memvalidasi keberadaan paket, opsi ``ceph_client_package_state`` harus "
"diatur ke ``present``."

msgid ""
"The ceph_client role now supports the ability to configure whether apt/yum "
"tasks install the latest available package, or just ensure that the package "
"is present. The default action is to ensure that the latest package is "
"present. The action taken may be changed to only ensure that the package is "
"present by setting ``ceph_client_package_state`` to ``present``."
msgstr ""
"Peran ceph_client sekarang mendukung kemampuan untuk mengkonfigurasi apakah "
"tugas apt/yum menginstal paket terbaru yang tersedia, atau hanya memastikan "
"bahwa paket tersebut ada. Tindakan default adalah untuk memastikan bahwa "
"paket terbaru hadir. Tindakan yang diambil dapat diubah hanya untuk "
"memastikan bahwa paket hadir dengan mengatur ``ceph_client_package_state`` "
"ke ``present``."

msgid ""
"The ceph_client role will now look for and configure manila services to work "
"with ceph and cephfs."
msgstr ""
"Peran ceph_client sekarang akan mencari dan mengkonfigurasi layanan manila "
"untuk bekerja dengan ceph dan cephfs."

msgid ""
"The check to validate whether an appropriate ssh public key is available to "
"copy into the container cache has been corrected to check the deployment "
"host, not the LXC host."
msgstr ""
"Pemeriksaan untuk memvalidasi apakah kunci publik ssh yang sesuai tersedia "
"untuk disalin ke dalam cache kontainer telah diperbaiki untuk memeriksa "
"deployment host, bukan host LXC."

msgid ""
"The cloudkitty dashboard is available in Horizon. Deployers can enable the "
"panel by setting the following Ansible variable:"
msgstr ""
"Dasbor cloudkitty tersedia di Horizon. Deployer dapat mengaktifkan panel "
"dengan mengatur variabel Ansible berikut:"

msgid ""
"The compression option in the ``galera_server`` role has been removed due to "
"the fact that it is not recommended by MariaDB anymore.  This means that all "
"the dependencies from Percona such as QPress are no longer necessary."
msgstr ""
"Opsi kompresi dalam peran ``galera_server`` telah dihapus karena fakta bahwa "
"itu tidak direkomendasikan oleh MariaDB lagi. Ini berarti bahwa semua "
"dependensi dari Percona seperti QPress tidak lagi diperlukan."

msgid ""
"The conditional that determines whether the ``sso_callback_template.html`` "
"file is deployed for federated deployments has been fixed."
msgstr ""
"Persyaratan yang menentukan apakah file ``sso_callback_template.html`` "
"dikerahkan untuk penyebaran federasi telah diperbaiki."

msgid ""
"The config_template action plugin now has a new option to toggle list "
"extension for JSON or YAML formats. The new option is ``list_extend`` and is "
"a boolean. The default is True which maintains the existing API."
msgstr ""
"Plugin action config_template sekarang memiliki opsi baru untuk beralih "
"ekstensi daftar untuk format JSON atau YAML. Opsi baru adalah "
"``list_extend`` dan merupakan boolean. Defaultnya adalah True yang "
"memelihara API yang ada."

msgid ""
"The config_template template module now supports writing out valueless INI "
"options without suffixing them with '=' or ':'. This is done via the "
"'ignore_none_type' attribute. If ignore_none_type is set to true, these key/"
"value entries will be ignored, if it's set to false, then "
"ConfigTemplateParser will write out only the option name without the '=' or "
"':' suffix. The default is true."
msgstr ""
"Modul template config_template sekarang mendukung penulisan opsi INI yang "
"tidak bernilai tanpa membuatnya suffix dengan '=' atau ':'. Ini dilakukan "
"melalui atribut 'ign_none_type'. Jika ign_none_type disetel ke true, entri "
"key/value ini akan diabaikan, jika disetel ke false, maka "
"ConfigTemplateParser hanya akan menuliskan nama opsi tanpa akhiran '=' atau "
"':'. Defaultnya true."

msgid ""
"The container cache preparation process now allows ``copy-on-write`` to be "
"set as the ``lxc_container_backing_method`` when the "
"``lxc_container_backing_store`` is set to ``lvm``. When this is set a base "
"container will be created using a name of the form `<linux-distribution>`-"
"`distribution-release>`-`<host-cpu-architecture>`. The container will be "
"stopped as it is not used for anything except to be a backing store for all "
"other containers which will be based on a snapshot of the base container."
msgstr ""
"Proses persiapan cache kontainer sekarang memungkinkan ``copy-on-write`` "
"dapat ditetapkan sebagai ``lxc_container_backing_method`` ketika "
"``lxc_container_backing_store`` diatur ke ``lvm``. Ketika ini diatur "
"kontainer dasar akan dibuat menggunakan nama dari bentuk `<linux-"
"distribution>`-`distribution-release>`-`<host-cpu-architecture>`.  Kontainer "
"akan dihentikan karena tidak digunakan untuk apa pun kecuali menjadi backing "
"store untuk semua kontainer lain yang akan didasarkan pada snapshot dari "
"kontainer dasar (base container)."

msgid ""
"The container cache preparation process now allows ``overlayfs`` to be set "
"as the ``lxc_container_backing_store``. When this is set a base container "
"will be created using a name of the form `<linux-distribution>`-"
"`distribution-release>`-`<host-cpu-architecture>`. The container will be "
"stopped as it is not used for anything except to be a backing store for all "
"other containers which will be based on a snapshot of the base container. "
"The ``overlayfs`` backing store is not recommended to be used for production "
"unless the host kernel version is 3.18 or higher."
msgstr ""
"Proses persiapan cache kontainer sekarang memungkinkan ``overlayfs`` untuk "
"ditetapkan sebagai ``lxc_container_backing_store``. Ketika ini diatur "
"kontainer dasar akan dibuat menggunakan nama dari bentuk  `<linux-"
"distribution>`-`distribution-release>`-`<host-cpu-architecture>`. Kontainer "
"akan dihentikan karena tidak digunakan untuk apa pun kecuali menjadi backing "
"store untuk semua kontainer lain yang akan didasarkan pada snapshot dari "
"kontainer dasar. Backing store ``overlayfs`` tidak disarankan untuk "
"digunakan untuk produksi kecuali versi host kernel 3.18 atau lebih tinggi."

msgid ""
"The container creation process now allows ``copy-on-write`` to be set as the "
"``lxc_container_backing_method`` when the ``lxc_container_backing_store`` is "
"set to ``lvm``. When this is set it will use a snapshot of the base "
"container to build the containers."
msgstr ""
"Proses pembuatan kontainer sekarang memungkinkan ``copy-on-write`` untuk "
"ditetapkan sebagai ``lxc_container_backing_method`` ketika "
"``lxc_container_backing_store`` diatur ke ``lvm``. Saat ini diatur, ia akan "
"menggunakan snapshot dari kontainer dasar untuk membangun kontainer."

msgid ""
"The container creation process now allows ``overlayfs`` to be set as the "
"``lxc_container_backing_store``. When this is set it will use a snapshot of "
"the base container to build the containers. The ``overlayfs`` backing store "
"is not recommended to be used for production unless the host kernel version "
"is 3.18 or higher."
msgstr ""
"Proses pembuatan kontainer sekarang memungkinkan ``overlayfs`` untuk "
"ditetapkan sebagai ``lxc_container_backing_store``. Saat ini diatur, ia akan "
"menggunakan snapshot dari kontainer dasar untuk membangun kontainer.  "
"Backing store ``overlayfs`` tidak disarankan untuk digunakan untuk produksi "
"kecuali versi host kernel 3.18 atau lebih tinggi."

msgid ""
"The container image cache within machinectl has been set to \"64G\" by "
"default."
msgstr ""
"Container image cache di dalam machinectl telah diatur ke \"64G\" secara "
"default."

msgid ""
"The container property ``container_release`` has been removed as this is "
"automatically set to the same version as the host in the container creation "
"process."
msgstr ""
"Properti kontainer ``container_release`` telah dihapus karena ini secara "
"otomatis disetel ke versi yang sama dengan host dalam proses pembuatan "
"kontainer."

msgid ""
"The copy of the ``/etc/openstack-release`` file is now optional. To disable "
"the copy of the file, set ``openstack_distrib_file`` to ``no``."
msgstr ""
"Salinan file ``/etc/openstack-release`` sekarang opsional. Untuk "
"menonaktifkan salinan file, atur ``openstack_distrib_file`` ke ``no``."

msgid ""
"The data structure for ``ceph_gpg_keys`` has been changed to be a list of "
"dicts, each of which is passed directly to the applicable apt_key/rpm_key "
"module. As such any overrides would need to be reviewed to ensure that they "
"do not pass any key/value pairs which would cause the module to fail."
msgstr ""
"Struktur data untuk ``ceph_gpg_keys`` telah diubah menjadi daftar dicts, "
"yang masing-masing diteruskan langsung ke modul apt_key/rpm_key yang "
"berlaku. Karenanya, setiap pengesampingan akan perlu ditinjau untuk "
"memastikan bahwa mereka tidak melewatkan pasangan key/value yang akan "
"menyebabkan modul gagal."

msgid ""
"The data structure for ``galera_client_gpg_keys`` has been changed to be a "
"dict passed directly to the applicable apt_key/rpm_key module. As such any "
"overrides would need to be reviewed to ensure that they do not pass any key/"
"value pairs which would cause the module to fail."
msgstr ""
"Struktur data untuk ``galera_client_gpg_keys`` telah diubah menjadi dict "
"yang diteruskan langsung ke modul apt_key/rpm_key yang berlaku. Karenanya, "
"setiap pengesampingan akan perlu ditinjau untuk memastikan bahwa mereka "
"tidak melewatkan pasangan key/value yang akan menyebabkan modul gagal."

msgid ""
"The data structure for ``galera_gpg_keys`` has been changed to be a dict "
"passed directly to the applicable apt_key/rpm_key module. As such any "
"overrides would need to be reviewed to ensure that they do not pass any key/"
"value pairs which would cause the module to fail."
msgstr ""
"Struktur data untuk ``galera_gpg_keys`` telah diubah menjadi dict yang "
"diteruskan langsung ke modul apt_key/rpm_key yang berlaku. Karenanya, setiap "
"pengesampingan akan perlu ditinjau untuk memastikan bahwa mereka tidak "
"melewatkan pasangan key/value yang akan menyebabkan modul gagal."

msgid ""
"The data structure for ``rabbitmq_gpg_keys`` has been changed to be a dict "
"passed directly to the applicable apt_key/rpm_key module. As such any "
"overrides would need to be reviewed to ensure that they do not pass any key/"
"value pairs which would cause the module to fail."
msgstr ""
"Struktur data untuk ``rabbitmq_gpg_keys`` telah diubah menjadi dict yang "
"diteruskan langsung ke modul apt_key/rpm_key yang berlaku. Karenanya, setiap "
"pengesampingan akan perlu ditinjau untuk memastikan bahwa mereka tidak "
"melewatkan pasangan key/value yang akan menyebabkan modul gagal."

msgid ""
"The database and user creates have been removed from the ``os_horizon`` "
"role. These tasks have been relocated to the playbooks."
msgstr ""
"Database dan pembuatan user telah dihapus dari peran ``os_horizon``. Tugas "
"ini telah dipindahkan ke playbook."

msgid ""
"The database create and user creates have been removed from the "
"``os_cinder`` role. These tasks have been relocated to the playbooks."
msgstr ""
"Pembuatan database dan pembuatan user telah dihapus dari peran "
"``os_cinder``. Tugas ini telah dipindahkan ke playbook."

msgid ""
"The database create and user creates have been removed from the "
"``os_glance`` role. These tasks have been relocated to the playbooks."
msgstr ""
"Pembuatan database dan pembuatan user telah dihapus dari peran "
"``os_glance``. Tugas ini telah dipindahkan ke playbook."

msgid ""
"The database create and user creates have been removed from the ``os_heat`` "
"role. These tasks have been relocated to the playbooks."
msgstr ""
"Pembuatan database dan pembuatan user telah dihapus dari peran ``os_heat``. "
"Tugas ini telah dipindahkan ke playbook."

msgid ""
"The database create and user creates have been removed from the "
"``os_neutron`` role. These tasks have been relocated to the playbooks."
msgstr ""
"Pembuatan database dan pembuatan user telah dihapus dari peran "
"``os_neutron``. Tugas ini telah dipindahkan ke playbook."

msgid ""
"The database create and user creates have been removed from the ``os_nova`` "
"role. These tasks have been relocated to the playbooks."
msgstr ""
"Pembuatan database dan pembuatan user dihapus dari peran ``os_nova``. Tugas "
"ini telah dipindahkan ke playbook."

msgid ""
"The default Mnesia ``dump_log_write_threshold`` value has changed to ``300`` "
"instead of ``100`` for efficiency. ``dump_log_write_threshold`` specifies "
"the maximum number of writes allowed to the transaction log before a new "
"dump of the log is performed. Increasing this value can increase the "
"performances during the queues/exchanges/bindings creation/destroying. The "
"values should be between 100 and 1000. More detail [1]."
msgstr ""
"Nilai Mnesia ``dump_log_write_threshold`` default telah berubah menjadi "
"``300`` daripada ``100`` untuk efisiensi. ``dump_log_write_threshold`` "
"menentukan jumlah maksimum penulisan yang diizinkan untuk log transaksi "
"sebelum dump baru dari log dilakukan. Peningkatan nilai ini dapat "
"meningkatkan kinerja selama antrian/pertukaran/kreasi binding/penghancuran "
"(queues/exchanges/bindings creation/destroying). Nilai harus antara 100 dan "
"1000. Lebih detail [1]."

msgid ""
"The default TLS verion has been set to TLS1.2.  This only allows version 1.2 "
"of the protocol to be used when terminating or creating TLS connections.  "
"You can change the value with the keystone_ssl_protocol variable."
msgstr ""
"Verifikasi TLS default telah ditetapkan ke TLS1.2. Ini hanya memungkinkan "
"versi 1.2 protokol untuk digunakan ketika mengakhiri atau membuat koneksi "
"TLS. Anda dapat mengubah nilainya dengan variabel keystone_ssl_protocol."

msgid ""
"The default TLS version has been set to TLS1.2.  This only allows version "
"1.2 of the protocol to be used when terminating or creating TLS "
"connections.  You can change the value with the barbican_ssl_protocol "
"variable."
msgstr ""
"Verifikasi TLS default telah ditetapkan ke TLS1.2. Ini hanya memungkinkan "
"versi 1.2 protokol untuk digunakan ketika mengakhiri atau membuat koneksi "
"TLS. Anda dapat mengubah nilainya dengan variabel barbican_ssl_protocol."

msgid ""
"The default TLS version has been set to TLS1.2.  This only allows version "
"1.2 of the protocol to be used when terminating or creating TLS "
"connections.  You can change the value with the gnocchi_ssl_protocol "
"variable."
msgstr ""
"Verifikasi TLS default telah ditetapkan ke TLS1.2. Ini hanya memungkinkan "
"versi 1.2 protokol untuk digunakan ketika mengakhiri atau membuat koneksi "
"TLS. Anda dapat mengubah nilainya dengan variabel gnocchi_ssl_protocol."

msgid ""
"The default TLS version has been set to TLS1.2.  This only allows version "
"1.2 of the protocol to be used when terminating or creating TLS "
"connections.  You can change the value with the horizon_ssl_protocol "
"variable."
msgstr ""
"Versi TLS default telah diatur ke TLS1.2. Ini hanya memungkinkan versi 1.2 "
"protokol untuk digunakan ketika mengakhiri atau membuat koneksi TLS. Anda "
"bisa mengubah nilainya dengan variabel horizon_ssl_protocol."

msgid ""
"The default TLS version has been set to TLS1.2.  This only allows version "
"1.2 of the protocol to be used when terminating or creating TLS "
"connections.  You can change the value with the ssl_protocol variable."
msgstr ""
"Verifikasi TLS default telah ditetapkan ke TLS1.2. Ini hanya memungkinkan "
"versi 1.2 protokol untuk digunakan ketika mengakhiri atau membuat koneksi "
"TLS. Anda dapat mengubah nilainya dengan variabel ssl_protocol."

msgid ""
"The default TLS version has been set to TLS1.2.  This only allows version "
"1.2 of the protocol to be used when terminating or creating TLS "
"connections.  You can change the value with the trove_ssl_protocol variable."
msgstr ""
"Verifikasi TLS default telah ditetapkan ke TLS1.2. Ini hanya memungkinkan "
"versi 1.2 protokol untuk digunakan ketika mengakhiri atau membuat koneksi "
"TLS. Anda dapat mengubah nilainya dengan variabel trove_ssl_protocol."

msgid ""
"The default TLS version has been set to force-tlsv12.  This only allows "
"version 1.2 of the protocol to be used when terminating or creating TLS "
"connections.  You can change the value with the haproxy_ssl_bind_options "
"variable."
msgstr ""
"Verifikasi TLS default telah ditetapkan ke TLS1.2. Ini hanya memungkinkan "
"versi 1.2 protokol untuk digunakan ketika mengakhiri atau membuat koneksi "
"TLS. Anda dapat mengubah nilainya dengan variabel haproxy_ssl_bind_options."

msgid ""
"The default apt sources configuration is now set to only include the "
"``main`` and ``universe`` components as those are the only required "
"components for a functional deployment. If deployers wish to include other "
"components then the variable ``lxc_container_template_apt_components`` may "
"be set in ``/etc/openstack_deploy/user_variables.yml`` with the full list of "
"desired components."
msgstr ""
"Konfigurasi sumber apt default sekarang diatur untuk hanya menyertakan "
"komponen ``main`` dan ``universe`` karena itu adalah satu-satunya komponen "
"yang diperlukan untuk penyebaran fungsional. Jika deployer ingin memasukkan "
"komponen lain, maka variabel ``lxc_container_template_apt_components`` dapat "
"diatur dalam ``/etc/openstack_deploy/user_variables.yml`` dengan daftar "
"lengkap komponen yang diinginkan."

msgid ""
"The default apt sources configuration uses all components. If deployers wish "
"to change this to reduce the components configured then the variable "
"``lxc_container_template_apt_components`` may be set in ``/etc/"
"openstack_deploy/user_variables.yml`` with the full list of desired "
"components."
msgstr ""
"Konfigurasi sumber apt default menggunakan semua komponen. Jika deployer "
"ingin mengubah ini untuk mengurangi komponen yang dikonfigurasi maka "
"variabel ``lxc_container_template_apt_components`` dapat diatur dalam ``/etc/"
"openstack_deploy/user_variables.yml`` dengan daftar lengkap komponen yang "
"diinginkan."

msgid ""
"The default behaviour of ``ensure_endpoint`` in the keystone module has "
"changed to update an existing endpoint, if one exists that matches the "
"service name, type, region and interface. This ensures that no duplicate "
"service entries can exist per region."
msgstr ""
"Perilaku default ``ensure_endpoint`` dalam modul keystone telah berubah "
"untuk memperbarui endpoint yang ada, jika ada yang cocok dengan nama "
"layanan, jenis, wilayah, dan antarmuka. Ini memastikan bahwa tidak ada entri "
"layanan duplikat yang dapat ada per wilayah."

msgid ""
"The default behaviour of rsync, to perform reverse lookups, has been changed "
"to ``False``. This can be set to ``True`` by setting the "
"``swift_rsync_reverse_lookup`` variable to ``True``."
msgstr ""
"Perilaku default rsync, untuk melakukan pencarian terbalik, telah diubah "
"menjadi ``False``. Ini dapat diatur ke ``True`` dengan mengatur variabel "
"``swift_rsync_reverse_lookup`` ke ``True``."

msgid ""
"The default bind address for all openstack services and infrastructure "
"services such as galera, rabbitmq and memcached has changed from 0.0.0.0 to "
"the IP address of the openstack mangement network on the relevent host or "
"container. Deployers should ensure that any additional systems that expect "
"to communicate with internal components of their openstack-ansible "
"deployment do so over the managment network. Services which are bound to the "
"management network IP will not be accessible via other interfaces."
msgstr ""
"Alamat bind default untuk semua layanan openstack dan layanan infrastruktur "
"seperti galera, rabbitmq, dan memcache telah berubah dari 0.0.0.0 menjadi "
"alamat IP jaringan pengelolaan openstack pada host atau container yang "
"relevan. Deployer harus memastikan bahwa sistem tambahan apa pun yang "
"berharap untuk berkomunikasi dengan komponen internal dari penerapan "
"openstack-ansible mereka melakukannya melalui jaringan manajemen. Layanan "
"yang terikat ke IP jaringan manajemen tidak akan dapat diakses melalui "
"interfaces lain."

msgid ""
"The default container apt sources have been changed from using ``http://"
"mirror.rackspace.com/ubuntu`` to ``http://archive.ubuntu.com/ubuntu/`` for "
"packages and ``http://security.ubuntu.com/ubuntu`` for security packages. "
"This is to resolve issues with unavailable packages during the install "
"process due to incomplete mirror updates."
msgstr ""
"Sumber apt container default telah diubah dari menggunakan ``http://mirror."
"rackspace.com/ubuntu`` menjadi ``http://archive.ubuntu.com/ubuntu/`` untuk "
"paket dan ``http://security.ubuntu.com/ubuntu`` untuk paket keamanan. Ini "
"untuk menyelesaikan masalah dengan paket yang tidak tersedia selama proses "
"instalasi karena pembaruan mirror tidak lengkap."

msgid ""
"The default container apt sources have been changed from using ``https://"
"mirror.rackspace.com/ubuntu`` to ``http://archive.ubuntu.com/ubuntu`` for "
"packages and ``http://security.ubuntu.com/ubuntu`` for security packages. "
"This is to resolve issues with unavailable packages during the install "
"process due to incomplete mirror updates."
msgstr ""
"Sumber apt kontainer default telah diubah dari menggunakan ``https://mirror."
"rackspace.com/ubuntu`` menjadi ``http://archive.ubuntu.com/ubuntu`` untuk "
"paket dan ``http://security.ubuntu.com/ubuntu`` untuk paket keamanan. Ini "
"untuk menyelesaikan masalah dengan paket yang tidak tersedia selama proses "
"instalasi karena pembaruan mirror tidak lengkap."

msgid ""
"The default database collation has changed from `utf8_unicode_ci` to "
"`utf8_general_ci`. Existing databases and tables will need to be converted."
msgstr ""
"Susunan database default telah berubah dari  `utf8_unicode_ci` menjadi "
"`utf8_general_ci`. Database dan tabel yang ada perlu dikonversi."

msgid ""
"The default horizon instance launch panels have been changed to the next "
"generation panels. To enable legacy functionality set the following options "
"accordingly:"
msgstr ""
"Panel peluncuran instance horizon default telah diubah menjadi panel "
"generasi berikutnya. Untuk mengaktifkan fungsi legacy, setel opsi berikut "
"sesuai:"

msgid ""
"The default location for the image downloads in the ``os_tempest`` role set "
"by the ``tempest_image_dir`` variable has now been changed to be ``/opt/"
"cache/files`` in order to match the default location in nodepool. This "
"improves the reliability of CI testing in OpenStack CI as it will find the "
"file already cached there."
msgstr ""
"Lokasi default untuk unduhan image dalam peran ``os_tempest`` yang "
"ditetapkan oleh variabel ``tempest_image_dir`` sekarang telah diubah menjadi "
"``/opt/cache/files``  untuk mencocokkan lokasi default di nodepool. Ini "
"meningkatkan keandalan pengujian CI di OpenStack CI karena akan menemukan "
"file sudah di-cache di sana."

msgid ""
"The default location of the default tempest configuration is now ``/etc/"
"tempest/tempest.conf`` rather than the previous default of ``$HOME/.tempest/"
"etc``."
msgstr ""
"Lokasi default dari konfigurasi tempest default sekarang ``/etc/tempest/"
"tempest.conf`` sebagai ganti default sebelumnya ``$HOME/.tempest/etc``."

msgid ""
"The default method for download roles has been switched from ``galaxy`` to "
"``git-clone``. This has no functional effect, but is now required in order "
"to successfully download the ``ceph-ansible`` repository. In order to "
"prevent clashes between the old and new roles, the existing ``/etc/ansible/"
"roles/ceph*`` folders should be removed prior to running ``scripts/bootstrap-"
"ansible.sh`` during the minor upgrade process."
msgstr ""
"Metode default untuk peran unduhan telah diubah dari ``galaxy`` ke ``git-"
"clone``. Ini tidak memiliki efek fungsional, tetapi sekarang diperlukan "
"untuk berhasil mengunduh repositori ``ceph-ansible``. Untuk mencegah "
"bentrokan antara peran lama dan baru, folder ``/etc/ansible/roles/ceph*`` "
"yang ada harus dihapus sebelum menjalankan ``scripts/bootstrap-ansible.sh`` "
"selama proses upgrade minor. ."

msgid ""
"The default nova console type has been changed to novnc. Spice is still "
"supported however due to novnc being more actively maintained it is now a "
"better default option."
msgstr ""
"Jenis konsol nova default telah diubah menjadi novnc. Spice masih didukung "
"namun karena novnc lebih aktif dipelihara sekarang menjadi opsi default yang "
"lebih baik."

msgid ""
"The default queue policy has changed to ``^(?!(amq\\.)|(.*_fanout_)|"
"(reply_)).*`` instead of ``^(?!amq\\.).*`` for efficiency. The new HA policy "
"excludes reply queues (these queues have a single consumer and TTL policy), "
"fanout queues (they have the TTL policy) and amq queues (they are auto-"
"delete queues, with a single consumer)."
msgstr ""
"Kebijakan antrian default telah berubah menjadi  ``^(?!(amq\\.)|(.*_fanout_)|"
"(reply_)).*`` instead of ``^(?!amq\\.).*`` untuk efisiensi. Kebijakan HA "
"yang baru tidak termasuk reply queues (antrian ini memiliki satu konsumen "
"dan kebijakan TTL), fanout queues (mereka memiliki kebijakan TTL) dan amq "
"queues (antrian auto-delete, dengan satu konsumen)."

msgid ""
"The default ulimit for RabbitMQ is now 65536. Deployers can still adjust "
"this limit using the ``rabbitmq_ulimit`` Ansible variable."
msgstr ""
"Ulimit default untuk RabbitMQ sekarang 65536. Deployer masih dapat "
"menyesuaikan batas ini menggunakan variabel ``rabbitmq_ulimit``."

msgid ""
"The default value of ``service_credentials/os_endpoint_type`` within "
"ceilometer's configuration file has been changed to **internalURL**. This "
"may be overridden through the use of the "
"``ceilometer_ceilometer_conf_overrides`` variable."
msgstr ""
"Nilai default dari  ``service_credentials/os_endpoint_type`` dalam file "
"konfigurasi ceilometer telah diubah menjadi **internalURL**. Ini mungkin "
"ditimpa melalui penggunaan variabel ``ceilometer_ceilometer_conf_overrides``."

msgid ""
"The default values for ``ceph_gpg_keys`` have been changed for all supported "
"platforms and now use vendored keys. This means that the task execution will "
"no longer reach out to the internet to add the keys, making offline or proxy-"
"based installations easier and more reliable."
msgstr ""
"Nilai default untuk ``ceph_gpg_keys`` telah diubah untuk semua platform yang "
"didukung dan sekarang menggunakan kunci yang dibatalkan. Ini berarti bahwa "
"pelaksanaan tugas tidak lagi menjangkau ke internet untuk menambahkan kunci, "
"membuat instalasi offline atau berbasis proxy lebih mudah dan lebih dapat "
"diandalkan."

msgid ""
"The default values for ``galera_client_gpg_keys`` have been changed for all "
"supported platforms will use vendored keys. This means that the task "
"execution will no longer reach out to the internet to add the keys, making "
"offline or proxy-based installations easier and more reliable."
msgstr ""
"Nilai default untuk ``galera_client_gpg_keys`` telah diubah untuk semua "
"platform yang didukung akan menggunakan kunci yang dibatalkan. Ini berarti "
"bahwa pelaksanaan tugas tidak lagi menjangkau ke internet untuk menambahkan "
"kunci, membuat instalasi offline atau berbasis proxy lebih mudah dan lebih "
"dapat diandalkan."

msgid ""
"The default values for ``galera_gpg_keys`` have been changed for all "
"supported platforms will use vendored keys. This means that the task "
"execution will no longer reach out to the internet to add the keys, making "
"offline or proxy-based installations easier and more reliable."
msgstr ""
"Nilai default untuk ``galera_gpg_keys`` telah diubah untuk semua platform "
"yang didukung akan menggunakan kunci yang dibatalkan. Ini berarti bahwa "
"pelaksanaan tugas tidak lagi menjangkau ke internet untuk menambahkan kunci, "
"membuat instalasi offline atau berbasis proxy lebih mudah dan lebih dapat "
"diandalkan."

msgid ""
"The default values for ``rabbitmq_gpg_keys`` have been changed for all "
"supported platforms will use vendored keys. This means that the task "
"execution will no longer reach out to the internet to add the keys, making "
"offline or proxy-based installations easier and more reliable."
msgstr ""
"Nilai default untuk ``rabbitmq_gpg_keys`` telah diubah untuk semua platform "
"yang didukung akan menggunakan kunci yang dibatalkan. Ini berarti bahwa "
"pelaksanaan tugas tidak lagi menjangkau ke internet untuk menambahkan kunci, "
"membuat instalasi offline atau berbasis proxy lebih mudah dan lebih dapat "
"diandalkan."

msgid ""
"The default variable `nova_default_schedule_zone` was previously set by "
"default to ``nova``. This default has been removed to allow the default to "
"be set by the nova code instead. Deployers wishing to maintain the default "
"availability zone of nova must now set the variable as a user_variables.yml "
"or group_vars override."
msgstr ""
"Variabel default `nova_default_schedule_zone` sebelumnya ditetapkan secara "
"default ke ``nova``.  Default ini telah dihapus untuk memungkinkan default "
"diatur oleh kode nova sebagai gantinya. Deployer yang ingin mempertahankan "
"zona ketersediaan default nova sekarang harus menetapkan variabel sebagai "
"override user_variables.yml atau group_vars."

msgid ""
"The deployer can now define an environment variable ``GROUP_VARS_PATH`` with "
"the folders of its choice (separated by the colon sign) to define an user "
"space group_vars folder. These vars will apply but be (currently) overriden "
"by the OpenStack-Ansible default group vars, by the set facts, and by the "
"user_* variables. If the deployer defines multiple paths, the variables "
"found are merged, and precedence is increasing from left to right (the last "
"defined in GROUP_VARS_PATH wins)"
msgstr ""
"Deployer sekarang dapat mendefinisikan variabel lingkungan "
"``GROUP_VARS_PATH`` dengan folder pilihannya (dipisahkan oleh tanda titik "
"dua) untuk menentukan folder space_vars ruang pengguna. Vars ini akan "
"berlaku tetapi akan (saat ini) ditimpa oleh vars grup default OpenStack-"
"Ansible, oleh fakta yang ditetapkan, dan oleh variabel user_*. Jika deployer "
"mendefinisikan beberapa lintasan, variabel yang ditemukan digabungkan, dan "
"prioritas meningkat dari kiri ke kanan (yang terakhir didefinisikan dalam "
"GROUP_VARS_PATH wins)"

msgid ""
"The deployer can now define an environment variable ``HOST_VARS_PATH`` with "
"the folders of its choice (separated by the colon sign) to define an user "
"space host_vars folder. These vars will apply but be (currently) overriden "
"by the OpenStack-Ansible default host vars, by the set facts, and by the "
"user_* variables. If the deployer defines multiple paths, the variables "
"found are merged, and precedence is increasing from left to right (the last "
"defined in HOST_VARS_PATH wins)"
msgstr ""
"Deployer sekarang dapat mendefinisikan variabel lingkungan "
"``HOST_VARS_PATH`` dengan folder pilihannya (dipisahkan oleh tanda titik "
"dua) untuk menentukan folder host_vars ruang pengguna. Vars ini akan berlaku "
"tetapi akan (saat ini) diganti oleh vars host default OpenStack-Ansible, "
"oleh fakta yang ditetapkan, dan oleh variabel user_*. Jika deployer "
"mendefinisikan beberapa lintasan, variabel yang ditemukan digabungkan, dan "
"prioritas meningkat dari kiri ke kanan (yang terakhir didefinisikan dalam "
"HOST_VARS_PATH wins)"

msgid ""
"The deployment configuration file ``openstack_environment.yml`` has been "
"removed and is no longer used in the dynamic inventory generation process. "
"This file was previously rendered functionally irrelevant to the inventory "
"generation process in the Liberty release."
msgstr ""
"File konfigurasi penyebaran ``openstack_environment.yml`` telah dihapus dan "
"tidak lagi digunakan dalam proses pembuatan inventaris dinamis. File ini "
"sebelumnya secara fungsional tidak relevan dengan proses pembuatan "
"inventaris dalam rilis Liberty."

msgid ""
"The deprecated Neutron LBaaS v2 plugin has been removed from the Neutron "
"role."
msgstr ""
"Plugin Neutron LBaaS v2 yang sudah usang telah dihapus dari peran Neutron."

msgid ""
"The deprecated Neutron LBaaS v2 plugin support has been removed from "
"openstack-ansible."
msgstr ""
"Dukungan plugin Neutron LBaaS v2 yang sudah usang telah dihapus dari "
"openstack-ansible."

msgid ""
"The dictionary-based variables in ``defaults/main.yml`` are now individual "
"variables. The dictionary-based variables could not be changed as the "
"documentation instructed. Instead it was required to override the entire "
"dictionary. Deployers must use the new variable names to enable or disable "
"the security configuration changes applied by the security role. For more "
"information, see `Launchpad Bug 1577944 <https://bugs.launchpad.net/"
"openstack-ansible/+bug/1577944>`_."
msgstr ""
"Variabel dictionary-based di  ``defaults/main.yml`` sekarang menjadi "
"variabel individual. Variabel dictionary-based tidak dapat diubah seperti "
"yang diperintahkan oleh dokumentasi. Sebaliknya itu diperlukan untuk menimpa "
"seluruh dictionary. Deployer harus menggunakan nama variabel baru untuk "
"mengaktifkan atau menonaktifkan perubahan konfigurasi keamanan yang "
"diterapkan oleh peran keamanan. Untuk informasi lebih lanjut, lihat "
"`Launchpad Bug 1577944 <https://bugs.launchpad.net/openstack-ansible/"
"+bug/1577944>`_."

msgid ""
"The distribution of the ``.my.cnf`` database access configuration file which "
"contains sensitive root credentials has now been limited to only be "
"distributed to containers and hosts which require it for troubleshooting "
"purposes."
msgstr ""
"Distribusi file konfigurasi akses database ``.my.cnf`` yang berisi "
"kredensial root sensitif kini telah dibatasi hanya didistribusikan ke "
"kontainer dan host yang memerlukannya untuk tujuan pemecahan masalah."

msgid ""
"The distribution of the ``.my.cnf`` database access configuration file which "
"contains sensitive root credentials has now been limited to only be "
"distributed to containers and hosts which require it for troubleshooting "
"purposes. It is recommended that this file be removed from all hosts and "
"containers. The only containers that should have the file are the Utility "
"container and the Galera containers. This may be done by executing ``ansible "
"'all:!galera:!utility' -m shell -a 'rm -f /root/.my.cnf'`` from the ``/opt/"
"openstack-ansible/`` directory."
msgstr ""
"Distribusi file konfigurasi akses database ``.my.cnf`` yang berisi "
"kredensial root sensitif kini telah dibatasi hanya didistribusikan ke "
"kontainer dan host yang memerlukannya untuk tujuan pemecahan masalah. "
"Disarankan bahwa file ini dihapus dari semua host dan kontainer. Satu-"
"satunya kontainer yang harus memiliki file adalah kontainer Utility dan "
"kontainer Galera. Ini dapat dilakukan dengan mengeksekusi direktori "
"``ansible 'all:!galera:!utility' -m shell -a 'rm -f /root/.my.cnf'`` from "
"the ``/opt/openstack-ansible/`` ."

msgid ""
"The distribution package lookup and data output has been removed from the "
"py_pkgs lookup so that the repo-build use of py_pkgs has reduced output and "
"the lookup is purpose specific for python packages only."
msgstr ""
"Pencarian paket distribusi dan output data telah dihapus dari pencarian "
"py_pkgs sehingga penggunaan repo-build dari py_pkgs telah mengurangi output "
"dan pencarian khusus untuk paket python saja."

msgid ""
"The documentation for STIG V-51337 has more information about how each LSM "
"is enabled along with special notes for SELinux."
msgstr ""
"Dokumentasi untuk STIG V-51337 memiliki informasi lebih lanjut tentang "
"bagaimana setiap LSM diaktifkan bersama dengan catatan spesial untuk SELinux."

msgid ""
"The dynamic_inventory script previously set the provider network attributes "
"``is_container_address`` and ``is_ssh_address`` to True for the management "
"network regardless of whether a deployer had them configured this way or "
"not. Now, these attributes must be configured by deployers and the "
"dynamic_inventory script will fail if they are missing or not True."
msgstr ""
"Script dynamic_inventory sebelumnya menetapkan atribut jaringan provider "
"``is_container_address`` dan ``is_ssh_address`` ke True untuk jaringan "
"manajemen terlepas dari apakah seorang deployer telah mereka konfigurasikan "
"dengan cara ini atau tidak. Sekarang, atribut ini harus dikonfigurasikan "
"oleh deployer dan script dynamic_inventory akan gagal jika hilang atau not "
"True."

msgid ""
"The endpoint which designate uses to communicate with neutron has been set "
"to the internalURL by default. This change has been done within the template "
"``designate.conf.j2`` and can be changed using the "
"``designate_designate_conf_overrides`` variable."
msgstr ""
"Endpoint yang digunakan untuk berkomunikasi dengan neutron telah ditetapkan "
"ke internalURL secara default. Perubahan ini telah dilakukan di dalam "
"template ``designate.conf.j2`` dan dapat diubah menggunakan variabel "
"``designate_designate_conf_overrides``."

msgid ""
"The entire repo build process is now idempotent. From now on when the repo "
"build is re-run, it will only fetch updated git repositories and rebuild the "
"wheels/venvs if the requirements have changed, or a new release is being "
"deployed."
msgstr ""
"Seluruh proses pembuatan repo sekarang idempoten. Mulai sekarang ketika repo "
"build dijalankan kembali (re-run), ia hanya akan mengambil repositori git "
"yang diperbarui dan membangun kembali (rebuild) wheels/venvs jika "
"persyaratan telah berubah, atau rilis baru sedang digunakan."

msgid ""
"The env.d directory included with OpenStack-Ansible is now used as the first "
"source for the environment skeleton, and ``/etc/openstack_deploy/env.d`` "
"will be used only to override values. Deployers without customizations will "
"no longer need to copy the env.d directory to /etc/openstack_deploy. As a "
"result, the env.d copy operation has been removed from the node bootstrap "
"role."
msgstr ""
"Direktori env.d yang disertakan dengan OpenStack-Ansible sekarang digunakan "
"sebagai sumber pertama untuk kerangka lingkungan, dan ``/etc/"
"openstack_deploy/env.d`` hanya akan digunakan untuk mengganti nilai. "
"Deployer tanpa kustomisasi tidak perlu lagi menyalin direktori env.d ke /etc/"
"openstack_deploy. Akibatnya, operasi copy env.d telah dihapus dari peran "
"bootstrap node."

msgid ""
"The environment variable ``FORKS`` is no longer used. The standard Ansible "
"environment variable ``ANSIBLE_FORKS`` should be used instead."
msgstr ""
"Variabel lingkungan ``FORKS`` tidak lagi digunakan. Variabel lingkungan "
"Ansible standar ``ANSIBLE_FORKS`` harus digunakan sebagai gantinya."

msgid "The environment variables added are:"
msgstr "Variabel lingkungan yang ditambahkan adalah:"

msgid ""
"The extra packages percona packages used by the ppc64le are now downloaded "
"by the Ansible deployment host by default, as opposed to the target hosts. "
"Once downloaded the packages are pushed up to the target hosts. This "
"behaviour may be adjusted by setting "
"``galera_server_extra_package_downloader`` to ``target-host``. The packages "
"are downloaded to the path set in ``galera_server_extra_package_path``."
msgstr ""
"Paket tambahan paket percona yang digunakan oleh ppc64le sekarang diunduh "
"oleh host deployment Ansible secara default, sebagai lawan dari host target. "
"Setelah diunduh, paket didorong ke host target. Perilaku ini dapat "
"disesuaikan dengan mengatur ``galera_server_extra_package_downloader`` ke "
"``target-host``. Paket tersebut diunduh ke jalur yang ditetapkan "
"``galera_server_extra_package_path``."

msgid ""
"The filename of the apt source can now be defined with the variable "
"``filename`` inside the dicts ``galera_repo`` and "
"``galera_percona_xtrabackup_repo``."
msgstr ""
"Nama file dari sumber apt sekarang dapat didefinisikan dengan variabel "
"``filename`` di dalam dict ``galera_repo`` dan "
"``galera_percona_xtrabackup_repo``."

msgid ""
"The filename of the apt source for the haproxy ppa can now be defined with "
"the ``filename`` section of the dict ``haproxy_repo``."
msgstr ""
"Nama file sumber apt untuk haproxy ppa sekarang dapat didefinisikan dengan "
"bagian ``filename`` dict ``haproxy_repo``."

msgid ""
"The filename of the apt source for the ubuntu cloud archive can now be "
"defined with the variable ``uca_apt_source_list_filename``."
msgstr ""
"Nama file sumber apt untuk arsip cloud ubuntu sekarang dapat didefinisikan "
"dengan variabel ``uca_apt_source_list_filename``."

msgid ""
"The filename of the apt source for the ubuntu cloud archive used in ceph "
"client can now be defined by giving a filename in the uca part of the dict "
"``ceph_apt_repos``."
msgstr ""
"Nama file sumber apt untuk arsip cloud ubuntu yang digunakan dalam ceph "
"client sekarang dapat didefinisikan dengan memberikan nama file di bagian "
"uca dict ``ceph_apt_repos``."

msgid ""
"The filename of the apt/yum source can now be defined with the variable "
"``mariadb_repo_filename``."
msgstr ""
"Nama file dari sumber apt/yum sekarang dapat didefinisikan dengan variabel "
"``mariadb_repo_filename``."

msgid ""
"The first release of the Red Hat Enterprise Linux 7 STIG was entirely "
"renumbered from the pre-release versions. Many of the STIG configurations "
"simply changed numbers, but some were removed or changed. A few new "
"configurations were added as well."
msgstr ""
"Rilis pertama Red Hat Enterprise Linux 7 STIG sepenuhnya dinomori ulang dari "
"versi pra-rilis. Banyak konfigurasi STIG hanya mengubah angka, tetapi "
"beberapa dihapus atau diubah. Beberapa konfigurasi baru juga ditambahkan."

msgid ""
"The first tier of the ``keystone_ldap`` dictionary variable now relates to "
"the Keystone Domain name. An existing ``keystone_ldap`` configuration entry "
"can be converted by renaming the ``ldap`` key to the domain name 'Default'. "
"**Note** that the domain name entry is case-sensitive."
msgstr ""
"Tingkat pertama dari variabel kamus ``keystone_ldap`` sekarang berhubungan "
"dengan nama Keystone Domain. Entri konfigurasi ``keystone_ldap`` yang ada "
"dapat dikonversi dengan mengganti nama kunci ``ldap`` ke nama domain "
"'Default'. **Note** bahwa entri nama domain adalah peka huruf besar-kecil "
"(case-sensitive)."

msgid ""
"The fix for the broken bind mounts in the galera container (see `bug 1609862 "
"<https://launchpad.net/bugs/1609862>` for details) will be applied to the "
"LXC container configuration file, but a restart of each galera container is "
"required to put the change into effect."
msgstr ""
"Perbaikan untuk pemasangan bind yang rusak di kontainer galera (lihat `bug "
"1609862 <https://launchpad.net/bugs/1609862>` untuk detailnya) akan "
"diterapkan pada file konfigurasi kontainer LXC, tetapi memulai kembali "
"(restart) setiap kontainer galera diperlukan untuk memberlakukan perubahan."

msgid ""
"The fix to remove deleted global override keys mistakenly deleted the "
"``container_cidr`` key. This was used by downstream consumers, and cannot be "
"reconstructed with other information inside the inventory file. Regression "
"tests were also added."
msgstr ""
"Perbaikan untuk menghapus kunci global override yang dihapus secara keliru "
"menghapus kunci ``container_cidr``. Ini digunakan oleh konsumen hilir, dan "
"tidak dapat direkonstruksi dengan informasi lain di dalam file inventory. "
"Tes regresi juga ditambahkan."

msgid ""
"The following Nova tunables have been removed, users need to start using the "
"`nova_nova_conf_overrides` dictionary to override them. If those values were "
"not previously overridden, there should be no need to override them. - "
"nova_quota_cores - nova_quota_injected_file_content_bytes - "
"nova_quota_injected_file_path_length - nova_quota_injected_files - "
"nova_quota_instances - nova_quota_key_pairs - nova_quota_metadata_items - "
"nova_quota_ram - nova_quota_server_group_members - nova_quota_server_groups "
"- nova_max_instances_per_host - nova_scheduler_available_filters - "
"nova_scheduler_weight_classes - nova_scheduler_driver - "
"nova_scheduler_driver_task_period - nova_rpc_conn_pool_size - "
"nova_rpc_thread_pool_size - nova_rpc_response_timeout - "
"nova_force_config_drive - nova_enable_instance_password - "
"nova_default_schedule_zone - nova_fatal_deprecations - "
"nova_resume_guests_state_on_host_boot - nova_cross_az_attach - "
"nova_remove_unused_resized_minimum_age_seconds - nova_cpu_model - "
"nova_cpu_model_extra_flags"
msgstr ""
"Nova tunables berikut telah dihapus, pengguna harus mulai menggunakan kamus "
"`nova_nova_conf_overrides` untuk menimpanya. Jika nilai-nilai itu sebelumnya "
"tidak diganti, seharusnya tidak perlu menimpa mereka. - nova_quota_cores - "
"nova_quota_injected_file_content_bytes - "
"nova_quota_injected_file_path_length - nova_quota_injected_files - "
"nova_quota_instances - nova_quota_key_pairs - nova_quota_metadata_items - "
"nova_quota_ram - nova_quota_server_group_members - nova_quota_server_groups "
"- nova_max_instances_per_host - nova_scheduler_available_filters - "
"nova_scheduler_weight_classes - nova_scheduler_driver - "
"nova_scheduler_driver_task_period - nova_rpc_conn_pool_size - "
"nova_rpc_thread_pool_size - nova_rpc_response_timeout - "
"nova_force_config_drive - nova_enable_instance_password - "
"nova_default_schedule_zone - nova_fatal_deprecations - "
"nova_resume_guests_state_on_host_boot - nova_cross_az_attach - "
"nova_remove_unused_resized_minimum_age_seconds - nova_cpu_model - "
"nova_cpu_model_extra_flags"

msgid ""
"The following Nova variables have been removed because they have no effect "
"in the current release of Nova. - nova_max_age - nova_osapi_compute_workers "
"- nova_metadata_workers"
msgstr ""
"Variabel Nova berikut telah dihapus karena tidak memiliki efek dalam rilis "
"Nova saat ini. - nova_max_age - nova_osapi_compute_workers - "
"nova_metadata_workers"

msgid ""
"The following headers were added as additional default (and static) values. "
"`X-Content-Type-Options nosniff`, `X-XSS-Protection \"1; mode=block\"`, and "
"`Content-Security-Policy \"default-src 'self' https: wss:;\"`.  "
"Additionally, the `X-Frame-Options DENY` header was added, defaulting to "
"DENY.  You may override the header via the `keystone_x_frame_options` "
"variable."
msgstr ""
"Header berikut ditambahkan sebagai nilai default tambahan (dan statis). `X-"
"Content-Type-Options nosniff`, `X-XSS-Protection \"1; mode=block\"`, dan "
"`Content-Security-Policy \"default-src 'self' https: wss:;\"`. Selain itu, "
"tajuk `X-Frame-Options DENY` telah ditambahkan, default ke DENY. Anda dapat "
"mengganti header melalui variabel `keystone_x_frame_options`."

msgid ""
"The following secrets are no longer used by OpenStack-Ansible and can be "
"removed from user_secrets.yml:"
msgstr ""
"Rahasia berikut tidak lagi digunakan oleh OpenStack-Ansible dan dapat "
"dihapus dari user_secrets.yml:"

msgid ""
"The following variable changes have been made in the  ``lxc_host`` role:"
msgstr "Perubahan variabel berikut telah dibuat dalam peran ``lxc_host``:"

msgid ""
"The following variable name changes have been implemented in order to better "
"reflect their purpose."
msgstr ""
"Perubahan nama variabel berikut telah diterapkan untuk lebih mencerminkan "
"tujuan mereka."

msgid ""
"The following variables are no longer used and have therefore been removed."
msgstr "Variabel berikut tidak lagi digunakan dan karenanya telah dihapus."

msgid ""
"The following variables have been removed as they no longer serve any "
"purpose."
msgstr ""
"Variabel berikut telah dihapus karena tidak lagi melayani tujuan apa pun."

msgid ""
"The following variables have been removed because they are no longer used. * "
"``galera_percona_xtrabackup_repo`` * ``use_percona_upstream`` * "
"``galera_xtrabackup_compression`` * ``galera_server_percona_distro_packages``"
msgstr ""
"Variabel berikut telah dihapus karena tidak lagi digunakan. * "
"``galera_percona_xtrabackup_repo`` * ``use_percona_upstream`` * "
"``galera_xtrabackup_compression`` * ``galera_server_percona_distro_packages``"

msgid ""
"The following variables have been removed from the ``haproxy_server`` role "
"as they are no longer necessary or used. - haproxy_repo - haproxy_gpg_keys - "
"haproxy_required_distro_packages"
msgstr ""
"Variabel berikut telah dihapus dari peran ``haproxy_server`` karena tidak "
"lagi diperlukan atau digunakan. - haproxy_repo - haproxy_gpg_keys - "
"haproxy_required_distro_packages"

msgid ""
"The following variables have been removed from the ``os_ceilometer`` role as "
"their respective upstream files are no longer present. * "
"``ceilometer_event_definitions_yaml_overrides`` * "
"``ceilometer_event_pipeline_yaml_overrides``"
msgstr ""
"Variabel berikut telah dihapus dari peran ``os_ceilometer`` karena masing-"
"masing file hulu tidak lagi ada. * "
"``ceilometer_event_definitions_yaml_overrides`` * "
"``ceilometer_event_pipeline_yaml_overrides``"

msgid ""
"The following variables have been removed from the ``os_tempest`` role to "
"simplify it. They have been replaced through the use of the data structure "
"``tempest_images`` which now has equivalent variables per image. - "
"cirros_version - tempest_img_url - tempest_image_file - "
"tempest_img_disk_format - tempest_img_name - tempest_images.sha256 (replaced "
"by checksum)"
msgstr ""
"Variabel berikut telah dihapus dari peran ``os_tempest`` untuk "
"menyederhanakannya. Mereka telah diganti melalui penggunaan struktur data "
"``tempest_images`` yang sekarang memiliki variabel setara per image. - "
"cirros_version - tempest_img_url - tempest_image_file - "
"tempest_img_disk_format - tempest_img_name - tempest_images.sha256 (replaced "
"by checksum)"

msgid ""
"The following variables have been renamed in order to make the variable "
"names neutral for multiple operating systems."
msgstr ""
"Variabel berikut telah diubah namanya untuk membuat nama variabel netral "
"untuk beberapa sistem operasi."

msgid "The following variables therefore have been removed."
msgstr "Karena itu variabel berikut telah dihapus."

msgid ""
"The functionality previously using these variables has been transitioned to "
"using a simpler data structure."
msgstr ""
"Fungsi yang sebelumnya menggunakan variabel-variabel ini telah ditransisikan "
"untuk menggunakan struktur data yang lebih sederhana."

msgid ""
"The galera cluster now supports cluster health checks over HTTP using port "
"9200. The new cluster check ensures a node is healthy by running a simple "
"query against the wsrep sync status using monitoring user. This change will "
"provide for a more robust cluster check ensuring we have the most fault "
"tolerant galera cluster possible."
msgstr ""
"Cluster galera sekarang mendukung pemeriksaan kesehatan cluster melalui HTTP "
"menggunakan port 9200. Pemeriksaan cluster baru memastikan node sehat dengan "
"menjalankan kueri sederhana terhadap status sinkronisasi wsrep menggunakan "
"pengguna pemantauan. Perubahan ini akan menyediakan untuk pemeriksaan gugus "
"yang lebih kuat yang memastikan kami memiliki galera yang paling toleran "
"terhadap kesalahan."

msgid ""
"The galera_client role always checks whether the latest package is installed "
"when executed. If a deployer wishes to change the check to only validate the "
"presence of the package, the option ``galera_client_package_state`` should "
"be set to ``present``."
msgstr ""
"Peran galera_client selalu memeriksa apakah paket terbaru diinstal ketika "
"dieksekusi. Jika seorang penggelar ingin mengubah tanda centang untuk hanya "
"memvalidasi keberadaan paket, opsi ``galera_client_package_state`` harus "
"diatur ke ``present``."

msgid "The galera_client role now installs MariaDB client version 10.1."
msgstr "Peran galera_client sekarang menginstal klien MariaDB versi 10.1."

msgid ""
"The galera_client role now supports the ability to configure whether apt/yum "
"tasks install the latest available package, or just ensure that the package "
"is present. The default action is to ensure that the latest package is "
"present. The action taken may be changed to only ensure that the package is "
"present by setting ``galera_client_package_state`` to ``present``."
msgstr ""
"Peran galera_client sekarang mendukung kemampuan untuk mengonfigurasi apakah "
"tugas apt/yum menginstal paket terbaru yang tersedia, atau hanya memastikan "
"bahwa paket tersebut ada. Tindakan default adalah untuk memastikan bahwa "
"paket terbaru hadir. Tindakan yang diambil dapat diubah hanya untuk "
"memastikan bahwa paket hadir dengan mengatur ``galera_client_package_state`` "
"ke ``present``."

msgid ""
"The galera_server role always checks whether the latest package is installed "
"when executed. If a deployer wishes to change the check to only validate the "
"presence of the package, the option ``galera_server_package_state`` should "
"be set to ``present``."
msgstr ""
"Peran galera_server selalu memeriksa apakah paket terbaru diinstal ketika "
"dieksekusi. Jika seorang penggelar ingin mengubah tanda centang untuk hanya "
"memvalidasi keberadaan paket, opsi ``galera_server_package_state`` harus "
"diatur ke  ``present``."

msgid ""
"The galera_server role now includes the functionality from the galera_client "
"role, and as a result a number of the variables from the galera_client "
"defaults are now available to override in the galera_server role defaults. "
"In addition, a number of default variables have been generalised, removing "
"the specific `_client_` or `_server_` parts of the names. Users of this role "
"should check that any overrides they are using have the correct variables "
"names for the new combined role."
msgstr ""
"Peran galera_server sekarang termasuk fungsionalitas dari peran "
"galera_client, dan sebagai hasilnya sejumlah variabel dari standar "
"galera_client sekarang tersedia untuk menggantikan dalam standar peran "
"galera_server. Selain itu, sejumlah variabel default telah digeneralisasi, "
"menghapus bagian `_client_` atau` _server_` tertentu dari nama. Pengguna "
"peran ini harus memeriksa bahwa setiap penggantian yang mereka gunakan "
"memiliki nama variabel yang benar untuk peran gabungan yang baru."

msgid ""
"The galera_server role now includes the functionality from the galera_client "
"role, and can optionally install the client and server components. This is "
"controlled using two booleans, galera_install_server and "
"galera_install_client, both of which default to false."
msgstr ""
"Peran galera_server sekarang termasuk fungsionalitas dari peran "
"galera_client, dan secara opsional dapat menginstal komponen klien dan "
"server. Ini dikontrol menggunakan dua booleans, galera_install_server, dan "
"galera_install_client, yang keduanya default ke false."

msgid "The galera_server role now installs MariaDB server version 10.1."
msgstr "Peran galera_server sekarang menginstal server MariaDB versi 10.1."

msgid ""
"The galera_server role now supports the ability to configure whether apt/yum "
"tasks install the latest available package, or just ensure that the package "
"is present. The default action is to ensure that the latest package is "
"present. The action taken may be changed to only ensure that the package is "
"present by setting ``galera_server_package_state`` to ``present``."
msgstr ""
"Peran galera_server sekarang mendukung kemampuan untuk mengonfigurasi apakah "
"tugas apt/yum menginstal paket terbaru yang tersedia, atau hanya memastikan "
"bahwa paket tersebut ada. Tindakan default adalah untuk memastikan bahwa "
"paket terbaru hadir. Tindakan yang diambil dapat diubah hanya untuk "
"memastikan bahwa paket hadir dengan mengatur ``galera_server_package_state`` "
"ke ``present``."

msgid ""
"The git clone part of the repo build process now only happens when the "
"requirements change. A git reclone can be forced by using the boolean "
"variable ``repo_build_git_reclone``."
msgstr ""
"Bagian git clone dari proses repo build sekarang hanya terjadi ketika "
"persyaratan berubah. Sebuah git reclone dapat dipaksa dengan menggunakan "
"variabel boolean ``repo_build_git_reclone``."

msgid ""
"The git source for python2_lxc was used in the past as the package was not "
"available on pypi. Now that the package `has been published <https://pypi."
"python.org/pypi/lxc-python2>`_ the `py_from_git` role dependency has been "
"removed from the `lxc_hosts` playbook, the role has been removed from the "
"required roles list and the repo details have been removed from the "
"repo_packages files as none of these details are required any more."
msgstr ""
"Sumber git untuk python2_lxc digunakan di masa lalu karena paket tidak "
"tersedia di pypi. Sekarang paket `has been published <https://pypi.python."
"org/pypi/lxc-python2>`_   ketergantungan peran `py_from_git` telah dihapus "
"dari playbook` lxc_hosts`, peran tersebut telah dihapus dari daftar peran "
"yang diperlukan dan detail repo telah dihapus dari file repo_packages karena "
"tidak ada detail ini yang diperlukan lagi."

msgid ""
"The glance registry service for the v2 API is now disabled by default as it "
"is not required and is scheduled to be removed in the future. The service "
"can be enabled by setting ``glance_enable_v2_registry`` to ``True``. As the "
"glance v1 API is still enabled by default, and it requires the registry "
"service, the glance-registry service will still remain running and "
"operational as before. If the variable ``glance_enable_v1_api`` is set to "
"``False`` then both the v1 API and the registry service will be disabled and "
"removed."
msgstr ""
"Layanan sekilas registri untuk API v2 sekarang dinonaktifkan secara default "
"karena tidak diperlukan dan dijadwalkan untuk dihapus di masa depan. Layanan "
"ini dapat diaktifkan dengan mengatur ``glance_enable_v2_registry`` ke "
"``True``. Karena glance v1 API masih diaktifkan secara default, dan "
"memerlukan layanan registri, layanan glance-registry akan tetap berjalan dan "
"operasional seperti sebelumnya. Jika variabel ``glance_enable_v1_api`` "
"diatur ke ``False`` maka API v1 dan layanan registri akan dinonaktifkan dan "
"dihapus."

msgid ""
"The glance registry service is now disabled by default as it is not required "
"for the v2 API and is scheduled to be removed in the future. The service can "
"be enabled by setting ``glance_enable_v2_registry`` to ``True``."
msgstr ""
"Layanan glance registry sekarang dinonaktifkan secara default karena tidak "
"diperlukan untuk API v2 dan dijadwalkan untuk dihapus di masa depan. Layanan "
"ini dapat diaktifkan dengan mengatur ``glance_enable_v2_registry`` ke "
"``True``."

msgid ""
"The glance v1 API is now disabled by default as the API is scheduled to be "
"removed in Queens."
msgstr ""
"Glance v1 API sekarang dinonaktifkan secara default karena API dijadwalkan "
"akan dihapus di Queens."

msgid ""
"The glance v1 API is now removed upstream and the deployment code is now "
"removed from this glance ansible role. The variable ``glance_enable_v1_api`` "
"is removed."
msgstr ""
"Glance v1 API sekarang dihapus di hulu dan kode penempatan sekarang dihapus "
"dari peran glance ansible ini. Variabel ``glance_enable_v1_api`` dihapus."

msgid ""
"The global override ``cinder_nfs_client`` is replaced in favor of fully "
"supporting multi backends configuration via the cinder_backends stanza."
msgstr ""
"Override global ``cinder_nfs_client`` diganti demi konfigurasi multi-backend "
"yang sepenuhnya mendukung melalui stanza cinder_backends."

msgid ""
"The gnocchi ceph component has been moved out as a default component "
"required by the ceph_client role. It can now be optionally specified through "
"the use of the ``ceph_extra_components`` variable."
msgstr ""
"Komponen gnocchi ceph telah dipindahkan sebagai komponen default yang "
"diperlukan oleh peran ceph_client. Sekarang dapat ditentukan secara opsional "
"melalui penggunaan variabel ``ceph_extra_components``."

msgid ""
"The gnocchi_archive_policies and gnocchi_archive_policy_rules variables "
"never had full support in the role so were ineffective at the intended "
"purpose. The task references to them have been removed and the library to "
"perform gnocchi operations has also been removed. This eliminates the need "
"for the gnocchi client to be installed outside the virtual environment as "
"well."
msgstr ""
"Variabel gnocchi_archive_policies dan gnocchi_archive_policy_rules tidak "
"pernah memiliki dukungan penuh dalam peran sehingga tidak efektif pada "
"tujuan yang dimaksud. Referensi tugas kepada mereka telah dihapus dan "
"perpustakaan untuk melakukan operasi gnocchi juga telah dihapus. Ini "
"menghilangkan kebutuhan untuk klien gnocchi untuk diinstal di luar "
"lingkungan virtual juga."

msgid ""
"The haproxy daemon is now able to bind to any port on CentOS 7. The "
"``haproxy_connect_any`` SELinux boolean is now set to ``on``."
msgstr ""
"Daemon haproxy sekarang dapat mengikat ke port apa pun di CentOS 7. "
"``haproxy_connect_any`` SELinux boolean sekarang disetel ke ``on``."

msgid ""
"The haproxy-install.yml playbook will now be run as a part of setup-"
"infrastructure.yml."
msgstr ""
"Playbook haproxy-install.yml sekarang akan dijalankan sebagai bagian dari "
"setup-infrastructure.yml."

msgid ""
"The haproxy_server role always checks whether the latest package is "
"installed when executed. If a deployer wishes to change the check to only "
"validate the presence of the package, the option ``haproxy_package_state`` "
"should be set to ``present``."
msgstr ""
"Peran haproxy_server selalu memeriksa apakah paket terbaru diinstal ketika "
"dijalankan. Jika seorang deployer ingin mengubah tanda centang untuk hanya "
"memvalidasi keberadaan paket, opsi ``haproxy_package_state`` harus diatur ke "
"``present``."

msgid ""
"The haproxy_server role now supports the ability to configure whether apt/"
"yum tasks install the latest available package, or just ensure that the "
"package is present. The default action is to ensure that the latest package "
"is present. The action taken may be changed to only ensure that the package "
"is present by setting ``haproxy_package_state`` to ``present``."
msgstr ""
"Peran haproxy_server sekarang mendukung kemampuan untuk mengkonfigurasi "
"apakah tugas apt/yum menginstal paket terbaru yang tersedia, atau hanya "
"memastikan bahwa paket tersebut ada. Tindakan default adalah untuk "
"memastikan bahwa paket terbaru hadir. Tindakan yang diambil dapat diubah "
"hanya untuk memastikan bahwa paket hadir dengan mengatur "
"``haproxy_package_state`` ke ``present``."

msgid ""
"The horizon next generation instance management panels have been enabled by "
"default. This changes horizon to use the upstream defaults instead of the "
"legacy panels. `Documentation can be found here <http://docs.openstack.org/"
"developer/horizon/topics/settings.html#launch-instance-ng-enabled>`_."
msgstr ""
"Panel manajemen instance horizon generasi berikutnya telah diaktifkan secara "
"default. Ini mengubah horizon untuk menggunakan default upstream daripada "
"panel lawas (legacy)  `Documentation can be found here <http://docs."
"openstack.org/developer/horizon/topics/settings.html#launch-instance-ng-"
"enabled>`_."

msgid ""
"The in tree \"ansible.cfg\" file in the playbooks directory has been "
"removed. This file was making compatibility difficult for deployers who need "
"to change these values. Additionally this files very existance forced "
"Ansible to ignore any other config file in either a users home directory or "
"in the default \"/etc/ansible\" directory."
msgstr ""
"File in tree \"ansible.cfg\" di direktori playbooks telah dihapus. File ini "
"menyulitkan kompatibilitas untuk para deployer yang perlu mengubah nilai "
"ini. Selain itu, file ini sangat dipaksa keberadaan Ansible untuk "
"mengabaikan file konfigurasi lain di direktori home user atau di direktori "
"\"/etc/ansible\" default."

msgid ""
"The installation of Erlang and is now optimized for CentOS. Erlang 19.x is "
"now installed via a single package that is maintained by RabbitMQ developers "
"and it provides the minimal features required for RabbitMQ to function. It "
"also includes HiPE support for increased performance."
msgstr ""
"Instalasi Erlang dan sekarang dioptimalkan untuk CentOS. Erlang 19.x "
"sekarang diinstal melalui satu paket yang dikelola oleh pengembang RabbitMQ "
"dan menyediakan fitur minimal yang diperlukan agar RabbitMQ berfungsi. Ini "
"juga termasuk dukungan HiPE untuk peningkatan kinerja."

msgid ""
"The installation of ``chrony`` is still enabled by default, but it is now "
"controlled by the ``security_enable_chrony`` variable."
msgstr ""
"Instalasi ``chrony`` masih diaktifkan secara default, tetapi sekarang "
"dikendalikan oleh variabel ``security_enable_chrony``."

msgid ""
"The internal variable ``python_ceph_package`` has been renamed to "
"``python_ceph_packages`` and is now a list instead of a string. If you are "
"using gnocchi with ceph and are using this internal variable in your "
"``ceph_extra_components`` overrides, please update it to "
"``python_ceph_packages``."
msgstr ""
"Variabel internal ``python_ceph_package`` telah diubah namanya menjadi "
"``python_ceph_packages`` dan sekarang menjadi daftar bukan lagi string. Jika "
"Anda menggunakan gnocchi dengan ceph dan menggunakan variabel internal ini "
"dalam override ``ceph_extra_components`` Anda, update ke "
"``python_ceph_packages``."

msgid ""
"The inventory generation code has been switched to use standard Python "
"packaging tools. For most, this should not be a visible change. However, "
"running the dynamic inventory script on a local development environment "
"should now be called via ``python dynamic_inventory.py``."
msgstr ""
"Kode pembuatan inventory telah diubah untuk menggunakan alat packaging "
"Python standar. Bagi kebanyakan orang, ini seharusnya bukan perubahan yang "
"terlihat. Namun, menjalankan skrip inventaris dinamis pada lingkungan "
"pengembangan lokal sekarang harus dipanggil melalui ``python "
"dynamic_inventory.py``."

msgid ""
"The inventory script will now dynamically populate the ``lxc_hosts`` group "
"dynamically based on which machines have container affinities defined. This "
"group is not allowed in user-defined configuration."
msgstr ""
"Skrip inventory sekarang akan secara dinamis mengisi grup ``lxc_hosts`` "
"secara dinamis berdasarkan pada mesin yang memiliki kesamaan (affinity) "
"kontainer yang ditentukan. Grup ini tidak diizinkan dalam konfigurasi yang "
"ditentukan pengguna."

msgid ""
"The ironic conductor service has been consolidated into the "
"``ironic_api_container``. The previously implemented "
"``ironic_conductor_container`` can be removed."
msgstr ""
"Layanan konduktor ironic telah dikonsolidasikan ke dalam "
"``ironic_api_container``. ``ironic_conductor_container`` yang sebelumnya "
"diterapkan dapat dihapus."

msgid ""
"The journald-remote is disabled from execution inside setup-infrastructure "
"until https://github.com/systemd/systemd/issues/2376 has been incorporated "
"in current systemd packages. The playbook can be enabled by setting "
"``journald_remote_enabled`` to ``True``"
msgstr ""
"Remote-journald dinonaktifkan dari eksekusi di dalam setup-infrastructure "
"hingga https://github.com/systemd/systemd/issues/2376 telah dimasukkan dalam "
"paket systemd saat ini. Playbook dapat diaktifkan dengan mengatur "
"``journald_remote_enabled`` ke ``True``"

msgid ""
"The journald-remote playbook is disabled from execution inside setup-"
"infrastructure until setting ``journald_remote_enabled`` is set to ``True`` "
"due to https://github.com/systemd/systemd/issues/2376"
msgstr ""
"Playbook journald-remote dinonaktifkan dari eksekusi di dalam setup-"
"infrastructure sampai pengaturan ``journald_remote_enabled`` diatur ke "
"``True`` karena https://github.com/systemd/systemd/issues/2376"

msgid ""
"The keepalived role was updated, and now includes an optional way to "
"configure vrrp scripts timeouts. See also: `VRRP timeout PR on keepalived "
"role <https://github.com/evrardjp/ansible-keepalived/"
"commit/0b2d13a13c1a03e14ac6f67286811ca1bf1928ac>`_."
msgstr ""
"Peran keepalived diperbarui, dan sekarang termasuk cara opsional untuk "
"mengkonfigurasi batas waktu skrip vrrp. Lihat juga: `VRRP timeout PR on "
"keepalived role <https://github.com/evrardjp/ansible-keepalived/"
"commit/0b2d13a13c1a03e14ac6f67286811ca1bf1928ac>`_."

msgid ""
"The key **is_ssh_address** has been removed from the `openstack_user_config."
"yml` and the dynamic inventory. This key was responsible mapping an address "
"to the container which was used for SSH connectivity. Because we've created "
"the SSH connectivity plugin, which allows us the ability to connect to "
"remote containers without SSH, this option is no longer useful. To keep the "
"`openstack_user_config.yml` clean deployers can remove the option however "
"moving forward it no longer has any effect."
msgstr ""
"Kunci **is_ssh_address** telah dihapus dari `openstack_user_config.yml` dan "
"dynamic inventory. Kunci ini bertanggung jawab memetakan alamat ke kontainer "
"yang digunakan untuk konektivitas SSH. Karena kami telah membuat plugin "
"konektivitas SSH, yang memungkinkan kami kemampuan untuk terhubung ke "
"kontainer jarak jauh tanpa SSH, opsi ini tidak lagi berguna. Untuk menjaga, "
"clean deployers `openstack_user_config.yml` dapat menghapus opsi namun "
"bergerak maju tidak lagi memiliki efek."

msgid ""
"The keystone endpoints for instances spawned by magnum will now be provided "
"with the public endpoints by default. Previously this was set to use "
"internal endpoints."
msgstr ""
"Endpoint keystone untuk instance yang dihasilkan oleh magnum sekarang akan "
"disediakan dengan endpoint publik secara default. Sebelumnya ini diatur "
"untuk menggunakan endpoint internal."

msgid ""
"The keystone endpoints now have versionless URLs. Any existing endpoints "
"will be updated."
msgstr ""
"Endpoint keyston sekarang memiliki URL tanpa versi. Setiap endpoint yang ada "
"akan diperbarui."

msgid ""
"The kubernetes version deployed with ocata is now constrained to version "
"2.0.0, matching the same version as deployed in all pike releases."
msgstr ""
"Versi kubernet yang digunakan dengan ocata sekarang dibatasi untuk versi "
"2.0.0, cocok dengan versi yang sama seperti yang digunakan di semua rilis "
"pike."

msgid ""
"The latest stable release of Ceph, Jewel, is now used as the default client "
"version since Hammer was scheduled for EOL in November 2016."
msgstr ""
"Rilis stabil terbaru dari Ceph, Jewel, sekarang digunakan sebagai versi "
"klien default sejak Hammer dijadwalkan untuk EOL pada November 2016."

msgid ""
"The latest version of the RHEL 7 STIG requires that a standard login banner "
"is presented to users when they log into the system (V-71863). The security "
"role now deploys a login banner that is used for console and ssh sessions."
msgstr ""
"Versi terbaru dari RHEL 7 STIG mensyaratkan bahwa banner login standar "
"(standard login banner) disajikan kepada pengguna ketika mereka masuk ke "
"sistem (V-71863). Peran keamanan sekarang menyebarkan login banner yang "
"digunakan untuk sesi konsol dan ssh."

msgid ""
"The liberty release notes list the configuration options scrubber_datadir, "
"cleanup_scrubber and cleanup_scrubber_time as being deprecated. Accordingly, "
"they have been removed from the OSA glance role."
msgstr ""
"Catatan rilis liberty mencantumkan opsi konfigurasi scrubber_datadir, "
"cleanup_scrubber dan cleanup_scrubber_time sudah tidak digunakan lagi. "
"Dengan demikian, mereka telah dihapus dari peran glance OSA."

msgid ""
"The limits.conf file for galera servers will now be deployed under ``/etc/"
"security/limits.d/99-limits.conf``. This is being done to ensure our changes "
"do not clobber existing settings within the system's default ``/etc/security/"
"limits.conf`` file when the file is templated."
msgstr ""
"File limit.conf untuk server galera sekarang akan digunakan di bawah ``/etc/"
"security/limits.d/99-limits.conf``.  Ini sedang dilakukan untuk memastikan "
"perubahan kami tidak merusak pengaturan yang ada dalam file ``/etc/security/"
"limits.conf`` default sistem ketika file tersebut templated."

msgid ""
"The list of enabled filters for the Cinder scheduler, "
"`scheduler_default_filters` in `cinder.conf`, could previously be defined "
"only via an entry in ``cinder_cinder_conf_overrides``. You now have the "
"option to instead define a list variable, "
"``cinder_scheduler_default_filters``, that defines the enabled filters. This "
"is helpful if you either want to disable one of the filters enabled by "
"default (at the time of writing, these are `AvailabilityZoneFilter`, "
"`CapacityFilter`, and `CapabilitiesFilter`), or if conversely you want to "
"add a filter that is normally not enabled, such as `DifferentBackendFilter` "
"or `InstanceLocalityFilter`."
msgstr ""
"Daftar filter yang diaktifkan untuk penjadwal Cinder, "
"`scheduler_default_filters` pada `cinder.conf`, sebelumnya hanya dapat "
"didefinisikan melalui entri di ``cinder_cinder_conf_overonfes``. Anda "
"sekarang memiliki opsi untuk mendefinisikan variabel daftar, "
"``cinder_scheduler_default_filters``, yang menentukan filter yang "
"diaktifkan. Ini berguna jika Anda ingin menonaktifkan salah satu filter yang "
"diaktifkan secara default (pada saat penulisan, ini adalah "
"`AvailabilityZoneFilter`,` CapacityFilter`, dan `CapabilitiesFilter`), atau "
"jika sebaliknya Anda ingin menambahkan filter yang biasanya tidak "
"diaktifkan, seperti `DifferentBackendFilter` atau` InstanceLocalityFilter`."

msgid ""
"The location of the ``/etc/openstack-release`` file placement can now be "
"changed. Set the variable ``openstack_distrib_file_path`` to place it in a "
"different path."
msgstr ""
"Lokasi penempatan file ``/etc/openstack-release`` sekarang dapat diubah. "
"Atur variabel ``openstack_distrib_file_path`` untuk menempatkannya di jalur "
"yang berbeda."

msgid ""
"The log path, ``/var/log/aodh`` is no longer used to capture service logs. "
"All logging for the aodh service will now be sent directly to the systemd "
"journal."
msgstr ""
"Path log, ``/var/log/aodh``  tidak lagi digunakan untuk mengambil log "
"layanan. Semua logging untuk layanan aodh sekarang akan dikirim langsung ke "
"jurnal systemd."

msgid ""
"The log path, ``/var/log/barbican`` is no longer used to capture service "
"logs. All logging for the barbican service will now be sent directly to the "
"systemd journal."
msgstr ""
"Path log, ``/var/log/barbican`` tidak lagi digunakan untuk mengambil log "
"layanan. Semua logging untuk layanan barbican sekarang akan dikirim langsung "
"ke jurnal systemd."

msgid ""
"The log path, ``/var/log/blazar`` is no longer used to capture service logs. "
"All logging for the blazar service will now be sent directly to the systemd "
"journal."
msgstr ""
"Path log, ``/var/log/blazar``  tidak lagi digunakan untuk mengambil log "
"layanan. Semua logging untuk layanan blazar sekarang akan dikirim langsung "
"ke jurnal systemd."

msgid ""
"The log path, ``/var/log/ceilometer`` is no longer used to capture service "
"logs. All logging for the ceilometer service will now be sent directly to "
"the systemd journal."
msgstr ""
"Path log, ``/var/log/ceilometer`` tidak lagi digunakan untuk mengambil log "
"layanan. Semua logging untuk layanan ceilometer sekarang akan dikirim "
"langsung ke jurnal systemd."

msgid ""
"The log path, ``/var/log/cinder`` is no longer used to capture service logs. "
"All logging for the cinder service will now be sent directly to the systemd "
"journal."
msgstr ""
"Path log, ``/var/log/cinder`` tidak lagi digunakan untuk mengambil log "
"layanan. Semua pencatatan untuk layanan cinder sekarang akan dikirim "
"langsung ke jurnal systemd."

msgid ""
"The log path, ``/var/log/cloudkitty`` is no longer used to capture service "
"logs. All logging for the cloudkitty service will now be sent directly to "
"the systemd journal."
msgstr ""
"Path log, ``/var/log/cloudkitty`` tidak lagi digunakan untuk mengambil log "
"layanan. Semua logging untuk layanan cloudkitty sekarang akan dikirim "
"langsung ke jurnal systemd."

msgid ""
"The log path, ``/var/log/congress`` is no longer used to capture service "
"logs. All logging for the congress service will now be sent directly to the "
"systemd journal."
msgstr ""
"Path log, ``/var/log/congress``` tidak lagi digunakan untuk mengambil log "
"layanan. Semua logging untuk layanan kongres sekarang akan dikirim langsung "
"ke jurnal systemd."

msgid ""
"The log path, ``/var/log/designate`` is no longer used to capture service "
"logs. All logging for the designate service will now be sent directly to the "
"systemd journal."
msgstr ""
"Path log, ``/var/log/designate`` tidak lagi digunakan untuk mengambil log "
"layanan. Semua logging untuk layanan yang ditunjuk sekarang akan dikirim "
"langsung ke jurnal systemd."

msgid ""
"The log path, ``/var/log/keystone`` is no longer used to capture service "
"logs. All logging for the Keystone service will now be sent directly to the "
"systemd journal."
msgstr ""
"Path log, ``/var/log/keystone`` tidak lagi digunakan untuk mengambil log "
"layanan. Semua logging untuk layanan Keystone sekarang akan dikirim langsung "
"ke jurnal systemd."

msgid ""
"The lxc_hosts role always checks whether the latest package is installed "
"when executed. If a deployer wishes to change the check to only validate the "
"presence of the package, the option ``lxc_hosts_package_state`` should be "
"set to ``present``."
msgstr ""
"Peran lxc_hosts selalu memeriksa apakah paket terbaru diinstal ketika "
"dijalankan. Jika seorang deployer ingin mengubah tanda centang untuk hanya "
"memvalidasi keberadaan paket, opsi ``lxc_hosts_package_state`` harus diatur "
"ke ``present``."

msgid ""
"The lxc_hosts role can now make use of a primary and secondary gpg keyserver "
"for gpg validation of the downloaded cache. Setting the servers to use can "
"be done using the ``lxc_image_cache_primary_keyserver`` and "
"``lxc_image_cache_secondary_keyserver`` variables."
msgstr ""
"Peran lxc_hosts sekarang dapat menggunakan server gpg primer dan sekunder "
"untuk validasi gpg dari cache yang diunduh. Pengaturan server untuk "
"digunakan dapat dilakukan dengan menggunakan variabel "
"``lxc_image_cache_primary_keyserver`` dan "
"``lxc_image_cache_secondary_keyserver``."

msgid ""
"The lxc_hosts role now supports the ability to configure whether apt/yum "
"tasks install the latest available package, or just ensure that the package "
"is present. The default action is to ensure that the latest package is "
"present. The action taken may be changed to only ensure that the package is "
"present by setting ``lxc_hosts_package_state`` to ``present``."
msgstr ""
"Peran lxc_hosts sekarang mendukung kemampuan untuk mengonfigurasi apakah "
"tugas apt/yum menginstal paket terbaru yang tersedia, atau hanya memastikan "
"bahwa paket tersebut ada. Aksi default adalah untuk memastikan bahwa paket "
"terbaru hadir. Aksi yang diambil dapat diubah hanya untuk memastikan bahwa "
"paket hadir dengan mengatur ``lxc_hosts_package_state`` ke ``present``."

msgid ""
"The magnum client interaction will now make use of the public endpoints by "
"default. Previously this was set to use internal endpoints."
msgstr ""
"Interaksi klien magnum sekarang akan menggunakan endpoint publik secara "
"default. Sebelumnya ini diatur untuk menggunakan endpoint internal."

msgid ""
"The masakari dashboard is available in Horizon. Deployers can enable the "
"panel by setting the following Ansible variable:"
msgstr ""
"Dasbor masakari tersedia di Horizon. Deployer dapat mengaktifkan panel "
"dengan mengatur variabel Ansible berikut:"

msgid ""
"The max connections setting for Galera is now determined automatically by "
"taking the number of vCPUs available and multiplying it by 100. Deployers "
"may override this default via the ``galera_max_connections`` variable."
msgstr ""
"Pengaturan koneksi maks untuk Galera sekarang ditentukan secara otomatis "
"dengan mengambil jumlah vCPU yang tersedia dan mengalikannya dengan 100. "
"Penyedia dapat menimpa default ini melalui variabel "
"``galera_max_connections``."

msgid ""
"The maximum amount of time to wait until forcibly failing the LXC cache "
"preparation process is now configurable using the ``lxc_cache_prep_timeout`` "
"variable. The value is specified in seconds, with the default being 20 "
"minutes."
msgstr ""
"Jumlah maksimum waktu untuk menunggu hingga gagal secara paksa dalam proses "
"persiapan cache LXC sekarang dapat dikonfigurasi menggunakan variabel "
"``lxc_cache_prep_timeout``. Nilai ditentukan dalam detik, dengan default "
"adalah 20 menit."

msgid ""
"The maximum erlang process limit for RabbitMQ has been set to 1048576 in "
"order to prevent virtual machine lockups which are caused when this limit "
"has been reached."
msgstr ""
"Batas proses erlang maksimum untuk RabbitMQ telah ditetapkan ke 1048576 "
"untuk mencegah penguncian mesin virtual yang disebabkan ketika batas ini "
"telah tercapai."

msgid ""
"The memcached log is removed from /var/log/memcached.log and is now stored "
"in the /var/log/memcached folder."
msgstr ""
"Log memcached dihapus dari /var/log/memcached.log dan sekarang disimpan di "
"folder /var/log/memcached"

msgid ""
"The memcached_server role always checks whether the latest package is "
"installed when executed. If a deployer wishes to change the check to only "
"validate the presence of the package, the option ``memcached_package_state`` "
"should be set to ``present``."
msgstr ""
"Peran memcached_server selalu memeriksa apakah paket terbaru diinstal ketika "
"dijalankan. Jika seorang penggelar ingin mengubah tanda centang untuk hanya "
"memvalidasi keberadaan paket, opsi ``memcached_package_state`` harus diatur "
"ke  ``present``."

msgid ""
"The memcached_server role now supports the ability to configure whether apt/"
"yum tasks install the latest available package, or just ensure that the "
"package is present. The default action is to ensure that the latest package "
"is present. The action taken may be changed to only ensure that the package "
"is present by setting ``memcached_package_state`` to ``present``."
msgstr ""
"Peran memcached_server sekarang mendukung kemampuan untuk mengkonfigurasi "
"apakah tugas apt/yum menginstal paket terbaru yang tersedia, atau hanya "
"memastikan bahwa paket tersebut ada. Tindakan default adalah untuk "
"memastikan bahwa paket terbaru hadir. Tindakan yang diambil dapat diubah "
"hanya untuk memastikan bahwa paket itu hadir dengan mengatur "
"``memcached_package_state`` ke ``present``."

msgid ""
"The murano dashboard is available in Horizon. Deployers can enable the panel "
"by setting the following Ansible variable:"
msgstr ""
"Dasbor murano tersedia di Horizon. Deployer dapat mengaktifkan panel dengan "
"mengatur variabel Ansible berikut:"

msgid ""
"The new LBaaS v2 dashboard is available in Horizon. Deployers can enable the "
"panel by setting the following Ansible variable:"
msgstr ""
"Dasbor LBaaS v2 baru tersedia di Horizon. Deployer dapat mengaktifkan panel "
"dengan mengatur variabel Ansible berikut:"

msgid ""
"The new host group ``neutron_openvswitch_agent`` has been added to the ``env."
"d/neutron.yml`` and ``env.d/nova.yml`` environment configuration files in "
"order to support the implementation of Open vSwitch. Deployers must ensure "
"that their environment configuration files are updated to include the above "
"group name. Please see the example implementations in `env.d/neutron.yml "
"<https://github.com/openstack/openstack-ansible/blob/stable/newton/etc/"
"openstack_deploy/env.d/neutron.yml>`_ and `env.d/nova.yml <https://github."
"com/openstack/openstack-ansible/blob/stable/newton/etc/openstack_deploy/env."
"d/nova.yml>`_."
msgstr ""
"Grup host baru ``neutron_openvswitch_agent`` telah ditambahkan ke file "
"konfigurasi lingkungan ``env.d/neutron.yml`` dan  ``env.d/nova.yml`` dalam "
"rangka mendukung implementasi Open vSwitch. Deployer harus memastikan bahwa "
"file konfigurasi lingkungan mereka diperbarui untuk menyertakan nama grup di "
"atas. Silakan lihat contoh implementasi di `env.d/neutron.yml <https://"
"github.com/openstack/openstack-ansible/blob/stable/newton/etc/"
"openstack_deploy/env.d/neutron.yml>`_ dan `env.d/nova.yml <https://github."
"com/openstack/openstack-ansible/blob/stable/newton/etc/openstack_deploy/env."
"d/nova.yml>`_."

msgid ""
"The new option `haproxy_backend_arguments` can be utilized to add arbitrary "
"options to a HAProxy backend like tcp-check or http-check."
msgstr ""
"Opsi baru `haproxy_backend_arguments` dapat digunakan untuk menambahkan opsi "
"arbitrary(acak) ke backend HAProxy seperti tcp-check atau http-check."

msgid ""
"The new provider network attribute ``sriov_host_interfaces`` is added to "
"support SR-IOV network mappings inside Neutron. The provider_network adds "
"new items network_sriov_mappings and network_sriov_mappings_list to the "
"provider_networks dictionary. Multiple interfaces can be defined by comma "
"separation."
msgstr ""
"Atribut jaringan penyedia baru ``sriov_host_interfaces`` ditambahkan untuk "
"mendukung pemetaan jaringan SR-IOV di dalam Neutron. Provider_network "
"menambahkan item baru network_sriov_mappings dan network_sriov_mappings_list "
"ke kamus (dictionary)  provider_networks. Beberapa antarmuka dapat "
"didefinisikan dengan pemisahan koma."

msgid ""
"The new variable ``tempest_workspace`` has been introduced to set the "
"location of the tempest workspace."
msgstr ""
"Variabel baru ``tempest_workspace`` telah diperkenalkan untuk mengatur "
"lokasi ruang kerja tempest."

msgid ""
"The nova SSH public key distribution has been made a lot faster especially "
"when deploying against very large clusters. To support larger clusters the "
"role has moved away from the \"authorized_key\" module and is now generating "
"a script to insert keys that may be missing from the authorized keys file. "
"The script is saved on all nova compute nodes and can be found at ``/usr/"
"local/bin/openstack-nova-key.sh``. If ever there is a need to reinsert keys "
"or fix issues on a given compute node the script can be executed at any time "
"without directly running the ansible playbooks or roles."
msgstr ""
"Distribusi kunci publik SSH nova telah dibuat jauh lebih cepat terutama "
"ketika digunakan terhadap kluster yang sangat besar. Untuk mendukung kluster "
"yang lebih besar, peran telah berpindah dari modul \"authorized_key\" dan "
"sekarang membuat skrip untuk memasukkan kunci yang mungkin hilang dari file "
"kunci yang diotorisasi. Script disimpan pada semua node komputasi nova dan "
"dapat ditemukan d i``/usr/local/bin/openstack-nova-key.sh``. Jika pernah ada "
"kebutuhan untuk memasukkan kembali kunci atau memperbaiki masalah pada node "
"komputasi yang diberikan, skrip dapat dieksekusi kapan saja tanpa secara "
"langsung menjalankan playbook atau peran ansible."

msgid ""
"The nova admin endpoint is now correctly registered as ``/v2.1/"
"%(tenant_id)s`` instead of ``/v2/%(tenant_id)s``."
msgstr ""
"The nova admin endpoint is now correctly registered as ``/v2.1/"
"%(tenant_id)s`` sebagai ganti ``/v2/%(tenant_id)s``."

msgid ""
"The nova configuration is updated to always specify an LXD storage pool name "
"when 'nova_virt_type' is 'lxd'. The variable 'lxd_storage_pool' is defaulted "
"to 'default', the LXD default storage pool name. A new variable "
"'lxd_init_storage_pool' is introduced which specifies the underlying storage "
"pool name. 'lxd_init_storage_pool' is used by lxd init when setting up the "
"storage pool. If not provided, lxd init will not use this parameter at all. "
"Please see the lxd man page for further information about the storage pool "
"parameter."
msgstr ""
"Konfigurasi nova diperbarui untuk selalu menentukan nama LXD storage pool "
"ketika 'nova_virt_type' adalah 'lxd'. Variabel 'lxd_storage_pool' default ke "
"'default', nama LXD storage pool default. Variabel baru "
"'lxd_init_storage_pool' diperkenalkan yang merincis (specify) nama storage "
"pool yang mendasarinya. 'lxd_init_storage_pool' digunakan oleh lxd init saat "
"mengatur storage pool. Jika tidak disediakan, lxd init tidak akan "
"menggunakan parameter ini sama sekali. Silakan lihat halaman manual lxd "
"untuk informasi lebih lanjut tentang parameter kumpulan penyimpanan (storage "
"pool)."

msgid ""
"The nova-cert service has been deprecated, is marked for removal in the "
"Ocata release, and will no longer be deployed by the os_nova role."
msgstr ""
"Layanan nova-cert telah ditinggalkan, ditandai untuk dihapus dalam rilis "
"Ocata, dan tidak akan lagi digunakan oleh peran os_nova."

msgid ""
"The nova-lxd driver is no longer supported upstream, and the git repo for "
"it's source code has been retired on the master branch. All code for "
"deploying or testing nova-lxd has been removed from the os_nova ansible "
"role. The following variables have been removed:"
msgstr ""
"Driver nova-lxd tidak lagi didukung hulu, dan repo git untuk kode sumbernya "
"telah dipensiunkan pada cabang master. Semua kode untuk menggunakan atau "
"menguji nova-lxd telah dihapus dari  os_nova ansible role. Variabel berikut "
"telah dihapus:"

msgid ""
"The nova_placement database which was implemented in the ocata release of "
"OpenStack-Ansible was never actually used for anything due to reverts in the "
"upstream code. The database should be empty and can be deleted. With this "
"the following variables also no longer have any function and have been "
"removed."
msgstr ""
"Database nova_placement yang diimplementasikan dalam rilis ocata dari "
"OpenStack-Ansible tidak pernah benar digunakan untuk apa pun karena kembali "
"pada kode hulu. Database harus kosong dan dapat dihapus. Dengan ini, "
"variabel berikut juga tidak lagi memiliki fungsi dan telah dihapus."

msgid ""
"The number of erlang asynchronous threads used by RabbitMQ have been "
"increased from the default of 32 to 128 in order to speed up message "
"processing."
msgstr ""
"Jumlah thread asynchronous erlang yang digunakan oleh RabbitMQ telah "
"ditingkatkan dari default 32 menjadi 128 untuk mempercepat pemrosesan pesan."

msgid ""
"The number of inotify watch instances available is limited system wide via a "
"sysctl setting. It is possible for certain processes, such as pypi-server, "
"or elasticsearch from the ops repo to consume a large number of inotify "
"watches. If the system wide maximum is reached then any process on the host "
"or in any container on the host will be unable to create a new inotify "
"watch. Systemd uses inotify watches, and if there are none available it is "
"unable to restart services. The processes which synchronise the repo server "
"contents between infra nodes also relies on inotify watches. If the repo "
"servers fail to synchronise, or services fail to restart when expected check "
"the the inotify watch limit which is defined in the sysctl value fs.inotify."
"max_user_watches. Patches have merged to increase these limits, but for "
"existing environments or those which have not upgraded to a recent enough "
"point release may have to apply an increased limit manually."
msgstr ""
"Jumlah inotify watch instances yang tersedia terbatas pada seluruh sistem "
"melalui pengaturan sysctl. Dimungkinkan untuk proses tertentu, seperti pypi-"
"server, atau elasticsearch dari ops repo untuk mengkonsumsi sejumlah besar "
"inotify watch. Jika lebar sistem maksimum tercapai maka proses apa pun pada "
"host atau dalam kontainer apa pun pada host tidak akan dapat membuat inotify "
"watch baru. Systemd menggunakan inotify watch, dan jika tidak ada yang "
"tersedia, ia tidak dapat memulai kembali layanan. Proses yang menyinkronkan "
"konten server repo antara infra nodes juga bergantung pada inotify watch. "
"Jika server repo gagal menyinkronkan, atau layanan gagal untuk me-restart "
"ketika diharapkan periksa batas inotify watch yang didefinisikan dalam nilai "
"sysctl fs.inotify.max_user_watches. Patch telah bergabung untuk meningkatkan "
"batas ini, tetapi untuk lingkungan yang ada atau yang belum ditingkatkan ke "
"point release yang cukup baru mungkin harus menerapkan batas yang "
"ditingkatkan secara manual."

msgid ""
"The number of worker threads for neutron will now be capped at 16 unless a "
"specific value is specified. Previously, the calculated number of workers "
"could get too high on systems with a large number of processors.  This was "
"particularly evident on POWER systems."
msgstr ""
"Jumlah worker thread untuk neutron sekarang akan ditutup pada 16 kecuali "
"nilai tertentu ditentukan. Sebelumnya, jumlah worker yang dihitung bisa "
"menjadi terlalu tinggi pada sistem dengan sejumlah besar prosesor. Ini "
"sangat jelas pada sistem POWER."

msgid ""
"The old class path names used within the ``neutron_plugin_base`` have been "
"deprecated in favor of the friendly names. Support for the use of the class "
"path plugins will be removed in the OpenStack Newton cycle."
msgstr ""
"Nama path kelas (class path) lama yang digunakan dalam "
"``neutron_plugin_base`` telah ditinggalkan, lebih menyukai nama yang "
"bersahabat. Dukungan untuk penggunaan plugin path kelas akan dihapus dalam "
"siklus OpenStack Newton."

msgid ""
"The openrc role will no longer be executed on all OpenStack service "
"containers/hosts. Instead a single host is designated through the use of the "
"``openstack_service_setup_host`` variable. The default is ``localhost`` (the "
"deployment host). Deployers can opt to change this to the utility container "
"by implementing the following override in ``user_variables.yml``."
msgstr ""
"Peran openrc tidak lagi dijalankan pada semua kontainer/host layanan "
"OpenStack. Sebagai gantinya satu host ditunjuk melalui penggunaan variabel "
"``openstack_service_setup_host``. Defaultnya adalah ``localhost`` (host "
"penyebaran). Deployer dapat memilih untuk mengubahnya ke kontainer utilitas "
"dengan mengimplementasikan penggantian berikut di ``user_variables.yml``."

msgid ""
"The openstack service uri protocol variables were not being used to set the "
"Trove specific uris. This resulted in 'http' always being used for the "
"public, admin and internal uris even when 'https' was intended."
msgstr ""
"Variabel protokol layanan uri openstack tidak digunakan untuk mengatur uris "
"spesifik Trove. Ini mengakibatkan 'http' selalu digunakan untuk publik, "
"admin dan uris internal bahkan ketika 'https' dimaksudkan."

msgid ""
"The openstack-ansible-memcached_server role includes a new override, "
"``memcached_connections`` which is automatically calculated from the number "
"of memcached connection limit plus additional 1k to configure the OS nofile "
"limit. Without proper nofile limit configuration, memcached will crash in "
"order to support higher parallel connection TCP/Memcache counts."
msgstr ""
"Peran openstack-ansible-memcached_server termasuk override baru, "
"``memcached_connections`` yang secara otomatis dihitung dari jumlah batas "
"koneksi memcached ditambah 1k tambahan untuk mengkonfigurasi batas nofile "
"OS. Tanpa konfigurasi batas nofile yang tepat, memcached akan macet untuk "
"mendukung jumlah TCP/Memcache koneksi paralel yang lebih tinggi."

msgid ""
"The openstack-ansible-memcached_server role includes a new override,"
"`memcached_connections` which is automatically calculated from the number of "
"memcached connection limit plus additional 1k to configure the OS nofile "
"limit. Without proper nofile limit configuration, memcached will crash in "
"order to support higher parallel connection TCP/Memcache counts."
msgstr ""
"Peran openstack-ansible-memcached_server mencakup override baru, "
"`memcached_connections` yang secara otomatis dihitung dari jumlah batas "
"koneksi memcached ditambah 1k tambahan untuk mengkonfigurasi batas nofile "
"OS. Tanpa konfigurasi batas nofile yang tepat, memcached akan macet untuk "
"mendukung jumlah TCP/Memcache koneksi paralel yang lebih tinggi."

msgid ""
"The openstack-ansible-security role is now configured to apply the security "
"configurations from the Red Hat Enterprise Linux 7 STIG to OpenStack-Ansible "
"deployments."
msgstr ""
"Peran openstack-ansible-security sekarang dikonfigurasi untuk menerapkan "
"konfigurasi keamanan dari Red Hat Enterprise Linux 7 STIG ke penyebaran "
"OpenStack-Ansible."

msgid ""
"The openstack-ansible-security role is now retired and the ansible-hardening "
"role replaces it. The ansible-hardening role provides the same functionality "
"and will be the maintained hardening role going forward."
msgstr ""
"Peran openstack-ansible-security sekarang sudah pensiun dan peran ansible-"
"hardening menggantikannya. Peran ansible-hardening menyediakan fungsi yang "
"sama dan akan menjadi peran pengerasan (hardening) yang dipertahankan di "
"masa mendatang."

msgid ""
"The openstack_hosts role always checks whether the latest package is "
"installed when executed. If a deployer wishes to change the check to only "
"validate the presence of the package, the option "
"``openstack_hosts_package_state`` should be set to ``present``."
msgstr ""
"Peran openstack_hosts selalu memeriksa apakah paket terbaru diinstal ketika "
"dijalankan. Jika seorang deployer ingin mengubah tanda centang untuk hanya "
"memvalidasi keberadaan paket, opsi ``openstack_hosts_package_state`` harus "
"diatur ke ``present``."

msgid ""
"The openstack_hosts role now supports the ability to configure whether apt/"
"yum tasks install the latest available package, or just ensure that the "
"package is present. The default action is to ensure that the latest package "
"is present. The action taken may be changed to only ensure that the package "
"is present by setting ``openstack_hosts_package_state`` to ``present``."
msgstr ""
"Peran openstack_hosts sekarang mendukung kemampuan untuk mengonfigurasi "
"apakah tugas apt/yum menginstal paket terbaru yang tersedia, atau hanya "
"memastikan bahwa paket tersebut ada. Tindakan default adalah untuk "
"memastikan bahwa paket terbaru hadir. Tindakan yang diambil dapat diubah "
"hanya untuk memastikan bahwa paket hadir dengan mengatur "
"``openstack_hosts_package_state`` ke ``present``."

msgid ""
"The option ``openstack_domain`` has been added to the **openstack_hosts** "
"role. This option is used to setup proper hostname entries for all hosts "
"within a given OpenStack deployment."
msgstr ""
"Opsi ``openstack_domain`` telah ditambahkan ke peran **openstack_hosts** . "
"Opsi ini digunakan untuk mengatur entri nama host yang tepat untuk semua "
"host dalam penerapan OpenStack yang diberikan."

msgid ""
"The option ``rabbitmq_erlang_version_spec`` has been added allowing "
"deployers to set the version of erlang used on a given installation."
msgstr ""
"Opsi ``rabbitmq_erlang_version_spec`` telah ditambahkan yang memungkinkan "
"deployer untuk mengatur versi erlang yang digunakan pada instalasi yang "
"diberikan."

msgid ""
"The option ``repo_venv_default_pip_packages`` has been added which will "
"allow deployers to insert any packages into a service venv as needed. The "
"option expects a list of strings which are valid python package names as "
"found on PYPI."
msgstr ""
"Opsi ``repo_venv_default_pip_packages`` telah ditambahkan yang akan "
"memungkinkan para deployer untuk memasukkan paket apa pun ke dalam sebuah "
"service venv sesuai kebutuhan. Opsi mengharapkan daftar string yang "
"merupakan nama paket python yang valid seperti yang ditemukan di PYPI."

msgid ""
"The option `rabbitmq_disable_non_tls_listeners` has been removed in favor of "
"setting the bind address and port configuration directly using a new option "
"`rabbitmq_port_bindings`. This new option is a hash allowing for multiple "
"bind addresses and port configurations."
msgstr ""
"Opsi `rabbitmq_disable_non_tls_listeners` telah dihapus demi pengaturan "
"alamat bind dan konfigurasi port secara langsung menggunakan opsi baru "
"`rabbitmq_port_bindings`. Opsi baru ini adalah hash yang memungkinkan untuk "
"multiple bind addresses dan konfigurasi port."

msgid ""
"The options ``lxc_host_machine_qgroup_space_limit`` and "
"``lxc_host_machine_qgroup_compression_limit`` have been added allowing a "
"deployer to set **qgroup** limits as they see fit. The default value for "
"these options is \"none\" which is effectively **unlimited**. These options "
"accept any nominal size value followed by the single letter type, example "
"``64G``. These options are only effective when the option "
"``lxc_host_machine_quota_disabled`` is set to **false**."
msgstr ""
"Opsi ``lxc_host_machine_qgroup_space_limit`` dan "
"``lxc_host_machine_qgroup_compression_limit`` telah ditambahkan yang "
"memungkinkan seorang deployer untuk menetapkan batas **qgroup** sesuai "
"keinginan mereka. Nilai default untuk opsi ini adalah \"none\" yang efektif "
"**unlimited**. Opsi ini menerima nilai ukuran nominal apa pun yang diikuti "
"oleh jenis huruf tunggal, misalnya ``64G``. Opsi ini hanya efektif ketika "
"opsi ``lxc_host_machine_quota_disabled`` disetel ke **false**."

msgid ""
"The options of application logrotate configuration files are now "
"configurable. ``rsyslog_client_log_rotate_options`` can be used to provide a "
"list of directives, and ``rsyslog_client_log_rotate_scripts`` can be used to "
"provide a list of postrotate, prerotate, firstaction, or lastaction scripts."
msgstr ""
"Opsi file konfigurasi logrotate aplikasi sekarang dapat dikonfigurasi. "
"``rsyslog_client_log_rotate_options`` dapat digunakan untuk memberikan "
"daftar arahan, dan ``rsyslog_client_log_rotate_scripts`` dapat digunakan "
"untuk memberikan daftar scrip postrotate, prerotate, firstaction, atau "
"lastaction."

msgid ""
"The original ``stable/rocky`` release (18.0.x) contained a reference to a "
"pre-release state of the ceph-ansible role (its 3.2.0beta1 release). That "
"role --- and hence, any OpenStack-Ansible ``stable/rocky`` release prior to "
"18.1.0 --- should not be used to deploy production Ceph clusters. As of this "
"release, ``stable/rocky`` tracks the ceph-ansible role's ``stable-3.1`` "
"branch."
msgstr ""
"Rilisan ``stable/rocky`` asli (18.0.x) berisi referensi ke status pra-rilis "
"peran ceph-ansible (rilis 3.2.0beta1-nya). Peran itu --- dan karenanya, "
"setiap rilis OpenStack-Ansible ``stable/rocky` --- tidak boleh digunakan "
"untuk menggunakan cluster Ceph produksi. Pada rilis ini, ``stable/rocky`` "
"melacak cabang ``stable-3.1`` peran ceph-ansible"

msgid ""
"The os_aodh role always checks whether the latest package is installed when "
"executed. If a deployer wishes to change the check to only validate the "
"presence of the package, the option ``aodh_package_state`` should be set to "
"``present``."
msgstr ""
"Peran os_aodh selalu memeriksa apakah paket terbaru diinstal ketika "
"dijalankan. Jika seorang deployer ingin mengubah tanda centang untuk hanya "
"memvalidasi keberadaan paket, opsi ``aodh_package_state`` harus diatur ke "
"``present``."

msgid ""
"The os_aodh role now supports the ability to configure whether apt/yum tasks "
"install the latest available package, or just ensure that the package is "
"present. The default action is to ensure that the latest package is present. "
"The action taken may be changed to only ensure that the package is present "
"by setting ``aodh_package_state`` to ``present``."
msgstr ""
"Peran os_aodh sekarang mendukung kemampuan untuk mengkonfigurasi apakah "
"tugas apt/yum menginstal paket terbaru yang tersedia, atau hanya memastikan "
"bahwa paket tersebut ada. Tindakan default adalah untuk memastikan bahwa "
"paket terbaru hadir. Tindakan yang diambil dapat diubah hanya untuk "
"memastikan bahwa paket hadir dengan mengatur ``aodh_package_state`` ke "
"``present``."

msgid ""
"The os_barbican role always checks whether the latest package is installed "
"when executed. If a deployer wishes to change the check to only validate the "
"presence of the package, the option ``barbican_package_state`` should be set "
"to ``present``."
msgstr ""
"Peran os_barbican selalu memeriksa apakah paket terbaru diinstal ketika "
"dieksekusi. Jika seorang deployer ingin mengubah tanda centang untuk hanya "
"memvalidasi keberadaan paket, opsi ``barbican_package_state`` harus diatur "
"ke ``present``."

msgid ""
"The os_barbican role now supports the ability to configure whether apt/yum "
"tasks install the latest available package, or just ensure that the package "
"is present. The default action is to ensure that the latest package is "
"present. The action taken may be changed to only ensure that the package is "
"present by setting ``barbican_package_state`` to ``present``."
msgstr ""
"Peran os_barbican sekarang mendukung kemampuan untuk mengonfigurasi apakah "
"tugas apt/yum menginstal paket terbaru yang tersedia, atau hanya memastikan "
"bahwa paket tersebut ada. Tindakan default adalah untuk memastikan bahwa "
"paket terbaru hadir. Tindakan yang diambil dapat diubah hanya untuk "
"memastikan bahwa paket hadir dengan mengatur ``barbican_package_state`` ke "
"``present``."

msgid ""
"The os_ceilometer role always checks whether the latest package is installed "
"when executed. If a deployer wishes to change the check to only validate the "
"presence of the package, the option ``ceilometer_package_state`` should be "
"set to ``present``."
msgstr ""
"Peran os_ceilometer selalu memeriksa apakah paket terbaru diinstal ketika "
"dijalankan. Jika seorang deployer ingin mengubah tanda centang untuk hanya "
"memvalidasi keberadaan paket, opsi ``ceilometer_package_state`` harus diatur "
"ke ``present``."

msgid ""
"The os_ceilometer role now supports the ability to configure whether apt/yum "
"tasks install the latest available package, or just ensure that the package "
"is present. The default action is to ensure that the latest package is "
"present. The action taken may be changed to only ensure that the package is "
"present by setting ``ceilometer_package_state`` to ``present``."
msgstr ""
"Peran os_ceilometer sekarang mendukung kemampuan untuk mengonfigurasi apakah "
"tugas apt/yum menginstal paket terbaru yang tersedia, atau hanya memastikan "
"bahwa paket tersebut ada. Tindakan default adalah untuk memastikan bahwa "
"paket terbaru hadir. Tindakan yang diambil dapat diubah hanya untuk "
"memastikan bahwa paket hadir dengan mengatur ``ceilometer_package_state`` ke "
"``present``."

msgid ""
"The os_cinder role always checks whether the latest package is installed "
"when executed. If a deployer wishes to change the check to only validate the "
"presence of the package, the option ``cinder_package_state`` should be set "
"to ``present``."
msgstr ""
"Peran os_cinder selalu memeriksa apakah paket terbaru diinstal ketika "
"dijalankan. Jika seorang deployer ingin mengubah tanda centang untuk hanya "
"memvalidasi keberadaan paket, opsi ``cinder_package_state`` harus diatur ke  "
"``present``."

msgid ""
"The os_cinder role now supports the ability to configure whether apt/yum "
"tasks install the latest available package, or just ensure that the package "
"is present. The default action is to ensure that the latest package is "
"present. The action taken may be changed to only ensure that the package is "
"present by setting ``cinder_package_state`` to ``present``."
msgstr ""
"Peran os_cinder sekarang mendukung kemampuan untuk mengonfigurasi apakah "
"tugas apt/yum menginstal paket terbaru yang tersedia, atau hanya memastikan "
"bahwa paket tersebut ada. Tindakan default adalah untuk memastikan bahwa "
"paket terbaru hadir. Tindakan yang diambil dapat diubah hanya untuk "
"memastikan bahwa paket hadir dengan mengatur ``cinder_package_state`` ke "
"``present``."

msgid ""
"The os_cloudkitty role always checks whether the latest package is installed "
"when executed. If a deployer wishes to change the check to only validate the "
"presence of the package, the option ``cloudkitty_package_state`` should be "
"set to ``present``."
msgstr ""
"Peran os_cloudkitty selalu memeriksa apakah paket terbaru diinstal ketika "
"dijalankan. Jika seorang penggelar ingin mengubah tanda centang untuk hanya "
"memvalidasi keberadaan paket, opsi ``cloudkitty_package_state`` harus diatur "
"ke ``present``."

msgid ""
"The os_cloudkitty role now supports the ability to configure whether apt/yum "
"tasks install the latest available package, or just ensure that the package "
"is present. The default action is to ensure that the latest package is "
"present. The action taken may be changed to only ensure that the package is "
"present by setting ``cloudkitty_package_state`` to ``present``."
msgstr ""
"Peran os_cloudkitty sekarang mendukung kemampuan untuk mengkonfigurasi "
"apakah tugas apt/yum menginstal paket terbaru yang tersedia, atau hanya "
"memastikan bahwa paket tersebut ada. Tindakan default adalah untuk "
"memastikan bahwa paket terbaru hadir. Tindakan yang diambil dapat diubah "
"hanya untuk memastikan bahwa paket hadir dengan mengatur "
"``cloudkitty_package_state`` ke ``present``."

msgid ""
"The os_designate role always checks whether the latest package is installed "
"when executed. If a deployer wishes to change the check to only validate the "
"presence of the package, the option ``designate_package_state`` should be "
"set to ``present``."
msgstr ""
"Peran os_designate selalu memeriksa apakah paket terbaru diinstal ketika "
"dijalankan. Jika seorang deployer ingin mengubah tanda centang untuk hanya "
"memvalidasi keberadaan paket, opsi ``designate_package_state`` harus diatur "
"ke ``present``."

msgid ""
"The os_designate role now supports the ability to configure whether apt/yum "
"tasks install the latest available package, or just ensure that the package "
"is present. The default action is to ensure that the latest package is "
"present. The action taken may be changed to only ensure that the package is "
"present by setting ``designate_package_state`` to ``present``."
msgstr ""
"Peran os_designate sekarang mendukung kemampuan untuk mengonfigurasi apakah "
"tugas apt/yum menginstal paket terbaru yang tersedia, atau hanya memastikan "
"bahwa paket tersebut ada. Tindakan default adalah untuk memastikan bahwa "
"paket terbaru hadir. Tindakan yang diambil dapat diubah untuk hanya "
"memastikan bahwa paket hadir dengan mengatur ``designate_package_state`` ke "
"``present``."

msgid ""
"The os_glance role always checks whether the latest package is installed "
"when executed. If a deployer wishes to change the check to only validate the "
"presence of the package, the option ``glance_package_state`` should be set "
"to ``present``."
msgstr ""
"Peran os_glance selalu memeriksa apakah paket terbaru diinstal ketika "
"dijalankan. Jika seorang deployer ingin mengubah tanda centang untuk hanya "
"memvalidasi keberadaan paket, opsi ``glance_package_state`` harus diatur ke  "
"``present``."

msgid ""
"The os_glance role now supports the ability to configure whether apt/yum "
"tasks install the latest available package, or just ensure that the package "
"is present. The default action is to ensure that the latest package is "
"present. The action taken may be changed to only ensure that the package is "
"present by setting ``glance_package_state`` to ``present``."
msgstr ""
"Peran os_glance sekarang mendukung kemampuan untuk mengonfigurasi apakah "
"tugas apt/yum menginstal paket terbaru yang tersedia, atau hanya memastikan "
"bahwa paket tersebut ada. Tindakan default adalah untuk memastikan bahwa "
"paket terbaru hadir. Tindakan yang diambil dapat diubah hanya untuk "
"memastikan bahwa paket hadir dengan mengatur ``glance_package_state`` ke "
"``present``."

msgid ""
"The os_gnocchi role always checks whether the latest package is installed "
"when executed. If a deployer wishes to change the check to only validate the "
"presence of the package, the option ``gnocchi_package_state`` should be set "
"to ``present``."
msgstr ""
"Peran os_gnocchi selalu memeriksa apakah paket terbaru diinstal ketika "
"dijalankan. Jika seorang deployer ingin mengubah tanda centang untuk hanya "
"memvalidasi keberadaan paket, opsi ``gnocchi_package_state`` harus diatur ke "
"``present``."

msgid ""
"The os_gnocchi role now supports the ability to configure whether apt/yum "
"tasks install the latest available package, or just ensure that the package "
"is present. The default action is to ensure that the latest package is "
"present. The action taken may be changed to only ensure that the package is "
"present by setting ``gnocchi_package_state`` to ``present``."
msgstr ""
"Peran os_gnocchi sekarang mendukung kemampuan untuk mengkonfigurasi apakah "
"tugas apt/yum menginstal paket terbaru yang tersedia, atau hanya memastikan "
"bahwa paket tersebut ada. Tindakan default adalah untuk memastikan bahwa "
"paket terbaru hadir. Tindakan yang diambil dapat diubah hanya untuk "
"memastikan bahwa paket hadir dengan mengatur ``gnocchi_package_state`` ke "
"``present``."

msgid ""
"The os_heat role always checks whether the latest package is installed when "
"executed. If a deployer wishes to change the check to only validate the "
"presence of the package, the option ``heat_package_state`` should be set to "
"``present``."
msgstr ""
"Peran os_heat selalu memeriksa apakah paket terbaru diinstal ketika "
"dijalankan. Jika seorang deployer ingin mengubah tanda centang untuk hanya "
"memvalidasi keberadaan paket, opsi ``heat_package_state`` harus diatur ke "
"``present``."

msgid ""
"The os_heat role now supports the ability to configure whether apt/yum tasks "
"install the latest available package, or just ensure that the package is "
"present. The default action is to ensure that the latest package is present. "
"The action taken may be changed to only ensure that the package is present "
"by setting ``heat_package_state`` to ``present``."
msgstr ""
"Peran os_heat sekarang mendukung kemampuan untuk mengonfigurasi apakah tugas "
"apt/yum menginstal paket terbaru yang tersedia, atau hanya memastikan bahwa "
"paket tersebut ada. Tindakan default adalah untuk memastikan bahwa paket "
"terbaru hadir. Tindakan yang diambil dapat diubah hanya untuk memastikan "
"bahwa paket hadir dengan mengatur ``heat_package_state`` ke ``present``."

msgid ""
"The os_horizon role always checks whether the latest package is installed "
"when executed. If a deployer wishes to change the check to only validate the "
"presence of the package, the option ``horizon_package_state`` should be set "
"to ``present``."
msgstr ""
"Peran os_horizon selalu memeriksa apakah paket terbaru diinstal ketika "
"dijalankan. Jika seorang deployer ingin mengubah tanda centang untuk hanya "
"memvalidasi keberadaan paket, opsi ``horizon_package_state`` harus diatur ke "
"``present``."

msgid ""
"The os_horizon role now has support for the horizon designate-ui dashboard. "
"The dashboard may be enabled by setting ``horizon_enable_designate_ui`` to "
"``True`` in ``/etc/openstack_deploy/user_variables.yml``."
msgstr ""
"Peran os_horizon sekarang memiliki dukungan untuk dasbor horizon designate-"
"ui. Dasbor dapat diaktifkan dengan pengaturan "
"``horizon_enable_designate_ui`` ke ``True`` dalam ``/etc/openstack_deploy/"
"user_variables.yml``."

msgid ""
"The os_horizon role now has support for the horizon ironic-ui dashboard. The "
"dashboard may be enabled by setting ``horizon_enable_ironic_ui`` to ``True`` "
"in ``/etc/openstack_deploy/user_variables.yml``."
msgstr ""
"Peran os_horizon sekarang memiliki dukungan untuk dasbor horizon ironic-ui. "
"Dasbor dapat diaktifkan dengan pengaturan ``horizon_enable_ironic_ui`` ke "
"``True`` dalam ``/etc/openstack_deploy/user_variables.yml``."

msgid ""
"The os_horizon role now has support for the horizon magnum-ui dashboard. The "
"dashboard may be enabled by setting ``horizon_enable_magnum_ui`` to ``True`` "
"in ``/etc/openstack_deploy/user_variables.yml``."
msgstr ""
"Peran os_horizon sekarang memiliki dukungan untuk dasbor horizon magnum-ui. "
"Dasbor dapat diaktifkan dengan pengaturan ``horizon_enable_magnum_ui`` ke "
"``True`` dalam ``/etc/openstack_deploy/user_variables.yml``."

msgid ""
"The os_horizon role now has support for the horizon manila-ui dashboard. The "
"dashboard may be enabled by setting ``horizon_enable_manila_ui`` to ``True`` "
"in ``/etc/openstack_deploy/user_variables.yml``."
msgstr ""
"Peran os_horizon sekarang memiliki dukungan untuk dasbor horizon manila-ui. "
"Dasbor dapat diaktifkan dengan pengaturan ``horizon_enable_manila_ui`` ke "
"``True`` dalam ``/etc/openstack_deploy/user_variables.yml``."

msgid ""
"The os_horizon role now supports the ability to configure whether apt/yum "
"tasks install the latest available package, or just ensure that the package "
"is present. The default action is to ensure that the latest package is "
"present. The action taken may be changed to only ensure that the package is "
"present by setting ``horizon_package_state`` to ``present``."
msgstr ""
"Peran os_horizon sekarang mendukung kemampuan untuk mengkonfigurasi apakah "
"tugas apt/yum menginstal paket terbaru yang tersedia, atau hanya memastikan "
"bahwa paket tersebut ada. Tindakan default adalah untuk memastikan bahwa "
"paket terbaru hadir. Tindakan yang diambil dapat diubah hanya untuk "
"memastikan bahwa paket hadir dengan mengatur ``horizon_package_state`` ke "
"``present``."

msgid ""
"The os_ironic role always checks whether the latest package is installed "
"when executed. If a deployer wishes to change the check to only validate the "
"presence of the package, the option ``ironic_package_state`` should be set "
"to ``present``."
msgstr ""
"Peran os_ironic selalu memeriksa apakah paket terbaru diinstal ketika "
"dieksekusi. Jika seorang deployer ingin mengubah tanda centang untuk hanya "
"memvalidasi keberadaan paket, opsi ``ironic_package_state`` harus diatur ke  "
"``present``."

msgid ""
"The os_ironic role now supports the ability to configure whether apt/yum "
"tasks install the latest available package, or just ensure that the package "
"is present. The default action is to ensure that the latest package is "
"present. The action taken may be changed to only ensure that the package is "
"present by setting ``ironic_package_state`` to ``present``."
msgstr ""
"Peran os_ironic sekarang mendukung kemampuan untuk mengonfigurasi apakah "
"tugas apt/yum menginstal paket terbaru yang tersedia, atau hanya memastikan "
"bahwa paket tersebut ada. Tindakan default adalah untuk memastikan bahwa "
"paket terbaru hadir. Tindakan yang diambil dapat diubah untuk hanya "
"memastikan bahwa paket hadir dengan mengatur ``ironic_package_state`` ke "
"``present``."

msgid ""
"The os_keystone role always checks whether the latest package is installed "
"when executed. If a deployer wishes to change the check to only validate the "
"presence of the package, the option ``keystone_package_state`` should be set "
"to ``present``."
msgstr ""
"Peran os_keystone selalu memeriksa apakah paket terbaru diinstal ketika "
"dijalankan. Jika seorang deployer ingin mengubah tanda centang untuk hanya "
"memvalidasi keberadaan paket, opsi ``keystone_package_state`` harus diatur "
"ke ``present``."

msgid ""
"The os_keystone role now performs a rolling upgrade without downtime during "
"installation. `The process for rolling upgrades is documented here <http://"
"docs.openstack.org/developer/keystone/upgrading.html#upgrading-without-"
"downtime>`_."
msgstr ""
"Peran os_keystone sekarang melakukan pemutakhiran bergulir tanpa downtime "
"selama instalasi. `The process for rolling upgrades is documented here "
"<http://docs.openstack.org/developer/keystone/upgrading.html#upgrading-"
"without-downtime>`_."

msgid ""
"The os_keystone role now supports the ability to configure whether apt/yum "
"tasks install the latest available package, or just ensure that the package "
"is present. The default action is to ensure that the latest package is "
"present. The action taken may be changed to only ensure that the package is "
"present by setting ``keystone_package_state`` to ``present``."
msgstr ""
"Peran os_keystone sekarang mendukung kemampuan untuk mengonfigurasi apakah "
"tugas apt/yum menginstal paket terbaru yang tersedia, atau hanya memastikan "
"bahwa paket tersebut ada. Tindakan default adalah untuk memastikan bahwa "
"paket terbaru hadir. Tindakan yang diambil dapat diubah hanya untuk "
"memastikan bahwa paket hadir dengan mengatur ``keystone_package_state`` ke "
"``present``."

msgid ""
"The os_magnum role always checks whether the latest package is installed "
"when executed. If a deployer wishes to change the check to only validate the "
"presence of the package, the option ``magnum_package_state`` should be set "
"to ``present``."
msgstr ""
"Peran os_magnum selalu memeriksa apakah paket terbaru diinstal ketika "
"dijalankan. Jika seorang deployer ingin mengubah tanda centang untuk hanya "
"memvalidasi keberadaan paket, opsi ``magnum_package_state`` harus diatur ke "
"``present``."

msgid ""
"The os_magnum role now supports the ability to configure whether apt/yum "
"tasks install the latest available package, or just ensure that the package "
"is present. The default action is to ensure that the latest package is "
"present. The action taken may be changed to only ensure that the package is "
"present by setting ``magnum_package_state`` to ``present``."
msgstr ""
"Peran os_magnum sekarang mendukung kemampuan untuk mengonfigurasi apakah "
"tugas apt/yum menginstal paket terbaru yang tersedia, atau hanya memastikan "
"bahwa paket tersebut ada. Tindakan default adalah untuk memastikan bahwa "
"paket terbaru hadir. Tindakan yang diambil dapat diubah hanya untuk "
"memastikan bahwa paket hadir dengan mengatur ``magnum_package_state`` ke "
"``present``."

msgid ""
"The os_neutron role always checks whether the latest package is installed "
"when executed. If a deployer wishes to change the check to only validate the "
"presence of the package, the option ``neutron_package_state`` should be set "
"to ``present``."
msgstr ""
"Peran os_neutron selalu memeriksa apakah paket terbaru diinstal ketika "
"dijalankan. Jika seorang deployer ingin mengubah tanda centang untuk hanya "
"memvalidasi keberadaan paket, opsi ``neutron_package_state`` harus diatur ke "
"``present``."

msgid ""
"The os_neutron role now supports the ability to configure whether apt/yum "
"tasks install the latest available package, or just ensure that the package "
"is present. The default action is to ensure that the latest package is "
"present. The action taken may be changed to only ensure that the package is "
"present by setting ``neutron_package_state`` to ``present``."
msgstr ""
"Peran os_neutron sekarang mendukung kemampuan untuk mengonfigurasi apakah "
"tugas apt/yum menginstal paket terbaru yang tersedia, atau hanya memastikan "
"bahwa paket tersebut ada. Tindakan default adalah untuk memastikan bahwa "
"paket terbaru hadir. Tindakan yang diambil dapat diubah hanya untuk "
"memastikan bahwa paket hadir dengan mengatur ``neutron_package_state`` ke "
"``present``."

msgid ""
"The os_neutron role uses the same handler name as the etcd role for "
"executing ``systemcl daemon-reload``. Given that newton uses Ansible 2.1.x "
"and that version of Ansible cannot process more than one handler by the same "
"name in a single playbook, only one handler ends up being executed. The "
"handler that does get executed is the etcd handler which is skipped unless "
"the deployment is using Calico."
msgstr ""
"Peran os_neutron menggunakan nama penangan yang sama dengan peran etcd untuk "
"mengeksekusi ``systemcl daemon-reload``. Mengingat bahwa newton menggunakan "
"Ansible 2.1.x dan versi Ansible tidak dapat memproses lebih dari satu "
"penangan dengan nama yang sama dalam satu playbook, hanya satu penangan yang "
"akhirnya dieksekusi. Handler yang dieksekusi adalah handler etcd yang "
"dilewati kecuali deployment menggunakan Calico."

msgid ""
"The os_nova role always checks whether the latest package is installed when "
"executed. If a deployer wishes to change the check to only validate the "
"presence of the package, the option ``nova_package_state`` should be set to "
"``present``."
msgstr ""
"Peran os_nova selalu memeriksa apakah paket terbaru diinstal ketika "
"dijalankan. Jika seorang deployer ingin mengubah tanda centang untuk hanya "
"memvalidasi keberadaan paket, opsi ``nova_package_state`` harus diatur ke "
"``present``."

msgid ""
"The os_nova role can now deploy the a custom /etc/libvirt/qemu.conf file by "
"defining ``qemu_conf_dict``."
msgstr ""
"Peran os_nova sekarang dapat menggunakan file /etc/libvirt/qemu.conf kustom "
"dengan mendefinisikan ``qemu_conf_dict``."

msgid ""
"The os_nova role can now deploy the nova-lxd hypervisor. This can be "
"achieved by setting ``nova_virt_type`` to ``lxd`` on a per-host basis in "
"``openstack_user_config.yml`` or on a global basis in ``user_variables.yml``."
msgstr ""
"Peran os_nova sekarang dapat menggunakan hypervisor nova-lxd. Ini dapat "
"dicapai dengan mengatur ``nova_virt_type`` ke ``lxd`` pada basis per-host di "
"``openstack_user_config.yml`` atau secara global dalam ``user_variables."
"yml``."

msgid ""
"The os_nova role can now detect a PowerNV environment and set the "
"virtualization type to 'kvm'."
msgstr ""
"Peran os_nova sekarang dapat mendeteksi lingkungan PowerNV dan mengatur tipe "
"virtualisasi ke 'kvm'."

msgid ""
"The os_nova role can now detect and support basic deployment of a PowerVM "
"environment. This sets the virtualization type to 'powervm' and installs/"
"updates the PowerVM NovaLink package and nova-powervm driver."
msgstr ""
"Peran os_nova sekarang dapat mendeteksi dan mendukung penyebaran dasar "
"lingkungan PowerVM. Ini menetapkan tipe virtualisasi ke 'powervm' dan "
"menginstal/memperbarui paket PowerVM NovaLink dan driver nova-powervm."

msgid ""
"The os_nova role now supports the ability to configure whether apt/yum tasks "
"install the latest available package, or just ensure that the package is "
"present. The default action is to ensure that the latest package is present. "
"The action taken may be changed to only ensure that the package is present "
"by setting ``nova_package_state`` to ``present``."
msgstr ""
"Peran os_nova sekarang mendukung kemampuan untuk mengkonfigurasi apakah "
"tugas apt/yum menginstal paket terbaru yang tersedia, atau hanya memastikan "
"bahwa paket tersebut ada. Tindakan default adalah untuk memastikan bahwa "
"paket terbaru hadir. Tindakan yang diambil dapat diubah hanya untuk "
"memastikan bahwa paket hadir dengan mengatur ``nova_package_state`` ke "
"``present``."

msgid ""
"The os_rally role always checks whether the latest package is installed when "
"executed. If a deployer wishes to change the check to only validate the "
"presence of the package, the option ``rally_package_state`` should be set to "
"``present``."
msgstr ""
"Peran os_rally selalu memeriksa apakah paket terbaru diinstal ketika "
"dijalankan. Jika seorang deployer ingin mengubah tanda centang untuk hanya "
"memvalidasi keberadaan paket, opsi ``rally_package_state`` harus diatur ke "
"``present``."

msgid ""
"The os_rally role now supports the ability to configure whether apt/yum "
"tasks install the latest available package, or just ensure that the package "
"is present. The default action is to ensure that the latest package is "
"present. The action taken may be changed to only ensure that the package is "
"present by setting ``rally_package_state`` to ``present``."
msgstr ""
"Peran os_rally sekarang mendukung kemampuan untuk mengkonfigurasi apakah "
"tugas apt/yum menginstal paket terbaru yang tersedia, atau hanya memastikan "
"bahwa paket tersebut ada. Tindakan default adalah untuk memastikan bahwa "
"paket terbaru hadir. Tindakan yang diambil dapat diubah hanya untuk "
"memastikan bahwa paket hadir dengan mengatur ``rally_package_state`` ke "
"``present``."

msgid ""
"The os_sahara role always checks whether the latest package is installed "
"when executed. If a deployer wishes to change the check to only validate the "
"presence of the package, the option ``sahara_package_state`` should be set "
"to ``present``."
msgstr ""
"Peran os_sahara selalu memeriksa apakah paket terbaru diinstal ketika "
"dijalankan. Jika seorang deployer ingin mengubah tanda centang untuk hanya "
"memvalidasi keberadaan paket, opsi ``sahara_package_state`` harus diatur ke "
"``present``."

msgid ""
"The os_sahara role now supports the ability to configure whether apt/yum "
"tasks install the latest available package, or just ensure that the package "
"is present. The default action is to ensure that the latest package is "
"present. The action taken may be changed to only ensure that the package is "
"present by setting ``sahara_package_state`` to ``present``."
msgstr ""
"Peran os_sahara sekarang mendukung kemampuan untuk mengkonfigurasi apakah "
"tugas apt/yum menginstal paket terbaru yang tersedia, atau hanya memastikan "
"bahwa paket tersebut ada. Tindakan default adalah untuk memastikan bahwa "
"paket terbaru hadir. Tindakan yang diambil dapat diubah hanya untuk "
"memastikan bahwa paket tersebut hadir dengan mengatur "
"``sahara_package_state`` ke ``present``."

msgid ""
"The os_swift and os_swift_sync role have been merged into the single "
"os_swift role. Two variables (``swift_do_setup`` and ``swift_do_sync``) have "
"been implemented to action the install and synchronise code paths. The "
"separate playbooks have been adjusted to make use of these variables to "
"ensure that the behaviour is exactly the same as before."
msgstr ""
"Peran os_swift dan os_swift_sync telah digabungkan ke dalam peran os_swift "
"tunggal. Dua variabel (``swift_do_setup`` dan ``swift_do_sync``) telah "
"diterapkan untuk melakukan tindakan menginstal dan menyinkronkan path kode. "
"Playbook terpisah telah disesuaikan untuk menggunakan variabel ini untuk "
"memastikan bahwa perilaku itu persis sama seperti sebelumnya."

msgid ""
"The os_swift role always checks whether the latest package is installed when "
"executed. If a deployer wishes to change the check to only validate the "
"presence of the package, the option ``swift_package_state`` should be set to "
"``present``."
msgstr ""
"Peran os_swift selalu memeriksa apakah paket terbaru diinstal ketika "
"dijalankan. Jika seorang deployer ingin mengubah tanda centang untuk hanya "
"memvalidasi keberadaan paket, opsi ``swift_package_state`` harus diatur ke "
"``present``."

msgid ""
"The os_swift role now allows the permissions for the log files created by "
"the swift account, container and object servers to be set. The variable is "
"``swift_syslog_log_perms`` and is set to ``0644`` by default."
msgstr ""
"Peran os_swift sekarang memungkinkan izin untuk file log yang dibuat oleh "
"akun swift, kontainer dan server objek diatur. Variabelnya adalah "
"``swift_syslog_log_perms`` dan diatur ke ``0644`` secara default."

msgid ""
"The os_swift role now supports the ability to configure whether apt/yum "
"tasks install the latest available package, or just ensure that the package "
"is present. The default action is to ensure that the latest package is "
"present. The action taken may be changed to only ensure that the package is "
"present by setting ``swift_package_state`` to ``present``."
msgstr ""
"Peran os_swift sekarang mendukung kemampuan untuk mengonfigurasi apakah "
"tugas apt/yum menginstal paket terbaru yang tersedia, atau hanya memastikan "
"bahwa paket tersebut ada. Tindakan default adalah untuk memastikan bahwa "
"paket terbaru hadir. Tindakan yang diambil dapat diubah hanya untuk "
"memastikan bahwa paket hadir dengan mengatur ``swift_package_state`` ke "
"``present``."

msgid ""
"The os_swift role now supports the swift3 middleware, allowing access to "
"swift via the Amazon S3 API.  This feature can enabled by setting "
"``swift_swift3_enabled`` to ``true``."
msgstr ""
"Peran os_swift sekarang mendukung middleware swift3, memungkinkan akses "
"cepat melalui Amazon S3 API. Fitur ini dapat diaktifkan dengan mengatur "
"``swift_swift3_enabled`` ke ``true``."

msgid ""
"The override ``rabbitmq_memory_high_watermark`` can be used to set the "
"maximum size of the erlang Virtual Machine before the garbage collection is "
"triggered. The default is lowered to ``0.2``, from ``0.4`` as the garbage "
"collection can require 2x of allocated amount during its operation. This can "
"result in a equivalent use of ``0.4``, resulting in 40% of memory usage, "
"visible to the rabbitMQ container. The original default setting of ``0.4`` "
"can lead to 80% memory allocation of rabbitMQ, potentially leading to a "
"scenario where the underlying Linux kernel is killing the process due to "
"shortage of virtual memory."
msgstr ""
"Override ``rabbitmq_memory_high_watermark`` dapat digunakan untuk mengatur "
"ukuran maksimum Mesin Virtual erlang sebelum pengumpulan sampah dipicu. "
"Default diturunkan ke ``0,2``, dari ``0,4`` karena pengumpulan sampah dapat "
"membutuhkan 2x jumlah yang dialokasikan selama operasinya. Ini dapat "
"menghasilkan penggunaan setara dengan ``0,4``, menghasilkan 40% penggunaan "
"memori, terlihat oleh kontainer rabbitMQ. Pengaturan default asli dari "
"``0,4`` dapat menyebabkan alokasi memori 80% dari rabbitMQ, berpotensi "
"mengarah ke skenario di mana kernel Linux yang mendasarinya membunuh proses "
"karena kekurangan memori virtual."

msgid ""
"The package cache on the repo server has been removed. If caching of "
"packages is desired, it should be setup outside of OpenStack-Ansible and the "
"variable ``lxc_container_cache_files`` (for LXC containers) or "
"``nspawn_container_cache_files_from_host`` (for nspawn containers) can be "
"used to copy the appropriate host configuration from the host into the "
"containers on creation. Alternatively, environment variables can be set to "
"use the cache in the host /etc/environment file prior to container creation, "
"or the ``deployment_environment_variables`` can have the right variables set "
"to use it. The following variables have been removed."
msgstr ""
"Cache paket pada server repo telah dihapus. Jika caching paket diinginkan, "
"itu harus di-setup di luar OpenStack-Ansible dan variabel "
"``lxc_container_cache_files`` (untuk kontainer LXC) atau "
"``nspawn_container_cache_files_from_host`` (untuk nspawn kontainer) dapat "
"digunakan untuk menyalin konfigurasi host yang sesuai dari host ke dalam "
"kontainer saat penciptaan. Atau, variabel lingkungan dapat diatur untuk "
"menggunakan cache di file host /etc/environment sebelum pembuatan kontainer, "
"atau ``deployment_environment_variables`` dapat memiliki variabel yang tepat "
"diatur untuk menggunakannya. Variabel berikut telah dihapus."

msgid ""
"The password minimum and maximum lifetimes are now opt-in changes that can "
"take action against user accounts instead of printing debug warnings. Refer "
"to the documentation for STIG requirements V-71927 and V-71931 to review the "
"opt-in process and warnings."
msgstr ""
"Masa hidup minimum dan maksimum kata sandi sekarang merupakan perubahan opt-"
"in yang dapat mengambil aksi terhadap akun pengguna daripada mencetak "
"peringatan debug. Rujuk ke dokumentasi untuk persyaratan STIG V-71927 dan "
"V-71931 untuk meninjau proses opt-in dan peringatan."

msgid ""
"The percona repository stayed in placed even after a change of the variable "
"``use_percona_upstream``. From now on, the percona repository will not be "
"present unless the deployer decides to ``use_percona_upstream``. This also "
"fixes a bug of the presence of this apt repository after an upgdrade from "
"Mitaka."
msgstr ""
"Repositori percona tetap ditempatkan bahkan setelah perubahan variabel "
"``use_percona_upstream``. Mulai sekarang, repositori percona tidak akan ada "
"kecuali jika deployer memutuskan untuk ``use_percona_upstream``. Ini juga "
"memperbaiki bug dari keberadaan repositori yang tepat ini setelah pembaruan "
"dari Mitaka."

msgid ""
"The percona-xtrabackup repository is now enabled in OpenStack-Ansible and it "
"allows deployers to install and use `Percona's XtraBackup project <https://"
"www.percona.com/software/mysql-database/percona-xtrabackup>`_ to perform "
"online backups of data stored in MariaDB."
msgstr ""
"Repository percona-xtrabackup sekarang diaktifkan di OpenStack-Ansible dan "
"memungkinkan deployer untuk menginstal dan menggunakan `Percona's XtraBackup "
"project <https://www.percona.com/software/mysql-database/percona-"
"xtrabackup>`_ untuk melakukan backup online data yang disimpan di MariaDB."

msgid ""
"The ping check that happens inside keepalived to make sure that the server "
"that runs it can reach 193.0.14.129 has been removed by default.  The "
"functionality can continue to be used if you define the "
"`keepalived_ping_address` in your `user_variables.yml` file to "
"`193.0.14.129` or any IP of your choice."
msgstr ""
"Pemeriksaan ping yang terjadi di dalam keepalived untuk memastikan bahwa "
"server yang menjalankannya dapat mencapai 193.0.14.129 telah dihapus secara "
"default. Fungsionalitas dapat terus digunakan jika Anda mendefinisikan "
"`keepalived_ping_address` dalam file `user_variables.yml` Anda menjadi "
"`193.0.14.129` atau IP apa pun pilihan Anda."

msgid ""
"The pip_install role always checks whether the latest package is installed "
"when executed. If a deployer wishes to change the check to only validate the "
"presence of the package, the option ``pip_install_package_state`` should be "
"set to ``present``."
msgstr ""
"Peran pip_install selalu memeriksa apakah paket terbaru diinstal ketika "
"dijalankan. Jika seorang deployer ingin mengubah tanda centang untuk hanya "
"memvalidasi keberadaan paket, opsi ``pip_install_package_state`` harus "
"diatur ke ``present``."

msgid ""
"The pip_install role can now configure pip to be locked down to the "
"repository built by OpenStack-Ansible. To enable the lockdown configuration, "
"deployers may set ``pip_lock_to_internal_repo`` to ``true`` in ``/etc/"
"openstack_deploy/user_variables.yml``."
msgstr ""
"Peran pip_install sekarang dapat mengkonfigurasi pip agar dikunci ke "
"repositori yang dibangun oleh OpenStack-Ansible. Untuk mengaktifkan "
"konfigurasi penguncian, deployer dapat mengatur "
"``pip_lock_to_internal_repo`` ke ``true`` dalam ``/etc/openstack_deploy/"
"user_variables.yml``."

msgid ""
"The pip_install role now supports the ability to configure whether apt/yum "
"tasks install the latest available package, or just ensure that the package "
"is present. The default action is to ensure that the latest package is "
"present. The action taken may be changed to only ensure that the package is "
"present by setting ``pip_install_package_state`` to ``present``."
msgstr ""
"Peran pip_install sekarang mendukung kemampuan untuk mengonfigurasi apakah "
"tugas apt/yum menginstal paket terbaru yang tersedia, atau hanya memastikan "
"bahwa paket tersebut ada. Tindakan default adalah untuk memastikan bahwa "
"paket terbaru hadir. Tindakan yang diambil dapat diubah hanya untuk "
"memastikan bahwa paket hadir dengan mengatur ``pip_install_package_state`` "
"ke ``present``."

msgid ""
"The pip_install_options variable is now honored during repo building.  This "
"variable allows deployers to specify trusted CA certificates by setting the "
"variable to \"--cert /etc/ssl/certs/ca-certificates.crt\""
msgstr ""
"Variabel pip_install_options sekarang dihormati selama pembuatan repo. "
"Variabel ini memungkinkan deployer untuk menentukan sertifikat CA tepercaya "
"dengan mengatur variabel ke \"--cert /etc/ssl/certs/ca-certificates.crt\""

msgid "The plugin names for the classifier and sfc changed:"
msgstr "Nama plugin untuk classifier dan sfc berubah:"

msgid ""
"The plugins folders have been renamed to the default names used in Ansible 2."
"x. This is part of the preparation for Ansible 2.x readiness. The renames "
"are specifically ``actions > action``, ``callbacks > callback``, ``filters > "
"filter``, ``lookups > lookup``."
msgstr ""
"Folder plugins telah diubah namanya menjadi nama default yang digunakan "
"dalam Ansible 2.x. Ini adalah bagian dari persiapan untuk kesiapan Ansible 2."
"x. Ganti nama secara khusus ``actions > action``, ``callbacks > callback``, "
"``filters > filter``, ``lookups > lookup``."

msgid ""
"The plumgrid network provider has been removed. This is being dropped "
"without a full deprecation cycle because the company, plumgrid, no longer "
"exists."
msgstr ""
"Penyedia jaringan plumgrid telah dihapus. Ini dijatuhkan tanpa siklus "
"penghentian penuh karena perusahaan, plumgrid, tidak ada lagi."

msgid ""
"The previous way of using a common backend_host across all deployments was "
"not recommended by the Cinder team and it will cause duplicate messages that "
"cause problems in the environment."
msgstr ""
"Cara sebelumnya menggunakan backend_host umum di semua penyebaran tidak "
"direkomendasikan oleh tim Cinder dan itu akan menyebabkan pesan duplikat "
"yang menyebabkan masalah di environment."

msgid ""
"The problem has been registered upstream and progresson the issue can be "
"followed there: https://jira.mariadb.org/browse/MDEV-15254"
msgstr ""
"Masalahnya telah terdaftar di hulu dan perkembangan masalah dapat diikuti di "
"sana : https://jira.mariadb.org/browse/MDEV-15254"

msgid ""
"The python packages `pip`, `setuptools` and `wheel` are now all pinned on a "
"per-tag basis. The pins are updated along with every OpenStack Service "
"update. This is done to ensure a consistent build experience with the latest "
"available packages at the time the tag is released. A deployer may override "
"the pins by adding a list of required pins using the `pip_packages` variable "
"in `user_variables.yml`."
msgstr ""
"Paket python `pip`, `setuptools` dan `wheel` sekarang semuanya disematkan "
"(pinned) pada basis per-tag. Pin diperbarui bersama dengan setiap update "
"OpenStack Service. Ini dilakukan untuk memastikan pengalaman membangun yang "
"konsisten dengan paket terbaru yang tersedia pada saat tag dirilis. Deployer "
"dapat menimpa pin dengan menambahkan daftar pin yang diperlukan menggunakan "
"variabel `pip_packages` di `user_variables.yml`."

msgid ""
"The python venv build process now only happens when requirements change. A "
"venv rebuild may be forced by using the boolean variable "
"``repo_build_venv_rebuild``."
msgstr ""
"Proses pembuatan python venv sekarang hanya terjadi ketika persyaratan "
"berubah. Pembangunan kembali venv dapat dipaksa dengan menggunakan variabel "
"boolean ``repo_build_venv_rebuild``."

msgid ""
"The python wheel build process now only happens when requirements change. A "
"wheel rebuild may be forced by using the boolean variable "
"``repo_build_wheel_rebuild``."
msgstr ""
"Proses pembuatan python wheel sekarang hanya terjadi ketika persyaratan "
"berubah. Pembangunan kembali wheel dapat dipaksa dengan menggunakan variabel "
"boolean ``repo_build_wheel_rebuild``."

msgid ""
"The quota for security group rules was erroneously set to 100 with the aim "
"to have 100 security group rules per security group instead of to "
"100*#security group rules. This patch fixes this discrepancy."
msgstr ""
"Kuota untuk aturan grup keamanan secara keliru ditetapkan ke 100 dengan "
"tujuan untuk memiliki 100 aturan grup keamanan per grup keamanan daripada ke "
"aturan grup 100*#security . Patch ini memperbaiki perbedaan ini."

msgid ""
"The rabbitMQ high watermark is set to ``0.2`` rather than ``0.4`` to prevent "
"possible OOM situations, which limits the maximum memory usage by rabbitMQ "
"to 40% rather than 80% of the memory visible to the rabbitMQ container. The "
"override ``rabbitmq_memory_high_watermark`` can be used to alter the limit."
msgstr ""
"Watermark tinggi rabbitMQ diatur ke ``0,2`` daripada ``0,4`` untuk mencegah "
"kemungkinan situasi OOM, yang membatasi penggunaan memori maksimum oleh "
"rabbitMQ hingga 40% daripada 80% memori yang terlihat oleh kontainer "
"rabbitMQ. Override ``rabbitmq_memory_high_watermark`` dapat digunakan untuk "
"mengubah batas."

msgid ""
"The rabbitmq server parameters have been replaced by corresponding oslo."
"messaging Notify parameters in order to abstract the messaging service from "
"the actual backend server deployment. - swift_oslomsg_notify_servers "
"replaces swift_rabbitmq_telemetry_servers - swift_oslomsg_notify_port "
"replaces swift_rabbitmq_telemetry_port - swift_oslomsg_notify_use_ssl "
"replaces swift_rabbitmq_telemetry_use_ssl - swift_oslomsg_notify_userid "
"replaces swift_rabbitmq_telemetry_userid - swift_oslomsg_notify_vhost "
"replaces swift_rabbitmq_telemetry_vhost - swift_oslomsg_notify_password "
"replaces swift_rabbitmq_telemetry_password"
msgstr ""
"Parameter server rabbitmq telah digantikan oleh parameter oslo.messaging "
"Notify untuk mengabstraksi layanan pesan dari deployment server backend yang "
"sebenarnya. - swift_oslomsg_notify_servers menggantikan "
"swift_rabbitmq_telemetry_servers - swift_oslomsg_notify_port menggantikan "
"swift_rabbitmq_telemetry_port - swift_oslomsg_notify_use_ssl menggantikan "
"swift_rabbitmq_telemetry_use_ssl - swift_oslomsg_notify_userid menggantikan "
"swift_rabbitmq_telemetry_userid - swift_oslomsg_notify_vhost menggantikan "
"swift_rabbitmq_telemetry_vhost - swift_oslomsg_notify_password menggantikan "
"swift_rabbitmq_telemetry_password"

msgid ""
"The rabbitmq server parameters have been replaced by corresponding oslo."
"messaging RPC and Notify parameters in order to abstract the messaging "
"service from the actual backend server deployment. - "
"aodh_oslomsg_rpc_servers replaces aodh_rabbitmq_servers - "
"aodh_oslomsg_rpc_port replaces aodh_rabbitmq_port - aodh_oslomsg_rpc_use_ssl "
"replaces aodh_rabbitmq_use_ssl - aodh_oslomsg_rpc_userid replaces "
"aodh_rabbitmq_userid - aodh_oslomsg_rpc_vhost replaces aodh_rabbitmq_vhost - "
"aodh_oslomsg_rpc_password replaces aodh_rabbitmq_password"
msgstr ""
"Parameter server rabbitmq telah digantikan oleh parameter oslo.messaging RPC "
"dan Notify untuk abstrak layanan pesan dari deployment server backend yang "
"sebenarnya. - - aodh_oslomsg_rpc_servers menggantikan aodh_rabbitmq_servers  "
"- aodh_oslomsg_rpc_port menggantikan aodh_rabbitmq_port - "
"aodh_oslomsg_rpc_use_ssl menggantikan aodh_rabbitmq_use_ssl - "
"aodh_oslomsg_rpc_userid menggantikan aodh_rabbitmq_userid - "
"aodh_oslomsg_rpc_vhost menggantikan aodh_rabbitmq_vhost - "
"aodh_oslomsg_rpc_password menggantikan aodh_rabbitmq_password"

msgid ""
"The rabbitmq server parameters have been replaced by corresponding oslo."
"messaging RPC and Notify parameters in order to abstract the messaging "
"service from the actual backend server deployment. - "
"barbican_oslomsg_rpc_servers replaces rabbitmq_servers - "
"barbican_oslomsg_rpc_port replaces rabbitmq_port - "
"barbican_oslomsg_rpc_userid replaces barbican_rabbitmq_userid - "
"barbican_oslomsg_rpc_vhost replaces barbican_rabbitmq_vhost - added "
"barbican_oslomsg_rpc_use_ssl - added barbican_oslomsg_notify_servers - added "
"barbican_oslomsg_notify_port - added barbican_oslomsg_notify_use_ssl - added "
"barbican_oslomsg_notify_userid - added barbican_oslomsg_notify_vhost - added "
"barbican_oslomsg_notify_password"
msgstr ""
"Parameter server rabbitmq telah digantikan oleh parameter oslo.messaging RPC "
"dan Notify  untuk abstrak layanan pesan dari deployment server backend yang "
"sebenarnya. - barbican_oslomsg_rpc_servers menggantikan rabbitmq_servers - "
"barbican_oslomsg_rpc_port menggantikan rabbitmq_port - "
"barbican_oslomsg_rpc_userid menggantikan barbican_rabbitmq_userid - "
"barbican_oslomsg_rpc_vhost menggantikan barbican_rabbitmq_vhost - "
"ditambahkan barbican_oslomsg_rpc_use_ssl - ditambahkan "
"barbican_oslomsg_notify_servers - ditambahkan barbican_oslomsg_notify_port - "
"ditambahkan barbican_oslomsg_notify_use_ssl - ditambahkan "
"barbican_oslomsg_notify_userid - ditambahkan barbican_oslomsg_notify_vhost - "
"ditambahkan barbican_oslomsg_notify_password"

msgid ""
"The rabbitmq server parameters have been replaced by corresponding oslo."
"messaging RPC and Notify parameters in order to abstract the messaging "
"service from the actual backend server deployment. - "
"ceilometer_oslomsg_rpc_servers replaces rabbitmq_servers - "
"ceilometer_oslomsg_rpc_port replaces rabbitmq_port - "
"ceilometer_oslomsg_rpc_userid replaces ceilometer_rabbitmq_userid - "
"ceilometer_oslomsg_rpc_vhost replaces ceilometer_rabbitmq_vhost - added "
"ceilometer_oslomsg_rpc_use_ssl - added ceilometer_oslomsg_notify_servers - "
"added ceilometer_oslomsg_notify_port - added "
"ceilometer_oslomsg_notify_use_ssl - added ceilometer_oslomsg_notify_userid - "
"added ceilometer_oslomsg_notify_vhost - added "
"ceilometer_oslomsg_notify_password"
msgstr ""
"Parameter server rabbitmq telah digantikan oleh parameter oslo.messaging RPC "
"dan Beritahu untuk abstrak layanan pesan dari deployment server backend yang "
"sebenarnya. - ceilometer_oslomsg_rpc_servers menggantikan rabbitmq_servers - "
"ceilometer_oslomsg_rpc_port menggantikan rabbitmq_port - "
"ceilometer_oslomsg_rpc_userid menggantikan ceilometer_rabbitmq_userid - "
"ceilometer_oslomsg_rpc_vhost menggantikan ceilometer_rabbitmq_vhost - "
"menambahkan ceilometer_oslomsg_rpc_use_ssl - menambahkan "
"ceilometer_oslomsg_notify_servers - menambahkan "
"ceilometer_oslomsg_notify_port - menambahkan "
"ceilometer_oslomsg_notify_use_ssl - menambahkan "
"ceilometer_oslomsg_notify_userid - menambahkan "
"ceilometer_oslomsg_notify_vhost - menambahkan "
"ceilometer_oslomsg_notify_password"

msgid ""
"The rabbitmq server parameters have been replaced by corresponding oslo."
"messaging RPC and Notify parameters in order to abstract the messaging "
"service from the actual backend server deployment. - "
"cinder_oslomsg_rpc_servers replaces cinder_rabbitmq_servers - "
"cinder_oslomsg_rpc_port replaces cinder_rabbitmq_port - "
"cinder_oslomsg_rpc_use_ssl replaces cinder_rabbitmq_use_ssl - "
"cinder_oslomsg_rpc_userid replaces cinder_rabbitmq_userid - "
"cinder_oslomsg_rpc_vhost replaces cinder_rabbitmq_vhost - "
"cinder_oslomsg_notify_servers replaces cinder_rabbitmq_telemetry_servers - "
"cinder_oslomsg_notify_port replaces cinder_rabbitmq_telemetry_port - "
"cinder_oslomsg_notify_use_ssl replaces cinder_rabbitmq_telemetry_use_ssl - "
"cinder_oslomsg_notify_userid replaces cinder_rabbitmq_telemetry_userid - "
"cinder_oslomsg_notify_vhost replaces cinder_rabbitmq_telemetry_vhost"
msgstr ""
"Parameter server rabbitmq telah digantikan oleh parameter oslo.messaging RPC "
"dan Notify untuk abstrak layanan pesan dari deployment server backend yang "
"sebenarnya. - cinder_oslomsg_rpc_servers menggantikan "
"cinder_rabbitmq_servers - cinder_oslomsg_rpc_port menggantikan "
"cinder_rabbitmq_port - cinder_oslomsg_rpc_use_ssl menggantikan "
"cinder_rabbitmq_use_ssl - cinder_oslomsg_rpc_userid menggantikan "
"cinder_rabbitmq_userid - cinder_oslomsg_rpc_vhost menggantikan "
"cinder_rabbitmq_vhost - cinder_oslomsg_notify_servers menggantikan "
"cinder_rabbitmq_telemetry_servers - cinder_oslomsg_notify_port menggantikan "
"cinder_rabbitmq_telemetry_port - cinder_oslomsg_notify_use_ssl menggantikan "
"cinder_rabbitmq_telemetry_use_ssl - cinder_oslomsg_notify_userid "
"menggantikan cinder_rabbitmq_telemetry_userid - cinder_oslomsg_notify_vhost "
"menggantikan cinder_rabbitmq_telemetry_vhost"

msgid ""
"The rabbitmq server parameters have been replaced by corresponding oslo."
"messaging RPC and Notify parameters in order to abstract the messaging "
"service from the actual backend server deployment. - "
"cloudkitty_oslomsg_rpc_servers replaces rabbitmq_servers - "
"cloudkitty_oslomsg_rpc_port replaces rabbitmq_port - "
"cloudkitty_oslomsg_rpc_userid replaces rabbitmq_userid - "
"cloudkitty_oslomsg_rpc_vhost replaces rabbitmq_vhost - "
"cloudkitty_oslomsg_rpc_use_ssl replaces rabbitmq_use_ssl - added "
"cloudkitty_oslomsg_notify_servers - added cloudkitty_oslomsg_notify_port - "
"added cloudkitty_oslomsg_notify_use_ssl - added "
"cloudkitty_oslomsg_notify_userid - added cloudkitty_oslomsg_notify_vhost"
msgstr ""
"Parameter server rabbitmq telah digantikan oleh oslo.messaging RPC dan "
"Notify parameter yang sesuai untuk abstrak layanan pesan dari penyebaran "
"server backend yang sebenarnya. \n"
"- cloudkitty_oslomsg_rpc_servers menggantikan rabbitmq_servers  \n"
"- cloudkitty_oslomsg_rpc_port menggantikan rabbitmq_port \n"
"- cloudkitty_oslomsg_rpc_userid menggantikan rabbitmq_userid \n"
"- cloudkitty_oslomsg_rpc_vhost menggantikan rabbitmq_vhost \n"
"- cloudkitty_oslomsg_rpc_use_ssl menggantikan rabbitmq_use_ssl \n"
"- menambahkan cloudkitty_oslomsg_notify_servers \n"
"- menambahkan cloudkitty_oslomsg_notify_port \n"
"- menambahkan cloudkitty_oslomsg_notify_use_ssl \n"
"- menambahkan cloudkitty_oslomsg_notify_userid \n"
"- tambah cloudkitty_oslomsg_notify_vhost"

msgid ""
"The rabbitmq server parameters have been replaced by corresponding oslo."
"messaging RPC and Notify parameters in order to abstract the messaging "
"service from the actual backend server deployment. - "
"designate_oslomsg_rpc_servers replaces designate_rabbitmq_servers - "
"designate_oslomsg_rpc_port replaces designate_rabbitmq_port - "
"designate_oslomsg_rpc_use_ssl replaces designate_rabbitmq_use_ssl - "
"designate_oslomsg_rpc_userid replaces designate_rabbitmq_userid - "
"designate_oslomsg_rpc_vhost replaces designate_rabbitmq_vhost - "
"designate_oslomsg_notify_servers replaces "
"designate_rabbitmq_telemetry_servers - designate_oslomsg_notify_port "
"replaces designate_rabbitmq_telemetry_port - "
"designate_oslomsg_notify_use_ssl replaces "
"designate_rabbitmq_telemetry_use_ssl - designate_oslomsg_notify_userid "
"replaces designate_rabbitmq_telemetry_userid - "
"designate_oslomsg_notify_vhost replaces designate_rabbitmq_telemetry_vhost - "
"designate_oslomsg_notify_password replaces "
"designate_rabbitmq_telemetry_password"
msgstr ""
"Parameter server rabbitmq telah digantikan oleh parameter oslo.messaging RPC "
"dan Notify untuk abstrak layanan pesan dari deployment server backend yang "
"sebenarnya. - designate_oslomsg_rpc_servers menggantikan "
"designate_rabbitmq_servers - designate_oslomsg_rpc_port menggantikan "
"designate_rabbitmq_port - designate_oslomsg_rpc_use_ssl menggantikan "
"designate_rabbitmq_use_ssl - designate_oslomsg_rpc_userid menggantikan "
"designate_rabbitmq_userid - designate_oslomsg_rpc_vhost menggantikan "
"designate_rabbitmq_vhost - designate_oslomsg_notify_servers menggantikan "
"designate_rabbitmq_telemetry_servers - designate_oslomsg_notify_port "
"menggantikan designate_rabbitmq_telemetry_port - "
"designate_oslomsg_notify_use_ssl menggantikan "
"designate_rabbitmq_telemetry_use_ssl - designate_oslomsg_notify_userid "
"menggantikan designate_rabbitmq_telemetry_userid - "
"designate_oslomsg_notify_vhost menggantikan "
"designate_rabbitmq_telemetry_vhost - designate_oslomsg_notify_password "
"menggantikan designate_rabbitmq_telemetry_password"

msgid ""
"The rabbitmq server parameters have been replaced by corresponding oslo."
"messaging RPC and Notify parameters in order to abstract the messaging "
"service from the actual backend server deployment. - "
"glance_oslomsg_rpc_servers replaces glance_rabbitmq_servers - "
"glance_oslomsg_rpc_port replaces glance_rabbitmq_port - "
"glance_oslomsg_rpc_use_ssl replaces glance_rabbitmq_use_ssl - "
"glance_oslomsg_rpc_userid replaces glance_rabbitmq_userid - "
"glance_oslomsg_rpc_vhost replaces glance_rabbitmq_vhost - "
"glance_oslomsg_notify_servers replaces glance_rabbitmq_telemetry_servers - "
"glance_oslomsg_notify_port replaces glance_rabbitmq_telemetry_port - "
"glance_oslomsg_notify_use_ssl replaces glance_rabbitmq_telemetry_use_ssl - "
"glance_oslomsg_notify_userid replaces glance_rabbitmq_telemetry_userid - "
"glance_oslomsg_notify_vhost replaces glance_rabbitmq_telemetry_vhost - "
"glance_oslomsg_notify_password replaces glance_rabbitmq_telemetry_password"
msgstr ""
"Parameter server rabbitmq telah digantikan oleh parameter oslo.messaging RPC "
"dan Notify untuk abstrak layanan pesan dari deployment server backend yang "
"sebenarnya. - glance_oslomsg_rpc_servers menggantikan "
"glance_rabbitmq_servers - glance_oslomsg_rpc_port menggantikan "
"glance_rabbitmq_port - glance_oslomsg_rpc_use_ssl menggantikan "
"glance_rabbitmq_use_ssl - glance_oslomsg_rpc_userid menggantikan "
"glance_rabbitmq_userid - glance_oslomsg_rpc_vhost menggantikan "
"glance_rabbitmq_vhost - glance_oslomsg_notify_servers menggantikan "
"glance_rabbitmq_telemetry_servers - glance_oslomsg_notify_port menggantikan "
"glance_rabbitmq_telemetry_port - glance_oslomsg_notify_use_ssl menggantikan "
"glance_rabbitmq_telemetry_use_ssl - glance_oslomsg_notify_userid "
"menggantikan glance_rabbitmq_telemetry_userid - glance_oslomsg_notify_vhost "
"menggantikan glance_rabbitmq_telemetry_vhost - "
"glance_oslomsg_notify_password menggantikan "
"glance_rabbitmq_telemetry_password"

msgid ""
"The rabbitmq server parameters have been replaced by corresponding oslo."
"messaging RPC and Notify parameters in order to abstract the messaging "
"service from the actual backend server deployment. - "
"heat_oslomsg_rpc_servers replaces heat_rabbitmq_servers - "
"heat_oslomsg_rpc_port replaces heat_rabbitmq_port - heat_oslomsg_rpc_use_ssl "
"replaces heat_rabbitmq_use_ssl - heat_oslomsg_rpc_userid replaces "
"heat_rabbitmq_userid - heat_oslomsg_rpc_vhost replaces heat_rabbitmq_vhost - "
"heat_oslomsg_rpc_password replaces heat_rabbitmq_password - "
"heat_oslomsg_notify_servers replaces heat_rabbitmq_telemetry_servers - "
"heat_oslomsg_notify_port replaces heat_rabbitmq_telemetry_port - "
"heat_oslomsg_notify_use_ssl replaces heat_rabbitmq_telemetry_use_ssl - "
"heat_oslomsg_notify_userid replaces heat_rabbitmq_telemetry_userid - "
"heat_oslomsg_notify_vhost replaces heat_rabbitmq_telemetry_vhost - "
"heat_oslomsg_notify_password replaces heat_rabbitmq_telemetry_password"
msgstr ""
"Parameter server rabbitmq telah digantikan oleh parameter oslo.messaging RPC "
"dan Notify  untuk abstrak layanan pesan dari deployment server backend yang "
"sebenarnya. - heat_oslomsg_rpc_servers menggantikan heat_rabbitmq_servers - "
"heat_oslomsg_rpc_port menggantikan heat_rabbitmq_port - "
"heat_oslomsg_rpc_use_ssl menggantikan heat_rabbitmq_use_ssl - "
"heat_oslomsg_rpc_userid menggantikan heat_rabbitmq_userid - "
"heat_oslomsg_rpc_vhost menggantikan heat_rabbitmq_vhost - "
"heat_oslomsg_rpc_password menggantikan heat_rabbitmq_password - "
"heat_oslomsg_notify_servers menggantikan heat_rabbitmq_telemetry_servers - "
"heat_oslomsg_notify_port menggantikan heat_rabbitmq_telemetry_port - "
"heat_oslomsg_notify_use_ssl menggantikan heat_rabbitmq_telemetry_use_ssl - "
"heat_oslomsg_notify_userid menggantikan heat_rabbitmq_telemetry_userid - "
"heat_oslomsg_notify_vhost menggantikan heat_rabbitmq_telemetry_vhost - "
"heat_oslomsg_notify_password menggantikan heat_rabbitmq_telemetry_password"

msgid ""
"The rabbitmq server parameters have been replaced by corresponding oslo."
"messaging RPC and Notify parameters in order to abstract the messaging "
"service from the actual backend server deployment. - "
"ironic_oslomsg_rpc_servers replaces ironic_rabbitmq_servers - "
"ironic_oslomsg_rpc_port replaces ironic_rabbitmq_port - "
"ironic_oslomsg_rpc_use_ssl replaces ironic_rabbitmq_use_ssl - "
"ironic_oslomsg_rpc_userid replaces ironic_rabbitmq_userid - "
"ironic_oslomsg_rpc_vhost replaces ironic_rabbitmq_vhost"
msgstr ""
"Parameter server rabbitmq telah digantikan oleh parameter oslo.messaging RPC "
"dan Notify  untuk abstrak layanan pesan dari deployment server backend yang "
"sebenarnya. - ironic_oslomsg_rpc_servers menggantikan "
"ironic_rabbitmq_servers - ironic_oslomsg_rpc_port menggantikan "
"ironic_rabbitmq_port - ironic_oslomsg_rpc_use_ssl menggantikan "
"ironic_rabbitmq_use_ssl - ironic_oslomsg_rpc_userid menggantikan "
"ironic_rabbitmq_userid - ironic_oslomsg_rpc_vhost menggantikan "
"ironic_rabbitmq_vhost"

msgid ""
"The rabbitmq server parameters have been replaced by corresponding oslo."
"messaging RPC and Notify parameters in order to abstract the messaging "
"service from the actual backend server deployment. - "
"keystone_oslomsg_rpc_servers replaces keystone_rabbitmq_servers - "
"keystone_oslomsg_rpc_port replaces keystone_rabbitmq_port - "
"keystone_oslomsg_rpc_use_ssl replaces keystone_rabbitmq_use_ssl - "
"keystone_oslomsg_rpc_userid replaces keystone_rabbitmq_userid - "
"keystone_oslomsg_rpc_vhost replaces keystone_rabbitmq_vhost - "
"keystone_oslomsg_notify_servers replaces keystone_rabbitmq_telemetry_servers "
"- keystone_oslomsg_notify_port replaces keystone_rabbitmq_telemetry_port - "
"keystone_oslomsg_notify_use_ssl replaces keystone_rabbitmq_telemetry_use_ssl "
"- keystone_oslomsg_notify_userid replaces keystone_rabbitmq_telemetry_userid "
"- keystone_oslomsg_notify_vhost replaces keystone_rabbitmq_telemetry_vhost"
msgstr ""
"Parameter server rabbitmq telah digantikan oleh parameter oslo.messaging RPC "
"dan Notify  untuk abstrak layanan pesan dari deployment server backend yang "
"sebenarnya. - keystone_oslomsg_rpc_servers menggantikan "
"keystone_rabbitmq_servers - keystone_oslomsg_rpc_port menggantikan "
"keystone_rabbitmq_port - keystone_oslomsg_rpc_use_ssl menggantikan "
"keystone_rabbitmq_use_ssl - keystone_oslomsg_rpc_userid menggantikan "
"keystone_rabbitmq_userid - keystone_oslomsg_rpc_vhost menggantikan "
"keystone_rabbitmq_vhost - keystone_oslomsg_notify_servers menggantikan "
"keystone_rabbitmq_telemetry_servers - keystone_oslomsg_notify_port "
"menggantikan keystone_rabbitmq_telemetry_port - "
"keystone_oslomsg_notify_use_ssl menggantikan "
"keystone_rabbitmq_telemetry_use_ssl - keystone_oslomsg_notify_userid "
"menggantikan keystone_rabbitmq_telemetry_userid - "
"keystone_oslomsg_notify_vhost menggantikan keystone_rabbitmq_telemetry_vhost"

msgid ""
"The rabbitmq server parameters have been replaced by corresponding oslo."
"messaging RPC and Notify parameters in order to abstract the messaging "
"service from the actual backend server deployment. - "
"magnum_oslomsg_rpc_servers replaces rabbitmq_servers - "
"magnum_oslomsg_rpc_port replaces rabbitmq_port - magnum_oslomsg_rpc_userid "
"replaces magnum_rabbitmq_userid - magnum_oslomsg_rpc_vhost replaces "
"magnum_rabbitmq_vhost - added magnum_oslomsg_rpc_use_ssl - added "
"magnum_oslomsg_notify_servers - added magnum_oslomsg_notify_port - added "
"magnum_oslomsg_notify_use_ssl - added magnum_oslomsg_notify_userid - added "
"magnum_oslomsg_notify_vhost - added magnum_oslomsg_notify_password"
msgstr ""
"Parameter server rabbitmq telah digantikan oleh parameter oslo.messaging RPC "
"dan Notify  untuk abstrak layanan pesan dari deployment server backend yang "
"sebenarnya. - magnum_oslomsg_rpc_servers menggantikan rabbitmq_servers - "
"magnum_oslomsg_rpc_port menggantikan rabbitmq_port - "
"magnum_oslomsg_rpc_userid menggantikan magnum_rabbitmq_userid - "
"magnum_oslomsg_rpc_vhost menggantikan magnum_rabbitmq_vhost - menambahkan "
"magnum_oslomsg_rpc_use_ssl - menambahkan magnum_oslomsg_notify_servers - "
"menambahkan magnum_oslomsg_notify_port - menambahkan "
"magnum_oslomsg_notify_use_ssl - menambahkan magnum_oslomsg_notify_userid - "
"menambahkan magnum_oslomsg_notify_vhost - menambahkan "
"magnum_oslomsg_notify_password"

msgid ""
"The rabbitmq server parameters have been replaced by corresponding oslo."
"messaging RPC and Notify parameters in order to abstract the messaging "
"service from the actual backend server deployment. - "
"neutron_oslomsg_rpc_servers replaces neutron_rabbitmq_servers - "
"neutron_oslomsg_rpc_port replaces neutron_rabbitmq_port - "
"neutron_oslomsg_rpc_use_ssl replaces neutron_rabbitmq_use_ssl - "
"neutron_oslomsg_rpc_userid replaces neutron_rabbitmq_userid - "
"neutron_oslomsg_rpc_vhost replaces neutron_rabbitmq_vhost - "
"neutron_oslomsg_notify_servers replaces neutron_rabbitmq_telemetry_servers - "
"neutron_oslomsg_notify_port replaces neutron_rabbitmq_telemetry_port - "
"neutron_oslomsg_notify_use_ssl replaces neutron_rabbitmq_telemetry_use_ssl - "
"neutron_oslomsg_notify_userid replaces neutron_rabbitmq_telemetry_userid - "
"neutron_oslomsg_notify_vhost replaces neutron_rabbitmq_telemetry_vhost"
msgstr ""
"Parameter server rabbitmq telah digantikan oleh parameter oslo.messaging RPC "
"dan Notify  untuk abstrak layanan pesan dari deployment server backend yang "
"sebenarnya. - neutron_oslomsg_rpc_servers menggantikan "
"neutron_rabbitmq_servers - neutron_oslomsg_rpc_port menggantikan "
"neutron_rabbitmq_port - neutron_oslomsg_rpc_use_ssl menggantikan "
"neutron_rabbitmq_use_ssl - neutron_oslomsg_rpc_userid menggantikan "
"neutron_rabbitmq_userid - neutron_oslomsg_rpc_vhost menggantikan "
"neutron_rabbitmq_vhost - neutron_oslomsg_notify_servers menggantikan "
"neutron_rabbitmq_telemetry_servers - neutron_oslomsg_notify_port "
"menggantikan neutron_rabbitmq_telemetry_port - "
"neutron_oslomsg_notify_use_ssl menggantikan "
"neutron_rabbitmq_telemetry_use_ssl - neutron_oslomsg_notify_userid "
"menggantikan neutron_rabbitmq_telemetry_userid - "
"neutron_oslomsg_notify_vhost menggantikan neutron_rabbitmq_telemetry_vhost"

msgid ""
"The rabbitmq server parameters have been replaced by corresponding oslo."
"messaging RPC and Notify parameters in order to abstract the messaging "
"service from the actual backend server deployment. - "
"nova_oslomsg_rpc_servers replaces nova_rabbitmq_servers - "
"nova_oslomsg_rpc_port replaces nova_rabbitmq_port - nova_oslomsg_rpc_use_ssl "
"replaces nova_rabbitmq_use_ssl - nova_oslomsg_rpc_userid replaces "
"nova_rabbitmq_userid - nova_oslomsg_rpc_vhost replaces nova_rabbitmq_vhost - "
"nova_oslomsg_notify_servers replaces nova_rabbitmq_telemetry_servers - "
"nova_oslomsg_notify_port replaces nova_rabbitmq_telemetry_port - "
"nova_oslomsg_notify_use_ssl replaces nova_rabbitmq_telemetry_use_ssl - "
"nova_oslomsg_notify_userid replaces nova_rabbitmq_telemetry_userid - "
"nova_oslomsg_notify_vhost replaces nova_rabbitmq_telemetry_vhost - "
"nova_oslomsg_notify_password replaces nova_rabbitmq_telemetry_password"
msgstr ""
"Parameter server rabbitmq telah digantikan oleh parameter oslo.messaging RPC "
"dan Notify  untuk abstrak layanan pesan dari deployment server backend yang "
"sebenarnya. - nova_oslomsg_rpc_servers menggantikan nova_rabbitmq_servers - "
"nova_oslomsg_rpc_port menggantikan nova_rabbitmq_port - "
"nova_oslomsg_rpc_use_ssl menggantikan nova_rabbitmq_use_ssl - "
"nova_oslomsg_rpc_userid menggantikan nova_rabbitmq_userid - "
"nova_oslomsg_rpc_vhost menggantikan nova_rabbitmq_vhost - "
"nova_oslomsg_notify_servers menggantikan nova_rabbitmq_telemetry_servers - "
"nova_oslomsg_notify_port menggantikan nova_rabbitmq_telemetry_port - "
"nova_oslomsg_notify_use_ssl menggantikan nova_rabbitmq_telemetry_use_ssl - "
"nova_oslomsg_notify_userid menggantikan nova_rabbitmq_telemetry_userid - "
"nova_oslomsg_notify_vhost menggantikan nova_rabbitmq_telemetry_vhost - "
"nova_oslomsg_notify_password menggantikan nova_rabbitmq_telemetry_password"

msgid ""
"The rabbitmq server parameters have been replaced by corresponding oslo."
"messaging RPC and Notify parameters in order to abstract the messaging "
"service from the actual backend server deployment. - "
"octavia_oslomsg_rpc_servers replaces octavia_rabbitmq_servers - "
"octavia_oslomsg_rpc_port replaces octavia_rabbitmq_port - "
"octavia_oslomsg_rpc_use_ssl replaces octavia_rabbitmq_use_ssl - "
"octavia_oslomsg_rpc_userid replaces octavia_rabbitmq_userid - "
"octavia_oslomsg_rpc_vhost replaces octavia_rabbitmq_vhost - "
"octavia_oslomsg_notify_servers replaces octavia_rabbitmq_telemetry_servers - "
"octavia_oslomsg_notify_port replaces octavia_rabbitmq_telemetry_port - "
"octavia_oslomsg_notify_use_ssl replaces octavia_rabbitmq_telemetry_use_ssl - "
"octavia_oslomsg_notify_userid replaces octavia_rabbitmq_telemetry_userid - "
"octavia_oslomsg_notify_vhost replaces octavia_rabbitmq_telemetry_vhost - "
"octavia_oslomsg_notify_password replaces octavia_rabbitmq_telemetry_password"
msgstr ""
"Parameter server rabbitmq telah digantikan oleh parameter oslo.messaging RPC "
"dan Notify  untuk abstrak layanan pesan dari deployment server backend yang "
"sebenarnya. - octavia_oslomsg_rpc_servers menggantikan "
"octavia_rabbitmq_servers - octavia_oslomsg_rpc_port menggantikan "
"octavia_rabbitmq_port - octavia_oslomsg_rpc_use_ssl menggantikan "
"octavia_rabbitmq_use_ssl - octavia_oslomsg_rpc_userid menggantikan "
"octavia_rabbitmq_userid - octavia_oslomsg_rpc_vhost menggantikan "
"octavia_rabbitmq_vhost - octavia_oslomsg_notify_servers menggantikan "
"octavia_rabbitmq_telemetry_servers - octavia_oslomsg_notify_port "
"menggantikan octavia_rabbitmq_telemetry_port - "
"octavia_oslomsg_notify_use_ssl menggantikan "
"octavia_rabbitmq_telemetry_use_ssl - octavia_oslomsg_notify_userid "
"menggantikan octavia_rabbitmq_telemetry_userid - "
"octavia_oslomsg_notify_vhost menggantikan octavia_rabbitmq_telemetry_vhost - "
"octavia_oslomsg_notify_password menggantikan "
"octavia_rabbitmq_telemetry_password"

msgid ""
"The rabbitmq server parameters have been replaced by corresponding oslo."
"messaging RPC and Notify parameters in order to abstract the messaging "
"service from the actual backend server deployment. - "
"sahara_oslomsg_rpc_servers replaces sahara_rabbitmq_servers - "
"sahara_oslomsg_rpc_port replaces sahara_rabbitmq_port - "
"sahara_oslomsg_rpc_use_ssl replaces sahara_rabbitmq_use_ssl - "
"sahara_oslomsg_rpc_userid replaces sahara_rabbitmq_userid - "
"sahara_oslomsg_rpc_vhost replaces sahara_rabbitmq_vhost - "
"sahara_oslomsg_notify_servers replaces sahara_rabbitmq_telemetry_servers - "
"sahara_oslomsg_notify_port replaces sahara_rabbitmq_telemetry_port - "
"sahara_oslomsg_notify_use_ssl replaces sahara_rabbitmq_telemetry_use_ssl - "
"sahara_oslomsg_notify_userid replaces sahara_rabbitmq_telemetry_userid - "
"sahara_oslomsg_notify_vhost replaces sahara_rabbitmq_telemetry_vhost"
msgstr ""
"Parameter server rabbitmq telah digantikan oleh parameter oslo.messaging RPC "
"dan Notify  untuk abstrak layanan pesan dari deployment server backend yang "
"sebenarnya. - sahara_oslomsg_rpc_servers menggantikan "
"sahara_rabbitmq_servers - sahara_oslomsg_rpc_port menggantikan "
"sahara_rabbitmq_port - sahara_oslomsg_rpc_use_ssl menggantikan "
"sahara_rabbitmq_use_ssl - sahara_oslomsg_rpc_userid menggantikan "
"sahara_rabbitmq_userid - sahara_oslomsg_rpc_vhost menggantikan "
"sahara_rabbitmq_vhost - sahara_oslomsg_notify_servers menggantikan "
"sahara_rabbitmq_telemetry_servers - sahara_oslomsg_notify_port menggantikan "
"sahara_rabbitmq_telemetry_port - sahara_oslomsg_notify_use_ssl menggantikan "
"sahara_rabbitmq_telemetry_use_ssl - sahara_oslomsg_notify_userid "
"menggantikan sahara_rabbitmq_telemetry_userid - sahara_oslomsg_notify_vhost "
"menggantikan sahara_rabbitmq_telemetry_vhost"

msgid ""
"The rabbitmq server parameters have been replaced by corresponding oslo."
"messaging RPC and Notify parameters in order to abstract the messaging "
"service from the actual backend server deployment. - "
"trove_oslomsg_rpc_servers replaces trove_rabbitmq_servers - "
"trove_oslomsg_rpc_port replaces trove_rabbitmq_port - "
"trove_oslomsg_rpc_use_ssl replaces trove_rabbitmq_use_ssl - "
"trove_oslomsg_rpc_userid replaces trove_rabbitmq_userid - "
"trove_oslomsg_rpc_vhost replaces trove_rabbitmq_vhost - added "
"trove_oslomsg_notify_servers - added trove_oslomsg_notify_port - added "
"trove_oslomsg_notify_use_ssl - added trove_oslomsg_notify_userid - added "
"trove_oslomsg_notify_vhost - added trove_oslomsg_notify_password"
msgstr ""
"Parameter server rabbitmq telah digantikan oleh parameter oslo.messaging RPC "
"dan Notify  untuk abstrak layanan pesan dari deployment server backend yang "
"sebenarnya. - trove_oslomsg_rpc_servers menggantikan trove_rabbitmq_servers "
"- trove_oslomsg_rpc_port menggantikan trove_rabbitmq_port - "
"trove_oslomsg_rpc_use_ssl menggantikan trove_rabbitmq_use_ssl - "
"trove_oslomsg_rpc_userid menggantikan trove_rabbitmq_userid - "
"trove_oslomsg_rpc_vhost menggantikan trove_rabbitmq_vhost - menambahkan "
"trove_oslomsg_notify_servers - menambahkan trove_oslomsg_notify_port - "
"menambahkan trove_oslomsg_notify_use_ssl - menambahkan "
"trove_oslomsg_notify_userid - menambahkan trove_oslomsg_notify_vhost - "
"menambahkan trove_oslomsg_notify_password"

msgid ""
"The rabbitmq_server role always checks whether the latest package is "
"installed when executed. If a deployer wishes to change the check to only "
"validate the presence of the package, the option ``rabbitmq_package_state`` "
"should be set to ``present``."
msgstr ""
"Peran rabbitmq_server selalu memeriksa apakah paket terbaru diinstal ketika "
"dijalankan. Jika seorang deployer ingin mengubah tanda centang untuk hanya "
"memvalidasi keberadaan paket, opsi ``rabbitmq_package_state`` harus diatur "
"ke ``present``."

msgid ""
"The rabbitmq_server role now supports the ability to configure whether apt/"
"yum tasks install the latest available package, or just ensure that the "
"package is present. The default action is to ensure that the latest package "
"is present. The action taken may be changed to only ensure that the package "
"is present by setting ``rabbitmq_package_state`` to ``present``."
msgstr ""
"Peran rabbitmq_server sekarang mendukung kemampuan untuk mengonfigurasi "
"apakah tugas apt/yum menginstal paket terbaru yang tersedia, atau hanya "
"memastikan bahwa paket tersebut ada. Tindakan default adalah untuk "
"memastikan bahwa paket terbaru hadir. Tindakan yang diambil dapat diubah "
"hanya untuk memastikan bahwa paket hadir dengan mengatur "
"``rabbitmq_package_state`` ke ``present``."

msgid ""
"The repo build process is now able to make use of a pre-staged git cache. If "
"the ``/var/www/repo/openstackgit`` folder on the repo server is found to "
"contain existing git clones then they will be updated if they do not already "
"contain the required SHA for the build."
msgstr ""
"Proses repo build sekarang dapat menggunakan cache git yang sudah diprogram "
"sebelumnya. Jika folder ``/var/www/repo/openstackgit`` pada server repo "
"ditemukan mengandung klon git yang ada maka mereka akan diperbarui jika "
"mereka belum mengandung SHA yang diperlukan untuk build."

msgid ""
"The repo build process is now able to support building and synchronizing "
"artifacts for multiple CPU architectures. Build artifacts are now tagged "
"with the appropriate CPU architecture by default, and synchronization of "
"build artifacts from secondary, architecture-specific repo servers back to "
"the primary repo server is supported."
msgstr ""
"Proses repo build sekarang dapat mendukung building dan synchronizing "
"artefak untuk beberapa arsitektur CPU. Artefak build sekarang ditandai "
"dengan arsitektur CPU yang sesuai secara default, dan sinkronisasi artefak "
"build dari sekunder, server repo spesifik arsitektur kembali ke server repo "
"primer didukung."

msgid ""
"The repo build process is now able to synchronize a git cache from the "
"deployment node to the repo server. The git cache path on the deployment "
"node is set using the variable ``repo_build_git_cache``. If the deployment "
"node hosts the repo container, then the folder will be symlinked into the "
"bind mount for the repo container. If the deployment node does not host the "
"repo container, then the contents of the folder will be synchronised into "
"the repo container."
msgstr ""
"Proses repo build sekarang dapat menyinkronkan git cache dari deployment "
"node ke server repo. Path git cache pada node deployment diatur menggunakan "
"variabel ``repo_build_git_cache``. Jika deployment node menjadi host "
"kontainer repo, maka folder akan disinkronkan ke bind mount untuk kontainer "
"repo. Jika deployment node tidak menjadi host kontainer repo, maka isi "
"folder akan disinkronkan ke kontainer repo."

msgid ""
"The repo build process no longer builds packaged venvs. Instead, the venvs "
"are created on the target hosts as the install process for each service "
"needs to. This opens up the opportunity for roles to be capable of creating "
"multiple venvs, and for any role to create venvs - neither of these options "
"were possible in previous releases."
msgstr ""
"Proses repo build tidak lagi membangun venvs paket. Sebagai gantinya, venvs "
"dibuat pada host target sebagaimana proses instalasi untuk setiap layanan "
"perlu. Ini membuka peluang bagi peran untuk dapat membuat banyak venvs, dan "
"peran apa pun untuk membuat venvs - tidak satu pun dari opsi ini yang "
"dimungkinkan dalam rilis sebelumnya."

msgid ""
"The repo build process now has the ability to store the pip sources within "
"the build archive. This ability is useful when deploying environments that "
"are \"multi-architecture\", \"multi-distro\", or \"multi-interpreter\" where "
"specific pre-build wheels may not be enough to support all of the "
"deployment. To enable the ability to store the python source code within a "
"given release, set the new option ``repo_build_store_pip_sources`` to "
"``true``."
msgstr ""
"Proses repo build sekarang memiliki kemampuan untuk menyimpan sumber pip "
"dalam arsip build. Kemampuan ini berguna ketika deploying lingkungan yang "
"\"multi-architecture\", \"multi-distro\", atau \"multi-interpreter\" di mana "
"wheels pre-build spesifik mungkin tidak cukup untuk mendukung semua "
"deployment. Untuk mengaktifkan kemampuan untuk menyimpan kode sumber python "
"dalam rilis yang diberikan, setel opsi baru ``repo_build_store_pip_sources`` "
"ke ``true``."

msgid ""
"The repo build process now only has the following tags, providing a clear "
"path for each deliverable. The tag ``repo-build-install`` completes the "
"installation of required packages. The tag ``repo-build-wheels`` completes "
"the wheel build process. The tag ``repo-build-venvs`` completes the venv "
"build process. Finally, the tag ``repo-build-index`` completes the manifest "
"preparation and indexing of the os-releases and links folders."
msgstr ""
"Proses repo build sekarang hanya memiliki tag berikut, memberikan path yang "
"jelas untuk setiap pengiriman. Tag ``repo-build-install`` menyelesaikan "
"instalasi paket yang diperlukan. Tag ``repo-build-wheels`` melengkapi proses "
"wheel build. Tag ``repo-build-venvs`` melengkapi proses venv build. "
"Akhirnya, tag ``repo-build-index`` melengkapi persiapan manifest dan "
"pengindeksan folder os-release dan tautan."

msgid ""
"The repo build process now selectively builds python packages based on "
"whether each OpenStack service group has any hosts in it. If there are no "
"hosts in the group, the list of python packages for the service will not be "
"built. This behaviour can be optionally changed to force all python packages "
"to be built by setting ``repo_build_wheel_selective`` to ``no``."
msgstr ""
"Proses repo build sekarang secara selektif membangun paket python "
"berdasarkan apakah setiap grup layanan OpenStack memiliki host di dalamnya. "
"Jika tidak ada host di grup, daftar paket python untuk layanan tidak akan "
"dibangun. Perilaku ini secara opsional dapat diubah untuk memaksa semua "
"paket python dibangun dengan mengatur ``repo_build_wheel_selective`` ke "
"``no``."

msgid ""
"The repo build process now selectively builds venvs based on whether each "
"OpenStack service group has any hosts in it. If there are no hosts in the "
"group, the venv will not be built. This behaviour can be optionally changed "
"to force all venvs to be built by setting ``repo_build_venv_selective`` to "
"``yes``."
msgstr ""
"Proses repo build sekarang secara selektif membangun venv berdasarkan apakah "
"masing-masing grup layanan OpenStack memiliki host di dalamnya. Jika tidak "
"ada host di grup, venv tidak akan dibangun. Perilaku ini secara opsional "
"dapat diubah untuk memaksa semua venvs untuk dibangun dengan mengatur "
"``repo_build_venv_selective`` ke ``yes``."

msgid ""
"The repo build process now selectively clones git repositories based on "
"whether each OpenStack service group has any hosts in it. If there are no "
"hosts in the group, the git repo for the service will not be cloned. This "
"behaviour can be optionally changed to force all git repositories to be "
"cloned by setting ``repo_build_git_selective`` to ``no``."
msgstr ""
"Proses repo build sekarang secara selektif mengkloning git repositori "
"berdasarkan apakah setiap grup layanan OpenStack memiliki host di dalamnya. "
"Jika tidak ada host di grup, repo git untuk layanan tidak akan dikloning. "
"Perilaku ini secara opsional dapat diubah untuk memaksa semua repositori git "
"untuk dikloning dengan menetapkan ``repo_build_git_selective`` ke ``no``."

msgid ""
"The repo install process is now able to support building and synchronizing "
"artifacts for multiple CPU architectures. To support multiple architectures, "
"one or more repo servers must be created for each CPU architecture in the "
"deployment. When multiple CPU architectures are detected among the repo "
"servers, the repo-discovery process will automatically assign a repo master "
"to perform the build process for each architecture."
msgstr ""
"Proses pemasangan repo sekarang dapat mendukung pembuatan dan sinkronisasi "
"artefak untuk beberapa arsitektur CPU. Untuk mendukung banyak arsitektur, "
"satu atau lebih server repo harus dibuat untuk setiap arsitektur CPU dalam "
"deployment. Ketika beberapa arsitektur CPU terdeteksi di antara server repo, "
"proses repo-discovery akan secara otomatis menetapkan master repo untuk "
"melakukan proses pembangunan untuk setiap arsitektur."

msgid ""
"The repo server file system structure has been updated to allow for multiple "
"Operating systems running multiple architectures to be run at the same time "
"and served from a single server without impacting pools, venvs, wheel "
"archives, and manifests. The new structure follows the following pattern `"
"$RELEASE/$OS_TYPE-$ARCH` and has been applied to *os-releases*, *venvs*, and "
"*pools*."
msgstr ""
"Struktur sistem file server repo telah diperbarui untuk memungkinkan "
"beberapa sistem Operasi menjalankan banyak arsitektur untuk dijalankan pada "
"waktu yang sama dan dilayani dari satu server tanpa memengaruhi pools, "
"venvs, wheel archives, and manifests. Struktur baru mengikuti pola berikut  `"
"$RELEASE/$OS_TYPE-$ARCH` dan telah diterapkan pada *os-releases*, *venvs*, "
"dan *pools*."

msgid ""
"The repo server no longer uses pypiserver, so it has been removed. Along "
"with this, the following variables have also been removed."
msgstr ""
"Server repo tidak lagi menggunakan pypiserver, jadi sudah dihapus. Bersamaan "
"dengan ini, variabel berikut juga telah dihapus."

msgid ""
"The repo server now has a Package Cache service for distribution packages. "
"To leverage the cache, deployers will need to configure the package manager "
"on all hosts to use the cache as a proxy. If a deployer would prefer to "
"disable this service, the variable ``repo_pkg_cache_enabled`` should be set "
"to ``false``."
msgstr ""
"Server repo sekarang memiliki layanan Package Cache untuk paket distribusi. "
"Untuk meningkatkan cache, para deployer perlu mengkonfigurasi manajer paket "
"pada semua host untuk menggunakan cache sebagai proxy. Jika seorang deployer "
"lebih memilih untuk menonaktifkan layanan ini, variabel "
"``repo_pkg_cache_enabled`` harus diatur ke ``false``."

msgid ""
"The repo server now implements nginx as a reverse proxy for python packages "
"sourced from pypi. The initial query will be to a local deployment of "
"pypiserver in order to serve any locally built packages, but if the package "
"is not available locally it will retry the query against the upstream pypi "
"mirror set in the variable ``repo_nginx_pypi_upstream`` (defaults to pypi) "
"and cache the response."
msgstr ""
"Server repo sekarang mengimplementasikan nginx sebagai proxy terbalik untuk "
"paket python yang bersumber dari pypi. Kueri awal adalah untuk penyebaran "
"pypiserver lokal untuk melayani setiap paket yang dibuat secara lokal, "
"tetapi jika paket tidak tersedia secara lokal, ia akan mencoba lagi kueri "
"terhadap mirror pypi hulu yang diatur dalam variabel "
"``repo_nginx_pypi_upstream`` (default ke pypi) dan cache response."

msgid "The repo server will now be used as a package manager cache."
msgstr "Server repo sekarang akan digunakan sebagai cache manajer paket."

msgid ""
"The repo server's reverse proxy for pypi has now been removed, leaving only "
"the pypiserver to serve packages already on the repo server. The attempt to "
"reverse proxy upstream pypi turned out to be very unstable with increased "
"complexity for deployers using proxies or offline installs. With this, the "
"variables ``repo_nginx_pypi_upstream`` and ``repo_nginx_proxy_cache_path`` "
"have also been removed."
msgstr ""
"Proxy reverse server repo untuk pypi kini telah dihapus, hanya menyisakan "
"pypiserver untuk melayani paket yang sudah ada di server repo. Upaya untuk "
"membalikkan proxy hulu proksi ternyata sangat tidak stabil dengan "
"meningkatnya kerumitan bagi deployer yang menggunakan proxy atau pemasangan "
"offline. Dengan ini, variabel ``repo_nginx_pypi_upstream`` dan "
"``repo_nginx_proxy_cache_path`` juga telah dihapus."

msgid ""
"The repo-clone-mirror.yml file is being deprecated, effective immediately.  "
"The playbook itself has been changed to no longer sync and will be removed "
"from the tree in the Mitaka branch."
msgstr ""
"File repo-clone-mirror.yml sedang tidak digunakan lagi, segera berlaku. "
"Playbook itu sendiri telah diubah menjadi tidak lagi disinkronkan dan akan "
"dihapus dari tree di branch Mitaka."

msgid ""
"The repo_build play now correctly evaluates environment variables configured "
"in /etc/environment.  This enables deployments in an environment with http "
"proxies."
msgstr ""
"Play repo_build sekarang dengan benar mengevaluasi variabel lingkungan yang "
"dikonfigurasi di /etc/environment.  Ini memungkinkan deployment di "
"lingkungan dengan proksi http."

msgid ""
"The repo_build role always checks whether the latest package is installed "
"when executed. If a deployer wishes to change the check to only validate the "
"presence of the package, the option ``repo_build_package_state`` should be "
"set to ``present``."
msgstr ""
"Role repo_build selalu memeriksa apakah paket terbaru diinstal ketika "
"dieksekusi. Jika seorang deployer ingin mengubah tanda centang untuk hanya "
"memvalidasi keberadaan paket, opsi ``repo_build_package_state`` harus diatur "
"ke ``present``."

msgid ""
"The repo_build role now supports the ability to configure whether apt/yum "
"tasks install the latest available package, or just ensure that the package "
"is present. The default action is to ensure that the latest package is "
"present. The action taken may be changed to only ensure that the package is "
"present by setting ``repo_build_package_state`` to ``present``."
msgstr ""
"Role repo_build sekarang mendukung kemampuan untuk mengonfigurasi apakah "
"tugas apt/yum menginstal paket terbaru yang tersedia, atau hanya memastikan "
"bahwa paket tersebut ada. Tindakan default adalah untuk memastikan bahwa "
"paket terbaru hadir. Tindakan yang diambil dapat diubah hanya untuk "
"memastikan bahwa paket hadir dengan mengatur ``repo_build_package_state`` ke "
"``present``."

msgid ""
"The repo_server role always checks whether the latest package is installed "
"when executed. If a deployer wishes to change the check to only validate the "
"presence of the package, the option ``repo_server_package_state`` should be "
"set to ``present``."
msgstr ""
"Role repo_server selalu memeriksa apakah paket terbaru diinstal ketika "
"dijalankan. Jika seorang deployer ingin mengubah tanda centang untuk hanya "
"memvalidasi keberadaan paket, opsi ``repo_server_package_state`` harus "
"diatur ke ``present``."

msgid ""
"The repo_server role now supports the ability to configure whether apt/yum "
"tasks install the latest available package, or just ensure that the package "
"is present. The default action is to ensure that the latest package is "
"present. The action taken may be changed to only ensure that the package is "
"present by setting ``repo_server_package_state`` to ``present``."
msgstr ""
"Role repo_server sekarang mendukung kemampuan untuk mengonfigurasi apakah "
"tugas apt/yum menginstal paket terbaru yang tersedia, atau hanya memastikan "
"bahwa paket tersebut ada. Tindakan default adalah untuk memastikan bahwa "
"paket terbaru hadir. Tindakan yang diambil dapat diubah hanya untuk "
"memastikan bahwa paket hadir dengan mengatur ``repo_server_package_state`` "
"ke ``present``."

msgid ""
"The requirements version has bumped to pull in os-vif 1.15.2, which contains "
"the fix for OSSA-2019-004 / CVE-2019-15753. Operators using linuxbridge "
"networking (the default in openstack-ansible) should update immediately. The "
"fixed package will be installed in the nova venv upon re-deployment of nova "
"using the os-nova-install.yml playbook. Afterwards, verify that the ageing "
"timer on neutron-controlled linux bridges displays as \"300.00\" raher than "
"\"0.00\" using ``brctl showstp <bridge name>``."
msgstr ""
"Versi persyaratan telah dihancurkan untuk menarik os-vif 1.15.2, yang berisi "
"perbaikan untuk OSSA-2019-004 / CVE-2019-15753. Operator yang menggunakan "
"jaringan linuxbridge (default di openstack-ansible) harus segera "
"memperbarui. Paket tetap akan diinstal di nova venv setelah penempatan "
"kembali nova menggunakan os-nova-install.yml playbook. Setelah itu, "
"verifikasi bahwa penghitung waktu penuaan pada neutron-controlled linux "
"bridges  ditampilkan sebagai \"300,00\" dari pada \"0,00\" menggunakan `` "
"brctl showstp <bridge name> ``."

msgid ""
"The role now enables auditing during early boot to comply with the "
"requirements in V-38438. By default, the GRUB configuration variables in ``/"
"etc/default/grub.d/`` will be updated and the active ``grub.cfg`` will be "
"updated."
msgstr ""
"Role sekarang memungkinkan audit selama boot awal untuk memenuhi persyaratan "
"di V-38438. Secara default, variabel konfigurasi GRUB di ``/etc/default/grub."
"d/`` akan diperbarui dan ``grub.cfg`` yang aktif akan diperbarui."

msgid ""
"The role now supports SUSE based distributions. Required packages can now be "
"installed using the `zypper` package manager."
msgstr ""
"Role sekarang mendukung distribusi berbasis SUSE. Paket yang dibutuhkan "
"sekarang dapat diinstal menggunakan manajer paket `zypper`."

msgid ""
"The role now supports using the distribution packages for the OpenStack "
"services instead of the pip ones. This feature is disabled by default and "
"can be enabled by simply setting the ``aodh_install_method`` variable to "
"``distro``."
msgstr ""
"Role sekarang mendukung menggunakan paket distribusi untuk layanan OpenStack "
"bukan yang pip. Fitur ini dinonaktifkan secara default dan dapat diaktifkan "
"hanya dengan mengatur variabel ``aodh_install_method`` menjadi ``distro``."

msgid ""
"The role now supports using the distribution packages for the OpenStack "
"services instead of the pip ones. This feature is disabled by default and "
"can be enabled by simply setting the ``barbican_install_method`` variable to "
"``distro``."
msgstr ""
"Role sekarang mendukung menggunakan paket distribusi untuk layanan OpenStack "
"bukan yang pip. Fitur ini dinonaktifkan secara default dan dapat diaktifkan "
"dengan hanya mengatur variabel ``barbican_install_method`` ke ``distro``."

msgid ""
"The role now supports using the distribution packages for the OpenStack "
"services instead of the pip ones. This feature is disabled by default and "
"can be enabled by simply setting the ``ceilometer_install_method`` variable "
"to ``distro``."
msgstr ""
"Peran sekarang mendukung menggunakan paket distribusi untuk layanan "
"OpenStack bukan yang pip. Fitur ini dinonaktifkan secara default dan dapat "
"diaktifkan hanya dengan mengatur variabel ``ceilometer_install_method`` "
"menjadi ``distro``."

msgid ""
"The role now supports using the distribution packages for the OpenStack "
"services instead of the pip ones. This feature is disabled by default and "
"can be enabled by simply setting the ``cinder_install_method`` variable to "
"``distro``.--"
msgstr ""
"Role sekarang mendukung menggunakan paket distribusi untuk layanan OpenStack "
"bukan yang pip. Fitur ini dinonaktifkan secara default dan dapat diaktifkan "
"hanya dengan mengatur variabel ``cinder_install_method`` menjadi "
"``distro`` .--"

msgid ""
"The role now supports using the distribution packages for the OpenStack "
"services instead of the pip ones. This feature is disabled by default and "
"can be enabled by simply setting the ``designate_install_method`` variable "
"to ``distro``."
msgstr ""
"Role sekarang mendukung menggunakan paket distribusi untuk layanan OpenStack "
"bukan yang pip. Fitur ini dinonaktifkan secara default dan dapat diaktifkan "
"dengan hanya mengatur variabel ``designate_install_method`` ke ``distro``."

msgid ""
"The role now supports using the distribution packages for the OpenStack "
"services instead of the pip ones. This feature is disabled by default and "
"can be enabled by simply setting the ``glance_install_method`` variable to "
"``distro``."
msgstr ""
"Role sekarang mendukung menggunakan paket distribusi untuk layanan OpenStack "
"bukan yang pip. Fitur ini dinonaktifkan secara default dan dapat diaktifkan "
"hanya dengan mengatur variabel `` glance_install_method`` menjadi `` "
"distro``."

msgid ""
"The role now supports using the distribution packages for the OpenStack "
"services instead of the pip ones. This feature is disabled by default and "
"can be enabled by simply setting the ``heat_install_method`` variable to "
"``distro``."
msgstr ""
"Role sekarang mendukung menggunakan paket distribusi untuk layanan OpenStack "
"bukan yang pip. Fitur ini dinonaktifkan secara default dan dapat diaktifkan "
"dengan hanya mengatur variabel ``heat_install_method`` ke ``distro``."

msgid ""
"The role now supports using the distribution packages for the OpenStack "
"services instead of the pip ones. This feature is disabled by default and "
"can be enabled by simply setting the ``keystone_install_method`` variable to "
"``distro``."
msgstr ""
"Role sekarang mendukung menggunakan paket distribusi untuk layanan OpenStack "
"bukan yang pip. Fitur ini dinonaktifkan secara default dan dapat diaktifkan "
"hanya dengan mengatur variabel ``keystone_install_method`` menjadi "
"``distro``."

msgid ""
"The role now supports using the distribution packages for the OpenStack "
"services instead of the pip ones. This feature is disabled by default and "
"can be enabled by simply setting the ``neutron_install_method`` variable to "
"``distro``."
msgstr ""
"Role sekarang mendukung menggunakan paket distribusi untuk layanan OpenStack "
"bukan yang pip. Fitur ini dinonaktifkan secara default dan dapat diaktifkan "
"hanya dengan mengatur variabel ``neutron_install_method`` menjadi ``distro``."

msgid ""
"The role now supports using the distribution packages for the OpenStack "
"services instead of the pip ones. This feature is disabled by default and "
"can be enabled by simply setting the ``nova_install_method`` variable to "
"``distro``."
msgstr ""
"Peran sekarang mendukung menggunakan paket distribusi untuk layanan "
"OpenStack bukan yang pip. Fitur ini dinonaktifkan secara default dan dapat "
"diaktifkan hanya dengan mengatur variabel ``nova_install_method`` menjadi "
"``distro``."

msgid ""
"The role now supports using the distribution packages for the OpenStack "
"services instead of the pip ones. This feature is disabled by default and "
"can be enabled by simply setting the ``octavia_install_method`` variable to "
"``distro``."
msgstr ""
"Role sekarang mendukung menggunakan paket distribusi untuk layanan OpenStack "
"bukan yang pip. Fitur ini dinonaktifkan secara default dan dapat diaktifkan "
"hanya dengan mengatur variabel ``octavia_install_method`` ke ``distro``."

msgid ""
"The role now supports using the distribution packages for the OpenStack "
"services instead of the pip ones. This feature is disabled by default and "
"can be enabled by simply setting the ``swift_install_method`` variable to "
"``distro``."
msgstr ""
"Role sekarang mendukung menggunakan paket distribusi untuk layanan OpenStack "
"bukan yang pip. Fitur ini dinonaktifkan secara default dan dapat diaktifkan "
"hanya dengan mengatur variabel ``swift_install_method`` menjadi ``distro``."

msgid ""
"The role now syncs the LXC packages down from COPR to each host and builds a "
"local LXC package repository in `/opt/thm-lxc2.0`. This greatly reduces the "
"amount of times that packages must be downloaded from the COPR server during "
"deployments, which will reduce failures until the packages can be hosted "
"with a more reliable source."
msgstr ""
"Role sekarang menyinkronkan paket LXC turun dari COPR ke setiap host dan "
"membangun repositori paket LXC lokal di `/opt/thm-lxc2.0`.  Ini sangat "
"mengurangi jumlah paket yang harus diunduh dari server COPR selama "
"penerapan, yang akan mengurangi kegagalan sampai paket dapat di-host dengan "
"sumber yang lebih andal."

msgid ""
"The role previously did not restart the audit daemon after generating a new "
"rules file. The `bug <https://launchpad.net/bugs/1590916>`_ has been fixed "
"and the audit daemon will be restarted after any audit rule changes."
msgstr ""
"Role sebelumnya tidak me-restart daemon audit setelah membuat file aturan "
"baru. `bug <https://launchpad.net/bugs/1590916>`_ telah diperbaiki dan "
"daemon audit akan dimulai kembali setelah ada perubahan peraturan audit."

msgid "The rsyslog.conf is now using v7+ style configuration settings"
msgstr "Rsyslog.conf sekarang menggunakan pengaturan konfigurasi style v7+"

msgid ""
"The rsyslog_client role always checks whether the latest package is "
"installed when executed. If a deployer wishes to change the check to only "
"validate the presence of the package, the option "
"``rsyslog_client_package_state`` should be set to ``present``."
msgstr ""
"Role rsyslog_client selalu memeriksa apakah paket terbaru diinstal ketika "
"dijalankan. Jika seorang deployer ingin mengubah tanda centang untuk hanya "
"memvalidasi keberadaan paket, opsi ``rsyslog_client_package_state`` harus "
"diatur ke ``present``."

msgid ""
"The rsyslog_client role now supports the ability to configure whether apt/"
"yum tasks install the latest available package, or just ensure that the "
"package is present. The default action is to ensure that the latest package "
"is present. The action taken may be changed to only ensure that the package "
"is present by setting ``rsyslog_client_package_state`` to ``present``."
msgstr ""
"Peran rsyslog_client sekarang mendukung kemampuan untuk mengkonfigurasi "
"apakah tugas apt/yum menginstal paket terbaru yang tersedia, atau hanya "
"memastikan bahwa paket tersebut ada. Tindakan default adalah untuk "
"memastikan bahwa paket terbaru hadir. Tindakan yang diambil dapat diubah "
"hanya untuk memastikan bahwa paket tersebut hadir dengan mengatur "
"``rsyslog_client_package_state`` ke ``present``."

msgid ""
"The rsyslog_server role always checks whether the latest package is "
"installed when executed. If a deployer wishes to change the check to only "
"validate the presence of the package, the option "
"``rsyslog_server_package_state`` should be set to ``present``."
msgstr ""
"Role rsyslog_server selalu memeriksa apakah paket terbaru diinstal ketika "
"dijalankan. Jika seorang deployer ingin mengubah tanda centang untuk hanya "
"memvalidasi keberadaan paket, opsi ``rsyslog_server_package_state`` harus "
"diatur ke ``present``."

msgid ""
"The rsyslog_server role now supports the ability to configure whether apt/"
"yum tasks install the latest available package, or just ensure that the "
"package is present. The default action is to ensure that the latest package "
"is present. The action taken may be changed to only ensure that the package "
"is present by setting ``rsyslog_server_package_state`` to ``present``."
msgstr ""
"Role rsyslog_server sekarang mendukung kemampuan untuk mengkonfigurasi "
"apakah tugas apt/yum menginstal paket terbaru yang tersedia, atau hanya "
"memastikan bahwa paket tersebut ada. Tindakan default adalah untuk "
"memastikan bahwa paket terbaru hadir. Tindakan yang diambil dapat diubah "
"hanya untuk memastikan bahwa paket hadir dengan mengatur "
"``rsyslog_server_package_state`` ke ``present``."

msgid ""
"The security role always checks whether the latest package is installed when "
"executed. If a deployer wishes to change the check to only validate the "
"presence of the package, the option ``security_package_state`` should be set "
"to ``present``."
msgstr ""
"Role keamanan selalu memeriksa apakah paket terbaru diinstal ketika "
"dijalankan. Jika seorang deployer ingin mengubah tanda centang untuk hanya "
"memvalidasi keberadaan paket, opsi ``security_package_state`` harus diatur "
"ke ``present``."

msgid ""
"The security role now handles ``ssh_config`` files that contain ``Match`` "
"stanzas. A marker is added to the configuration file and any new "
"configuration items will be added below that marker. In addition, the "
"configuration file is validated for each change to the ssh configuration "
"file."
msgstr ""
"Role keamanan sekarang menangani file ``ssh_config`` yang berisi stanzas "
"``Match``. Marker ditambahkan ke file konfigurasi dan setiap item "
"konfigurasi baru akan ditambahkan di bawah marker itu. Selain itu, file "
"konfigurasi divalidasi untuk setiap perubahan ke file konfigurasi ssh."

msgid ""
"The security role now has tasks that will disable the graphical interface on "
"a server using upstart (Ubuntu 14.04) or systemd (Ubuntu 16.04 and CentOS "
"7). These changes take effect after a reboot."
msgstr ""
"Role keamanan sekarang memiliki tugas yang akan menonaktifkan antarmuka "
"grafis pada server menggunakan upstart (Ubuntu 14.04) atau systemd (Ubuntu "
"16.04 dan CentOS 7). Perubahan ini mulai berlaku setelah reboot."

msgid ""
"The security role now supports the ability to configure whether apt/yum "
"tasks install the latest available package, or just ensure that the package "
"is present. The default action is to ensure that the latest package is "
"present. The action taken may be changed to only ensure that the package is "
"present by setting ``security_package_state`` to ``present``."
msgstr ""
"Role keamanan sekarang mendukung kemampuan untuk mengonfigurasi apakah tugas "
"apt/yum menginstal paket terbaru yang tersedia, atau hanya memastikan bahwa "
"paket tersebut ada. Tindakan default adalah untuk memastikan bahwa paket "
"terbaru hadir. Tindakan yang diambil dapat diubah hanya untuk memastikan "
"bahwa paket hadir dengan mengatur ``security_package_state`` ke ``present``."

msgid ""
"The security role previously set the permissions on all audit log files in "
"``/var/log/audit`` to ``0400``, but this prevents the audit daemon from "
"writing to the active log file. This will prevent ``auditd`` from starting "
"or restarting cleanly."
msgstr ""
"Role keamanan sebelumnya mengatur izin pada semua file log audit di ``/var/"
"log/audit`` ke ``0400``, tetapi ini mencegah daemon audit agar tidak menulis "
"ke file log aktif. Ini akan mencegah ``auditd`` dari memulai atau memulai "
"ulang dengan bersih."

msgid ""
"The security role will accept the currently installed version of a package "
"rather than attempting to update it. This reduces unexpected changes on the "
"system from subsequent runs of the security role. Deployers can still set "
"``security_package_state`` to ``latest`` to ensure that all packages "
"installed by the security role are up to date."
msgstr ""
"Peran keamanan akan menerima versi paket yang saat ini diinstal daripada "
"mencoba memperbaruinya. Ini mengurangi perubahan tak terduga pada sistem "
"dari menjalankan peran keamanan selanjutnya. Deployer masih dapat mengatur "
"``security_package_state`` ke `` atest`` untuk memastikan bahwa semua paket "
"yang diinstal oleh role keamanan adalah yang terbaru."

msgid ""
"The security role will no longer fix file permissions and ownership based on "
"the contents of the RPM database by default. Deployers can opt in for these "
"changes by setting ``security_reset_perm_ownership`` to ``yes``."
msgstr ""
"Role keamanan tidak akan lagi memperbaiki izin file dan kepemilikan "
"berdasarkan isi dari database RPM secara default. Deployer dapat ikut serta "
"dalam perubahan ini dengan mengatur ``security_reset_perm_ownership`` ke "
"``yes``."

msgid ""
"The security-hardening playbook hosts target can now be filtered using the "
"``security_host_group`` var."
msgstr ""
"Target host security-hardening playbook sekarang dapat difilter menggunakan "
"var ``security_host_group``."

msgid ""
"The service setup in keystone for aodh will now be executed through "
"delegation to the ``aodh_service_setup_host`` which, by default, is "
"``localhost`` (the deploy host). Deployers can opt to rather change this to "
"the utility container by implementing the following override in "
"``user_variables.yml``."
msgstr ""
"Pengaturan layanan dalam keystone untuk aodh sekarang akan dieksekusi "
"melalui delegasi dimana ``aodh_service_setup_host``, secara default, adalah "
"``localhost``  (the deploy host). Deployer dapat memilih untuk mengubah ini "
"ke kontainer utilitas dengan mengimplementasikan override berikut di "
"``user_variables.yml``."

msgid ""
"The service setup in keystone for barbican will now be executed through "
"delegation to the ``barbican_service_setup_host`` which, by default, is "
"``localhost`` (the deploy host). Deployers can opt to rather change this to "
"the utility container by implementing the following override in "
"``user_variables.yml``."
msgstr ""
"Pengaturan layanan dalam keystone untuk barbican sekarang akan dieksekusi "
"melalui delegasi ke dimana ``barbican_service_setup_host``, secara default, "
"adalah ``localhost`` (the deploy host).  Deployer dapat memilih untuk "
"mengubah ini ke kontainer utilitas dengan mengimplementasikan override "
"berikut di ``user_variables.yml``."

msgid ""
"The service setup in keystone for ceilometer will now be executed through "
"delegation to the ``ceilometer_service_setup_host`` which, by default, is "
"``localhost`` (the deploy host). Deployers can opt to rather change this to "
"the utility container by implementing the following override in "
"``user_variables.yml``."
msgstr ""
"Pengaturan layanan dalam keystone untuk ceilometer sekarang akan dieksekusi "
"melalui delegasi dimana ``ceilometer_service_setup_host``, secara default, "
"adalah ``localhost``  (the deploy host). Deployer dapat memilih untuk "
"mengubah ini ke kontainer utilitas dengan mengimplementasikan override "
"berikut di ``user_variables.yml``."

msgid ""
"The service setup in keystone for cinder will now be executed through "
"delegation to the ``cinder_service_setup_host`` which, by default, is "
"``localhost`` (the deploy host). Deployers can opt to rather change this to "
"the utility container by implementing the following override in "
"``user_variables.yml``."
msgstr ""
"Pengaturan layanan dalam keystone untuk cinder sekarang akan dieksekusi "
"melalui delegasi dimana ``cinder_service_setup_host`` yang, secara default, "
"adalah ``localhost`` (the deploy host). Deployer dapat memilih untuk "
"mengubah ini ke kontainer utilitas dengan mengimplementasikan override "
"berikut di ``user_variables.yml``."

msgid ""
"The service setup in keystone for cloudkitty will now be executed through "
"delegation to the ``cloudkitty_service_setup_host`` which, by default, is "
"``localhost`` (the deploy host). Deployers can opt to rather change this to "
"the utility container by implementing the following override in "
"``user_variables.yml``."
msgstr ""
"Pengaturan layanan dalam keystone untuk cloudkitty sekarang akan dieksekusi "
"melalui delegasi ke ``cloudkitty_service_setup_host`` yang, secara default, "
"adalah ``localhost`` (host penyebaran). Deployer dapat memilih untuk "
"mengubah ini ke kontainer utilitas dengan mengimplementasikan penggantian "
"berikut di ``user_variables.yml``."

msgid ""
"The service setup in keystone for designate will now be executed through "
"delegation to the ``designate_service_setup_host`` which, by default, is "
"``localhost`` (the deploy host). Deployers can opt to rather change this to "
"the utility container by implementing the following override in "
"``user_variables.yml``."
msgstr ""
"Pengaturan layanan dalam keystone untuk ditunjuk sekarang akan dieksekusi "
"melalui delegasi dimana ``designate_service_setup_host``, secara default, "
"adalah ``localhost``  (the deploy host).  Deployer dapat memilih untuk "
"mengubah ini ke kontainer utilitas dengan mengimplementasikan override "
"berikut di ``user_variables.yml``."

msgid ""
"The service setup in keystone for glance will now be executed through "
"delegation to the ``glance_service_setup_host`` which, by default, is "
"``localhost`` (the deploy host). Deployers can opt to rather change this to "
"the utility container by implementing the following override in "
"``user_variables.yml``."
msgstr ""
"Pengaturan layanan dalam keystone untuk sekilas sekarang akan dieksekusi "
"melalui delegasi dimana ``glance_service_setup_host``, secara default, "
"adalah ``localhost`` (the deploy host). Deployer dapat memilih untuk "
"mengubah ini ke kontainer utilitas dengan mengimplementasikan override "
"berikut di ``user_variables.yml``."

msgid ""
"The service setup in keystone for gnocchi will now be executed through "
"delegation to the ``gnocchi_service_setup_host`` which, by default, is "
"``localhost`` (the deploy host). Deployers can opt to rather change this to "
"the utility container by implementing the following override in "
"``user_variables.yml``."
msgstr ""
"Pengaturan layanan dalam keystone untuk gnocchi sekarang akan dieksekusi "
"melalui delegasi ke `` gnocchi_service_setup_host`` yang, secara default, "
"adalah `` localhost`` (host penyebaran). Deployer dapat memilih untuk "
"mengubah ini ke wadah utilitas dengan mengimplementasikan penggantian "
"berikut di `` user_variables.yml``."

msgid ""
"The service setup in keystone for heat will now be executed through "
"delegation to the ``heat_service_setup_host`` which, by default, is "
"``localhost`` (the deploy host). Deployers can opt to rather change this to "
"the utility container by implementing the following override in "
"``user_variables.yml``."
msgstr ""
"Pengaturan layanan dalam keystone untuk panas sekarang akan dieksekusi "
"melalui delegasi ke `` heat_service_setup_host`` yang, secara default, "
"adalah `` localhost`` (host penyebaran). Deployer dapat memilih untuk "
"mengubah ini ke wadah utilitas dengan mengimplementasikan penggantian "
"berikut di `` user_variables.yml``."

msgid ""
"The service setup in keystone for horizon will now be executed through "
"delegation to the ``horizon_service_setup_host`` which, by default, is "
"``localhost`` (the deploy host). Deployers can opt to rather change this to "
"the utility container by implementing the following override in "
"``user_variables.yml``."
msgstr ""
"Pengaturan layanan dalam keystone untuk horizon sekarang akan dieksekusi "
"melalui delegasi dimana ``horizon_service_setup_host``, secara default, "
"adalah ``localhost`` (the deploy host). Deployer dapat memilih untuk "
"mengubah ini ke kontainer utilitas dengan mengimplementasikan override "
"berikut di ``user_variables.yml``."

msgid ""
"The service setup in keystone for ironic will now be executed through "
"delegation to the ``ironic_service_setup_host`` which, by default, is "
"``localhost`` (the deploy host). Deployers can opt to rather change this to "
"the utility container by implementing the following override in "
"``user_variables.yml``."
msgstr ""
"Pengaturan layanan dalam keystone untuk ironic sekarang akan dieksekusi "
"melalui delegasi dimana ``ironic_service_setup_host``, secara default, "
"adalah ``localhost``  (the deploy host). Deployer dapat memilih untuk "
"mengubah ini ke kontainer utilitas dengan mengimplementasikan override "
"berikut di ``user_variables.yml``."

msgid ""
"The service setup in keystone for magnum will now be executed through "
"delegation to the ``magnum_service_setup_host`` which, by default, is "
"``localhost`` (the deploy host). Deployers can opt to rather change this to "
"the utility container by implementing the following override in "
"``user_variables.yml``."
msgstr ""
"Pengaturan layanan dalam keystone untuk magnum sekarang akan dieksekusi "
"melalui delegasi ke `` magnum_service_setup_host`` yang, secara default, "
"adalah `` localhost`` (host penyebaran). Deployer dapat memilih untuk "
"mengubah ini ke wadah utilitas dengan mengimplementasikan penggantian "
"berikut di `` user_variables.yml``."

msgid ""
"The service setup in keystone for neutron will now be executed through "
"delegation to the ``neutron_service_setup_host`` which, by default, is "
"``localhost`` (the deploy host). Deployers can opt to rather change this to "
"the utility container by implementing the following override in "
"``user_variables.yml``."
msgstr ""
"Pengaturan layanan dalam keystone untuk neutron sekarang akan dieksekusi "
"melalui delegasi dimana ``neutron_service_setup_host``, secara default, "
"adalah ``localhost``  (the deploy host). Deployer dapat memilih untuk "
"mengubah ini ke kontainer utilitas dengan mengimplementasikan override "
"berikut di ``user_variables.yml``."

msgid ""
"The service setup in keystone for nova will now be executed through "
"delegation to the ``nova_service_setup_host`` which, by default, is "
"``localhost`` (the deploy host). Deployers can opt to rather change this to "
"the utility container by implementing the following override in "
"``user_variables.yml``."
msgstr ""
"Pengaturan layanan dalam keystone untuk nova sekarang akan dieksekusi "
"melalui delegasi dimana ``nova_service_setup_host``, secara default, adalah "
"``localhost``  (the deploy host). Deployer dapat memilih untuk mengubah ini "
"ke kontainer utilitas dengan mengimplementasikan override berikut di "
"``user_variables.yml``."

msgid ""
"The service setup in keystone for octavia will now be executed through "
"delegation to the ``octavia_service_setup_host`` which, by default, is "
"``localhost`` (the deploy host). Deployers can opt to rather change this to "
"the utility container by implementing the following override in "
"``user_variables.yml``."
msgstr ""
"Pengaturan layanan dalam keystone untuk octavia sekarang akan dieksekusi "
"melalui delegasi dimana ``octavia_service_setup_host``, secara default, "
"adalah ``localhost`` (the deploy host). Deployer dapat memilih untuk "
"mengubah ini ke kontainer utilitas dengan mengimplementasikan override "
"berikut di ``user_variables.yml``."

msgid ""
"The service setup in keystone for sahara will now be executed through "
"delegation to the ``sahara_service_setup_host`` which, by default, is "
"``localhost`` (the deploy host). Deployers can opt to rather change this to "
"the utility container by implementing the following override in "
"``user_variables.yml``."
msgstr ""
"Pengaturan layanan dalam keystone untuk sahara sekarang akan dieksekusi "
"melalui delegasi dimana ``sahara_service_setup_host``, secara default, "
"adalah ``localhost`` (the deploy host). Deployer dapat memilih untuk "
"mengubah ini ke kontainer utilitas dengan mengimplementasikan override "
"berikut di ``user_variables.yml``."

msgid ""
"The service setup in keystone for swift will now be executed through "
"delegation to the ``swift_service_setup_host`` which, by default, is "
"``localhost`` (the deploy host). Deployers can opt to rather change this to "
"the utility container by implementing the following override in "
"``user_variables.yml``."
msgstr ""
"Pengaturan layanan dalam keystone untuk swift sekarang akan dieksekusi "
"melalui delegasi dimana ``swift_service_setup_host``, secara default, adalah "
"``localhost``(the deploy host). Deployer dapat memilih untuk mengubah ini ke "
"kontainer utilitas dengan mengimplementasikan override berikut di "
"``user_variables.yml``."

msgid ""
"The service setup in keystone for tempest will now be executed through "
"delegation to the ``tempest_service_setup_host`` which, by default, is "
"``localhost`` (the deploy host). Deployers can opt to rather change this to "
"the utility container by implementing the following override in "
"``user_variables.yml``."
msgstr ""
"Pengaturan layanan dalam keystone untuk prahara sekarang akan dijalankan "
"melalui delegasi dimana ``tempest_service_setup_host`` yang, secara default, "
"adalah ``localhost`` (the deploy host). Deployer dapat memilih untuk "
"mengubah ini ke kontainer utilitas dengan mengimplementasikan override "
"berikut di ``user_variables.yml``."

msgid ""
"The service updates for keystone will now be executed through delegation to "
"the ``keystone_service_setup_host`` which, by default, is ``localhost`` (the "
"deploy host). Deployers can opt to rather change this to the utility "
"container by implementing the following override in ``user_variables.yml``."
msgstr ""
"Pembaruan layanan untuk keystone sekarang akan dieksekusi melalui delegasi "
"ke dimana  ``keystone_service_setup_host``, secara default, adalah "
"``localhost`` (the deploy host). Deployer dapat memilih untuk mengubah ini "
"ke kontainer utilitas dengan mengimplementasikan override berikut di "
"``user_variables.yml``."

msgid ""
"The standard collectstatic and compression process in the os_horizon role "
"now happens after horizon customizations are installed, so that all static "
"resources will be collected and compressed."
msgstr ""
"Proses pengumpulan dan kompresi standar dalam role os_horizon sekarang "
"terjadi setelah penyesuaian horizon diinstal, sehingga semua sumber daya "
"statis akan dikumpulkan dan dikompresi."

msgid ""
"The supported upgrade path from Xenial to Bionic is via re-installation of "
"the host OS across all nodes and redeployment of the required services. The "
"Rocky branch of OSA is intended as the transition point for such upgrades "
"from Xenial to Bionic. At this time there is no support for in-place "
"operating system upgrades (typically via ``do-release-upgrade``)."
msgstr ""
"Path upgrade yang didukung dari Xenial ke Bionic adalah melalui re-"
"installation OS host di semua node dan redeployment layanan yang diperlukan. "
"Branch Rocky dari OSA dimaksudkan sebagai titik transisi untuk upgrade dari "
"Xenial ke Bionic. Saat ini tidak ada dukungan untuk upgrade sistem operasi "
"in-place (biasanya melalui ``do-release-upgrade``)."

msgid ""
"The sysctl configuration task was not skipping configurations where "
"``enabled`` was set to ``no``. Instead, it was removing configurations when "
"``enabled: no`` was set."
msgstr ""
"Tugas konfigurasi sysctl tidak melewatkan konfigurasi di mana ``enabled`` "
"disetel ke ``no``. Sebagai gantinya, itu menghapus konfigurasi ketika "
"``enabled: no`` ditetapkan."

msgid ""
"The tacker dashboard is available in Horizon. Deployers can enable the panel "
"by setting the following Ansible variable:"
msgstr ""
"Dasbor tacker tersedia di Horizon. Deployer dapat mengaktifkan panel dengan "
"mengatur variabel Ansible berikut:"

msgid ""
"The tag options when creating an LXC container have been simplified. The two "
"tags now supported by the `lxc_container_create` role are **lxc-{create,"
"config}**."
msgstr ""
"Opsi tag saat membuat kontainer LXC telah disederhanakan. Dua tag yang "
"sekarang didukung oleh peran `lxc_container_create` adalah **lxc-{create,"
"config}**."

msgid ""
"The task dropping the aodh systemd unit files now uses the "
"``config_template`` action plugin allowing deployers access to customize the "
"unit files as they see fit without having to load extra options into the "
"defaults and polute the generic systemd unit file with jinja2 variables and "
"conditionals."
msgstr ""
"Tugas menjatuhkan (dropping) file unit systemd aodh sekarang menggunakan "
"plugin aksi ``config_template`` yang memungkinkan akses deployer untuk "
"mengkustomisasi file unit sesuai keinginan tanpa harus memuat opsi tambahan "
"ke default dan mencemari file unit systemd generik dengan variabel jinja2 "
"dan persyaratannya"

msgid ""
"The task dropping the barbican systemd unit files now uses the "
"``config_template`` action plugin allowing deployers access to customize the "
"unit files as they see fit without having to load extra options into the "
"defaults and polute the generic systemd unit file with jinja2 variables and "
"conditionals."
msgstr ""
"Tugas dropping file unit systemd barbican sekarang menggunakan plugin aksi "
"``config_template`` yang memungkinkan akses deployer untuk mengkustomisasi "
"file unit sesuai keinginan tanpa harus memuat opsi tambahan ke default dan "
"mencemari file unit systemd generik dengan variabel jinja2 dan "
"persyaratannya."

msgid ""
"The task dropping the ceilometer systemd unit files now uses the "
"``config_template`` action plugin allowing deployers access to customize the "
"unit files as they see fit without having to load extra options into the "
"defaults and pollute the generic systemd unit file with jinja2 variables and "
"conditionals."
msgstr ""
"Tugas dropping file unit systemd ceilometer sekarang menggunakan plugin aksi "
"``config_template`` yang memungkinkan akses deployer untuk menyesuaikan file "
"unit sesuai keinginan tanpa harus memuat opsi tambahan ke default dan "
"mencemari file unit systemd generik dengan variabel jinja2 dan "
"persyaratannya."

msgid ""
"The task dropping the ceilometer systemd unit files now uses the "
"``config_template`` action plugin allowing deployers access to customize the "
"unit files as they see fit without having to load extra options into the "
"defaults and polute the generic systemd unit file with jinja2 variables and "
"conditionals."
msgstr ""
"Tugas dropping file unit systemd ceilometer sekarang menggunakan plugin aksi "
"``config_template`` yang memungkinkan akses deployer untuk mengkustomisasi "
"file unit sesuai keinginan tanpa harus memuat opsi tambahan ke default dan "
"mencemari file unit systemd generik dengan variabel jinja2 dan "
"persyaratannya."

msgid ""
"The task dropping the cinder systemd unit files now uses the "
"``config_template`` action plugin allowing deployers access to customize the "
"unit files as they see fit without having to load extra options into the "
"defaults and polute the generic systemd unit file with jinja2 variables and "
"conditionals."
msgstr ""
"Tugas menjatuhkan file unit systemd cinder sekarang menggunakan plugin aksi "
"``config_template`` yang memungkinkan akses penyebar untuk menyesuaikan file "
"unit sesuai keinginan tanpa harus memuat opsi tambahan ke default dan polute "
"file unit systemd generik dengan variabel jinja2 dan persyaratan."

msgid ""
"The task dropping the designate systemd unit files now uses the "
"``config_template`` action plugin allowing deployers access to customize the "
"unit files as they see fit without having to load extra options into the "
"defaults and polute the generic systemd unit file with jinja2 variables and "
"conditionals."
msgstr ""
"Tugas dropping file unit systemd designate sekarang menggunakan plugin aksi "
"``config_template`` yang memungkinkan akses deployer untuk mengkustomisasi "
"file unit sesuai keinginan tanpa harus memuat opsi tambahan ke default dan "
"mencemari file unit systemd generik dengan variabel jinja2 dan "
"persyaratannya."

msgid ""
"The task dropping the glance systemd unit files now uses the "
"``config_template`` action plugin allowing deployers access to customize the "
"unit files as they see fit without having to load extra options into the "
"defaults and polute the generic systemd unit file with jinja2 variables and "
"conditionals."
msgstr ""
"Tugas dropping file unit systemd glance sekarang menggunakan plugin aksi "
"``config_template`` yang memungkinkan akses deployer untuk mengkustomisasi "
"file unit sesuai keinginan tanpa harus memuat opsi tambahan ke default dan "
"mencemari file unit systemd generik dengan variabel jinja2 dan "
"persyaratannya."

msgid ""
"The task dropping the gnocchi systemd unit files now uses the "
"``config_template`` action plugin allowing deployers access to customize the "
"unit files as they see fit without having to load extra options into the "
"defaults and polute the generic systemd unit file with jinja2 variables and "
"conditionals."
msgstr ""
"Tugas menjatuhkan file unit systemd gnocchi sekarang menggunakan plugin aksi "
"`` config_template`` yang memungkinkan para penyebar mengakses untuk "
"mengkustomisasi file-file unit sesuai keinginan tanpa harus memuat opsi "
"tambahan ke default dan memutarkan file unit systemd umum dengan variabel "
"jinja2 dan persyaratan."

msgid ""
"The task dropping the heat systemd unit files now uses the "
"``config_template`` action plugin allowing deployers access to customize the "
"unit files as they see fit without having to load extra options into the "
"defaults and polute the generic systemd unit file with jinja2 variables and "
"conditionals."
msgstr ""
"Tugas dropping file unit systemd heat sekarang menggunakan plugin aksi "
"``config_template`` yang memungkinkan akses deployer untuk mengkustomisasi "
"file unit sesuai keinginan tanpa harus memuat opsi tambahan ke default dan "
"mencemari file unit systemd generik dengan variabel jinja2 dan "
"persyaratannya."

msgid ""
"The task dropping the ironic systemd unit files now uses the "
"``config_template`` action plugin allowing deployers access to customize the "
"unit files as they see fit without having to load extra options into the "
"defaults and polute the generic systemd unit file with jinja2 variables and "
"conditionals."
msgstr ""
"Tugas dropping file unit systemd ironis sekarang menggunakan plugin aksi "
"``config_template`` yang memungkinkan akses deployer untuk menyesuaikan file "
"unit sesuai keinginan tanpa harus memuat opsi tambahan ke default dan "
"mencemari file unit systemd generik dengan variabel jinja2 dan persyaratan."

msgid ""
"The task dropping the keystone systemd unit files now uses the "
"``config_template`` action plugin allowing deployers access to customize the "
"unit files as they see fit without having to load extra options into the "
"defaults and polute the generic systemd unit file with jinja2 variables and "
"conditionals."
msgstr ""
"Tugas dropping file unit systemd keystone sekarang menggunakan plugin aksi "
"``config_template`` yang memungkinkan akses deployer untuk mengkustomisasi "
"file unit sesuai keinginan tanpa harus memuat opsi tambahan ke default dan "
"mencemari file unit systemd generik dengan variabel jinja2 dan "
"persyaratannya."

msgid ""
"The task dropping the magnum systemd unit files now uses the "
"``config_template`` action plugin allowing deployers access to customize the "
"unit files as they see fit without having to load extra options into the "
"defaults and polute the generic systemd unit file with jinja2 variables and "
"conditionals."
msgstr ""
"Tugas menjatuhkan file unit systemd magnum sekarang menggunakan plugin aksi "
"``config_template`` yang memungkinkan akses penyebar untuk menyesuaikan file "
"unit sesuai keinginan tanpa harus memuat opsi tambahan ke default dan polute "
"file unit systemd generik dengan variabel jinja2 dan persyaratan."

msgid ""
"The task dropping the neutron systemd unit files now uses the "
"``config_template`` action plugin allowing deployers access to customize the "
"unit files as they see fit without having to load extra options into the "
"defaults and polute the generic systemd unit file with jinja2 variables and "
"conditionals."
msgstr ""
"Tugas dropping file unit systemd neutron sekarang menggunakan plugin aksi "
"``config_template`` yang memungkinkan akses deployer untuk mengkustomisasi "
"file unit sesuai keinginan tanpa harus memuat opsi tambahan ke default dan "
"mencemari file unit systemd generik dengan variabel jinja2 dan "
"persyaratannya."

msgid ""
"The task dropping the nova systemd unit files now uses the "
"``config_template`` action plugin allowing deployers access to customize the "
"unit files as they see fit without having to load extra options into the "
"defaults and polute the generic systemd unit file with jinja2 variables and "
"conditionals."
msgstr ""
"Tugas menjatuhkan file unit systemd nova sekarang menggunakan plugin aksi "
"``config_template`` yang memungkinkan akses deployer untuk menyesuaikan file "
"unit sesuai keinginan tanpa harus memuat opsi tambahan ke default dan polute "
"file unit systemd umum dengan variabel jinja2 dan persyaratan."

msgid ""
"The task dropping the octavia systemd unit files now uses the "
"``config_template`` action plugin allowing deployers access to customize the "
"unit files as they see fit without having to load extra options into the "
"defaults and polute the generic systemd unit file with jinja2 variables and "
"conditionals."
msgstr ""
"Tugas dropping file unit systemd octavia sekarang menggunakan plugin aksi "
"``config_template`` yang memungkinkan akses deployer untuk mengkustomisasi "
"file unit sesuai keinginan tanpa harus memuat opsi tambahan ke default dan "
"mencemari file unit systemd generik dengan variabel jinja2 dan "
"persyaratannya."

msgid ""
"The task dropping the sahara systemd unit files now uses the "
"``config_template`` action plugin allowing deployers access to customize the "
"unit files as they see fit without having to load extra options into the "
"defaults and polute the generic systemd unit file with jinja2 variables and "
"conditionals."
msgstr ""
"Tugas dropping file unit systemd sahara sekarang menggunakan plugin aksi "
"``config_template`` yang memungkinkan akses deployer untuk mengkustomisasi "
"file unit sesuai keinginan tanpa harus memuat opsi tambahan ke default dan "
"mencemari file unit systemd generik dengan variabel jinja2 dan "
"persyaratannya."

msgid ""
"The task dropping the swift systemd unit files now uses the "
"``config_template`` action plugin allowing deployers access to customize the "
"unit files as they see fit without having to load extra options into the "
"defaults and polute the generic systemd unit file with jinja2 variables and "
"conditionals."
msgstr ""
"Tugas menjatuhkan file unit systemd swift sekarang menggunakan plugin aksi "
"``config_template`` yang memungkinkan deployer akses untuk mengkustomisasi "
"file unit sesuai keinginan tanpa harus memuat opsi tambahan ke default dan "
"mencemari file unit systemd generik dengan variabel jinja2 dan persyaratan."

msgid ""
"The task dropping the trove systemd unit files now uses the "
"``config_template`` action plugin allowing deployers access to customize the "
"unit files as they see fit without having to load extra options into the "
"defaults and polute the generic systemd unit file with jinja2 variables and "
"conditionals."
msgstr ""
"Tugas dropping file unit systemve trove sekarang menggunakan plugin aksi "
"``config_template`` yang memungkinkan akses deployer untuk mengkustomisasi "
"file unit sesuai keinginan tanpa harus memuat opsi tambahan ke default dan "
"mencemari file unit systemd generik dengan variabel jinja2 dan "
"persyaratannya."

msgid ""
"The task now removes any permissions that are not allowed by the STIG. Any "
"log files that meet or exceed the STIG requirements will not be modified."
msgstr ""
"Tugas sekarang menghapus semua izin yang tidak diizinkan oleh STIG. File log "
"apa pun yang memenuhi atau melampaui persyaratan STIG tidak akan diubah."

msgid ""
"The tasks creating a keystone service user have been removed, along with "
"related variables ``keystone_service_user_name`` and "
"``keystone_service_password``. This user can be deleted in existing "
"deployments."
msgstr ""
"Tugas membuat pengguna layanan keystone telah dihapus, bersama dengan "
"variabel terkait ``keystone_service_user_name`` dan "
"``keystone_service_password``. Pengguna ini dapat dihapus di deployment yang "
"ada."

msgid ""
"The tasks in the os_horizon role will determine which LBaaS version is in "
"use (via ``neutron_plugin_base``) and activate the correct panel for LBaaS "
"v1 or v2."
msgstr ""
"Tugas dalam role os_horizon akan menentukan versi LBaaS mana yang digunakan "
"(melalui ``neutron_plugin_base``) dan mengaktifkan panel yang benar untuk "
"LBaaS v1 atau v2."

msgid ""
"The tasks that search for ``.shosts`` and ``shosts.equiv`` files (STIG ID: "
"RHEL-07-040330) are now skipped by default. The search takes a long time to "
"complete on systems with lots of files and it also causes a significant "
"amount of disk I/O while it runs."
msgstr ""
"Tugas yang mencari file ``.shosts`` dan ``shosts.equiv``  (STIG ID: "
"RHEL-07-040330) sekarang dilewati secara default. Pencarian membutuhkan "
"waktu lama untuk diselesaikan pada sistem dengan banyak file dan itu juga "
"menyebabkan sejumlah besar I/O disk saat dijalankan."

msgid ""
"The tasks within the ansible-hardening role are now based on Version 1, "
"Release 3 of the Red Hat Enteprise Linux Security Technical Implementation "
"Guide."
msgstr ""
"Tugas dalam role ansible-hardening sekarang didasarkan pada Version 1, "
"Release 3 of the Red Hat Enteprise Linux Security Technical Implementation "
"Guide."

msgid ""
"The trove service setup in keystone will now be executed through delegation "
"to the ``trove_service_setup_host`` which, by default, is ``localhost`` (the "
"deploy host). Deployers can opt to rather change this to the utility "
"container by implementing the following override in ``user_variables.yml``."
msgstr ""
"Setup layanan trove di keystone sekarang akan dieksekusi melalui delegasi "
"dimana ``trove_service_setup_host``, secara default, adalah ``localhost`` "
"(the deploy host). Deployer dapat memilih untuk mengubah ini ke kontainer "
"utilitas dengan mengimplementasikan override berikut di ``user_variables."
"yml``."

msgid ""
"The upgrade playbook `nova-flavor-migration.yml` will perform a migration of "
"nova flavor data. This will need to be completed prior to upgrading to "
"Liberty. It is recommended that Kilo be deployed from the `eol-kilo` tag "
"prior to upgrading to Liberty to ensure that this task is completed "
"successfully."
msgstr ""
"Playbook upgrade `nova-flavor-migration.yml` akan melakukan migrasi data "
"flavor nova. Ini harus diselesaikan sebelum upgrading ke Liberty. Dianjurkan "
"agar Kilo digunakan dari tag `eol-kilo` sebelum upgrading ke Liberty untuk "
"memastikan bahwa tugas ini berhasil diselesaikan."

msgid ""
"The upgrade process will backup and re-configure the /etc/openstack_deploy "
"directory. This includes inserting new environment details, updating changed "
"variable names, and generating newly added secrets."
msgstr ""
"Proses upgrade akan mencadangkan dan mengkonfigurasi ulang direktori /etc/"
"openstack_deploy.  Ini termasuk memasukkan detail lingkungan baru, "
"memperbarui nama variabel yang diubah, dan menghasilkan rahasia yang baru "
"ditambahkan."

msgid ""
"The upgrade step to remove legacy MariaDB apt sources was failing due to the "
"destruction of the repo containers. This issue has now been fixed by "
"skipping the repo containers in this step."
msgstr ""
"Langkah upgrade untuk menghapus sumber apt MariaDB lawas gagal karena "
"penghancuran kontainer repo. Masalah ini sekarang telah diperbaiki dengan "
"melewatkan kontainer repo di langkah ini."

msgid ""
"The upstream MariaDB init script has replaced the custom init script that "
"was provided by OpenStack-Ansible in previous versions."
msgstr ""
"Skrip init MariaDB hulu telah menggantikan skrip init kustom yang disediakan "
"oleh OpenStack-Ansible di versi sebelumnya."

msgid ""
"The upstream noVNC developers recommend that the keymap be automatically "
"detected for virtual machine consoles. The defaults for three Ansible "
"variables have been removed:"
msgstr ""
"Pengembang noVNC hulu merekomendasikan agar keymap terdeteksi secara "
"otomatis untuk konsol mesin virtual. Default untuk tiga variabel Ansible "
"telah dihapus:"

msgid ""
"The upstream noVNC developers recommend that the keymap be automatically "
"detected for virtual machine consoles. Three Ansible variables have been "
"removed:"
msgstr ""
"Pengembang noVNC hulu merekomendasikan agar keymap terdeteksi secara "
"otomatis untuk konsol mesin virtual. Tiga variabel yang mungkin telah "
"dihapus:"

msgid ""
"The use of the ``apt_package_pinning`` role as a meta dependency has been "
"removed from the rabbitmq_server role. While the package pinning role is "
"still used, it will now only be executed when the apt task file is executed."
msgstr ""
"Penggunaan role ``apt_package_pinning`` sebagai ketergantungan meta telah "
"dihapus dari role rabbitmq_server. Sementara role pinning paket masih "
"digunakan, sekarang hanya akan dieksekusi ketika file tugas apt dieksekusi."

msgid "The use_neutron option was marked to be removed in sahara."
msgstr "Opsi use_neutron ditandai untuk dihapus di sahara."

msgid ""
"The var ``lxc_container_ssh_delay`` along with SSH specific ping checks have "
"been removed in favor of using Ansible's wait_for_connection module, which "
"will not rely on SSH to the container to verify connectivity. A new variable "
"called ``lxc_container_wait_params`` has been added to allow configuration "
"of the parameters passed to the ``wait_for_connection`` module."
msgstr ""
"Var ``lxc_container_ssh_delay`` bersama dengan pemeriksaan ping spesifik SSH "
"telah dihapus karena menggunakan modul wait_for_connection Ansible, yang "
"tidak akan bergantung pada SSH ke kontainer untuk memverifikasi "
"konektivitas. Variabel baru yang disebut ``lxc_container_wait_params`` telah "
"ditambahkan untuk memungkinkan konfigurasi parameter yang diteruskan ke "
"modul ``wait_for_connection``."

msgid ""
"The var ``lxc_container_ssh_delay`` along with SSH specific ping checks have "
"been removed in favor of using Ansible's wait_for_connection module, which "
"will not rely on SSH to the container."
msgstr ""
"Var ``lxc_container_ssh_delay`` bersama dengan pemeriksaan ping spesifik SSH "
"telah dihapus karena menggunakan modul wait_for_connection Ansible, yang "
"tidak akan bergantung pada SSH ke kontainer."

msgid ""
"The variable ``aodh_apt_packages`` has been renamed to "
"``aodh_distro_packages``."
msgstr ""
"Variabel ``aodh_apt_packages`` telah diubah namanya menjadi "
"``aodh_distro_packages``."

msgid ""
"The variable ``aodh_requires_pip_packages`` is no longer required and has "
"therefore been removed."
msgstr ""
"Variabel ``aodh_requires_pip_packages`` tidak lagi diperlukan dan karenanya "
"telah dihapus."

msgid ""
"The variable ``barbican_requires_pip_packages`` is no longer required and "
"has therefore been removed."
msgstr ""
"Variabel ``barbican_requires_pip_packages`` tidak lagi diperlukan dan "
"karenanya telah dihapus."

msgid ""
"The variable ``ceilometer_apt_packages`` has been renamed to "
"``ceilometer_distro_packages``."
msgstr ""
"Variabel ``ceilometer_apt_packages`` telah diubah namanya menjadi "
"``ceilometer_distro_packages``."

msgid ""
"The variable ``ceilometer_developer_mode_apt_packages`` has been renamed to "
"``ceilometer_developer_mode_distro_packages``."
msgstr ""
"Variabel ``ceilometer_developer_mode_apt_packages`` telah diubah namanya "
"menjadi ``ceilometer_developer_mode_distro_packages``."

msgid ""
"The variable ``cinder_apt_packages`` has been renamed to "
"``cinder_distro_packages``."
msgstr ""
"Variabel ``cinder_apt_packages`` telah diubah namanya menjadi "
"``cinder_distro_packages``."

msgid ""
"The variable ``cinder_lvm_volume_apt_packages`` has been renamed to "
"``cinder_lvm_volume_distro_packages``."
msgstr ""
"Variabel ``cinder_lvm_volume_apt_packages`` telah diubah namanya menjadi "
"``cinder_lvm_volume_distro_packages``."

msgid ""
"The variable ``cinder_requires_pip_packages`` is no longer required and has "
"therefore been removed."
msgstr ""
"Variabel ``cinder_requires_pip_packages`` tidak lagi diperlukan dan "
"karenanya telah dihapus."

msgid ""
"The variable ``cinder_volume_apt_packages`` has been renamed to "
"``cinder_volume_distro_packages``."
msgstr ""
"Variabel ``cinder_volume_apt_packages`` telah diubah namanya menjadi "
"``cinder_volume_distro_packages``."

msgid ""
"The variable ``cloudkitty_requires_pip_packages`` is no longer required and "
"has therefore been removed."
msgstr ""
"Variabel ``cloudkitty_requires_pip_packages`` tidak lagi diperlukan dan "
"karenanya telah dihapus."

msgid ""
"The variable ``designate_requires_pip_packages`` is no longer required and "
"has therefore been removed."
msgstr ""
"Variabel ``designate_requires_pip_packages`` tidak lagi diperlukan dan "
"karenanya telah dihapus."

msgid ""
"The variable ``galera_client_apt_packages`` has been replaced by "
"``galera_client_distro_packages``."
msgstr ""
"Variabel ``galera_client_apt_packages`` telah digantikan oleh "
"``galera_client_distro_packages``."

msgid ""
"The variable ``galera_packages`` has been renamed to "
"``galera_server_mariadb_distro_packages``."
msgstr ""
"Variabel ``galera_packages`` telah diubah namanya menjadi "
"``galera_server_mariadb_distro_packages``."

msgid ""
"The variable ``galera_pre_packages`` has been renamed to "
"``galera_server_required_distro_packages``."
msgstr ""
"Variabel ``galera_pre_packages`` telah diubah namanya menjadi "
"``galera_server_required_distro_packages``."

msgid ""
"The variable ``galera_xtrabackup_threads`` has been renamed to "
"``galera_mariabackup_threads`` to reflect the change in the SST provider."
msgstr ""
"Variabel ``galera_xtrabackup_threads`` telah diubah namanya menjadi "
"``galera_mariabackup_threads`` untuk mencerminkan perubahan pada penyedia "
"SST."

msgid ""
"The variable ``glance_apt_packages`` has been renamed to "
"``glance_distro_packages``."
msgstr ""
"Variabel ``glance_apt_packages`` telah diubah namanya menjadi "
"``glance_distro_packages``."

msgid ""
"The variable ``glance_requires_pip_packages`` is no longer required and has "
"therefore been removed."
msgstr ""
"Variabel ``glance_requires_pip_packages`` tidak lagi diperlukan dan "
"karenanya telah dihapus."

msgid ""
"The variable ``gnocchi_required_pip_packages`` was incorrectly named and has "
"been renamed to ``gnocchi_requires_pip_packages`` to match the standard "
"across all roles."
msgstr ""
"Variabel ``gnocchi_required_pip_packages`` salah nama dan telah diubah "
"namanya menjadi ``gnocchi_requires_pip_packages`` untuk mencocokkan standar "
"di semua role."

msgid ""
"The variable ``gnocchi_requires_pip_packages`` is no longer required and has "
"therefore been removed."
msgstr ""
"Variabel ``gnocchi_requires_pip_packages`` tidak lagi diperlukan dan "
"karenanya telah dihapus."

msgid ""
"The variable ``haproxy_packages`` has been renamed to "
"``haproxy_distro_packages``."
msgstr ""
"Variabel ``haproxy_packages`` telah diubah namanya menjadi "
"``haproxy_distro_packages``."

msgid ""
"The variable ``haproxy_pre_packages`` has been renamed to "
"``haproxy_required_distro_packages``."
msgstr ""
"Variabel ``haproxy_pre_packages`` telah diubah namanya menjadi "
"``haproxy_required_distro_packages``."

msgid ""
"The variable ``heat_apt_packages`` has been renamed to "
"``heat_distro_packages``."
msgstr ""
"Variabel ``heat_apt_packages`` telah diubah namanya menjadi "
"``heat_distro_packages``."

msgid ""
"The variable ``heat_requires_pip_packages`` is no longer required and has "
"therefore been removed."
msgstr ""
"Variabel ``heat_requires_pip_packages`` tidak lagi diperlukan dan karenanya "
"telah dihapus."

msgid ""
"The variable ``horizon_apt_packages`` has been renamed to "
"``horizon_distro_packages``."
msgstr ""
"Variabel ``horizon_apt_packages`` telah diubah namanya menjadi "
"``horizon_distro_packages``."

msgid ""
"The variable ``horizon_requires_pip_packages`` is no longer required and has "
"therefore been removed."
msgstr ""
"Variabel ``horizon_requires_pip_packages`` tidak lagi diperlukan dan "
"karenanya telah dihapus."

msgid ""
"The variable ``ironic_api_apt_packages`` has been renamed to "
"``ironic_api_distro_packages``."
msgstr ""
"Variabel ``ironic_api_apt_packages`` telah diubah namanya menjadi "
"``ironic_api_distro_packages``."

msgid ""
"The variable ``ironic_conductor_apt_packages`` has been renamed to "
"``ironic_conductor_distro_packages``."
msgstr ""
"Variabel ``ironic_conductor_apt_packages`` telah diubah namanya menjadi "
"``ironic_conductor_distro_packages``."

msgid ""
"The variable ``ironic_conductor_standalone_apt_packages`` has been renamed "
"to ``ironic_conductor_standalone_distro_packages``."
msgstr ""
"Variabel ``ironic_conductor_standalone_apt_packages`` telah diubah namanya "
"menjadi ``ironic_conductor_standalone_distro_packages``."

msgid ""
"The variable ``ironic_requires_pip_packages`` is no longer required and has "
"therefore been removed."
msgstr ""
"Variabel ``ironic_requires_pip_packages`` tidak lagi diperlukan dan "
"karenanya telah dihapus."

msgid ""
"The variable ``keepalived_uca_enable`` is deprecated, and replaced by "
"``keepalived_ubuntu_src``. The ``keepalived_uca_enable`` variable will be "
"removed in future versions of the keepalived role. The value of "
"``keepalived_ubuntu_src`` should be either \"uca\", \"ppa\", or \"native\", "
"for respectively installing from the Ubuntu Cloud archive, from keepalived "
"stable ppa, or not installing from an external source."
msgstr ""
"Variabel ``keepalived_uca_enable`` sudah usang, dan diganti dengan "
"``keepalived_ubuntu_src``. Variabel ``keepalived_uca_enable`` akan dihapus "
"di versi selanjutnya dari peran keepalived. Nilai ``keepalived_ubuntu_src`` "
"harus berupa \"uca\", \"ppa\", atau \"native\", untuk masing-masing "
"menginstal dari arsip Ubuntu Cloud, dari keepalived stable ppa, atau tidak "
"menginstal dari sumber eksternal."

msgid ""
"The variable ``keepalived_use_latest_stable`` is deprecated, and replaced by "
"``keepalived_package_state``. The ``keepalived_use_latest_stable`` variable "
"will be removed in future versions of the keepalived role. The value of "
"``keepalived_package_state`` should be either \"latest\" or \"present\"."
msgstr ""
"Variabel ``keepalived_use_latest_stable`` sudah usang, dan diganti dengan "
"``keepalived_package_state``. Variabel ``keepalived_use_latest_stable`` akan "
"dihapus di versi selanjutnya dari peran keepalived. Nilai "
"``keepalived_package_state`` harus berupa \"latest\" atau \"present\"."

msgid ""
"The variable ``keystone_apt_packages`` has been renamed to "
"``keystone_distro_packages``."
msgstr ""
"Variabel ``keystone_apt_packages`` telah diubah namanya menjadi "
"``keystone_distro_packages``."

msgid ""
"The variable ``keystone_developer_apt_packages`` has been renamed to "
"``keystone_developer_mode_distro_packages``."
msgstr ""
"Variabel ``keystone_developer_apt_packages`` telah diubah namanya menjadi "
"``keystone_developer_mode_distro_packages``."

msgid ""
"The variable ``keystone_idp_apt_packages`` has been renamed to "
"``keystone_idp_distro_packages``."
msgstr ""
"Variabel ``keystone_idp_apt_packages`` telah diubah namanya menjadi "
"``keystone_idp_distro_packages``."

msgid ""
"The variable ``keystone_requires_pip_packages`` is no longer required and "
"has therefore been removed."
msgstr ""
"Variabel ``keystone_requires_pip_packages`` tidak lagi diperlukan dan "
"karenanya telah dihapus."

msgid ""
"The variable ``keystone_sp_apt_packages`` has been renamed to "
"``keystone_sp_distro_packages``."
msgstr ""
"Variabel ``keystone_sp_apt_packages`` telah diubah namanya menjadi "
"``keystone_sp_distro_packages``."

msgid ""
"The variable ``lxc_apt_packages`` has been renamed to "
"``lxc_hosts_distro_packages``."
msgstr ""
"Variabel ``lxc_apt_packages`` telah diubah namanya menjadi "
"``lxc_hosts_distro_packages``."

msgid ""
"The variable ``lxc_cache_environment`` has been added. This dictionary can "
"be overridden by deployers to set HTTP proxy environment variables that will "
"be applied to all lxc container download tasks."
msgstr ""
"Variabel ``lxc_cache_environment`` telah ditambahkan. Kamus ini dapat "
"ditimpa oleh deployment untuk menetapkan variabel lingkungan proxy HTTP yang "
"akan diterapkan pada semua tugas unduhan kontainer lxc."

msgid ""
"The variable ``lxc_container_release`` has been removed from the ``lxc-"
"container-create.yml`` playbook as it is no longer consumed by the container "
"creation process."
msgstr ""
"Variabel ``lxc_container_release`` telah dihapus dari playbook ``lxc-"
"container-create.yml`` karena tidak lagi dikonsumsi oleh proses pembuatan "
"kontainer."

msgid ""
"The variable ``lxc_host_machine_volume_size`` is used to set the size of the "
"default sparse file as well as define a limit within the ``machinectl`` "
"quota system. When the ``machinectl`` quota system is enabled deployers "
"should appropriately set this value to the size of the container volume, "
"even when not using a sparse file."
msgstr ""
"Variabel ``lxc_host_machine_volume_size`` digunakan untuk mengatur ukuran "
"file sparse default serta menentukan batas dalam sistem kuota "
"``machinectl``. Ketika sistem kuota ``machinectl`` diaktifkan, deployer "
"harus dengan tepat mengatur nilai ini ke ukuran volume kontainer, bahkan "
"ketika tidak menggunakan file sparse."

msgid ""
"The variable ``lxc_host_machine_volume_size`` now accepts any valid size "
"modifier acceptable by ``truncate -s`` and ``machinectl set-limit``. prior "
"to this change the option assumed an integer was set for some value in "
"gigabytes. All acceptable values can be seen within the `documentation for "
"machinectl <https://www.freedesktop.org/software/systemd/man/machinectl."
"html#set-limit%20%5BNAME%5D%20BYTES>`_"
msgstr ""
"Variabel ``lxc_host_machine_volume_size`` sekarang menerima setiap pengubah "
"ukuran yang valid yang dapat diterima oleh ``truncate -s`` dan ``machinectl "
"set-limit``. Sebelum perubahan ini, opsi diasumsikan integer ditetapkan "
"untuk beberapa nilai dalam gigabytes. Semua nilai yang dapat diterima dapat "
"dilihat di dalam `documentation for machinectl <https://www.freedesktop.org/"
"software/systemd/man/machinectl.html#set-limit%20%5BNAME%5D%20BYTES>`_"

msgid ""
"The variable ``lxc_image_cache_server_mirrors`` has been added to the "
"\"lxc_hosts\" role. This is a list type variable and gives deployers the "
"ability to specify multiple lxc-image mirrors at the same time."
msgstr ""
"Variabel ``lxc_image_cache_server_mirrors`` telah ditambahkan ke peran "
"\"lxc_hosts\". Ini adalah variabel tipe daftar dan memberikan kemampuan pada "
"penelepon untuk menentukan beberapa mirror lxc-image secara bersamaan."

msgid ""
"The variable ``lxc_image_cache_server`` has been deprecated in the "
"\"lxc_hosts\" role. By default this value will pull the first item out of "
"``lxc_image_cache_server_mirrors`` list which is only done for compatibility "
"(legacy) purposes. The default string type variable, "
"``lxc_image_cache_server``, will be removed from the \"lxc_hosts\" role in "
"the in \"R\" release."
msgstr ""
"Variabel ``lxc_image_cache_server`` telah ditinggalkan dalam peran "
"\"lxc_hosts\". Secara default nilai ini akan menarik item pertama dari "
"daftar ``lxc_image_cache_server_mirrors`` yang hanya dilakukan untuk tujuan "
"kompatibilitas (legacy). Variabel tipe string default, "
"``lxc_image_cache_server``, akan dihapus dari peran \"lxc_hosts\" di rilis "
"\"R\"."

msgid ""
"The variable ``lxc_net_manage_iptables`` has been added. This variable can "
"be overridden by deployers if system wide iptables rules are already in "
"place or managed by deployers chioce."
msgstr ""
"Variabel ``lxc_net_manage_iptables`` telah ditambahkan. Variabel ini dapat "
"ditimpa oleh deployer jika aturan iptables sistem yang lebar sudah ada atau "
"dikelola oleh chioce deployers."

msgid ""
"The variable ``magnum_requires_pip_packages`` is no longer required and has "
"therefore been removed."
msgstr ""
"Variabel ``magnum_requires_pip_packages`` tidak lagi diperlukan dan "
"karenanya telah dihapus."

msgid ""
"The variable ``memcached_apt_packages`` has been renamed to "
"``memcached_distro_packages``."
msgstr ""
"Variabel ``memcached_apt_packages`` telah diubah namanya menjadi "
"``memcached_distro_packages``."

msgid ""
"The variable ``neutron_agent_mode`` has been removed from the ``os_neutron`` "
"role. The appropriate value for ``l3_agent.ini`` is now determined based on "
"the ``neutron_plugin_type`` and host group membership."
msgstr ""
"Variabel ``neutron_agent_mode`` telah dihapus dari peran ``os_neutron``. "
"Nilai yang sesuai untuk ``l3_agent.ini`` sekarang ditentukan berdasarkan "
"``neutron_plugin_type`` dan keanggotaan grup host."

msgid ""
"The variable ``neutron_apt_packages`` has been renamed to "
"``neutron_distro_packages``."
msgstr ""
"Variabel ``neutron_apt_packages`` telah diubah namanya menjadi "
"``neutron_distro_packages``."

msgid ""
"The variable ``neutron_apt_remove_packages`` has been renamed to "
"``neutron_remove_distro_packages``."
msgstr ""
"Variabel ``neutron_apt_remove_packages`` telah diubah namanya menjadi "
"``neutron_remove_distro_packages``."

msgid ""
"The variable ``neutron_dhcp_domain`` has been renamed to "
"``neutron_dns_domain``."
msgstr ""
"Variabel ``neutron_dhcp_domain`` telah diubah namanya menjadi "
"``neutron_dns_domain``."

msgid ""
"The variable ``neutron_driver_firewall`` has been removed. The appropriate "
"value for ``neutron.conf`` is now determined based on the "
"``neutron_plugin_type``."
msgstr ""
"Variabel ``neutron_driver_firewall`` telah dihapus. Nilai yang sesuai untuk "
"``neutron.conf`` sekarang ditentukan berdasarkan ``neutron_plugin_type``."

msgid ""
"The variable ``neutron_driver_interface`` has been removed. The appropriate "
"value for ``neutron.conf`` is now determined based on the "
"``neutron_plugin_type``."
msgstr ""
"Variabel ``neutron_driver_interface`` telah dihapus. Nilai yang sesuai untuk "
"``neutron.conf`` sekarang ditentukan berdasarkan ``neutron_plugin_type``."

msgid ""
"The variable ``neutron_lbaas_apt_packages`` has been renamed to "
"``neutron_lbaas_distro_packages``."
msgstr ""
"Variabel ``neutron_lbaas_apt_packages`` telah diubah namanya menjadi "
"``neutron_lbaas_distro_packages``."

msgid ""
"The variable ``neutron_linuxbridge`` has been removed as it is no longer "
"used."
msgstr ""
"Variabel ``neutron_linuxbridge`` telah dihapus karena tidak lagi digunakan."

msgid ""
"The variable ``neutron_ml2_mechanism_drivers`` has been removed. The "
"appropriate value for ml2_conf.ini is now determined based on the "
"``neutron_plugin_type``."
msgstr ""
"Variabel ``neutron_ml2_mechanism_drivers`` telah dihapus. Nilai yang sesuai "
"untuk ml2_conf.ini sekarang ditentukan berdasarkan ``neutron_plugin_type``."

msgid ""
"The variable ``neutron_requires_pip_packages`` is no longer required and has "
"therefore been removed."
msgstr ""
"Variabel ``neutron_requires_pip_packages`` tidak lagi diperlukan dan "
"karenanya telah dihapus."

msgid ""
"The variable ``neutron_service_names`` has been removed. A more efficient "
"way of determining the list of Neutron services for service restarts has "
"been implemented."
msgstr ""
"Variabel ``neutron_service_names`` telah dihapus. Cara yang lebih efisien "
"untuk menentukan daftar layanan Neutron untuk memulai kembali layanan telah "
"diterapkan."

msgid ""
"The variable ``neutron_vpnaas_apt_packages`` has been renamed to "
"``neutron_vpnaas_distro_packages``."
msgstr ""
"Variabel ``neutron_vpnaas_apt_packages`` telah diubah namanya menjadi "
"``neutron_vpnaas_distro_packages``."

msgid ""
"The variable ``nova_compute_pip_packages`` is no longer used and has been "
"removed."
msgstr ""
"Variabel ``nova_compute_pip_packages`` tidak lagi digunakan dan telah "
"dihapus."

msgid ""
"The variable ``nova_requires_pip_packages`` is no longer required and has "
"therefore been removed."
msgstr ""
"Variabel ``nova_requires_pip_packages`` tidak lagi diperlukan dan karenanya "
"telah dihapus."

msgid ""
"The variable ``octavia_ansible_endpoint_type`` has been removed. The "
"endpoint used for ansible tasks has been hard set to the 'admin' endpoint as "
"is commonly used across all OSA roles."
msgstr ""
"Variabel ``octavia_ansible_endpoint_type`` telah dihapus. Endpoint yang "
"digunakan untuk tugas ansible telah sulit diatur ke endpoint 'admin' seperti "
"yang biasa digunakan di semua peran OSA."

msgid ""
"The variable ``octavia_image_downloader`` has been removed. The image "
"download now uses the same host designated by the "
"``octavia_service_setup_host`` for the image download."
msgstr ""
"Variabel ``octavia_image_downloader`` telah dihapus. Pengunduhan image "
"sekarang menggunakan host yang sama yang ditunjuk oleh "
"``octavia_service_setup_host`` untuk pengunduhan image."

msgid ""
"The variable ``octavia_requires_pip_packages`` is no longer required and has "
"therefore been removed."
msgstr ""
"Variabel ``octavia_requires_pip_packages`` tidak lagi diperlukan dan "
"karenanya telah dihapus."

msgid ""
"The variable ``openstack_host_apt_packages`` has been renamed to "
"``openstack_host_distro_packages``."
msgstr ""
"Variabel ``openstack_host_apt_packages`` telah diubah namanya menjadi "
"``openstack_host_distro_packages``."

msgid ""
"The variable ``proxy_env_url`` is now used by the apt-cacher-ng jinja2 "
"template to set up an HTTP/HTTPS proxy if needed."
msgstr ""
"Variabel ``proxy_env_url`` sekarang digunakan oleh templat jinja2 apt-cacher-"
"ng untuk mengatur proxy HTTP/HTTPS jika diperlukan."

msgid ""
"The variable ``rabbitmq_monitoring_password`` has been added to "
"``user_secrets.yml``. If this variable does not exist, the RabbitMQ "
"monitoring user will not be created."
msgstr ""
"Variabel ``rabbitmq_monitoring_password`` telah ditambahkan ke "
"``user_secrets.yml``. Jika variabel ini tidak ada, pengguna pemantauan "
"RabbitMQ tidak akan dibuat."

msgid ""
"The variable ``repo_build_pip_extra_index`` has been removed. The "
"replacement list variable ``repo_build_pip_extra_indexes`` should be used "
"instead."
msgstr ""
"Variabel ``repo_build_pip_extra_index`` telah dihapus. Variabel daftar "
"pengganti ``repo_build_pip_extra_indexes`` harus digunakan sebagai gantinya."

msgid ""
"The variable ``repo_requires_pip_packages`` is no longer required and has "
"therefore been removed."
msgstr ""
"Variabel ``repo_requires_pip_packages`` tidak lagi diperlukan dan karenanya "
"telah dihapus."

msgid ""
"The variable ``repo_server_packages`` that defines the list of packages "
"required to install a repo server has been replaced by "
"``repo_server_distro_packages``."
msgstr ""
"Variabel ``repo_server_packages`` yang mendefinisikan daftar paket yang "
"diperlukan untuk menginstal server repo telah diganti oleh "
"``repo_server_distro_packages``."

msgid ""
"The variable ``rsyslog_client_packages`` has been replaced by "
"``rsyslog_client_distro_packages``."
msgstr ""
"Variabel ``rsyslog_client_packages`` telah digantikan oleh "
"``rsyslog_client_distro_packages``."

msgid ""
"The variable ``rsyslog_server_packages`` has been replaced by "
"``rsyslog_server_distro_packages``."
msgstr ""
"Variabel ``rsyslog_server_packages`` telah diganti oleh "
"``rsyslog_server_distro_packages``."

msgid ""
"The variable ``sahara_requires_pip_packages`` is no longer required and has "
"therefore been removed."
msgstr ""
"Variabel ``sahara_requires_pip_packages`` tidak lagi diperlukan dan "
"karenanya telah dihapus."

msgid ""
"The variable ``security_audit_apparmor_changes`` is now renamed to "
"``security_audit_mac_changes`` and is enabled by default. Setting "
"``security_audit_mac_changes`` to ``no`` will disable syscall auditing for "
"any changes to AppArmor policies (in Ubuntu) or SELinux policies (in CentOS)."
msgstr ""
"Variabel ``security_audit_apparmor_changes`` sekarang diubah namanya menjadi "
"``security_audit_mac_changes`` dan diaktifkan secara default. Mengatur "
"``security_audit_mac_changes`` ke `` no`` akan menonaktifkan audit syscall "
"untuk setiap perubahan pada kebijakan AppArmor (di Ubuntu) atau kebijakan "
"SELinux (dalam CentOS)."

msgid ""
"The variable ``security_sysctl_enable_tcp_syncookies`` has replaced "
"``security_sysctl_tcp_syncookies`` and it is now a boolean instead of an "
"integer.  It is still enabled by default, but deployers can disable TCP "
"syncookies by setting the following Ansible variable:"
msgstr ""
"Variabel ``security_sysctl_enable_tcp_syncookies`` telah menggantikan "
"``security_sysctl_tcp_syncookies`` dan sekarang menjadi boolean bukan "
"integer. Ini masih diaktifkan secara default, tetapi deployer dapat "
"menonaktifkan TCP syncookies dengan mengatur variabel Ansible berikut:"

msgid ""
"The variable ``swift_apt_packages`` has been renamed to "
"``swift_distro_packages``."
msgstr ""
"Variabel ``swift_apt_packages`` telah diubah namanya menjadi "
"``swift_distro_packages``."

msgid ""
"The variable ``swift_requires_pip_packages`` is no longer required and has "
"therefore been removed."
msgstr ""
"Variabel ``swift_requires_pip_packages`` tidak lagi diperlukan dan karenanya "
"telah dihapus."

msgid ""
"The variable ``tempest_image_dir_owner`` is removed in favour of using "
"default ansible user to create the image directory."
msgstr ""
"Variabel ``tempest_image_dir_owner`` dihapus karena menggunakan pengguna "
"yang dimungkinkan secara default untuk membuat direktori image."

msgid ""
"The variable ``tempest_image_downloader`` has been removed. The image "
"download now uses the same host designated by the "
"``tempest_service_setup_host`` for the image download."
msgstr ""
"Variabel ``tempest_image_downloader`` telah dihapus. Unduhan image sekarang "
"menggunakan host yang sama yang ditunjuk oleh ``tempest_service_setup_host`` "
"untuk unduhan image."

msgid ""
"The variable ``tempest_requires_pip_packages`` is no longer required and has "
"therefore been removed."
msgstr ""
"Variabel ``tempest_requires_pip_packages`` tidak lagi diperlukan dan "
"karenanya telah dihapus."

msgid ""
"The variable ``trove_conductor_workers`` can be configured for defining the "
"number of workers for the trove conductor service. The default value is half "
"the number of vCPUs available on the machine with a capping value of 16."
msgstr ""
"Variabel ``trove_conductor_workers`` dapat dikonfigurasi untuk menentukan "
"jumlah pekerja (worker) untuk layanan konduktor trove. Nilai default adalah "
"setengah dari jumlah vCPU yang tersedia di mesin dengan nilai pembatasan 16."

msgid ""
"The variable ``trove_requires_pip_packages`` is no longer required and has "
"therefore been removed."
msgstr ""
"Variabel ``trove_requires_pip_packages`` tidak lagi diperlukan dan karenanya "
"telah dihapus."

msgid ""
"The variable ``verbose`` has been removed. Deployers should rely on the "
"``debug`` var to enable higher levels of logging."
msgstr ""
"Variabel ``verbose`` telah dihapus. Deployer harus bergantung pada var "
"``debug`` untuk mengaktifkan tingkat logging yang lebih tinggi."

msgid ""
"The variable ``verbose`` has been removed. Deployers should rely on the "
"``debug`` var to enable higher levels of memcached logging."
msgstr ""
"Variabel ``verbose`` telah dihapus. Deployer harus bergantung pada var "
"``debug`` untuk mengaktifkan level lebih tinggi dari logging memcached."

msgid ""
"The variable `cinder_iscsi_helper` has been replaced by the new variable "
"which is `cinder_target_helper` due to the fact that iscsi_helper has been "
"deprecated in Cinder."
msgstr ""
"Variabel `cinder_iscsi_helper` telah digantikan oleh variabel baru yaitu "
"`cinder_target_helper` karena fakta bahwa iscsi_helper telah ditinggalkan "
"dalam Cinder."

msgid ""
"The variable used to store the mysql password used by the ironic service "
"account has been changed.  The following variable:"
msgstr ""
"Variabel yang digunakan untuk menyimpan kata sandi mysql yang digunakan oleh "
"akun layanan ironic telah diubah. Variabel berikut:"

msgid ""
"The variables ```galera_client_package_*``` and "
"```galera_client_apt_percona_xtrabackup_*``` have been removed from the role "
"as Xtrabackup is no longer deployed."
msgstr ""
"Variabel ```galera_client_package_*``` dan "
"```galera_client_apt_percona_xtrabackup_*``` telah dihapus dari peran karena "
"Xtrabackup tidak lagi digunakan."

msgid ""
"The variables ``aodh_requirements_git_repo`` and "
"``aodh_requirements_git_install_branch`` have been removed in favour of "
"using the URL/path to the upper-constraints file using the variable "
"``pip_install_upper_constraints`` instead."
msgstr ""
"Variabel ``aodh_requirements_git_repo`` dan "
"``aodh_requirements_git_install_branch`` telah dihapus mendukung pemakaian "
"URL/path ke file upper-constraints menggunakan variabel "
"``pip_install_upper_constraints`` sebagai gantinya."

msgid ""
"The variables ``barbican_requirements_git_repo`` and "
"``barbican_requirements_git_install_branch`` have been removed in favour of "
"using the URL/path to the upper-constraints file using the variable "
"``pip_install_upper_constraints`` instead."
msgstr ""
"Variabel ``barbican_requirements_git_repo`` dan "
"``barbican_requirements_git_install_branch`` telah dihapus mendukung "
"pemakaian URL/path ke file upper-constraints menggunakan variabel "
"``pip_install_upper_constraints`` sebagai gantinya."

msgid ""
"The variables ``ceilometer_oslomsg_rpc_servers`` and "
"``ceilometer_oslomsg_notify_servers`` have been removed in favour of using "
"``ceilometer_oslomsg_rpc_host_group`` and "
"``ceilometer_oslomsg_notify_host_group`` instead."
msgstr ""
"Variabel ``ceilometer_oslomsg_rpc_servers`` dan "
"``ceilometer_oslomsg_notify_servers`` telah dihapus mendukung pemakaian "
"``ceilometer_oslomsg_rpc_host_group`` dan "
"``ceilometer_oslomsg_notify_host_group`` sebagai gantinya."

msgid ""
"The variables ``ceilometer_requirements_git_repo`` and "
"``ceilometer_requirements_git_install_branch`` have been removed in favour "
"of using the URL/path to the upper-constraints file using the variable "
"``pip_install_upper_constraints`` instead."
msgstr ""
"Variabel ``ceilometer_requirements_git_repo`` dan "
"``ceilometer_requirements_git_install_branch`` telah dihapus mendukung "
"pemakaian URL/path ke file upper-constraints menggunakan variabel "
"``pip_install_upper_constraints`` sebagai gantinya."

msgid ""
"The variables ``cinder_requirements_git_repo`` and "
"``cinder_requirements_git_install_branch`` have been removed in favour of "
"using the URL/path to the upper-constraints file using the variable "
"``pip_install_upper_constraints`` instead."
msgstr ""
"Variabel ``cinder_requirements_git_repo`` dan "
"``cinder_requirements_git_install_branch`` telah dihapus mendukung pemakaian "
"URL/path ke file upper-constraints menggunakan variabel "
"``pip_install_upper_constraints`` sebagai gantinya."

msgid ""
"The variables ``cinder_sigkill_timeout`` and ``cinder_restart_wait`` have "
"been deprecated and will be removed in Pike."
msgstr ""
"Variabel ``cinder_sigkill_timeout`` dan ``cinder_restart_wait`` telah "
"ditinggalkan dan akan dihapus di Pike."

msgid ""
"The variables ``cinder_sigkill_timeout`` and ``cinder_restart_wait`` have "
"been removed. The previous default values have now been set in the template "
"directly and can be adjusted by using the ``cinder_*_init_overrides`` "
"variables which use the ``config_template`` task to change template defaults."
msgstr ""
"Variabel ``cinder_sigkill_timeout`` dan ``cinder_restart_wait`` telah "
"dihapus. Nilai-nilai default sebelumnya sekarang telah ditetapkan dalam "
"template secara langsung dan dapat disesuaikan dengan menggunakan variabel  "
"``cinder_*_init_overrides`` yang menggunakan tugas ``config_template`` untuk "
"mengubah default template."

msgid ""
"The variables ``cloudkitty_requirements_git_repo`` and "
"``cloudkitty_requirements_git_install_branch`` have been removed in favour "
"of using the URL/path to the upper-constraints file using the variable "
"``pip_install_upper_constraints`` instead."
msgstr ""
"Variabel ``cloudkitty_requirements_git_repo`` dan "
"``cloudkitty_requirements_git_install_branch`` telah dihapus karena "
"menggunakan URL/path ke file batasan atas menggunakan variabel "
"``pip_install_upper_constraints`` sebagai gantinya."

msgid ""
"The variables ``galera_client_apt_repo_url`` and "
"``galera_client_yum_repo_url`` are deprecated in favour of the common "
"variable ``galera_client_repo_url``."
msgstr ""
"Variabel ``galera_client_apt_repo_url`` dan ``galera_client_yum_repo_url`` "
"tidak digunakan lagi karena variabel umum ``galera_client_repo_url``."

msgid ""
"The variables ``glance_requirements_git_repo`` and "
"``glance_requirements_git_install_branch`` have been removed in favour of "
"using the URL/path to the upper-constraints file using the variable "
"``pip_install_upper_constraints`` instead."
msgstr ""
"Variabel ``glance_requirements_git_repo`` dan "
"``glance_requirements_git_install_branch`` telah dihapus mendukung pemakaian "
"URL/path ke file upper-constraints menggunakan variabel "
"``pip_install_upper_constraints`` sebagai gantinya."

msgid ""
"The variables ``gnocchi_requirements_git_repo`` and "
"``gnocchi_requirements_git_install_branch`` have been removed in favour of "
"using the URL/path to the upper-constraints file using the variable "
"``pip_install_upper_constraints`` instead."
msgstr ""
"Variabel ``gnocchi_requirements_git_repo`` dan "
"``gnocchi_requirements_git_install_branch`` telah dihapus mendukung "
"pemakaian URL/path ke file upper-constraints menggunakan variabel "
"``pip_install_upper_constraints`` sebagai gantinya."

msgid ""
"The variables ``haproxy_keepalived_(internal|external)_cidr`` now has a "
"default set to ``169.254.(2|1).1/24``. This is to prevent Ansible undefined "
"variable warnings. Deployers must set values for these variables for a "
"working haproxy with keepalived environment when using more than one haproxy "
"node."
msgstr ""
"Variabel ``haproxy_keepalived_(internal|external)_cidr`` sekarang memiliki "
"pengaturan default ke ``169.254.(2|1).1/24``. Ini untuk mencegah peringatan "
"variabel yang tidak terdefinisi Ansible. Deployer harus menetapkan nilai "
"variabel ini untuk haproxy yang berfungsi dengan lingkungan keepalived "
"ketika menggunakan lebih dari satu node haproxy."

msgid ""
"The variables ``heat_requirements_git_repo`` and "
"``heat_requirements_git_install_branch`` have been removed in favour of "
"using the URL/path to the upper-constraints file using the variable "
"``pip_install_upper_constraints`` instead."
msgstr ""
"Variabel ``heat_requirements_git_repo`` dan "
"``heat_requirements_git_install_branch`` telah dihapus mendukung pemakaian "
"URL/path ke file upper-constraints menggunakan variabel "
"``pip_install_upper_constraints`` sebagai gantinya."

msgid ""
"The variables ``horizon_requirements_git_repo`` and "
"``horizon_requirements_git_install_branch`` have been removed in favour of "
"using the URL/path to the upper-constraints file using the variable "
"``pip_install_upper_constraints`` instead."
msgstr ""
"Variabel ``horizon_requirements_git_repo`` dan "
"``horizon_requirements_git_install_branch`` telah dihapus mendukung "
"pemakaian URL/path ke file upper-constraints menggunakan variabel "
"``pip_install_upper_constraints`` sebagai gantinya."

msgid ""
"The variables ``ironic_requirements_git_repo`` and "
"``ironic_requirements_git_install_branch`` have been removed in favour of "
"using the URL/path to the upper-constraints file using the variable "
"``pip_install_upper_constraints`` instead."
msgstr ""
"Variabel ``ironic_requirements_git_repo`` dan "
"``ironic_requirements_git_install_branch`` telah dihapus mendukung pemakaian "
"URL/path ke file upper-constraints menggunakan variabel "
"``pip_install_upper_constraints`` sebagai gantinya."

msgid ""
"The variables ``keystone_apache_enabled`` and ``keystone_mod_wsgi_enabled`` "
"have been removed and replaced with a single variable "
"``keystone_web_server`` to optionally set the web server used for keystone."
msgstr ""
"Variabel ``keystone_apache_enabled`` dan ``keystone_mod_wsgi_enabled`` telah "
"dihapus dan diganti dengan variabel tunggal ``keystone_web_server`` untuk "
"secara opsional mengatur server web yang digunakan untuk keystone."

msgid ""
"The variables ``keystone_memcached_servers`` and "
"``keystone_cache_backend_argument`` have been deprecated in favor of "
"``keystone_cache_servers``, a list of servers for caching purposes."
msgstr ""
"Variabel ``keystone_memcached_servers`` dan "
"``keystone_cache_backend_argument`` telah tidak digunakan lagi mendukung "
"``keystone_cache_servers``, daftar server untuk tujuan caching."

msgid ""
"The variables ``keystone_requirements_git_repo`` and "
"``keystone_requirements_git_install_branch`` have been removed in favour of "
"using the URL/path to the upper-constraints file using the variable "
"``pip_install_upper_constraints`` instead."
msgstr ""
"Variabel ``keystone_requirements_git_repo`` dan "
"``keystone_requirements_git_install_branch`` telah dihapus mendukung "
"pemakaian URL/path ke file the upper-constraints menggunakan variabel "
"``pip_install_upper_constraints`` sebagai gantinya."

msgid ""
"The variables ``magnum_requirements_git_repo`` and "
"``magnum_requirements_git_install_branch`` have been removed in favour of "
"using the URL/path to the upper-constraints file using the variable "
"``pip_install_upper_constraints`` instead."
msgstr ""
"Variabel `` magnum_requirements_git_repo`` dan "
"``magnum_requirements_git_install_branch`` telah dihapus mendukung pemakaian "
"URL/path ke file the upper-constraints menggunakan variabel "
"``pip_install_upper_constraints`` sebagai gantinya."

msgid ""
"The variables ``neutron_requirements_git_repo`` and "
"``neutron_requirements_git_install_branch`` have been removed in favour of "
"using the URL/path to the upper-constraints file using the variable "
"``pip_install_upper_constraints`` instead."
msgstr ""
"Variabel ``neutron_requirements_git_repo`` dan "
"``neutron_requirements_git_install_branch`` telah dihapus karena menggunakan "
"URL / path ke file batasan atas menggunakan variabel "
"``pip_install_upper_constraints`` sebagai gantinya."

msgid ""
"The variables ``nova_lxd_requirements_git_repo`` and "
"``nova_lxd_requirements_git_install_branch`` have been removed in favour of "
"using the URL/path to the upper-constraints file using the variable "
"``pip_install_upper_constraints`` instead."
msgstr ""
"Variabel ``nova_lxd_requirements_git_repo`` dan "
"``nova_lxd_requirements_git_install_branch`` telah dihapus mendukung "
"pemakaian URL/path ke file the upper-constraints menggunakan variabel "
"``pip_install_upper_constraints`` sebagai gantinya."

msgid ""
"The variables ``nova_requirements_git_repo`` and "
"``nova_requirements_git_install_branch`` have been removed in favour of "
"using the URL/path to the upper-constraints file using the variable "
"``pip_install_upper_constraints`` instead."
msgstr ""
"Variabel ``nova_requirements_git_repo`` dan "
"``nova_requirements_git_install_branch`` telah dihapus mendukung pemakaian "
"URL/path ke file the upper-constraints menggunakan variabel "
"``pip_install_upper_constraints`` sebagai gantinya."

msgid ""
"The variables ``nova_scheduler_use_baremetal_filters`` and "
"``nova_metadata_host`` have been removed, matching upstream nova changes. "
"The ``nova_virt_types`` dict no longer needs the "
"``nova_scheduler_use_baremetal_filters`` and ``nova_firewall_driver`` keys "
"as well."
msgstr ""
"Variabel ``nova_scheduler_use_baremetal_filters`` dan ``nova_metadata_host`` "
"telah dihapus, sesuai dengan perubahan nova hulu. Pustaka "
"``nova_virt_types`` tidak lagi membutuhkan kunci "
"``nova_scheduler_use_baremetal_filters`` dan juga ``nova_firewall_driver``."

msgid ""
"The variables ``rally_requirements_git_repo`` and "
"``rally_requirements_git_install_branch`` have been removed in favour of "
"using the URL/path to the upper-constraints file using the variable "
"``pip_install_upper_constraints`` instead."
msgstr ""
"Variabel ``rally_requirements_git_repo`` dan "
"``rally_requirements_git_install_branch`` telah dihapus mendukung pemakaian "
"URL/path ke file the upper-constraints menggunakan variabel "
"``pip_install_upper_constraints`` sebagai gantinya."

msgid ""
"The variables ``sahara_requirements_git_repo`` and "
"``sahara_requirements_git_install_branch`` have been removed in favour of "
"using the URL/path to the upper-constraints file using the variable "
"``pip_install_upper_constraints`` instead."
msgstr ""
"Variabel ``sahara_requirements_git_repo`` dan "
"``sahara_requirements_git_install_branch`` telah dihapus mendukung pemakaian "
"URL/path ke file the upper-constraints  menggunakan variabel "
"``pip_install_upper_constraints`` sebagai gantinya."

msgid ""
"The variables ``swift_requirements_git_repo`` and "
"``swift_requirements_git_install_branch`` have been removed in favour of "
"using the URL/path to the upper-constraints file using the variable "
"``pip_install_upper_constraints`` instead."
msgstr ""
"Variabel ``swift_requirements_git_repo`` dan "
"``swift_requirements_git_install_branch`` telah dihapus mendukung pemakaian "
"URL/path ke file the upper-constraints menggunakan variabel "
"``pip_install_upper_constraints`` sebagai gantinya."

msgid ""
"The variables ``tempest_requirements_git_repo`` and "
"``tempest_requirements_git_install_branch`` have been removed in favour of "
"using the URL/path to the upper-constraints file using the variable "
"``pip_install_upper_constraints`` instead."
msgstr ""
"Variabel ``tempest_requirements_git_repo`` dan "
"``tempest_requirements_git_install_branch`` telah dihapus mendukung "
"pemakaian URL/path ke file the upper-constraints  menggunakan variabel "
"``pip_install_upper_constraints`` sebagai gantinya."

msgid ""
"The variables ``trove_requirements_git_repo`` and "
"``trove_requirements_git_install_branch`` have been removed in favour of "
"using the URL/path to the upper-constraints file using the variable "
"``pip_install_upper_constraints`` instead."
msgstr ""
"Variabel ``trove_requirements_git_repo`` dan "
"``trove_requirements_git_install_branch`` telah dihapus mendukung pemakaian "
"URL/path ke file the upper-constraints menggunakan variabel "
"``pip_install_upper_constraints`` sebagai gantinya."

msgid ""
"The variables beginning with ``openstack_host_systat_`` in the "
"openstack_hosts role have been renamed to ``openstack_host_sysstat_``.  This "
"was done to better reflect their dependency to sysstat."
msgstr ""
"Variabel yang dimulai dengan ``openstack_host_systat_`` dalam peran "
"openstack_hosts telah diubah namanya menjadi ``openstack_host_sysstat_``. "
"Ini dilakukan untuk lebih mencerminkan ketergantungan mereka pada sysstat."

msgid ""
"The variables used to produce the ``/etc/openstack-release`` file have been "
"changed in order to improve consistency in the name spacing according to "
"their purpose."
msgstr ""
"Variabel yang digunakan untuk menghasilkan file  ``/etc/openstack-release`` "
"telah diubah untuk meningkatkan konsistensi dalam spasi nama (name spacing) "
"sesuai dengan tujuannya."

msgid ""
"The vars plugin ``override_folder.py`` has been removed. With the move to "
"Ansible 2.4 [\"https://review.openstack.org/#/c/522778\"] this plugin is no "
"longer required. The functionality this plugin provided has been replaced "
"with the native Ansible inventory plugin."
msgstr ""
"Plugin vars ``override_folder.py`` telah dihapus. Dengan pindah ke Ansible "
"2.4 [\"https://review.openstack.org/#/c/522778\"] plugin ini tidak lagi "
"diperlukan. Fungsionalitas yang disediakan plugin ini telah diganti dengan "
"plugin inventory native Ansible."

msgid ""
"The vars to set ``source_sample_interval`` for the ``os_ceilometer`` role "
"are deprecated and will be removed in the Queen cycle. To override these "
"variables after Queen, utilize the ``ceilometer_pipeline_yaml_overrides`` "
"file."
msgstr ""
"Vars untuk mengatur ``source_sample_interval`` untuk peran ``os_ceilometer`` "
"sudah usang dan akan dihapus dalam siklus Queen. Untuk mengganti variabel "
"ini setelah Queen, gunakan file ``ceilometer_pipeline_yaml_overrides``."

msgid "The version of Erlang is kept constant using yum's versionlock plugin."
msgstr "Versi Erlang dijaga konstan menggunakan plugin versionlock yum."

msgid ""
"The watcher dashboard is available in Horizon. Deployers can enable the "
"panel by setting the following Ansible variable:"
msgstr ""
"Dasbor watcher tersedia di Horizon. Deployer dapat mengaktifkan panel dengan "
"mengatur variabel Ansible berikut:"

msgid ""
"The workaround of requiring the addition of gnocchiclient to the "
"``repo_build_upper_constraints_overrides`` variable is no longer required. "
"The appropriate constraints have been implemented as a global pin."
msgstr ""
"Penyelesaian yang membutuhkan penambahan gnocchiclient ke variabel "
"``repo_build_upper_constraints_overrides`` tidak lagi diperlukan. Kendala "
"yang sesuai telah diterapkan sebagai pin global."

msgid ""
"The zun dashboard is available in Horizon. Deployers can enable the panel by "
"setting the following Ansible variable:"
msgstr ""
"Dasbor zun tersedia di Horizon. Deployer dapat mengaktifkan panel dengan "
"mengatur variabel Ansible berikut:"

msgid ""
"There is a bug in the version of keepalived which ships with Ubuntu 14.04 "
"which results in all backup nodes having the same priority. This causes the "
"automatic failover to fail when more than two keepalived hosts are "
"configured. To work around this issue it is recommended that deployers limit "
"the number of keepalived hosts to no more than two, or that each host is "
"configured with different priorities."
msgstr ""
"Ada bug dalam versi keepalived yang dikirimkan bersama Ubuntu 14.04 yang "
"menghasilkan semua node cadangan yang memiliki prioritas yang sama. Hal ini "
"menyebabkan automatic failover gagal ketika lebih dari dua host yang "
"disimpan tetap dikonfigurasi. Untuk mengatasi masalah ini, disarankan bahwa "
"para deployer membatasi jumlah host yang disimpan tidak lebih dari dua, atau "
"bahwa setiap host dikonfigurasi dengan prioritas yang berbeda."

msgid ""
"There is a new default configuration for keepalived, supporting more than 2 "
"nodes."
msgstr ""
"Ada konfigurasi default baru untuk keepalived, mendukung lebih dari 2 node."

msgid ""
"There is a new default configuration for keepalived. When running the "
"haproxy playbook, the configuration change will cause a keepalived restart "
"unless the deployer has used a custom configuration file. The restart will "
"cause the virtual IP addresses managed by keepalived to be briefly "
"unconfigured, then reconfigured."
msgstr ""
"Ada konfigurasi default baru untuk keepalived. Saat menjalankan haproxy "
"playbook, perubahan konfigurasi akan menyebabkan restart tetap hidup kecuali "
"jika deployer telah menggunakan file konfigurasi kustom. Restart akan "
"menyebabkan alamat IP virtual yang dikelola oleh keepalived secara singkat "
"tidak dikonfigurasi, kemudian dikonfigurasi ulang."

msgid ""
"There is currently an Ansible bug in regards to ``HOSTNAME``. If the host ``."
"bashrc`` holds a var named ``HOSTNAME``, the container where the "
"``lxc_container`` module attaches will inherit this var and potentially set "
"the wrong ``$HOSTNAME``. See `the Ansible fix <https://github.com/ansible/"
"ansible/pull/22246>`_ which will be released in Ansible version 2.3."
msgstr ""
"Saat ini ada bug Ansible terkait ``HOSTNAME``. Jika host ``.bashrc`` "
"memegang var bernama ``HOSTNAME``, kontainer tempat modul ``lxc_container`` "
"dilampirkan akan mewarisi var ini dan berpotensi mengatur ``$HOSTNAME`` yang "
"salah. Lihat `the Ansible fix  <https://github.com/ansible/ansible/"
"pull/22246>` _ yang akan dirilis dalam versi Ansible 2.3."

msgid ""
"There is now a fix in place that ensures any sysctl configuration with "
"``enabled: no`` will be skipped and the configuration will be left unaltered "
"on the system."
msgstr ""
"Sekarang ada perbaikan di tempat yang memastikan konfigurasi sysctl dengan "
"``enabled: no`` akan dilewati dan konfigurasi akan dibiarkan tidak diubah "
"pada sistem."

msgid ""
"There is now experimental support to deploy OpenStack-Ansible on CentOS 7 "
"for both development and test environments."
msgstr ""
"Sekarang ada dukungan eksperimental untuk menggunakan OpenStack-Ansible di "
"CentOS 7 untuk pengembangan dan lingkungan pengujian."

msgid ""
"There was previously an environment variable (``ANSIBLE_ROLE_FETCH_MODE``) "
"to set whether the roles in ansible-role-requirements.yml were fetched using "
"ansible-galaxy or using git, however the default has been git for some time "
"ansible since the use of the ``ceph-ansible`` respoitory for ceph "
"deployment, using ansible-galaxy to download the roles does not work "
"properly. This functionality has therefore been removed."
msgstr ""
"Sebelumnya ada variabel lingkungan (``ANSIBLE_ROLE_FETCH_MODE``) untuk "
"mengatur apakah role dalam ansible-role-requirements.yml diambil menggunakan "
"ansible-galaxy atau menggunakan git, namun defaultnya telah git selama "
"beberapa waktu ansible karena  penggunaan respoitory ``ceph-ansible`` untuk "
"deployment ceph, menggunakan ansible-galaxy untuk mengunduh role tidak "
"berfungsi dengan baik. Fungsi ini karenanya telah dihapus."

msgid ""
"These kernel parameters are now set to ``1`` on all hosts by the "
"``openstack_hosts`` role, which ensures that bridge traffic is always sent "
"through iptables."
msgstr ""
"Parameter kernel ini sekarang disetel ke ``1`` pada semua host oleh role "
"``openstack_hosts``, yang memastikan bahwa lalu lintas jembatan (bridge "
"traffic) selalu dikirim melalui iptables."

msgid ""
"This also allows the initialization to become a blocking process and Ansible "
"will wait for the initialization to complete prior to running the next task."
msgstr ""
"Ini juga memungkinkan inisialisasi menjadi proses pemblokiran dan Ansible "
"akan menunggu inisialisasi selesai sebelum menjalankan tugas berikutnya."

msgid ""
"This consolidates the amphora image tasks in a common file and adds a way to "
"download an amphora image from an artefact storage over http(s). With the "
"Octavia team providing test images the tests were modified to not build "
"images any longer but download them."
msgstr ""
"Ini mengkonsolidasikan tugas image amphora dalam file umum dan menambahkan "
"cara untuk mengunduh image amphora dari penyimpanan artefak melalui http(s). "
"Dengan tim Octavia yang menyediakan image uji, pengujian tersebut "
"dimodifikasi untuk tidak membuat image lagi tetapi mengunduhnya."

msgid ""
"This has been resolved by introducing a /dev/random and /dev/urandom inside "
"the chroot-ed environment."
msgstr ""
"Ini telah diselesaikan dengan memperkenalkan /dev/random dan /dev/urandom di "
"dalam lingkungan chroot-ed."

msgid ""
"This issue can be resolved either by upgrading the environment to a recent "
"OpenStack-Ansible Ocata release, or by doing the following."
msgstr ""
"Masalah ini dapat diatasi dengan memutakhirkan lingkungan ke rilis OpenStack-"
"Ansible Ocata terbaru, atau dengan melakukan hal berikut."

msgid "This issue has been resolved in the 14.2.15 release."
msgstr "Masalah ini telah diatasi dalam rilis 14.2.15."

msgid "This issue has been resolved in the 15.1.17 release."
msgstr "Masalah ini telah diatasi dalam rilis 15.1.17."

msgid "This issue has been resolved in the 16.0.8 release."
msgstr "Masalah ini telah diatasi dalam rilis 16.0.8."

msgid ""
"This results in any upgrades to the newton software to never end up running "
"the version of neutron software as intended. This can be seen by observing "
"that the running processes are still using the older software venv."
msgstr ""
"Ini menghasilkan setiap upgrade ke perangkat lunak newton agar tidak pernah "
"menjalankan versi perangkat lunak neutron sebagaimana dimaksud. Ini dapat "
"dilihat dengan mengamati bahwa proses yang berjalan masih menggunakan "
"perangkat lunak yang lebih lama."

msgid ""
"This role assumes that there is a network named \"public|private\" and a "
"subnet named \"public|private-subnet\". These names are made configurable by "
"the addition of two sets of variables; ``tempest_public_net_name`` and "
"``tempest_public_subnet_name`` for public networks and "
"``tempest_private_net_name`` and ``tempest_private_subnet_name`` for private "
"networks This addresses `bug 1588818 <https://bugs.launchpad.net/openstack-"
"ansible/+bug/1588818>`_"
msgstr ""
"Role ini mengasumsikan bahwa ada jaringan bernama \"public|private\" dan "
"subnet bernama \"public|private-subnet\". Nama ini dibuat dapat "
"dikonfigurasi dengan penambahan dua set variabel; "
"``tempest_public_net_name`` dan ``tempest_public_subnet_name`` untuk "
"jaringan publik dan ``tempest_private_net_name`` dan "
"``tempest_private_subnet_name`` untuk jaringan pribadi. Alamat ini  `bug "
"1588818 <https://bugs.launchpad.net/openstack-ansible/+bug/1588818>`_"

msgid ""
"This role now optionally enables your compute nodes' KVM kernel module "
"nested virtualization capabilities, by setting nova_nested_virt_enabled to "
"true. Depending on your distribution and libvirt version, you might need to "
"set additional variables to fully enabled nested virtualization. For "
"details, please see https://docs.openstack.org/nova/latest/admin/"
"configuration/hypervisor-kvm.html#nested-guest-support."
msgstr ""
"Role ini sekarang secara opsional memungkinkan node komputasi Anda punya "
"kemampuan virtualisasi tersarang modul kernel KVM, dengan mengatur "
"nova_nested_virt_enabled menjadi true. Bergantung pada distribusi dan versi "
"libvirt Anda, Anda mungkin perlu mengatur variabel tambahan untuk "
"virtualisasi bersarang (nested) yang diaktifkan sepenuhnya. Untuk detailnya, "
"silakan lihat https://docs.openstack.org/nova/latest/admin/configuration/"
"hypervisor-kvm.html#nested-guest-support."

msgid ""
"This upgrade task is related to `bug 1582279 <https://bugs.launchpad.net/"
"openstack-ansible/+bug/1582279>`_."
msgstr ""
"Tugas pemutakhiran ini terkait dengan `bug 1582279 <https://bugs.launchpad."
"net/openstack-ansible/+bug/1582279>`_."

msgid ""
"This upgrade task is related to `bug 1594584 <https://bugs.launchpad.net/"
"openstack-ansible/+bug/1594584>`_."
msgstr ""
"Tugas pemutakhiran ini terkait dengan `bug 1594584 <https://bugs.launchpad."
"net/openstack-ansible/+bug/1594584>`_."

msgid ""
"This version is the minimum version necessary to upgrade from Pike to Queens "
"for deployers using ANSIBLE_ROLE_FETCH_MODE=\"git-clone\"."
msgstr ""
"Versi ini adalah versi minimum yang diperlukan untuk meningkatkan dari Pike "
"ke Queens untuk deployer menggunakan  ANSIBLE_ROLE_FETCH_MODE=\"git-clone\"."

msgid ""
"This will also cause the old error logs in ``/var/log/mysql_logs`` in the "
"container to become unavailable since the new bind mount is mounted on top "
"of the existing logs directory within the container. If these logs are "
"critical for a deployer to keep, the deployer should:"
msgstr ""
"Ini juga akan menyebabkan log kesalahan lama di ``/var/log/mysql_logs`` "
"dalam kontainer menjadi tidak tersedia karena bind mount baru dipasang di "
"atas direktori log yang ada di dalam kontainer. Jika log ini penting untuk "
"disimpan oleh seorang deployer, deployer harus:"

msgid ""
"To ensure the deployment system remains clean the Ansible execution "
"environment is contained within a virtual environment. The virtual "
"environment is created at \"/opt/ansible-runtime\" and the \"ansible.*\" CLI "
"commands are linked within /usr/local/bin to ensure there is no interruption "
"in the deployer workflow."
msgstr ""
"Untuk memastikan sistem deployment tetap bersih, lingkungan eksekusi Ansible "
"termuat dalam lingkungan virtual. Lingkungan virtual dibuat di  \"/opt/"
"ansible-runtime\" dan \"ansible.*\" Perintah CLI ditautkan dalam /usr/local/"
"bin untuk memastikan tidak ada gangguan dalam alur kerja penggunaan."

msgid ""
"To fix this issue the ``pip.conf`` file needs to be removed from all "
"repository servers. The upgrade playbook ``repo-server-pip-conf-removal."
"yml`` will remove the pip.conf file from the repository servers if it's "
"found."
msgstr ""
"Untuk memperbaiki masalah ini, file ``pip.conf`` perlu dihapus dari semua "
"server repositori. Upgrade playbook ``repo-server-pip-conf-removal.yml`` "
"akan menghapus file pip.conf dari server repositori jika ditemukan."

msgid ""
"To provide compatibility with Centos-8 the LXC cache preparation has been "
"greatly simplified to remove the requirement for machinectl and btrfs, which "
"is a combination not available on Centos-8. This has the side effect of "
"machinectl no longer being a supported backing store for LXC."
msgstr ""
"Untuk memberikan kompatibilitas dengan Centos-8 persiapan cache LXC telah "
"sangat disederhanakan untuk menghapus persyaratan untuk machinectl dan "
"btrfs, yang merupakan kombinasi yang tidak tersedia pada Centos-8. Ini "
"memiliki efek samping dari machinectl tidak lagi menjadi  supported backing "
"store untuk LXC."

msgid ""
"To work around this issue, the recommendation is to set the following "
"overrides in ``/etc/openstack_deploy/user_variables.yml`` to ensure that the "
"last known good version of MariaDB is used."
msgstr ""
"Untuk mengatasi masalah ini, rekomendasinya adalah mengatur override berikut "
"di ``/etc/openstack_deploy/user_variables.yml`` untuk memastikan bahwa versi "
"MariaDB yang baik dan terakhir diketahui digunakan."

msgid "Train Series Release Notes"
msgstr "Catatan Rilis Seri Train"

msgid ""
"Two Neutron variables have been deprecated and are now removed from "
"OpenStack-Ansible - ``neutron_l3_router_delete_namespaces`` and "
"``neutron_dhcp_delete_namespaces``."
msgstr ""
"Dua variabel Neutron telah ditinggalkan dan sekarang dihapus dari OpenStack-"
"Ansible - ``neutron_l3_router_delete_namespaces`` dan "
"``neutron_dhcp_delete_namespaces``."

msgid ""
"Two new options were added for handling authentication with Swift storage "
"backends - ``glance_swift_store_user_domain`` and "
"``glance_swift_store_project_domain``. Both are set to ``default`` and can "
"be adjusted if deployers use a different Keystone domain to authenticate to "
"swift."
msgstr ""
"Dua opsi baru ditambahkan untuk menangani otentikasi dengan backend "
"penyimpanan Swift - ``glance_swift_store_user_domain`` dan "
"``glance_swift_store_project_domain``. Keduanya diatur ke ``default`` dan "
"dapat disesuaikan jika deployer menggunakan domain Keystone yang berbeda "
"untuk mengautentikasi ke swift."

msgid ""
"Two new variables (`rabbitmq_async_threads` and `rabbitmq_process_limit`) "
"have been added to the openstack-ansible-rabbitmq_server role. The variable "
"`rabbitmq_async_threads` limits the number of asynchronous threads for file "
"and socket I/O. The variable `rabbitmq_process_limit` limits the overall "
"number of supported processes inside the erlang VM."
msgstr ""
"Dua variabel baru (`rabbitmq_async_threads` dan` rabbitmq_process_limit`) "
"telah ditambahkan ke peran openstack-ansible-rabbitmq_server. Variabel "
"`rabbitmq_async_threads` membatasi jumlah asynchronous thread untuk file dan "
"soket I/O. Variabel `rabbitmq_process_limit` membatasi jumlah keseluruhan "
"proses yang didukung di dalam VM erlang."

msgid ""
"Ubuntu Cloud Archive (UCA) was installed by default on repo, nova, neutron "
"nodes, but not on the other nodes. From now on, we are using UCA everywhere "
"to avoid dependency issues (like having virtualenv build with incompatible "
"versions of python-cryptography). The same reasoning applies to CentOS and "
"RDO packages."
msgstr ""
"Ubuntu Cloud Archive (UCA) diinstal secara default pada repo, nova, node "
"neutron, tetapi tidak pada node lain. Mulai sekarang, kami menggunakan UCA "
"di mana-mana untuk menghindari masalah ketergantungan (seperti membangun "
"virtualenv dengan versi python-cryptography yang tidak kompatibel). Alasan "
"yang sama berlaku untuk paket CentOS dan RDO."

msgid ""
"Ubuntu Trusty (14.04) support is now removed from the os_cloudkitty role."
msgstr ""
"Dukungan Ubuntu Trusty (14.04) sekarang dihapus dari peran os_cloudkitty."

msgid ""
"Ubuntu has 4 different 'components' - main, universe, multiverse and "
"restricted:"
msgstr ""
"Ubuntu memiliki 4 'components' yang berbeda - main, universe, multiverse and "
"restricted:"

msgid ""
"Universe: Community maintained software, i.e. not officially supported "
"software."
msgstr ""
"Universe: Perangkat lunak yang dikelola komunitas, yaitu perangkat lunak "
"yang tidak didukung secara resmi."

msgid "Upgrade Notes"
msgstr "Catatan Upgrade"

msgid ""
"Upgrades will not replace entries in the /etc/openstack_deploy/env.d "
"directory, though new versions of OpenStack-Ansible will now use the shipped "
"env.d as a base, which may alter existing deployments."
msgstr ""
"Upgrade tidak akan menggantikan entri di direktori /etc/openstack_deploy/env."
"d, meskipun versi baru OpenStack-Ansible sekarang akan menggunakan env.d "
"yang dikirimkan sebagai basis, yang dapat mengubah penyebaran yang ada."

msgid ""
"Upgrading from Newton to Ocata will now correctly add existing Nova "
"instances to the ``nova_cell1_name`` cell. For more information see `bug "
"1682169 <https://bugs.launchpad.net/openstack-ansible/+bug/1682169>`_."
msgstr ""
"Upgrading dari Newton ke Ocata sekarang akan dengan benar menambahkan "
"instance Nova yang ada ke sel ``nova_cell1_name``. Untuk informasi lebih "
"lanjut, lihat `bug 1682169 <https://bugs.launchpad.net/openstack-ansible/"
"+bug/1682169>`_."

msgid "Upstream is now depending on version 2.1.0 of ldappool."
msgstr "Upstream sekarang tergantung pada versi 2.1.0 dari ldappool."

msgid ""
"Usage of tempest_tempest_conf_overrides, where it could have 2 different "
"formats. one for config_template and another one for tempestconf.profile Now "
"for tempestconf.profile overrides `tempest_tempestconf_profile_overrides` "
"variable should be used."
msgstr ""
"Penggunaan  tempest_tempest_conf_overrides, di mana ia bisa memiliki 2 "
"format berbeda. satu untuk config_template dan satu lagi untuk tempestconf."
"profile Now untuk override tempestconf.profile "
"`tempest_tempestconf_profile_overrides` variabel harus digunakan."

msgid ""
"Users should purge the 'ntp' package from their hosts if ceph-ansible is "
"enabled. ceph-ansible previously was configured to install ntp by default "
"which conflicts with the OSA ansible-hardening role chrony service."
msgstr ""
"Pengguna harus membersihkan paket 'ntp' dari host mereka jika mungkin "
"diaktifkan. ceph-ansible sebelumnya dikonfigurasikan untuk menginstal ntp "
"secara default yang bertentangan dengan layanan kroni role ansible-hardening "
"OSA."

msgid "Ussuri Series Release Notes"
msgstr "Catatan Rilis Seri Ussuri"

msgid ""
"VPNaaS dashboard is again available in Horizon. Deployers can enable the "
"panel by setting the following Ansible variable:"
msgstr ""
"Dasbor VPNaaS tersedia lagi di Horizon. Deployer dapat mengaktifkan panel "
"dengan mengatur variabel Ansible berikut:"

msgid ""
"Variable ``ceph_extra_confs`` has been expanded to support retrieving "
"additional ceph.conf and keyrings from multiple ceph clusters automatically."
msgstr ""
"Variabel ``ceph_extra_confs`` telah diperluas untuk mendukung pengambilan "
"ceph.conf tambahan dan keyring dari beberapa cluster ceph secara otomatis."

msgid ""
"Variable `libvirt_package` in ceph_client role has been renamed to "
"`libvirt_packages` and converted from string to a list."
msgstr ""
"Variabel `libvirt_package` dalam peran ceph_client telah diubah namanya "
"menjadi`libvirt_packages` dan dikonversi dari string ke daftar."

msgid ""
"Variable `rabbitmq_release_version` has been removed as not used anymore."
msgstr ""
"Variabel `rabbitmq_release_version` telah dihapus karena tidak digunakan "
"lagi."

msgid ""
"Variable `uca_repo` has been removed. Deployers are appreciated to use "
"`user_external_repos_list` instead if they want to define extra repository "
"Variable `uca_apt_repo_url` was renamed to `apt_repo_url` in order to "
"correspond it's usage as it also affect Debian deployments now."
msgstr ""
"Variabel `uca_repo` telah dihapus. Pemberi kerja diapresiasi untuk "
"menggunakan `user_external_repos_list` sebagai gantinya jika mereka ingin "
"mendefinisikan repositori tambahan. Variabel `uca_apt_repo_url` diubah "
"namanya menjadi `apt_repo_url` untuk menyesuaikan penggunaannya karena hal "
"itu juga mempengaruhi penyebaran Debian sekarang."

msgid ""
"We are limiting the tarred inventory backups to 15 in addition to changes "
"that only apply backups when the config has changed. These changes are to "
"address an issue where the inventory was corruped with parallel runs on "
"large clusters."
msgstr ""
"Kami membatasi tarred inventory backup hingga 15 di samping perubahan yang "
"hanya berlaku backup saat konfigurasi telah berubah. Perubahan ini untuk "
"mengatasi masalah di mana inventory rusak dengan berjalan paralel pada "
"kluster besar."

msgid ""
"When Glance is configured to use a swift store backend, it will use Keystone "
"v3 authentication by default via the ``glance_swift_store_auth_version`` "
"variable."
msgstr ""
"Ketika Glance dikonfigurasikan untuk menggunakan swift store backend, ia "
"akan menggunakan otentikasi Keystone v3 secara default melalui variabel "
"``glance_swift_store_auth_version``."

msgid ""
"When ``venvwithindex=True`` and ``ignorerequirements=True`` are both "
"specified in ``rally_git_install_fragments`` (as was previously the "
"default), this results in rally being installed from PyPI without any "
"constraints being applied. This results in inconsistent builds from day to "
"day, and can cause build failures for stable implementations due to new "
"library releases. Going forward, we remove the ``rally_git_*`` overrides in "
"``playbooks/defaults/repo_packages/openstack_testing.yml`` so that the "
"integrated build installs rally from PyPI, but with appropriate constraints "
"applied."
msgstr ""
"Ketika ``venvwithindex=True`` dan ``ignorerequirements=True`` keduanya "
"ditentukan dalam ``rally_git_install_fragments`` (seperti sebelumnya "
"default), ini menghasilkan rally yang dipasang dari PyPI tanpa kendala yang "
"diterapkan. Ini menghasilkan build yang tidak konsisten dari hari ke hari, "
"dan dapat menyebabkan kegagalan build untuk implementasi yang stabil karena "
"rilis library baru. Ke depan, kami menghapus ``rally_git_*`` overrides di "
"``playbooks/defaults/repo_packages/openstack_testing.yml`` sehingga build "
"terintegrasi menginstal rally dari PyPI, tetapi dengan batasan yang sesuai "
"diterapkan."

msgid ""
"When `venvwithindex=True` and `ignorerequirements=True` are both specified "
"in `tempest_git_install_fragments` (as was previously the default), this "
"results in tempest being installed from PyPI without any constraints being "
"applied. This could result in the version of tempest being installed in the "
"integrated build being different than the version being installed in the "
"independent role tests. Going forward, we remove the `tempest_git_*` "
"overrides in playbooks/defaults/repo_packages/openstack_testing.yml so that "
"the integrated build installs tempest from PyPI, but with appropriate "
"constraints applied."
msgstr ""
"Ketika `venvwithindex=True` and `ignorerequirements=True` keduanya "
"ditentukan dalam `tempest_git_install_fragments` (seperti sebelumnya "
"default), ini mengakibatkan tempest diinstal dari PyPI tanpa kendala yang "
"diterapkan. Ini bisa mengakibatkan versi tempest yang dipasang di integrated "
"build berbeda dari versi yang diinstal di independent role test. Ke depan, "
"kami menghapus `tempest_git_*` overrides di  playbooks/defaults/"
"repo_packages/openstack_testing.yml  sehingga integrated build menginstal "
"tempest dari PyPI, tetapi dengan batasan yang sesuai diterapkan."

msgid ""
"When a task fails while executing a playbook, the default behaviour for "
"Ansible is to fail for that host without executing any notifiers. This can "
"result in configuration changes being executed, but services not being "
"restarted. OpenStack-Ansible now sets ``ANSIBLE_FORCE_HANDLERS`` to ``True`` "
"by default to ensure that all notified handlers attempt to execute before "
"stopping the playbook execution."
msgstr ""
"Ketika tugas gagal saat menjalankan playbook, perilaku default untuk Ansible "
"adalah gagal untuk host itu tanpa mengeksekusi notifier. Ini dapat "
"mengakibatkan perubahan konfigurasi yang dieksekusi, tetapi layanan tidak "
"restarted. OpenStack-Ansible sekarang menetapkan ``ANSIBLE_FORCE_HANDLERS`` "
"menjadi ``True`` secara default untuk memastikan bahwa semua penangan yang "
"diberitahukan mencoba melakukan sebelum menghentikan eksekusi playbook."

msgid ""
"When enabled, Neutron Firewall as a Service (FWaaS) provides projects the "
"option to implement perimeter security (filtering at the router), adding to "
"filtering at the instance interfaces which is provided by 'Security Groups'."
msgstr ""
"Ketika diaktifkan, Neutron Firewall as a Service (FWaaS) memberikan proyek "
"opsi untuk menerapkan keamanan perimeter (pemfilteran pada router), menambah "
"pemfilteran pada antarmuka instance yang disediakan oleh 'Security Groups'."

msgid ""
"When executing a deployment which includes the telemetry systems "
"(ceilometer, gnocchi, aodh), the repo build will fail due to the inability "
"for pip to read the constraints properly from the extras section in "
"ceilometer's setup.cfg. The current workaround for this is to add the "
"following content to ``/etc/openstack_deploy/user_variables.yml``."
msgstr ""
"Ketika menjalankan deployment yang mencakup sistem telemetri (ceilometer, "
"gnocchi, aodh), repo build akan gagal karena ketidakmampuan pip untuk "
"membaca kendala dengan benar dari bagian ekstra di setup.cfg ceilometer. "
"Solusi saat ini untuk ini adalah menambahkan konten berikut ke  ``/etc/"
"openstack_deploy/user_variables.yml``."

msgid ""
"When migrating from Liberty to Mitaka neutron does not automatically set or "
"migrate networks MTU settings. Neutron has no migration to correctly set the "
"MTU on existing networks so we've created an OSA MTU migration playbook to "
"work-around this issue. The playbook will set the MTU on networks created "
"before the upgrade by iterating on known values from the user_variables and "
"facts. Should any known network name be encountered the MTU will be set to "
"the known value. If no MTU and no global override is present the playbook "
"will fall back to using 1500 for vlan/flat networks and 1450 for vxlan "
"networks."
msgstr ""
"Ketika bermigrasi dari Liberty ke Mitaka, neutron tidak secara otomatis "
"mengatur atau memigrasi pengaturan jaringan MTU. Neutron tidak memiliki "
"migrasi untuk mengatur MTU dengan benar di jaringan yang ada sehingga kami "
"telah membuat playbook migrasi OSA MTU untuk mengatasi masalah ini. Playbook "
"akan mengatur MTU pada jaringan yang dibuat sebelum upgrade dengan "
"mengulangi (iterating) nilai yang diketahui dari user_variables dan fakta. "
"Jika ada nama jaringan yang diketahui dijumpai, MTU akan ditetapkan ke nilai "
"yang diketahui. Jika tidak ada MTU dan tidak ada global override, playbook "
"akan kembali menggunakan 1500 untuk jaringan vlan/flat dan 1450 untuk "
"jaringan vxlan."

msgid ""
"When running aodh with apache(httpd) all apache logs will be stored in the "
"standard apache log directory which is controlled by the distro specific "
"variable ``aodh_apache_default_log_folder``."
msgstr ""
"Saat menjalankan aodh dengan apache(httpd) semua log apache akan disimpan "
"dalam direktori log apache standar yang dikendalikan oleh variabel spesifik "
"distro ``aodh_apache_default_log_folder``."

msgid ""
"When running keystone with apache(httpd) all apache logs will be stored in "
"the standard apache log directory which is controlled by the distro specific "
"variable ``keystone_apache_default_log_folder``."
msgstr ""
"Saat menjalankan keystone dengan apache(httpd) semua log apache akan "
"disimpan dalam direktori log apache standar yang dikendalikan oleh variabel "
"spesifik distro ``keystone_apache_default_log_folder``."

msgid ""
"When the ``glance_enable_v2_registry`` variable is set to ``True`` the "
"corresponding ``data_api`` setting is now correctly set. Previously it was "
"not set and therefore the API service was not correctly informed that the "
"registry was operating."
msgstr ""
"Ketika variabel ``glance_enable_v2_registry`` diatur ke ``True`` pengaturan "
"``data_api`` yang sesuai sekarang diatur dengan benar. Sebelumnya itu tidak "
"disetel dan oleh karena itu layanan API tidak diinformasikan dengan benar "
"bahwa registri beroperasi."

msgid ""
"When the security role was run in Ansible's check mode and a tag was "
"provided, the ``check_mode`` variable was not being set. Any tasks which "
"depend on that variable would fail. This `bug is fixed <https://bugs."
"launchpad.net/openstack-ansible/+bug/1590086>`_ and the ``check_mode`` "
"variable is now set properly on every playbook run."
msgstr ""
"Ketika peran keamanan dijalankan dalam mode pemeriksaan Ansible dan tag "
"diberikan, variabel ``check_mode`` tidak diatur. Tugas apa pun yang "
"bergantung pada variabel itu akan gagal. Bug ini diperbaiki `bug is fixed "
"<https://bugs.launchpad.net/openstack-ansible/+bug/1590086>` _ dan variabel "
"``check_mode`` sekarang ditetapkan dengan benar pada setiap proses playbook."

msgid ""
"When upgrading a Swift deployment from Mitaka to Newton it should be noted "
"that the enabled middleware list has changed. In Newton the \"staticweb\" "
"middleware will be loaded by default. While the change adds a feature it is "
"non-disruptive in upgrades."
msgstr ""
"Ketika upgrading deployment Swift dari Mitaka ke Newton, harus diperhatikan "
"bahwa daftar middleware yang diaktifkan telah berubah. Di Newton middleware "
"\"staticweb\" akan dimuat secara default. Sementara perubahan menambahkan "
"fitur, itu tidak mengganggu dalam upgrade."

msgid ""
"When upgrading deployers will need to ensure they have a backup of all "
"logging from within the container prior to running the playbooks. If the "
"logging node is present within the deployment all logs should already be "
"sync'd with the logging server and no action is required. As a pre-step it's "
"recommended that deployers clean up logging directories from within "
"containers prior to running the playbooks. After the playbooks have run the "
"bind mount will be in effect at \"/var/log\" which will mount over all "
"previous log files and directories."
msgstr ""
"Saat upgrading versi, deployer perlu memastikan mereka memiliki backup semua "
"pencatatan (logging) dari dalam kontainer sebelum menjalankan playbooks. "
"Jika node logging hadir dalam deployment semua log harus sudah disinkronkan "
"dengan server logging dan tidak ada aksi yang diperlukan. Sebagai langkah "
"awal, disarankan agar para deployers membersihkan direktori pendataan dari "
"dalam kontainer sebelum menjalankan playbooks. Setelah playbook dijalankan, "
"bind mount akan berlaku di \"/var/log\" yang akan dipasang di semua file log "
"dan direktori sebelumnya."

msgid ""
"When upgrading from Kilo to Liberty, the ``port_security`` extension driver "
"will not be configured due to the known issues with enabling it after "
"creating networks."
msgstr ""
"Saat upgrading dari Kilo ke Liberty, driver ekstensi ``port_security`` tidak "
"akan dikonfigurasikan karena masalah yang diketahui dengan mengaktifkannya "
"setelah membuat jaringan."

msgid ""
"When upgrading from early Kilo versions of OpenStack-Ansible, the RabbitMQ "
"minor version may need to be upgraded during the upgrade process. This is "
"noted in both the manual steps and the ``run-upgrade.sh`` script."
msgstr ""
"Saat upgrading dari versi Kilo awal OpenStack-Ansible, versi minor RabbitMQ "
"mungkin perlu ditingkatkan (upgraded) selama proses upgrade. Ini dicatat di "
"kedua langkah manual dan skrip ``run-upgrade.sh``."

msgid ""
"When upgrading from pike to queens there are the following changes to the "
"container/service setup."
msgstr ""
"Saat upgrading dari pike ke queen ada perubahan berikut untuk pengaturan "
"container/service."

msgid ""
"When upgrading it is possible for an old \"neutron-ns-metadata-proxy\" "
"process to remain running in memory. If this happens the old version of the "
"process can cause unexpected issues in a production environment. To fix this "
"a task has been added to the os_neutron role that will execute a process "
"lookup and kill any \"neutron-ns-metadata-proxy\" processes that are not "
"running the current release tag. Once the old processes are removed the "
"metadata agent running will respawn everything needed within 60 seconds."
msgstr ""
"Ketika upgrading dimungkinkan untuk proses lama \"neutron-ns-metadata-proxy"
"\" untuk tetap berjalan di memori. Jika ini terjadi, versi proses lama dapat "
"menyebabkan masalah yang tidak terduga di lingkungan produksi. Untuk "
"memperbaikinya, tugas telah ditambahkan ke peran os_neutron yang akan "
"menjalankan pencarian proses dan membunuh proses \"neutron-ns-metadata-proxy"
"\" yang tidak menjalankan tag rilis saat ini. Setelah proses lama dihapus, "
"agen metadata yang berjalan akan respawn semua yang dibutuhkan dalam waktu "
"60 detik."

msgid ""
"When upgrading it is possible for an old ``neutron-ns-metadata-proxy`` "
"process to remain running in memory. If this happens the old version of the "
"process can cause unexpected issues in a production environment. To fix this "
"a task has been added to the os_neutron role that will execute a process "
"lookup and kill any ``neutron-ns-metadata-proxy`` processes that are not "
"running the current release tag. Once the old processes are removed the "
"metadata agent running will respawn everything needed within 60 seconds."
msgstr ""
"Ketika upgrading dimungkinkan untuk proses lama ``neutron-ns-metadata-"
"proxy`` untuk tetap berjalan di memori. Jika ini terjadi, versi proses lama "
"dapat menyebabkan masalah yang tidak terduga di lingkungan produksi. Untuk "
"memperbaikinya, tugas telah ditambahkan ke peran os_neutron yang akan "
"menjalankan pencarian proses dan membunuh proses ``neutron-ns-metadata-"
"proxy`` yang tidak menjalankan tag rilis saat ini. Setelah proses lama "
"dihapus, agen metadata yang berjalan akan respawn semua yang dibutuhkan "
"dalam waktu 60 detik."

msgid ""
"When upgrading nova the cinder ``catalog_info`` will change to use the "
"``cinderv3`` endpoint. Ensure that you have upgraded cinder so that the "
"``cinderv3`` endpoint exists in the keystone catalog."
msgstr ""
"Saat upgrading nova, cinder ``catalog_info`` akan berubah untuk menggunakan "
"endpoint ``cinderv3``. Pastikan Anda telah upgraded cinder sehingga endpoint "
"``cinderv3`` ada di katalog keystone."

msgid ""
"When upgrading there is nothing a deployer **must** immediately do to run "
"neutron agent services on hosts within the ``network_hosts`` group. Simply "
"executing the playbooks will deploy the neutron servers on the baremetal "
"machines and will leave all existing agents containers alone."
msgstr ""
"Ketika upgrading tidak ada yang bisa digunakan deployer **must** segera "
"untuk menjalankan layanan agen neutron di host dalam grup ``network_hosts``. "
"Cukup menjalankan playbook akan deploy server neutron pada mesin baremetal "
"dan akan meninggalkan semua kontainer agen yang ada sendirian."

msgid ""
"When using Glance and NFS the NFS mount point will now be managed using a "
"systemd mount unit file. This change ensures the deployment of glance is not "
"making potentially system impacting changes to the ``/etc/fstab`` and "
"modernizes how we deploy glance when using shared storage."
msgstr ""
"Saat menggunakan Glance dan NFS, NFS mount point sekarang akan dikelola "
"menggunakan file unit mount systemd. Perubahan ini memastikan deployment "
"glance tidak berpotensi mengubah sistem yang berdampak pada ``/etc/fstab`` "
"dan memodernisasi cara kami deploy glance saat menggunakan penyimpanan "
"bersama."

msgid ""
"When using LXC containers with a copy-on-write back-end, the ``lxc_hosts`` "
"role execution would fail due to undefined variables with the "
"``nspawn_host_`` prefix. This issue has now been fixed."
msgstr ""
"Saat menggunakan kontainer LXC dengan back-end copy-on-write, eksekusi role "
"``lxc_hosts`` akan gagal karena variabel yang tidak ditentukan dengan awalan "
"(prefix)  ``nspawn_host_``. Masalah ini sekarang telah diperbaiki."

msgid ""
"When using a copy-on-write backing store, the lxc_container_base_name can "
"now include a prefix defined by ``lxc_container_base_name_prefix``."
msgstr ""
"Saat menggunakan backing store copy-on-write, lxc_container_base_name "
"sekarang dapat menyertakan awalan yang ditentukan oleh "
"``lxc_container_base_name_prefix``."

msgid ""
"When using copy-on-write backing stores for containers, the base container "
"name may be set using the variable ``lxc_container_base_name`` which "
"defaults to `<linux-distribution>`-`distribution-release>`-`<host-cpu-"
"architecture>`."
msgstr ""
"Saat menggunakan backing store copy-on-write untuk kontainer, nama kontainer "
"dasar dapat diatur menggunakan variabel ``lxc_container_base_name`` yang "
"default ke `<linux-distribution>`-`distribution-release>`-`<host-cpu-"
"architecture>`."

msgid ""
"When using the **nspawn** driver container networking is managed by systemd-"
"networkd both on the host and within the container. This gives us a single "
"interface to manage regardless of distro and allows systemd to efficiently "
"manage the resources."
msgstr ""
"Saat menggunakan jaringan kontainer driver **nspawn**  dikelola oleh systemd-"
"networkd baik pada host maupun di dalam kontainer. Ini memberi kami satu "
"antarmuka untuk mengelola terlepas dari distro dan memungkinkan systemd "
"untuk mengelola sumber daya secara efisien."

msgid ""
"When using the **nspawn** driver containers will connect to the system "
"bridges using a MACVLAN, more on this type of network setup can be seen "
"`here <https://www.systutorials.com/docs/linux/man/8-ip-link/>`_."
msgstr ""
"Saat menggunakan kontainer driver **nspawn** akan terhubung ke sistem bridge "
"menggunakan MACVLAN, lebih lanjut tentang jenis pengaturan jaringan ini "
"dapat dilihat `here <https://www.systutorials.com/docs/linux/man/8-ip-link/"
">`_."

msgid ""
"When using the connection plugin's ``container_user`` option, "
"``ansible_remote_tmp`` should be set to a system writable path such as '/var/"
"tmp/'."
msgstr ""
"Saat menggunakan plugin koneksi opsi  ``container_user``, "
"``ansible_remote_tmp``  harus disetel ke path writable sistem seperti '/var/"
"tmp/'."

msgid ""
"When using the pypy python interpreter you can configure the garbage "
"collection (gc) settings for pypy. Set the minimum GC value using the "
"``swift_pypy_gc_min`` variable. GC will only happen when the memory size is "
"above this value. Set the maximum GC value using the ``swift_pypy_gc_max`` "
"variable. This is the maximum memory heap size for pypy. Both variables are "
"not defined by default, and will only be used if the values are defined and "
"``swift_pypy_enabled`` is set to ``True``."
msgstr ""
"Saat menggunakan interpreter python pypy, Anda dapat mengonfigurasi "
"pengaturan garbage collection (gc) untuk pypy. Tetapkan nilai GC minimum "
"menggunakan variabel ``swift_pypy_gc_min``. GC hanya akan terjadi ketika "
"ukuran memori di atas nilai ini. Tetapkan nilai GC maksimum menggunakan "
"variabel ``swift_pypy_gc_max``. Ini adalah ukuran tumpukan memori maksimum "
"untuk pypy. Kedua variabel tidak didefinisikan secara default, dan hanya "
"akan digunakan jika nilainya ditentukan dan ``swift_pypy_enabled`` diatur ke "
"``True``."

msgid ""
"Whether ceilometer should be enabled by default for each service is now "
"dynamically determined based on whether there are any ceilometer hosts/"
"containers deployed. This behaviour can still be overridden by toggling "
"``<service>_ceilometer_enabled`` in ``/etc/openstack_deploy/user_variables."
"yml``."
msgstr ""
"Apakah ceilometer harus diaktifkan secara default untuk setiap layanan "
"sekarang ditentukan secara dinamis berdasarkan apakah ada host/kontainer "
"ceilometer yang digunakan. Perilaku ini masih bisa ditimpa dengan toggling "
"``<service>_ceilometer_enabled`` di ``/etc/openstack_deploy/user_variables."
"yml``."

msgid ""
"Whether the Neutron DHCP Agent, Metadata Agent or LinuxBridge Agent should "
"be enabled is now dynamically determined based on the "
"``neutron_plugin_type`` and the ``neutron_ml2_mechanism_drivers`` that are "
"set. This aims to simplify the configuration of Neutron services and "
"eliminate the need for deployers to override the entire ``neutron_services`` "
"dict variable to disable these services."
msgstr ""
"Apakah Neutron DHCP Agent, Metadata Agent atau LinuxBridge Agent harus "
"diaktifkan sekarang ditentukan secara dinamis berdasarkan "
"``neutron_plugin_type`` dan ``neutron_ml2_mechanism_drivers`` yang "
"ditetapkan. Ini bertujuan untuk menyederhanakan konfigurasi layanan Neutron "
"dan meniadakan kebutuhan deployer untuk override seluruh variabel dict "
"``neutron_services`` untuk menonaktifkan layanan ini."

msgid ""
"While default python interpreter for swift is cpython, pypy is now an "
"option. This change adds the ability to greatly improve swift performance "
"without the core code modifications. These changes have been implemented "
"using the documentation provided by Intel and Swiftstack. Notes about the "
"performance increase can be seen `here <https://software.intel.com/en-us/"
"blogs/2016/05/06/doubling-the-performance-of-openstack-swift-with-no-code-"
"changes>`_."
msgstr ""
"Sementara interpreter python default untuk swift adalah cpython, pypy "
"sekarang menjadi pilihan. Perubahan ini menambahkan kemampuan untuk sangat "
"meningkatkan kinerja swift tanpa modifikasi kode inti. Perubahan ini telah "
"dilaksanakan dengan menggunakan dokumentasi yang disediakan oleh Intel dan "
"Swiftstack. Catatan tentang peningkatan kinerja dapat dilihat `here <https://"
"software.intel.com/en-us/blogs/2016/05/06/doubling-the-performance-of-"
"openstack-swift-with-no-code-changes>`_."

msgid ""
"With the implementation of `systemd-journal-remote` the `rsyslog_client` "
"role is no longer run by default. To enable the legacy functionality, the "
"variable `rsyslog_client_enabled` and `rsyslog_server_enabled` can be set to "
"**true**."
msgstr ""
"Dengan implementasi `systemd-journal-remote` peran` rsyslog_client` tidak "
"lagi dijalankan secara default. Untuk mengaktifkan fungsi legacy, variabel "
"`rsyslog_client_enabled` dan` rsyslog_server_enabled` dapat diatur ke "
"**true**."

msgid ""
"With the release of CentOS 7.5, all pike releases are broken due to a "
"mismatch in version between the libvirt-python library specified by the "
"OpenStack community, and the version provided in CentOS 7.5. As such OSA is "
"unable build the appropriate python library for libvirt. The only recourse "
"for this is to upgrade the environment to the latest queens release."
msgstr ""
"Dengan rilis CentOS 7.5, semua rilis pike rusak karena ketidakcocokan dalam "
"versi antara pustaka libvirt-python yang ditentukan oleh komunitas "
"OpenStack, dan versi yang disediakan di CentOS 7.5. Karena itu OSA tidak "
"dapat membangun pustaka python yang sesuai untuk libvirt. Satu-satunya jalan "
"lain (recourse) untuk ini adalah melakukan upgrade lingkungan ke rilis ratu "
"terbaru."

msgid ""
"With the release of CentOS 7.6, deployments were breaking and becoming very "
"slow when we restart dbus in order to catch some PolicyKit changes. However, "
"those changes were never actaully used so they were happening for no reason. "
"We no longer make any modifications to the systemd-machined configuration "
"and/or PolicyKit to maintain upstream compatibility."
msgstr ""
"Dengan rilis CentOS 7.6, deployment menjadi rusak dan menjadi sangat lambat "
"ketika kami me-restart dbus untuk menangkap beberapa perubahan PolicyKit. "
"Namun, perubahan itu tidak pernah digunakan secara penuh sehingga terjadi "
"tanpa alasan. Kami tidak lagi melakukan modifikasi pada konfigurasi systemd-"
"machined dan/atau PolicyKit untuk menjaga kompatibilitas hulu."

msgid ""
"Within the ``haproxy`` role *hatop* has been changed from a package "
"installation to a source-based installation. This has been done to ensure "
"that the same operator tooling is available across all supported "
"distributions. The download URL for the source can be set using the variable "
"``haproxy_hatop_download_url``."
msgstr ""
"Dalam peran ``haproxy`` *hatop* telah diubah dari instalasi paket menjadi "
"instalasi berbasis sumber. Ini telah dilakukan untuk memastikan bahwa "
"peralatan operator yang sama tersedia di semua distribusi yang didukung. URL "
"unduhan untuk sumber dapat diatur dengan menggunakan variabel "
"``haproxy_hatop_download_url``."

msgid ""
"XtraBackup is currently on version 2.4.5 for amd64 architecture when pulling "
"rpm/deb packages from the repos. To pull the latest available 2.4 branch "
"version from the yum/apt repository set the ``use_percona_upstream`` "
"variable to ``True``. The default behavior using deb packages is unchanged."
msgstr ""
"XtraBackup saat ini pada versi 2.4.5 untuk arsitektur amd64 ketika menarik "
"paket rpm/deb dari repo. Untuk menarik versi 2.4 branch terbaru yang "
"tersedia dari repositori yum/apt, setel variabel ``use_percona_upstream`` "
"menjadi ``True``. Perilaku default menggunakan paket deb tidak berubah."

msgid ""
"XtraBackup is currently on version 2.4.5 for ppc64le architecture when "
"pulling deb packages from the repos."
msgstr ""
"XtraBackup saat ini pada versi 2.4.5 untuk arsitektur ppc64le ketika menarik "
"paket deb dari repo."

msgid ""
"Yaml files used for ceilometer configuration will now allow a deployer to "
"override a given list. If an override is provided that matches an already "
"defined list in one of the ceilometer default yaml files the entire list "
"will be replaced by the provided override. Previously, a nested lists of "
"lists within the default ceilometer configration files would extend should a "
"deployer provide an override matching an existing pipeline. The extension of "
"the defaults had a high probability to cause undesirable outcomes and was "
"very unpredictable."
msgstr ""
"File yaml yang digunakan untuk konfigurasi ceilometer sekarang akan "
"memungkinkan deployer untuk override daftar yang diberikan. Jika override "
"disediakan yang cocok dengan daftar yang sudah ditentukan dalam salah satu "
"file yaml default ceilometer, seluruh daftar akan diganti oleh override yang "
"disediakan. Sebelumnya, daftar yang bersarang di dalam file konfigurasi "
"ceilometer default akan diperluas jika deployer menyediakan override yang "
"cocok dengan pipeline yang ada. Perpanjangan default memiliki probabilitas "
"tinggi untuk menyebabkan hasil yang tidak diinginkan dan sangat tidak "
"terduga."

msgid ""
"You can create a file for the network_host group, inside its group vars "
"folder ``/etc/openstack_deploy/group_vars/network_hosts``, with the content:"
msgstr ""
"Anda dapat membuat file untuk grup network_host, di dalam folder grup vars "
"``/etc/openstack_deploy/group_vars/network_hosts``, dengan konten:"

msgid ""
"You can force update the translations direct from Zanata by setting "
"``horizon_translations_update`` to ``True``. This will call the "
"``pull_catalog`` option built into ``horizon-manage.py``. You should only "
"use this when testing translations, otherwise this should remain set to the "
"default of ``False``."
msgstr ""
"Anda dapat memaksa memperbarui terjemahan langsung dari Zanata dengan "
"mengatur ``horizon_translations_update`` ke ``True``. Ini akan memanggil "
"opsi ``pull_catalog`` yang dibangun di dalam ``horizon-manage.py``. Anda "
"hanya harus menggunakan ini saat menguji terjemahan, jika tidak, ini akan "
"tetap diatur ke default ``False``."

msgid ""
"You can now set the Libvirt CPU model and feature flags from the appropriate "
"entry under the ``nova_virt_types`` dictionary variable (normally ``kvm``). "
"``nova_cpu_model`` is a string value that sets the CPU model; this value is "
"ignored if you set any ``nova_cpu_mode`` other than ``custom``. "
"``nova_cpu_model_extra_flags`` is a list that allows you to specify extra "
"CPU feature flags not normally passed through with ``host-model``, or the "
"``custom`` CPU model of your choice."
msgstr ""
"Anda sekarang dapat mengatur model CPU Libvirt dan flag fitur dari entri "
"yang sesuai di bawah variabel pustaka ``nova_virt_types`` (biasanya "
"``kvm``). ``nova_cpu_model`` adalah nilai string yang mengatur model CPU; "
"nilai ini diabaikan jika Anda mengatur ``nova_cpu_mode`` selain ``custom``. "
"``nova_cpu_model_extra_flags`` adalah daftar yang memungkinkan Anda "
"menentukan flag fitur CPU tambahan yang biasanya tidak dilewati dengan "
"``host-model``, atau model CPU ``custom`` pilihan Anda."

msgid ""
"You can set a private repository for epel, you must use "
"``repo_centos_epel_mirror`` for the repo URL and if you need to get the GPG "
"key from intranet or a mirror use ``repo_centos_epel_key`` for gpg key "
"location."
msgstr ""
"Anda dapat mengatur repositori pribadi untuk epel, Anda harus menggunakan "
"``repo_centos_epel_mirror`` untuk URL repo dan jika Anda perlu mendapatkan "
"GPG key dari penggunaan intranet atau mirror ``repo_centos_epel_key`` untuk "
"lokasi gpg key."

msgid ""
"You can set the ``endpoint_type`` used when creating the Trove service "
"network by specifying the ``trove_service_net_endpoint_type`` variable. This "
"will default to ``internal``. Other possible options are ``public`` and "
"``admin``."
msgstr ""
"Anda dapat mengatur ``endpoint_type`` yang digunakan saat membuat jaringan "
"layanan Trove dengan menentukan variabel "
"``trove_service_net_endpoint_type``. Ini akan default ke ``internal``. Opsi "
"lain yang mungkin adalah ``public`` dan ``admin``."

msgid ""
"You can specify the ``galera_package_arch`` variable to force a specific "
"architecture when installing percona and qpress packages. This will be "
"automatically calculated based on the architecture of the ``galera_server`` "
"host. Acceptable values are ``x86_64`` for ``Ubuntu-14.04`, ``Ubuntu-16.04`` "
"and ``RHEL 7``, and ``ppc64le`` for ``Ubuntu-16.04``."
msgstr ""
"Anda dapat menentukan variabel ``galera_package_arch`` untuk memaksa "
"arsitektur spesifik saat menginstal paket percona dan qpress. Ini akan "
"dihitung secara otomatis berdasarkan arsitektur host ``galera_server``. "
"Nilai yang dapat diterima adalah ``x86_64`` untuk ``Ubuntu-14.04``, "
"``Ubuntu-16.04`` dan ``RHEL 7``, dan ``ppc64le`` untuk ``Ubuntu-16.04``."

msgid ""
"You can specify the ``galera_package_arch`` variable to force a specific "
"architecture when installing percona and qpress packages. This will be "
"automatically calculated based on the architecture of the ``galera_server`` "
"host. Acceptable values are ``x86_64`` for ``Ubuntu-16.04`` and ``RHEL 7``, "
"and ``ppc64le`` for ``Ubuntu-16.04``."
msgstr ""
"Anda dapat menentukan variabel ``galera_package_arch`` untuk memaksa "
"arsitektur spesifik saat menginstal paket percona dan qpress. Ini akan "
"dihitung secara otomatis berdasarkan arsitektur host ``galera_server``. "
"Nilai yang dapat diterima adalah ``x86_64`` untuk ``Ubuntu-16.04`` dan "
"``RHEL 7``, dan ``ppc64le`` untuk ``Ubuntu-16.04``."

msgid "[1] http://erlang.org/doc/man/mnesia.html#dump_log_write_threshold"
msgstr "[1] http://erlang.org/doc/man/mnesia.html#dump_log_write_threshold"

msgid "[client.cinder] key = XXXXXXXXXXX"
msgstr "[client.cinder] key = XXXXXXXXXXX"

msgid ""
"`SESSION_ENGINE` has been changed to memcached by default. So that horizon "
"do not require it's own database for storing session information anymore. "
"`horizon_galera_*` variables has no effect now."
msgstr ""
"`SESSION_ENGINE` telah diubah menjadi memcached secara default. Sehingga "
"horizon tidak memerlukan database sendiri untuk menyimpan informasi sesi "
"lagi. Variabel `horizon_galera_ *` tidak berpengaruh sekarang."

msgid ""
"`Service Function Chaining Extension for OpenStack Networking <https://docs."
"openstack.org/networking-sfc/latest/>`_"
msgstr ""
"`Service Function Chaining Extension for OpenStack Networking <https://docs."
"openstack.org/networking-sfc/latest/>`_"

msgid ""
"``PermitRootLogin`` in the ssh configuration has changed from ``yes`` to "
"``without-password``.  This will only allow ssh to be used to authenticate "
"root via a key."
msgstr ""
"``PermitRootLogin`` dalam konfigurasi ssh telah berubah dari ``yes`` menjadi "
"``without-password``. Ini hanya akan memungkinkan ssh digunakan untuk "
"mengotentikasi root melalui kunci."

msgid ""
"``SKIP_OSA_BOOTSTRAP_AIO``: Skip execution of the bootstrap-aio playbook in "
"gate-check-commit"
msgstr ""
"``SKIP_OSA_BOOTSTRAP_AIO``: Lewati eksekusi playbook bootstrap-aio di gate-"
"check-commit"

msgid ""
"``SKIP_OSA_ROLE_CLONE``: Skip execution of the get-role-requirements-"
"playbook in the bootstrap-ansible.sh script"
msgstr ""
"``SKIP_OSA_ROLE_CLONE``: Lewati eksekusi get-role-requirements-playbook "
"dalam skrip bootstrap-ansible.sh"

msgid ""
"``SKIP_OSA_RUNTIME_VENV_BUILD``: Skip bootstrapping of the OSA ansible venv "
"in bootstrap-ansible.sh"
msgstr ""
"``SKIP_OSA_RUNTIME_VENV_BUILD``: Lewati bootstrap dari OSA ansible venv di "
"bootstrap-ansible.sh"

msgid "``ceilometer_requires_pip_packages``"
msgstr "``ceilometer_requires_pip_packages``"

msgid "``ceilometer_service_description``"
msgstr "``ceilometer_service_description``"

msgid "``ceilometer_service_name``"
msgstr "``ceilometer_service_name``"

msgid "``ceilometer_service_port``"
msgstr "``ceilometer_service_port``"

msgid "``ceilometer_service_proto``"
msgstr "``ceilometer_service_proto``"

msgid "``ceilometer_service_type``"
msgstr "``ceilometer_service_type``"

msgid ""
"``ceph``: This option installs Ceph from a ceph.com repo. Additional "
"variables to adjust items such as Ceph release and regional download mirror "
"can be found in the variables files."
msgstr ""
"``ceph``: Opsi ini menginstal Ceph dari repo ceph.com. Variabel tambahan "
"untuk menyesuaikan item seperti rilis Ceph dan mirror unduhan regional dapat "
"ditemukan di file variabel."

msgid "``cinder.backup.drivers.ceph.CephBackupDriver``"
msgstr "``cinder.backup.drivers.ceph.CephBackupDriver``"

msgid "``cinder.backup.drivers.swift.SwiftBackupDriver``"
msgstr "``cinder.backup.drivers.swift.SwiftBackupDriver``"

msgid ""
"``distro``: This options installs Ceph from the operating system's default "
"repository and unlike the other options does not attempt to manage package "
"keys or add additional package repositories."
msgstr ""
"``distro``: Opsi ini menginstal Ceph dari repositori default sistem operasi "
"dan tidak seperti opsi lain tidak mencoba untuk mengelola kunci paket atau "
"menambah repositori paket tambahan."

msgid "``flow_classifier``"
msgstr "``flow_classifier``"

msgid "``galera_package_arch``"
msgstr "``galera_package_arch``"

msgid "``lxc_container_template_apt_components``"
msgstr "``lxc_container_template_apt_components``"

msgid "``lxc_container_template_main_apt_repo``"
msgstr "``lxc_container_template_main_apt_repo``"

msgid "``lxc_container_template_security_apt_repo``"
msgstr "``lxc_container_template_security_apt_repo``"

msgid ""
"``lxc_host_machine_qgroup_compression_limit`` -> "
"``lxc_host_btrfs_qgroup_compression_limit``"
msgstr ""
"``lxc_host_machine_qgroup_compression_limit`` -> "
"``lxc_host_btrfs_qgroup_compression_limit``"

msgid ""
"``lxc_host_machine_qgroup_space_limit`` -> "
"``lxc_host_btrfs_qgroup_space_limit``"
msgstr ""
"``lxc_host_machine_qgroup_space_limit`` -> "
"``lxc_host_btrfs_qgroup_space_limit``"

msgid ""
"``lxc_host_machine_quota_disabled`` -> ``lxc_host_btrfs_quota_disabled``"
msgstr ""
"``lxc_host_machine_quota_disabled`` -> ``lxc_host_btrfs_quota_disabled``"

msgid "``nova_compute_manager`` is now phased out."
msgstr "``nova_compute_manager`` sekarang dihapus."

msgid ""
"``nova_libvirt_live_migration_flag`` is now phased out. Please create a nova "
"configuration override with ``live_migration_tunnelled: True`` if you want "
"to force the flag ``VIR_MIGRATE_TUNNELLED`` to libvirt. Nova \"chooses a "
"sensible default\" otherwise."
msgstr ""
"``nova_libvirt_live_migration_flag`` sekarang dihapus. Harap buat override "
"konfigurasi nova dengan ``live_migration_tunnelled: True`` jika Anda ingin "
"memaksa flag ``VIR_MIGRATE_TUNNELLED`` ke libvirt. Nova \"chooses a sensible "
"default\" jika tidak."

msgid "``nova_placement_db_max_overflow``"
msgstr "``nova_placement_db_max_overflow``"

msgid "``nova_placement_db_max_pool_size``"
msgstr "``nova_placement_db_max_pool_size``"

msgid "``nova_placement_db_pool_timeout``"
msgstr "``nova_placement_db_pool_timeout``"

msgid "``nova_placement_galera_database``"
msgstr "``nova_placement_galera_database``"

msgid "``nova_placement_galera_user``"
msgstr "``nova_placement_galera_user``"

msgid ""
"``openstack_code_name`` --> ``openstack_distrib_code_name`` "
"``openstack_release`` --> ``openstack_distrib_release``"
msgstr ""
"``openstack_code_name`` --> ``openstack_distrib_code_name`` "
"``openstack_release`` --> ``openstack_distrib_release``"

msgid "``percona_package_download_validate_certs``"
msgstr "``percona_package_download_validate_certs``"

msgid "``percona_package_fallback_url``"
msgstr "``percona_package_fallback_url``"

msgid "``percona_package_path``"
msgstr "``percona_package_path``"

msgid "``percona_package_sha256``"
msgstr "``percona_package_sha256``"

msgid "``percona_package_url``"
msgstr "``percona_package_url``"

msgid "``playbooks/inventory/group_vars/hosts.yml``"
msgstr "``playbooks/inventory/group_vars/hosts.yml``"

msgid "``qpress_package_download_validate_certs``"
msgstr "``qpress_package_download_validate_certs``"

msgid "``qpress_package_fallback_url``"
msgstr "``qpress_package_fallback_url``"

msgid "``qpress_package_path``"
msgstr "``qpress_package_path``"

msgid "``qpress_package_sha256``"
msgstr "``qpress_package_sha256``"

msgid "``qpress_package_url``"
msgstr "``qpress_package_url``"

msgid "``repo_build_concurrency``"
msgstr "``repo_build_concurrency``"

msgid "``repo_build_venv_build_dir``"
msgstr "``repo_build_venv_build_dir``"

msgid "``repo_build_venv_command_options``"
msgstr "``repo_build_venv_command_options``"

msgid "``repo_build_venv_dir``"
msgstr "``repo_build_venv_dir``"

msgid "``repo_build_venv_pip_install_options``"
msgstr "``repo_build_venv_pip_install_options``"

msgid "``repo_build_venv_rebuild``"
msgstr "``repo_build_venv_rebuild``"

msgid "``repo_build_venv_selective``"
msgstr "``repo_build_venv_selective``"

msgid "``repo_build_venv_timeout``"
msgstr "``repo_build_venv_timeout``"

msgid "``repo_pkg_cache_bind``"
msgstr "``repo_pkg_cache_bind``"

msgid "``repo_pkg_cache_dir``"
msgstr "``repo_pkg_cache_dir``"

msgid "``repo_pkg_cache_dirname``"
msgstr "``repo_pkg_cache_dirname``"

msgid "``repo_pkg_cache_enabled``"
msgstr "``repo_pkg_cache_enabled``"

msgid "``repo_pkg_cache_group``"
msgstr "``repo_pkg_cache_group``"

msgid "``repo_pkg_cache_owner``"
msgstr "``repo_pkg_cache_owner``"

msgid "``repo_pkg_cache_port``"
msgstr "``repo_pkg_cache_port``"

msgid "``repo_pypiserver_bin``"
msgstr "``repo_pypiserver_bin``"

msgid "``repo_pypiserver_init_overrides``"
msgstr "``repo_pypiserver_init_overrides``"

msgid "``repo_pypiserver_package_path``"
msgstr "``repo_pypiserver_package_path``"

msgid "``repo_pypiserver_pip_packages``"
msgstr "``repo_pypiserver_pip_packages``"

msgid "``repo_pypiserver_port``"
msgstr "``repo_pypiserver_port``"

msgid "``repo_pypiserver_start_options``"
msgstr "``repo_pypiserver_start_options``"

msgid "``repo_pypiserver_working_dir``"
msgstr "``repo_pypiserver_working_dir``"

msgid "``repo_venv_default_pip_packages``"
msgstr "``repo_venv_default_pip_packages``"

msgid "``requirements.txt``"
msgstr "``requirements.txt``"

msgid "``sfc``"
msgstr "``sfc``"

msgid ""
"``uca``: This option installs Ceph from the Ubuntu Cloud Archive. Additional "
"variables to adjust items such as the OpenStack/Ceph release can be found in "
"the variables files."
msgstr ""
"``uca``: Opsi ini menginstal Ceph dari Ubuntu Cloud Archive. Variabel "
"tambahan untuk menyesuaikan item seperti rilis OpenStack/Ceph dapat "
"ditemukan dalam file variabel."

msgid ""
"`horizon_listen_ports` variable was transformed to the dictionary with "
"required keys `http` and `https` to have effect not only for apache ports."
"conf file, but also for the virtual host."
msgstr ""
"Variabel `horizon_listen_ports` ditransformasikan ke kamus dengan kunci yang "
"diperlukan`http` dan `https` agar memiliki efek tidak hanya untuk file "
"apache ports.conf, tetapi juga untuk host virtual."

msgid ""
"`rabbitmq_install_method: file` is deprecated now and will be removed in the "
"Wallaby release. As for now supported options are only `external_repo` and "
"`distro`. Among with that the following variables are deprecated and "
"prepared for the removal:"
msgstr ""
"`rabbitmq_install_method: file` sudah tidak digunakan lagi dan akan dihapus "
"dalam rilis Wallaby. Sedangkan untuk opsi yang didukung saat ini hanya "
"`external_repo` dan`distro`. Diantara dengan itu variabel-variabel berikut "
"sudah usang dan siap untuk dihapus:"

msgid ""
"aodh.yml and haproxy.yml will be copied into ``/etc/openstack_deploy/env."
"d``. LBaaS agent information will be added to ``/etc/openstack_deploy/env.d/"
"neutron.yml``."
msgstr ""
"aodh.yml dan haproxy.yml akan disalin ke ``/etc/openstack_deploy/env.d``. "
"Informasi agen LBaaS akan ditambahkan ke ``/etc/openstack_deploy/env.d/"
"neutron.yml``."

msgid ""
"ceilometer-polling services running on compute nodes did not have the "
"polling namespace configured. Because of this they used the default value of "
"running all pollsters from the central and compute namespaces. But the "
"pollsters from the central namespace don't have to run on every compute "
"node. This is fixed by only running the compute pollsters on compute nodes."
msgstr ""
"Layanan ceilometer-polling yang berjalan pada node komputasi tidak memiliki "
"namespace polling yang dikonfigurasi. Karena itu, mereka menggunakan nilai "
"default untuk menjalankan semua pollster dari pusat dan menghitung "
"namespace. Tetapi pollster dari namespace pusat tidak harus berjalan pada "
"setiap node komputasi. Ini diperbaiki dengan hanya menjalankan pollster "
"komputasi pada node komputasi."

msgid ""
"ceph-ansible is no longer configured to install ntp by default, which "
"creates a conflict with OSA's ansible-hardening role that is used to "
"implement ntp using 'chrony'."
msgstr ""
"ceph-ansible tidak lagi dikonfigurasikan untuk menginstal ntp secara "
"default, yang menciptakan konflik dengan role ansible-hardening OSA yang "
"digunakan untuk mengimplementasikan ntp menggunakan 'chrony'."

msgid "cinder_v2_service_password"
msgstr "cinder_v2_service_password"

msgid "container_openstack_password"
msgstr "container_openstack_password"

msgid "error: Failed to initialize NSS library"
msgstr "error: Failed to initialize NSS library"

msgid ""
"galera_package_download_validate_certs changed to "
"percona_package_download_validate_certs for clarity"
msgstr ""
"galera_package_download_validate_certs diubah menjadi "
"percona_package_download_validate_certs untuk kejelasan"

msgid "galera_package_path changed to percona_package_path for clarity"
msgstr "galera_package_path changed to percona_package_path untuk kejelasan"

msgid "galera_package_sha256 changed to percona_package_sha256 for clarity"
msgstr ""
"galera_package_sha256 changed to percona_package_sha256 untuk kejelasan"

msgid "galera_package_url changed to percona_package_url for clarity"
msgstr "galera_package_url changed to percona_package_url untuk kejelasan"

msgid "has been changed to:"
msgstr "telah diubah menjadi:"

msgid "https://bugs.launchpad.net/nova-lxd/+bug/1746068"
msgstr "https://bugs.launchpad.net/nova-lxd/+bug/1746068"

msgid "https://bugs.launchpad.net/openstack-ansible/+bug/1697531"
msgstr "https://bugs.launchpad.net/openstack-ansible/+bug/1697531"

msgid "https://bugs.launchpad.net/ubuntu/+source/python-pylxd/+bug/1736454"
msgstr "https://bugs.launchpad.net/ubuntu/+source/python-pylxd/+bug/1736454"

msgid "https://github.com/lxc/lxc/issues/1623"
msgstr "https://github.com/lxc/lxc/issues/1623"

msgid "https://github.com/systemd/systemd/issues/6121"
msgstr "https://github.com/systemd/systemd/issues/6121"

msgid "keystone_assignment_driver"
msgstr "keystone_assignment_driver"

msgid "keystone_auth_admin_token"
msgstr "keystone_auth_admin_token"

msgid "keystone_identity_driver"
msgstr "keystone_identity_driver"

msgid "keystone_ldap_identity_driver"
msgstr "keystone_ldap_identity_driver"

msgid "keystone_resource_driver"
msgstr "keystone_resource_driver"

msgid "keystone_revocation_driver"
msgstr "keystone_revocation_driver"

msgid "keystone_token_driver"
msgstr "keystone_token_driver"

msgid "keystone_token_provider"
msgstr "keystone_token_provider"

msgid ""
"liberty release notes: https://wiki.openstack.org/wiki/ReleaseNotes/"
"Liberty#OpenStack_Image_Service_.28Glance.29"
msgstr ""
"catatan rilis liberty: https://wiki.openstack.org/wiki/ReleaseNotes/"
"Liberty#OpenStack_Image_Service_.28Glance.29"

msgid "lxd_bind_address"
msgstr "lxd_bind_address"

msgid "lxd_bind_port"
msgstr "lxd_bind_port"

msgid "lxd_storage_backend"
msgstr "lxd_storage_backend"

msgid "lxd_storage_create_device"
msgstr "lxd_storage_create_device"

msgid "lxd_trust_password"
msgstr "lxd_trust_password"

msgid ""
"memcached now logs with multiple levels of verbosity, depending on the user "
"variables. Setting ``debug: True`` enables maximum verbosity while setting "
"``verbose: True`` logs with an intermediate level."
msgstr ""
"sekarang memcached log dengan beberapa level verbosity, tergantung pada "
"variabel pengguna. Mengatur ``debug: True`` memungkinkan verbosity maksimum "
"sementara pengaturan ``verbose: True`` mencatat dengan tingkat menengah."

msgid ""
"networking_sfc.services.flowclassifier.plugin.FlowClassifierPlugin => "
"flow_classifier"
msgstr ""
"networking_sfc.services.flowclassifier.plugin.FlowClassifierPlugin => "
"flow_classifier"

msgid "networking_sfc.services.sfc.plugin.SfcPlugin => sfc"
msgstr "networking_sfc.services.sfc.plugin.SfcPlugin => sfc"

msgid ""
"nova-placement-api has been removed from the os_nova role, along with all "
"`nova_placement_*` variables. Please review the `os_placement` role for "
"information about how to configure the new placement service."
msgstr ""
"nova-placement-api telah dihapus dari peran os_nova, bersama dengan semua "
"variabel `nova_placement_*`. Harap tinjau peran `os_placement` untuk "
"informasi tentang cara mengonfigurasi layanan penempatan baru."

msgid "nova_apt_packages -> nova_distro_packages"
msgstr "nova_apt_packages -> nova_distro_packages"

msgid "nova_compute_kvm_apt_packages -> nova_compute_kvm_distro_packages"
msgstr "nova_compute_kvm_apt_packages -> nova_compute_kvm_distro_packages"

msgid "nova_compute_lxd_pip_packages"
msgstr "nova_compute_lxd_pip_packages"

msgid "nova_console_keymap"
msgstr "nova_console_keymap"

msgid "nova_ec2_service_password"
msgstr "nova_ec2_service_password"

msgid "nova_novnc_apt_packages -> nova_novnc_distro_packages"
msgstr "nova_novnc_apt_packages -> nova_novnc_distro_packages"

msgid "nova_novncproxy_vnc_keymap"
msgstr "nova_novncproxy_vnc_keymap"

msgid "nova_s3_service_password"
msgstr "nova_s3_service_password"

msgid "nova_spice_apt_packages -> nova_spice_distro_packages"
msgstr "nova_spice_apt_packages -> nova_spice_distro_packages"

msgid "nova_spice_console_keymap"
msgstr "nova_spice_console_keymap"

msgid "nova_supported_virt_types 'lxd' list entry"
msgstr "nova_supported_virt_types 'lxd' list entry"

msgid "nova_v21_service_password"
msgstr "nova_v21_service_password"

msgid "nova_v3_service_password"
msgstr "nova_v3_service_password"

msgid ""
"openSUSE Leap 42.X support is still work in progress and not fully tested "
"besides basic coverange in the OpenStack CI and individual manual testing. "
"Even though backporting fixes to the Pike release will be done on best "
"effort basis, it's advised to use the master branch when working on openSUSE "
"hosts."
msgstr ""
"Dukungan openSUSE Leap 42.X masih berjalan dan belum sepenuhnya diuji selain "
"cakupan dasar dalam OpenStack CI dan pengujian manual individu. Meskipun "
"perbaikan backporting pada rilis Pike akan dilakukan berdasarkan upaya "
"terbaik, disarankan untuk menggunakan branch master saat bekerja pada host "
"openSUSE."

msgid ""
"pip can be installed via the deployment host using the new variable "
"``pip_offline_install``. This can be useful in environments where the "
"containers lack internet connectivity. Please refer to the `limited "
"connectivity installation guide <http://docs.openstack.org/developer/"
"openstack-ansible/install-guide/app-no-internet-connectivity.html#install-"
"pip-through-deployment-host>`_ for more information."
msgstr ""
"pip dapat diinstal melalui deployment host menggunakan variabel baru "
"``pip_offline_install``. Ini dapat berguna di lingkungan di mana kontainer "
"tidak memiliki konektivitas internet. Silakan merujuk ke `limited "
"connectivity installation guide <http://docs.openstack.org/developer/"
"openstack-ansible/install-guide/app-no-internet-connectivity.html#install-"
"pip-through-deployment-host>`_ untuk informasi lebih lanjut."

msgid "rabbitmq_package_path"
msgstr "rabbitmq_package_path"

msgid "rabbitmq_package_sha256"
msgstr "rabbitmq_package_sha256"

msgid "rabbitmq_package_url"
msgstr "rabbitmq_package_url"

msgid "swift_container_mysql_password"
msgstr "swift_container_mysql_password"