11558 lines
516 KiB
Plaintext
11558 lines
516 KiB
Plaintext
# suhartono <cloudsuhartono@gmail.com>, 2018. #zanata
|
||
# suhartono <cloudsuhartono@gmail.com>, 2019. #zanata
|
||
msgid ""
|
||
msgstr ""
|
||
"Project-Id-Version: operations-guide\n"
|
||
"Report-Msgid-Bugs-To: \n"
|
||
"POT-Creation-Date: 2019-01-26 12:01+0000\n"
|
||
"MIME-Version: 1.0\n"
|
||
"Content-Type: text/plain; charset=UTF-8\n"
|
||
"Content-Transfer-Encoding: 8bit\n"
|
||
"PO-Revision-Date: 2019-01-27 07:46+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 "\"Hey Alvaro, can you run a VLAN on top of a VLAN?\""
|
||
msgstr "\"Hey Alvaro, can you run a VLAN on top of a VLAN?\""
|
||
|
||
msgid "\"If you did, you'd add an extra 4 bytes to the packet…\""
|
||
msgstr "\"If you did, you'd add an extra 4 bytes to the packet…\""
|
||
|
||
msgid "\"The Issue\""
|
||
msgstr "\"The Issue\""
|
||
|
||
msgid "**Block Storage service (cinder)**"
|
||
msgstr "**Block Storage service (cinder)**"
|
||
|
||
msgid "**Compute nodes**"
|
||
msgstr "**Compute nodes**"
|
||
|
||
msgid "**Compute service (nova)**"
|
||
msgstr "**Compute service (nova)**"
|
||
|
||
msgid "**Controller node**"
|
||
msgstr "**Controller node**"
|
||
|
||
msgid "**Create a port that can be reused**"
|
||
msgstr "**Create a port that can be reused**"
|
||
|
||
msgid "**Detach a port from an instance**"
|
||
msgstr "**Detach a port from an instance**"
|
||
|
||
msgid "**Example of Complexity**"
|
||
msgstr "**Example of Complexity**"
|
||
|
||
msgid "**Example**"
|
||
msgstr "**Example**"
|
||
|
||
msgid "**Identity service (keystone)**"
|
||
msgstr "**Identity service (keystone)**"
|
||
|
||
msgid "**Image service (glance)**"
|
||
msgstr "**Image service (glance)**"
|
||
|
||
msgid "**Networking service (neutron)**"
|
||
msgstr "**Networking service (neutron)**"
|
||
|
||
msgid "**Overhead**"
|
||
msgstr "**Overhead**"
|
||
|
||
msgid "**Provision an instance**"
|
||
msgstr "**Provision an instance**"
|
||
|
||
msgid ""
|
||
"**Retrieve an IP address when an instance is deleted before detaching a "
|
||
"port**"
|
||
msgstr ""
|
||
"**Retrieve an IP address when an instance is deleted before detaching a "
|
||
"port**"
|
||
|
||
msgid "**Shared services**"
|
||
msgstr "**Shared services**"
|
||
|
||
msgid "**Storage nodes**"
|
||
msgstr "**Storage nodes**"
|
||
|
||
msgid ""
|
||
"**To capture packets from the patch-tun internal interface on integration "
|
||
"bridge, br-int:**"
|
||
msgstr ""
|
||
"**To capture packets from the patch-tun internal interface on integration "
|
||
"bridge, br-int:**"
|
||
|
||
msgid ""
|
||
"**To create the middleware and plug it in through Paste configuration:**"
|
||
msgstr ""
|
||
"**To create the middleware and plug it in through Paste configuration:**"
|
||
|
||
msgid "**To create the scheduler and plug it in through configuration**"
|
||
msgstr "**To create the scheduler and plug it in through configuration**"
|
||
|
||
msgid ""
|
||
"**To discover which internal VLAN tag is in use for a GRE tunnel by using "
|
||
"the ovs-ofctl command**"
|
||
msgstr ""
|
||
"**To discover which internal VLAN tag is in use for a GRE tunnel by using "
|
||
"the ovs-ofctl command**"
|
||
|
||
msgid ""
|
||
"**To discover which internal VLAN tag is in use for a given external VLAN by "
|
||
"using the ovs-ofctl command**"
|
||
msgstr ""
|
||
"**To discover which internal VLAN tag is in use for a given external VLAN by "
|
||
"using the ovs-ofctl command**"
|
||
|
||
msgid "**To perform a rollback**"
|
||
msgstr "**To perform a rollback**"
|
||
|
||
msgid "**To update Block Storage quotas for a tenant (project)**"
|
||
msgstr "**To update Block Storage quotas for a tenant (project)**"
|
||
|
||
msgid "**To update quota values for a tenant (project)**"
|
||
msgstr "**To update quota values for a tenant (project)**"
|
||
|
||
msgid "**To view Block Storage quotas for a tenant (project)**"
|
||
msgstr "**To view Block Storage quotas for a tenant (project)**"
|
||
|
||
msgid "**To view and update default Block Storage quota values**"
|
||
msgstr "**To view and update default Block Storage quota values**"
|
||
|
||
msgid "**Use**"
|
||
msgstr "**Use**"
|
||
|
||
msgid "*Actions which delete things should not be enabled by default.*"
|
||
msgstr "*Actions which delete things should not be enabled by default.*"
|
||
|
||
msgid "/var/lib/nova/instances"
|
||
msgstr "/var/lib/nova/instances"
|
||
|
||
msgid "0 GB"
|
||
msgstr "0 GB"
|
||
|
||
msgid "1"
|
||
msgstr "1"
|
||
|
||
msgid "1 GB"
|
||
msgstr "1 GB"
|
||
|
||
msgid "10"
|
||
msgstr "10"
|
||
|
||
msgid "10 GB"
|
||
msgstr "10 GB"
|
||
|
||
msgid "100"
|
||
msgstr "100"
|
||
|
||
msgid "15"
|
||
msgstr "15"
|
||
|
||
msgid "16 GB"
|
||
msgstr "16 GB"
|
||
|
||
msgid "160 GB"
|
||
msgstr "160 GB"
|
||
|
||
msgid "2"
|
||
msgstr "2"
|
||
|
||
msgid "2 GB"
|
||
msgstr "2 GB"
|
||
|
||
msgid "20"
|
||
msgstr "20"
|
||
|
||
msgid "20 GB"
|
||
msgstr "20 GB"
|
||
|
||
msgid "200 physical cores."
|
||
msgstr "200 physical cores."
|
||
|
||
msgid "21"
|
||
msgstr "21"
|
||
|
||
msgid "22"
|
||
msgstr "22"
|
||
|
||
msgid "3"
|
||
msgstr "3"
|
||
|
||
msgid "4"
|
||
msgstr "4"
|
||
|
||
msgid "4 GB"
|
||
msgstr "4 GB"
|
||
|
||
msgid "40 GB"
|
||
msgstr "40 GB"
|
||
|
||
msgid "5"
|
||
msgstr "5"
|
||
|
||
msgid "512 MB"
|
||
msgstr "512 MB"
|
||
|
||
msgid "8"
|
||
msgstr "8"
|
||
|
||
msgid "8 GB"
|
||
msgstr "8 GB"
|
||
|
||
msgid "80 GB"
|
||
msgstr "80 GB"
|
||
|
||
msgid "98"
|
||
msgstr "98"
|
||
|
||
msgid "99"
|
||
msgstr "99"
|
||
|
||
msgid ":command:`cinder-manage`"
|
||
msgstr ":command:`cinder-manage`"
|
||
|
||
msgid ":command:`euca-describe-availability-zones verbose`"
|
||
msgstr ":command:`euca-describe-availability-zones verbose`"
|
||
|
||
msgid ":command:`glance-manage`"
|
||
msgstr ":command:`glance-manage`"
|
||
|
||
msgid ":command:`keystone-manage`"
|
||
msgstr ":command:`keystone-manage`"
|
||
|
||
msgid ":command:`nova-manage`"
|
||
msgstr ":command:`nova-manage`"
|
||
|
||
msgid ":command:`openstack compute service list`"
|
||
msgstr ":command:`openstack compute service list`"
|
||
|
||
msgid ":command:`openstack host list` (os-hosts)"
|
||
msgstr ":command:`openstack host list` (os-hosts)"
|
||
|
||
msgid ""
|
||
":ref:`table_segregation_methods` provides a comparison view of each "
|
||
"segregation method currently provided by OpenStack Compute."
|
||
msgstr ""
|
||
":ref:`table_segregation_methods` memberikan tampilan perbandingan setiap "
|
||
"metode pemisahan yang saat ini disediakan oleh OpenStack Compute."
|
||
|
||
msgid ""
|
||
":term:`Availability zones <availability zone>` and host aggregates, which "
|
||
"merely divide a single Compute deployment."
|
||
msgstr ""
|
||
":term:`Availability zones <availability zone>` dan host agregat, yang hanya "
|
||
"membagi satu penyebaran Compute."
|
||
|
||
msgid ""
|
||
"A DHCP problem might be caused by a misbehaving dnsmasq process. First, "
|
||
"debug by checking logs and then restart the dnsmasq processes only for that "
|
||
"project (tenant). In VLAN mode, there is a dnsmasq process for each tenant. "
|
||
"Once you have restarted targeted dnsmasq processes, the simplest way to rule "
|
||
"out dnsmasq causes is to kill all of the dnsmasq processes on the machine "
|
||
"and restart ``nova-network``. As a last resort, do this as root:"
|
||
msgstr ""
|
||
"Masalah DHCP mungkin disebabkan oleh proses dnsmasq yang salah. Pertama, "
|
||
"debug dengan memeriksa log dan kemudian restart proses dnsmasq hanya untuk "
|
||
"proyek itu (tenant). Dalam mode VLAN, ada proses dnsmasq untuk setiap "
|
||
"tenant. Setelah Anda me-restart proses dnsmasq yang ditargetkan, cara paling "
|
||
"sederhana untuk mengesampingkan penyebab dnsmasq adalah dengan mematikan "
|
||
"semua proses dnsmasq pada mesin dan me-restart ``nova-network``. Sebagai "
|
||
"upaya terakhir, lakukan ini sebagai root:"
|
||
|
||
msgid ""
|
||
"A NetApp appliance is used in each region for both block storage and "
|
||
"instance storage. There are future plans to move the instances off the "
|
||
"NetApp appliance and onto a distributed file system such as :term:`Ceph` or "
|
||
"GlusterFS."
|
||
msgstr ""
|
||
"Alat NetApp digunakan di setiap wilayah untuk penyimpanan blok dan "
|
||
"penyimpanan instance. Ada rencana di masa depan untuk memindahkan instance "
|
||
"dari alat NetApp dan ke sistem file terdistribusi seperti :term: `Ceph` atau "
|
||
"GlusterFS."
|
||
|
||
msgid ""
|
||
"A basic type of alert monitoring is to simply check and see whether a "
|
||
"required process is running. For example, ensure that the ``nova-api`` "
|
||
"service is running on the cloud controller:"
|
||
msgstr ""
|
||
"Jenis dasar pemantauan peringatan adalah dengan hanya memeriksa dan melihat "
|
||
"apakah proses yang diperlukan sedang berjalan. Sebagai contoh, pastikan "
|
||
"bahwa layanan ``nova-api`` berjalan pada pengontrol cloud:"
|
||
|
||
msgid ""
|
||
"A cloud controller node runs several different services. You can install "
|
||
"services that communicate only using the message queue internally— ``nova-"
|
||
"scheduler`` and ``nova-console`` on a new server for expansion. However, "
|
||
"other integral parts require more care."
|
||
msgstr ""
|
||
"Node pengontrol cloud menjalankan beberapa layanan berbeda. Anda dapat "
|
||
"menginstal layanan yang berkomunikasi hanya menggunakan antrian pesan secara "
|
||
"internal— ``nova-scheduler`` dan `` nova-console`` pada server baru untuk "
|
||
"ekspansi. Namun, bagian integral lainnya membutuhkan perawatan lebih."
|
||
|
||
msgid ""
|
||
"A cloud environment that is scaled to a certain size will require the file "
|
||
"descriptor limits to be adjusted."
|
||
msgstr ""
|
||
"Lingkungan cloud yang diskalakan ke ukuran tertentu akan membutuhkan batas "
|
||
"deskriptor file untuk disesuaikan."
|
||
|
||
msgid ""
|
||
"A cloud with multiple sites where you can schedule VMs \"anywhere\" or on a "
|
||
"particular site."
|
||
msgstr ""
|
||
"Cloud dengan banyak situs tempat Anda dapat menjadwalkan VM \"anywhere\" "
|
||
"atau di situs tertentu."
|
||
|
||
msgid ""
|
||
"A cloud with multiple sites, where you schedule VMs to a particular site and "
|
||
"you want a shared infrastructure."
|
||
msgstr ""
|
||
"Cloud dengan banyak situs, tempat Anda menjadwalkan VM ke situs tertentu dan "
|
||
"Anda menginginkan infrastruktur bersama."
|
||
|
||
msgid ""
|
||
"A common scenario is to take down production management services in "
|
||
"preparation for an upgrade, completed part of the upgrade process, and "
|
||
"discovered one or more problems not encountered during testing. As a "
|
||
"consequence, you must roll back your environment to the original \"known good"
|
||
"\" state. You also made sure that you did not make any state changes after "
|
||
"attempting the upgrade process; no new instances, networks, storage volumes, "
|
||
"and so on. Any of these new resources will be in a frozen state after the "
|
||
"databases are restored from backup."
|
||
msgstr ""
|
||
"Skenario umum adalah menghapus layanan manajemen produksi dalam persiapan "
|
||
"untuk upgrade, menyelesaikan bagian dari proses upgrade, dan menemukan satu "
|
||
"atau lebih masalah yang tidak ditemukan selama pengujian. Sebagai akibatnya, "
|
||
"Anda harus memutar kembali (roll back) lingkungan Anda ke keadaan \"known "
|
||
"good\" yang asli. Anda juga memastikan bahwa Anda tidak membuat perubahan "
|
||
"keadaan setelah mencoba proses upgrade; tidak ada instance baru, jaringan, "
|
||
"volume penyimpanan, dan sebagainya. Sumber daya baru ini akan dalam keadaan "
|
||
"beku setelah database dipulihkan dari cadangan."
|
||
|
||
msgid ""
|
||
"A common use of host aggregates is to provide information for use with the "
|
||
"``nova-scheduler``. For example, you might use a host aggregate to group a "
|
||
"set of hosts that share specific flavors or images."
|
||
msgstr ""
|
||
"Penggunaan agregat host yang umum adalah untuk memberikan informasi untuk "
|
||
"digunakan dengan ``nova-scheduler``. Misalnya, Anda dapat menggunakan "
|
||
"agregat host untuk mengelompokkan serangkaian host yang berbagi flavor atau "
|
||
"image tertentu."
|
||
|
||
msgid ""
|
||
"A common way of dealing with the recovery from a full system failure, such "
|
||
"as a power outage of a data center, is to assign each service a priority, "
|
||
"and restore in order. :ref:`table_example_priority` shows an example."
|
||
msgstr ""
|
||
"Cara umum menangani pemulihan dari kegagalan sistem penuh, seperti pemadaman "
|
||
"listrik pusat data, adalah menetapkan setiap layanan sebagai prioritas, dan "
|
||
"memulihkannya secara berurutan. :ref: `table_example_priority` menampilkan "
|
||
"contoh."
|
||
|
||
msgid "A compute node"
|
||
msgstr "Node komputasi "
|
||
|
||
msgid ""
|
||
"A critical part of a cloud's scalability is the amount of effort that it "
|
||
"takes to run your cloud. To minimize the operational cost of running your "
|
||
"cloud, set up and use an automated deployment and configuration "
|
||
"infrastructure with a configuration management system, such as :term:"
|
||
"`Puppet` or :term:`Chef`. Combined, these systems greatly reduce manual "
|
||
"effort and the chance for operator error."
|
||
msgstr ""
|
||
"Bagian penting dari skalabilitas cloud adalah jumlah upaya yang diperlukan "
|
||
"untuk menjalankan cloud Anda. Untuk meminimalkan biaya operasional "
|
||
"menjalankan cloud Anda, atur dan gunakan penyebaran otomatis dan "
|
||
"infrastruktur konfigurasi dengan sistem manajemen konfigurasi, seperti :term:"
|
||
"`Puppet` atau :term:`Chef`. Digabungkan, sistem ini sangat mengurangi upaya "
|
||
"manual dan kemungkinan kesalahan operator."
|
||
|
||
msgid ""
|
||
"A different API endpoint for every region. Each region has a full nova "
|
||
"installation."
|
||
msgstr ""
|
||
"Endpoint API yang berbeda untuk setiap wilayah. Setiap wilayah memiliki "
|
||
"instalasi nova lengkap."
|
||
|
||
msgid ""
|
||
"A feature was introduced in Essex to periodically check and see if there "
|
||
"were any ``_base`` files not in use. If there were, OpenStack Compute would "
|
||
"delete them. This idea sounds innocent enough and has some good qualities to "
|
||
"it. But how did this feature end up turned on? It was disabled by default in "
|
||
"Essex. As it should be. It was `decided to be turned on in Folsom <https://"
|
||
"bugs.launchpad.net/nova/+bug/1029674>`_. I cannot emphasize enough that:"
|
||
msgstr ""
|
||
"Fitur diperkenalkan di Essex untuk secara berkala memeriksa dan melihat "
|
||
"apakah ada ``_base`` file yang tidak digunakan. Jika ada, OpenStack Compute "
|
||
"akan menghapusnya. Gagasan ini kedengarannya cukup polos dan memiliki "
|
||
"kualitas yang bagus. Tetapi bagaimana fitur ini akhirnya dihidupkan? Itu "
|
||
"dinonaktifkan secara default di Essex. Seperti seharusnya. Dulu `decided to "
|
||
"be turned on in Folsom <https://bugs.launchpad.net/nova/+bug/1029674>`_. "
|
||
"Saya tidak bisa cukup menekankan bahwa:"
|
||
|
||
msgid "A few nights later, it happened again."
|
||
msgstr "Beberapa malam kemudian, itu terjadi lagi."
|
||
|
||
msgid ""
|
||
"A long requested service, to provide the ability to manipulate DNS entries "
|
||
"associated with OpenStack resources has gathered a following. The designate "
|
||
"project was also released."
|
||
msgstr ""
|
||
"Layanan yang lama diminta, untuk menyediakan kemampuan untuk memanipulasi "
|
||
"entri DNS yang terkait dengan sumber daya OpenStack telah mengumpulkan hal "
|
||
"berikut. Proyek yang ditunjuk juga dirilis."
|
||
|
||
msgid ""
|
||
"A major quality push has occurred across drivers and plug-ins in Block "
|
||
"Storage, Compute, and Networking. Particularly, developers of Compute and "
|
||
"Networking drivers that require proprietary or hardware products are now "
|
||
"required to provide an automated external testing system for use during the "
|
||
"development process."
|
||
msgstr ""
|
||
"Peningkatan kualitas utama telah terjadi di seluruh driver dan plug-in di "
|
||
"Block Storage, Compute, dan Networking. Khususnya, pengembang driver Compute "
|
||
"dan Networking yang memerlukan produk-produk perangkat keras atau "
|
||
"kepemilikan sekarang diminta untuk menyediakan sistem pengujian eksternal "
|
||
"otomatis untuk digunakan selama proses pengembangan."
|
||
|
||
msgid ""
|
||
"A much-requested answer to big data problems, a dedicated team has been "
|
||
"making solid progress on a Hadoop-as-a-Service project."
|
||
msgstr ""
|
||
"Jawaban yang banyak diminta untuk masalah big data, tim berdedikasi telah "
|
||
"membuat kemajuan yang solid pada proyek Hadoop-as-a-Service."
|
||
|
||
msgid ""
|
||
"A note about DAIR's architecture: ``/var/lib/nova/instances`` is a shared "
|
||
"NFS mount. This means that all compute nodes have access to it, which "
|
||
"includes the ``_base`` directory. Another centralized area is ``/var/log/"
|
||
"rsyslog`` on the cloud controller. This directory collects all OpenStack "
|
||
"logs from all compute nodes. I wondered if there were any entries for the "
|
||
"file that :command:`virsh` is reporting:"
|
||
msgstr ""
|
||
"Catatan tentang arsitektur DAIR: ``/var/lib/nova/instances`` adalah mount "
|
||
"NFS bersama. Ini berarti bahwa semua node komputasi memiliki akses ke sana, "
|
||
"yang mencakup direktori ``_base``. Area terpusat lainnya adalah ``/var/log/"
|
||
"rsyslog`` pada pengontrol cloud. Direktori ini mengumpulkan semua log "
|
||
"OpenStack dari semua node komputasi. Saya bertanya-tanya apakah ada entri "
|
||
"untuk file yang :command:`virsh` melaporkan:"
|
||
|
||
msgid ""
|
||
"A number of operating systems use rsyslog as the default logging service. "
|
||
"Since it is natively able to send logs to a remote location, you do not have "
|
||
"to install anything extra to enable this feature, just modify the "
|
||
"configuration file. In doing this, consider running your logging over a "
|
||
"management network or using an encrypted VPN to avoid interception."
|
||
msgstr ""
|
||
"Sejumlah sistem operasi menggunakan rsyslog sebagai layanan logging standar. "
|
||
"Karena secara asli dapat mengirim log ke lokasi yang jauh, Anda tidak perlu "
|
||
"menginstal apa pun tambahan untuk mengaktifkan fitur ini, cukup modifikasi "
|
||
"file konfigurasi. Dalam melakukan ini, pertimbangkan untuk menjalankan "
|
||
"pendataan Anda melalui jaringan manajemen atau menggunakan VPN terenkripsi "
|
||
"untuk menghindari intersepsi."
|
||
|
||
msgid ""
|
||
"A quick Google search turned up this: `DHCP lease errors in VLAN mode "
|
||
"<https://lists.launchpad.net/openstack/msg11696.html>`_ which further "
|
||
"supported our DHCP theory."
|
||
msgstr ""
|
||
"Pencarian Google cepat muncul ini: `DHCP lease errors in VLAN mode <https://"
|
||
"lists.launchpad.net/openstack/msg11696.html>`_ yang selanjutnya mendukung "
|
||
"teori DHCP kami."
|
||
|
||
msgid ""
|
||
"A quick way to check whether DNS is working is to resolve a hostname inside "
|
||
"your instance by using the :command:`host` command. If DNS is working, you "
|
||
"should see:"
|
||
msgstr ""
|
||
"Cara cepat untuk memeriksa apakah DNS berfungsi adalah dengan menyelesaikan "
|
||
"nama host di dalam instance Anda dengan menggunakan perintah :command:"
|
||
"`host`. Jika DNS berfungsi, Anda akan melihat:"
|
||
|
||
msgid ""
|
||
"A report came in: VMs were launching slowly, or not at all. Cue the standard "
|
||
"checks—nothing on the Nagios, but there was a spike in network towards the "
|
||
"current master of our RabbitMQ cluster. Investigation started, but soon the "
|
||
"other parts of the queue cluster were leaking memory like a sieve. Then the "
|
||
"alert came in—the master Rabbit server went down and connections failed over "
|
||
"to the slave."
|
||
msgstr ""
|
||
"Sebuah laporan muncul: VM diluncurkan perlahan, atau tidak sama sekali. Beri "
|
||
"tanda pada pemeriksaan standar — tidak ada apa pun di Nagios, tetapi ada "
|
||
"lonjakan jaringan terhadap master saat ini dari kluster RabbitMQ kami. "
|
||
"Investigasi dimulai, tetapi segera bagian-bagian lain dari antrian cluster "
|
||
"membocorkan memori seperti saringan (sieve). Kemudian peringatan datang — "
|
||
"server master Kelinci down dan koneksi gagal ke slave."
|
||
|
||
msgid ""
|
||
"A security domain comprises of users, applications, servers or networks that "
|
||
"share common trust requirements and expectations within a system. Typically "
|
||
"they have the same authentication and authorization requirements and users."
|
||
msgstr ""
|
||
"Domain keamanan terdiri dari pengguna, aplikasi, server atau jaringan yang "
|
||
"berbagi persyaratan dan harapan kepercayaan bersama dalam suatu sistem. "
|
||
"Biasanya mereka memiliki persyaratan dan pengguna otentikasi dan otorisasi "
|
||
"yang sama."
|
||
|
||
msgid "A service to provide queues of messages and notifications was released."
|
||
msgstr "Layanan untuk menyediakan antrian pesan dan pemberitahuan dirilis."
|
||
|
||
msgid "A shell where you can get some work done"
|
||
msgstr "Shell tempat Anda bisa menyelesaikan pekerjaan"
|
||
|
||
msgid ""
|
||
"A similar pattern can be followed in other projects that use the driver "
|
||
"architecture. Simply create a module and class that conform to the driver "
|
||
"interface and plug it in through configuration. Your code runs when that "
|
||
"feature is used and can call out to other services as necessary. No project "
|
||
"core code is touched. Look for a \"driver\" value in the project's ``.conf`` "
|
||
"configuration files in ``/etc/<project>`` to identify projects that use a "
|
||
"driver architecture."
|
||
msgstr ""
|
||
"Pola serupa dapat diikuti dalam proyek lain yang menggunakan arsitektur "
|
||
"driver. Cukup buat modul dan kelas yang sesuai dengan antarmuka driver dan "
|
||
"hubungkan melalui konfigurasi. Kode Anda berjalan ketika fitur itu digunakan "
|
||
"dan dapat memanggil layanan lain yang diperlukan. Tidak ada kode core proyek "
|
||
"yang disentuh. Cari nilai \"driver\" di file konfigurasi ``.conf`` proyek di "
|
||
"``/etc/<project>`` untuk mengidentifikasi proyek yang menggunakan arsitektur "
|
||
"driver."
|
||
|
||
msgid ""
|
||
"A single :term:`API endpoint` for compute, or you require a second level of "
|
||
"scheduling."
|
||
msgstr ""
|
||
"Single :term:`API endpoint` untuk komputasi, atau Anda memerlukan "
|
||
"penjadwalan tingkat kedua."
|
||
|
||
msgid "A single-site cloud with equipment fed by separate power supplies."
|
||
msgstr ""
|
||
"Single-site cloud dengan peralatan yang diumpankan oleh catu daya terpisah."
|
||
|
||
msgid ""
|
||
"A tangible example of this is the ``nova-compute`` process. In order to "
|
||
"manage the image cache with libvirt, ``nova-compute`` has a periodic process "
|
||
"that scans the contents of the image cache. Part of this scan is calculating "
|
||
"a checksum for each of the images and making sure that checksum matches what "
|
||
"``nova-compute`` expects it to be. However, images can be very large, and "
|
||
"these checksums can take a long time to generate. At one point, before it "
|
||
"was reported as a bug and fixed, ``nova-compute`` would block on this task "
|
||
"and stop responding to RPC requests. This was visible to users as failure of "
|
||
"operations such as spawning or deleting instances."
|
||
msgstr ""
|
||
"Contoh nyata dari ini adalah proses ``nova-compute``. Untuk mengelola cache "
|
||
"image dengan libvirt, ``nova-compute`` memiliki proses periodik yang "
|
||
"memindai isi cache image. Bagian dari pemindaian ini menghitung checksum "
|
||
"untuk setiap image dan memastikan bahwa checksum cocok dengan apa yang "
|
||
"diharapkan oleh ``nova-compute``. Namun, image bisa sangat besar, dan "
|
||
"checksum ini dapat memakan waktu lama untuk dibuat. Pada satu titik, sebelum "
|
||
"dilaporkan sebagai bug dan diperbaiki, ``nova-compute`` akan memblokir tugas "
|
||
"ini dan berhenti merespons permintaan RPC. Ini terlihat oleh pengguna "
|
||
"sebagai kegagalan operasi seperti memijah atau menghapus instance."
|
||
|
||
msgid ""
|
||
"A tool such as **collectd** can be used to store this information. While "
|
||
"collectd is out of the scope of this book, a good starting point would be to "
|
||
"use collectd to store the result as a COUNTER data type. More information "
|
||
"can be found in `collectd's documentation <https://collectd.org/wiki/index."
|
||
"php/Data_source>`_."
|
||
msgstr ""
|
||
"Alat seperti **collectd ** dapat digunakan untuk menyimpan informasi ini. "
|
||
"Meskipun collectd berada di luar cakupan buku ini, titik awal yang baik "
|
||
"adalah menggunakan collectd untuk menyimpan hasilnya sebagai tipe data "
|
||
"COUNTER. Informasi lebih lanjut dapat ditemukan di `collectd's documentation "
|
||
"<https://collectd.org/wiki/index.php/Data_source>`_."
|
||
|
||
msgid "A user recently tried launching a CentOS instance on that node"
|
||
msgstr ""
|
||
"Seorang pengguna baru-baru ini mencoba meluncurkan instance CentOS pada node "
|
||
"itu"
|
||
|
||
msgid "AMQP broker"
|
||
msgstr "AMQP broker"
|
||
|
||
msgid "Abstract"
|
||
msgstr "Abstrak"
|
||
|
||
msgid "Account quotas"
|
||
msgstr "Kuota akun"
|
||
|
||
msgid "Acknowledgements"
|
||
msgstr "Ucapan Terima Kasih"
|
||
|
||
msgid ""
|
||
"Adam Powell in Racker IT supplied us with bandwidth each day and second "
|
||
"monitors for those of us needing more screens."
|
||
msgstr ""
|
||
"Adam Powell di Racker IT memberi kami bandwidth setiap hari dan monitor "
|
||
"kedua bagi kami yang membutuhkan lebih banyak layar."
|
||
|
||
msgid ""
|
||
"Add all raw disks to one large RAID array, either hardware or software "
|
||
"based. You can partition this large array with the boot, root, swap, and LVM "
|
||
"areas. This option is simple to implement and uses all partitions. However, "
|
||
"disk I/O might suffer."
|
||
msgstr ""
|
||
"Tambahkan semua disk baku ke satu array RAID besar, baik berbasis perangkat "
|
||
"keras atau perangkat lunak. Anda dapat mempartisi array besar ini dengan "
|
||
"area boot, root, swap, dan LVM. Opsi ini mudah diterapkan dan menggunakan "
|
||
"semua partisi. Namun, disk I/O mungkin terbebani."
|
||
|
||
msgid "Add device ``snooper0`` to bridge ``br-int``:"
|
||
msgstr "Tambahkan perangkat ``snooper0`` untuk menjembatani ``br-int``:"
|
||
|
||
msgid "Add metadata to the container to allow the IP:"
|
||
msgstr "Tambahkan metadata ke kontainer untuk memungkinkan IP:"
|
||
|
||
msgid "Add the repository for the new release packages."
|
||
msgstr "Tambahkan repositori untuk paket rilis baru."
|
||
|
||
msgid "Adding Custom Logging Statements"
|
||
msgstr "Menambahkan Pernyataan Logging Kustom"
|
||
|
||
msgid "Adding Images"
|
||
msgstr "Menambahkan Images"
|
||
|
||
msgid "Adding Projects"
|
||
msgstr "Menambahkan Proyek"
|
||
|
||
msgid "Adding Signed Images"
|
||
msgstr "Menambahkan Signed Images"
|
||
|
||
msgid "Adding a Compute Node"
|
||
msgstr "Menambahkan Node Komputasi"
|
||
|
||
msgid ""
|
||
"Adding a new object storage node is different from adding compute or block "
|
||
"storage nodes. You still want to initially configure the server by using "
|
||
"your automated deployment and configuration-management systems. After that "
|
||
"is done, you need to add the local disks of the object storage node into the "
|
||
"object storage ring. The exact command to do this is the same command that "
|
||
"was used to add the initial disks to the ring. Simply rerun this command on "
|
||
"the object storage proxy server for all disks on the new object storage "
|
||
"node. Once this has been done, rebalance the ring and copy the resulting "
|
||
"ring files to the other storage nodes."
|
||
msgstr ""
|
||
"Menambahkan node penyimpanan objek baru berbeda dari menambahkan komputasi "
|
||
"atau memblokir node penyimpanan. Anda masih ingin mengkonfigurasi server "
|
||
"dengan menggunakan sistem manajemen konfigurasi dan penyebaran otomatis "
|
||
"Anda. Setelah itu selesai, Anda perlu menambahkan disk lokal dari node "
|
||
"penyimpanan objek ke dalam ring penyimpanan objek. Perintah yang tepat untuk "
|
||
"melakukan ini adalah perintah yang sama yang digunakan untuk menambahkan "
|
||
"disk awal ke ring. Cukup jalankan kembali perintah ini pada server proxy "
|
||
"penyimpanan objek untuk semua disk pada node penyimpanan objek baru. Setelah "
|
||
"ini selesai, menyeimbangkan ulang ring dan menyalin file ring yang "
|
||
"dihasilkan ke node penyimpanan lainnya."
|
||
|
||
msgid "Adding an Object Storage Node"
|
||
msgstr "Menambahkan node penyimpanan objek ( Object Storage node)"
|
||
|
||
msgid "Adding cloud controller nodes"
|
||
msgstr "Menambahkan node pengontrol cloud"
|
||
|
||
msgid ""
|
||
"Adding to a RAID array (RAID stands for redundant array of independent "
|
||
"disks), based on the number of disks you have available, so that you can add "
|
||
"capacity as your cloud grows. Some options are described in more detail "
|
||
"below."
|
||
msgstr ""
|
||
"Menambah array RAID (RAID adalah singkatan dari redundant array of "
|
||
"independent disks), berdasarkan jumlah disk yang Anda miliki, sehingga Anda "
|
||
"dapat menambah kapasitas saat cloud Anda tumbuh. Beberapa opsi dijelaskan "
|
||
"secara lebih rinci di bawah ini."
|
||
|
||
msgid ""
|
||
"Additionally, for Identity-related issues, try the tips in :ref:"
|
||
"`sql_backend`."
|
||
msgstr ""
|
||
"Selain itu, untuk masalah yang berkaitan dengan Identitas, cobalah kiat di :"
|
||
"ref:`sql_backend`."
|
||
|
||
msgid ""
|
||
"Additionally, this instance in question was responsible for a very, very "
|
||
"large backup job each night. While \"The Issue\" (as we were now calling it) "
|
||
"didn't happen exactly when the backup happened, it was close enough (a few "
|
||
"hours) that we couldn't ignore it."
|
||
msgstr ""
|
||
"Selain itu, instance ini bertanggung jawab atas pekerjaan backup yang "
|
||
"sangat, sangat besar setiap malam. Sementara \"The Issue\" (seperti yang "
|
||
"kita sebut sekarang) tidak terjadi tepat ketika backup terjadi, itu cukup "
|
||
"dekat (beberapa jam) sehingga kami tidak bisa mengabaikannya."
|
||
|
||
msgid ""
|
||
"Additionally, you can refer to `neutron client <https://docs.openstack.org/"
|
||
"python-neutronclient/latest/>`_ for more options."
|
||
msgstr ""
|
||
"Selain itu, Anda dapat merujuk `neutron client <https://docs.openstack.org/"
|
||
"python-neutronclient/latest/>`_ untuk opsi lainnya."
|
||
|
||
msgid ""
|
||
"Adjust the appropriate limits in the ``/etc/security/limits.conf`` "
|
||
"configuration file."
|
||
msgstr ""
|
||
"Sesuaikan batas yang sesuai dalam file konfigurasi ``/etc/security/limits."
|
||
"conf``."
|
||
|
||
msgid "Administrative Command-Line Tools"
|
||
msgstr "Alat Command-Line Administratif"
|
||
|
||
msgid "Advanced Configuration"
|
||
msgstr "Konfigurasi Lanjutan"
|
||
|
||
msgid "After a Compute Node Reboots"
|
||
msgstr "Setelah node komputasi, reboot"
|
||
|
||
msgid ""
|
||
"After a cloud controller reboots, ensure that all required services were "
|
||
"successfully started. The following commands use :command:`ps` and :command:"
|
||
"`grep` to determine if nova, glance, and keystone are currently running:"
|
||
msgstr ""
|
||
"Setelah pengontrol cloud dinyalakan ulang, pastikan semua layanan yang "
|
||
"diperlukan berhasil dimulai. Perintah berikut menggunakan :command:`ps` dan :"
|
||
"command:`grep` untuk menentukan apakah nova, glance, dan keystone saat ini "
|
||
"sedang berjalan:"
|
||
|
||
msgid "After a few minutes of troubleshooting, I saw the following details:"
|
||
msgstr "Setelah beberapa menit pemecahan masalah, saya melihat detail berikut:"
|
||
|
||
msgid ""
|
||
"After digging into the nova (OpenStack Compute) code, I noticed two areas in "
|
||
"``api/ec2/cloud.py`` potentially impacting my system:"
|
||
msgstr ""
|
||
"Setelah menggali kode nova (OpenStack Compute), saya perhatikan dua area di "
|
||
"``api/ec2/cloud.py`` yang berpotensi memengaruhi sistem saya:"
|
||
|
||
msgid ""
|
||
"After finding the instance ID we headed over to ``/var/lib/nova/instances`` "
|
||
"to find the ``console.log``:"
|
||
msgstr ""
|
||
"Setelah menemukan ID instance kami menuju ke ``/var/lib/nova/instances`` "
|
||
"untuk menemukan ``console.log``:"
|
||
|
||
msgid ""
|
||
"After migration, users see different results from :command:`openstack image "
|
||
"list` and :command:`glance image-list`. To ensure users see the same images "
|
||
"in the list commands, edit the :file:`/etc/glance/policy.json` file and :"
|
||
"file:`/etc/nova/policy.json` file to contain ``\"context_is_admin\": \"role:"
|
||
"admin\"``, which limits access to private images for projects."
|
||
msgstr ""
|
||
"Setelah migrasi, pengguna melihat hasil yang berbeda dari :command:"
|
||
"`openstack image list` dan :command:`glance image-list`. Untuk memastikan "
|
||
"pengguna melihat image yang sama dalam perintah daftar, edit file :file:`/"
|
||
"etc/glance/policy.json` dan file :file:`/etc/nova/policy.json` yang berisi ``"
|
||
"\"context_is_admin\": \"role:admin\"``, yang membatasi akses ke image "
|
||
"pribadi untuk proyek."
|
||
|
||
msgid ""
|
||
"After reproducing the problem several times, I came to the unfortunate "
|
||
"conclusion that this cloud did indeed have a problem. Even worse, my time "
|
||
"was up in Kelowna and I had to return back to Calgary."
|
||
msgstr ""
|
||
"Setelah mereproduksi masalah beberapa kali, saya sampai pada kesimpulan yang "
|
||
"tidak menguntungkan bahwa cloud ini memang memiliki masalah. Lebih buruk "
|
||
"lagi, waktu saya habis di Kelowna dan saya harus kembali ke Calgary."
|
||
|
||
msgid ""
|
||
"After restarting the instance, everything was back up and running. We "
|
||
"reviewed the logs and saw that at some point, network communication stopped "
|
||
"and then everything went idle. We chalked this up to a random occurrence."
|
||
msgstr ""
|
||
"Setelah memulai kembali instance, semuanya kembali dan berjalan. Kami "
|
||
"meninjau log dan melihat bahwa pada titik tertentu, komunikasi jaringan "
|
||
"berhenti dan kemudian semuanya menjadi menganggur. Kami mencatat ini hingga "
|
||
"kejadian acak."
|
||
|
||
msgid ""
|
||
"After that, use the :command:`openstack` command to reboot all instances "
|
||
"that were on c01.example.com while regenerating their XML files at the same "
|
||
"time:"
|
||
msgstr ""
|
||
"Setelah itu, gunakan perintah :command:`openstack` untuk me-reboot semua "
|
||
"instance yang ada di c01.example.com saat membuat ulang file XML mereka pada "
|
||
"saat yang sama:"
|
||
|
||
msgid ""
|
||
"After the compute node is successfully running, you must deal with the "
|
||
"instances that are hosted on that compute node because none of them are "
|
||
"running. Depending on your SLA with your users or customers, you might have "
|
||
"to start each instance and ensure that they start correctly."
|
||
msgstr ""
|
||
"Setelah simpul komputasi berhasil dijalankan, Anda harus berurusan dengan "
|
||
"instance yang dihosting pada simpul komputasi tersebut karena tidak ada "
|
||
"satupun yang berjalan. Tergantung pada SLA Anda dengan pengguna atau "
|
||
"pelanggan Anda, Anda mungkin harus memulai setiap instance dan memastikan "
|
||
"bahwa mereka memulai dengan benar."
|
||
|
||
msgid "After the dnsmasq processes start again, check whether DNS is working."
|
||
msgstr "Setelah proses dnsmasq mulai lagi, periksa apakah DNS berfungsi."
|
||
|
||
msgid ""
|
||
"After the packet is on this NIC, it transfers to the compute node's default "
|
||
"gateway. The packet is now most likely out of your control at this point. "
|
||
"The diagram depicts an external gateway. However, in the default "
|
||
"configuration with multi-host, the compute host is the gateway."
|
||
msgstr ""
|
||
"Setelah paket berada di NIC ini, ia mentransfer ke gateway default node "
|
||
"komputasi. Paket sekarang kemungkinan besar di luar kendali Anda pada saat "
|
||
"ini. Diagram menggambarkan gateway eksternal. Namun, dalam konfigurasi "
|
||
"default dengan multi-host, host komputasi adalah gateway."
|
||
|
||
msgid ""
|
||
"After you consider these factors, you can determine how many cloud "
|
||
"controller cores you require. A typical eight core, 8 GB of RAM server is "
|
||
"sufficient for up to a rack of compute nodes — given the above caveats."
|
||
msgstr ""
|
||
"Setelah Anda mempertimbangkan faktor-faktor ini, Anda dapat menentukan "
|
||
"berapa banyak core pengontrol cloud yang Anda butuhkan. Server delapan core, "
|
||
"8 GB RAM biasanya cukup untuk satu rak node komputasi - mengingat peringatan "
|
||
"di atas."
|
||
|
||
msgid ""
|
||
"After you establish that the instance booted properly, the task is to figure "
|
||
"out where the failure is."
|
||
msgstr ""
|
||
"Setelah Anda memastikan bahwa instance boot dengan benar, tugasnya adalah "
|
||
"mencari tahu di mana kegagalannya."
|
||
|
||
msgid ""
|
||
"After you have the list, you can use the :command:`openstack` command to "
|
||
"start each instance:"
|
||
msgstr ""
|
||
"Setelah Anda memiliki daftar, Anda dapat menggunakan perintah :command:"
|
||
"`openstack` untuk memulai setiap instance:"
|
||
|
||
msgid ""
|
||
"Again, it turns out that the image was a snapshot. The three other instances "
|
||
"that successfully started were standard cloud images. Was it a problem with "
|
||
"snapshots? That didn't make sense."
|
||
msgstr ""
|
||
"Sekali lagi, ternyata image itu adalah snapshot. Tiga instance lain yang "
|
||
"berhasil dimulai adalah image cloud standar. Apakah itu masalah dengan foto? "
|
||
"Itu tidak masuk akal."
|
||
|
||
msgid ""
|
||
"Again, the right answer depends on your environment. You have to make your "
|
||
"decision based on the trade-offs between space utilization, simplicity, and "
|
||
"I/O performance."
|
||
msgstr ""
|
||
"Sekali lagi, jawaban yang tepat tergantung pada lingkungan Anda. Anda harus "
|
||
"membuat keputusan berdasarkan pertukaran antara pemanfaatan ruang, "
|
||
"kesederhanaan, dan kinerja I/O."
|
||
|
||
msgid "Ah-hah! So OpenStack was deleting it. But why?"
|
||
msgstr "Ah-hah! Jadi OpenStack menghapusnya. Tapi kenapa?"
|
||
|
||
msgid ""
|
||
"All files and directories in ``/var/lib/nova/instances`` are uniquely named. "
|
||
"The files in \\_base are uniquely titled for the glance image that they are "
|
||
"based on, and the directory names ``instance-xxxxxxxx`` are uniquely titled "
|
||
"for that particular instance. For example, if you copy all data from ``/var/"
|
||
"lib/nova/instances`` on one compute node to another, you do not overwrite "
|
||
"any files or cause any damage to images that have the same unique name, "
|
||
"because they are essentially the same file."
|
||
msgstr ""
|
||
"Semua file dan direktori di ``/var/lib/nova/instances`` diberi nama unik. "
|
||
"File-file di \\_base secara unik berjudul untuk glance image yang menjadi "
|
||
"dasarnya, dan nama direktori ``instance-xxxxxxxx`` secara unik berjudul "
|
||
"untuk instance tertentu. Misalnya, jika Anda menyalin semua data dari ``/"
|
||
"var/lib/nova/instances`` pada satu node komputasi ke yang lain, Anda tidak "
|
||
"menimpa file apa pun atau menyebabkan kerusakan pada image yang memiliki "
|
||
"nama unik yang sama, karena mereka adalah dasarnya file yang sama."
|
||
|
||
msgid ""
|
||
"All in all, just issue the :command:`reboot` command. The operating system "
|
||
"cleanly shuts down services and then automatically reboots. If you want to "
|
||
"be very thorough, run your backup jobs just before you reboot."
|
||
msgstr ""
|
||
"Secara keseluruhan, cukup terbitkan perintah :command:`reboot` . Sistem "
|
||
"operasi dengan bersih mematikan layanan dan kemudian secara otomatis reboot. "
|
||
"Jika Anda ingin sangat teliti, jalankan pekerjaan cadangan Anda tepat "
|
||
"sebelum Anda reboot."
|
||
|
||
msgid ""
|
||
"All interfaces on the ``br-tun`` are internal to Open vSwitch. To monitor "
|
||
"traffic on them, you need to set up a mirror port as described above for "
|
||
"``patch-tun`` in the ``br-int`` bridge."
|
||
msgstr ""
|
||
"Semua antarmuka pada ``br-tun`` bersifat internal ke Open vSwitch. Untuk "
|
||
"memantau lalu lintas, Anda perlu mengatur port mirror seperti dijelaskan di "
|
||
"atas untuk ``patch-tun`` di jembatan ``br-int``."
|
||
|
||
msgid "All nodes"
|
||
msgstr "All nodes"
|
||
|
||
msgid ""
|
||
"All of the alert types mentioned earlier can also be used for trend "
|
||
"reporting. Some other trend examples include:"
|
||
msgstr ""
|
||
"Semua jenis peringatan yang disebutkan sebelumnya juga dapat digunakan untuk "
|
||
"pelaporan tren. Beberapa contoh tren lainnya termasuk:"
|
||
|
||
msgid ""
|
||
"All of the code for OpenStack lives in ``/opt/stack``. Go to the swift "
|
||
"directory in the ``shell`` screen and edit your middleware module."
|
||
msgstr ""
|
||
"Semua kode untuk OpenStack hidup di ``/opt/stack``. Buka direktori swift di "
|
||
"layar ``shell`` dan edit modul middleware Anda."
|
||
|
||
msgid ""
|
||
"All sites are based on Ubuntu 14.04, with KVM as the hypervisor. The "
|
||
"OpenStack version in use is typically the current stable version, with 5 to "
|
||
"10 percent back-ported code from trunk and modifications."
|
||
msgstr ""
|
||
"Semua situs didasarkan pada Ubuntu 14.04, dengan KVM sebagai hypervisor. "
|
||
"Versi OpenStack yang digunakan biasanya adalah versi stabil saat ini, dengan "
|
||
"5 hingga 10 persen kode porting belakang dari trunk dan modifikasi."
|
||
|
||
msgid ""
|
||
"All translation of GRE tunnels to and from internal VLANs happens on this "
|
||
"bridge."
|
||
msgstr ""
|
||
"Semua terjemahan terowongan GRE ke dan dari VLAN internal terjadi di "
|
||
"jembatan ini."
|
||
|
||
msgid "Allow DHCP client traffic."
|
||
msgstr "Izinkan lalu lintas klien DHCP."
|
||
|
||
msgid "Allow IPv6 ICMP traffic to allow RA packets."
|
||
msgstr "Izinkan lalu lintas ICMP IPv6 untuk memungkinkan paket RA."
|
||
|
||
msgid "Allow traffic from defined IP/MAC pairs."
|
||
msgstr "Izinkan lalu lintas dari pasangan IP/MAC yang ditentukan."
|
||
|
||
msgid ""
|
||
"Almost all OpenStack components have an underlying database to store "
|
||
"persistent information. Usually this database is MySQL. Normal MySQL "
|
||
"administration is applicable to these databases. OpenStack does not "
|
||
"configure the databases out of the ordinary. Basic administration includes "
|
||
"performance tweaking, high availability, backup, recovery, and repairing. "
|
||
"For more information, see a standard MySQL administration guide."
|
||
msgstr ""
|
||
"Hampir semua komponen OpenStack memiliki basis data untuk menyimpan "
|
||
"informasi yang persisten. Biasanya database ini adalah MySQL. Administrasi "
|
||
"MySQL normal berlaku untuk database ini. OpenStack tidak mengkonfigurasi "
|
||
"basis data yang tidak biasa. Administrasi dasar mencakup penyesuaian "
|
||
"kinerja, ketersediaan tinggi, cadangan, pemulihan, dan perbaikan. Untuk "
|
||
"informasi lebih lanjut, lihat panduan administrasi MySQL standar."
|
||
|
||
msgid ""
|
||
"Also check that all services are functioning. The following set of commands "
|
||
"sources the ``openrc`` file, then runs some basic glance, nova, and "
|
||
"openstack commands. If the commands work as expected, you can be confident "
|
||
"that those services are in working condition:"
|
||
msgstr ""
|
||
"Periksa juga apakah semua layanan berfungsi. Set perintah berikut sumber "
|
||
"file ``openrc``, kemudian menjalankan beberapa perintah dasar glance, nova, "
|
||
"dan openstack. Jika perintah berfungsi seperti yang diharapkan, Anda dapat "
|
||
"yakin bahwa layanan tersebut dalam kondisi kerja:"
|
||
|
||
msgid "Also check that it is functioning:"
|
||
msgstr "Juga periksa apakah berfungsi:"
|
||
|
||
msgid "Also ensure that it has successfully connected to the AMQP server:"
|
||
msgstr "Juga memastikan bahwa ia telah berhasil terhubung ke server AMQP:"
|
||
|
||
msgid ""
|
||
"Also, in practice, the ``nova-compute`` services on the compute nodes do not "
|
||
"always reconnect cleanly to rabbitmq hosted on the controller when it comes "
|
||
"back up after a long reboot; a restart on the nova services on the compute "
|
||
"nodes is required."
|
||
msgstr ""
|
||
"Juga, dalam praktiknya, layanan ``nova-compute`` pada node komputasi tidak "
|
||
"selalu terhubung kembali dengan bersih ke rabbitmq yang dihosting pada "
|
||
"pengontrol ketika ia kembali setelah boot ulang yang panjang; diperlukan "
|
||
"restart layanan nova pada node komputasi."
|
||
|
||
msgid "Alter the configuration until it works."
|
||
msgstr "Ubah konfigurasi hingga berfungsi."
|
||
|
||
msgid ""
|
||
"Alternatively, it is possible to configure VLAN-based networks to use "
|
||
"external routers rather than the l3-agent shown here, so long as the "
|
||
"external router is on the same VLAN:"
|
||
msgstr ""
|
||
"Atau, dimungkinkan untuk mengkonfigurasi jaringan berbasis VLAN untuk "
|
||
"menggunakan router eksternal daripada agen l3 yang ditunjukkan di sini, "
|
||
"selama router eksternal berada di VLAN yang sama:"
|
||
|
||
msgid ""
|
||
"Although the title of this story is much more dramatic than the actual "
|
||
"event, I don't think, or hope, that I'll have the opportunity to use "
|
||
"\"Valentine's Day Massacre\" again in a title."
|
||
msgstr ""
|
||
"Meskipun judul cerita ini jauh lebih dramatis daripada peristiwa yang "
|
||
"sebenarnya, saya tidak berpikir, atau berharap, bahwa saya akan memiliki "
|
||
"kesempatan untuk menggunakan \"Valentine's Day Massacre\" lagi dalam sebuah "
|
||
"judul."
|
||
|
||
msgid ""
|
||
"Although this method is not documented or supported, you can use it when "
|
||
"your compute node is permanently offline but you have instances locally "
|
||
"stored on it."
|
||
msgstr ""
|
||
"Meskipun metode ini tidak didokumentasikan atau didukung, Anda dapat "
|
||
"menggunakannya saat node komputasi Anda offline secara permanen tetapi Anda "
|
||
"memiliki instance yang disimpan secara lokal di dalamnya."
|
||
|
||
msgid "Among the log statements you'll see the lines:"
|
||
msgstr "Di antara pernyataan log Anda akan melihat baris:"
|
||
|
||
msgid ""
|
||
"An OpenStack cloud does not have much value without users. This chapter "
|
||
"covers topics that relate to managing users, projects, and quotas. This "
|
||
"chapter describes users and projects as described by version 2 of the "
|
||
"OpenStack Identity API."
|
||
msgstr ""
|
||
"Cloud OpenStack tidak memiliki banyak nilai tanpa pengguna. Bab ini mencakup "
|
||
"topik yang berhubungan dengan mengelola pengguna, proyek, dan kuota. Bab ini "
|
||
"menjelaskan pengguna dan proyek sebagaimana dijelaskan oleh versi 2 dari "
|
||
"OpenStack Identity API."
|
||
|
||
msgid ""
|
||
"An advanced use of this general concept allows different flavor types to run "
|
||
"with different CPU and RAM allocation ratios so that high-intensity "
|
||
"computing loads and low-intensity development and testing systems can share "
|
||
"the same cloud without either starving the high-use systems or wasting "
|
||
"resources on low-utilization systems. This works by setting ``metadata`` in "
|
||
"your host aggregates and matching ``extra_specs`` in your flavor types."
|
||
msgstr ""
|
||
"Penggunaan lanjutan dari konsep umum ini memungkinkan jenis flavor berbeda "
|
||
"untuk dijalankan dengan rasio alokasi CPU dan RAM yang berbeda sehingga "
|
||
"beban komputasi intensitas tinggi dan pengembangan dan sistem pengujian "
|
||
"intensitas rendah dapat berbagi cloud yang sama tanpa penurunan (starving) "
|
||
"sistem penggunaan tinggi ataupun pemborosan. sumber daya pada sistem "
|
||
"pemanfaatan rendah. Ini bekerja dengan mengatur ``metadata`` di agregat host "
|
||
"Anda dan mencocokkan ``extra_specs`` dalam jenis flavor Anda."
|
||
|
||
msgid ""
|
||
"An alternative to enabling the RabbitMQ web management interface is to use "
|
||
"the ``rabbitmqctl`` commands. For example, :command:`rabbitmqctl "
|
||
"list_queues| grep cinder` displays any messages left in the queue. If there "
|
||
"are messages, it's a possible sign that cinder services didn't connect "
|
||
"properly to rabbitmq and might have to be restarted."
|
||
msgstr ""
|
||
"Alternatif untuk mengaktifkan antarmuka manajemen web RabbitMQ adalah dengan "
|
||
"menggunakan perintah ``rabbitmqctl``. Sebagai contoh, :command:`rabbitmqctl "
|
||
"list_queues| grep cinder` menampilkan pesan apa pun yang tersisa di antrian. "
|
||
"Jika ada pesan, itu kemungkinan pertanda bahwa layanan cinder tidak "
|
||
"terhubung dengan benar ke rabbitmq dan mungkin harus dimulai ulang."
|
||
|
||
msgid ""
|
||
"An attempt was made to deprecate ``nova-network`` during the Havana release, "
|
||
"which was aborted due to the lack of equivalent functionality (such as the "
|
||
"FlatDHCP multi-host high-availability mode mentioned in this guide), lack of "
|
||
"a migration path between versions, insufficient testing, and simplicity when "
|
||
"used for the more straightforward use cases ``nova-network`` traditionally "
|
||
"supported. Though significant effort has been made to address these "
|
||
"concerns, ``nova-network`` was not be deprecated in the Juno release. In "
|
||
"addition, to a limited degree, patches to ``nova-network`` have again begin "
|
||
"to be accepted, such as adding a per-network settings feature and SR-IOV "
|
||
"support in Juno."
|
||
msgstr ""
|
||
"Upaya telah dilakukan untuk menurunkan (deprecate) ``nova-network`` selama "
|
||
"rilis Havana, yang dibatalkan karena kurangnya fungsi yang setara (seperti "
|
||
"mode FlatDHCP multi-host high-availability yang disebutkan dalam panduan "
|
||
"ini), kurangnya migrasi jalur antara versi, pengujian yang tidak mencukupi, "
|
||
"dan kesederhanaan saat digunakan untuk kasus penggunaan yang lebih mudah "
|
||
"``nova-network`` yang didukung secara tradisional. Meskipun upaya signifikan "
|
||
"telah dilakukan untuk mengatasi masalah ini, ``nova-network`` tidak "
|
||
"ditinggalkan dalam rilis Juno. Selain itu, untuk tingkat yang terbatas, "
|
||
"patch ke ``nova-network`` telah mulai diterima lagi, seperti menambahkan "
|
||
"fitur pengaturan per-network dan dukungan SR-IOV di Juno."
|
||
|
||
msgid ""
|
||
"An automated deployment system installs and configures operating systems on "
|
||
"new servers, without intervention, after the absolute minimum amount of "
|
||
"manual work, including physical racking, MAC-to-IP assignment, and power "
|
||
"configuration. Typically, solutions rely on wrappers around PXE boot and "
|
||
"TFTP servers for the basic operating system install and then hand off to an "
|
||
"automated configuration management system."
|
||
msgstr ""
|
||
"Sistem penyebaran otomatis menginstal dan mengkonfigurasi sistem operasi "
|
||
"pada server baru, tanpa intervensi, setelah jumlah minimum absolut dari "
|
||
"pekerjaan manual, termasuk pemerasan fisik, penugasan MAC-ke-IP, dan "
|
||
"konfigurasi daya. Biasanya, solusi mengandalkan pembungkus (wrapper) di "
|
||
"sekitar boot PXE dan server TFTP untuk instalasi sistem operasi dasar dan "
|
||
"kemudian diserahkan ke sistem manajemen konfigurasi otomatis."
|
||
|
||
msgid "An external server outside of the cloud"
|
||
msgstr "Server eksternal di luar cloud"
|
||
|
||
msgid ""
|
||
"An hour later I received the same alert, but for another compute node. Crap. "
|
||
"OK, now there's definitely a problem going on. Just like the original node, "
|
||
"I was able to log in by SSH. The bond0 NIC was DOWN but the 1gb NIC was "
|
||
"active."
|
||
msgstr ""
|
||
"Satu jam kemudian saya menerima peringatan yang sama, tetapi untuk node "
|
||
"komputasi lain. Crap. OK, sekarang pasti ada masalah yang terjadi. Sama "
|
||
"seperti node asli, saya bisa masuk oleh SSH. Bond0 NIC BAWAH tetapi 1gb NIC "
|
||
"aktif."
|
||
|
||
msgid ""
|
||
"An initial idea was to just increase the lease time. If the instance only "
|
||
"renewed once every week, the chances of this problem happening would be "
|
||
"tremendously smaller than every minute. This didn't solve the problem, "
|
||
"though. It was just covering the problem up."
|
||
msgstr ""
|
||
"Gagasan awal adalah hanya menambah waktu sewa. Jika instance hanya "
|
||
"diperbarui sekali setiap minggu, peluang terjadinya masalah ini akan jauh "
|
||
"lebih kecil daripada setiap menit. Tapi ini tidak menyelesaikan masalah. Itu "
|
||
"hanya menutupi masalah."
|
||
|
||
msgid "An instance running on that compute node"
|
||
msgstr "Sebuah instance berjalan pada node komputasi itu"
|
||
|
||
msgid ""
|
||
"An integral part of a configuration-management system is the item that it "
|
||
"controls. You should carefully consider all of the items that you want, or "
|
||
"do not want, to be automatically managed. For example, you may not want to "
|
||
"automatically format hard drives with user data."
|
||
msgstr ""
|
||
"Bagian integral dari sistem manajemen konfigurasi adalah item yang "
|
||
"dikontrolnya. Anda harus hati-hati mempertimbangkan semua item yang Anda "
|
||
"inginkan, atau tidak ingin, dikelola secara otomatis. Misalnya, Anda mungkin "
|
||
"tidak ingin memformat hard drive dengan data pengguna secara otomatis."
|
||
|
||
msgid ""
|
||
"An upgrade pre-testing system is excellent for getting the configuration to "
|
||
"work. However, it is important to note that the historical use of the system "
|
||
"and differences in user interaction can affect the success of upgrades."
|
||
msgstr ""
|
||
"Sistem pra-testing upgrade sangat baik untuk membuat konfigurasi berfungsi. "
|
||
"Namun, penting untuk dicatat bahwa penggunaan historis sistem dan perbedaan "
|
||
"dalam interaksi pengguna dapat mempengaruhi keberhasilan upgrade."
|
||
|
||
msgid "And finally, you can disassociate the floating IP:"
|
||
msgstr "Dan akhirnya, Anda dapat melepaskan IP mengambang:"
|
||
|
||
msgid ""
|
||
"And the best part: the same user had just tried creating a CentOS instance. "
|
||
"What?"
|
||
msgstr ""
|
||
"Dan bagian terbaiknya: pengguna yang sama baru saja mencoba membuat instance "
|
||
"CentOS. Apa?"
|
||
|
||
msgid ""
|
||
"Another common concept across various OpenStack projects is that of periodic "
|
||
"tasks. Periodic tasks are much like cron jobs on traditional Unix systems, "
|
||
"but they are run inside an OpenStack process. For example, when OpenStack "
|
||
"Compute (nova) needs to work out what images it can remove from its local "
|
||
"cache, it runs a periodic task to do this."
|
||
msgstr ""
|
||
"Konsep umum lainnya di berbagai proyek OpenStack adalah tugas berkala. Tugas "
|
||
"berkala mirip dengan pekerjaan cron pada sistem Unix tradisional, tetapi "
|
||
"dijalankan di dalam proses OpenStack. Sebagai contoh, ketika OpenStack "
|
||
"Compute (nova) perlu mencari image apa yang dapat dihapus dari cache lokal, "
|
||
"itu menjalankan tugas berkala untuk melakukan ini."
|
||
|
||
msgid ""
|
||
"Any time an instance shuts down unexpectedly, it might have problems on "
|
||
"boot. For example, the instance might require an ``fsck`` on the root "
|
||
"partition. If this happens, the user can use the dashboard VNC console to "
|
||
"fix this."
|
||
msgstr ""
|
||
"Setiap kali sebuah instance dimatikan secara tak terduga, mungkin ada "
|
||
"masalah saat boot. Sebagai contoh, instance mungkin memerlukan ``fsck`` di "
|
||
"partisi root. Jika ini terjadi, pengguna dapat menggunakan konsol VNC dasbor "
|
||
"untuk memperbaikinya."
|
||
|
||
msgid "Appendix"
|
||
msgstr "Lampiran"
|
||
|
||
msgid ""
|
||
"Armed with a patched qemu and a way to reproduce, we set out to see if we've "
|
||
"finally solved The Issue. After 48 hours straight of hammering the instance "
|
||
"with bandwidth, we were confident. The rest is history. You can search the "
|
||
"bug report for \"joe\" to find my comments and actual tests."
|
||
msgstr ""
|
||
"Dipersenjatai dengan qemu yang di-patch dan cara untuk mereproduksi, kami "
|
||
"berangkat untuk melihat apakah kami akhirnya telah menyelesaikan The Issue. "
|
||
"Setelah 48 jam terus-menerus memukul instance dengan bandwidth, kami yakin. "
|
||
"Sisanya (the rest) adalah sejarah. Anda dapat mencari \"bug\" laporan bug "
|
||
"untuk menemukan komentar saya dan tes yang sebenarnya."
|
||
|
||
msgid ""
|
||
"Artificial scale testing can go only so far. After your cloud is upgraded, "
|
||
"you must pay careful attention to the performance aspects of your cloud."
|
||
msgstr ""
|
||
"Pengujian skala buatan hanya bisa sejauh ini. Setelah cloud Anda "
|
||
"ditingkatkan (upgraded), Anda harus memperhatikan aspek kinerja cloud Anda."
|
||
|
||
msgid ""
|
||
"As a cloud administrative user, you can use the OpenStack dashboard to "
|
||
"create and manage projects, users, images, and flavors. Users are allowed to "
|
||
"create and manage images within specified projects and to share images, "
|
||
"depending on the Image service configuration. Typically, the policy "
|
||
"configuration allows admin users only to set quotas and create and manage "
|
||
"services. The dashboard provides an :guilabel:`Admin` tab with a :guilabel:"
|
||
"`System Panel` and an :guilabel:`Identity` tab. These interfaces give you "
|
||
"access to system information and usage as well as to settings for "
|
||
"configuring what end users can do. Refer to the `Horizon Administration "
|
||
"Guide <https://docs.openstack.org/horizon/latest/admin/>`_ for detailed how-"
|
||
"to information about using the dashboard as an admin user."
|
||
msgstr ""
|
||
"Sebagai pengguna cloud administrasi, Anda dapat menggunakan dasbor OpenStack "
|
||
"untuk membuat dan mengelola proyek, pengguna, image, dan flavor. Pengguna "
|
||
"diizinkan untuk membuat dan mengelola image dalam proyek yang ditentukan dan "
|
||
"untuk berbagi image, tergantung pada konfigurasi layanan Image. Biasanya, "
|
||
"konfigurasi kebijakan hanya mengizinkan pengguna admin untuk menetapkan "
|
||
"kuota dan membuat serta mengelola layanan. Dasbor menyediakan tab :guilabel: "
|
||
"`Admin` dengan :guilabel:` System Panel` dan sebuah tab :guilabel: "
|
||
"`Identity`. Antarmuka ini memberi Anda akses ke informasi dan penggunaan "
|
||
"sistem serta pengaturan untuk mengonfigurasi apa yang dapat dilakukan end "
|
||
"user. Mengacu kepada `Horizon Administration Guide <https://docs.openstack."
|
||
"org/horizon/latest/admin/>`_ untuk informasi rinci tentang cara menggunakan "
|
||
"dasbor sebagai pengguna admin."
|
||
|
||
msgid ""
|
||
"As a last resort, our network admin (Alvaro) and myself sat down with four "
|
||
"terminal windows, a pencil, and a piece of paper. In one window, we ran "
|
||
"ping. In the second window, we ran ``tcpdump`` on the cloud controller. In "
|
||
"the third, ``tcpdump`` on the compute node. And the forth had ``tcpdump`` on "
|
||
"the instance. For background, this cloud was a multi-node, non-multi-host "
|
||
"setup."
|
||
msgstr ""
|
||
"Sebagai upaya terakhir, admin jaringan kami (Alvaro) dan saya sendiri duduk "
|
||
"dengan empat windows terminal, pensil, dan selembar kertas. Di satu jendela, "
|
||
"kami menjalankan ping. Di windows kedua, kami menjalankan ``tcpdump`` pada "
|
||
"pengontrol cloud. Pada yang ketiga, ``tcpdump`` pada compute node. Dan "
|
||
"keempat memiliki ``tcpdump`` pada instance. Sebagai latar belakang, cloud "
|
||
"ini merupakan pengaturan multi-node, non-multi-host."
|
||
|
||
msgid ""
|
||
"As a specific example, compare a cloud that supports a managed web-hosting "
|
||
"platform with one running integration tests for a development project that "
|
||
"creates one VM per code commit. In the former, the heavy work of creating a "
|
||
"VM happens only every few months, whereas the latter puts constant heavy "
|
||
"load on the cloud controller. You must consider your average VM lifetime, as "
|
||
"a larger number generally means less load on the cloud controller."
|
||
msgstr ""
|
||
"Sebagai contoh spesifik, bandingkan cloud yang mendukung platform hosting "
|
||
"web yang dikelola dengan satu yang menjalankan tes integrasi untuk proyek "
|
||
"pengembangan yang membuat satu VM per komit kode. Dalam yang pertama, "
|
||
"pekerjaan berat menciptakan VM terjadi hanya setiap beberapa bulan, "
|
||
"sedangkan yang terakhir menempatkan beban berat konstan pada pengendali "
|
||
"cloud. Anda harus mempertimbangkan masa pakai VM rata-rata, karena jumlah "
|
||
"yang lebih besar umumnya berarti lebih sedikit beban pada pengontrol cloud."
|
||
|
||
msgid ""
|
||
"As an OpenStack cloud is composed of so many different services, there are a "
|
||
"large number of log files. This chapter aims to assist you in locating and "
|
||
"working with them and describes other ways to track the status of your "
|
||
"deployment."
|
||
msgstr ""
|
||
"Karena cloud OpenStack terdiri dari begitu banyak layanan yang berbeda, ada "
|
||
"banyak file log. Bab ini bertujuan untuk membantu Anda menemukan dan bekerja "
|
||
"dengan mereka dan menjelaskan cara-cara lain untuk melacak status penempatan "
|
||
"Anda."
|
||
|
||
msgid ""
|
||
"As an administrative user, you can update the Block Storage service quotas "
|
||
"for a tenant, as well as update the quota defaults for a new tenant. See :"
|
||
"ref:`table_block_storage_quota`."
|
||
msgstr ""
|
||
"Sebagai pengguna administratif, Anda dapat memperbarui kuota layanan Block "
|
||
"Storage untuk tenant, serta memperbarui kuota default untuk tenant baru. "
|
||
"Lihat :ref:`table_block_storage_quota`."
|
||
|
||
msgid ""
|
||
"As an administrative user, you can update the Compute service quotas for an "
|
||
"existing tenant, as well as update the quota defaults for a new tenant. See :"
|
||
"ref:`table_compute_quota`."
|
||
msgstr ""
|
||
"Sebagai pengguna administratif, Anda dapat memperbarui kuota layanan Compute "
|
||
"untuk penyewa yang ada, serta memperbarui kuota default untuk penyewa baru. "
|
||
"Lihat :ref:`table_compute_quota`."
|
||
|
||
msgid ""
|
||
"As an administrative user, you can use the :command:`cinder quota-*` "
|
||
"commands, which are provided by the ``python-cinderclient`` package, to view "
|
||
"and update tenant quotas."
|
||
msgstr ""
|
||
"Sebagai pengguna administratif, Anda dapat menggunakan perintah :command:"
|
||
"`cinder quota-*`, yang disediakan oleh paket ``python-cinderclient``, untuk "
|
||
"melihat dan memperbarui kuota tenant."
|
||
|
||
msgid ""
|
||
"As an administrator, you have a few ways to discover what your OpenStack "
|
||
"cloud looks like simply by using the OpenStack tools available. This section "
|
||
"gives you an idea of how to get an overview of your cloud, its shape, size, "
|
||
"and current state."
|
||
msgstr ""
|
||
"Sebagai administrator, Anda memiliki beberapa cara untuk menemukan seperti "
|
||
"apa cloud OpenStack Anda hanya dengan menggunakan alat OpenStack yang "
|
||
"tersedia. Bagian ini memberi Anda gambaran tentang cara mendapatkan ikhtisar "
|
||
"cloud, bentuk, ukuran, dan kondisi saat ini."
|
||
|
||
msgid ""
|
||
"As an example, recording ``nova-api`` usage can allow you to track the need "
|
||
"to scale your cloud controller. By keeping an eye on ``nova-api`` requests, "
|
||
"you can determine whether you need to spawn more ``nova-api`` processes or "
|
||
"go as far as introducing an entirely new server to run ``nova-api``. To get "
|
||
"an approximate count of the requests, look for standard INFO messages in ``/"
|
||
"var/log/nova/nova-api.log``:"
|
||
msgstr ""
|
||
"Sebagai contoh, merekam penggunaan ``nova-api`` dapat memungkinkan Anda "
|
||
"untuk melacak kebutuhan untuk meningkatkan skala pengontrol cloud Anda. "
|
||
"Dengan mengawasi permintaan ``nova-api``, Anda dapat menentukan apakah Anda "
|
||
"perlu menelurkan (spawn) lebih banyak proses ``nova-api`` atau sejauh "
|
||
"memperkenalkan server yang sama sekali baru untuk menjalankan ``nova-api`` . "
|
||
"Untuk mendapatkan perkiraan jumlah permintaan, cari pesan INFO standar di ``/"
|
||
"var/log/nova/nova-api.log``:"
|
||
|
||
msgid ""
|
||
"As for your initial deployment, you should ensure that all hardware is "
|
||
"appropriately burned in before adding it to production. Run software that "
|
||
"uses the hardware to its limits—maxing out RAM, CPU, disk, and network. Many "
|
||
"options are available, and normally double as benchmark software, so you "
|
||
"also get a good idea of the performance of your system."
|
||
msgstr ""
|
||
"Apapun penyebaran awal Anda, Anda harus memastikan bahwa semua perangkat "
|
||
"keras dibakar (burned) secara tepat sebelum menambahkannya ke produksi. "
|
||
"Jalankan perangkat lunak yang menggunakan perangkat keras hingga batasnya — "
|
||
"memaksimalkan RAM, CPU, disk, dan jaringan. Banyak pilihan yang tersedia, "
|
||
"dan biasanya berfungsi ganda sebagai perangkat lunak benchmark, jadi Anda "
|
||
"juga mendapatkan ide bagus tentang kinerja sistem Anda."
|
||
|
||
msgid ""
|
||
"As mentioned, there's currently no way to cleanly migrate from ``nova-"
|
||
"network`` to neutron. We recommend that you keep a migration in mind and "
|
||
"what that process might involve for when a proper migration path is released."
|
||
msgstr ""
|
||
"Seperti yang disebutkan, saat ini tidak ada cara untuk bermigrasi secara "
|
||
"bersih dari ``nova-network`` ke neutron. Kami menyarankan Anda mengingat "
|
||
"migrasi dan apa proses yang mungkin terlibat ketika jalur migrasi yang tepat "
|
||
"dirilis."
|
||
|
||
msgid "As soon as this setting was fixed, everything worked."
|
||
msgstr "Segera setelah pengaturan ini diperbaiki, semuanya bekerja."
|
||
|
||
msgid "As this would be the server's bonded NIC."
|
||
msgstr "Karena ini akan menjadi NIC yang terikat pada server."
|
||
|
||
msgid ""
|
||
"As with most architecture choices, the right answer depends on your "
|
||
"environment. If you are using existing hardware, you know the disk density "
|
||
"of your servers and can determine some decisions based on the options above. "
|
||
"If you are going through a procurement process, your user's requirements "
|
||
"also help you determine hardware purchases. Here are some examples from a "
|
||
"private cloud providing web developers custom environments at AT&T. This "
|
||
"example is from a specific deployment, so your existing hardware or "
|
||
"procurement opportunity may vary from this. AT&T uses three types of "
|
||
"hardware in its deployment:"
|
||
msgstr ""
|
||
"As with most architecture choices, the right answer depends on your "
|
||
"environment. If you are using existing hardware, you know the disk density "
|
||
"of your servers and can determine some decisions based on the options above. "
|
||
"If you are going through a procurement process, your user's requirements "
|
||
"also help you determine hardware purchases. Here are some examples from a "
|
||
"private cloud providing web developers custom environments at AT&T. This "
|
||
"example is from a specific deployment, so your existing hardware or "
|
||
"procurement opportunity may vary from this. AT&T uses three types of "
|
||
"hardware in its deployment:"
|
||
|
||
msgid ""
|
||
"As your cloud grows, MySQL is utilized more and more. If you suspect that "
|
||
"MySQL might be becoming a bottleneck, you should start researching MySQL "
|
||
"optimization. The MySQL manual has an entire section dedicated to this "
|
||
"topic: `Optimization Overview <https://dev.mysql.com/doc/refman/5.5/en/"
|
||
"optimize-overview.html>`_."
|
||
msgstr ""
|
||
"Seiring cloud Anda tumbuh, MySQL semakin banyak digunakan. Jika Anda "
|
||
"mencurigai bahwa MySQL mungkin menjadi hambatan, Anda harus mulai meneliti "
|
||
"optimasi MySQL. Manual MySQL memiliki seluruh bagian yang didedikasikan "
|
||
"untuk topik ini: `Optimization Overview <https://dev.mysql.com/doc/"
|
||
"refman/5.5/en/optimize-overview.html>`_."
|
||
|
||
msgid ""
|
||
"As your focus turns to stable operations, we recommend that you do skim this "
|
||
"guide to get a sense of the content. Some of this content is useful to read "
|
||
"in advance so that you can put best practices into effect to simplify your "
|
||
"life in the long run. Other content is more useful as a reference that you "
|
||
"might turn to when an unexpected event occurs (such as a power failure), or "
|
||
"to troubleshoot a particular problem."
|
||
msgstr ""
|
||
"Saat fokus Anda beralih ke operasi yang stabil, kami sarankan Anda membaca "
|
||
"panduan ini untuk memahami kontennya. Beberapa konten ini bermanfaat untuk "
|
||
"dibaca terlebih dahulu sehingga Anda dapat menerapkan praktik terbaik untuk "
|
||
"menyederhanakan hidup Anda dalam jangka panjang. Konten lain lebih "
|
||
"bermanfaat sebagai referensi yang dapat Anda gunakan ketika terjadi "
|
||
"peristiwa tak terduga (seperti listrik mati), atau memecahkan masalah "
|
||
"tertentu."
|
||
|
||
msgid ""
|
||
"Aside from connection failures, RabbitMQ log files are generally not useful "
|
||
"for debugging OpenStack related issues. Instead, we recommend you use the "
|
||
"RabbitMQ web management interface. Enable it on your cloud controller:"
|
||
msgstr ""
|
||
"Selain dari kegagalan koneksi, file log RabbitMQ umumnya tidak berguna untuk "
|
||
"debugging masalah terkait OpenStack. Sebagai gantinya, kami sarankan Anda "
|
||
"menggunakan antarmuka manajemen web RabbitMQ. Aktifkan di pengontrol cloud "
|
||
"Anda:"
|
||
|
||
msgid ""
|
||
"Aside from the creation and termination of VMs, you must consider the impact "
|
||
"of users accessing the service particularly on ``nova-api`` and its "
|
||
"associated database. Listing instances garners a great deal of information "
|
||
"and, given the frequency with which users run this operation, a cloud with a "
|
||
"large number of users can increase the load significantly. This can occur "
|
||
"even without their knowledge. For example, leaving the OpenStack dashboard "
|
||
"instances tab open in the browser refreshes the list of VMs every 30 seconds."
|
||
msgstr ""
|
||
"Selain pembuatan dan penghentian VM, Anda harus mempertimbangkan dampak dari "
|
||
"pengguna yang mengakses layanan khususnya pada ``nova-api`` dan database "
|
||
"terkaitnya. Mendaftar instance mengumpulkan banyak informasi dan, mengingat "
|
||
"frekuensi pengguna menjalankan operasi ini, cloud dengan sejumlah besar "
|
||
"pengguna dapat meningkatkan beban secara signifikan. Ini dapat terjadi "
|
||
"bahkan tanpa sepengetahuan mereka. Misalnya, membiarkan tab instance dasbor "
|
||
"OpenStack terbuka di browser menyegarkan daftar VM setiap 30 detik."
|
||
|
||
msgid ""
|
||
"Aside from the direct-to-blueprint pathway, there is another very well-"
|
||
"regarded mechanism to influence the development roadmap: the user survey. "
|
||
"Found at `OpenStack User Survey <https://www.openstack.org/user-survey/>`_, "
|
||
"it allows you to provide details of your deployments and needs, anonymously "
|
||
"by default. Each cycle, the user committee analyzes the results and produces "
|
||
"a report, including providing specific information to the technical "
|
||
"committee and project team leads."
|
||
msgstr ""
|
||
"Selain dari jalur direct-to-blueprint, ada mekanisme lain yang sangat "
|
||
"dipertimbangkan untuk memengaruhi roadmap pengembangan: survei pengguna. "
|
||
"Ditemukan di `OpenStack User Survey <https://www.openstack.org/user-survey/"
|
||
">` _, ini memungkinkan Anda untuk memberikan rincian penyebaran dan "
|
||
"kebutuhan Anda, secara anonim secara default. Setiap siklus, komite pengguna "
|
||
"menganalisis hasil dan menghasilkan laporan, termasuk memberikan informasi "
|
||
"spesifik kepada komite teknis dan pimpinan tim proyek."
|
||
|
||
msgid "Aspects to Watch"
|
||
msgstr "Aspects to Watch (aspek untuk dilihat)"
|
||
|
||
msgid "Assign a lost IPv4 address back to a project"
|
||
msgstr "Mengangkat alamat IPv4 yang hilang kembali ke proyek"
|
||
|
||
msgid ""
|
||
"At that time, our control services were hosted by another team and we didn't "
|
||
"have much debugging information to determine what was going on with the "
|
||
"master, and we could not reboot it. That team noted that it failed without "
|
||
"alert, but managed to reboot it. After an hour, the cluster had returned to "
|
||
"its normal state and we went home for the day."
|
||
msgstr ""
|
||
"Pada saat itu, layanan kontrol kami dihosting oleh tim lain dan kami tidak "
|
||
"memiliki banyak informasi debug untuk menentukan apa yang terjadi dengan "
|
||
"master, dan kami tidak dapat mem-boot ulang. Tim itu mencatat bahwa ia gagal "
|
||
"tanpa peringatan, tetapi berhasil mem-boot ulangnya. Setelah satu jam, gugus "
|
||
"telah kembali ke keadaan normal dan kami pulang untuk hari itu."
|
||
|
||
msgid ""
|
||
"At the data center, I was finishing up some tasks and remembered the lock-"
|
||
"up. I logged into the new instance and ran :command:`ps aux` again. It "
|
||
"worked. Phew. I decided to run it one more time. It locked up."
|
||
msgstr ""
|
||
"Di pusat data, saya menyelesaikan beberapa tugas dan mengingat "
|
||
"pengunciannya. Saya masuk ke instance baru dan menjalankan: command: `ps "
|
||
"aux` lagi. Itu berhasil. Fiuh. Saya memutuskan untuk menjalankannya sekali "
|
||
"lagi. Terkunci."
|
||
|
||
msgid ""
|
||
"At the end of 2012, Cybera (a nonprofit with a mandate to oversee the "
|
||
"development of cyberinfrastructure in Alberta, Canada) deployed an updated "
|
||
"OpenStack cloud for their `DAIR project <https://www.canarie.ca/cloud/>`_. A "
|
||
"few days into production, a compute node locks up. Upon rebooting the node, "
|
||
"I checked to see what instances were hosted on that node so I could boot "
|
||
"them on behalf of the customer. Luckily, only one instance."
|
||
msgstr ""
|
||
"Pada akhir 2012, Cybera (sebuah organisasi nirlaba dengan mandat untuk "
|
||
"mengawasi pengembangan infrastruktur cyber di Alberta, Kanada) mengerahkan "
|
||
"OpenStack cloud yang diperbarui untuk proyek mereka `DAIR project <https://"
|
||
"www.canarie.ca/cloud/>` _ . Beberapa hari setelah produksi, sebuah node "
|
||
"komputasi terkunci. Setelah me-reboot node, saya memeriksa untuk melihat "
|
||
"instance apa yang di-host pada node itu sehingga saya bisa mem-bootnya atas "
|
||
"nama pelanggan. Untungnya, hanya satu instance."
|
||
|
||
msgid ""
|
||
"At the end of August 2012, a post-secondary school in Alberta, Canada "
|
||
"migrated its infrastructure to an OpenStack cloud. As luck would have it, "
|
||
"within the first day or two of it running, one of their servers just "
|
||
"disappeared from the network. Blip. Gone."
|
||
msgstr ""
|
||
"Pada akhir Agustus 2012, sebuah sekolah pasca sekolah menengah di Alberta, "
|
||
"Kanada memigrasikan infrastrukturnya ke cloud OpenStack. Seperti "
|
||
"keberuntungan, dalam hari pertama atau kedua berjalan, salah satu server "
|
||
"mereka hilang dari jaringan. Blip. Hilang."
|
||
|
||
msgid ""
|
||
"At the same time of finding the bug report, a co-worker was able to "
|
||
"successfully reproduce The Issue! How? He used ``iperf`` to spew a ton of "
|
||
"bandwidth at an instance. Within 30 minutes, the instance just disappeared "
|
||
"from the network."
|
||
msgstr ""
|
||
"Pada saat yang sama menemukan laporan bug, rekan kerja berhasil mereproduksi "
|
||
"The Issue! How? Dia menggunakan ``iperf`` untuk memuntahkan satu ton "
|
||
"bandwidth pada sebuah instance. Dalam 30 menit, instance baru saja "
|
||
"menghilang dari jaringan."
|
||
|
||
msgid ""
|
||
"At the time of writing, OpenStack has more than 3,000 configuration options. "
|
||
"You can see them documented at the `OpenStack Configuration Reference "
|
||
"<https://docs.openstack.org/ocata/config-reference/config-overview.html>`_. "
|
||
"This chapter cannot hope to document all of these, but we do try to "
|
||
"introduce the important concepts so that you know where to go digging for "
|
||
"more information."
|
||
msgstr ""
|
||
"Pada saat penulisan, OpenStack memiliki lebih dari 3.000 opsi konfigurasi. "
|
||
"Anda dapat melihatnya didokumentasikan di `OpenStack Configuration Reference "
|
||
"<https://docs.openstack.org/ocata/config-reference/config-overview.html>`_. "
|
||
"Bab ini tidak dapat berharap untuk mendokumentasikan semua ini, tetapi kami "
|
||
"mencoba memperkenalkan konsep-konsep penting sehingga Anda tahu ke mana "
|
||
"harus mencari informasi lebih lanjut."
|
||
|
||
msgid ""
|
||
"At the very base of any operating system are the hard drives on which the "
|
||
"operating system (OS) is installed."
|
||
msgstr ""
|
||
"Di bagian paling dasar dari setiap sistem operasi adalah hard drive tempat "
|
||
"sistem operasi (OS) diinstal."
|
||
|
||
msgid ""
|
||
"Attack vectors increase further in a public facing OpenStack deployment. For "
|
||
"example, the API endpoints and the software behind it become vulnerable to "
|
||
"hostile entities attempting to gain unauthorized access or prevent access to "
|
||
"services. You should provide appropriate filtering and periodic security "
|
||
"auditing."
|
||
msgstr ""
|
||
"Vektor serangan meningkat lebih lanjut di publik yang menghadapi penyebaran "
|
||
"OpenStack. Misalnya, endpoint API dan perangkat lunak di belakangnya menjadi "
|
||
"rentan terhadap entitas yang bermusuhan yang berusaha mendapatkan akses "
|
||
"tidak sah atau mencegah akses ke layanan. Anda harus memberikan penyaringan "
|
||
"yang sesuai dan audit keamanan berkala."
|
||
|
||
msgid "Attempt to boot a nova instance in the affected environment."
|
||
msgstr "Mencoba mem-boot instance nova di lingkungan yang terpengaruh."
|
||
|
||
msgid "Attempt to list the objects in the ``middleware-test`` container:"
|
||
msgstr ""
|
||
"Cobalah untuk membuat daftar objek dalam kontainer ``middleware-test``:"
|
||
|
||
msgid "Automated configuration"
|
||
msgstr "Konfigurasi otomatis"
|
||
|
||
msgid "Automated deployment"
|
||
msgstr "Penyebaran otomatis"
|
||
|
||
msgid "Availability zone"
|
||
msgstr "Zona ketersediaan"
|
||
|
||
msgid "Availability zones"
|
||
msgstr "Availability zones"
|
||
|
||
msgid "Availability zones and host aggregates"
|
||
msgstr "Zona ketersediaan dan agregat host"
|
||
|
||
msgid "Available vCPUs"
|
||
msgstr "Available vCPUs"
|
||
|
||
msgid ""
|
||
"Back in your DevStack instance on the shell screen, add some metadata to "
|
||
"your container to allow the request from the remote machine:"
|
||
msgstr ""
|
||
"Kembali ke instance DevStack Anda pada layar shell, tambahkan beberapa "
|
||
"metadata ke kontainer Anda untuk memungkinkan permintaan dari mesin jarak "
|
||
"jauh:"
|
||
|
||
msgid ""
|
||
"Back up HOT template ``yaml`` files, and the ``/etc/heat/`` directory "
|
||
"containing Orchestration configuration files."
|
||
msgstr ""
|
||
"Buat cadangan file templat HOT ``yaml``, dan direktori ``/etc/heat/`` yang "
|
||
"berisi file konfigurasi Orchestration."
|
||
|
||
msgid ""
|
||
"Back up the ``/etc/ceilometer`` directory containing Telemetry configuration "
|
||
"files."
|
||
msgstr ""
|
||
"Cadangkan direktori ``/etc/ceilometer`` yang berisi file konfigurasi "
|
||
"Telemetry."
|
||
|
||
msgid "Backing storage services"
|
||
msgstr "Mendukung layanan penyimpanan"
|
||
|
||
msgid "Backup and Recovery"
|
||
msgstr "Cadangan dan Pemulihan"
|
||
|
||
msgid ""
|
||
"Backup and subsequent recovery is one of the first tasks system "
|
||
"administrators learn. However, each system has different items that need "
|
||
"attention. By taking care of your database, image service, and appropriate "
|
||
"file system locations, you can be assured that you can handle any event "
|
||
"requiring recovery."
|
||
msgstr ""
|
||
"Pencadangan dan pemulihan selanjutnya adalah salah satu tugas pertama yang "
|
||
"dipelajari oleh administrator sistem. Namun, setiap sistem memiliki item "
|
||
"berbeda yang perlu diperhatikan. Dengan menjaga basis data, layanan gambar, "
|
||
"dan lokasi sistem file yang sesuai, Anda dapat yakin bahwa Anda dapat "
|
||
"menangani segala peristiwa yang membutuhkan pemulihan."
|
||
|
||
msgid "Bare metal Deployment (ironic)"
|
||
msgstr "Penggunaan bare-metal (ironic)"
|
||
|
||
msgid "Baremetal security"
|
||
msgstr "Keamanan baremetal"
|
||
|
||
msgid ""
|
||
"Be mindful of consistency when utilizing third party clouds to explore "
|
||
"authentication options."
|
||
msgstr ""
|
||
"Berhati-hatilah terhadap konsistensi saat menggunakan cloud pihak ketiga "
|
||
"untuk menjelajahi opsi otentikasi."
|
||
|
||
msgid ""
|
||
"Be sure that the instance has successfully booted and is at a login screen "
|
||
"before doing the above."
|
||
msgstr ""
|
||
"Pastikan instance telah berhasil di-boot dan berada di layar login sebelum "
|
||
"melakukan hal di atas."
|
||
|
||
msgid ""
|
||
"Because it is recommended to not use partitions on a swift disk, simply "
|
||
"format the disk as a whole:"
|
||
msgstr ""
|
||
"Karena disarankan untuk tidak menggunakan partisi pada swift disk, cukup "
|
||
"format disk secara keseluruhan:"
|
||
|
||
msgid ""
|
||
"Because of the high redundancy of Object Storage, dealing with object "
|
||
"storage node issues is a lot easier than dealing with compute node issues."
|
||
msgstr ""
|
||
"Karena redundansi yang tinggi dari Object Storage, berurusan dengan masalah "
|
||
"node penyimpanan objek jauh lebih mudah daripada berurusan dengan masalah "
|
||
"node komputasi."
|
||
|
||
msgid ""
|
||
"Because without sensible quotas a single tenant could use up all the "
|
||
"available resources, default quotas are shipped with OpenStack. You should "
|
||
"pay attention to which quota settings make sense for your hardware "
|
||
"capabilities."
|
||
msgstr ""
|
||
"Karena tanpa kuota yang masuk akal penyewa tunggal dapat menggunakan semua "
|
||
"sumber daya yang tersedia, kuota default dikirimkan dengan OpenStack. Anda "
|
||
"harus memperhatikan pengaturan kuota yang masuk akal untuk kemampuan "
|
||
"perangkat keras Anda."
|
||
|
||
msgid ""
|
||
"Because your cloud is most likely composed of many servers, you must check "
|
||
"logs on each of those servers to properly piece an event together. A better "
|
||
"solution is to send the logs of all servers to a central location so that "
|
||
"they can all be accessed from the same area."
|
||
msgstr ""
|
||
"Karena cloud Anda kemungkinan besar terdiri dari banyak server, Anda harus "
|
||
"memeriksa log pada masing-masing server untuk menyatukan acara dengan benar. "
|
||
"Solusi yang lebih baik adalah dengan mengirim log dari semua server ke "
|
||
"lokasi pusat sehingga semuanya dapat diakses dari area yang sama."
|
||
|
||
msgid ""
|
||
"Betsy Hagemeier, a Fanatical Executive Assistant, took care of a room "
|
||
"reshuffle and helped us settle in for the week."
|
||
msgstr ""
|
||
"Betsy Hagemeier, Asisten Eksekutif Fanatik, mengurus perombakan kamar dan "
|
||
"membantu kami menetap selama seminggu."
|
||
|
||
msgid "Block Storage"
|
||
msgstr "Block Storage"
|
||
|
||
msgid "Block Storage Improvements"
|
||
msgstr "Peningkatan Block Storage"
|
||
|
||
msgid ""
|
||
"Block Storage is considered a stable project, with wide uptake and a long "
|
||
"track record of quality drivers. The team has discussed many areas of work "
|
||
"at the summits, including better error reporting, automated discovery, and "
|
||
"thin provisioning features."
|
||
msgstr ""
|
||
"Block Storage dianggap sebagai proyek yang stabil, dengan serapan luas dan "
|
||
"rekam jejak yang panjang mengenai driver berkualitas. Tim telah membahas "
|
||
"banyak bidang pekerjaan di puncak, termasuk pelaporan kesalahan yang lebih "
|
||
"baik, penemuan otomatis, dan fitur thin provisioning."
|
||
|
||
msgid "Block Storage nodes"
|
||
msgstr "Block Storage nodes"
|
||
|
||
msgid "Block Storage service"
|
||
msgstr "Layanan Block Storage"
|
||
|
||
msgid ""
|
||
"Block Storage service - Updating the Block Storage service only requires "
|
||
"restarting the service."
|
||
msgstr ""
|
||
"Layanan Block Storage - Update layanan Block Storage hanya membutuhkan "
|
||
"restarting layanan."
|
||
|
||
msgid "Boot a test server:"
|
||
msgstr "Boot server uji:"
|
||
|
||
msgid ""
|
||
"Both Compute and Block Storage rely on schedulers to determine where to "
|
||
"place virtual machines or volumes. In Havana, the Compute scheduler "
|
||
"underwent significant improvement, while in Icehouse it was the scheduler in "
|
||
"Block Storage that received a boost. Further down the track, an effort "
|
||
"started this cycle that aims to create a holistic scheduler covering both "
|
||
"will come to fruition. Some of the work that was done in Kilo can be found "
|
||
"under the `Gantt project <https://wiki.openstack.org/wiki/Gantt/kilo>`_."
|
||
msgstr ""
|
||
"Compute dan Block Storage keduanya bergantung pada penjadwal untuk "
|
||
"menentukan di mana menempatkan mesin atau volume virtual. Di Havana, "
|
||
"penjadwal Compute mengalami peningkatan yang signifikan, sedangkan di "
|
||
"Icehouse itu penjadwal di Block Storage yang menerima dorongan. Lebih jauh "
|
||
"ke bawah jalur, upaya memulai siklus ini yang bertujuan untuk membuat "
|
||
"penjadwal holistik yang mencakup keduanya akan membuahkan hasil. Beberapa "
|
||
"pekerjaan yang dilakukan di Kilo dapat ditemukan di bawah `Gantt project "
|
||
"<https://wiki.openstack.org/wiki/Gantt/kilo>`_."
|
||
|
||
msgid ""
|
||
"Both Ubuntu and Red Hat Enterprise Linux include mechanisms for configuring "
|
||
"the operating system, including preseed and kickstart, that you can use "
|
||
"after a network boot. Typically, these are used to bootstrap an automated "
|
||
"configuration system. Alternatively, you can use an image-based approach for "
|
||
"deploying the operating system, such as systemimager. You can use both "
|
||
"approaches with a virtualized infrastructure, such as when you run VMs to "
|
||
"separate your control services and physical infrastructure."
|
||
msgstr ""
|
||
"Ubuntu dan Red Hat Enterprise Linux menyertakan mekanisme untuk "
|
||
"mengkonfigurasi sistem operasi, termasuk preseed dan kickstart, yang dapat "
|
||
"Anda gunakan setelah boot jaringan. Biasanya, ini digunakan untuk mem-"
|
||
"bootstrap sistem konfigurasi otomatis. Atau, Anda dapat menggunakan "
|
||
"pendekatan berbasis image untuk menggunakan sistem operasi, seperti "
|
||
"systemimager. Anda dapat menggunakan kedua pendekatan dengan infrastruktur "
|
||
"tervirtualisasi, seperti ketika Anda menjalankan VM untuk memisahkan layanan "
|
||
"kontrol dan infrastruktur fisik Anda."
|
||
|
||
msgid "Burn-in Testing"
|
||
msgstr "Burn-in Testing"
|
||
|
||
msgid ""
|
||
"But how can you tell whether images are being successfully uploaded to the "
|
||
"Image service? Maybe the disk that Image service is storing the images on is "
|
||
"full or the S3 back end is down. You could naturally check this by doing a "
|
||
"quick image upload:"
|
||
msgstr ""
|
||
"Tetapi bagaimana Anda bisa tahu apakah image berhasil diunggah ke layanan "
|
||
"Image? Mungkin disk tempat layanan Image menyimpan image pada penuh atau S3 "
|
||
"back end turun. Anda secara alami dapat memeriksanya dengan melakukan "
|
||
"unggahan image cepat:"
|
||
|
||
msgid ""
|
||
"By comparing a tenant's hard limit with their current resource usage, you "
|
||
"can see their usage percentage. For example, if this tenant is using 1 "
|
||
"floating IP out of 10, then they are using 10 percent of their floating IP "
|
||
"quota. Rather than doing the calculation manually, you can use SQL or the "
|
||
"scripting language of your choice and create a formatted report:"
|
||
msgstr ""
|
||
"Dengan membandingkan batas keras penyewa dengan penggunaan sumber daya "
|
||
"mereka saat ini, Anda dapat melihat persentase penggunaannya. Misalnya, jika "
|
||
"penyewa ini menggunakan 1 IP mengambang dari 10, maka mereka menggunakan 10 "
|
||
"persen kuota IP mengambang mereka. Daripada melakukan perhitungan secara "
|
||
"manual, Anda dapat menggunakan SQL atau bahasa scripting pilihan Anda dan "
|
||
"membuat laporan yang diformat:"
|
||
|
||
msgid "By default, Object Storage logs to syslog."
|
||
msgstr "Secara default, Object Storage mencatat log ke syslog."
|
||
|
||
msgid ""
|
||
"By mistake, I configured OpenStack to attach all tenant VLANs to vlan20 "
|
||
"instead of bond0 thereby stacking one VLAN on top of another. This added an "
|
||
"extra 4 bytes to each packet and caused a packet of 1504 bytes to be sent "
|
||
"out which would cause problems when it arrived at an interface that only "
|
||
"accepted 1500."
|
||
msgstr ""
|
||
"Secara tidak sengaja, saya mengkonfigurasi OpenStack untuk melampirkan semua "
|
||
"tenant VLAN ke vlan20 dan bukannya bond0 sehingga menumpuk satu VLAN di atas "
|
||
"yang lain. Ini menambahkan 4 byte tambahan untuk setiap paket dan "
|
||
"menyebabkan paket 1504 byte dikirim yang akan menyebabkan masalah ketika "
|
||
"tiba di antarmuka yang hanya menerima 1500."
|
||
|
||
msgid ""
|
||
"By modifying your configuration setup, you can set up IPv6 when using ``nova-"
|
||
"network`` for networking, and a tested setup is documented for FlatDHCP and "
|
||
"a multi-host configuration. The key is to make ``nova-network`` think a "
|
||
"``radvd`` command ran successfully. The entire configuration is detailed in "
|
||
"a Cybera blog post, `“An IPv6 enabled cloud” <http://www.cybera.ca/news-and-"
|
||
"events/tech-radar/an-ipv6-enabled-cloud/>`_."
|
||
msgstr ""
|
||
"Dengan memodifikasi pengaturan konfigurasi Anda, Anda dapat mengatur IPv6 "
|
||
"saat menggunakan ``nova-network`` untuk jaringan, dan pengaturan yang diuji "
|
||
"didokumentasikan untuk FlatDHCP dan konfigurasi multi-host. Kuncinya adalah "
|
||
"membuat ``nova-network`` berpikir perintah ``radvd`` berhasil dijalankan. "
|
||
"Seluruh konfigurasi dirinci dalam posting blog Cybera, `“An IPv6 enabled "
|
||
"cloud” <http://www.cybera.ca/news-and-events/tech-radar/an-ipv6-enabled-"
|
||
"cloud/>`_."
|
||
|
||
msgid ""
|
||
"By running this command periodically and keeping a record of the result, you "
|
||
"can create a trending report over time that shows whether your ``nova-api`` "
|
||
"usage is increasing, decreasing, or keeping steady."
|
||
msgstr ""
|
||
"Dengan menjalankan perintah ini secara berkala dan menyimpan catatan "
|
||
"hasilnya, Anda dapat membuat laporan trending dari waktu ke waktu yang "
|
||
"menunjukkan apakah penggunaan ``nova-api`` Anda meningkat, menurun, atau "
|
||
"tetap stabil."
|
||
|
||
msgid ""
|
||
"By taking this script and rolling it into an alert for your monitoring "
|
||
"system (such as Nagios), you now have an automated way of ensuring that "
|
||
"image uploads to the Image Catalog are working."
|
||
msgstr ""
|
||
"Dengan mengambil skrip ini dan mengubahnya menjadi peringatan untuk sistem "
|
||
"pemantauan Anda (seperti Nagios), Anda sekarang memiliki cara otomatis untuk "
|
||
"memastikan bahwa unggahan image ke Image Catalog berfungsi."
|
||
|
||
msgid "CERN"
|
||
msgstr "CERN"
|
||
|
||
msgid ""
|
||
"CONF.node_availability_zone has been renamed to CONF."
|
||
"default_availability_zone and is used only by the ``nova-api`` and ``nova-"
|
||
"scheduler`` services."
|
||
msgstr ""
|
||
"CONF.node_available_zone telah diubah namanya menjadi CONF."
|
||
"default_available_zone dan hanya digunakan oleh layanan ``nova-api`` dan "
|
||
"``nova-scheduler``."
|
||
|
||
msgid "CONF.node_availability_zone still works but is deprecated."
|
||
msgstr "CONF.node_avilities_zone masih berfungsi tetapi sudah usang."
|
||
|
||
msgid "Can instances launch and be destroyed?"
|
||
msgstr "Bisakah instance diluncurkan dan dihancurkan?"
|
||
|
||
msgid "Can objects be stored and deleted?"
|
||
msgstr "Bisakah benda disimpan dan dihapus?"
|
||
|
||
msgid "Can users be created?"
|
||
msgstr "Bisakah pengguna dibuat?"
|
||
|
||
msgid "Can volumes be created and destroyed?"
|
||
msgstr "Bisakah volume dibuat dan dimusnahkan?"
|
||
|
||
msgid "Capacity Planning"
|
||
msgstr "Perencanaan Kapasitas"
|
||
|
||
msgid "Capacity planning and scaling"
|
||
msgstr "Perencanaan dan penskalaan kapasitas"
|
||
|
||
msgid "Cells"
|
||
msgstr "Cells"
|
||
|
||
msgid "Cells and regions"
|
||
msgstr "Sel dan daerah"
|
||
|
||
msgid ""
|
||
"Cells and regions, which segregate an entire cloud and result in running "
|
||
"separate Compute deployments."
|
||
msgstr ""
|
||
"Sel dan wilayah, yang memisahkan seluruh cloud dan menghasilkan menjalankan "
|
||
"penyebaran Compute yang terpisah."
|
||
|
||
msgid "Centrally Managing Logs"
|
||
msgstr "Mengelola Log Secara terpusat"
|
||
|
||
msgid ""
|
||
"Certain locations might require local vendors to provide support and "
|
||
"services for each site which may vary with the licensing agreement in place."
|
||
msgstr ""
|
||
"Lokasi tertentu mungkin memerlukan vendor lokal untuk memberikan dukungan "
|
||
"dan layanan untuk setiap situs yang mungkin berbeda dengan perjanjian "
|
||
"lisensi yang berlaku."
|
||
|
||
msgid "Change to the directory where Object Storage is installed:"
|
||
msgstr "Ubah ke direktori tempat Object Storage diinstal:"
|
||
|
||
msgid "Check cloud usage:"
|
||
msgstr "Periksa penggunaan cloud:"
|
||
|
||
msgid "Check for instances in a failed or weird state and investigate why."
|
||
msgstr "Periksa instance dalam keadaan gagal atau aneh dan selidiki mengapa."
|
||
|
||
msgid "Check for operator accounts that should be removed."
|
||
msgstr "Periksa akun operator yang harus dihapus."
|
||
|
||
msgid "Check for security patches and apply them as needed."
|
||
msgstr "Periksa patch keamanan dan terapkan seperlunya."
|
||
|
||
msgid "Check for user accounts that should be removed."
|
||
msgstr "Periksa akun pengguna yang harus dihapus."
|
||
|
||
msgid "Check memory consumption:"
|
||
msgstr "Periksa konsumsi memori:"
|
||
|
||
msgid "Check the port connection using the netcat utility:"
|
||
msgstr "Periksa koneksi port menggunakan utilitas netcat:"
|
||
|
||
msgid "Check the ports for the lost IP address and update the name:"
|
||
msgstr "Periksa port untuk alamat IP yang hilang dan perbarui namanya:"
|
||
|
||
msgid "Check usage and trends over the past month."
|
||
msgstr "Periksa penggunaan dan tren selama sebulan terakhir."
|
||
|
||
msgid "Check your monitoring system for alerts and act on them."
|
||
msgstr ""
|
||
"Periksa sistem pemantauan Anda untuk peringatan dan menindaklanjutinya."
|
||
|
||
msgid "Check your ticket queue for new tickets."
|
||
msgstr "Periksa antrean tiket Anda untuk tiket baru."
|
||
|
||
msgid ""
|
||
"Clean up after an OpenStack upgrade (any unused or new services to be aware "
|
||
"of?)."
|
||
msgstr ""
|
||
"Bersihkan setelah upgrade OpenStack (layanan apa pun yang tidak digunakan "
|
||
"atau baru untuk diperhatikan?)."
|
||
|
||
msgid ""
|
||
"Clean up by clearing all mirrors on ``br-int`` and deleting the dummy "
|
||
"interface:"
|
||
msgstr ""
|
||
"Bersihkan dengan menghapus semua mirror di ``br-int`` dan menghapus "
|
||
"antarmuka dummy:"
|
||
|
||
msgid "Click the :guilabel:`Create Project` button."
|
||
msgstr "Klik tombol :guilabel:`Create Project`."
|
||
|
||
msgid "Cloud (General)"
|
||
msgstr "Cloud (Umum)"
|
||
|
||
msgid "Cloud Controller and Storage Proxy Failures and Maintenance"
|
||
msgstr "Kegagalan Pengontrol Cloud dan Proksi Penyimpanan dan Pemeliharaan"
|
||
|
||
msgid "Cloud controller"
|
||
msgstr "Cloud controller"
|
||
|
||
msgid "Cloud controller receives the renewal request and sends a response."
|
||
msgstr "Pengontrol cloud menerima permintaan pembaruan dan mengirim respons."
|
||
|
||
msgid "Cloud controller receives the second request and sends a new response."
|
||
msgstr ""
|
||
"Pengontrol cloud menerima permintaan kedua dan mengirimkan respons baru."
|
||
|
||
msgid "Cloud security architecture"
|
||
msgstr "Arsitektur keamanan cloud"
|
||
|
||
msgid ""
|
||
"Cloud security architecture should recognize the issues that arise with "
|
||
"security management, which addresses these issues with security controls. "
|
||
"Cloud security controls are put in place to safeguard any weaknesses in the "
|
||
"system, and reduce the effect of an attack."
|
||
msgstr ""
|
||
"Arsitektur keamanan cloud harus mengenali masalah yang muncul dengan "
|
||
"manajemen keamanan, yang mengatasi masalah ini dengan kontrol keamanan. "
|
||
"Kontrol keamanan cloud diterapkan untuk melindungi segala kelemahan dalam "
|
||
"sistem, dan mengurangi efek serangan."
|
||
|
||
msgid ""
|
||
"Cloud-based applications typically request more discrete hardware "
|
||
"(horizontal scaling) as opposed to traditional applications, which require "
|
||
"larger hardware to scale (vertical scaling)."
|
||
msgstr ""
|
||
"Aplikasi berbasis cloud biasanya meminta lebih banyak perangkat keras "
|
||
"diskrit (penskalaan horizontal) sebagai kebalikan dari aplikasi tradisional, "
|
||
"yang membutuhkan perangkat keras yang lebih besar untuk skala (penskalaan "
|
||
"vertikal)."
|
||
|
||
msgid "Command-Line Tools"
|
||
msgstr "Command-Line Tools"
|
||
|
||
msgid "Common areas of regulation include:"
|
||
msgstr "Area regulasi yang umum meliputi:"
|
||
|
||
msgid "Compute"
|
||
msgstr "Compute"
|
||
|
||
msgid "Compute Node Failures and Maintenance"
|
||
msgstr "Compute Node Failures dan Maintenance"
|
||
|
||
msgid "Compute nodes"
|
||
msgstr "Compute nodes"
|
||
|
||
msgid ""
|
||
"Compute nodes can fail the same way a cloud controller can fail. A "
|
||
"motherboard failure or some other type of hardware failure can cause an "
|
||
"entire compute node to go offline. When this happens, all instances running "
|
||
"on that compute node will not be available. Just like with a cloud "
|
||
"controller failure, if your infrastructure monitoring does not detect a "
|
||
"failed compute node, your users will notify you because of their lost "
|
||
"instances."
|
||
msgstr ""
|
||
"Compute Node bisa gagal dengan cara yang sama seperti cloud controller bisa "
|
||
"gagal. Kegagalan motherboard atau beberapa jenis kegagalan perangkat keras "
|
||
"lainnya dapat menyebabkan seluruh compute Nodei offline. Ketika ini terjadi, "
|
||
"semua instance yang berjalan pada compute Node itu tidak akan tersedia. "
|
||
"Seperti halnya kegagalan pengontrol cloud, jika pemantauan infrastruktur "
|
||
"Anda tidak mendeteksi compute Node yang gagal, pengguna Anda akan memberi "
|
||
"tahu Anda karena instans mereka yang hilang."
|
||
|
||
msgid ""
|
||
"Compute nodes have 24 to 48 cores, with at least 4 GB of RAM per core and "
|
||
"approximately 40 GB of ephemeral storage per core."
|
||
msgstr ""
|
||
"Compute nodes memiliki 24 hingga 48 core, dengan setidaknya 4 GB RAM per "
|
||
"core dan sekitar 40 GB penyimpanan sesaat per core."
|
||
|
||
msgid "Compute quota descriptions"
|
||
msgstr "Deskripsi kuota Compute"
|
||
|
||
msgid "Compute service - Edit the configuration file and restart the service."
|
||
msgstr "Layanan Compute - Edit file konfigurasi dan restart layanan."
|
||
|
||
msgid "Compute service, including networking components."
|
||
msgstr "Layanan Compute, termasuk komponen jaringan."
|
||
|
||
msgid "Conclusion"
|
||
msgstr "Kesimpulan"
|
||
|
||
msgid "Configuration Management"
|
||
msgstr "Configuration Management (manajemen konfigurasi)"
|
||
|
||
msgid "Configuration changes to ``nova.conf``."
|
||
msgstr "Konfigurasi berubah menjadi ``nova.conf``."
|
||
|
||
msgid "Connect the qemu-nbd device to the disk."
|
||
msgstr "Hubungkan perangkat qemu-nbd ke disk."
|
||
|
||
msgid "Connect the qemu-nbd device to the disk:"
|
||
msgstr "Hubungkan perangkat qemu-nbd ke disk:"
|
||
|
||
msgid ""
|
||
"Consider adopting structure and options from the service configuration files "
|
||
"and merging them with existing configuration files. The `OpenStack "
|
||
"Configuration Reference <https://docs.openstack.org/ocata/config-reference/"
|
||
">`_ contains new, updated, and deprecated options for most services."
|
||
msgstr ""
|
||
"Pertimbangkan untuk mengadopsi struktur dan opsi dari file konfigurasi "
|
||
"layanan dan menggabungkannya dengan file konfigurasi yang ada. `OpenStack "
|
||
"Configuration Reference <https://docs.openstack.org/ocata/config-reference/"
|
||
">` _ berisi opsi baru, yang diperbarui, dan tidak digunakan lagi untuk "
|
||
"sebagian besar layanan."
|
||
|
||
msgid ""
|
||
"Consider security implications and requirements before designing the "
|
||
"physical and logical network topologies. Make sure that the networks are "
|
||
"properly segregated and traffic flows are going to the correct destinations "
|
||
"without crossing through locations that are undesirable. Consider the "
|
||
"following factors:"
|
||
msgstr ""
|
||
"Pertimbangkan implikasi dan persyaratan keamanan sebelum merancang topologi "
|
||
"jaringan fisik dan logis. Pastikan bahwa jaringan dipisahkan dengan baik dan "
|
||
"arus lalu lintas menuju ke tujuan yang benar tanpa melintasi lokasi yang "
|
||
"tidak diinginkan. Pertimbangkan faktor-faktor berikut:"
|
||
|
||
msgid ""
|
||
"Consider the approach to upgrading your environment. You can perform an "
|
||
"upgrade with operational instances, but this is a dangerous approach. You "
|
||
"might consider using live migration to temporarily relocate instances to "
|
||
"other compute nodes while performing upgrades. However, you must ensure "
|
||
"database consistency throughout the process; otherwise your environment "
|
||
"might become unstable. Also, don't forget to provide sufficient notice to "
|
||
"your users, including giving them plenty of time to perform their own "
|
||
"backups."
|
||
msgstr ""
|
||
"Pertimbangkan pendekatan untuk upgrade lingkungan Anda. Anda dapat melakukan "
|
||
"upgrade dengan instance operasional, tetapi ini adalah pendekatan yang "
|
||
"berbahaya. Anda mungkin mempertimbangkan menggunakan migrasi langsung untuk "
|
||
"memindahkan sementara instance ke node komputasi lain saat melakukan "
|
||
"upgrade. Namun, Anda harus memastikan konsistensi database selama proses "
|
||
"berlangsung; jika tidak, lingkungan Anda mungkin menjadi tidak stabil. Juga, "
|
||
"jangan lupa untuk memberikan pemberitahuan yang cukup kepada pengguna Anda, "
|
||
"termasuk memberi mereka banyak waktu untuk melakukan backup sendiri."
|
||
|
||
msgid "Consider the following example:"
|
||
msgstr "Perhatikan contoh berikut:"
|
||
|
||
msgid "Consider the following security implications and requirements:"
|
||
msgstr "Pertimbangkan implikasi dan persyaratan keamanan berikut:"
|
||
|
||
msgid ""
|
||
"Consider the impact of an upgrade to users. The upgrade process interrupts "
|
||
"management of your environment including the dashboard. If you properly "
|
||
"prepare for the upgrade, existing instances, networking, and storage should "
|
||
"continue to operate. However, instances might experience intermittent "
|
||
"network interruptions."
|
||
msgstr ""
|
||
"Pertimbangkan dampak upgrade ke pengguna. Proses upgrade mengganggu "
|
||
"manajemen lingkungan Anda termasuk dasbor. Jika Anda mempersiapkan upgrade "
|
||
"dengan benar, instance yang ada, jaringan, dan penyimpanan harus terus "
|
||
"beroperasi. Namun, instance mungkin mengalami gangguan jaringan terputus "
|
||
"putus (intermittent)."
|
||
|
||
msgid ""
|
||
"Consider updating your SQL server configuration as described in the "
|
||
"`Installation Tutorials and Guides <https://docs.openstack.org/rocky/install/"
|
||
">`_."
|
||
msgstr ""
|
||
"Pertimbangkan memperbarui konfigurasi server SQL Anda seperti yang "
|
||
"dijelaskan dalam `Installation Tutorials and Guides <https://docs.openstack."
|
||
"org/rocky/install/>`_."
|
||
|
||
msgid ""
|
||
"Consider using a public cloud to test the scalability limits of your cloud "
|
||
"controller configuration. Most public clouds bill by the hour, which means "
|
||
"it can be inexpensive to perform even a test with many nodes."
|
||
msgstr ""
|
||
"Pertimbangkan untuk menggunakan cloud publik untuk menguji batas "
|
||
"skalabilitas konfigurasi pengontrol cloud Anda. Sebagian besar awan publik "
|
||
"menagih per jam, yang berarti tidak mahal untuk melakukan bahkan pengujian "
|
||
"dengan banyak node."
|
||
|
||
msgid ""
|
||
"Considered experimental. A new service, nova-cells. Each cell has a full "
|
||
"nova installation except nova-api."
|
||
msgstr ""
|
||
"Dianggap eksperimental. Layanan baru, nova-cells. Setiap sel memiliki "
|
||
"instalasi nova penuh kecuali nova-api."
|
||
|
||
msgid "Console (boot up messages) for VM instances:"
|
||
msgstr "Console (boot up messages) for VM instances:"
|
||
|
||
msgid "Container quotas"
|
||
msgstr "Kuota kontainer"
|
||
|
||
msgid ""
|
||
"Contains each floating IP address that was added to Compute. This table is "
|
||
"related to the ``fixed_ips`` table by way of the ``floating_ips."
|
||
"fixed_ip_id`` column."
|
||
msgstr ""
|
||
"Berisi setiap alamat IP mengambang (floating IP) yang ditambahkan ke "
|
||
"Compute. Tabel ini terkait dengan tabel ``fix_ips`` melalui kolom "
|
||
"``floating_ips.fixed_ip_id``."
|
||
|
||
msgid ""
|
||
"Contains each possible IP address for the subnet(s) added to Compute. This "
|
||
"table is related to the ``instances`` table by way of the ``fixed_ips."
|
||
"instance_uuid`` column."
|
||
msgstr ""
|
||
"Berisi setiap kemungkinan alamat IP untuk subnet yang ditambahkan ke "
|
||
"Compute. Tabel ini terkait dengan tabel ``instance`` melalui kolom "
|
||
"``fixed_ips.instance_uuid``."
|
||
|
||
msgid "Contents"
|
||
msgstr "Isi"
|
||
|
||
msgid ""
|
||
"Continuing the diagnosis the next morning was kick started by another "
|
||
"identical failure. We quickly got the message queue running again, and tried "
|
||
"to work out why Rabbit was suffering from so much network traffic. Enabling "
|
||
"debug logging on nova-api quickly brought understanding. A ``tail -f /var/"
|
||
"log/nova/nova-api.log`` was scrolling by faster than we'd ever seen before. "
|
||
"CTRL+C on that and we could plainly see the contents of a system log spewing "
|
||
"failures over and over again - a system log from one of our users' instances."
|
||
msgstr ""
|
||
"Melanjutkan diagnosis keesokan paginya tendangan dimulai (kick started) oleh "
|
||
"kegagalan lain yang identik. Kami dengan cepat menjalankan antrean pesan "
|
||
"lagi, dan mencoba mencari tahu mengapa Rabbit menderita begitu banyak lalu "
|
||
"lintas jaringan. Mengaktifkan debug logging di nova-api dengan cepat membawa "
|
||
"pemahaman. ``tail -f /var/log/nova/nova-api.log`` bergulir lebih cepat dari "
|
||
"yang pernah kami lihat sebelumnya. CTRL+C untuk itu dan kita bisa melihat "
|
||
"dengan jelas isi dari kegagalan log sistem yang memuntahkan berulang-ulang - "
|
||
"log sistem dari salah satu instance pengguna kami."
|
||
|
||
msgid ""
|
||
"Copy contents of configuration backup directories that you created during "
|
||
"the upgrade process back to ``/etc/<service>`` directory."
|
||
msgstr ""
|
||
"Salin konten direktori cadangan konfigurasi yang Anda buat selama proses "
|
||
"upgrade kembali ke ``/etc/<service>`` directory."
|
||
|
||
msgid ""
|
||
"Copy the code as shown below into ``ip_whitelist.py``. The following code is "
|
||
"a middleware example that restricts access to a container based on IP "
|
||
"address as explained at the beginning of the section. Middleware passes the "
|
||
"request on to another application. This example uses the swift \"swob\" "
|
||
"library to wrap Web Server Gateway Interface (WSGI) requests and responses "
|
||
"into objects for swift to interact with. When you're done, save and close "
|
||
"the file."
|
||
msgstr ""
|
||
"Salin kode seperti yang ditunjukkan di bawah ini ke ``ip_whitelist.py``. "
|
||
"Kode berikut adalah contoh middleware yang membatasi akses ke sebuah "
|
||
"kontainer berdasarkan alamat IP seperti yang dijelaskan di awal bagian. "
|
||
"Middleware meneruskan permintaan ke aplikasi lain. Contoh ini menggunakan "
|
||
"pustaka \"swob\" swift untuk membungkus permintaan dan respons Web Server "
|
||
"Gateway Interface (WSGI) menjadi objek untuk berinteraksi dengan swift. "
|
||
"Setelah selesai, simpan dan tutup file."
|
||
|
||
msgid "Corrective controls:"
|
||
msgstr "Kontrol korektif:"
|
||
|
||
msgid ""
|
||
"Create a clone of your automated configuration infrastructure with changed "
|
||
"package repository URLs."
|
||
msgstr ""
|
||
"Buat klon dari infrastruktur konfigurasi otomatis Anda dengan URL repositori "
|
||
"paket yang diubah."
|
||
|
||
msgid "Create a container called ``middleware-test``:"
|
||
msgstr "Buat kontainer yang disebut ``middleware-test``:"
|
||
|
||
msgid "Create a port on the ``Public_AGILE`` network:"
|
||
msgstr "Buat port di jaringan `` Public_AGILE``:"
|
||
|
||
msgid "Create a port:"
|
||
msgstr "Membuat port:"
|
||
|
||
msgid "Create an OpenStack Development Environment"
|
||
msgstr "Buat Lingkungan Pengembangan OpenStack"
|
||
|
||
msgid "Create and bring up a dummy interface, ``snooper0``:"
|
||
msgstr "Membuat dan memunculkan antarmuka dummy, ``snooper0``:"
|
||
|
||
msgid "Create context"
|
||
msgstr "Buat konteks"
|
||
|
||
msgid ""
|
||
"Create mirror of ``patch-tun`` to ``snooper0`` (returns UUID of mirror port):"
|
||
msgstr ""
|
||
"Buat mirror dari ``patch-tun`` ke ``snooper0`` (mengembalikan UUID port "
|
||
"mirror):"
|
||
|
||
msgid "Create the ``ip_scheduler.py`` Python source code file:"
|
||
msgstr "Buat file kode sumber Python ``ip_scheduler.py``:"
|
||
|
||
msgid "Create the ``ip_whitelist.py`` Python source code file:"
|
||
msgstr "Buat file kode sumber Python ``ip_whitelist.py``:"
|
||
|
||
msgid "Create ways to automatically test these actions."
|
||
msgstr "Buat cara untuk menguji tindakan ini secara otomatis."
|
||
|
||
msgid "Customization"
|
||
msgstr "Kustomisasi"
|
||
|
||
msgid "Customizing Object Storage (Swift) Middleware"
|
||
msgstr "Menyesuaikan Object Storage (Swift) Middleware"
|
||
|
||
msgid "Customizing the Dashboard (Horizon)"
|
||
msgstr "Menyesuaikan Dasbor (Horizon)"
|
||
|
||
msgid "Customizing the OpenStack Compute (nova) Scheduler"
|
||
msgstr "Menyesuaikan OpenStack Compute (nova) Scheduler"
|
||
|
||
msgid "DAIR"
|
||
msgstr "DAIR"
|
||
|
||
msgid ""
|
||
"DAIR is hosted at two different data centers across Canada: one in Alberta "
|
||
"and the other in Quebec. It consists of a cloud controller at each location, "
|
||
"although, one is designated the \"master\" controller that is in charge of "
|
||
"central authentication and quotas. This is done through custom scripts and "
|
||
"light modifications to OpenStack. DAIR is currently running Havana."
|
||
msgstr ""
|
||
"DAIR di-host di dua pusat data berbeda di Kanada: satu di Alberta dan yang "
|
||
"lainnya di Quebec. Ini terdiri dari pengontrol cloud di setiap lokasi, "
|
||
"meskipun, satu ditunjuk pengontrol \"master\" yang bertanggung jawab atas "
|
||
"otentikasi pusat dan kuota. Ini dilakukan melalui skrip khusus dan "
|
||
"modifikasi ringan ke OpenStack. DAIR saat ini menjalankan Havana."
|
||
|
||
msgid ""
|
||
"DHCP agents running on OpenStack networks run in namespaces similar to the "
|
||
"l3-agents. DHCP namespaces are named ``qdhcp-<uuid>`` and have a TAP device "
|
||
"on the integration bridge. Debugging of DHCP issues usually involves working "
|
||
"inside this network namespace."
|
||
msgstr ""
|
||
"Agen DHCP yang berjalan pada jaringan OpenStack dijalankan dalam namespace "
|
||
"yang mirip dengan agen l3. Namespace DHCP diberi nama ``qdhcp- <uuid> `` "
|
||
"dan memiliki perangkat TAP di jembatan integrasi. Debugging masalah DHCP "
|
||
"biasanya melibatkan bekerja di dalam namespace jaringan ini."
|
||
|
||
msgid ""
|
||
"DHCP traffic uses UDP. The client sends from port 68 to port 67 on the "
|
||
"server. Try to boot a new instance and then systematically listen on the "
|
||
"NICs until you identify the one that isn't seeing the traffic. To use "
|
||
"``tcpdump`` to listen to ports 67 and 68 on br100, you would do:"
|
||
msgstr ""
|
||
"Lalu lintas DHCP menggunakan UDP. Klien mengirim dari port 68 ke port 67 di "
|
||
"server. Cobalah untuk mem-boot instance baru dan kemudian secara sistematis "
|
||
"mendengarkan NIC sampai Anda mengidentifikasi yang tidak melihat lalu "
|
||
"lintas. Untuk menggunakan ``tcpdump`` untuk mendengarkan port 67 dan 68 di "
|
||
"br100, Anda harus:"
|
||
|
||
msgid "DNS service (designate)"
|
||
msgstr "Layanan DNS (ditunjuk)"
|
||
|
||
msgid "Daily"
|
||
msgstr "Harian"
|
||
|
||
msgid ""
|
||
"Dashboard - In typical environments, updating Dashboard only requires "
|
||
"restarting the Apache HTTP service."
|
||
msgstr ""
|
||
"Dasbor - Dalam lingkungan umum, memperbarui Dasbor hanya membutuhkan "
|
||
"restarting layanan HTTP Apache."
|
||
|
||
msgid "Dashboard node"
|
||
msgstr "Dashboard node"
|
||
|
||
msgid ""
|
||
"Data compliance policies governing certain types of information needing to "
|
||
"reside in certain locations due to regulatory issues - and more importantly, "
|
||
"cannot reside in other locations for the same reason."
|
||
msgstr ""
|
||
"Kebijakan kepatuhan data yang mengatur jenis informasi tertentu yang perlu "
|
||
"berada di lokasi tertentu karena masalah peraturan - dan yang lebih penting, "
|
||
"tidak dapat berada di lokasi lain karena alasan yang sama."
|
||
|
||
msgid ""
|
||
"Data location policies ensuring that the services deployed to the cloud are "
|
||
"used according to laws and regulations in place for the employees, foreign "
|
||
"subsidiaries, or third parties."
|
||
msgstr ""
|
||
"Kebijakan lokasi data yang memastikan bahwa layanan yang digunakan untuk "
|
||
"cloud digunakan sesuai dengan hukum dan peraturan yang berlaku untuk "
|
||
"karyawan, anak perusahaan asing, atau pihak ketiga."
|
||
|
||
msgid ""
|
||
"Data ownership policies governing the possession and responsibility for data."
|
||
msgstr ""
|
||
"Kebijakan kepemilikan data yang mengatur kepemilikan dan tanggung jawab atas "
|
||
"data."
|
||
|
||
msgid "Data processing service for OpenStack (sahara)"
|
||
msgstr "Layanan pemrosesan data untuk OpenStack (sahara)"
|
||
|
||
msgid ""
|
||
"Data retention policies ensuring storage of persistent data and records "
|
||
"management to meet data archival requirements."
|
||
msgstr ""
|
||
"Kebijakan penyimpanan data memastikan penyimpanan data yang persisten dan "
|
||
"manajemen catatan untuk memenuhi persyaratan arsip data."
|
||
|
||
msgid "Data security domains"
|
||
msgstr "Domain keamanan data"
|
||
|
||
msgid ""
|
||
"Data sovereignty policies governing the storage of data in foreign countries "
|
||
"or otherwise separate jurisdictions."
|
||
msgstr ""
|
||
"Kebijakan kedaulatan data yang mengatur penyimpanan data di negara asing "
|
||
"atau yurisdiksi terpisah."
|
||
|
||
msgid ""
|
||
"Data storage regulations in Europe are currently driven by provisions of the "
|
||
"`Data protection board <https://edpb.europa.eu/>`_. `Financial Industry "
|
||
"Regulatory Authority <http://finra.complinet.com/>`_ works on this in the "
|
||
"United States."
|
||
msgstr ""
|
||
"Peraturan penyimpanan data di Eropa saat ini didorong oleh ketentuan `Data "
|
||
"protection board <https://edpb.europa.eu/>`_. `Financial Industry Regulatory "
|
||
"Authority <http://finra.complinet.com/>`_ bekerja pada ini di Amerika "
|
||
"Serikat."
|
||
|
||
msgid "Database Backups"
|
||
msgstr "Backup Database"
|
||
|
||
msgid "Database Connectivity"
|
||
msgstr "Konektivitas Basis Data"
|
||
|
||
msgid "Database as a Service (trove)"
|
||
msgstr "Database as a Service (trove)"
|
||
|
||
msgid "Databases"
|
||
msgstr "Databases"
|
||
|
||
msgid "Dealing with Network Namespaces"
|
||
msgstr "Berurusan dengan Network Namespaces"
|
||
|
||
msgid "Debugging DHCP Issues with nova-network"
|
||
msgstr "Debugging Issue DHCP dengan nova-network"
|
||
|
||
msgid "Debugging DNS Issues"
|
||
msgstr "Mendebug DNS Issues"
|
||
|
||
msgid ""
|
||
"Decrease DHCP timeouts by modifying the :file:`/etc/nova/nova.conf` file on "
|
||
"the compute nodes back to the original value for your environment."
|
||
msgstr ""
|
||
"Kurangi waktu tunggu DHCP dengan memodifikasi file :file:`/etc/nova/nova."
|
||
"conf` pada komputasi nodes kembali ke nilai asli untuk lingkungan Anda."
|
||
|
||
msgid ""
|
||
"Dedicate entire disks to certain partitions. For example, you could allocate "
|
||
"disk one and two entirely to the boot, root, and swap partitions under a "
|
||
"RAID 1 mirror. Then, allocate disk three and four entirely to the LVM "
|
||
"partition, also under a RAID 1 mirror. Disk I/O should be better because I/O "
|
||
"is focused on dedicated tasks. However, the LVM partition is much smaller."
|
||
msgstr ""
|
||
"Dedikasikan seluruh disk untuk partisi tertentu. Misalnya, Anda bisa "
|
||
"mengalokasikan disk satu dan dua seluruhnya untuk partisi boot, root, dan "
|
||
"swap di bawah mirror RAID 1. Kemudian, alokasikan disk tiga dan empat "
|
||
"seluruhnya ke partisi LVM, juga di bawah mirror RAID 1. Disk I/O harus lebih "
|
||
"baik karena I/O fokus pada tugas khusus. Namun, partisi LVM jauh lebih kecil."
|
||
|
||
msgid ""
|
||
"Default CPU overcommit ratio (``cpu_allocation_ratio`` in the ``nova.conf`` "
|
||
"file) of 16:1."
|
||
msgstr ""
|
||
"Rasio overcommit CPU default (``cpu_allocation_ratio`` dalam file ``nova."
|
||
"conf``) dari 16: 1."
|
||
|
||
msgid "Default drop rule for unmatched traffic."
|
||
msgstr "Aturan penurunan default untuk lalu lintas yang tidak cocok."
|
||
|
||
msgid ""
|
||
"Delete the instance and create a new instance using the ``--nic port-id`` "
|
||
"option."
|
||
msgstr ""
|
||
"Hapus instance dan buat instance baru menggunakan opsi ``--nic port-id``."
|
||
|
||
msgid "Delete the ports that are not needed:"
|
||
msgstr "Hapus port yang tidak diperlukan:"
|
||
|
||
msgid ""
|
||
"Depending on the type of server, the contents and order of your package list "
|
||
"might vary from this example."
|
||
msgstr ""
|
||
"Bergantung pada jenis server, isi dan urutan daftar paket Anda mungkin "
|
||
"berbeda dari contoh ini."
|
||
|
||
msgid ""
|
||
"Depending on your specific configuration, upgrading all packages might "
|
||
"restart or break services supplemental to your OpenStack environment. For "
|
||
"example, if you use the TGT iSCSI framework for Block Storage volumes and "
|
||
"the upgrade includes new packages for it, the package manager might restart "
|
||
"the TGT iSCSI services and impact connectivity to volumes."
|
||
msgstr ""
|
||
"Bergantung pada konfigurasi spesifik Anda, upgrading semua paket mungkin "
|
||
"restart atau merusak (break) layanan tambahan ke lingkungan OpenStack Anda. "
|
||
"Misalnya, jika Anda menggunakan framework TGT iSCSI untuk volume Block "
|
||
"Storage dan upgrade termasuk paket-paket baru untuk itu, manajer paket "
|
||
"mungkin restart layanan TGT iSCSI dan berdampak konektivitas ke volume."
|
||
|
||
msgid "Deployment"
|
||
msgstr "Deployment"
|
||
|
||
msgid "Deprecation of Nova Network"
|
||
msgstr "Penghentian Nova Network"
|
||
|
||
msgid "Description"
|
||
msgstr "Deskripsi"
|
||
|
||
msgid ""
|
||
"Designate a server as the central logging server. The best practice is to "
|
||
"choose a server that is solely dedicated to this purpose. Create a file "
|
||
"called ``/etc/rsyslog.d/server.conf`` with the following contents:"
|
||
msgstr ""
|
||
"Tentukan server sebagai server logging pusat. Praktik terbaik adalah memilih "
|
||
"server yang semata-mata didedikasikan untuk tujuan ini. Buat file bernama "
|
||
"``/etc/rsyslog.d/server.conf`` dengan konten berikut:"
|
||
|
||
msgid "Detective controls:"
|
||
msgstr "Kontrol detektif:"
|
||
|
||
msgid ""
|
||
"Determine which OpenStack packages are installed on your system. Use the :"
|
||
"command:`dpkg --get-selections` command. Filter for OpenStack packages, "
|
||
"filter again to omit packages explicitly marked in the ``deinstall`` state, "
|
||
"and save the final output to a file. For example, the following command "
|
||
"covers a controller node with keystone, glance, nova, neutron, and cinder:"
|
||
msgstr ""
|
||
"Tentukan paket OpenStack mana yang diinstal pada sistem Anda. Gunakan "
|
||
"perintah :command:`dpkg --get-selections`. Saring untuk paket OpenStack, "
|
||
"saring lagi untuk menghilangkan paket yang secara eksplisit ditandai dalam "
|
||
"keadaan ``deinstall``, dan simpan hasil akhir ke file. Misalnya, perintah "
|
||
"berikut ini mencakup node pengontrol dengan keystone, glance, nova, neutron, "
|
||
"dan cinder:"
|
||
|
||
msgid "Determine which servers the RabbitMQ alarms are coming from."
|
||
msgstr "Tentukan dari server mana alarm RabbitMQ berasal."
|
||
|
||
msgid "Determining Which Component Is Broken"
|
||
msgstr "Menentukan Komponen Yang Rusak"
|
||
|
||
msgid "Determining cloud scalability"
|
||
msgstr "Menentukan skalabilitas cloud"
|
||
|
||
msgid ""
|
||
"Determining the scalability of your cloud and how to improve it requires "
|
||
"balancing many variables. No one solution meets everyone's scalability "
|
||
"goals. However, it is helpful to track a number of metrics. You can define "
|
||
"virtual hardware templates called \"flavors\" in OpenStack, which will "
|
||
"impact your cloud scaling decisions. These templates define sizes for memory "
|
||
"in RAM, root disk size, amount of ephemeral data disk space available, and "
|
||
"the number of CPU cores."
|
||
msgstr ""
|
||
"Menentukan skalabilitas cloud Anda dan cara memperbaikinya memerlukan "
|
||
"penyeimbangan banyak variabel. Tidak ada solusi yang memenuhi sasaran "
|
||
"skalabilitas semua orang. Namun, melacak sejumlah metrik bermanfaat. Anda "
|
||
"dapat mendefinisikan template perangkat keras virtual yang disebut \"flavors"
|
||
"\" di OpenStack, yang akan memengaruhi keputusan penskalaan cloud Anda. "
|
||
"Template ini menentukan ukuran untuk memori dalam RAM, ukuran disket root, "
|
||
"jumlah ruang disk data sementara yang tersedia, dan jumlah core CPU."
|
||
|
||
msgid "Deterrent controls:"
|
||
msgstr "Kontrol pencegah (deterrent):"
|
||
|
||
msgid ""
|
||
"Develop an upgrade procedure and assess it thoroughly by using a test "
|
||
"environment similar to your production environment."
|
||
msgstr ""
|
||
"Kembangkan prosedur upgrade dan nilai secara menyeluruh dengan menggunakan "
|
||
"lingkungan pengujian yang serupa dengan lingkungan produksi Anda."
|
||
|
||
msgid "Diagnose Your Compute Nodes"
|
||
msgstr "Diagnosis Node Komputasi Anda"
|
||
|
||
msgid "Differences Between Various Drivers"
|
||
msgstr "Perbedaan Antara Berbagai Driver"
|
||
|
||
msgid ""
|
||
"Differentiations between \"hot\" (active) and \"cold\" (inactive) sites, "
|
||
"where significant savings may be made in situations where one site is a cold "
|
||
"standby for disaster recovery purposes only."
|
||
msgstr ""
|
||
"Perbedaan antara situs \"hot\" (active) dan \"cold\" (inactive), di mana "
|
||
"penghematan yang signifikan dapat dilakukan dalam situasi di mana satu situs "
|
||
"siaga cold untuk tujuan pemulihan bencana saja."
|
||
|
||
msgid "Direct incoming traffic from VM to the security group chain."
|
||
msgstr "Lalu lintas masuk langsung dari VM ke rantai grup keamanan."
|
||
|
||
msgid "Direct packets associated with a known session to the RETURN chain."
|
||
msgstr ""
|
||
"Paket langsung yang terkait dengan sesi yang diketahui ke rantai RETURN."
|
||
|
||
msgid "Direct traffic from the VM interface to the security group chain."
|
||
msgstr "Lalu lintas langsung dari antarmuka VM ke rantai grup keamanan."
|
||
|
||
msgid ""
|
||
"Disable scheduling of new VMs to the node, optionally providing a reason "
|
||
"comment:"
|
||
msgstr ""
|
||
"Nonaktifkan penjadwalan VM baru ke node, opsional memberikan komentar alasan:"
|
||
|
||
msgid "Disappearing Images"
|
||
msgstr "Gambar yang hilang"
|
||
|
||
msgid ""
|
||
"Disaster recovery policies ensuring regular data backups and relocation of "
|
||
"cloud applications to another supplier in scenarios where a provider may go "
|
||
"out of business, or their data center could become inoperable."
|
||
msgstr ""
|
||
"Kebijakan pemulihan bencana memastikan pencadangan data berkala dan relokasi "
|
||
"aplikasi cloud ke pemasok lain dalam skenario di mana penyedia mungkin "
|
||
"keluar dari bisnis, atau pusat data mereka bisa menjadi tidak dapat "
|
||
"dioperasikan."
|
||
|
||
msgid "Disconnect the qemu-nbd device."
|
||
msgstr "Putuskan sambungan perangkat qemu-nbd."
|
||
|
||
msgid ""
|
||
"Discrete regions with separate API endpoints and no coordination between "
|
||
"regions."
|
||
msgstr ""
|
||
"Wilayah diskrit dengan endpoint API terpisah dan tidak ada koordinasi antar "
|
||
"wilayah."
|
||
|
||
msgid "Disk"
|
||
msgstr "Disk"
|
||
|
||
msgid "Disk partitioning and RAID"
|
||
msgstr "Partisi disk dan RAID"
|
||
|
||
msgid "Disk partitioning and disk array setup for scalability"
|
||
msgstr "Partisi disk dan pengaturan array disk untuk skalabilitas"
|
||
|
||
msgid "Disk space"
|
||
msgstr "Ruang disk"
|
||
|
||
msgid "Disk space is cheap these days. Data recovery is not."
|
||
msgstr "Ruang disk bisa murah hari ini. Pemulihan data akan tidak."
|
||
|
||
msgid "Disk usage"
|
||
msgstr "Disk usage"
|
||
|
||
msgid "Distributed Virtual Router"
|
||
msgstr "Distributed Virtual Router (router virtual terdistribusi)"
|
||
|
||
msgid ""
|
||
"Do a full manual install by using the `Installation Tutorials and Guides "
|
||
"<https://docs.openstack.org/rocky/install/>`_ for your platform. Review the "
|
||
"final configuration files and installed packages."
|
||
msgstr ""
|
||
"Lakukan instalasi manual lengkap dengan menggunakan `Installation Tutorials "
|
||
"and Guides <https://docs.openstack.org/rocky/install/>` _ untuk platform "
|
||
"Anda. Tinjau file konfigurasi akhir dan paket yang diinstal."
|
||
|
||
msgid "Double VLAN"
|
||
msgstr "VLAN ganda"
|
||
|
||
msgid "Down the Rabbit Hole"
|
||
msgstr "Down the Rabbit Hole (masuk kedalam lubang kelinci)"
|
||
|
||
msgid "Downgrade OpenStack packages."
|
||
msgstr "Downgrade paket OpenStack."
|
||
|
||
msgid ""
|
||
"Downgrading packages is by far the most complicated step; it is highly "
|
||
"dependent on the distribution and the overall administration of the system."
|
||
msgstr ""
|
||
"Paket penurunan versi sejauh ini merupakan langkah paling rumit; sangat "
|
||
"tergantung pada distribusi dan administrasi keseluruhan sistem."
|
||
|
||
msgid ""
|
||
"Downtime, whether planned or unscheduled, is a certainty when running a "
|
||
"cloud. This chapter aims to provide useful information for dealing "
|
||
"proactively, or reactively, with these occurrences."
|
||
msgstr ""
|
||
"Waktu henti, baik yang direncanakan atau tidak, adalah kepastian saat "
|
||
"menjalankan cloud. Bab ini bertujuan untuk memberikan informasi yang berguna "
|
||
"untuk menangani kejadian ini secara proaktif, atau reaktif."
|
||
|
||
msgid "Driver Quality Improvements"
|
||
msgstr "Peningkatan Kualitas Driver"
|
||
|
||
msgid "Drop packets that are not associated with a state."
|
||
msgstr "Turunkan paket yang tidak terkait dengan keadaan."
|
||
|
||
msgid "Drop traffic without an IP/MAC allow rule."
|
||
msgstr "Turunkan traffic tanpa aturan IP/MAC."
|
||
|
||
msgid ""
|
||
"During an upgrade, operators can add configuration options to ``nova.conf`` "
|
||
"which lock the version of RPC messages and allow live upgrading of the "
|
||
"services without interruption caused by version mismatch. The configuration "
|
||
"options allow the specification of RPC version numbers if desired, but "
|
||
"release name alias are also supported. For example:"
|
||
msgstr ""
|
||
"Selama upgrade, operator dapat menambahkan opsi konfigurasi ke ``nova.conf`` "
|
||
"yang mengunci versi pesan RPC dan memungkinkan upgrade langsung layanan "
|
||
"tanpa gangguan yang disebabkan oleh ketidakcocokan versi. Opsi konfigurasi "
|
||
"memungkinkan spesifikasi nomor versi RPC jika diinginkan, tetapi nama alias "
|
||
"rilis juga didukung. Sebagai contoh:"
|
||
|
||
msgid ""
|
||
"EC2 compatibility credentials can be downloaded by selecting :guilabel:"
|
||
"`Project`, then :guilabel:`Compute`, then :guilabel:`Access & Security`, "
|
||
"then :guilabel:`API Access` to display the :guilabel:`Download EC2 "
|
||
"Credentials` button. Click the button to generate a ZIP file with server "
|
||
"x509 certificates and a shell script fragment. Create a new directory in a "
|
||
"secure location because these are live credentials containing all the "
|
||
"authentication information required to access your cloud identity, unlike "
|
||
"the default ``user-openrc``. Extract the ZIP file here. You should have "
|
||
"``cacert.pem``, ``cert.pem``, ``ec2rc.sh``, and ``pk.pem``. The ``ec2rc.sh`` "
|
||
"is similar to this:"
|
||
msgstr ""
|
||
"Kredensial kompatibilitas EC2 dapat diunduh dengan memilih :guilabel:"
|
||
"`Project`, lalu :guilabel:`Compute`, lalu :guilabel:`Access & Security`, "
|
||
"lalu :guilabel:`API Access` untuk menampilkan tombol :guilabel:`Download EC2 "
|
||
"Credentials`. Klik tombol untuk membuat file ZIP dengan sertifikat server "
|
||
"x509 dan fragmen skrip shell. Buat direktori baru di lokasi yang aman karena "
|
||
"ini adalah kredensial langsung yang berisi semua informasi otentikasi yang "
|
||
"diperlukan untuk mengakses identitas cloud Anda, tidak seperti ``user-"
|
||
"openrc`` default. Ekstrak file ZIP di sini. Anda harus memiliki ``cacert."
|
||
"pem``, ``cert.pem``, ``ec2rc.sh``, dan ``pk.pem``. ``Ec2rc.sh`` mirip dengan "
|
||
"ini:"
|
||
|
||
msgid ""
|
||
"Each OpenStack cloud is different even if you have a near-identical "
|
||
"architecture as described in this guide. As a result, you must still test "
|
||
"upgrades between versions in your environment using an approximate clone of "
|
||
"your environment."
|
||
msgstr ""
|
||
"Setiap cloud OpenStack berbeda bahkan jika Anda memiliki arsitektur yang "
|
||
"hampir sama seperti yang dijelaskan dalam panduan ini. Akibatnya, Anda masih "
|
||
"harus menguji upgrade antar versi di lingkungan Anda menggunakan klon "
|
||
"perkiraan lingkungan Anda."
|
||
|
||
msgid ""
|
||
"Each cloud implements services differently. Understand the security "
|
||
"requirements of every cloud that handles the organization's data or "
|
||
"workloads."
|
||
msgstr ""
|
||
"Setiap cloud mengimplementasikan layanan secara berbeda. Memahami "
|
||
"persyaratan keamanan setiap cloud yang menangani data atau beban kerja "
|
||
"organisasi."
|
||
|
||
msgid ""
|
||
"Each layer scales horizontally. As the number of logs grows you can add more "
|
||
"log pushers, more Logstash indexers, and more ElasticSearch nodes."
|
||
msgstr ""
|
||
"Setiap lapisan bersisik secara horizontal. Saat jumlah log bertambah, Anda "
|
||
"dapat menambahkan lebih banyak push log, lebih banyak pengindeks log, dan "
|
||
"lebih banyak node ElasticSearch."
|
||
|
||
msgid ""
|
||
"Each method provides different functionality and can be best divided into "
|
||
"two groups:"
|
||
msgstr ""
|
||
"Setiap metode menyediakan fungsionalitas yang berbeda dan dapat dibagi "
|
||
"menjadi dua kelompok:"
|
||
|
||
msgid ""
|
||
"Each site runs a different configuration, as a resource cells in an "
|
||
"OpenStack Compute cells setup. Some sites span multiple data centers, some "
|
||
"use off compute node storage with a shared file system, and some use on "
|
||
"compute node storage with a non-shared file system. Each site deploys the "
|
||
"Image service with an Object Storage back end. A central Identity, "
|
||
"dashboard, and Compute API service are used. A login to the dashboard "
|
||
"triggers a SAML login with Shibboleth, which creates an account in the "
|
||
"Identity service with an SQL back end. An Object Storage Global Cluster is "
|
||
"used across several sites."
|
||
msgstr ""
|
||
"Setiap situs menjalankan konfigurasi yang berbeda, sebagai sel sumber daya "
|
||
"dalam pengaturan sel OpenStack Compute. Beberapa situs menjangkau beberapa "
|
||
"pusat data, beberapa menggunakan penyimpanan node komputasi dengan sistem "
|
||
"file bersama, dan beberapa digunakan pada penyimpanan node komputasi dengan "
|
||
"sistem file yang tidak digunakan bersama. Setiap situs menyebarkan layanan "
|
||
"Image dengan back end Object Storage. Layanan Identity pokok, dashboard, dan "
|
||
"Compute API digunakan. Login ke dasbor memicu login SAML dengan Shibboleth, "
|
||
"yang membuat akun di layanan Identity dengan SQL back end. Object Storage "
|
||
"Global Cluster digunakan di beberapa situs."
|
||
|
||
msgid ""
|
||
"Early indications are that it does do this well for a base set of scenarios, "
|
||
"such as using the ML2 plug-in with Open vSwitch, one flat external network "
|
||
"and VXLAN tenant networks. However, it does appear that there are problems "
|
||
"with the use of VLANs, IPv6, Floating IPs, high north-south traffic "
|
||
"scenarios and large numbers of compute nodes. It is expected these will "
|
||
"improve significantly with the next release, but bug reports on specific "
|
||
"issues are highly desirable."
|
||
msgstr ""
|
||
"Indikasi awal adalah bahwa ia melakukan ini dengan baik untuk serangkaian "
|
||
"skenario dasar, seperti menggunakan plug-in ML2 dengan Open vSwitch, satu "
|
||
"jaringan eksternal datar dan jaringan penyewa VXLAN. Namun, tampaknya ada "
|
||
"masalah dengan penggunaan VLAN, IPv6, Floating IPs, skenario lalu lintas "
|
||
"north-south yang tinggi dan sejumlah besar node komputasi. Diharapkan ini "
|
||
"akan meningkat secara signifikan dengan rilis berikutnya, tetapi laporan bug "
|
||
"tentang masalah spesifik sangat diinginkan."
|
||
|
||
msgid "Easier Upgrades"
|
||
msgstr "Upgrade yang Lebih Mudah"
|
||
|
||
msgid ""
|
||
"Edit the ``/etc/rabbitmq/rabbitmq.config`` configuration file, and change "
|
||
"the ``collect_statistics_interval`` parameter between 30000-60000 "
|
||
"milliseconds. Alternatively you can turn off statistics collection by "
|
||
"setting ``collect_statistics`` parameter to \"none\"."
|
||
msgstr ""
|
||
"Edit file konfigurasi ``/etc/rabbitmq/rabbitmq.config``, dan ubah parameter "
|
||
"``collect_statistics_interval`` antara 30000-60000 milidetik. Atau Anda "
|
||
"dapat mematikan pengumpulan statistik dengan mengatur parameter "
|
||
"``collect_statistics`` menjadi \"none\"."
|
||
|
||
msgid ""
|
||
"Either approach is valid. Use the approach that matches your experience."
|
||
msgstr ""
|
||
"Semua pendekatan ini valid. Gunakan pendekatan yang sesuai dengan pengalaman "
|
||
"Anda."
|
||
|
||
msgid "ElasticSearch"
|
||
msgstr "ElasticSearch"
|
||
|
||
msgid ""
|
||
"Emma Richards of Rackspace Guest Relations took excellent care of our lunch "
|
||
"orders and even set aside a pile of sticky notes that had fallen off the "
|
||
"walls."
|
||
msgstr ""
|
||
"Emma Richards dari Rackspace Guest Relations merawat pesanan makan siang "
|
||
"kami dengan sangat baik dan bahkan menyisihkan setumpuk catatan tempel yang "
|
||
"jatuh dari dinding."
|
||
|
||
msgid "Enable scheduling of VMs to the node:"
|
||
msgstr "Aktifkan penjadwalan VM ke node:"
|
||
|
||
msgid "Enabling IPv6 Support"
|
||
msgstr "Mengaktifkan Dukungan IPv6"
|
||
|
||
msgid "Encode certificate in DER format"
|
||
msgstr "Encode sertifikat dalam format DER"
|
||
|
||
msgid ""
|
||
"Ensure that cryptsetup is installed, and ensure that ``pythin-"
|
||
"barbicanclient`` Python package is installed"
|
||
msgstr ""
|
||
"Pastikan cryptsetup diinstal, dan pastikan bahwa ``pythin-barbicanclient`` "
|
||
"Python package diinstal"
|
||
|
||
msgid "Ensure that the operating system has recognized the new disk:"
|
||
msgstr "Pastikan sistem operasi telah mengenali disk baru:"
|
||
|
||
msgid "Ephemeral"
|
||
msgstr "Ephemeral"
|
||
|
||
msgid ""
|
||
"Even at smaller-scale testing, look for excess network packets to determine "
|
||
"whether something is going horribly wrong in inter-component communication."
|
||
msgstr ""
|
||
"Bahkan pada pengujian skala kecil, cari paket jaringan berlebih untuk "
|
||
"menentukan apakah ada sesuatu yang salah dalam komunikasi antar-komponen."
|
||
|
||
msgid ""
|
||
"Ever have one of those days where all of the sudden you get the Google "
|
||
"results you were looking for? Well, that's what happened here. I was looking "
|
||
"for information on dhclient and why it dies when it can't renew its lease "
|
||
"and all of the sudden I found a bunch of OpenStack and dnsmasq discussions "
|
||
"that were identical to the problem we were seeing!"
|
||
msgstr ""
|
||
"Pernahkah mengalami salah satu dari hari-hari itu di mana tiba-tiba Anda "
|
||
"mendapatkan hasil Google yang Anda cari? Nah, itulah yang terjadi di sini. "
|
||
"Saya mencari informasi tentang dhclient dan mengapa ia mati ketika ia tidak "
|
||
"dapat memperpanjang sewa dan tiba-tiba saya menemukan banyak diskusi "
|
||
"OpenStack dan dnsmasq yang identik dengan masalah yang kami lihat!"
|
||
|
||
msgid "Excessive database management memory consumption"
|
||
msgstr "Konsumsi memori manajemen database yang berlebihan"
|
||
|
||
msgid "Factors affecting OpenStack deployment"
|
||
msgstr "Faktor-faktor yang mempengaruhi pengerahan OpenStack"
|
||
|
||
msgid ""
|
||
"Failures of hardware are common in large-scale deployments such as an "
|
||
"infrastructure cloud. Consider your processes and balance time saving "
|
||
"against availability. For example, an Object Storage cluster can easily live "
|
||
"with dead disks in it for some period of time if it has sufficient capacity. "
|
||
"Or, if your compute installation is not full, you could consider live "
|
||
"migrating instances off a host with a RAM failure until you have time to "
|
||
"deal with the problem."
|
||
msgstr ""
|
||
"Kegagalan perangkat keras umum terjadi dalam penyebaran berskala besar "
|
||
"seperti cloud infrastruktur. Pertimbangkan proses Anda dan seimbangkan "
|
||
"penghematan waktu dengan ketersediaan. Sebagai contoh, sebuah cluster Object "
|
||
"Storage dapat dengan mudah hidup dengan disk mati di dalamnya untuk beberapa "
|
||
"periode waktu jika memiliki kapasitas yang cukup. Atau, jika instalasi "
|
||
"komputasi Anda tidak penuh, Anda dapat mempertimbangkan memigrasi instance "
|
||
"langsung dari host dengan kegagalan RAM hingga Anda punya waktu untuk "
|
||
"mengatasi masalah tersebut."
|
||
|
||
msgid "Family Educational Rights and Privacy Act (FERPA)"
|
||
msgstr "Family Educational Rights and Privacy Act (FERPA)"
|
||
|
||
msgid ""
|
||
"Feature requests typically start their life in Etherpad, a collaborative "
|
||
"editing tool, which is used to take coordinating notes at a design summit "
|
||
"session specific to the feature. This then leads to the creation of a "
|
||
"blueprint on the Launchpad site for the particular project, which is used to "
|
||
"describe the feature more formally. Blueprints are then approved by project "
|
||
"team members, and development can begin."
|
||
msgstr ""
|
||
"Permintaan fitur biasanya memulai kehidupannya di Etherpad, alat pengeditan "
|
||
"kolaboratif, yang digunakan untuk membuat catatan koordinasi pada sesi "
|
||
"puncak desain khusus untuk fitur tersebut. Ini kemudian mengarah pada "
|
||
"pembuatan cetak biru di situs Launchpad untuk proyek tertentu, yang "
|
||
"digunakan untuk menggambarkan fitur lebih formal. Cetak biru kemudian "
|
||
"disetujui oleh anggota tim proyek, dan pengembangan dapat dimulai."
|
||
|
||
msgid ""
|
||
"Felix Lee of Academia Sinica Grid Computing Centre in Taiwan contributed "
|
||
"this story."
|
||
msgstr ""
|
||
"Felix Lee dari Academia Sinica Grid Computing Center di Taiwan menyumbangkan "
|
||
"cerita ini."
|
||
|
||
msgid "Figure. Neutron network paths"
|
||
msgstr "Figur. Jalur jaringan neutron"
|
||
|
||
msgid "Figure. Traffic route for ping packet"
|
||
msgstr "Angka. Rute lalu lintas untuk paket ping"
|
||
|
||
msgid "File System Backups"
|
||
msgstr "Cadangan Sistem File"
|
||
|
||
msgid "File descriptor limits when scaling a cloud environment"
|
||
msgstr "Batas deskriptor file saat menskala lingkungan cloud"
|
||
|
||
msgid ""
|
||
"File system to store files and directories, where all the data lives, "
|
||
"including the root partition that starts and runs the system."
|
||
msgstr ""
|
||
"Sistem file untuk menyimpan file dan direktori, tempat semua data hidup, "
|
||
"termasuk partisi root yang memulai dan menjalankan sistem."
|
||
|
||
msgid "Final steps"
|
||
msgstr "Langkah terakhir"
|
||
|
||
msgid ""
|
||
"Finally, Alvaro noticed something. When a packet from the outside hits the "
|
||
"cloud controller, it should not be configured with a VLAN. We verified this "
|
||
"as true. When the packet went from the cloud controller to the compute node, "
|
||
"it should only have a VLAN if it was destined for an instance. This was "
|
||
"still true. When the ping reply was sent from the instance, it should be in "
|
||
"a VLAN. True. When it came back to the cloud controller and on its way out "
|
||
"to the Internet, it should no longer have a VLAN. False. Uh oh. It looked as "
|
||
"though the VLAN part of the packet was not being removed."
|
||
msgstr ""
|
||
"Akhirnya, Alvaro memperhatikan sesuatu. Ketika sebuah paket dari luar "
|
||
"mengenai pengendali cloud, itu tidak harus dikonfigurasikan dengan VLAN. "
|
||
"Kami memverifikasi ini sebagai benar. Ketika paket pergi dari cloud "
|
||
"controller ke compute node, seharusnya hanya memiliki VLAN jika ditakdirkan "
|
||
"untuk instance. Ini masih benar. Ketika balasan ping dikirim dari instance, "
|
||
"itu harus dalam VLAN. Benar. Ketika kembali ke pengontrol cloud dan dalam "
|
||
"perjalanan keluar ke Internet, seharusnya tidak lagi memiliki VLAN. Salah. "
|
||
"Uh oh. Tampaknya bagian VLAN dari paket itu tidak dihapus."
|
||
|
||
msgid ""
|
||
"Finally, I checked StackTach and reviewed the user's events. They had "
|
||
"created and deleted several snapshots—most likely experimenting. Although "
|
||
"the timestamps didn't match up, my conclusion was that they launched their "
|
||
"instance and then deleted the snapshot and it was somehow removed from ``/"
|
||
"var/lib/nova/instances/_base``. None of that made sense, but it was the best "
|
||
"I could come up with."
|
||
msgstr ""
|
||
"Akhirnya, saya memeriksa StackTach dan meninjau acara pengguna. Mereka telah "
|
||
"membuat dan menghapus beberapa foto — kemungkinan besar bereksperimen. "
|
||
"Meskipun timestamp tidak cocok, kesimpulan saya adalah bahwa mereka "
|
||
"meluncurkan instance mereka dan kemudian menghapus snapshot dan entah "
|
||
"bagaimana dihapus dari ``/var/lib/nova/instances/_base``. Tidak ada yang "
|
||
"masuk akal, tapi itu yang terbaik yang bisa saya lakukan."
|
||
|
||
msgid "Finally, mount the disk:"
|
||
msgstr "Akhirnya, pasang disk:"
|
||
|
||
msgid ""
|
||
"Finally, reattach volumes using the same method described in the section :"
|
||
"ref:`volumes`."
|
||
msgstr ""
|
||
"Terakhir, pasang kembali volume menggunakan metode yang sama seperti yang "
|
||
"dijelaskan di bagian :ref:`volume`."
|
||
|
||
msgid ""
|
||
"Find the ID for each instance by listing the server IDs using the following "
|
||
"command:"
|
||
msgstr ""
|
||
"Temukan ID untuk setiap instance dengan mendaftar ID server menggunakan "
|
||
"perintah berikut:"
|
||
|
||
msgid ""
|
||
"Find the ``[filter:ratelimit]`` section in ``/etc/swift/proxy-server.conf``, "
|
||
"and copy in the following configuration section after it:"
|
||
msgstr ""
|
||
"Temukan bagian ``[filter: ratelimit] `` di ``/etc/swift/proxy-server.conf``, "
|
||
"dan salin di bagian konfigurasi berikut setelahnya:"
|
||
|
||
msgid ""
|
||
"Find the ``[pipeline:main]`` section in ``/etc/swift/proxy-server.conf``, "
|
||
"and add ``ip_whitelist`` after ratelimit to the list like so. When you're "
|
||
"done, save and close the file:"
|
||
msgstr ""
|
||
"Temukan bagian ``[pipeline: main] `` di ``/etc/swift/proxy-server.conf``, "
|
||
"dan tambahkan ``ip_whitelist`` setelah ratelimit ke daftar seperti itu. "
|
||
"Setelah selesai, simpan dan tutup file:"
|
||
|
||
msgid ""
|
||
"Find the ``provider:segmentation_id`` of the network you're interested in. "
|
||
"This is the same field used for the VLAN ID in VLAN-based networks:"
|
||
msgstr ""
|
||
"Temukan ``provider: segmentation_id`` dari jaringan yang Anda minati. Ini "
|
||
"adalah bidang yang sama dengan yang digunakan untuk ID VLAN di jaringan "
|
||
"berbasis VLAN:"
|
||
|
||
msgid "Find the ``scheduler_driver`` config and change it like so:"
|
||
msgstr "Temukan konfigurasi ``scheduler_driver`` dan ubah seperti ini:"
|
||
|
||
msgid ""
|
||
"Find the external VLAN tag of the network you're interested in. This is the "
|
||
"``provider:segmentation_id`` as returned by the networking service:"
|
||
msgstr ""
|
||
"Temukan tag VLAN eksternal dari jaringan yang Anda minati. Ini adalah "
|
||
"``provider:segmentation_id`` yang dikembalikan oleh layanan jaringan:"
|
||
|
||
msgid "Find the port corresponding to the instance. For example:"
|
||
msgstr "Temukan port yang sesuai dengan instance. Sebagai contoh:"
|
||
|
||
msgid "Finding a Failure in the Path"
|
||
msgstr "Menemukan Kegagalan di Path"
|
||
|
||
msgid "Firewalls"
|
||
msgstr "Firewalls"
|
||
|
||
msgid "First, find the UUID of the instance in question:"
|
||
msgstr "Pertama, temukan UUID dari instance yang dimaksud:"
|
||
|
||
msgid "First, unmount the disk:"
|
||
msgstr "Pertama, lepaskan disk:"
|
||
|
||
msgid ""
|
||
"First, you can discover what servers belong to your OpenStack cloud by "
|
||
"running:"
|
||
msgstr ""
|
||
"Pertama, Anda dapat menemukan server apa yang menjadi milik OpenStack cloud "
|
||
"Anda dengan menjalankan:"
|
||
|
||
msgid "Fixed IPs"
|
||
msgstr "IP tetap"
|
||
|
||
msgid "Floating IPs"
|
||
msgstr "IP mengambang"
|
||
|
||
msgid "For Object Storage, each region has a swift environment."
|
||
msgstr "Untuk Object Storage, setiap wilayah memiliki lingkungan yang cepat."
|
||
|
||
msgid ""
|
||
"For a discussion of metric tracking, including how to extract metrics from "
|
||
"your cloud, see the `OpenStack Operations Guide <https://docs.openstack.org/"
|
||
"operations-guide/ops-logging-monitoring.html>`_."
|
||
msgstr ""
|
||
"Untuk diskusi tentang pelacakan metrik, termasuk cara mengekstrak metrik "
|
||
"dari cloud Anda, lihat `OpenStack Operations Guide <https://docs.openstack."
|
||
"org/operations-guide/ops-logging-monitoring.html>`_."
|
||
|
||
msgid ""
|
||
"For compute nodes, ``nova-scheduler`` will manage differences in sizing with "
|
||
"core count and RAM. However, you should consider that the user experience "
|
||
"changes with differing CPU speeds. When adding object storage nodes, a :term:"
|
||
"`weight` should be specified that reflects the :term:`capability` of the "
|
||
"node."
|
||
msgstr ""
|
||
"Untuk komputasi node, ``nova-scheduler`` akan mengatur perbedaan ukuran "
|
||
"dengan core count dan RAM. Namun, Anda harus mempertimbangkan bahwa "
|
||
"pengalaman pengguna berubah dengan kecepatan CPU yang berbeda. Saat "
|
||
"menambahkan node penyimpanan objek, :term: `weight` harus ditentukan yang "
|
||
"mencerminkan :term:` capability ` node."
|
||
|
||
msgid ""
|
||
"For each compute node your environment, view the ``/etc/init.d`` directory "
|
||
"and check if it contains nova*, cinder*, neutron*, or glance*, Also check "
|
||
"RabbitMQ message queues that are growing without being consumed which will "
|
||
"indicate which OpenStack services are affected. Restart the affected "
|
||
"OpenStack services."
|
||
msgstr ""
|
||
"Untuk setiap node komputasi lingkungan Anda, lihat direktori ``/etc/init."
|
||
"d`` dan periksa apakah mengandung nova*, cinder*, neutron*, or glance*, "
|
||
"Juga periksa antrian pesan RabbitMQ yang tumbuh tanpa dikonsumsi yang akan "
|
||
"menunjukkan layanan OpenStack mana yang terpengaruh. Mulai ulang layanan "
|
||
"OpenStack yang terpengaruh."
|
||
|
||
msgid ""
|
||
"For each controller node in your environment, view the ``/etc/init.d`` "
|
||
"directory to check it contains nova*, cinder*, neutron*, or glance*. Also "
|
||
"check RabbitMQ message queues that are growing without being consumed which "
|
||
"will indicate which OpenStack service is affected. Restart the affected "
|
||
"OpenStack service."
|
||
msgstr ""
|
||
"Untuk setiap node pengontrol di lingkungan Anda, lihat direktori ``/etc/init."
|
||
"d`` untuk memeriksanya berisi nova*, cinder*, neutron*, atau glance*. Juga "
|
||
"periksa antrian pesan RabbitMQ yang tumbuh tanpa dikonsumsi yang akan "
|
||
"menunjukkan layanan OpenStack mana yang terpengaruh. Mulai ulang layanan "
|
||
"OpenStack yang terpengaruh."
|
||
|
||
msgid ""
|
||
"For environments using the OpenStack Networking service (neutron), verify "
|
||
"the release version of the database. For example:"
|
||
msgstr ""
|
||
"Untuk lingkungan yang menggunakan layanan OpenStack Networking (neutron), "
|
||
"verifikasi versi rilis dari database. Sebagai contoh:"
|
||
|
||
msgid "For example, run the following command:"
|
||
msgstr "Misalnya, jalankan perintah berikut:"
|
||
|
||
msgid "For example, to place a 5 GB quota on an account:"
|
||
msgstr "Misalnya, untuk menempatkan kuota 5 GB pada akun:"
|
||
|
||
msgid "For example, to restrict a project's image storage to 5 GB, do this:"
|
||
msgstr ""
|
||
"Misalnya, untuk membatasi penyimpanan image proyek hingga 5 GB, lakukan ini:"
|
||
|
||
msgid ""
|
||
"For example, you usually cannot configure NICs for VLANs when PXE booting. "
|
||
"Additionally, you usually cannot PXE boot with bonded NICs. If you run into "
|
||
"this scenario, consider using a simple 1 GB switch in a private network on "
|
||
"which only your cloud communicates."
|
||
msgstr ""
|
||
"Misalnya, Anda biasanya tidak dapat mengonfigurasi NIC untuk VLAN saat PXE "
|
||
"boot. Selain itu, Anda biasanya tidak dapat melakukan PXE boot dengan NIC "
|
||
"terikat. Jika Anda mengalami skenario ini, pertimbangkan untuk menggunakan "
|
||
"switch 1 GB sederhana di jaringan pribadi tempat cloud Anda berkomunikasi."
|
||
|
||
msgid "For example:"
|
||
msgstr "Sebagai contoh:"
|
||
|
||
msgid ""
|
||
"For further research about OpenStack deployment, investigate the supported "
|
||
"and documented preconfigured, prepackaged installers for OpenStack from "
|
||
"companies such as `Canonical <https://www.ubuntu.com/openstack>`_, `Cisco "
|
||
"<https://www.cisco.com/c/en/us/solutions/data-center-virtualization/"
|
||
"openstack-at-cisco/index.html>`_, `Cloudscaling <http://cloudscaling.com/"
|
||
"blog/>`_, `IBM <http://www-03.ibm.com/software/products/en/ibm-cloud-"
|
||
"orchestrator>`_, `Metacloud <http://www.cisco.com/c/en/us/products/cloud-"
|
||
"systems-management/metacloud/index.html>`_, `Mirantis <https://www.mirantis."
|
||
"com>`_, `Rackspace <https://www.rackspace.com/cloud/private>`_, `Red Hat "
|
||
"<https://www.redhat.com/openstack>`_, `SUSE <https://www.suse.com/products/"
|
||
"suse-openstack-cloud>`_, and `SwiftStack <https://www.swiftstack.com>`_."
|
||
msgstr ""
|
||
"Untuk penelitian lebih lanjut tentang penyebaran OpenStack, selidiki "
|
||
"installer prakonfigurasi yang didukung dan didokumentasikan, yang telah "
|
||
"dikemas untuk OpenStack dari perusahaan seperti `Canonical <https://www."
|
||
"ubuntu.com/openstack>`_, `Cisco <https://www.cisco.com/c/en/us/solutions/"
|
||
"data-center-virtualization/openstack-at-cisco/index.html>`_, `Cloudscaling "
|
||
"<http://cloudscaling.com/blog/>`_, `IBM <http://www-03.ibm.com/software/"
|
||
"products/en/ibm-cloud-orchestrator>`_, `Metacloud <http://www.cisco.com/c/en/"
|
||
"us/products/cloud-systems-management/metacloud/index.html>`_, `Mirantis "
|
||
"<https://www.mirantis.com>`_, `Rackspace <https://www.rackspace.com/cloud/"
|
||
"private>`_, `Red Hat <https://www.redhat.com/openstack>`_, `SUSE <https://"
|
||
"www.suse.com/products/suse-openstack-cloud>`_, dan `SwiftStack <https://www."
|
||
"swiftstack.com>`_."
|
||
|
||
msgid ""
|
||
"For instructions on installing, upgrading, or removing command-line clients, "
|
||
"see the `Install the OpenStack command-line client <https://docs.openstack."
|
||
"org/python-openstackclient/latest/>`_."
|
||
msgstr ""
|
||
"Untuk instruksi tentang menginstal, memutakhirkan, atau menghapus klien "
|
||
"command-line client, lihat `Install the OpenStack command-line client "
|
||
"<https://docs.openstack.org/python-openstackclient/latest/>`_."
|
||
|
||
msgid ""
|
||
"For more information OpenStack Security, see the `OpenStack Security Guide "
|
||
"<https://docs.openstack.org/security-guide/>`_."
|
||
msgstr ""
|
||
"Untuk informasi lebih lanjut, OpenStack Security, lihat `OpenStack Security "
|
||
"Guide <https://docs.openstack.org/security-guide/>`_."
|
||
|
||
msgid ""
|
||
"For more information on installing DevStack, see the `DevStack <https://docs."
|
||
"openstack.org/devstack/latest/>`_ website."
|
||
msgstr ""
|
||
"Untuk informasi lebih lanjut tentang menginstal DevStack, lihat `DevStack "
|
||
"<https://docs.openstack.org/devstack/latest/>`_ situs web."
|
||
|
||
msgid ""
|
||
"For more information, see See also `NIST Special Publication 800-53 <https://"
|
||
"web.nvd.nist.gov/view/800-53/>`_."
|
||
msgstr ""
|
||
"Untuk informasi lebih lanjut, lihat Lihat juga `NIST Special Publication "
|
||
"800-53 <https://web.nvd.nist.gov/view/800-53/>`_."
|
||
|
||
msgid ""
|
||
"For more information, see `RabbitMQ documentation <https://www.rabbitmq.com/"
|
||
"partitions.html>`_."
|
||
msgstr ""
|
||
"Untuk informasi lebih lanjut, lihat `RabbitMQ documentation <https://www."
|
||
"rabbitmq.com/partitions.html>`_."
|
||
|
||
msgid ""
|
||
"For resource alerting, for example, monitor disk capacity on a compute node "
|
||
"with Nagios, add the following to your Nagios configuration:"
|
||
msgstr ""
|
||
"Untuk peringatan sumber daya, misalnya, monitor kapasitas disk pada node "
|
||
"komputasi dengan Nagios, tambahkan yang berikut ini ke konfigurasi Nagios "
|
||
"Anda:"
|
||
|
||
msgid ""
|
||
"For stable operations, you want to detect failure promptly and determine "
|
||
"causes efficiently. With a distributed system, it's even more important to "
|
||
"track the right items to meet a service-level target. Learning where these "
|
||
"logs are located in the file system or API gives you an advantage. This "
|
||
"chapter also showed how to read, interpret, and manipulate information from "
|
||
"OpenStack services so that you can monitor effectively."
|
||
msgstr ""
|
||
"Untuk operasi yang stabil, Anda ingin mendeteksi kegagalan dengan segera dan "
|
||
"menentukan penyebab secara efisien. Dengan sistem terdistribusi, bahkan "
|
||
"lebih penting untuk melacak item yang tepat untuk memenuhi target tingkat "
|
||
"layanan. Belajar di mana log ini berada di sistem file atau API memberi Anda "
|
||
"keuntungan. Bab ini juga menunjukkan cara membaca, menafsirkan, dan "
|
||
"memanipulasi informasi dari layanan OpenStack sehingga Anda dapat memonitor "
|
||
"secara efektif."
|
||
|
||
msgid ""
|
||
"For the cloud controller, the good news is if your cloud is using the "
|
||
"FlatDHCP multi-host HA network mode, existing instances and volumes continue "
|
||
"to operate while the cloud controller is offline. For the storage proxy, "
|
||
"however, no storage traffic is possible until it is back up and running."
|
||
msgstr ""
|
||
"Untuk pengendali cloud, kabar baiknya adalah jika cloud Anda menggunakan "
|
||
"mode jaringan HA multi-host FlatDHCP, instance dan volume yang ada terus "
|
||
"beroperasi saat pengendali cloud sedang offline. Untuk proksi penyimpanan, "
|
||
"bagaimanapun, tidak ada lalu lintas penyimpanan yang mungkin sampai itu "
|
||
"kembali dan berjalan."
|
||
|
||
msgid ""
|
||
"For the second path, you can write new features and plug them in using "
|
||
"changes to a configuration file. If the project where your feature would "
|
||
"need to reside uses the Python Paste framework, you can create middleware "
|
||
"for it and plug it in through configuration. There may also be specific ways "
|
||
"of customizing a project, such as creating a new scheduler driver for "
|
||
"Compute or a custom tab for the dashboard."
|
||
msgstr ""
|
||
"Untuk jalur kedua, Anda dapat menulis fitur baru dan menghubungkannya dengan "
|
||
"menggunakan perubahan pada file konfigurasi. Jika proyek tempat fitur Anda "
|
||
"harus berada menggunakan framework Python Paste, Anda dapat membuat "
|
||
"middleware untuk itu dan menghubungkannya melalui konfigurasi. Mungkin juga "
|
||
"ada cara-cara khusus untuk menyesuaikan proyek, seperti membuat driver "
|
||
"penjadwal baru untuk Compute atau tab khusus untuk dasbor."
|
||
|
||
msgid ""
|
||
"For the storage proxy, ensure that the :term:`Object Storage service <Object "
|
||
"Storage service (swift)>` has resumed:"
|
||
msgstr ""
|
||
"Untuk proxy penyimpanan, pastikan bahwa :term:`Object Storage service "
|
||
"<Object Storage service (swift)>` telah dilanjutkan:"
|
||
|
||
msgid ""
|
||
"For this example, we will use the Open vSwitch (OVS) back end. Other back-"
|
||
"end plug-ins will have very different flow paths. OVS is the most popularly "
|
||
"deployed network driver, according to the April 2016 OpenStack User Survey. "
|
||
"We'll describe each step in turn, with :ref:`network_paths` for reference."
|
||
msgstr ""
|
||
"Untuk contoh ini, kita akan menggunakan back end Open vSwitch (OVS). Plug-in "
|
||
"back-end lainnya akan memiliki jalur aliran yang sangat berbeda. OVS adalah "
|
||
"driver jaringan yang paling populer digunakan, menurut Survei Pengguna "
|
||
"OpenStack April 2016. Kami akan menjelaskan setiap langkah pada gilirannya, "
|
||
"dengan :ref:`network_paths` sebagai referensi."
|
||
|
||
msgid ""
|
||
"From the vnet NIC, the packet transfers to a bridge on the compute node, "
|
||
"such as ``br100``."
|
||
msgstr ""
|
||
"Dari vnet NIC, paket mentransfer ke sebuah jembatan (bridge) di node "
|
||
"komputasi, seperti ``br100``."
|
||
|
||
msgid ""
|
||
"From these tables, you can see that a floating IP is technically never "
|
||
"directly related to an instance; it must always go through a fixed IP."
|
||
msgstr ""
|
||
"Dari tabel ini, Anda dapat melihat bahwa IP mengambang secara teknis tidak "
|
||
"pernah terkait langsung dengan instance; itu harus selalu melalui IP tetap."
|
||
|
||
msgid ""
|
||
"From this you see that the DHCP server on that network is using the "
|
||
"``tape6256f7d-31`` device and has an IP address of ``10.0.1.100``. Seeing "
|
||
"the address ``169.254.169.254``, you can also see that the dhcp-agent is "
|
||
"running a metadata-proxy service. Any of the commands mentioned previously "
|
||
"in this chapter can be run in the same way. It is also possible to run a "
|
||
"shell, such as ``bash``, and have an interactive session within the "
|
||
"namespace. In the latter case, exiting the shell returns you to the top-"
|
||
"level default namespace."
|
||
msgstr ""
|
||
"Dari sini Anda melihat bahwa server DHCP pada jaringan itu menggunakan "
|
||
"perangkat ``tape6256f7d-31`` dan memiliki alamat IP ``10.0.1.100``. Melihat "
|
||
"alamat ``169.254.169.254``, Anda juga dapat melihat bahwa agen dhcp "
|
||
"menjalankan layanan proxy-metadata. Perintah apa pun yang disebutkan "
|
||
"sebelumnya dalam bab ini dapat dijalankan dengan cara yang sama. "
|
||
"Dimungkinkan juga untuk menjalankan shell, seperti ``bash``, dan memiliki "
|
||
"sesi interaktif di dalam namespace. Dalam kasus terakhir, keluar dari shell "
|
||
"mengembalikan Anda ke namespace default tingkat atas."
|
||
|
||
msgid ""
|
||
"Functional testing like this is not a replacement for proper unit and "
|
||
"integration testing, but it serves to get you started."
|
||
msgstr ""
|
||
"Pengujian fungsional seperti ini bukan pengganti untuk pengujian unit dan "
|
||
"integrasi yang tepat, tetapi berfungsi untuk membantu Anda memulai."
|
||
|
||
msgid ""
|
||
"Further days go by and we catch The Issue in action more and more. We find "
|
||
"that dhclient is not running after The Issue happens. Now we're back to "
|
||
"thinking it's a DHCP issue. Running ``/etc/init.d/networking`` restart "
|
||
"brings everything back up and running."
|
||
msgstr ""
|
||
"Hari-hari selanjutnya berlalu dan kami terus menangkap isu ini. Kami "
|
||
"menemukan bahwa dhclient tidak berjalan setelah The Issue terjadi. Sekarang "
|
||
"kita kembali berpikir itu masalah DHCP. Menjalankan restart ``/etc/init.d/"
|
||
"networking`` membawa semuanya kembali dan berjalan."
|
||
|
||
msgid ""
|
||
"Further troubleshooting showed that libvirt was not running at all. This "
|
||
"made more sense. If libvirt wasn't running, then no instance could be "
|
||
"virtualized through KVM. Upon trying to start libvirt, it would silently die "
|
||
"immediately. The libvirt logs did not explain why."
|
||
msgstr ""
|
||
"Pemecahan masalah lebih lanjut menunjukkan bahwa libvirt tidak berjalan sama "
|
||
"sekali. Ini lebih masuk akal. Jika libvirt tidak berjalan, maka tidak ada "
|
||
"instance yang dapat divirtualisasikan melalui KVM. Setelah mencoba memulai "
|
||
"libvirt, ia akan segera mati secara diam-diam. Log libvirt tidak menjelaskan "
|
||
"alasannya."
|
||
|
||
msgid ""
|
||
"GRE-based networks are passed with ``patch-tun`` to the tunnel bridge ``br-"
|
||
"tun`` on interface ``patch-int``. This bridge also contains one port for "
|
||
"each GRE tunnel peer, so one for each compute node and network node in your "
|
||
"network. The ports are named sequentially from ``gre-1`` onward."
|
||
msgstr ""
|
||
"Jaringan berbasis GRE diteruskan dengan ``patch-tun`` ke bridge tunnel ``br-"
|
||
"tun`` pada antarmuka ``patch-int``. Jembatan ini juga berisi satu port untuk "
|
||
"setiap peer tunnel GRE, jadi satu untuk setiap node komputasi dan node "
|
||
"jaringan di jaringan Anda. Port diberi nama secara berurutan dari ``gre-1`` "
|
||
"dan seterusnya."
|
||
|
||
msgid ""
|
||
"GRE-based networks will be passed to the tunnel bridge ``br-tun``, which "
|
||
"behaves just like the GRE interfaces on the compute node."
|
||
msgstr ""
|
||
"Jaringan berbasis GRE akan diteruskan ke bridge tunnel ``br-tun``, yang "
|
||
"berperilaku seperti antarmuka GRE pada node komputasi."
|
||
|
||
msgid "Generate signature of image and convert it to a base64 representation:"
|
||
msgstr ""
|
||
"Hasilkan signature of imager dan mengubahnya menjadi representasi base64:"
|
||
|
||
msgid "Geographical Considerations for Object Storage"
|
||
msgstr "Pertimbangan Geografis untuk Object Storage"
|
||
|
||
msgid "Get a list of instances that need to be moved:"
|
||
msgstr "Dapatkan daftar instance yang perlu dipindahkan:"
|
||
|
||
msgid "Getting Credentials"
|
||
msgstr "Mendapatkan Kredensial"
|
||
|
||
msgid ""
|
||
"Go back to the first step and try restarting the RabbitMQ service again. If "
|
||
"you still have errors, remove the contents in the ``/var/lib/rabbitmq/mnesia/"
|
||
"`` directory between stopping and starting the RabbitMQ service."
|
||
msgstr ""
|
||
"Kembali ke langkah pertama dan coba restart layanan RabbitMQ lagi. Jika Anda "
|
||
"masih memiliki kesalahan, hapus konten di direktori ``/var/lib/rabbitmq/"
|
||
"mnesia/`` antara berhenti dan memulai layanan RabbitMQ."
|
||
|
||
msgid "Gramm-Leach-Bliley Act (GLBA)"
|
||
msgstr "Gramm-Leach-Bliley Act (GLBA)"
|
||
|
||
msgid ""
|
||
"Grep for 0x<``provider:segmentation_id``>, 0x3 in this case, in the output "
|
||
"of ``ovs-ofctl dump-flows br-tun``:"
|
||
msgstr ""
|
||
"Grep untuk 0x<`` provider: segmentation_id``>, 0x3 dalam hal ini, dalam "
|
||
"output dari ``ovs-ofctl dump-flows br-tun``:"
|
||
|
||
msgid ""
|
||
"Grep for the ``provider:segmentation_id``, 2113 in this case, in the output "
|
||
"of :command:`ovs-ofctl dump-flows br-int`:"
|
||
msgstr ""
|
||
"Grep untuk ``provider:segmentation_id``, 2113 dalam hal ini, dalam output "
|
||
"dari :command:`ovs-ofctl dump-flows br-int`:"
|
||
|
||
msgid "Guest security domains"
|
||
msgstr "Domain keamanan guest"
|
||
|
||
msgid "HDWMY"
|
||
msgstr "HDWMY"
|
||
|
||
msgid "Handling a Complete Failure"
|
||
msgstr "Menangani Kegagalan Lengkap"
|
||
|
||
msgid "Hardware Procurement"
|
||
msgstr "Pengadaan Perangkat Keras"
|
||
|
||
msgid ""
|
||
"Hardware does not have to be consistent, but it should at least have the "
|
||
"same type of CPU to support instance migration."
|
||
msgstr ""
|
||
"Perangkat keras tidak harus konsisten, tetapi setidaknya harus memiliki "
|
||
"jenis CPU yang sama untuk mendukung migrasi instance."
|
||
|
||
msgid ""
|
||
"Hardware for compute nodes. Typically 256 or 144 GB memory, two processors, "
|
||
"24 cores. 4–6 TB direct attached storage, typically in a RAID 5 "
|
||
"configuration."
|
||
msgstr ""
|
||
"Perangkat keras untuk komputasi node. Biasanya memori 256 atau 144 GB, dua "
|
||
"prosesor, 24 core. Penyimpanan langsung terpasang 4–6 TB, biasanya dalam "
|
||
"konfigurasi RAID 5."
|
||
|
||
msgid ""
|
||
"Hardware for controller nodes, used for all stateless OpenStack API "
|
||
"services. About 32–64 GB memory, small attached disk, one processor, varied "
|
||
"number of cores, such as 6–12."
|
||
msgstr ""
|
||
"Perangkat keras untuk node pengontrol, digunakan untuk semua layanan "
|
||
"OpenStack API stateless. Tentang memori 32–64 GB, disk kecil yang terpasang, "
|
||
"satu prosesor, jumlah core yang bervariasi, seperti 6-12."
|
||
|
||
msgid ""
|
||
"Hardware for storage nodes. Typically for these, the disk space is optimized "
|
||
"for the lowest cost per GB of storage while maintaining rack-space "
|
||
"efficiency."
|
||
msgstr ""
|
||
"Perangkat keras untuk node penyimpanan. Biasanya untuk ini, ruang disk "
|
||
"dioptimalkan untuk biaya terendah per GB penyimpanan sambil mempertahankan "
|
||
"efisiensi ruang rak (rack-space)."
|
||
|
||
msgid "Havana Haunted by the Dead"
|
||
msgstr "Havana Haunted by the Dead (Havana Dihantui oleh Orang Mati)"
|
||
|
||
msgid ""
|
||
"He re-enabled the switch ports and the two compute nodes immediately came "
|
||
"back to life."
|
||
msgstr ""
|
||
"Dia mengaktifkan kembali port switch dan kedua node komputasi segera hidup "
|
||
"kembali."
|
||
|
||
msgid "Health Insurance Portability and Accountability Act (HIPAA)"
|
||
msgstr "Health Insurance Portability and Accountability Act (HIPAA)"
|
||
|
||
msgid "Here is an example error log:"
|
||
msgstr "Berikut ini contoh log kesalahan:"
|
||
|
||
msgid ""
|
||
"Here is an example of a log message with the corresponding ERROR (Python "
|
||
"traceback) immediately following:"
|
||
msgstr ""
|
||
"Berikut adalah contoh dari pesan log dengan ERROR (Python traceback) yang "
|
||
"sesuai segera berikut:"
|
||
|
||
msgid ""
|
||
"Here is an example using the ratios for gathering scalability information "
|
||
"for the number of VMs expected as well as the storage needed. The following "
|
||
"numbers support (200 / 2) × 16 = 1600 VM instances and require 80 TB of "
|
||
"storage for ``/var/lib/nova/instances``:"
|
||
msgstr ""
|
||
"Berikut adalah contoh menggunakan rasio untuk mengumpulkan informasi "
|
||
"skalabilitas untuk jumlah VM yang diharapkan serta penyimpanan yang "
|
||
"dibutuhkan. Angka-angka berikut ini mendukung (200/2) × 16 = 1600 VM "
|
||
"instance dan membutuhkan penyimpanan 80 TB untuk ``/var/lib/nova/"
|
||
"instances``:"
|
||
|
||
msgid ""
|
||
"Here we can see that the request was denied because the remote IP address "
|
||
"wasn't in the set of allowed IPs."
|
||
msgstr ""
|
||
"Di sini kita dapat melihat bahwa permintaan ditolak karena alamat IP jarak "
|
||
"jauh tidak dalam set IP yang diizinkan."
|
||
|
||
msgid ""
|
||
"Here you can see packets received on port ID 1 with the VLAN tag 2113 are "
|
||
"modified to have the internal VLAN tag 7. Digging a little deeper, you can "
|
||
"confirm that port 1 is in fact ``int-br-eth1``:"
|
||
msgstr ""
|
||
"Di sini Anda dapat melihat paket yang diterima pada port ID 1 dengan tag "
|
||
"VLAN 2113 dimodifikasi untuk memiliki tag VLAN internal 7. Menggali lebih "
|
||
"dalam, Anda dapat mengonfirmasi bahwa port 1 sebenarnya ``int-br-eth1``:"
|
||
|
||
msgid ""
|
||
"Here's a quick list of various to-do items for each hour, day, week, month, "
|
||
"and year. Please note that these tasks are neither required nor definitive "
|
||
"but helpful ideas:"
|
||
msgstr ""
|
||
"Berikut adalah daftar singkat berbagai hal yang harus dilakukan untuk setiap "
|
||
"jam, hari, minggu, bulan, dan tahun. Harap perhatikan bahwa tugas-tugas ini "
|
||
"tidak diperlukan atau ide yang pasti tetapi membantu:"
|
||
|
||
msgid ""
|
||
"Here, the ID associated with the instance is ``faf7ded8-4a46-413b-b113-"
|
||
"f19590746ffe``. If you search for this string on the cloud controller in the "
|
||
"``/var/log/nova-*.log`` files, it appears in ``nova-api.log`` and ``nova-"
|
||
"scheduler.log``. If you search for this on the compute nodes in ``/var/log/"
|
||
"nova-*.log``, it appears in ``nova-compute.log``. If no ERROR or CRITICAL "
|
||
"messages appear, the most recent log entry that reports this may provide a "
|
||
"hint about what has gone wrong."
|
||
msgstr ""
|
||
"Di sini, ID yang terkait dengan instance adalah ``faf7ded8-4a46-413b-b113-"
|
||
"f19590746ffe``. Jika Anda mencari string ini pada pengontrol cloud di file "
|
||
"``/var/log/nova-*.log``, muncul di ``nova-api.log`` dan `` nova-scheduler."
|
||
"log`` . Jika Anda mencari ini di compute nodes di ``/var/log/nova-*.log``, "
|
||
"muncul di ``nova-compute.log``. Jika tidak ada pesan ERROR atau CRITICAL "
|
||
"yang muncul, entri log terbaru yang melaporkan ini dapat memberikan petunjuk "
|
||
"tentang apa yang salah."
|
||
|
||
msgid ""
|
||
"Here, the external server received the ping request and sent a ping reply. "
|
||
"On the compute node, you can see that both the ping and ping reply "
|
||
"successfully passed through. You might also see duplicate packets on the "
|
||
"compute node, as seen above, because ``tcpdump`` captured the packet on both "
|
||
"the bridge and outgoing interface."
|
||
msgstr ""
|
||
"Di sini, server eksternal menerima permintaan ping dan mengirim balasan "
|
||
"ping. Pada node komputasi, Anda dapat melihat bahwa ping dan balasan ping "
|
||
"berhasil dilewati. Anda mungkin juga melihat paket duplikat pada node "
|
||
"komputasi, seperti yang terlihat di atas, karena ``tcpdump`` menangkap paket "
|
||
"di kedua jembatan dan antarmuka keluar."
|
||
|
||
msgid ""
|
||
"Here, two floating IPs are available. The first has been allocated to a "
|
||
"project, while the other is unallocated."
|
||
msgstr ""
|
||
"Di sini, dua IP mengambang tersedia. Yang pertama telah dialokasikan untuk "
|
||
"proyek, sementara yang lain tidak dialokasikan."
|
||
|
||
msgid ""
|
||
"Here, you see three flows related to this GRE tunnel. The first is the "
|
||
"translation from inbound packets with this tunnel ID to internal VLAN ID 1. "
|
||
"The second shows a unicast flow to output port 53 for packets destined for "
|
||
"MAC address fa:16:3e:a6:48:24. The third shows the translation from the "
|
||
"internal VLAN representation to the GRE tunnel ID flooded to all output "
|
||
"ports. For further details of the flow descriptions, see the man page for "
|
||
"``ovs-ofctl``. As in the previous VLAN example, numeric port IDs can be "
|
||
"matched with their named representations by examining the output of ``ovs-"
|
||
"ofctl show br-tun``."
|
||
msgstr ""
|
||
"Di sini, Anda melihat tiga aliran yang terkait dengan terowongan GRE ini. "
|
||
"Yang pertama adalah aliran terjemahan dari paket inbound dengan ID "
|
||
"terowongan ini ke ID VLAN internal 1. Yang kedua menunjukkan aliran unicast "
|
||
"ke port output 53 untuk paket yang ditujukan untuk alamat MAC fa:16:3e:"
|
||
"a6:48:24. Yang ketiga menunjukkan aliran terjemahan dari representasi VLAN "
|
||
"internal ke terowongan GRE yang ID dibanjiri ke semua port output. Untuk "
|
||
"detail lebih lanjut dari deskripsi aliran, lihat halaman manual untuk ``ovs-"
|
||
"ofctl``. Seperti pada contoh VLAN sebelumnya, ID port numerik dapat "
|
||
"dicocokkan dengan representasi namanya dengan memeriksa output ``ovs-ofctl "
|
||
"show br-tun``."
|
||
|
||
msgid ""
|
||
"Herein lies a selection of tales from OpenStack cloud operators. Read, and "
|
||
"learn from their wisdom."
|
||
msgstr ""
|
||
"Di sinilah letak berbagai kisah dari operator cloud OpenStack. Baca, dan "
|
||
"belajarlah dari kebijaksanaan mereka."
|
||
|
||
msgid "High Availability"
|
||
msgstr "Ketersediaan Tinggi"
|
||
|
||
msgid "Host aggregates"
|
||
msgstr "Host aggregates"
|
||
|
||
msgid ""
|
||
"Host aggregates and instance-type extra specs are used to provide two "
|
||
"different resource allocation ratios. The default resource allocation ratios "
|
||
"we use are 4:1 CPU and 1.5:1 RAM. Compute-intensive workloads use instance "
|
||
"types that require non-oversubscribed hosts where ``cpu_ratio`` and "
|
||
"``ram_ratio`` are both set to 1.0. Since we have hyper-threading enabled on "
|
||
"our compute nodes, this provides one vCPU per CPU thread, or two vCPUs per "
|
||
"physical core."
|
||
msgstr ""
|
||
"Agregat host dan spesifikasi tambahan tipe instanace digunakan untuk "
|
||
"menyediakan dua rasio alokasi sumber daya yang berbeda. Rasio alokasi sumber "
|
||
"daya default yang kami gunakan adalah 4:1 CPU dan 1.5:1 RAM. Beban kerja "
|
||
"intensif-komputasi menggunakan tipe instance yang memerlukan non-"
|
||
"oversubscribed host dimana ``cpu_ratio`` dan ``ram_ratio`` keduanya diatur "
|
||
"ke 1.0. Karena kami memiliki hyper-threading yang diaktifkan pada node "
|
||
"komputasi kami, ini menyediakan satu vCPU per utas CPU, atau dua vCPU per "
|
||
"core fisik."
|
||
|
||
msgid "Host aggregates zone"
|
||
msgstr "Zona agregat host"
|
||
|
||
msgid "Hourly"
|
||
msgstr "Per jam"
|
||
|
||
msgid "How many backups to keep?"
|
||
msgstr "Berapa banyak cadangan yang harus disimpan?"
|
||
|
||
msgid ""
|
||
"How much storage is required ``(flavor disk size × number of instances)``"
|
||
msgstr ""
|
||
"Berapa banyak penyimpanan yang dibutuhkan ``(flavor disk size × number of "
|
||
"instances)``"
|
||
|
||
msgid ""
|
||
"How networks attach to hypervisors can expose security vulnerabilities. To "
|
||
"mitigate hypervisor breakouts, separate networks from other systems and "
|
||
"schedule instances for the network onto dedicated Compute nodes. This "
|
||
"prevents attackers from having access to the networks from a compromised "
|
||
"instance."
|
||
msgstr ""
|
||
"Bagaimana jaringan dilampirkan ke hypervisor dapat mengekspos kerentanan "
|
||
"keamanan. Untuk mengurangi gangguan hypervisor, pisahkan jaringan dari "
|
||
"sistem lain dan jadwalkan instance untuk jaringan ke node Compute khusus. "
|
||
"Ini mencegah penyerang memiliki akses ke jaringan dari instance yang "
|
||
"dikompromikan."
|
||
|
||
msgid "How often should backups be tested?"
|
||
msgstr "Seberapa sering cadangan harus diuji?"
|
||
|
||
msgid ""
|
||
"However, that is not to say that it needs to be the same size or use "
|
||
"identical hardware as the production environment. It is important to "
|
||
"consider the hardware and scale of the cloud that you are upgrading. The "
|
||
"following tips can help you minimise the cost:"
|
||
msgstr ""
|
||
"Namun, itu tidak berarti bahwa ukurannya harus sama atau menggunakan "
|
||
"perangkat keras yang identik dengan lingkungan produksi. Penting untuk "
|
||
"mempertimbangkan perangkat keras dan skala cloud yang sedang Anda upgrade. "
|
||
"Kiat-kiat berikut dapat membantu Anda meminimalkan biaya:"
|
||
|
||
msgid ""
|
||
"However, you need more than the core count alone to estimate the load that "
|
||
"the API services, database servers, and queue servers are likely to "
|
||
"encounter. You must also consider the usage patterns of your cloud."
|
||
msgstr ""
|
||
"Namun, Anda membutuhkan lebih dari jumlah core saja untuk memperkirakan "
|
||
"beban yang mungkin dihadapi oleh layanan API, server database, dan server "
|
||
"antrian. Anda juga harus mempertimbangkan pola penggunaan cloud Anda."
|
||
|
||
msgid "Hypervisor security"
|
||
msgstr "Keamanan hypervisor"
|
||
|
||
msgid ""
|
||
"Hypervisor security is not an issue if the security of instances is not "
|
||
"important. However, enterprises can minimize vulnerability by avoiding "
|
||
"hardware sharing with others in a public cloud."
|
||
msgstr ""
|
||
"Keamanan hypervisor bukan masalah jika keamanan instance tidak penting. "
|
||
"Namun, perusahaan dapat meminimalkan kerentanan dengan menghindari berbagi "
|
||
"perangkat keras dengan orang lain di cloud publik."
|
||
|
||
msgid ""
|
||
"I checked Glance and noticed that this image was a snapshot that the user "
|
||
"created. At least that was good news—this user would have been the only user "
|
||
"affected."
|
||
msgstr ""
|
||
"Saya memeriksa Glance dan memperhatikan bahwa image ini adalah snapshot yang "
|
||
"dibuat pengguna. Setidaknya itu adalah kabar baik — pengguna ini akan "
|
||
"menjadi satu-satunya pengguna yang terpengaruh."
|
||
|
||
msgid ""
|
||
"I just upgraded OpenStack from Grizzly to Havana 2013.2-2 using the RDO "
|
||
"repository and everything was running pretty well—except the EC2 API."
|
||
msgstr ""
|
||
"Saya baru saja memutakhirkan OpenStack dari Grizzly ke Havana 2013.2-2 "
|
||
"menggunakan repositori RDO dan semuanya berjalan cukup baik — kecuali EC2 "
|
||
"API."
|
||
|
||
msgid ""
|
||
"I logged into the cloud controller and was able to both ``ping`` and SSH "
|
||
"into the problematic compute node which seemed very odd. Usually if I "
|
||
"receive this type of alert, the compute node has totally locked up and would "
|
||
"be inaccessible."
|
||
msgstr ""
|
||
"Saya masuk ke cloud controller dan bisa ``ping`` dan SSH ke node komputasi "
|
||
"bermasalah yang tampak sangat aneh. Biasanya jika saya menerima jenis "
|
||
"peringatan ini, node komputasi telah benar-benar terkunci dan tidak dapat "
|
||
"diakses."
|
||
|
||
msgid ""
|
||
"I looked at the status of both NICs in the bonded pair and saw that neither "
|
||
"was able to communicate with the switch port. Seeing as how each NIC in the "
|
||
"bond is connected to a separate switch, I thought that the chance of a "
|
||
"switch port dying on each switch at the same time was quite improbable. I "
|
||
"concluded that the 10gb dual port NIC had died and needed replaced. I "
|
||
"created a ticket for the hardware support department at the data center "
|
||
"where the node was hosted. I felt lucky that this was a new node and no one "
|
||
"else was hosted on it yet."
|
||
msgstr ""
|
||
"Saya melihat status kedua NIC pada pasangan terikat dan melihat bahwa tidak "
|
||
"ada yang dapat berkomunikasi dengan port switch. Melihat bagaimana masing-"
|
||
"masing NIC dalam ikatan terhubung ke switch terpisah, saya berpikir bahwa "
|
||
"peluang port switch mati pada setiap switch pada saat yang sama cukup "
|
||
"mustahil. Saya menyimpulkan bahwa port ganda 10GB NIC telah mati dan perlu "
|
||
"diganti. Saya membuat tiket untuk departemen dukungan perangkat keras di "
|
||
"pusat data tempat node di-host. Saya merasa beruntung bahwa ini adalah node "
|
||
"baru dan belum ada orang lain yang meng-host-nya."
|
||
|
||
msgid ""
|
||
"I noticed that the API would suffer from a heavy load and respond slowly to "
|
||
"particular EC2 requests such as ``RunInstances``."
|
||
msgstr ""
|
||
"Saya perhatikan bahwa API akan menderita dari beban yang berat dan merespons "
|
||
"dengan lambat permintaan EC2 tertentu seperti ``RunInances``."
|
||
|
||
msgid ""
|
||
"I reviewed the ``nova`` database and saw the instance's entry in the ``nova."
|
||
"instances`` table. The image that the instance was using matched what virsh "
|
||
"was reporting, so no inconsistency there."
|
||
msgstr ""
|
||
"Saya meninjau basis data ``nova`` dan melihat entri instance di tabel ``nova."
|
||
"instances``. Image yang menggunakan instance cocok dengan apa yang "
|
||
"dilaporkan virsh, jadi tidak ada ketidakkonsistenan di sana."
|
||
|
||
msgid ""
|
||
"I was on-site in Kelowna, British Columbia, Canada setting up a new "
|
||
"OpenStack cloud. The deployment was fully automated: Cobbler deployed the OS "
|
||
"on the bare metal, bootstrapped it, and Puppet took over from there. I had "
|
||
"run the deployment scenario so many times in practice and took for granted "
|
||
"that everything was working."
|
||
msgstr ""
|
||
"Saya ada di lokasi di Kelowna, British Columbia, Kanada menyiapkan cloud "
|
||
"OpenStack baru. Penyebaran sepenuhnya otomatis: Cobbler mengerahkan OS pada "
|
||
"bare metal, bootstrap, dan Puppet mengambil alih dari sana. Saya telah "
|
||
"menjalankan skenario penyebaran berkali-kali dalam praktik dan menerima "
|
||
"begitu saja bahwa semuanya bekerja."
|
||
|
||
msgid ""
|
||
"I was totally confused at this point, so I texted our network admin to see "
|
||
"if he was available to help. He logged in to both switches and immediately "
|
||
"saw the problem: the switches detected spanning tree packets coming from the "
|
||
"two compute nodes and immediately shut the ports down to prevent spanning "
|
||
"tree loops:"
|
||
msgstr ""
|
||
"Saya benar-benar bingung pada saat ini, jadi saya mengirim sms admin "
|
||
"jaringan kami untuk melihat apakah dia tersedia untuk membantu. Dia login ke "
|
||
"kedua switch dan segera melihat masalahnya: switch mendeteksi spanning tree "
|
||
"paket yang berasal dari dua node komputasi dan segera menutup port untuk "
|
||
"mencegah spanning tree loop:"
|
||
|
||
msgid "Identity"
|
||
msgstr "Identity"
|
||
|
||
msgid ""
|
||
"Identity is another security consideration. Authentication centralization "
|
||
"provides a single authentication point for users across the deployment, and "
|
||
"a single administration point for traditional create, read, update, and "
|
||
"delete operations. Centralized authentication is also useful for auditing "
|
||
"purposes because all authentication tokens originate from the same source."
|
||
msgstr ""
|
||
"Identitas adalah pertimbangan keamanan lainnya. Sentralisasi otentikasi "
|
||
"menyediakan titik otentikasi tunggal untuk pengguna di seluruh penyebaran, "
|
||
"dan titik administrasi tunggal untuk operasi tradisional membuat, membaca, "
|
||
"memperbarui, dan menghapus. Otentikasi terpusat juga berguna untuk tujuan "
|
||
"audit karena semua token otentikasi berasal dari sumber yang sama."
|
||
|
||
msgid ""
|
||
"Identity service - Clear any expired tokens before synchronizing the "
|
||
"database."
|
||
msgstr ""
|
||
"Layanan Identity - Hapus token yang kedaluwarsa sebelum menyinkronkan "
|
||
"database."
|
||
|
||
msgid ""
|
||
"If Keystone is located remotely instead, edit the ``glance-api.conf`` and "
|
||
"``nova.conf`` files. In the ``[barbican]`` section, configre the "
|
||
"``auth_endpoint`` option:"
|
||
msgstr ""
|
||
"Jika Keystone terletak dari jarak jauh, edit file ``glance-api.conf`` dan "
|
||
"``nova.conf``. Di bagian ``[barbican] ``, konfigurasikan opsi "
|
||
"``auth_endpoint``:"
|
||
|
||
msgid ""
|
||
"If OpenStack :term:`Identity service <Identity service (keystone)>` is "
|
||
"responding slowly, it could be due to the token table getting large. This "
|
||
"can be fixed by running the :command:`keystone-manage token_flush` command."
|
||
msgstr ""
|
||
"Jika OpenStack :term:`Identity service <Identity service (keystone)>` "
|
||
"merespons dengan lambat, bisa jadi karena tabel token semakin besar. Ini "
|
||
"dapat diperbaiki dengan menjalankan perintah :command:`keystone-manage "
|
||
"token_flush` ."
|
||
|
||
msgid ""
|
||
"If a compute node fails and won't be fixed for a few hours (or at all), you "
|
||
"can relaunch all instances that are hosted on the failed node if you use "
|
||
"shared storage for ``/var/lib/nova/instances``."
|
||
msgstr ""
|
||
"Jika compute Node gagal dan tidak akan diperbaiki selama beberapa jam (atau "
|
||
"sama sekali), Anda dapat meluncurkan kembali semua instance yang di-host "
|
||
"pada node gagal jika Anda menggunakan penyimpanan bersama untuk ``/var/lib/"
|
||
"nova/instances``."
|
||
|
||
msgid ""
|
||
"If a hard drive fails in an Object Storage node, replacing it is relatively "
|
||
"easy. This assumes that your Object Storage environment is configured "
|
||
"correctly, where the data that is stored on the failed drive is also "
|
||
"replicated to other drives in the Object Storage environment."
|
||
msgstr ""
|
||
"Jika hard drive gagal dalam node Object Storage, mengganti itu relatif "
|
||
"mudah. Ini mengasumsikan bahwa lingkungan penyimpanan objek Anda "
|
||
"dikonfigurasi dengan benar, di mana data yang disimpan pada drive yang gagal "
|
||
"juga direplikasi ke drive lain di lingkungan penyimpanan objek."
|
||
|
||
msgid ""
|
||
"If a storage node requires a reboot, simply reboot it. Requests for data "
|
||
"hosted on that node are redirected to other copies while the server is "
|
||
"rebooting."
|
||
msgstr ""
|
||
"Jika storage node memerlukan reboot, cukup reboot itu. Permintaan untuk data "
|
||
"yang di-host pada node itu dialihkan ke salinan lain saat server me-reboot."
|
||
|
||
msgid ""
|
||
"If an instance does not boot, meaning ``virsh list`` never shows the "
|
||
"instance as even attempting to boot, do the following on the compute node:"
|
||
msgstr ""
|
||
"Jika sebuah instance tidak bisa boot, berarti ``virsh list`` tidak pernah "
|
||
"memperlihatkan instance tersebut bahkan ketika mencoba untuk boot, lakukan "
|
||
"hal berikut pada node komputasi:"
|
||
|
||
msgid ""
|
||
"If any of these links are missing or incorrect, it suggests a configuration "
|
||
"error. Bridges can be added with ``ovs-vsctl add-br``, and ports can be "
|
||
"added to bridges with ``ovs-vsctl add-port``. While running these by hand "
|
||
"can be useful debugging, it is imperative that manual changes that you "
|
||
"intend to keep be reflected back into your configuration files."
|
||
msgstr ""
|
||
"Jika ada dari tautan ini yang hilang atau salah, ini menunjukkan kesalahan "
|
||
"konfigurasi. Bridges dapat ditambahkan dengan ``ovs-vsctl add-br``, dan port "
|
||
"dapat ditambahkan ke bridge dengan ``ovs-vsctl add-port``. Saat menjalankan "
|
||
"ini dengan tangan dapat menjadi debugging yang berguna, sangat penting bahwa "
|
||
"perubahan manual yang Anda ingin tetap dipantulkan kembali ke file "
|
||
"konfigurasi Anda."
|
||
|
||
msgid ""
|
||
"If possible, we highly recommend that you dump your production database "
|
||
"tables and test the upgrade in your development environment using this data. "
|
||
"Several MySQL bugs have been uncovered during database migrations because of "
|
||
"slight table differences between a fresh installation and tables that "
|
||
"migrated from one version to another. This will have impact on large real "
|
||
"datasets, which you do not want to encounter during a production outage."
|
||
msgstr ""
|
||
"Jika memungkinkan, kami sangat menyarankan Anda membuang tabel database "
|
||
"produksi Anda dan menguji upgrade di lingkungan pengembangan Anda "
|
||
"menggunakan data ini. Beberapa bug MySQL telah ditemukan selama migrasi "
|
||
"basis data karena sedikit perbedaan tabel antara instalasi baru dan tabel "
|
||
"yang dimigrasikan dari satu versi ke versi lain. Ini akan berdampak pada "
|
||
"kumpulan data nyata besar, yang Anda tidak ingin temui selama penghentian "
|
||
"(outage) produksi."
|
||
|
||
msgid ""
|
||
"If restarting the dnsmasq process doesn't fix the issue, you might need to "
|
||
"use ``tcpdump`` to look at the packets to trace where the failure is. The "
|
||
"DNS server listens on UDP port 53. You should see the DNS request on the "
|
||
"bridge (such as, br100) of your compute node. Let's say you start listening "
|
||
"with ``tcpdump`` on the compute node:"
|
||
msgstr ""
|
||
"Jika memulai kembali proses dnsmasq tidak memperbaiki masalah, Anda mungkin "
|
||
"perlu menggunakan ``tcpdump`` untuk melihat paket-paket untuk melacak di "
|
||
"mana kegagalannya. Server DNS mendengarkan pada port UDP 53. Anda harus "
|
||
"melihat permintaan DNS pada bridge (seperti, br100) dari node komputasi "
|
||
"Anda. Katakanlah Anda mulai mendengarkan dengan ``tcpdump`` pada compute "
|
||
"node:"
|
||
|
||
msgid ""
|
||
"If the affected instances also had attached volumes, first generate a list "
|
||
"of instance and volume UUIDs:"
|
||
msgstr ""
|
||
"Jika instance yang terpengaruh juga memiliki volume terlampir, pertama-tama "
|
||
"buat daftar instance dan volume UUID:"
|
||
|
||
msgid ""
|
||
"If the error indicates that the problem is with another component, switch to "
|
||
"tailing that component's log file. For example, if nova cannot access "
|
||
"glance, look at the ``glance-api`` log:"
|
||
msgstr ""
|
||
"Jika kesalahan menunjukkan bahwa masalahnya ada pada komponen lain, alihkan "
|
||
"untuk menyesuaikan file log komponen itu. Misalnya, jika nova tidak dapat "
|
||
"mengakses glance, lihat pada log ``glance-api``:"
|
||
|
||
msgid ""
|
||
"If the instance fails to resolve the hostname, you have a DNS problem. For "
|
||
"example:"
|
||
msgstr ""
|
||
"Jika instance gagal untuk menyelesaikan nama host, Anda memiliki masalah "
|
||
"DNS. Sebagai contoh:"
|
||
|
||
msgid ""
|
||
"If the package manager prompts you to update configuration files, reject the "
|
||
"changes. The package manager appends a suffix to newer versions of "
|
||
"configuration files. Consider reviewing and adopting content from these "
|
||
"files."
|
||
msgstr ""
|
||
"Jika manajer paket meminta Anda untuk update file konfigurasi, tolak "
|
||
"perubahannya. Manajer paket menambahkan akhiran ke versi yang lebih baru "
|
||
"dari file konfigurasi. Pertimbangkan untuk meninjau dan mengadopsi konten "
|
||
"dari file-file ini."
|
||
|
||
msgid ""
|
||
"If the problem does not seem to be related to dnsmasq itself, at this point "
|
||
"use ``tcpdump`` on the interfaces to determine where the packets are getting "
|
||
"lost."
|
||
msgstr ""
|
||
"Jika masalah tampaknya tidak terkait dengan dnsmasq itu sendiri, pada titik "
|
||
"ini gunakan ``tcpdump`` pada antarmuka untuk menentukan di mana paket-paket "
|
||
"hilang."
|
||
|
||
msgid ""
|
||
"If the service refuses to stop, then run the :command:`pkill` command to "
|
||
"stop the service, then restart the service:"
|
||
msgstr ""
|
||
"Jika layanan menolak untuk berhenti, maka jalankan perintah :command:"
|
||
"`pkill`untuk menghentikan layanan, kemudian mulai ulang layanan:"
|
||
|
||
msgid ""
|
||
"If there are errors, run the :command:`cluster_status` command to make sure "
|
||
"there are no partitions:"
|
||
msgstr ""
|
||
"Jika ada kesalahan, jalankan perintah :command:`cluster_status` untuk "
|
||
"memastikan tidak ada partisi:"
|
||
|
||
msgid ""
|
||
"If there are no errors, restart the RabbitMQ service on the next controller "
|
||
"node."
|
||
msgstr ""
|
||
"Jika tidak ada kesalahan, restart layanan RabbitMQ pada node controller "
|
||
"berikutnya."
|
||
|
||
msgid ""
|
||
"If there is not enough information in the existing logs, you may need to add "
|
||
"your own custom logging statements to the ``nova-*`` services."
|
||
msgstr ""
|
||
"Jika tidak ada informasi yang cukup di log yang ada, Anda mungkin perlu "
|
||
"menambahkan pernyataan logging kustom Anda sendiri ke layanan ``nova- * ``."
|
||
|
||
msgid ""
|
||
"If there's a suspicious-looking dnsmasq log message, take a look at the "
|
||
"command-line arguments to the dnsmasq processes to see if they look correct:"
|
||
msgstr ""
|
||
"Jika ada pesan log dnsmasq yang tampak mencurigakan, lihat argumen baris "
|
||
"perintah untuk proses dnsmasq untuk melihat apakah mereka terlihat benar:"
|
||
|
||
msgid "If you access or view the user's content and data, get approval first!"
|
||
msgstr ""
|
||
"Jika Anda mengakses atau melihat konten dan data pengguna, dapatkan "
|
||
"persetujuan terlebih dahulu!"
|
||
|
||
msgid ""
|
||
"If you are able to use :term:`SSH <secure shell (SSH)>` to log into an "
|
||
"instance, but it takes a very long time (on the order of a minute) to get a "
|
||
"prompt, then you might have a DNS issue. The reason a DNS issue can cause "
|
||
"this problem is that the SSH server does a reverse DNS lookup on the IP "
|
||
"address that you are connecting from. If DNS lookup isn't working on your "
|
||
"instances, then you must wait for the DNS reverse lookup timeout to occur "
|
||
"for the SSH login process to complete."
|
||
msgstr ""
|
||
"Jika Anda dapat menggunakan :term:`SSH <secure shell (SSH)>` untuk masuk ke "
|
||
"sebuah instance, tetapi butuh waktu yang sangat lama (dalam urutan satu "
|
||
"menit) untuk mendapatkan prompt, maka Anda mungkin memiliki DNS issue. "
|
||
"Alasan masalah DNS dapat menyebabkan masalah ini adalah bahwa server SSH "
|
||
"melakukan pencarian DNS terbalik pada alamat IP yang Anda hubungkan. Jika "
|
||
"pencarian DNS tidak bekerja pada instance Anda, maka Jika Anda dapat "
|
||
"menggunakan: istilah: `SSH <secure shell (SSH)>` untuk masuk ke sebuah "
|
||
"instance, tetapi butuh waktu yang sangat lama (dalam urutan satu menit) "
|
||
"untuk mendapatkan prompt, maka Anda mungkin memiliki Masalah DNS. Alasan "
|
||
"masalah DNS dapat menyebabkan masalah ini adalah bahwa server SSH melakukan "
|
||
"pencarian DNS terbalik pada alamat IP yang Anda hubungkan. Jika pencarian "
|
||
"DNS tidak berfungsi pada instance Anda, maka Anda harus menunggu waktu "
|
||
"tunggu DNS reverse lookup agar proses masuk SSH selesai."
|
||
|
||
msgid ""
|
||
"If you are encountering any sort of networking difficulty, one good initial "
|
||
"troubleshooting step is to make sure that your interfaces are up. For "
|
||
"example:"
|
||
msgstr ""
|
||
"Jika Anda menghadapi kesulitan jaringan apa pun, satu langkah pemecahan "
|
||
"masalah awal yang baik adalah memastikan bahwa antarmuka Anda sudah aktif. "
|
||
"Sebagai contoh:"
|
||
|
||
msgid ""
|
||
"If you are logged in to an instance and ping an external host, for example, "
|
||
"Google, the ping packet takes the route shown in :ref:`figure_traffic_route`."
|
||
msgstr ""
|
||
"Jika Anda masuk ke instance dan melakukan ping host eksternal, misalnya, "
|
||
"Google, paket ping mengambil rute yang ditunjukkan :ref:"
|
||
"`figure_traffic_route`."
|
||
|
||
msgid ""
|
||
"If you are using cinder, run the following command to see a similar listing:"
|
||
msgstr ""
|
||
"Jika Anda menggunakan cinder, jalankan perintah berikut untuk melihat daftar "
|
||
"serupa:"
|
||
|
||
msgid ""
|
||
"If you can't ping the IP address of the compute node, the problem is between "
|
||
"the instance and the compute node. This includes the bridge connecting the "
|
||
"compute node's main NIC with the vnet NIC of the instance."
|
||
msgstr ""
|
||
"Jika Anda tidak bisa melakukan ping alamat IP dari node komputasi, "
|
||
"masalahnya adalah antara instance dan node komputasi. Ini termasuk jembatan "
|
||
"yang menghubungkan NIC utama node komputasi dengan vnet NIC dari instance."
|
||
|
||
msgid ""
|
||
"If you can't, try pinging the IP address of the compute node where the "
|
||
"instance is hosted. If you can ping this IP, then the problem is somewhere "
|
||
"between the compute node and that compute node's gateway."
|
||
msgstr ""
|
||
"Jika Anda tidak bisa, coba ping alamat IP dari node compute tempat instance "
|
||
"di-host. Jika Anda dapat melakukan ping IP ini, maka masalahnya adalah di "
|
||
"suatu tempat antara node komputasi dan gateway node komputasi itu."
|
||
|
||
msgid ""
|
||
"If you cannot have any data loss at all, you should also focus on a highly "
|
||
"available deployment. The `OpenStack High Availability Guide <https://docs."
|
||
"openstack.org/ha-guide/index.html>`_ offers suggestions for elimination of a "
|
||
"single point of failure that could cause system downtime. While it is not a "
|
||
"completely prescriptive document, it offers methods and techniques for "
|
||
"avoiding downtime and data loss."
|
||
msgstr ""
|
||
"Jika Anda tidak dapat kehilangan data sama sekali, Anda juga harus fokus "
|
||
"pada penyebaran yang sangat tersedia. The `OpenStack High Availability Guide "
|
||
"<https://docs.openstack.org/ha-guide/index.html>`_ menawarkan saran untuk "
|
||
"menghilangkan satu titik kegagalan yang dapat menyebabkan gangguan sistem. "
|
||
"Meskipun ini bukan dokumen yang sepenuhnya preskriptif, ia menawarkan metode "
|
||
"dan teknik untuk menghindari downtime dan kehilangan data."
|
||
|
||
msgid ""
|
||
"If you cannot launch an instance, check the ``/var/log/rabbitmq`` log files "
|
||
"for reported connection issues."
|
||
msgstr ""
|
||
"Jika Anda tidak dapat meluncurkan instance, periksa file log ``/var/log/"
|
||
"rabbitmq`` untuk masalah koneksi yang dilaporkan."
|
||
|
||
msgid "If you cannot launch an instance, continue to troubleshoot the issue."
|
||
msgstr ""
|
||
"Jika Anda tidak dapat meluncurkan sebuah instance, lanjutkan untuk "
|
||
"memecahkan masalah."
|
||
|
||
msgid ""
|
||
"If you do not follow last three steps, OpenStack Compute cannot manage the "
|
||
"instance any longer. It fails to respond to any command issued by OpenStack "
|
||
"Compute, and it is marked as shut down."
|
||
msgstr ""
|
||
"Jika Anda tidak mengikuti tiga langkah terakhir, OpenStack Compute tidak "
|
||
"dapat mengelola instance lagi. Gagal merespons perintah apa pun yang "
|
||
"dikeluarkan oleh OpenStack Compute, dan ditandai sebagai dimatikan."
|
||
|
||
msgid ""
|
||
"If you do not see the ``DHCPDISCOVER``, a problem exists with the packet "
|
||
"getting from the instance to the machine running dnsmasq. If you see all of "
|
||
"the preceding output and your instances are still not able to obtain IP "
|
||
"addresses, then the packet is able to get from the instance to the host "
|
||
"running dnsmasq, but it is not able to make the return trip."
|
||
msgstr ""
|
||
"Jika Anda tidak melihat ``DHCPDISCOVER``, ada masalah dengan paket yang "
|
||
"didapat dari instance ke mesin yang menjalankan dnsmasq. Jika Anda melihat "
|
||
"semua output sebelumnya dan instance Anda masih tidak dapat memperoleh "
|
||
"alamat IP, maka paket tersebut bisa mendapatkan dari instance ke host yang "
|
||
"menjalankan dnsmasq, tetapi tidak dapat melakukan perjalanan kembali."
|
||
|
||
msgid ""
|
||
"If you find that you have reached or are reaching the capacity limit of your "
|
||
"computing resources, you should plan to add additional compute nodes. Adding "
|
||
"more nodes is quite easy. The process for adding compute nodes is the same "
|
||
"as when the initial compute nodes were deployed to your cloud: use an "
|
||
"automated deployment system to bootstrap the bare-metal server with the "
|
||
"operating system and then have a configuration-management system install and "
|
||
"configure OpenStack Compute. Once the Compute service has been installed and "
|
||
"configured in the same way as the other compute nodes, it automatically "
|
||
"attaches itself to the cloud. The cloud controller notices the new node(s) "
|
||
"and begins scheduling instances to launch there."
|
||
msgstr ""
|
||
"Jika Anda menemukan bahwa Anda telah mencapai atau sedang mencapai batas "
|
||
"kapasitas sumber daya komputasi Anda, Anda harus merencanakan untuk "
|
||
"menambahkan node komputasi tambahan. Menambahkan lebih banyak node cukup "
|
||
"mudah. Proses untuk menambahkan node komputasi sama dengan ketika node "
|
||
"komputasi awal dikerahkan ke cloud Anda: gunakan sistem penyebaran otomatis "
|
||
"untuk mem-bootstrap server bare-metal dengan sistem operasi dan kemudian "
|
||
"memiliki sistem manajemen konfigurasi menginstal dan mengkonfigurasi "
|
||
"OpenStack Compute . Setelah layanan Compute telah diinstal dan "
|
||
"dikonfigurasikan dengan cara yang sama seperti node komputasi lainnya, ia "
|
||
"secara otomatis melampirkan dirinya ke cloud. Kontroler awan memperhatikan "
|
||
"node baru dan mulai menjadwalkan instance untuk diluncurkan di sana."
|
||
|
||
msgid ""
|
||
"If you know the fully qualified domain name (FQDN) that will be assigned to "
|
||
"the IP address, assign the port with the same name:"
|
||
msgstr ""
|
||
"Jika Anda tahu nama domain yang sepenuhnya memenuhi syarat (FQDN) yang akan "
|
||
"ditetapkan ke alamat IP, tetapkan porta dengan nama yang sama:"
|
||
|
||
msgid ""
|
||
"If you modify the configuration, it reverts the next time you restart ``nova-"
|
||
"network`` or ``neutron-server``. You must use OpenStack to manage iptables."
|
||
msgstr ""
|
||
"Jika Anda mengubah konfigurasi, itu akan kembali saat Anda memulai kembali "
|
||
"``nova-network`` atau ``neutron-server`` di lain waktu. Anda harus "
|
||
"menggunakan OpenStack untuk mengelola iptables."
|
||
|
||
msgid ""
|
||
"If you need to reboot a compute node due to planned maintenance, such as a "
|
||
"software or hardware upgrade, perform the following steps:"
|
||
msgstr ""
|
||
"Jika Anda perlu me-reboot node komputasi karena pemeliharaan yang "
|
||
"direncanakan, seperti peningkatan perangkat lunak atau perangkat keras, "
|
||
"lakukan langkah-langkah berikut:"
|
||
|
||
msgid ""
|
||
"If you need to shut down a storage node for an extended period of time (one "
|
||
"or more days), consider removing the node from the storage ring. For example:"
|
||
msgstr ""
|
||
"Jika Anda perlu mematikan storage node untuk periode waktu yang lama (satu "
|
||
"hari atau lebih), pertimbangkan untuk melepaskan node dari lingkaran "
|
||
"storage. Sebagai contoh:"
|
||
|
||
msgid "If you only want to backup a single database, you can instead run:"
|
||
msgstr ""
|
||
"Jika Anda hanya ingin membuat cadangan satu database, Anda dapat menjalankan:"
|
||
|
||
msgid ""
|
||
"If you receive alerts for RabbitMQ, take the following steps to troubleshoot "
|
||
"and resolve the issue:"
|
||
msgstr ""
|
||
"Jika Anda menerima peringatan untuk RabbitMQ, ambil langkah-langkah berikut "
|
||
"untuk memecahkan masalah dan menyelesaikan masalah:"
|
||
|
||
msgid ""
|
||
"If you removed the release repositories, you must first reinstall them and "
|
||
"run the :command:`apt-get update` command."
|
||
msgstr ""
|
||
"Jika Anda menghapus repositori rilis, Anda harus menginstalnya kembali dan "
|
||
"menjalankan perintah :command:`apt-get update` "
|
||
|
||
msgid ""
|
||
"If you run FlatDHCPManager, one bridge is on the compute node. If you run "
|
||
"VlanManager, one bridge exists for each VLAN."
|
||
msgstr ""
|
||
"Jika Anda menjalankan FlatDHCPManager, satu bridge ada di simpul komputasi. "
|
||
"Jika Anda menjalankan VlanManager, ada satu bridge untuk setiap VLAN."
|
||
|
||
msgid "If you still cannot find the lost IP address, repeat these steps again."
|
||
msgstr ""
|
||
"Jika Anda masih tidak dapat menemukan alamat IP yang hilang, ulangi langkah "
|
||
"ini lagi."
|
||
|
||
msgid ""
|
||
"If you support the EC2 API on your cloud, you should also install the "
|
||
"euca2ools package or some other EC2 API tool so that you can get the same "
|
||
"view your users have. Using EC2 API-based tools is mostly out of the scope "
|
||
"of this guide, though we discuss getting credentials for use with it."
|
||
msgstr ""
|
||
"Jika Anda mendukung EC2 API di cloud Anda, Anda juga harus menginstal paket "
|
||
"euca2ools atau alat EC2 API lainnya sehingga Anda bisa mendapatkan tampilan "
|
||
"yang sama dengan yang dimiliki oleh pengguna Anda. Menggunakan alat berbasis "
|
||
"EC2 API sebagian besar berada di luar cakupan panduan ini, meskipun kami "
|
||
"membahas cara mendapatkan kredensial untuk digunakan dengannya."
|
||
|
||
msgid ""
|
||
"If you use a configuration-management system, such as Puppet, that ensures "
|
||
"the ``nova-compute`` service is always running, you can temporarily move the "
|
||
"``init`` files:"
|
||
msgstr ""
|
||
"Jika Anda menggunakan sistem manajemen konfigurasi, seperti Puppet, yang "
|
||
"memastikan layanan ``nova-compute`` selalu berjalan, Anda dapat memindahkan "
|
||
"sementara file ``init`` untuk sementara:"
|
||
|
||
msgid ""
|
||
"If you use an external storage plug-in or shared file system with your "
|
||
"cloud, you can test whether it works by creating a second share or endpoint. "
|
||
"This allows you to test the system before entrusting the new version on to "
|
||
"your storage."
|
||
msgstr ""
|
||
"Jika Anda menggunakan plug-in penyimpanan eksternal atau sistem file bersama "
|
||
"dengan cloud Anda, Anda dapat menguji apakah itu berfungsi dengan membuat "
|
||
"share atau endpoint kedua. Ini memungkinkan Anda untuk menguji sistem "
|
||
"sebelum mempercayakan versi baru ke penyimpanan Anda."
|
||
|
||
msgid ""
|
||
"If you're running the Cirros image, it doesn't have the \"host\" program "
|
||
"installed, in which case you can use ping to try to access a machine by "
|
||
"hostname to see whether it resolves. If DNS is working, the first line of "
|
||
"ping would be:"
|
||
msgstr ""
|
||
"Jika Anda menjalankan image Cirros, itu tidak memiliki program \"host\" yang "
|
||
"diinstal, dalam hal ini Anda dapat menggunakan ping untuk mencoba mengakses "
|
||
"mesin dengan nama host untuk melihat apakah itu menyelesaikan. Jika DNS "
|
||
"berfungsi, baris pertama ping adalah:"
|
||
|
||
msgid ""
|
||
"If you're using the Networking service ML2 plug-in, update the Networking "
|
||
"service database to indicate that all ports that used to be hosted on c01."
|
||
"example.com are now hosted on c02.example.com:"
|
||
msgstr ""
|
||
"Jika Anda menggunakan ML2 plug-in layanan Networking , perbarui database "
|
||
"layanan Networking untuk menunjukkan bahwa semua port yang dulu di-host di "
|
||
"c01.example.com sekarang di-host di c02.example.com:"
|
||
|
||
msgid ""
|
||
"If your OpenStack Block Storage nodes are separate from your compute nodes, "
|
||
"the same procedure still applies because the same queuing and polling system "
|
||
"is used in both services."
|
||
msgstr ""
|
||
"Jika node Block Storage OpenStack Anda terpisah dari node komputasi Anda, "
|
||
"prosedur yang sama masih berlaku karena sistem antrian dan sistem suara "
|
||
"polling yang sama digunakan di kedua layanan."
|
||
|
||
msgid "If your cloud is not using a shared storage, run:"
|
||
msgstr "Jika cloud Anda tidak menggunakan penyimpanan bersama, jalankan:"
|
||
|
||
msgid "If your cloud is using a shared storage:"
|
||
msgstr "Jika cloud Anda menggunakan penyimpanan bersama:"
|
||
|
||
msgid ""
|
||
"If your instance failed to obtain an IP through DHCP, some messages should "
|
||
"appear in the console. For example, for the Cirros image, you see output "
|
||
"that looks like the following:"
|
||
msgstr ""
|
||
"Jika instance Anda gagal mendapatkan IP melalui DHCP, beberapa pesan akan "
|
||
"muncul di konsol. Misalnya, untuk image Cirros, Anda melihat output yang "
|
||
"terlihat seperti berikut:"
|
||
|
||
msgid ""
|
||
"If your instances are still not able to obtain IP addresses, the next thing "
|
||
"to check is whether dnsmasq is seeing the DHCP requests from the instance. "
|
||
"On the machine that is running the dnsmasq process, which is the compute "
|
||
"host if running in multi-host mode, look at ``/var/log/syslog`` to see the "
|
||
"dnsmasq output. If dnsmasq is seeing the request properly and handing out an "
|
||
"IP, the output looks like this:"
|
||
msgstr ""
|
||
"Jika instance Anda masih tidak dapat memperoleh alamat IP, hal berikutnya "
|
||
"yang perlu diperiksa adalah apakah dnsmasq melihat permintaan DHCP dari "
|
||
"instance. Pada mesin yang menjalankan proses dnsmasq, yang merupakan host "
|
||
"komputasi jika berjalan dalam mode multi-host, lihat ``/var/log/syslog`` "
|
||
"untuk melihat output dnsmasq. Jika dnsmasq melihat permintaan dengan benar "
|
||
"dan membagikan IP, hasilnya terlihat seperti ini:"
|
||
|
||
msgid ""
|
||
"If your new object storage node has a different number of disks than the "
|
||
"original nodes have, the command to add the new node is different from the "
|
||
"original commands. These parameters vary from environment to environment."
|
||
msgstr ""
|
||
"Jika node penyimpanan objek baru Anda memiliki jumlah disk yang berbeda dari "
|
||
"node asli, perintah untuk menambahkan node baru berbeda dari perintah asli. "
|
||
"Parameter ini bervariasi dari satu lingkungan ke lingkungan lainnya."
|
||
|
||
msgid ""
|
||
"Image API v2 supports multiline properties, so this option is not required "
|
||
"for v2 but it can still be used."
|
||
msgstr ""
|
||
"Image API v2 mendukung properti multiline, jadi opsi ini tidak diperlukan "
|
||
"untuk v2 tetapi masih dapat digunakan."
|
||
|
||
msgid "Image Catalog and Delivery"
|
||
msgstr "Katalog Image dan Pengiriman"
|
||
|
||
msgid "Image Catalog and Delivery services"
|
||
msgstr "Katalog Image dan layanan Delivery"
|
||
|
||
msgid "Image service"
|
||
msgstr "Layanan Image"
|
||
|
||
msgid "Image usage"
|
||
msgstr "Penggunaan image"
|
||
|
||
msgid "Images"
|
||
msgstr "Images"
|
||
|
||
msgid ""
|
||
"Imagine a scenario where you have public access to one of your containers, "
|
||
"but what you really want is to restrict access to that to a set of IPs based "
|
||
"on a whitelist. In this example, we'll create a piece of middleware for "
|
||
"swift that allows access to a container from only a set of IP addresses, as "
|
||
"determined by the container's metadata items. Only those IP addresses that "
|
||
"you explicitly whitelist using the container's metadata will be able to "
|
||
"access the container."
|
||
msgstr ""
|
||
"Bayangkan sebuah skenario di mana Anda memiliki akses publik ke salah satu "
|
||
"kontainer Anda, tetapi yang Anda inginkan adalah membatasi akses ke satu set "
|
||
"IP berdasarkan daftar putih. Dalam contoh ini, kami akan membuat sepotong "
|
||
"middleware untuk swift yang memungkinkan akses ke sebuah kontainer dari "
|
||
"hanya satu set alamat IP, seperti yang ditentukan oleh item metadata dari "
|
||
"kontainer. Hanya alamat IP yang Anda daftar putih secara eksplisit "
|
||
"menggunakan metadata kontainer yang akan dapat mengakses kontainer."
|
||
|
||
msgid "Implementing Periodic Tasks"
|
||
msgstr "Menerapkan Tugas Berkala"
|
||
|
||
msgid ""
|
||
"In OpenStack user interfaces and documentation, a group of users is referred "
|
||
"to as a :term:`project` or :term:`tenant`. These terms are interchangeable."
|
||
msgstr ""
|
||
"Dalam antarmuka pengguna dan dokumentasi OpenStack, sekelompok pengguna "
|
||
"disebut sebagai :term:`project` atau :term:`tenant`. Ketentuan-ketentuan "
|
||
"ini dapat dipertukarkan."
|
||
|
||
msgid ""
|
||
"In ``nova.conf``, ``vlan_interface`` specifies what interface OpenStack "
|
||
"should attach all VLANs to. The correct setting should have been:"
|
||
msgstr ""
|
||
"Dalam ``nova.conf``, ``vlan_interface`` menentukan antarmuka apa yang harus "
|
||
"diikat (attach) OpenStack dengan semua VLAN. Pengaturan yang benar "
|
||
"seharusnya:"
|
||
|
||
msgid ""
|
||
"In addition, consider remote power control as well. While IPMI usually "
|
||
"controls the server's power state, having remote access to the PDU that the "
|
||
"server is plugged into can really be useful for situations when everything "
|
||
"seems wedged."
|
||
msgstr ""
|
||
"Selain itu, pertimbangkan juga kendali daya jarak jauh. Sementara IPMI "
|
||
"biasanya mengontrol status daya server, memiliki akses jarak jauh ke PDU "
|
||
"yang tersambung ke server benar-benar dapat berguna untuk situasi ketika "
|
||
"semuanya tampak terjepit (wedged)."
|
||
|
||
msgid ""
|
||
"In addition, database migrations are now tested with the Turbo Hipster tool. "
|
||
"This tool tests database migration performance on copies of real-world user "
|
||
"databases."
|
||
msgstr ""
|
||
"Selain itu, migrasi basis data sekarang diuji dengan alat Turbo Hipster. "
|
||
"Alat ini menguji kinerja migrasi basis data pada salinan basis data pengguna "
|
||
"dunia nyata."
|
||
|
||
msgid ""
|
||
"In an OpenStack cloud, the dnsmasq process acts as the DNS server for the "
|
||
"instances in addition to acting as the DHCP server. A misbehaving dnsmasq "
|
||
"process may be the source of DNS-related issues inside the instance. As "
|
||
"mentioned in the previous section, the simplest way to rule out a "
|
||
"misbehaving dnsmasq process is to kill all the dnsmasq processes on the "
|
||
"machine and restart ``nova-network``. However, be aware that this command "
|
||
"affects everyone running instances on this node, including tenants that have "
|
||
"not seen the issue. As a last resort, as root:"
|
||
msgstr ""
|
||
"Dalam cloud OpenStack, proses dnsmasq bertindak sebagai server DNS untuk "
|
||
"instance selain bertindak sebagai server DHCP. Proses dnsmasq yang keliru "
|
||
"mungkin menjadi sumber masalah terkait DNS di dalam instance. Seperti "
|
||
"disebutkan di bagian sebelumnya, cara paling sederhana untuk mengesampingkan "
|
||
"proses dnsmasq yang rusak adalah dengan mematikan semua proses dnsmasq pada "
|
||
"mesin dan memulai kembali ``nova-network``. Namun, perlu diketahui bahwa "
|
||
"perintah ini mempengaruhi semua orang yang menjalankan instance pada node "
|
||
"ini, termasuk penyewa yang belum melihat masalah. Sebagai upaya terakhir, "
|
||
"sebagai root:"
|
||
|
||
msgid ""
|
||
"In an elastic cloud environment using the ``Public_AGILE`` network, each "
|
||
"instance has a publicly accessible IPv4 & IPv6 address. It does not support "
|
||
"the concept of OpenStack floating IP addresses that can easily be attached, "
|
||
"removed, and transferred between instances. However, there is a workaround "
|
||
"using neutron ports which contain the IPv4 & IPv6 address."
|
||
msgstr ""
|
||
"Dalam lingkungan cloud yang elastis menggunakan jaringan ``Public_AGILE``, "
|
||
"setiap instance memiliki alamat IPv4 & IPv6 yang dapat diakses publik. Itu "
|
||
"tidak mendukung konsep alamat IP mengambang OpenStack yang dapat dengan "
|
||
"mudah dilampirkan, dihapus, dan ditransfer antar instance. Namun, ada solusi "
|
||
"menggunakan port neutron yang berisi alamat IPv4 & IPv6."
|
||
|
||
msgid ""
|
||
"In most cases, the error is the result of something in libvirt's XML file "
|
||
"(``/etc/libvirt/qemu/instance-xxxxxxxx.xml``) that no longer exists. You can "
|
||
"enforce re-creation of the XML file as well as rebooting the instance by "
|
||
"running the following command:"
|
||
msgstr ""
|
||
"Dalam kebanyakan kasus, kesalahan adalah hasil dari sesuatu dalam file XML "
|
||
"libvirt (``/etc/libvirt/qemu/instance-xxxxxxxx.xml``) yang tidak lagi ada. "
|
||
"Anda dapat memberlakukan kembali penciptaan file XML serta me-reboot "
|
||
"instance dengan menjalankan perintah berikut:"
|
||
|
||
msgid ""
|
||
"In our experience, most operators don't sit right next to the servers "
|
||
"running the cloud, and many don't necessarily enjoy visiting the data "
|
||
"center. OpenStack should be entirely remotely configurable, but sometimes "
|
||
"not everything goes according to plan."
|
||
msgstr ""
|
||
"Dalam pengalaman kami, sebagian besar operator tidak duduk tepat di sebelah "
|
||
"server yang menjalankan cloud, dan banyak yang tidak selalu menikmati "
|
||
"mengunjungi pusat data. OpenStack harus sepenuhnya dapat dikonfigurasi dari "
|
||
"jarak jauh, tetapi terkadang tidak semuanya berjalan sesuai rencana."
|
||
|
||
msgid ""
|
||
"In some scenarios, instances are running but are inaccessible through SSH "
|
||
"and do not respond to any command. The VNC console could be displaying a "
|
||
"boot failure or kernel panic error messages. This could be an indication of "
|
||
"file system corruption on the VM itself. If you need to recover files or "
|
||
"inspect the content of the instance, qemu-nbd can be used to mount the disk."
|
||
msgstr ""
|
||
"Dalam beberapa skenario, instance berjalan tetapi tidak dapat diakses "
|
||
"melalui SSH dan tidak menanggapi perintah apa pun. Konsol VNC dapat "
|
||
"menampilkan pesan kegagalan boot atau kesalahan panik kernel. Ini bisa "
|
||
"menjadi indikasi kerusakan sistem file pada VM itu sendiri. Jika Anda perlu "
|
||
"memulihkan file atau memeriksa konten instance, qemu-nbd dapat digunakan "
|
||
"untuk me-mount disk."
|
||
|
||
msgid ""
|
||
"In this case, ``gre-1`` is a tunnel from IP 10.10.128.21, which should match "
|
||
"a local interface on this node, to IP 10.10.128.16 on the remote side."
|
||
msgstr ""
|
||
"Dalam hal ini, ``gre-1`` adalah terowongan dari IP 10.10.128.21, yang harus "
|
||
"cocok dengan antarmuka lokal pada node ini, ke IP 10.10.128.16 di sisi jarak "
|
||
"jauh (remote side)."
|
||
|
||
msgid ""
|
||
"In this error, a nova service has failed to connect to the RabbitMQ server "
|
||
"because it got a connection refused error."
|
||
msgstr ""
|
||
"Dalam kesalahan ini, layanan nova telah gagal terhubung ke server RabbitMQ "
|
||
"karena mendapat koneksi menolak kesalahan."
|
||
|
||
msgid ""
|
||
"In this example, ``cinder-volumes`` failed to start and has provided a stack "
|
||
"trace, since its volume back end has been unable to set up the storage volume"
|
||
"—probably because the LVM volume that is expected from the configuration "
|
||
"does not exist."
|
||
msgstr ""
|
||
"Dalam contoh ini, ``cinder-volume`` gagal untuk memulai dan telah "
|
||
"menyediakan jejak stack (stack trace), karena volume back end-nya tidak "
|
||
"dapat mengatur volume penyimpanan— mungkin karena volume LVM yang diharapkan "
|
||
"dari konfigurasi tidak ada ."
|
||
|
||
msgid "In this example, these locations have the following IP addresses:"
|
||
msgstr "Dalam contoh ini, lokasi ini memiliki alamat IP berikut:"
|
||
|
||
msgid ""
|
||
"In this guide, we assume that you have successfully deployed an OpenStack "
|
||
"cloud and are able to perform basic operations such as adding images, "
|
||
"booting instances, and attaching volumes."
|
||
msgstr ""
|
||
"Dalam panduan ini, kami mengasumsikan bahwa Anda telah berhasil menggunakan "
|
||
"cloud OpenStack dan dapat melakukan operasi dasar seperti menambahkan image, "
|
||
"mem-boot instance, dan mengkaitkan volume."
|
||
|
||
msgid ""
|
||
"In this instance, having an out-of-band access into nodes running OpenStack "
|
||
"components is a boon. The IPMI protocol is the de facto standard here, and "
|
||
"acquiring hardware that supports it is highly recommended to achieve that "
|
||
"lights-out data center aim."
|
||
msgstr ""
|
||
"Dalam instance ini, memiliki akses out-of-band ke node yang menjalankan "
|
||
"komponen OpenStack adalah suatu anugerah. Protokol IPMI adalah standar de "
|
||
"facto di sini, dan memperoleh perangkat keras yang mendukungnya sangat "
|
||
"disarankan untuk mencapai tujuan pusat data yang padam (lights-out)."
|
||
|
||
msgid ""
|
||
"Industry standards policy governing additional requirements on what type of "
|
||
"cardholder data may or may not be stored and how it is to be protected."
|
||
msgstr ""
|
||
"Kebijakan standar industri yang mengatur persyaratan tambahan tentang jenis "
|
||
"data pemegang kartu yang dapat disimpan atau tidak dan bagaimana data itu "
|
||
"harus dilindungi."
|
||
|
||
msgid "Influencing the Roadmap"
|
||
msgstr "Mempengaruhi Roadmap"
|
||
|
||
msgid "Information Available to You"
|
||
msgstr "Informasi Tersedia untuk Anda"
|
||
|
||
msgid "Injected file content bytes"
|
||
msgstr "Byte konten file yang disuntikkan"
|
||
|
||
msgid "Injected file path bytes"
|
||
msgstr "Byte jalur file yang disuntikkan"
|
||
|
||
msgid "Injected files"
|
||
msgstr "File yang disuntikkan"
|
||
|
||
msgid ""
|
||
"Inside the book sprint room with us each day was our book sprint facilitator "
|
||
"Adam Hyde. Without his tireless support and encouragement, we would have "
|
||
"thought a book of this scope was impossible in five days. Adam has proven "
|
||
"the book sprint method effectively again and again. He creates both tools "
|
||
"and faith in collaborative authoring at `www.booksprints.net <https://www."
|
||
"booksprints.net/>`_."
|
||
msgstr ""
|
||
"Di dalam ruang sprint buku bersama kami setiap hari adalah fasilitator "
|
||
"sprint buku kami, Adam Hyde. Tanpa dukungan dan dorongannya yang tak kenal "
|
||
"lelah, kami akan mengira sebuah buku tentang lingkup ini tidak mungkin dalam "
|
||
"lima hari. Adam telah membuktikan metode sprint buku secara efektif berulang "
|
||
"kali. Ia menciptakan alat dan keyakinan dalam penulisan kolaboratif pada "
|
||
"`www.booksprints.net <https://www.booksprints.net/>`_."
|
||
|
||
msgid "Inspecting API Calls"
|
||
msgstr "Memeriksa Panggilan API"
|
||
|
||
msgid "Inspecting and Recovering Data from Failed Instances"
|
||
msgstr "Memeriksa dan Memulihkan Data dari Instance Gagal"
|
||
|
||
msgid "Install OpenStack command-line clients"
|
||
msgstr "Instal klien command-line OpenStack"
|
||
|
||
msgid "Install the ``keystone`` and ``swift`` clients on your local machine:"
|
||
msgstr "Instal klien ``keystone`` dan ``swift`` di mesin lokal Anda:"
|
||
|
||
msgid "Instance \"ignores\" the response and re-sends the renewal request."
|
||
msgstr ""
|
||
"Instance \"ignores\" respons dan mengirim kembali permintaan pembaruan."
|
||
|
||
msgid ""
|
||
"Instance begins sending a renewal request to ``255.255.255.255`` since it "
|
||
"hasn't heard back from the cloud controller."
|
||
msgstr ""
|
||
"Mesin virtual mulai mengirim permintaan pembaruan ke `` 255.255.255.255`` "
|
||
"karena belum mendapat balasan dari pengendali cloud."
|
||
|
||
msgid "Instance tries to renew IP."
|
||
msgstr "Instance mencoba memperbarui IP."
|
||
|
||
msgid "Instances"
|
||
msgstr "Instance"
|
||
|
||
msgid "Intelligent Alerting"
|
||
msgstr "Peringatan Intelligent"
|
||
|
||
msgid ""
|
||
"Intelligent alerting can be thought of as a form of continuous integration "
|
||
"for operations. For example, you can easily check to see whether the Image "
|
||
"service is up and running by ensuring that the ``glance-api`` and ``glance-"
|
||
"registry`` processes are running or by seeing whether ``glance-api`` is "
|
||
"responding on port 9292."
|
||
msgstr ""
|
||
"Peringatan intelligent dapat dianggap sebagai bentuk integrasi berkelanjutan "
|
||
"untuk operasi. Misalnya, Anda dapat dengan mudah memeriksa untuk melihat "
|
||
"apakah layanan Image sudah berjalan dan berjalan dengan memastikan bahwa "
|
||
"proses ``glance-api`` dan ``glance-registry`` sedang berjalan atau dengan "
|
||
"melihat apakah ``glance-api`` merespons pada port 9292."
|
||
|
||
msgid ""
|
||
"Intelligent alerting takes considerably more time to plan and implement than "
|
||
"the other alerts described in this chapter. A good outline to implement "
|
||
"intelligent alerting is:"
|
||
msgstr ""
|
||
"Peringatan intelligent membutuhkan jauh lebih banyak waktu untuk "
|
||
"merencanakan dan mengimplementasikan daripada peringatan lain yang "
|
||
"dijelaskan dalam bab ini. Outline yang baik untuk menerapkan peringatan "
|
||
"Intelligent adalah:"
|
||
|
||
msgid ""
|
||
"Intended to detect and react appropriately to any incidents that occur. "
|
||
"System and network security monitoring, including intrusion detection and "
|
||
"prevention arrangements, are typically employed to detect attacks on cloud "
|
||
"systems and the supporting communications infrastructure."
|
||
msgstr ""
|
||
"Dimaksudkan untuk mendeteksi dan bereaksi secara tepat terhadap setiap "
|
||
"insiden yang terjadi. Pemantauan keamanan sistem dan jaringan, termasuk "
|
||
"deteksi intrusi dan pengaturan pencegahan, biasanya digunakan untuk "
|
||
"mendeteksi serangan pada sistem cloud dan infrastruktur komunikasi pendukung."
|
||
|
||
msgid "Internal network connectivity"
|
||
msgstr "Konektivitas jaringan internal"
|
||
|
||
msgid ""
|
||
"It is also possible to add project members and adjust the project quotas. "
|
||
"We'll discuss those actions later, but in practice, it can be quite "
|
||
"convenient to deal with all these operations at one time."
|
||
msgstr ""
|
||
"Dimungkinkan juga untuk menambah anggota proyek dan menyesuaikan kuota "
|
||
"proyek. Kami akan membahas tindakan-tindakan itu nanti, tetapi dalam "
|
||
"praktiknya, mungkin cukup nyaman untuk menangani semua operasi ini sekaligus."
|
||
|
||
msgid ""
|
||
"It is possible to watch packets on internal interfaces, but it does take a "
|
||
"little bit of networking gymnastics. First you need to create a dummy "
|
||
"network device that normal Linux tools can see. Then you need to add it to "
|
||
"the bridge containing the internal interface you want to snoop on. Finally, "
|
||
"you need to tell Open vSwitch to mirror all traffic to or from the internal "
|
||
"port onto this dummy port. After all this, you can then run :command:"
|
||
"`tcpdump` on the dummy interface and see the traffic on the internal port."
|
||
msgstr ""
|
||
"Dimungkinkan untuk menonton paket pada antarmuka internal, tetapi dibutuhkan "
|
||
"sedikit senam jaringan. Pertama, Anda perlu membuat perangkat jaringan "
|
||
"tiruan yang bisa dilihat oleh alat Linux normal. Maka Anda perlu "
|
||
"menambahkannya ke jembatan yang berisi antarmuka internal yang ingin Anda "
|
||
"sembunyikan. Terakhir, Anda perlu memberi tahu Open vSwitch untuk "
|
||
"mencerminkan semua lalu lintas ke atau dari port internal ke port dummy ini. "
|
||
"Setelah semua ini, Anda kemudian dapat menjalankan :command: `tcpdump` pada "
|
||
"antarmuka dummy dan melihat lalu lintas di port internal."
|
||
|
||
msgid ""
|
||
"It is quite common for the RabbitMQ service to hang when it is restarted or "
|
||
"stopped. Therefore, it is highly recommended that you manually restart "
|
||
"RabbitMQ on each controller node."
|
||
msgstr ""
|
||
"Sangat umum bagi layanan RabbitMQ untuk hang ketika dinyalakan kembali atau "
|
||
"dihentikan. Oleh karena itu, sangat disarankan agar Anda me-restart RabbitMQ "
|
||
"secara manual pada setiap node pengontrol."
|
||
|
||
msgid ""
|
||
"It turns out the reason that this compute node locked up was a hardware "
|
||
"issue. We removed it from the DAIR cloud and called Dell to have it "
|
||
"serviced. Dell arrived and began working. Somehow or another (or a fat "
|
||
"finger), a different compute node was bumped and rebooted. Great."
|
||
msgstr ""
|
||
"Ternyata alasan bahwa simpul komputasi ini terkunci adalah masalah perangkat "
|
||
"keras. Kami menghapusnya dari cloud DAIR dan memanggil Dell untuk diservis. "
|
||
"Dell tiba dan mulai bekerja. Entah bagaimana atau yang lain (atau jari yang "
|
||
"gemuk), simpul komputasi yang berbeda dihancurkan (bumped) dan di-boot "
|
||
"ulang. Great."
|
||
|
||
msgid ""
|
||
"It was funny to read the report. It was full of people who had some strange "
|
||
"network problem but didn't quite explain it in the same way."
|
||
msgstr ""
|
||
"Lucu membaca laporan itu. Itu penuh dengan orang yang memiliki beberapa "
|
||
"masalah jaringan aneh tetapi tidak cukup menjelaskannya dengan cara yang "
|
||
"sama."
|
||
|
||
msgid ""
|
||
"It's worth mentioning this directory in the context of failed compute nodes. "
|
||
"This directory contains the libvirt KVM file-based disk images for the "
|
||
"instances that are hosted on that compute node. If you are not running your "
|
||
"cloud in a shared storage environment, this directory is unique across all "
|
||
"compute nodes."
|
||
msgstr ""
|
||
"Layak disebutkan direktori ini dalam konteks gagal node komputasi. Direktori "
|
||
"ini berisi image disk berbasis file KVM libvirt untuk instance yang di-host "
|
||
"pada node komputasi itu. Jika Anda tidak menjalankan cloud di lingkungan "
|
||
"penyimpanan bersama, direktori ini unik di semua node komputasi."
|
||
|
||
msgid ""
|
||
"Items to monitor for RabbitMQ include the number of items in each of the "
|
||
"queues and the processing time statistics for the server."
|
||
msgstr ""
|
||
"Item yang dipantau untuk RabbitMQ mencakup jumlah item di setiap antrian dan "
|
||
"statistik waktu pemrosesan untuk server."
|
||
|
||
msgid "Jump to the VM specific chain."
|
||
msgstr "Beralih ke rantai spesifik VM."
|
||
|
||
msgid ""
|
||
"Just as important as a backup policy is a recovery policy (or at least "
|
||
"recovery testing)."
|
||
msgstr ""
|
||
"Sama pentingnya dengan kebijakan cadangan adalah kebijakan pemulihan (atau "
|
||
"setidaknya pengujian pemulihan)."
|
||
|
||
msgid "Key pairs"
|
||
msgstr "Key pairs (pasangan kunci)"
|
||
|
||
msgid "Keystone"
|
||
msgstr "Keystone"
|
||
|
||
msgid ""
|
||
"Keystone is handled a little differently. To modify the logging level, edit "
|
||
"the ``/etc/keystone/logging.conf`` file and look at the ``logger_root`` and "
|
||
"``handler_file`` sections."
|
||
msgstr ""
|
||
"Keystone ditangani sedikit berbeda. Untuk memodifikasi level logging, edit "
|
||
"file ``/etc/keystone/logging.conf`` dan lihat bagian ``logger_root`` dan "
|
||
"``handler_file``."
|
||
|
||
msgid "Keystone services"
|
||
msgstr "Layanan keystone"
|
||
|
||
msgid "Keystone, All nova services"
|
||
msgstr "Keystone, Semua layanan nova"
|
||
|
||
msgid "Keystone, ``nova-api``"
|
||
msgstr "Keystone, ``nova-api``"
|
||
|
||
msgid "Kibana"
|
||
msgstr "Kibana"
|
||
|
||
msgid ""
|
||
"L3-agent router namespaces are named ``qrouter-<router_uuid>``, and dhcp-"
|
||
"agent name spaces are named ``qdhcp-<net_uuid>``. This output shows a "
|
||
"network node with four networks running dhcp-agents, one of which is also "
|
||
"running an l3-agent router. It's important to know which network you need to "
|
||
"be working in. A list of existing networks and their UUIDs can be obtained "
|
||
"by running ``openstack network list`` with administrative credentials."
|
||
msgstr ""
|
||
"Namespace router agen L3 dinamai ``qrouter- <router_uuid> ``, dan space nama "
|
||
"agen dhcp-agent dinamai ``qdhcp- <net_uuid> ``. Output ini menunjukkan node "
|
||
"jaringan dengan empat jaringan yang menjalankan dhcp-agent, salah satunya "
|
||
"juga menjalankan router l3-agent. Sangat penting untuk mengetahui di "
|
||
"jaringan mana Anda perlu bekerja. Daftar jaringan yang ada dan UUIDnya dapat "
|
||
"diperoleh dengan menjalankan ``openstack network list`` dengan kredensial "
|
||
"administratif."
|
||
|
||
msgid "Large instances"
|
||
msgstr "Instance besar"
|
||
|
||
msgid "Launch several neutron ports:"
|
||
msgstr "Luncurkan beberapa port neutron:"
|
||
|
||
msgid "Lay of the Land"
|
||
msgstr "Lay of the Land"
|
||
|
||
msgid "Legal requirements"
|
||
msgstr "Persyaratan legal"
|
||
|
||
msgid ""
|
||
"Like all major system upgrades, your upgrade could fail for one or more "
|
||
"reasons. You can prepare for this situation by having the ability to roll "
|
||
"back your environment to the previous release, including databases, "
|
||
"configuration files, and packages. We provide an example process for rolling "
|
||
"back your environment in :ref:`rolling_back_a_failed_upgrade`."
|
||
msgstr ""
|
||
"Seperti semua upgrade sistem utama, upgrade Anda bisa gagal karena satu atau "
|
||
"beberapa alasan. Anda dapat mempersiapkan diri untuk situasi ini dengan "
|
||
"memiliki kemampuan untuk memutar kembali lingkungan Anda ke rilis "
|
||
"sebelumnya, termasuk database, file konfigurasi, dan paket. Kami memberikan "
|
||
"contoh proses untuk mengembalikan lingkungan Anda di :ref:"
|
||
"`rolling_back_a_failed_upgrade`."
|
||
|
||
msgid ""
|
||
"Limit the total size (in bytes) or number of objects that can be stored in a "
|
||
"single container."
|
||
msgstr ""
|
||
"Batasi ukuran total (dalam byte) atau jumlah objek yang dapat disimpan dalam "
|
||
"satu kontainer."
|
||
|
||
msgid ""
|
||
"Limit the total size (in bytes) that a user has available in the Object "
|
||
"Storage service."
|
||
msgstr ""
|
||
"Batasi ukuran total (dalam byte) yang telah tersedia pengguna di layanan "
|
||
"Object Storage."
|
||
|
||
msgid ""
|
||
"Linux network namespaces are a kernel feature the networking service uses to "
|
||
"support multiple isolated layer-2 networks with overlapping IP address "
|
||
"ranges. The support may be disabled, but it is on by default. If it is "
|
||
"enabled in your environment, your network nodes will run their dhcp-agents "
|
||
"and l3-agents in isolated namespaces. Network interfaces and traffic on "
|
||
"those interfaces will not be visible in the default namespace."
|
||
msgstr ""
|
||
"Namespace jaringan Linux adalah fitur kernel yang digunakan layanan jaringan "
|
||
"untuk mendukung beberapa jaringan layer-2 yang terisolasi dengan rentang "
|
||
"alamat IP yang tumpang tindih. Dukungan mungkin dinonaktifkan, tetapi "
|
||
"diaktifkan secara default. Jika diaktifkan di lingkungan Anda, node jaringan "
|
||
"Anda akan menjalankan agen dhcp dan l3-agen di ruang nama yang terisolasi. "
|
||
"Antarmuka jaringan dan lalu lintas pada antarmuka tersebut tidak akan "
|
||
"terlihat di namespace default."
|
||
|
||
msgid "List the currently set quota values for a tenant, as follows:"
|
||
msgstr ""
|
||
"Daftar nilai kuota yang ditetapkan saat ini untuk tenant, sebagai berikut:"
|
||
|
||
msgid "Log Indexer"
|
||
msgstr "Log Indexer"
|
||
|
||
msgid "Log Pusher"
|
||
msgstr "Log Pusher"
|
||
|
||
msgid "Log in as an administrative user."
|
||
msgstr "Masuk sebagai pengguna administratif."
|
||
|
||
msgid ""
|
||
"Log in to each of the controller nodes for the affected environment, and "
|
||
"check the ``/var/log/rabbitmq`` log files for any reported issues."
|
||
msgstr ""
|
||
"Masuk ke masing-masing node pengontrol untuk lingkungan yang terpengaruh, "
|
||
"dan periksa file log ``/var/log/rabbitmq`` untuk masalah yang dilaporkan."
|
||
|
||
msgid "Log location"
|
||
msgstr "Log location"
|
||
|
||
msgid "Logging"
|
||
msgstr "Logging"
|
||
|
||
msgid "Logging and Monitoring"
|
||
msgstr "Logging dan Pemantauan"
|
||
|
||
msgid ""
|
||
"Logging for horizon is configured in ``/etc/openstack_dashboard/"
|
||
"local_settings.py``. Because horizon is a Django web application, it follows "
|
||
"the `Django Logging framework conventions <https://docs.djangoproject.com/en/"
|
||
"dev/topics/logging/>`_."
|
||
msgstr ""
|
||
"Logging untuk horizon dikonfigurasi dalam ``/etc/openstack_dashboard/"
|
||
"local_settings.py``. Karena horizon adalah aplikasi web Django, ia mengikuti "
|
||
"`Django Logging framework conventions <https://docs.djangoproject.com/en/dev/"
|
||
"topics/logging/>`_."
|
||
|
||
msgid ""
|
||
"Logical separation within your nova deployment for physical isolation or "
|
||
"redundancy."
|
||
msgstr ""
|
||
"Pemisahan logis dalam penyebaran nova Anda untuk isolasi fisik atau "
|
||
"redundansi."
|
||
|
||
msgid ""
|
||
"Logpusher is a pair of Python scripts that first listens to Jenkins build "
|
||
"events, then converts them into Gearman jobs. Gearman provides a generic "
|
||
"application framework to farm out work to other machines or processes that "
|
||
"are better suited to do the work. It allows you to do work in parallel, to "
|
||
"load balance processing, and to call functions between languages. Later, "
|
||
"Logpusher performs Gearman jobs to push log files into logstash. Logstash "
|
||
"indexer reads these log events, filters them to remove unwanted lines, "
|
||
"collapse multiple events together, and parses useful information before "
|
||
"shipping them to ElasticSearch for storage and indexing. Kibana is a "
|
||
"logstash oriented web client for ElasticSearch."
|
||
msgstr ""
|
||
"Logpusher adalah sepasang skrip Python yang pertama kali mendengarkan "
|
||
"Jenkins membuat event, kemudian mengubahnya menjadi pekerjaan Gearman. "
|
||
"Gearman menyediakan kerangka kerja aplikasi generik untuk mengolah pekerjaan "
|
||
"ke mesin lain atau proses yang lebih cocok untuk melakukan pekerjaan itu. "
|
||
"Ini memungkinkan Anda melakukan pekerjaan secara paralel, memuat pemrosesan "
|
||
"keseimbangan, dan memanggil fungsi antar bahasa. Kemudian, Logpusher "
|
||
"melakukan pekerjaan Gearman untuk mendorong file log ke logstash. Logstash "
|
||
"indexer membaca event log ini, memfilternya untuk menghapus baris yang tidak "
|
||
"diinginkan, menggabungkan beberapa kejadian bersama, dan mem-parsing "
|
||
"informasi yang berguna sebelum mengirimkannya ke ElasticSearch untuk "
|
||
"penyimpanan dan pengindeksan. Kibana adalah klien web berorientasi logstash "
|
||
"untuk ElasticSearch."
|
||
|
||
msgid "Logstash"
|
||
msgstr "Logstash"
|
||
|
||
msgid ""
|
||
"Logstash is a high performance indexing and search engine for logs. Logs "
|
||
"from Jenkins test runs are sent to logstash where they are indexed and "
|
||
"stored. Logstash facilitates reviewing logs from multiple sources in a "
|
||
"single test run, searching for errors or particular events within a test "
|
||
"run, and searching for log event trends across test runs."
|
||
msgstr ""
|
||
"Logstash adalah pengindeksan dan mesin pencari kinerja tinggi untuk log. Log "
|
||
"dari uji coba Jenkins dikirim ke logstash tempat mereka diindeks dan "
|
||
"disimpan. Logstash memfasilitasi peninjauan log dari berbagai sumber dalam "
|
||
"satu uji coba, mencari kesalahan atau event tertentu dalam uji coba, dan "
|
||
"mencari tren event log di seluruh uji coba."
|
||
|
||
msgid "Look at your OpenStack service :term:`catalog`:"
|
||
msgstr "Lihatlah layanan OpenStack Anda :term:`catalog`:"
|
||
|
||
msgid ""
|
||
"Look for any errors or traces in the log file. For more information, see :"
|
||
"doc:`ops-logging-monitoring`."
|
||
msgstr ""
|
||
"Cari kesalahan atau jejak dalam file log. Untuk informasi lebih lanjut, "
|
||
"lihat :doc: `ops-logging-monitoring`."
|
||
|
||
msgid "Look for connection issues identified in the log files."
|
||
msgstr "Cari masalah koneksi yang diidentifikasi dalam file log."
|
||
|
||
msgid ""
|
||
"Look for the vnet NIC. You can also reference ``nova.conf`` and look for the "
|
||
"``flat_interface_bridge`` option."
|
||
msgstr ""
|
||
"Carilah vnet NIC. Anda juga dapat mereferensikan ``nova.conf`` dan mencari "
|
||
"opsi ``flat_interface_bridge``."
|
||
|
||
msgid "MIT CSAIL"
|
||
msgstr "MIT CSAIL"
|
||
|
||
msgid ""
|
||
"MTU is maximum transmission unit. It specifies the maximum number of bytes "
|
||
"that the interface accepts for each packet. If two interfaces have two "
|
||
"different MTUs, bytes might get chopped off and weird things happen—such as "
|
||
"random session lockups."
|
||
msgstr ""
|
||
"MTU adalah unit transmisi maksimum. Ini menentukan jumlah maksimum byte yang "
|
||
"diterima antarmuka untuk setiap paket. Jika dua antarmuka memiliki dua MTU "
|
||
"yang berbeda, byte mungkin akan terpotong dan hal-hal aneh terjadi - seperti "
|
||
"penguncian sesi acak."
|
||
|
||
msgid ""
|
||
"Maintaining an OpenStack cloud requires that you manage multiple physical "
|
||
"servers, and this number might grow over time. Because managing nodes "
|
||
"manually is error prone, we strongly recommend that you use a configuration-"
|
||
"management tool. These tools automate the process of ensuring that all your "
|
||
"nodes are configured properly and encourage you to maintain your "
|
||
"configuration information (such as packages and configuration options) in a "
|
||
"version-controlled repository."
|
||
msgstr ""
|
||
"Mempertahankan cloud OpenStack mengharuskan Anda mengelola beberapa server "
|
||
"fisik, dan jumlah ini mungkin bertambah seiring waktu. Karena mengelola node "
|
||
"secara manual rentan kesalahan, kami sangat menyarankan Anda menggunakan "
|
||
"alat manajemen konfigurasi. Alat-alat ini mengotomatiskan proses memastikan "
|
||
"bahwa semua node Anda dikonfigurasi dengan benar dan mendorong Anda untuk "
|
||
"mempertahankan informasi konfigurasi Anda (seperti paket dan opsi "
|
||
"konfigurasi) dalam version-controlled repository."
|
||
|
||
msgid "Maintenance, Failures, and Debugging"
|
||
msgstr "Pemeliharaan, Kegagalan, dan Debugging"
|
||
|
||
msgid ""
|
||
"Make a full database backup of your production data. Since the Kilo release, "
|
||
"database downgrades are not supported, and restoring from backup is the only "
|
||
"method available to retrieve a previous database version."
|
||
msgstr ""
|
||
"Buat cadangan database lengkap dari data produksi Anda. Sejak rilis Kilo, "
|
||
"penurunan versi database tidak didukung, dan memulihkan dari cadangan adalah "
|
||
"satu-satunya metode yang tersedia untuk mengambil versi database sebelumnya."
|
||
|
||
msgid "Make another storage endpoint on the same system"
|
||
msgstr "Buat endpoint penyimpanan lain pada sistem yang sama"
|
||
|
||
msgid "Make sure you are in the ``devstack`` directory:"
|
||
msgstr "Pastikan Anda berada di direktori ``devstack``:"
|
||
|
||
msgid "Make sure you're in the ``devstack`` directory:"
|
||
msgstr "Pastikan Anda berada di direktori ``devstack``:"
|
||
|
||
msgid "Manage repositories"
|
||
msgstr "Kelola repositori"
|
||
|
||
msgid "Management security domains"
|
||
msgstr "Manajemen domain keamanan"
|
||
|
||
msgid "Managing Projects"
|
||
msgstr "Mengelola Proyek"
|
||
|
||
msgid "Managing Projects and Users"
|
||
msgstr "Mengelola Proyek dan Pengguna"
|
||
|
||
msgid "Managing floating IP addresses between instances"
|
||
msgstr "Mengelola alamat IP mengambang antar instance"
|
||
|
||
msgid ""
|
||
"Managing the users for both public and private clouds. The Identity service "
|
||
"allows for LDAP to be part of the authentication process. This may ease user "
|
||
"management if integrating into existing systems."
|
||
msgstr ""
|
||
"Mengelola pengguna untuk cloud publik dan pribadi. Layanan Identity "
|
||
"memungkinkan LDAP menjadi bagian dari proses otentikasi. Ini dapat "
|
||
"memudahkan manajemen pengguna jika berintegrasi ke sistem yang ada."
|
||
|
||
msgid "Manually Disassociating a Floating IP"
|
||
msgstr "Secara Manual Melepaskan IP Mengambang"
|
||
|
||
msgid ""
|
||
"Many OpenStack projects allow for customization of specific features using a "
|
||
"driver architecture. You can write a driver that conforms to a particular "
|
||
"interface and plug it in through configuration. For example, you can easily "
|
||
"plug in a new scheduler for Compute. The existing schedulers for Compute are "
|
||
"feature full and well documented at `Scheduling <https://docs.openstack.org/"
|
||
"ocata/config-reference/compute/schedulers.html>`_. However, depending on "
|
||
"your user's use cases, the existing schedulers might not meet your "
|
||
"requirements. You might need to create a new scheduler."
|
||
msgstr ""
|
||
"Banyak proyek OpenStack memungkinkan penyesuaian fitur tertentu menggunakan "
|
||
"arsitektur driver. Anda dapat menulis driver yang sesuai dengan antarmuka "
|
||
"tertentu dan menghubungkannya melalui konfigurasi. Misalnya, Anda dapat "
|
||
"dengan mudah memasang penjadwal baru untuk Compute. Penjadwal yang ada untuk "
|
||
"Compute adalah fitur lengkap dan didokumentasikan dengan baik di `Scheduling "
|
||
"<https://docs.openstack.org/ocata/config-reference/compute/schedulers."
|
||
"html>`_. Namun, tergantung pada kasus penggunaan pengguna Anda, penjadwal "
|
||
"yang ada mungkin tidak memenuhi persyaratan Anda. Anda mungkin perlu membuat "
|
||
"penjadwal baru."
|
||
|
||
msgid ""
|
||
"Many OpenStack projects implement a driver layer, and each of these drivers "
|
||
"will implement its own configuration options. For example, in OpenStack "
|
||
"Compute (nova), there are various hypervisor drivers implemented—libvirt, "
|
||
"xenserver, hyper-v, and vmware, for example. Not all of these hypervisor "
|
||
"drivers have the same features, and each has different tuning requirements."
|
||
msgstr ""
|
||
"Banyak proyek OpenStack menerapkan lapisan driver, dan masing-masing driver "
|
||
"ini akan menerapkan opsi konfigurasi sendiri. Sebagai contoh, dalam "
|
||
"OpenStack Compute (nova), ada berbagai driver hypervisor yang "
|
||
"diimplementasikan — libvirt, xenserver, hyper-v, dan vmware, misalnya. Tidak "
|
||
"semua driver hypervisor ini memiliki fitur yang sama, dan masing-masing "
|
||
"memiliki persyaratan penyetelan yang berbeda."
|
||
|
||
msgid ""
|
||
"Matching ``gre-<n>`` interfaces to tunnel endpoints is possible by looking "
|
||
"at the Open vSwitch state:"
|
||
msgstr ""
|
||
"Mencocokkan antarmuka ``gre- <n> `` dengan endpoints terowongan dimungkinkan "
|
||
"dengan melihat kondisi Open vSwitch:"
|
||
|
||
msgid "Megabytes of instance RAM allowed per project."
|
||
msgstr "Megabita instance RAM diizinkan per proyek."
|
||
|
||
msgid "Memory"
|
||
msgstr "Memory"
|
||
|
||
msgid "Memory usage"
|
||
msgstr "Memory usage"
|
||
|
||
msgid "Message Service (zaqar)"
|
||
msgstr "Message Service (zaqar)"
|
||
|
||
msgid "Message queue and database services"
|
||
msgstr "Antrian pesan dan layanan basis data"
|
||
|
||
msgid "Metadata items"
|
||
msgstr "Item metadata"
|
||
|
||
msgid "Migrate all instances one by one:"
|
||
msgstr "Migrasikan semua instance satu per satu:"
|
||
|
||
msgid "Monitoring"
|
||
msgstr "Pemantauan"
|
||
|
||
msgid "Monitoring Tools"
|
||
msgstr "Alat Pemantau"
|
||
|
||
msgid ""
|
||
"Monitoring the resource usage and user growth will enable you to know when "
|
||
"to procure. The `Logging and Monitoring <https://docs.openstack.org/"
|
||
"operations-guide/ops-logging-monitoring.html>`_ chapte in the Operations "
|
||
"Guide details some useful metrics."
|
||
msgstr ""
|
||
"Memantau penggunaan sumber daya dan pertumbuhan pengguna akan memungkinkan "
|
||
"Anda mengetahui kapan harus membeli. Bab `Logging and Monitoring <https://"
|
||
"docs.openstack.org/operations-guide/ops-logging-monitoring.html>`_ dalam "
|
||
"Operations Guide merinci beberapa metrik yang berguna."
|
||
|
||
msgid "Monthly"
|
||
msgstr "Bulanan"
|
||
|
||
msgid ""
|
||
"Most countries have legislative and regulatory requirements governing the "
|
||
"storage and management of data in cloud environments. This is particularly "
|
||
"relevant for public, community and hybrid cloud models, to ensure data "
|
||
"privacy and protection for organizations using a third party cloud provider."
|
||
msgstr ""
|
||
"Sebagian besar negara memiliki persyaratan legislatif dan peraturan yang "
|
||
"mengatur penyimpanan dan pengelolaan data di lingkungan cloud. Ini sangat "
|
||
"relevan untuk model cloud publik, komunitas, dan hybrid, untuk memastikan "
|
||
"privasi data dan perlindungan bagi organisasi yang menggunakan penyedia "
|
||
"cloud pihak ketiga."
|
||
|
||
msgid ""
|
||
"Most instances are size m1.medium (two virtual cores, 50 GB of storage)."
|
||
msgstr ""
|
||
"Sebagian besar instance adalah ukuran m1.medium (dua core virtual, 50 GB "
|
||
"penyimpanan)."
|
||
|
||
msgid ""
|
||
"Most services use the convention of writing their log files to "
|
||
"subdirectories of the ``/var/log directory``, as listed in :ref:"
|
||
"`table_log_locations`."
|
||
msgstr ""
|
||
"Sebagian besar layanan menggunakan konvensi penulisan file log mereka ke "
|
||
"subdirektori dari ``/var/log directory``, sebagaimana tercantum dalam :ref:"
|
||
"`table_log_locations`."
|
||
|
||
msgid "Mount the qemu-nbd device."
|
||
msgstr "Pasang (mount) perangkat qemu-nbd."
|
||
|
||
msgid ""
|
||
"Multi-site OpenStack deployments present additional licensing considerations "
|
||
"over and above regular OpenStack clouds, particularly where site licenses "
|
||
"are in use to provide cost efficient access to software licenses. The "
|
||
"licensing for host operating systems, guest operating systems, OpenStack "
|
||
"distributions (if applicable), software-defined infrastructure including "
|
||
"network controllers and storage systems, and even individual applications "
|
||
"need to be evaluated."
|
||
msgstr ""
|
||
"Penyebaran OpenStack multi-situs menghadirkan pertimbangan lisensi tambahan "
|
||
"di atas dan di atas cloud OpenStack biasa, khususnya di mana lisensi situs "
|
||
"digunakan untuk menyediakan akses yang efisien biaya ke lisensi perangkat "
|
||
"lunak. Lisensi untuk sistem operasi host, sistem operasi guest, distribusi "
|
||
"OpenStack (jika ada), infrastruktur yang ditentukan perangkat lunak termasuk "
|
||
"pengontrol jaringan dan sistem penyimpanan, dan bahkan aplikasi individual "
|
||
"perlu dievaluasi."
|
||
|
||
msgid "Multi-site security"
|
||
msgstr "Keamanan multi-situs"
|
||
|
||
msgid "Nagios"
|
||
msgstr "Nagios"
|
||
|
||
msgid ""
|
||
"Nagios alerts you with a `WARNING` when any disk on the compute node is 80 "
|
||
"percent full and `CRITICAL` when 90 percent is full."
|
||
msgstr ""
|
||
"Nagios memberi tahu Anda dengan `WARNING ` saat semua disk pada node "
|
||
"komputasi 80 persen penuh dan` CRITICAL ` saat 90 persen penuh."
|
||
|
||
msgid ""
|
||
"Nagios checks that at least one ``nova-compute`` service is running at all "
|
||
"times."
|
||
msgstr ""
|
||
"Nagios memeriksa bahwa setidaknya satu layanan ``nova-compute`` berjalan "
|
||
"setiap saat."
|
||
|
||
msgid ""
|
||
"Nagios is an open source monitoring service. It is capable of executing "
|
||
"arbitrary commands to check the status of server and network services, "
|
||
"remotely executing arbitrary commands directly on servers, and allowing "
|
||
"servers to push notifications back in the form of passive monitoring. Nagios "
|
||
"has been around since 1999. Although newer monitoring services are "
|
||
"available, Nagios is a tried-and-true systems administration staple."
|
||
msgstr ""
|
||
"Nagios adalah layanan pemantauan sumber terbuka. Ia mampu mengeksekusi "
|
||
"perintah acak (arbitrary) untuk memeriksa status server dan layanan "
|
||
"jaringan, melakukan perintah jarak jauh secara langsung pada server, dan "
|
||
"memungkinkan server untuk mendorong pemberitahuan kembali dalam bentuk "
|
||
"pemantauan pasif. Nagios telah ada sejak 1999. Meskipun layanan pemantauan "
|
||
"yang lebih baru tersedia, Nagios adalah bahan pokok administrasi sistem yang "
|
||
"benar-benar ada."
|
||
|
||
msgid "Name"
|
||
msgstr "Name"
|
||
|
||
msgid "NeCTAR"
|
||
msgstr "NeCTAR"
|
||
|
||
msgid ""
|
||
"Negative or hostile users who would attack or compromise the security of "
|
||
"your deployment regardless of firewalls or security agreements."
|
||
msgstr ""
|
||
"Pengguna negatif atau bermusuhan yang akan menyerang atau membahayakan "
|
||
"keamanan penyebaran Anda terlepas dari firewall atau perjanjian keamanan."
|
||
|
||
msgid "Network Configuration in the Database for nova-network"
|
||
msgstr "Konfigurasi jaringan dalam Database untuk nova-network"
|
||
|
||
msgid "Network I/O"
|
||
msgstr "Network I/O"
|
||
|
||
msgid "Network Inspection"
|
||
msgstr "Inspeksi jaringan"
|
||
|
||
msgid "Network Troubleshooting"
|
||
msgstr "Pemecahan Masalah Jaringan"
|
||
|
||
msgid "Network configuration"
|
||
msgstr "Konfigurasi jaringan"
|
||
|
||
msgid ""
|
||
"Network configuration is a very large topic that spans multiple areas of "
|
||
"this book. For now, make sure that your servers can PXE boot and "
|
||
"successfully communicate with the deployment server."
|
||
msgstr ""
|
||
"Konfigurasi jaringan adalah topik yang sangat besar yang mencakup beberapa "
|
||
"area buku ini. Untuk saat ini, pastikan server Anda dapat melakukan PXE "
|
||
"booting dan berhasil berkomunikasi dengan server deployment."
|
||
|
||
msgid ""
|
||
"Network troubleshooting can be challenging. A network issue may cause "
|
||
"problems at any point in the cloud. Using a logical troubleshooting "
|
||
"procedure can help mitigate the issue and isolate where the network issue "
|
||
"is. This chapter aims to give you the information you need to identify any "
|
||
"issues for ``nova-network`` or OpenStack Networking (neutron) with Linux "
|
||
"Bridge or Open vSwitch."
|
||
msgstr ""
|
||
"Pemecahan masalah jaringan bisa jadi menantang. Masalah jaringan dapat "
|
||
"menyebabkan masalah kapan saja di cloud. Menggunakan prosedur pemecahan "
|
||
"masalah logis dapat membantu mengurangi masalah dan mengisolasi di mana "
|
||
"masalah jaringan berada. Bab ini bertujuan untuk memberi Anda informasi yang "
|
||
"Anda butuhkan untuk mengidentifikasi masalah apa pun untuk ``nova-network`` "
|
||
"atau OpenStack Networking (neutron) dengan Linux Bridge atau Open vSwitch."
|
||
|
||
msgid "Network usage (bandwidth and IP usage)"
|
||
msgstr "Penggunaan jaringan (bandwidth dan penggunaan IP)"
|
||
|
||
msgid "Networking"
|
||
msgstr "Networking (jaringan)"
|
||
|
||
msgid "Networking configuration just for PXE booting"
|
||
msgstr "Konfigurasi jaringan hanya untuk boot PXE"
|
||
|
||
msgid "Networking security"
|
||
msgstr "Keamanan jaringan"
|
||
|
||
msgid "Networking service"
|
||
msgstr "Layanan Networking"
|
||
|
||
msgid ""
|
||
"Networking service - Edit the configuration file and restart the service."
|
||
msgstr "Layanan Networking - Edit file konfigurasi dan restart layanan."
|
||
|
||
msgid "New API Versions"
|
||
msgstr "Versi API Baru"
|
||
|
||
msgid "Next, create ``/etc/rsyslog.d/client.conf`` with the following line:"
|
||
msgstr "Selanjutnya, buat ``/etc/rsyslog.d/client.conf`` dengan baris berikut:"
|
||
|
||
msgid "Next, find the fixed IP entry for that UUID:"
|
||
msgstr "Selanjutnya, cari entri IP tetap untuk UUID itu:"
|
||
|
||
msgid ""
|
||
"Next, manually detach and reattach the volumes, where X is the proper mount "
|
||
"point:"
|
||
msgstr ""
|
||
"Selanjutnya, lepaskan dan pasang kembali volume secara manual, di mana X "
|
||
"adalah titik pemasangan yang tepat:"
|
||
|
||
msgid ""
|
||
"Next, open a new shell to the instance and then ping the external host where "
|
||
"``tcpdump`` is running. If the network path to the external server and back "
|
||
"is fully functional, you see something like the following:"
|
||
msgstr ""
|
||
"Selanjutnya, buka shell baru ke instance dan kemudian ping host eksternal di "
|
||
"mana ``tcpdump`` sedang berjalan. Jika jalur jaringan ke server eksternal "
|
||
"dan kembali berfungsi penuh, Anda melihat sesuatu seperti berikut:"
|
||
|
||
msgid ""
|
||
"Next, physically remove the disk from the server and replace it with a "
|
||
"working disk."
|
||
msgstr ""
|
||
"Selanjutnya, secara fisik menghapus disk dari server dan menggantinya dengan "
|
||
"disk yang berfungsi."
|
||
|
||
msgid "Next, redistribute the ring files to the other nodes:"
|
||
msgstr "Selanjutnya, mendistribusikan kembali file ring ke node lain:"
|
||
|
||
msgid ""
|
||
"Next, the ``libvirtd`` daemon was run on the command line. Finally a helpful "
|
||
"error message: it could not connect to d-bus. As ridiculous as it sounds, "
|
||
"libvirt, and thus ``nova-compute``, relies on d-bus and somehow d-bus "
|
||
"crashed. Simply starting d-bus set the entire chain back on track, and soon "
|
||
"everything was back up and running."
|
||
msgstr ""
|
||
"Selanjutnya, daemon ``libvirtd`` dijalankan pada command line. Akhirnya "
|
||
"muncul pesan kesalahan yang bermanfaat: tidak dapat terhubung ke d-bus. "
|
||
"Kedengarannya konyol, libvirt, dan karenanya ``nova-compute``, bergantung "
|
||
"pada d-bus dan entah bagaimana d-bus jatuh. Cukup memulai d-bus, atur "
|
||
"seluruh rantai kembali ke jalurnya, dan segera semuanya kembali dan berjalan."
|
||
|
||
msgid ""
|
||
"Next, the ``nova`` database contains three tables that store usage "
|
||
"information."
|
||
msgstr ""
|
||
"Selanjutnya, database ``nova`` berisi tiga tabel yang menyimpan informasi "
|
||
"penggunaan."
|
||
|
||
msgid ""
|
||
"Next, the internal bridge, ``br-int``, contains ``int-eth1-br``, which pairs "
|
||
"with ``phy-eth1-br`` to connect to the physical network shown in the "
|
||
"previous bridge, ``patch-tun``, which is used to connect to the GRE tunnel "
|
||
"bridge and the TAP devices that connect to the instances currently running "
|
||
"on the system:"
|
||
msgstr ""
|
||
"Selanjutnya, jembatan internal, ``br-int``, berisi ``int-eth1-br``, yang "
|
||
"berpasangan dengan ``phy-eth1-br`` untuk menyambung ke jaringan fisik yang "
|
||
"ditunjukkan pada jembatan sebelumnya, ``patch-tun``, yang digunakan untuk "
|
||
"menghubungkan ke jembatan terowongan GRE dan perangkat TAP yang terhubung ke "
|
||
"instance yang sedang berjalan pada sistem:"
|
||
|
||
msgid ""
|
||
"Next, the packets from either input go through the integration bridge, again "
|
||
"just as on the compute node."
|
||
msgstr ""
|
||
"Selanjutnya, paket-paket dari salah satu input masuk melalui jembatan "
|
||
"integrasi, lagi seperti pada node komputasi."
|
||
|
||
msgid ""
|
||
"Next, update the nova database to indicate that all instances that used to "
|
||
"be hosted on c01.example.com are now hosted on c02.example.com:"
|
||
msgstr ""
|
||
"Selanjutnya, perbarui database nova untuk menunjukkan bahwa semua instance "
|
||
"yang dulu di-host di c01.example.com sekarang di-host di c02.example.com:"
|
||
|
||
msgid "Node type"
|
||
msgstr "Node type"
|
||
|
||
msgid ""
|
||
"Not all packets have a size of 1500. Running the :command:`ls` command over "
|
||
"SSH might only create a single packets less than 1500 bytes. However, "
|
||
"running a command with heavy output, such as :command:`ps aux` requires "
|
||
"several packets of 1500 bytes."
|
||
msgstr ""
|
||
"Tidak semua paket memiliki ukuran 1500. Menjalankan perintah :command:`ls` "
|
||
"di atas SSH mungkin hanya membuat paket tunggal kurang dari 1500 byte. "
|
||
"Namun, menjalankan perintah dengan output yang berat, seperti :command:`ps "
|
||
"aux` membutuhkan beberapa paket 1500 byte."
|
||
|
||
msgid ""
|
||
"Not entirely network specific, but it contains information about the "
|
||
"instance that is utilizing the ``fixed_ip`` and optional ``floating_ip``."
|
||
msgstr ""
|
||
"Tidak sepenuhnya spesifik jaringan, tetapi berisi informasi tentang instance "
|
||
"yang menggunakan ``fixed_ip`` dan opsional ``floating_ip``."
|
||
|
||
msgid ""
|
||
"Now try the command from Step 10 again and it succeeds. There are no objects "
|
||
"in the container, so there is nothing to list; however, there is also no "
|
||
"error to report."
|
||
msgstr ""
|
||
"Sekarang coba perintah dari Langkah 10 lagi dan berhasil. Tidak ada benda di "
|
||
"dalam kontainer, jadi tidak ada yang perlu didaftar; Namun, tidak ada "
|
||
"kesalahan untuk dilaporkan."
|
||
|
||
msgid "Now you can import a previously backed-up database:"
|
||
msgstr "Sekarang Anda dapat mengimpor basis data yang dicadangkan sebelumnya:"
|
||
|
||
msgid "Now you can refer to your token on the command line as ``$TOKEN``."
|
||
msgstr ""
|
||
"Sekarang Anda dapat merujuk token Anda pada command line sebagai ``$TOKEN``."
|
||
|
||
msgid "Number of Block Storage snapshots allowed per tenant."
|
||
msgstr "Jumlah snapshot Block Storage diizinkan per tenant."
|
||
|
||
msgid "Number of Block Storage volumes allowed per tenant"
|
||
msgstr "Jumlah volume Block Storage yang diizinkan per tenant"
|
||
|
||
msgid "Number of bytes allowed per injected file path."
|
||
msgstr "Jumlah byte yang diizinkan per jalur file yang disuntikkan."
|
||
|
||
msgid "Number of content bytes allowed per injected file."
|
||
msgstr "Jumlah byte konten yang diizinkan per file yang disuntikkan."
|
||
|
||
msgid ""
|
||
"Number of fixed IP addresses allowed per project. This number must be equal "
|
||
"to or greater than the number of allowed instances."
|
||
msgstr ""
|
||
"Jumlah alamat IP tetap yang diizinkan per proyek. Jumlah ini harus sama "
|
||
"dengan atau lebih besar dari jumlah instance yang diizinkan."
|
||
|
||
msgid "Number of floating IP addresses allowed per project."
|
||
msgstr "Jumlah alamat IP mengambang yang diizinkan per proyek."
|
||
|
||
msgid "Number of injected files allowed per project."
|
||
msgstr "Jumlah file yang disuntikkan diizinkan per proyek."
|
||
|
||
msgid "Number of instance cores allowed per project."
|
||
msgstr "Jumlah core instance yang diizinkan per proyek."
|
||
|
||
msgid "Number of instances allowed per project."
|
||
msgstr "Jumlah instance yang diizinkan per proyek."
|
||
|
||
msgid "Number of key pairs allowed per user."
|
||
msgstr "Jumlah pasangan kunci yang diizinkan per pengguna."
|
||
|
||
msgid "Number of metadata items allowed per instance."
|
||
msgstr "Jumlah item metadata diizinkan per instance."
|
||
|
||
msgid "Number of security group rules per project."
|
||
msgstr "Jumlah aturan grup keamanan per proyek."
|
||
|
||
msgid "Number of security groups per project."
|
||
msgstr "Jumlah grup keamanan per proyek."
|
||
|
||
msgid "Number of volume gigabytes allowed per tenant"
|
||
msgstr "Jumlah gigabyte volume yang diizinkan per tenant"
|
||
|
||
msgid ""
|
||
"OK, so where is the MTU issue coming from? Why haven't we seen this in any "
|
||
"other deployment? What's new in this situation? Well, new data center, new "
|
||
"uplink, new switches, new model of switches, new servers, first time using "
|
||
"this model of servers… so, basically everything was new. Wonderful. We toyed "
|
||
"around with raising the MTU at various areas: the switches, the NICs on the "
|
||
"compute nodes, the virtual NICs in the instances, we even had the data "
|
||
"center raise the MTU for our uplink interface. Some changes worked, some "
|
||
"didn't. This line of troubleshooting didn't feel right, though. We shouldn't "
|
||
"have to be changing the MTU in these areas."
|
||
msgstr ""
|
||
"Oke, jadi dari mana datangnya masalah MTU? Mengapa kami belum melihat ini di "
|
||
"penyebaran lain? Apa yang baru dalam situasi ini? Nah, pusat data baru, "
|
||
"uplink baru, switch baru, model switch baru, server baru, pertama kali "
|
||
"menggunakan model server ini ... jadi, pada dasarnya semuanya baru. Hebat. "
|
||
"Kami bermain-main dengan menaikkan MTU di berbagai bidang: sakelar, NIC pada "
|
||
"node komputasi, NIC virtual dalam instance, kami bahkan meminta pusat data "
|
||
"menaikkan MTU untuk antarmuka uplink kami. Beberapa perubahan berhasil, "
|
||
"beberapa tidak. Baris pemecahan masalah (line of troubleshooting) ini "
|
||
"rasanya tidak benar. Kita tidak harus mengubah MTU di area ini."
|
||
|
||
msgid "Object Storage"
|
||
msgstr "Object Storage"
|
||
|
||
msgid "Obtain the tenant ID, as follows:"
|
||
msgstr "Dapatkan ID tenant, sebagai berikut:"
|
||
|
||
msgid ""
|
||
"Oisin Feeley read it, made some edits, and provided emailed feedback right "
|
||
"when we asked."
|
||
msgstr ""
|
||
"Oisin Feeley membacanya, melakukan beberapa pengeditan, dan memberikan umpan "
|
||
"balik melalui email saat kami bertanya."
|
||
|
||
msgid ""
|
||
"On Wednesday night we had a fun happy hour with the Austin OpenStack Meetup "
|
||
"group and Racker Katie Schmidt took great care of our group."
|
||
msgstr ""
|
||
"Pada hari Rabu malam, kami bersenang-senang dengan kelompok OpenStack Meetup "
|
||
"Austin dan Racker Katie Schmidt merawat kelompok kami."
|
||
|
||
msgid ""
|
||
"On all distributions, you must perform some final tasks to complete the "
|
||
"upgrade process."
|
||
msgstr ""
|
||
"Di semua distribusi, Anda harus melakukan beberapa tugas akhir untuk "
|
||
"menyelesaikan proses upgrade."
|
||
|
||
msgid "On all nodes:"
|
||
msgstr "Di semua node:"
|
||
|
||
msgid ""
|
||
"On compute nodes and nodes running ``nova-network``, use the following "
|
||
"command to see information about interfaces, including information about "
|
||
"IPs, VLANs, and whether your interfaces are up:"
|
||
msgstr ""
|
||
"Saat node komputasi dan node menjalankan ``nova-network``, gunakan perintah "
|
||
"berikut untuk melihat informasi tentang antarmuka, termasuk informasi "
|
||
"tentang IP, VLAN, dan apakah antarmuka Anda sudah aktif:"
|
||
|
||
msgid ""
|
||
"On my last day in Kelowna, I was in a conference call from my hotel. In the "
|
||
"background, I was fooling around on the new cloud. I launched an instance "
|
||
"and logged in. Everything looked fine. Out of boredom, I ran :command:`ps "
|
||
"aux` and all of the sudden the instance locked up."
|
||
msgstr ""
|
||
"Pada hari terakhir saya di Kelowna, saya melakukan panggilan konferensi dari "
|
||
"hotel saya. Di latar belakang, aku bermain-main di awan baru. Saya "
|
||
"meluncurkan sebuah instance dan masuk. Semuanya tampak baik-baik saja. "
|
||
"Karena bosan, saya jalankan :command: `ps aux` dan tiba-tiba instancenya "
|
||
"terkunci."
|
||
|
||
msgid "On the Compute node, create the following NRPE configuration:"
|
||
msgstr "Pada simpul Compute, buat konfigurasi NRPE berikut:"
|
||
|
||
msgid "On the compute node, add the following to your NRPE configuration:"
|
||
msgstr "Pada node komputasi, tambahkan berikut ini ke konfigurasi NRPE Anda:"
|
||
|
||
msgid "On the compute node:"
|
||
msgstr "Pada node komputasi:"
|
||
|
||
msgid "On the external server:"
|
||
msgstr "Di server eksternal:"
|
||
|
||
msgid "On the instance:"
|
||
msgstr "Pada instance:"
|
||
|
||
msgid ""
|
||
"On the integration bridge, networks are distinguished using internal VLANs "
|
||
"regardless of how the networking service defines them. This allows instances "
|
||
"on the same host to communicate directly without transiting the rest of the "
|
||
"virtual, or physical, network. These internal VLAN IDs are based on the "
|
||
"order they are created on the node and may vary between nodes. These IDs are "
|
||
"in no way related to the segmentation IDs used in the network definition and "
|
||
"on the physical wire."
|
||
msgstr ""
|
||
"Pada jembatan integrasi, jaringan dibedakan menggunakan VLAN internal "
|
||
"terlepas dari bagaimana layanan jaringan menentukannya. Ini memungkinkan "
|
||
"instance pada host yang sama untuk berkomunikasi secara langsung tanpa "
|
||
"mentransit sisa jaringan (rest of network) virtual atau fisik. ID VLAN "
|
||
"internal ini didasarkan pada urutan pembuatannya pada node dan dapat "
|
||
"bervariasi antar node. ID ini sama sekali tidak terkait dengan ID segmentasi "
|
||
"yang digunakan dalam definisi jaringan dan pada kabel fisik."
|
||
|
||
msgid ""
|
||
"Once nova is sending notifications, install and configure StackTach. "
|
||
"StackTach works for queue consumption and pipeline processing are configured "
|
||
"to read these notifications from RabbitMQ servers and store them in a "
|
||
"database. Users can inquire on instances, requests, and servers by using the "
|
||
"browser interface or command-line tool, `Stacky <https://github.com/"
|
||
"rackerlabs/stacky>`_. Since StackTach is relatively new and constantly "
|
||
"changing, installation instructions quickly become outdated. Refer to the "
|
||
"`StackTach Git repository <https://git.openstack.org/cgit/openstack/"
|
||
"stacktach>`_ for instructions as well as a demostration video. Additional "
|
||
"details on the latest developments can be discovered at the `official page "
|
||
"<http://stacktach.com/>`_"
|
||
msgstr ""
|
||
"Setelah nova mengirim pemberitahuan, instal dan konfigurasikan StackTach. "
|
||
"StackTach berfungsi untuk konsumsi antrian dan pemrosesan pipa "
|
||
"dikonfigurasikan untuk membaca notifikasi ini dari server RabbitMQ dan "
|
||
"menyimpannya dalam database. Pengguna dapat menanyakan instance, permintaan, "
|
||
"dan server dengan menggunakan antarmuka browser atau alat command-line, "
|
||
"`Stacky <https://github.com/rackerlabs/stacky>` _. Karena StackTach relatif "
|
||
"baru dan terus berubah, instruksi instalasi dengan cepat menjadi usang. "
|
||
"Lihat repositori `StackTach Git <https://git.openstack.org/cgit/openstack/"
|
||
"stacktach>` _ untuk instruksi serta video demostration. Rincian tambahan "
|
||
"tentang perkembangan terbaru dapat ditemukan di`official page <http://"
|
||
"stacktach.com/>`_"
|
||
|
||
msgid "Once the files are restored, start everything back up:"
|
||
msgstr "Setelah file dipulihkan, mulai kembali semuanya:"
|
||
|
||
msgid ""
|
||
"Once you have completed the inspection, unmount the mount point and release "
|
||
"the qemu-nbd device:"
|
||
msgstr ""
|
||
"Setelah Anda menyelesaikan inspeksi, lepaskan mount point dan lepaskan "
|
||
"perangkat qemu-nbd:"
|
||
|
||
msgid ""
|
||
"Once you mount the disk file, you should be able to access it and treat it "
|
||
"as a collection of normal directories with files and a directory structure. "
|
||
"However, we do not recommend that you edit or touch any files because this "
|
||
"could change the :term:`access control lists (ACLs) <access control list "
|
||
"(ACL)>` that are used to determine which accounts can perform what "
|
||
"operations on files and directories. Changing ACLs can make the instance "
|
||
"unbootable if it is not already."
|
||
msgstr ""
|
||
"Setelah Anda memasang file disk, Anda harus dapat mengaksesnya dan "
|
||
"memperlakukannya sebagai kumpulan direktori normal dengan file dan struktur "
|
||
"direktori. Namun, kami tidak menyarankan Anda mengedit atau menyentuh file "
|
||
"apa pun karena ini dapat mengubah :term:`access control lists (ACLs) <access "
|
||
"control list (ACL)>` yang digunakan untuk menentukan akun mana yang dapat "
|
||
"melakukan operasi apa pada file dan direktori. Mengubah ACL dapat membuat "
|
||
"instance tidak bisa di-boot jika belum."
|
||
|
||
msgid ""
|
||
"Once you've determined which namespace you need to work in, you can use any "
|
||
"of the debugging tools mention earlier by prefixing the command with ``ip "
|
||
"netns exec <namespace>``. For example, to see what network interfaces exist "
|
||
"in the first qdhcp namespace returned above, do this:"
|
||
msgstr ""
|
||
"Setelah Anda menentukan namespace mana yang Anda butuhkan untuk bekerja, "
|
||
"Anda dapat menggunakan salah satu alat debugging yang disebutkan sebelumnya "
|
||
"dengan mengawali perintah dengan ``ip netns exec <namespace> ``. Misalnya, "
|
||
"untuk melihat antarmuka jaringan apa yang ada di namespace qdhcp pertama "
|
||
"yang dikembalikan di atas, lakukan ini:"
|
||
|
||
msgid ""
|
||
"One cloud controller acted as a gateway to all compute nodes. VlanManager "
|
||
"was used for the network config. This means that the cloud controller and "
|
||
"all compute nodes had a different VLAN for each OpenStack project. We used "
|
||
"the ``-s`` option of ``ping`` to change the packet size. We watched as "
|
||
"sometimes packets would fully return, sometimes they'd only make it out and "
|
||
"never back in, and sometimes the packets would stop at a random point. We "
|
||
"changed ``tcpdump`` to start displaying the hex dump of the packet. We "
|
||
"pinged between every combination of outside, controller, compute, and "
|
||
"instance."
|
||
msgstr ""
|
||
"Satu pengendali cloud bertindak sebagai gateway ke semua node komputasi. "
|
||
"VlanManager digunakan untuk konfigurasi jaringan. Ini berarti bahwa "
|
||
"pengontrol cloud dan semua node komputasi memiliki VLAN yang berbeda untuk "
|
||
"setiap proyek OpenStack. Kami menggunakan opsi ``-s`` dari ``ping`` untuk "
|
||
"mengubah ukuran paket. Kami menyaksikan kadang-kadang paket akan kembali "
|
||
"sepenuhnya, kadang-kadang mereka hanya bisa keluar dan tidak pernah kembali, "
|
||
"dan kadang-kadang paket akan berhenti secara acak. Kami mengubah ``tcpdump`` "
|
||
"untuk mulai menampilkan dump hex paket. Kami melakukan ping di antara setiap "
|
||
"kombinasi luar, pengontrol, komputasi, dan instance."
|
||
|
||
msgid ""
|
||
"One common networking problem is that an instance boots successfully but is "
|
||
"not reachable because it failed to obtain an IP address from dnsmasq, which "
|
||
"is the DHCP server that is launched by the ``nova-network`` service."
|
||
msgstr ""
|
||
"Salah satu masalah jaringan yang umum adalah bahwa instance mem-boot dengan "
|
||
"sukses tetapi tidak dapat dijangkau karena gagal mendapatkan alamat IP dari "
|
||
"dnsmasq, yang merupakan server DHCP yang diluncurkan oleh layanan ``nova-"
|
||
"network``."
|
||
|
||
msgid ""
|
||
"One great, although very in-depth, way of troubleshooting network issues is "
|
||
"to use ``tcpdump``. We recommended using ``tcpdump`` at several points along "
|
||
"the network path to correlate where a problem might be. If you prefer "
|
||
"working with a GUI, either live or by using a ``tcpdump`` capture, check out "
|
||
"`Wireshark <https://www.wireshark.org/>`_."
|
||
msgstr ""
|
||
"Satu cara hebat, meskipun sangat mendalam, cara mengatasi masalah jaringan "
|
||
"adalah dengan menggunakan ``tcpdump``. Kami merekomendasikan penggunaan "
|
||
"``tcpdump`` di beberapa titik di sepanjang jalur jaringan (network path) "
|
||
"untuk menghubungkan di mana masalah mungkin terjadi. Jika Anda lebih suka "
|
||
"bekerja dengan GUI, secara langsung atau dengan menggunakan tangkapan "
|
||
"``tcpdump``, periksa `Wireshark <https://www.wireshark.org/>`_."
|
||
|
||
msgid ""
|
||
"One key element of systems administration that is often overlooked is that "
|
||
"end users are the reason systems administrators exist. Don't go the BOFH "
|
||
"route and terminate every user who causes an alert to go off. Work with "
|
||
"users to understand what they're trying to accomplish and see how your "
|
||
"environment can better assist them in achieving their goals. Meet your users "
|
||
"needs by organizing your users into projects, applying policies, managing "
|
||
"quotas, and working with them."
|
||
msgstr ""
|
||
"Salah satu elemen kunci dari administrasi sistem yang sering diabaikan "
|
||
"adalah bahwa end users (pengguna) menjadi alasan administrator sistem hidup. "
|
||
"Jangan pergi dengan rute BOFH dan menghentikan setiap pengguna yang "
|
||
"menyebabkan peringatan berbunyi. Bekerja dengan pengguna untuk memahami apa "
|
||
"yang mereka coba capai dan melihat bagaimana lingkungan Anda dapat lebih "
|
||
"membantu mereka dalam mencapai tujuan mereka. Memenuhi kebutuhan pengguna "
|
||
"Anda dengan mengatur pengguna Anda ke dalam proyek, menerapkan kebijakan, "
|
||
"mengelola kuota, dan bekerja dengan mereka."
|
||
|
||
msgid ""
|
||
"One last test is to launch a second instance and see whether the two "
|
||
"instances can ping each other. If they can, the issue might be related to "
|
||
"the firewall on the compute node."
|
||
msgstr ""
|
||
"Satu tes terakhir adalah meluncurkan instance kedua dan melihat apakah kedua "
|
||
"instance dapat saling ping. Jika mereka bisa, masalahnya mungkin terkait "
|
||
"dengan firewall pada node komputasi."
|
||
|
||
msgid ""
|
||
"One morning, a compute node failed to run any instances. The log files were "
|
||
"a bit vague, claiming that a certain instance was unable to be started. This "
|
||
"ended up being a red herring because the instance was simply the first "
|
||
"instance in alphabetical order, so it was the first instance that ``nova-"
|
||
"compute`` would touch."
|
||
msgstr ""
|
||
"Suatu pagi, sebuah compute node gagal menjalankan instance. File log agak "
|
||
"kabur, mengklaim bahwa instance tertentu tidak dapat dimulai. Ini akhirnya "
|
||
"menjadi red herring karena instance hanyalah instance pertama dalam urutan "
|
||
"abjad, jadi itu adalah instance pertama yang akan disentuh ``nova-compute``."
|
||
|
||
msgid ""
|
||
"One of the long-time complaints surrounding OpenStack Networking was the "
|
||
"lack of high availability for the layer 3 components. The Juno release "
|
||
"introduced Distributed Virtual Router (DVR), which aims to solve this "
|
||
"problem."
|
||
msgstr ""
|
||
"Salah satu keluhan lama seputar OpenStack Networking adalah kurangnya "
|
||
"ketersediaan tinggi untuk komponen layer 3. Rilis Juno memperkenalkan "
|
||
"Distributed Virtual Router (DVR), yang bertujuan untuk menyelesaikan masalah "
|
||
"ini."
|
||
|
||
msgid ""
|
||
"One of the most requested features since OpenStack began (for components "
|
||
"other than Object Storage, which tends to \"just work\"): easier upgrades. "
|
||
"In all recent releases internal messaging communication is versioned, "
|
||
"meaning services can theoretically drop back to backward-compatible "
|
||
"behavior. This allows you to run later versions of some components, while "
|
||
"keeping older versions of others."
|
||
msgstr ""
|
||
"Salah satu fitur yang paling banyak diminta sejak OpenStack dimulai (untuk "
|
||
"komponen selain Object Storage, yang cenderung \"just work\"): peningkatan "
|
||
"yang lebih mudah. Dalam semua rilis terbaru, komunikasi pesan internal "
|
||
"diversi versi, layanan makna secara teoritis dapat kembali ke perilaku "
|
||
"backward-compatible. Ini memungkinkan Anda untuk menjalankan versi beberapa "
|
||
"komponen yang lebih baru, sambil mempertahankan versi yang lebih lama dari "
|
||
"yang lain."
|
||
|
||
msgid ""
|
||
"One way to plan for cloud controller or storage proxy maintenance is to "
|
||
"simply do it off-hours, such as at 1 a.m. or 2 a.m. This strategy affects "
|
||
"fewer users. If your cloud controller or storage proxy is too important to "
|
||
"have unavailable at any point in time, you must look into high-availability "
|
||
"options."
|
||
msgstr ""
|
||
"Salah satu cara untuk merencanakan pengontrol cloud atau pemeliharaan proksi "
|
||
"penyimpanan adalah dengan melakukannya di luar jam, seperti pada pukul 1 "
|
||
"atau 2 pagi. Strategi ini memengaruhi lebih sedikit pengguna. Jika "
|
||
"pengontrol cloud atau proksi penyimpanan Anda terlalu penting untuk tidak "
|
||
"tersedia kapan pun, Anda harus melihat ke opsi ketersediaan tinggi."
|
||
|
||
msgid ""
|
||
"Open OpenStack Dashboard and launch an instance. If the instance launches, "
|
||
"the issue is resolved."
|
||
msgstr ""
|
||
"Buka OpenStack Dashboard dan luncurkan instance. Jika instance diluncurkan, "
|
||
"masalah teratasi."
|
||
|
||
msgid ""
|
||
"Open vSwitch, as used in the previous OpenStack Networking examples is a "
|
||
"full-featured multilayer virtual switch licensed under the open source "
|
||
"Apache 2.0 license. Full documentation can be found at `the project's "
|
||
"website <http://www.openvswitch.org/>`_. In practice, given the preceding "
|
||
"configuration, the most common issues are being sure that the required "
|
||
"bridges (``br-int``, ``br-tun``, and ``br-ex``) exist and have the proper "
|
||
"ports connected to them."
|
||
msgstr ""
|
||
"Open vSwitch, seperti yang digunakan dalam contoh OpenStack Networking "
|
||
"sebelumnya adalah switch virtual multilayer berfitur lengkap yang "
|
||
"dilisensikan di bawah lisensi open source Apache 2.0. Dokumentasi lengkap "
|
||
"dapat ditemukan di `the project's website <http://www.openvswitch.org/>` _. "
|
||
"Dalam prakteknya, mengingat konfigurasi sebelumnya, masalah yang paling umum "
|
||
"adalah memastikan bahwa jembatan yang diperlukan (``br-int``, ``br-tun``, "
|
||
"dan ``br-ex``) ada dan memiliki hak port yang terhubung dengannya."
|
||
|
||
msgid "OpenStack"
|
||
msgstr "OpenStack"
|
||
|
||
msgid ""
|
||
"OpenStack :term:`Block Storage service <Block Storage service (cinder)>` is "
|
||
"similar to the Image service, so start by checking Identity-related "
|
||
"services, and the back-end storage. Additionally, both the Block Storage and "
|
||
"Image services rely on AMQP and SQL functionality, so consider these when "
|
||
"debugging."
|
||
msgstr ""
|
||
"OpenStack :term:`Block Storage service <Block Storage service (cinder)>` "
|
||
"mirip dengan layanan Image, jadi mulailah dengan memeriksa layanan yang "
|
||
"berhubungan dengan Identity, dan penyimpanan back-end. Selain itu, baik "
|
||
"layanan Block Storage dan Image bergantung pada fungsi AMQP dan SQL, jadi "
|
||
"pertimbangkan ini saat debugging."
|
||
|
||
msgid ""
|
||
"OpenStack :term:`Image service <Image service (glance)>` can be slowed down "
|
||
"by things related to the Identity service, but the Image service itself can "
|
||
"be slowed down if connectivity to the back-end storage in use is slow or "
|
||
"otherwise problematic. For example, your back-end NFS server might have gone "
|
||
"down."
|
||
msgstr ""
|
||
"OpenStack :term:`Image service <Image service (glance)>` dapat diperlambat "
|
||
"oleh hal-hal yang terkait dengan layanan Identity, tetapi layanan Image itu "
|
||
"sendiri dapat diperlambat jika konektivitas ke penyimpanan back-end yang "
|
||
"digunakan lambat atau sebaliknya bermasalah. Sebagai contoh, server NFS back-"
|
||
"end Anda mungkin sudah turun."
|
||
|
||
msgid "OpenStack Block Storage service"
|
||
msgstr "Layanan OpenStack Block Storage"
|
||
|
||
msgid ""
|
||
"OpenStack Compute cells are designed to allow running the cloud in a "
|
||
"distributed fashion without having to use more complicated technologies, or "
|
||
"be invasive to existing nova installations. Hosts in a cloud are partitioned "
|
||
"into groups called *cells*. Cells are configured in a tree. The top-level "
|
||
"cell (\"API cell\") has a host that runs the ``nova-api`` service, but no "
|
||
"``nova-compute`` services. Each child cell runs all of the other typical "
|
||
"``nova-*`` services found in a regular installation, except for the ``nova-"
|
||
"api`` service. Each cell has its own message queue and database service and "
|
||
"also runs ``nova-cells``, which manages the communication between the API "
|
||
"cell and child cells."
|
||
msgstr ""
|
||
"Sel OpenStack Compute dirancang untuk memungkinkan menjalankan cloud secara "
|
||
"terdistribusi tanpa harus menggunakan teknologi yang lebih rumit, atau "
|
||
"invasif dengan instalasi nova yang ada. Host di cloud dipartisi ke dalam "
|
||
"grup yang disebut *cells *. Sel dikonfigurasikan dalam pohon. Sel top-level "
|
||
"(\"API cell\") memiliki host yang menjalankan layanan ``nova-api``, tetapi "
|
||
"tidak ada layanan ``nova-compute``. Setiap sel anak menjalankan semua "
|
||
"layanan ``nova- * `` tipikal lainnya yang ditemukan dalam instalasi reguler, "
|
||
"kecuali untuk layanan ``nova-api``. Setiap sel memiliki antrian pesan dan "
|
||
"layanan basis datanya sendiri dan juga menjalankan ``nova-sel``, yang "
|
||
"mengelola komunikasi antara sel API dan sel anak (child cell)."
|
||
|
||
msgid "OpenStack Compute service"
|
||
msgstr "Layanan OpenStack Compute"
|
||
|
||
msgid "OpenStack Identity service"
|
||
msgstr "Layanan OpenStack Identity"
|
||
|
||
msgid "OpenStack Image service"
|
||
msgstr "Layanan OpenStack Image"
|
||
|
||
msgid ""
|
||
"OpenStack Networking has many more degrees of freedom than ``nova-network`` "
|
||
"does because of its pluggable back end. It can be configured with open "
|
||
"source or vendor proprietary plug-ins that control software defined "
|
||
"networking (SDN) hardware or plug-ins that use Linux native facilities on "
|
||
"your hosts, such as Open vSwitch or Linux Bridge."
|
||
msgstr ""
|
||
"OpenStack Networking memiliki lebih banyak derajat kebebasan daripada ``nova-"
|
||
"network`` karena back end pluggable-nya. Ini dapat dikonfigurasikan dengan "
|
||
"plug-in open source atau vendor proprietary yang mengontrol plug-in atau "
|
||
"hardware software defined networking (SDN) yang menggunakan fasilitas "
|
||
"native Linux pada host Anda, seperti Open vSwitch atau Linux Bridge."
|
||
|
||
msgid "OpenStack Networking service"
|
||
msgstr "Layanan OpenStack Networking"
|
||
|
||
msgid ""
|
||
"OpenStack Object Storage, known as swift when reading the code, is based on "
|
||
"the Python `Paste <https://pypi.org/project/Paste/>`_ framework. The best "
|
||
"introduction to its architecture is on `Read The Docs <https://paste."
|
||
"readthedocs.io/en/latest/>`_. Because of the swift project's use of this "
|
||
"framework, you are able to add features to a project by placing some custom "
|
||
"code in a project's pipeline without having to change any of the core code."
|
||
msgstr ""
|
||
"OpenStack Object Storage, dikenal sebagai swift ketika membaca kode, "
|
||
"didasarkan pada Python `Paste <https://pypi.org/project/Paste/>`_ framework. "
|
||
"Pengantar terbaik untuk arsitekturnya aktif di `Read The Docs <https://paste."
|
||
"readthedocs.io/en/latest/>`_. Karena penggunaan framework proyek swift ini, "
|
||
"Anda dapat menambahkan fitur ke proyek dengan menempatkan beberapa kode "
|
||
"khusus dalam pipa proyek tanpa harus mengubah kode core apa pun."
|
||
|
||
msgid "OpenStack Operations Guide"
|
||
msgstr "Panduan Operasi OpenStack"
|
||
|
||
msgid "OpenStack Specific Resources"
|
||
msgstr "Sumber Daya Tertentu OpenStack"
|
||
|
||
msgid ""
|
||
"OpenStack can be deployed on any hardware supported by an OpenStack "
|
||
"compatible Linux distribution."
|
||
msgstr ""
|
||
"OpenStack dapat digunakan pada perangkat keras apa pun yang didukung oleh "
|
||
"distribusi Linux yang kompatibel dengan OpenStack."
|
||
|
||
msgid ""
|
||
"OpenStack follows a six month release cycle, typically releasing in April/"
|
||
"May and October/November each year. At the start of each cycle, the "
|
||
"community gathers in a single location for a Project Teams Gathering (PTG). "
|
||
"At the PTG, the features for the coming releases are discussed, prioritized, "
|
||
"and planned. The below figure shows an example release cycle, with dates "
|
||
"showing milestone releases, code freeze, and string freeze dates, along with "
|
||
"an example of when the summit occurs. Milestones are interim releases within "
|
||
"the cycle that are available as packages for download and testing. Code "
|
||
"freeze is putting a stop to adding new features to the release. String "
|
||
"freeze is putting a stop to changing any strings within the source code."
|
||
msgstr ""
|
||
"OpenStack mengikuti siklus rilis enam bulan, biasanya dirilis pada bulan "
|
||
"April / Mei dan Oktober / November setiap tahun. Pada awal setiap siklus, "
|
||
"masyarakat berkumpul di satu lokasi untuk Project Teams Gathering (PTG). Di "
|
||
"PTG, fitur untuk rilis mendatang dibahas, diprioritaskan, dan direncanakan. "
|
||
"Gambar di bawah ini menunjukkan contoh siklus rilis, dengan tanggal yang "
|
||
"menunjukkan rilis tonggak, pembekuan kode, dan tanggal pembekuan string, "
|
||
"bersama dengan contoh kapan KTT terjadi. Tonggak sejarah adalah rilis "
|
||
"sementara dalam siklus yang tersedia sebagai paket untuk diunduh dan diuji. "
|
||
"Pembekuan kode (code freeze) menghentikan penambahan fitur baru ke rilis. "
|
||
"Pembekuan string (string freeze) menghentikan perubahan string dalam kode "
|
||
"sumber."
|
||
|
||
msgid ""
|
||
"OpenStack images can often be thought of as \"virtual machine templates.\" "
|
||
"Images can also be standard installation media such as ISO images. "
|
||
"Essentially, they contain bootable file systems that are used to launch "
|
||
"instances."
|
||
msgstr ""
|
||
"Images OpenStack sering dapat dianggap sebagai \"virtual machine templates."
|
||
"\". Images juga bisa menjadi media instalasi standar seperti image ISO. "
|
||
"Pada dasarnya, mereka berisi sistem file bootable yang digunakan untuk "
|
||
"meluncurkan instance."
|
||
|
||
msgid ""
|
||
"OpenStack is designed to be horizontally scalable. Rather than switching to "
|
||
"larger servers, you procure more servers and simply install identically "
|
||
"configured services. Ideally, you scale out and load balance among groups of "
|
||
"functionally identical services (for example, compute nodes or ``nova-api`` "
|
||
"nodes), that communicate on a message bus."
|
||
msgstr ""
|
||
"OpenStack dirancang untuk dapat diskalakan secara horizontal. Daripada "
|
||
"beralih ke server yang lebih besar, Anda membeli lebih banyak server dan "
|
||
"cukup menginstal layanan yang dikonfigurasikan secara identik. Idealnya, "
|
||
"Anda memperbesar dan memuat keseimbangan di antara grup layanan yang identik "
|
||
"secara fungsional (misalnya, komputasi node atau node ``nova-api``), yang "
|
||
"berkomunikasi pada bus pesan (message bus)."
|
||
|
||
msgid ""
|
||
"OpenStack is designed to increase in size in a straightforward manner. "
|
||
"Taking into account the considerations previous mentioned, particularly on "
|
||
"the sizing of the cloud controller, it should be possible to procure "
|
||
"additional compute or object storage nodes as needed. New nodes do not need "
|
||
"to be the same specification or vendor as existing nodes."
|
||
msgstr ""
|
||
"OpenStack dirancang untuk meningkatkan ukuran secara langsung. "
|
||
"Mempertimbangkan pertimbangan yang disebutkan sebelumnya, terutama pada "
|
||
"ukuran pengontrol cloud, harus dimungkinkan untuk mendapatkan node komputasi "
|
||
"atau penyimpanan objek tambahan sesuai kebutuhan. Node baru tidak perlu "
|
||
"spesifikasi atau vendor yang sama dengan node yang ada."
|
||
|
||
msgid ""
|
||
"OpenStack is intended to work well across a variety of installation flavors, "
|
||
"from very small private clouds to large public clouds. To achieve this, the "
|
||
"developers add configuration options to their code that allow the behavior "
|
||
"of the various components to be tweaked depending on your needs. "
|
||
"Unfortunately, it is not possible to cover all possible deployments with the "
|
||
"default configuration values."
|
||
msgstr ""
|
||
"OpenStack dimaksudkan untuk bekerja dengan baik di berbagai flavor "
|
||
"instalasi, dari awan pribadi yang sangat kecil hingga awan publik yang "
|
||
"besar. Untuk mencapai ini, pengembang menambahkan opsi konfigurasi ke kode "
|
||
"mereka yang memungkinkan perilaku berbagai komponen untuk di-tweak "
|
||
"tergantung pada kebutuhan Anda. Sayangnya, tidak mungkin untuk mencakup "
|
||
"semua kemungkinan penyebaran dengan nilai konfigurasi default."
|
||
|
||
msgid ""
|
||
"OpenStack might not do everything you need it to do out of the box. To add a "
|
||
"new feature, you can follow different paths."
|
||
msgstr ""
|
||
"OpenStack mungkin tidak melakukan semua yang Anda butuhkan untuk dilakukan "
|
||
"di luar kotak. Untuk menambahkan fitur baru, Anda dapat mengikuti jalur yang "
|
||
"berbeda."
|
||
|
||
msgid "OpenStack on OpenStack (TripleO)"
|
||
msgstr "OpenStack pada OpenStack (TripleO)"
|
||
|
||
msgid ""
|
||
"OpenStack services use the standard logging levels, at increasing severity: "
|
||
"TRACE, DEBUG, INFO, AUDIT, WARNING, ERROR, and CRITICAL. That is, messages "
|
||
"only appear in the logs if they are more \"severe\" than the particular log "
|
||
"level, with DEBUG allowing all log statements through. For example, TRACE is "
|
||
"logged only if the software has a stack trace, while INFO is logged for "
|
||
"every message including those that are only for information."
|
||
msgstr ""
|
||
"Layanan OpenStack menggunakan level logging standar, dengan tingkat "
|
||
"keparahan (severity) meningkat: TRACE, DEBUG, INFO, AUDIT, WARNING, ERROR, "
|
||
"dan CRITICAL. Artinya, pesan hanya muncul di log jika mereka lebih \"severe"
|
||
"\" daripada tingkat log tertentu, dengan DEBUG memungkinkan semua pernyataan "
|
||
"log dilalui. Misalnya, TRACE dicatat hanya jika perangkat lunak memiliki "
|
||
"jejak tumpukan (stack trace), sementara INFO dicatat untuk setiap pesan "
|
||
"termasuk yang hanya untuk informasi."
|
||
|
||
msgid ""
|
||
"OpenStack truly welcomes your ideas (and contributions) and highly values "
|
||
"feedback from real-world users of the software. By learning a little about "
|
||
"the process that drives feature development, you can participate and perhaps "
|
||
"get the additions you desire."
|
||
msgstr ""
|
||
"OpenStack benar-benar menyambut ide-ide Anda (dan kontribusi) dan sangat "
|
||
"menghargai umpan balik dari pengguna perangkat lunak dunia nyata. Dengan "
|
||
"mempelajari sedikit tentang proses yang mendorong pengembangan fitur, Anda "
|
||
"dapat berpartisipasi dan mungkin mendapatkan tambahan yang Anda inginkan."
|
||
|
||
msgid ""
|
||
"OpenStack's collection of different components interact with each other "
|
||
"strongly. For example, uploading an image requires interaction from ``nova-"
|
||
"api``, ``glance-api``, ``glance-registry``, keystone, and potentially "
|
||
"``swift-proxy``. As a result, it is sometimes difficult to determine exactly "
|
||
"where problems lie. Assisting in this is the purpose of this section."
|
||
msgstr ""
|
||
"Koleksi OpenStack untuk berbagai komponen saling berinteraksi satu sama lain "
|
||
"dengan kuat. Misalnya, mengunggah gambar memerlukan interaksi dari ``nova-"
|
||
"api``, ``glance-api``, ``glance-registry``, keystone, dan berpotensi ``swift-"
|
||
"proxy``. Akibatnya, terkadang sulit untuk menentukan dengan tepat di mana "
|
||
"letak masalah. Membantu dalam hal ini adalah tujuan dari bagian ini."
|
||
|
||
msgid "Option 1"
|
||
msgstr "Opsi 1"
|
||
|
||
msgid "Option 2"
|
||
msgstr "Opsi 2"
|
||
|
||
msgid "Option 3"
|
||
msgstr "Opsi 3"
|
||
|
||
msgid "Optionally, migrate the instances back to their original compute node."
|
||
msgstr "Secara opsional, migrasi instance kembali ke node komputasi aslinya."
|
||
|
||
msgid "Orchestration"
|
||
msgstr "Orchestration"
|
||
|
||
msgid "Orchestration service"
|
||
msgstr "Layanan Orchestration"
|
||
|
||
msgid "Other backup considerations include:"
|
||
msgstr "Pertimbangan cadangan lainnya termasuk:"
|
||
|
||
msgid "Other considerations"
|
||
msgstr "Pertimbangan lainnya"
|
||
|
||
msgid ""
|
||
"Other newer configuration tools include `Juju <https://jujucharms.com/>`_ "
|
||
"and `Salt <http://www.saltstack.com/>`_; and more mature configuration "
|
||
"management tools include `CFEngine <https://cfengine.com/>`_ and `Bcfg2 "
|
||
"<http://bcfg2.org/>`_."
|
||
msgstr ""
|
||
"Alat konfigurasi baru lainnya termasuk `Juju <https://jujucharms.com/>`_ dan "
|
||
"`Salt <http://www.saltstack.com/>`_; dan alat manajemen konfigurasi yang "
|
||
"lebih matang meliputi `CFEngine <https://cfengine.com/>`_ dan `Bcfg2 "
|
||
"<http://bcfg2.org/>`_."
|
||
|
||
msgid ""
|
||
"Other services follow the same process, with their respective directories "
|
||
"and databases."
|
||
msgstr ""
|
||
"Layanan lain mengikuti proses yang sama, dengan direktori dan database "
|
||
"masing-masing."
|
||
|
||
msgid "Output from ``/var/log/nova/nova-api.log`` on :term:`Grizzly`:"
|
||
msgstr "Output dari ``/var/log/nova/nova-api.log`` pada :term:`Grizzly`:"
|
||
|
||
msgid "Output from ``/var/log/nova/nova-api.log`` on :term:`Havana`:"
|
||
msgstr "Output dari ``/var/log/nova/nova-api.log`` pada :term:`Havana`:"
|
||
|
||
msgid "Overlay interconnects for joining separated tenant networks"
|
||
msgstr ""
|
||
"Overlay interkoneksi untuk bergabung dengan jaringan penyewa yang terpisah"
|
||
|
||
msgid ""
|
||
"Packets, now tagged with the external VLAN tag, then exit onto the physical "
|
||
"network via ``eth1``. The Layer2 switch this interface is connected to must "
|
||
"be configured to accept traffic with the VLAN ID used. The next hop for this "
|
||
"packet must also be on the same layer-2 network."
|
||
msgstr ""
|
||
"Paket, sekarang ditandai dengan tag VLAN eksternal, kemudian keluar ke "
|
||
"jaringan fisik melalui ``eth1``. Switch Layer2 yang terhubung dengan "
|
||
"antarmuka ini harus dikonfigurasi untuk menerima lalu lintas dengan ID VLAN "
|
||
"yang digunakan. Hop berikutnya untuk paket ini juga harus berada di jaringan "
|
||
"layer-2 yang sama."
|
||
|
||
msgid ""
|
||
"Partition all drives in the same way in a horizontal fashion, as shown in :"
|
||
"ref:`partition_setup`."
|
||
msgstr ""
|
||
"Partisi semua drive dengan cara yang sama secara horizontal, seperti yang "
|
||
"ditunjukkan pada :ref:`partition_setup`."
|
||
|
||
msgid "Partition setup of drives"
|
||
msgstr "Pengaturan partisi drive"
|
||
|
||
msgid ""
|
||
"Partitioning, which provides greater flexibility for layout of operating "
|
||
"system and swap space, as described below."
|
||
msgstr ""
|
||
"Partisi, yang memberikan fleksibilitas lebih besar untuk tata letak sistem "
|
||
"operasi dan ruang swap, seperti dijelaskan di bawah ini."
|
||
|
||
msgid "Payment Card Industry Data Security Standard (PCI DSS)"
|
||
msgstr "Payment Card Industry Data Security Standard (PCI DSS)"
|
||
|
||
msgid "Perform a backup"
|
||
msgstr "Lakukan pencadangan"
|
||
|
||
msgid ""
|
||
"Perform some cleaning of the environment prior to starting the upgrade "
|
||
"process to ensure a consistent state. For example, instances not fully "
|
||
"purged from the system after deletion might cause indeterminate behavior."
|
||
msgstr ""
|
||
"Lakukan pembersihan lingkungan sebelum memulai proses upgrade untuk "
|
||
"memastikan kondisi yang konsisten. Misalnya, instance yang tidak sepenuhnya "
|
||
"dibersihkan dari sistem setelah penghapusan dapat menyebabkan perilaku tak "
|
||
"tentu."
|
||
|
||
msgid "Perform source NAT on outgoing traffic."
|
||
msgstr "Lakukan NAT sumber pada lalu lintas keluar."
|
||
|
||
msgid "Performance and Optimizing"
|
||
msgstr "Performa dan Mengoptimalkan"
|
||
|
||
msgid ""
|
||
"Performance increased greatly after deleting the old records and my new "
|
||
"deployment continues to behave well."
|
||
msgstr ""
|
||
"Performa meningkat pesat setelah menghapus catatan lama dan penerapan baru "
|
||
"saya terus berperilaku baik."
|
||
|
||
msgid ""
|
||
"Periodic tasks are important to understand because of limitations in the "
|
||
"threading model that OpenStack uses. OpenStack uses cooperative threading in "
|
||
"Python, which means that if something long and complicated is running, it "
|
||
"will block other tasks inside that process from running unless it "
|
||
"voluntarily yields execution to another cooperative thread."
|
||
msgstr ""
|
||
"Tugas berkala penting untuk dipahami karena keterbatasan dalam model "
|
||
"threading yang digunakan OpenStack. OpenStack menggunakan threading "
|
||
"kooperatif dalam Python, yang berarti bahwa jika sesuatu yang panjang dan "
|
||
"rumit berjalan, itu akan memblokir tugas-tugas lain di dalam proses itu dari "
|
||
"berjalan kecuali itu secara sukarela menghasilkan eksekusi ke thread "
|
||
"kooperatif lain."
|
||
|
||
msgid ""
|
||
"Pick a service endpoint from your service catalog, such as compute. Try a "
|
||
"request, for example, listing instances (servers):"
|
||
msgstr ""
|
||
"Pilih endpoint layanan dari katalog layanan Anda, seperti komputasi. Coba "
|
||
"permintaan, misalnya, daftar instance (server):"
|
||
|
||
msgid "Place the tenant ID in a variable:"
|
||
msgstr "Tempatkan ID tenant dalam variabel:"
|
||
|
||
msgid "Planned Maintenance"
|
||
msgstr "Planned Maintenance"
|
||
|
||
msgid "Planning for deploying and provisioning OpenStack"
|
||
msgstr "Merencanakan untuk menggunakan dan menyediakan OpenStack"
|
||
|
||
msgid "Pre-upgrade considerations"
|
||
msgstr "Pertimbangan pra-upgrade"
|
||
|
||
msgid "Pre-upgrade testing environment"
|
||
msgstr "Pra-upgrade lingkungan pengujian"
|
||
|
||
msgid "Prepare any quarterly reports on usage and statistics."
|
||
msgstr "Siapkan laporan triwulanan tentang penggunaan dan statistik."
|
||
|
||
msgid "Prerequisites"
|
||
msgstr "Prasyarat"
|
||
|
||
msgid "Press **Ctrl+A** followed by **0**."
|
||
msgstr "Tekan **Ctrl+A** diikuti oleh **0**."
|
||
|
||
msgid "Press **Ctrl+A** followed by **3** to check the log output."
|
||
msgstr "Tekan **Ctrl+A** diikuti oleh **3** untuk memeriksa output log."
|
||
|
||
msgid ""
|
||
"Press **Ctrl+A** followed by **3** to check the log output. Look at the "
|
||
"swift log statements again, and among the log statements, you'll see the "
|
||
"lines:"
|
||
msgstr ""
|
||
"Tekan **Ctrl+A** diikuti oleh **3** untuk memeriksa output log. Lihatlah "
|
||
"pernyataan log swift lagi, dan di antara laporan log, Anda akan melihat "
|
||
"baris:"
|
||
|
||
msgid "Press **Ctrl+A** followed by **3**."
|
||
msgstr "Tekan **Ctrl+A** diikuti oleh **3**."
|
||
|
||
msgid "Press **Ctrl+A** followed by **9**."
|
||
msgstr "Tekan **Ctrl+A** diikuti oleh **9**."
|
||
|
||
msgid ""
|
||
"Press **Ctrl+A** followed by **N** until you reach the ``n-sch`` screen."
|
||
msgstr ""
|
||
"Tekan **Ctrl+A** diikuti oleh **N** sampai Anda mencapai layar ``n-sch``."
|
||
|
||
msgid "Press **Ctrl+C** to kill the service."
|
||
msgstr "Tekan **Ctrl+C** untuk membunuh layanan."
|
||
|
||
msgid "Press **Enter** to run it."
|
||
msgstr "Tekan **Enter** untuk menjalankannya."
|
||
|
||
msgid "Press **Up Arrow** to bring up the last command."
|
||
msgstr "Tekan **Up Arrow** untuk memunculkan perintah terakhir."
|
||
|
||
msgid "Press Enter to run it."
|
||
msgstr "Tekan Enter untuk menjalankannya."
|
||
|
||
msgid "Press **Ctrl+A** followed by **0**."
|
||
msgstr "Teken **Ctrl+A** diikuti oleh **0**."
|
||
|
||
msgid "Prevent DHCP Spoofing by VM."
|
||
msgstr "Mencegah Spoofing DHCP oleh VM."
|
||
|
||
msgid "Preventive controls:"
|
||
msgstr "Kontrol pencegahan (preventive):"
|
||
|
||
msgid ""
|
||
"Previously, all services had an availability zone. Currently, only the "
|
||
"``nova-compute`` service has its own availability zone. Services such as "
|
||
"``nova-scheduler``, ``nova-network``, and ``nova-conductor`` have always "
|
||
"spanned all availability zones."
|
||
msgstr ""
|
||
"Sebelumnya, semua layanan memiliki zona ketersediaan. Saat ini, hanya "
|
||
"layanan ``nova-compute`` yang memiliki zona ketersediaannya sendiri. Layanan "
|
||
"seperti ``nova-scheduler``, ``nova-network``, dan ``nova-conductor`` selalu "
|
||
"membentang semua zona ketersediaan."
|
||
|
||
msgid ""
|
||
"Prior to the steps below, an asymmetric keypair and certificate must be "
|
||
"generated. In this example, these are called private_key.pem and new_cert."
|
||
"crt, respectively, and both reside in the current directory. Also note that "
|
||
"the image in this example is cirros-0.3.5-x86_64-disk.img, but any image can "
|
||
"be used."
|
||
msgstr ""
|
||
"Sebelum langkah-langkah di bawah ini, asymmetric keypair dan certificate "
|
||
"harus dibuat. Dalam contoh ini, masing-masing disebut private_key.pem dan "
|
||
"new_cert.crt, dan keduanya berada di direktori saat ini. Perhatikan juga "
|
||
"bahwa image dalam contoh ini adalah cirros-0.3.5-x86_64-disk.img, tetapi "
|
||
"image apa pun dapat digunakan."
|
||
|
||
msgid "Priority"
|
||
msgstr "Priority"
|
||
|
||
msgid ""
|
||
"Privacy and security are spread over different industry-specific laws and "
|
||
"regulations:"
|
||
msgstr ""
|
||
"Privasi dan keamanan tersebar di berbagai undang-undang dan peraturan khusus "
|
||
"industri:"
|
||
|
||
msgid "Process Monitoring"
|
||
msgstr "Pemantauan Proses"
|
||
|
||
msgid ""
|
||
"Profit. You can now see traffic on ``patch-tun`` by running :command:"
|
||
"`tcpdump -i snooper0`."
|
||
msgstr ""
|
||
"Profit. Anda sekarang dapat melihat lalu lintas di ``patch-tun`` dengan "
|
||
"menjalankan :command:`tcpdump -i snooper0`."
|
||
|
||
msgid "Projects or Tenants?"
|
||
msgstr "Proyek atau Penyewa?"
|
||
|
||
msgid "Property name"
|
||
msgstr "Nama properti"
|
||
|
||
msgid "Provision an instance"
|
||
msgstr "Memberikan instance"
|
||
|
||
msgid "Public network connectivity for user virtual machines"
|
||
msgstr "Konektivitas jaringan publik untuk mesin virtual pengguna"
|
||
|
||
msgid "Public security domains"
|
||
msgstr "Domain keamanan publik"
|
||
|
||
msgid ""
|
||
"Put the image ID for the only installed image into an environment variable:"
|
||
msgstr ""
|
||
"Masukkan ID image untuk satu-satunya image yang diinstal ke dalam variabel "
|
||
"lingkungan:"
|
||
|
||
msgid "Python"
|
||
msgstr "Python"
|
||
|
||
msgid "Quarterly"
|
||
msgstr "Triwulanan"
|
||
|
||
msgid "Quota"
|
||
msgstr "Kuota"
|
||
|
||
msgid "Quotas"
|
||
msgstr "Kuota"
|
||
|
||
msgid ""
|
||
"RAID is not used in this simplistic one-drive setup because generally for "
|
||
"production clouds, you want to ensure that if one disk fails, another can "
|
||
"take its place. Instead, for production, use more than one disk. The number "
|
||
"of disks determine what types of RAID arrays to build."
|
||
msgstr ""
|
||
"RAID tidak digunakan dalam pengaturan satu drive yang sederhana ini karena "
|
||
"umumnya untuk cloud produksi, Anda ingin memastikan bahwa jika satu disk "
|
||
"gagal, disk lain dapat menggantikannya. Sebagai gantinya, untuk produksi, "
|
||
"gunakan lebih dari satu disk. Jumlah disk menentukan jenis array RAID yang "
|
||
"akan dibuat."
|
||
|
||
msgid "RAM"
|
||
msgstr "RAM"
|
||
|
||
msgid "RabbitMQ Web Management Interface or rabbitmqctl"
|
||
msgstr "RabbitMQ Web Management Interface atau rabbitmqctl"
|
||
|
||
msgid "RabbitMQ alerts"
|
||
msgstr "Peringatan RabbitMQ"
|
||
|
||
msgid "RabbitMQ service hangs"
|
||
msgstr "Layanan RabbitMQ hang"
|
||
|
||
msgid "RabbitMQ troubleshooting"
|
||
msgstr "Pemecahan masalah RabbitMQ"
|
||
|
||
msgid ""
|
||
"Read through the JSON response to get a feel for how the catalog is laid out."
|
||
msgstr "Bacalah respons JSON untuk merasakan bagaimana katalog disusun."
|
||
|
||
msgid "Reading the Logs"
|
||
msgstr "Membaca Log"
|
||
|
||
msgid "Rebooting a Cloud Controller or Storage Proxy"
|
||
msgstr "Reboot Pengontrol Cloud atau Proksi Penyimpanan"
|
||
|
||
msgid "Rebooting a Storage Node"
|
||
msgstr "Rebooting Storage Node"
|
||
|
||
msgid "Recovering Backups"
|
||
msgstr "Memulihkan Cadangan"
|
||
|
||
msgid ""
|
||
"Recovering backups is a fairly simple process. To begin, first ensure that "
|
||
"the service you are recovering is not running. For example, to do a full "
|
||
"recovery of ``nova`` on the cloud controller, first stop all ``nova`` "
|
||
"services:"
|
||
msgstr ""
|
||
"Memulihkan cadangan adalah proses yang cukup sederhana. Untuk memulai, "
|
||
"pertama pastikan bahwa layanan yang Anda pulihkan tidak berjalan. Misalnya, "
|
||
"untuk melakukan pemulihan penuh ``nova`` pada pengontrol cloud, pertama-tama "
|
||
"hentikan semua layanan ``nova``:"
|
||
|
||
msgid ""
|
||
"Reduce the consequences of an incident, normally by limiting the damage. "
|
||
"They come into effect during or after an incident. Restoring system backups "
|
||
"in order to rebuild a compromised system is an example of a corrective "
|
||
"control."
|
||
msgstr ""
|
||
"Kurangi konsekuensi dari suatu insiden, biasanya dengan membatasi kerusakan. "
|
||
"Mereka mulai berlaku selama atau setelah suatu insiden. Mengembalikan "
|
||
"cadangan sistem untuk membangun kembali sistem yang dikompromikan adalah "
|
||
"contoh dari kontrol korektif."
|
||
|
||
msgid ""
|
||
"Refer to the following upgrade notes for information on upgrading specific "
|
||
"OpenStack services:"
|
||
msgstr ""
|
||
"Lihat catatan upgrade berikut untuk informasi tentang upgrade layanan "
|
||
"OpenStack tertentu:"
|
||
|
||
msgid ""
|
||
"Regardless of the overcommit ratio, an instance can not be placed on any "
|
||
"physical node with fewer raw (pre-overcommit) resources than instance flavor "
|
||
"requires."
|
||
msgstr ""
|
||
"Terlepas dari rasio overcommit, sebuah instance tidak dapat ditempatkan pada "
|
||
"setiap node fisik dengan sumber daya (pre-overcommit) mentah yang lebih "
|
||
"sedikit daripada yang dibutuhkan oleh instance flavor."
|
||
|
||
msgid ""
|
||
"Regardless of which AMQP broker you use, such as RabbitMQ, there are common "
|
||
"issues which not only slow down operations, but can also cause real "
|
||
"problems. Sometimes messages queued for services stay on the queues and are "
|
||
"not consumed. This can be due to dead or stagnant services and can be "
|
||
"commonly cleared up by either restarting the AMQP-related services or the "
|
||
"OpenStack service in question."
|
||
msgstr ""
|
||
"Terlepas dari broker AMQP mana yang Anda gunakan, seperti RabbitMQ, ada "
|
||
"masalah umum yang tidak hanya memperlambat operasi, tetapi juga dapat "
|
||
"menyebabkan masalah nyata. Terkadang pesan yang antri untuk layanan tetap "
|
||
"berada di antrian dan tidak digunakan. Ini bisa disebabkan oleh layanan mati "
|
||
"atau stagnan dan biasanya dapat diselesaikan dengan me-restart layanan "
|
||
"terkait AMQP atau layanan OpenStack yang bersangkutan."
|
||
|
||
msgid "Regions"
|
||
msgstr "Regions"
|
||
|
||
msgid "Remote management"
|
||
msgstr "Manajemen jarak jauh"
|
||
|
||
msgid "Remove all packages."
|
||
msgstr "Hapus semua paket."
|
||
|
||
msgid "Remove databases."
|
||
msgstr "Hapus database."
|
||
|
||
msgid "Remove remaining files."
|
||
msgstr "Hapus file yang tersisa."
|
||
|
||
msgid "Remove the repository for the previous release packages."
|
||
msgstr "Hapus repositori untuk paket rilis sebelumnya."
|
||
|
||
msgid "Repeat steps 7-8."
|
||
msgstr "Ulangi langkah 7-8."
|
||
|
||
msgid "Replacement of Open vSwitch Plug-in with Modular Layer 2"
|
||
msgstr "Penggantian Open vSwitch Plug-in dengan Modular Layer 2"
|
||
|
||
msgid "Replacing Components"
|
||
msgstr "Mengganti Komponen"
|
||
|
||
msgid "Replacing a Swift Disk"
|
||
msgstr "Mengganti Swift Disk"
|
||
|
||
msgid "Resource Alerting"
|
||
msgstr "Peringatan Sumberdaya"
|
||
|
||
msgid ""
|
||
"Resource alerting provides notifications when one or more resources are "
|
||
"critically low. While the monitoring thresholds should be tuned to your "
|
||
"specific OpenStack environment, monitoring resource usage is not specific to "
|
||
"OpenStack at all—any generic type of alert will work fine."
|
||
msgstr ""
|
||
"Peringatan sumber daya memberikan pemberitahuan ketika satu atau beberapa "
|
||
"sumber daya sangat rendah. Sementara ambang pemantauan harus disesuaikan "
|
||
"dengan lingkungan OpenStack spesifik Anda, pemantauan penggunaan sumber daya "
|
||
"sama sekali tidak khusus untuk OpenStack — semua jenis peringatan umum akan "
|
||
"berfungsi dengan baik."
|
||
|
||
msgid "Resources"
|
||
msgstr "Sumber daya"
|
||
|
||
msgid ""
|
||
"Resources such as memory, disk, and CPU are generic resources that all "
|
||
"servers (even non-OpenStack servers) have and are important to the overall "
|
||
"health of the server. When dealing with OpenStack specifically, these "
|
||
"resources are important for a second reason: ensuring that enough are "
|
||
"available to launch instances. There are a few ways you can see OpenStack "
|
||
"resource usage. The first is through the :command:`nova` command:"
|
||
msgstr ""
|
||
"Sumber daya seperti memori, disk, dan CPU adalah sumber daya generik yang "
|
||
"dimiliki semua server (bahkan server non-OpenStack) dan penting bagi "
|
||
"kesehatan server secara keseluruhan. Ketika berhadapan dengan OpenStack "
|
||
"secara khusus, sumber daya ini penting untuk alasan kedua: memastikan bahwa "
|
||
"cukup tersedia untuk meluncurkan instance. Ada beberapa cara Anda dapat "
|
||
"melihat penggunaan sumber daya OpenStack. Yang pertama adalah melalui "
|
||
"perintah :command:`nova` :"
|
||
|
||
msgid "Restart the RabbitMQ service on all of the controller nodes:"
|
||
msgstr "Restart layanan RabbitMQ di semua node pengontrol:"
|
||
|
||
msgid ""
|
||
"Restart the RabbitMQ service on the first controller node. The :command:"
|
||
"`service rabbitmq-server restart` command may not work in certain "
|
||
"situations, so it is best to use:"
|
||
msgstr ""
|
||
"Restart layanan RabbitMQ pada node pengontrol pertama. Perintah :command:"
|
||
"`service rabbitmq-server restart` mungkin tidak berfungsi dalam situasi "
|
||
"tertentu, jadi yang terbaik adalah menggunakan: "
|
||
|
||
msgid ""
|
||
"Restart the ``swift proxy`` service to make swift use your middleware. Start "
|
||
"by switching to the ``swift-proxy`` screen:"
|
||
msgstr ""
|
||
"Mulai ulang layanan ``swift proxy`` untuk menjadikan swift menggunakan "
|
||
"middleware Anda. Mulailah dengan beralih ke layar ``swift-proxy``:"
|
||
|
||
msgid ""
|
||
"Restart the nova scheduler service to make nova use your scheduler. Start by "
|
||
"switching to the ``n-sch`` screen:"
|
||
msgstr ""
|
||
"Mulai ulang layanan penjadwal nova untuk membuat nova menggunakan penjadwal "
|
||
"Anda. Mulailah dengan beralih ke layar (screen) ``n-sch``:"
|
||
|
||
msgid "Restore databases from backup."
|
||
msgstr "Restore databases dari backup."
|
||
|
||
msgid ""
|
||
"Restore databases from the ``RELEASE_NAME-db-backup.sql`` backup file that "
|
||
"you created with the :command:`mysqldump` command during the upgrade process:"
|
||
msgstr ""
|
||
"Pulihkan basis data dari file cadangan ``RELEASE_NAME-db-backup.sql`` yang "
|
||
"Anda buat dengan perintah :command:`mysqldump` selama proses upgrade:"
|
||
|
||
msgid "Resume the instance using :command:`virsh`:"
|
||
msgstr "Lanjutkan instance menggunakan :command:`virsh`:"
|
||
|
||
msgid "Resume the instance."
|
||
msgstr "Lanjutkan instance."
|
||
|
||
msgid "Retrieve image for upload"
|
||
msgstr "Ambil image untuk diunggah"
|
||
|
||
msgid ""
|
||
"Reverse the direction to see the path of a ping reply. From this path, you "
|
||
"can see that a single packet travels across four different NICs. If a "
|
||
"problem occurs with any of these NICs, a network issue occurs."
|
||
msgstr ""
|
||
"Balikkan arah (reverse) untuk melihat jalur balasan ping. Dari jalur ini, "
|
||
"Anda dapat melihat bahwa satu paket bergerak melintasi empat NIC yang "
|
||
"berbeda. Jika masalah terjadi dengan salah satu NIC ini, masalah jaringan "
|
||
"terjadi."
|
||
|
||
msgid "Review and plan any major OpenStack upgrades."
|
||
msgstr "Tinjau dan rencanakan setiap upgrade OpenStack utama."
|
||
|
||
msgid "Review and plan any necessary cloud additions."
|
||
msgstr "Tinjau dan rencanakan semua penambahan awan yang diperlukan."
|
||
|
||
msgid "Review common actions in your cloud."
|
||
msgstr "Tinjau tindakan umum di cloud Anda."
|
||
|
||
msgid ""
|
||
"Review the component's configuration file to see how each OpenStack "
|
||
"component accesses its corresponding database. Look for a ``connection`` "
|
||
"option. The following command uses ``grep`` to display the SQL connection "
|
||
"string for nova, glance, cinder, and keystone:"
|
||
msgstr ""
|
||
"Tinjau file konfigurasi komponen untuk melihat bagaimana setiap komponen "
|
||
"OpenStack mengakses database terkait. Cari opsi ``connection``. Perintah "
|
||
"berikut menggunakan ``grep`` untuk menampilkan string koneksi SQL untuk "
|
||
"nova, glance, cinder, dan keystone:"
|
||
|
||
msgid "Review usage and trends over the past quarter."
|
||
msgstr "Tinjau penggunaan dan tren selama kuartal terakhir."
|
||
|
||
msgid "Roll back configuration files."
|
||
msgstr "Roll back file konfigurasi."
|
||
|
||
msgid "Roll back packages."
|
||
msgstr "Roll backpaket."
|
||
|
||
msgid "Roll these tests into an alerting system."
|
||
msgstr "Gulirkan tes ini ke sistem peringatan."
|
||
|
||
msgid "Rolling back a failed upgrade"
|
||
msgstr "Mengembalikan upgrade yang gagal"
|
||
|
||
msgid ""
|
||
"Rolling back your environment should be the final course of action since you "
|
||
"are likely to lose any data added since the backup."
|
||
msgstr ""
|
||
"Mengembalikan lingkungan Anda harus menjadi tindakan terakhir karena Anda "
|
||
"kemungkinan kehilangan data yang ditambahkan sejak cadangan."
|
||
|
||
msgid "Routing through or avoiding specific networks"
|
||
msgstr "Routing melalui atau menghindari jaringan tertentu"
|
||
|
||
msgid ""
|
||
"Run the :command:`openstack port set` command to remove the port from the "
|
||
"instance:"
|
||
msgstr ""
|
||
"Jalankan perintah :command:`openstack port set` untuk menghapus port dari "
|
||
"instance:"
|
||
|
||
msgid ""
|
||
"Run the :command:`rabbitmqctl status` to view the current file descriptor "
|
||
"limits:"
|
||
msgstr ""
|
||
"Jalankan :command:`rabbitmqctl status` untuk melihat batas deskriptor file "
|
||
"saat ini:"
|
||
|
||
msgid "Run the following command to view the current iptables configuration:"
|
||
msgstr "Jalankan perintah berikut untuk melihat konfigurasi iptables saat ini:"
|
||
|
||
msgid "Run the following command to view the properties of existing images:"
|
||
msgstr "Jalankan perintah berikut untuk melihat properti image yang ada:"
|
||
|
||
msgid "Run this on the command line of the following areas:"
|
||
msgstr "Jalankan ini pada command line area berikut:"
|
||
|
||
msgid "Running Daemons on the CLI"
|
||
msgstr "Menjalankan Daemon di CLI"
|
||
|
||
msgid "Running Instances"
|
||
msgstr "Menjalankan Instance"
|
||
|
||
msgid "SQL back end"
|
||
msgstr "SQL back end"
|
||
|
||
msgid "Save the configuration files on all nodes. For example:"
|
||
msgstr "Simpan file konfigurasi di semua node. Sebagai contoh:"
|
||
|
||
msgid "Scalable Hardware"
|
||
msgstr "Perangkat keras yang dapat diskalakan"
|
||
|
||
msgid "Scheduler Improvements"
|
||
msgstr "Perbaikan Penjadwal"
|
||
|
||
msgid "Scheduling to hosts with trusted hardware support."
|
||
msgstr "Penjadwalan ke host dengan dukungan perangkat keras tepercaya."
|
||
|
||
msgid ""
|
||
"Secondly, DAIR's shared ``/var/lib/nova/instances`` directory contributed to "
|
||
"the problem. Since all compute nodes have access to this directory, all "
|
||
"compute nodes periodically review the \\_base directory. If there is only "
|
||
"one instance using an image, and the node that the instance is on is down "
|
||
"for a few minutes, it won't be able to mark the image as still in use. "
|
||
"Therefore, the image seems like it's not in use and is deleted. When the "
|
||
"compute node comes back online, the instance hosted on that node is unable "
|
||
"to start."
|
||
msgstr ""
|
||
"Kedua, direktori ``/var/lib/nova/instances``` bersama DAIR berkontribusi "
|
||
"pada masalah. Karena semua node komputasi memiliki akses ke direktori ini, "
|
||
"semua node komputasi secara berkala meninjau direktori \\ _base. Jika hanya "
|
||
"ada satu instance menggunakan image, dan simpul yang dihidupkan instance "
|
||
"turun selama beberapa menit, itu tidak akan dapat menandai image sebagai "
|
||
"masih digunakan. Oleh karena itu, image sepertinya tidak digunakan dan "
|
||
"dihapus. Ketika node komputasi kembali online, instance yang dihosting pada "
|
||
"node itu tidak dapat memulai."
|
||
|
||
msgid ""
|
||
"Securing a multi-site OpenStack installation brings several challenges. "
|
||
"Tenants may expect a tenant-created network to be secure. In a multi-site "
|
||
"installation the use of a non-private connection between sites may be "
|
||
"required. This may mean that traffic would be visible to third parties and, "
|
||
"in cases where an application requires security, this issue requires "
|
||
"mitigation. In these instances, install a VPN or encrypted connection "
|
||
"between sites to conceal sensitive traffic."
|
||
msgstr ""
|
||
"Mengamankan instalasi OpenStack multi-situs membawa beberapa tantangan. "
|
||
"Penyewa dapat mengharapkan jaringan yang dibuat penyewa aman. Dalam "
|
||
"instalasi multi-situs, penggunaan koneksi non-pribadi antara situs mungkin "
|
||
"diperlukan. Ini mungkin berarti bahwa lalu lintas akan terlihat oleh pihak "
|
||
"ketiga dan, dalam kasus di mana aplikasi membutuhkan keamanan, masalah ini "
|
||
"membutuhkan mitigasi. Dalam hal ini, instal VPN atau koneksi terenkripsi "
|
||
"antara situs untuk menyembunyikan lalu lintas sensitif."
|
||
|
||
msgid "Security Configuration for Compute, Networking, and Storage"
|
||
msgstr "Konfigurasi Keamanan untuk Komputasi, Jaringan, dan Penyimpanan"
|
||
|
||
msgid ""
|
||
"Security breach policies governing the ways to notify individuals through "
|
||
"cloud provider's systems or other means if their personal data gets "
|
||
"compromised in any way."
|
||
msgstr ""
|
||
"Kebijakan pelanggaran keamanan yang mengatur cara untuk memberi tahu "
|
||
"individu melalui sistem penyedia cloud atau cara lain jika data pribadi "
|
||
"mereka dikompromikan dengan cara apa pun."
|
||
|
||
msgid "Security domains"
|
||
msgstr "Domain keamanan"
|
||
|
||
msgid "Security domains include:"
|
||
msgstr "Domain keamanan meliputi:"
|
||
|
||
msgid "Security group rules"
|
||
msgstr "Aturan grup keamanan"
|
||
|
||
msgid "Security groups"
|
||
msgstr "Grup keamanan"
|
||
|
||
msgid "Security requirements"
|
||
msgstr "Persyaratan keamanan"
|
||
|
||
msgid "Segregating your cloud"
|
||
msgstr "Memisahkan cloud Anda"
|
||
|
||
msgid ""
|
||
"Segregating your cloud is needed when users require different regions for "
|
||
"legal considerations for data storage, redundancy across earthquake fault "
|
||
"lines, or for low-latency API calls. It can be segregated by *cells*, "
|
||
"*regions*, *availability zones*, or *host aggregates*."
|
||
msgstr ""
|
||
"Memisahkan cloud Anda diperlukan ketika pengguna memerlukan wilayah yang "
|
||
"berbeda untuk pertimbangan hukum untuk penyimpanan data, redundansi di "
|
||
"seluruh jalur gangguan gempa bumi, atau untuk panggilan API latensi rendah. "
|
||
"Ini dapat dipisahkan oleh *cells*, *regions*, *availability zones*, atau "
|
||
"*host aggregates*."
|
||
|
||
msgid "Select the :guilabel:`Identity` tab in the left navigation bar."
|
||
msgstr "Pilih tab :guilabel:`Identity` di bar navigasi kiri."
|
||
|
||
msgid "Semiannually"
|
||
msgstr "Tengah tahunan"
|
||
|
||
msgid "Send unmatched traffic to the fallback chain."
|
||
msgstr "Kirim lalu lintas yang tak cocok ke rantai fallback."
|
||
|
||
msgid "Seriously, Google."
|
||
msgstr "Serius, Google."
|
||
|
||
msgid "Server Groups"
|
||
msgstr "Grup Server"
|
||
|
||
msgid "Server load"
|
||
msgstr "Server load"
|
||
|
||
msgid "Servers and Services"
|
||
msgstr "Server dan Layanan"
|
||
|
||
msgid "Service"
|
||
msgstr "Service"
|
||
|
||
msgid "Service specific upgrade instructions"
|
||
msgstr "Instruksi upgrade layanan khusus"
|
||
|
||
msgid "Services"
|
||
msgstr "Services"
|
||
|
||
msgid ""
|
||
"Services related to OpenStack Compute are normally fairly fast and rely on a "
|
||
"couple of backend services: Identity for authentication and authorization), "
|
||
"and AMQP for interoperability. Any slowness related to services is normally "
|
||
"related to one of these. Also, as with all other services, SQL is used "
|
||
"extensively."
|
||
msgstr ""
|
||
"Layanan yang terkait dengan OpenStack Compute biasanya cukup cepat dan "
|
||
"bergantung pada beberapa layanan backend: Identity untuk otentikasi dan "
|
||
"otorisasi), dan AMQP untuk interoperabilitas. Setiap kelambatan yang terkait "
|
||
"dengan layanan biasanya terkait dengan salah satunya. Juga, seperti semua "
|
||
"layanan lainnya, SQL digunakan secara luas."
|
||
|
||
msgid "Set Block Storage Quotas"
|
||
msgstr "Tetapkan Kuota Block Storage"
|
||
|
||
msgid "Set Compute Service Quotas"
|
||
msgstr "Tetapkan Kuota Layanan Compute"
|
||
|
||
msgid "Set Image Quotas"
|
||
msgstr "Tetapkan Kuota Image"
|
||
|
||
msgid "Set Object Storage Quotas"
|
||
msgstr "Tetapkan Kuota Object Storage"
|
||
|
||
msgid ""
|
||
"Set up the Key Manager service by editing /etc/nova/nova.conf and adding the "
|
||
"entries in the codeblock below"
|
||
msgstr ""
|
||
"Atur layanan Key Manager dengan mengedit /etc/nova/nova.conf dan menambahkan "
|
||
"entri di codeblock di bawah ini"
|
||
|
||
msgid ""
|
||
"Several configuration-management tools are available, and this guide does "
|
||
"not recommend a specific one. The most popular ones in the OpenStack "
|
||
"community are:"
|
||
msgstr ""
|
||
"Beberapa alat manajemen konfigurasi tersedia, dan panduan ini tidak "
|
||
"merekomendasikan yang spesifik. Yang paling populer di komunitas OpenStack "
|
||
"adalah:"
|
||
|
||
msgid ""
|
||
"Several minutes after ``nova-network`` is restarted, you should see new "
|
||
"dnsmasq processes running:"
|
||
msgstr ""
|
||
"Beberapa menit setelah ``nova-network`` dimulai ulang, Anda akan melihat "
|
||
"proses dnsmasq baru berjalan:"
|
||
|
||
msgid ""
|
||
"Several options are available for MySQL load balancing, and the supported "
|
||
"AMQP brokers have built-in clustering support. Information on how to "
|
||
"configure these and many of the other services can be found in the "
|
||
"`Operations Guide <https://docs.openstack.org/operations-guide/>`_."
|
||
msgstr ""
|
||
"Beberapa opsi tersedia untuk penyeimbangan beban MySQL, dan AMQP broker yang "
|
||
"didukung memiliki dukungan pengelompokan bawaan. Informasi tentang cara "
|
||
"mengkonfigurasi ini dan banyak layanan lainnya dapat ditemukan di Internet "
|
||
"`Operations Guide <https://docs.openstack.org/operations-guide/>`_."
|
||
|
||
msgid ""
|
||
"Several pre-made images exist and can easily be imported into the Image "
|
||
"service. A common image to add is the CirrOS image, which is very small and "
|
||
"used for testing purposes. To add this image, simply do:"
|
||
msgstr ""
|
||
"Beberapa image pra-made ada dan dapat dengan mudah diimpor ke layanan Image. "
|
||
"Image yang umum untuk ditambahkan adalah image CirrOS, yang sangat kecil dan "
|
||
"digunakan untuk tujuan pengujian. Untuk menambahkan image ini, cukup lakukan:"
|
||
|
||
msgid "Should backups be kept off-site?"
|
||
msgstr "Haruskah cadangan disimpan off-site?"
|
||
|
||
msgid ""
|
||
"Shut down your compute node, perform the maintenance, and turn the node back "
|
||
"on."
|
||
msgstr ""
|
||
"Matikan simpul komputasi Anda, lakukan pemeliharaan, dan nyalakan kembali "
|
||
"simpul tersebut."
|
||
|
||
msgid "Shutting Down a Storage Node"
|
||
msgstr "Mematikan Storage Node"
|
||
|
||
msgid "Signature hash method = SHA-256"
|
||
msgstr "Metode hash signature = SHA-256"
|
||
|
||
msgid "Signature hash methods: SHA-224, SHA-256, SHA-384, and SHA-512"
|
||
msgstr "Metode hash signature: SHA-224, SHA-256, SHA-384, and SHA-512"
|
||
|
||
msgid "Signature key type = RSA-PSS"
|
||
msgstr "Jenis signature key = RSA-PSS"
|
||
|
||
msgid ""
|
||
"Signature key types: DSA, ECC_SECT571K1, ECC_SECT409K1, ECC_SECT571R1, "
|
||
"ECC_SECT409R1, ECC_SECP521R1, ECC_SECP384R1, and RSA-PSS"
|
||
msgstr ""
|
||
"Jenis signature key: DSA, ECC_SECT571K1, ECC_SECT409K1, ECC_SECT571R1, "
|
||
"ECC_SECT409R1, ECC_SECP521R1, ECC_SECP384R1, dan RSA-PSS"
|
||
|
||
msgid "Signature verification will occur when Compute boots the signed image"
|
||
msgstr "Verifikasi signature akan terjadi ketika Compute mem-boot signed image"
|
||
|
||
msgid ""
|
||
"Similarly, if you have an existing cloud and are looking to upgrade from "
|
||
"``nova-network`` to OpenStack Networking, you should have the option to "
|
||
"delay the upgrade for this period of time. However, each release of "
|
||
"OpenStack brings significant new innovation, and regardless of your use of "
|
||
"networking methodology, it is likely best to begin planning for an upgrade "
|
||
"within a reasonable timeframe of each release."
|
||
msgstr ""
|
||
"Demikian pula, jika Anda memiliki cloud yang ada dan ingin memutakhirkan "
|
||
"dari ``nova-network`` ke OpenStack Networking, Anda harus memiliki opsi "
|
||
"untuk menunda upgrade untuk periode waktu ini. Namun, setiap rilis OpenStack "
|
||
"membawa inovasi baru yang signifikan, dan terlepas dari penggunaan "
|
||
"metodologi jaringan Anda, mungkin yang terbaik untuk mulai merencanakan "
|
||
"peningkatan dalam jangka waktu yang wajar dari setiap rilis."
|
||
|
||
msgid ""
|
||
"Since my database contained many records—over 1 million metadata records and "
|
||
"over 300,000 instance records in \"deleted\" or \"errored\" states—each "
|
||
"search took a long time. I decided to clean up the database by first "
|
||
"archiving a copy for backup and then performing some deletions using the "
|
||
"MySQL client. For example, I ran the following SQL command to remove rows of "
|
||
"instances deleted for over a year:"
|
||
msgstr ""
|
||
"Karena basis data saya berisi banyak catatan — lebih dari 1 juta catatan "
|
||
"metadata dan lebih dari 300.000 catatan instance dalam status \"deleted\" "
|
||
"atau \"errored\" - setiap pencarian membutuhkan waktu lama. Saya memutuskan "
|
||
"untuk membersihkan database dengan terlebih dahulu mengarsipkan salinan "
|
||
"untuk cadangan dan kemudian melakukan beberapa penghapusan menggunakan klien "
|
||
"MySQL. Sebagai contoh, saya menjalankan perintah SQL berikut untuk menghapus "
|
||
"deretan instance yang dihapus selama lebih dari setahun:"
|
||
|
||
msgid ""
|
||
"Since the Liberty release, OpenStack services will automatically recover "
|
||
"from a RabbitMQ outage. You should only consider restarting OpenStack "
|
||
"services after checking if RabbitMQ heartbeat functionality is enabled, and "
|
||
"if OpenStack services are not picking up messages from RabbitMQ queues."
|
||
msgstr ""
|
||
"Sejak rilis Liberty, layanan OpenStack akan secara otomatis pulih dari "
|
||
"pemadaman (outage) RabbitMQ. Anda hanya harus mempertimbangkan memulai "
|
||
"kembali layanan OpenStack setelah memeriksa apakah fungsi heartbeat RabbitMQ "
|
||
"diaktifkan, dan jika layanan OpenStack tidak menerima pesan dari antrian "
|
||
"RabbitMQ."
|
||
|
||
msgid ""
|
||
"Since the Liberty release, OpenStack with RabbitMQ 3.4.x or 3.6.x has an "
|
||
"issue with the management database consuming the memory allocated to "
|
||
"RabbitMQ. This is caused by statistics collection and processing. When a "
|
||
"single node with RabbitMQ reaches its memory threshold, all exchange and "
|
||
"queue processing is halted until the memory alarm recovers."
|
||
msgstr ""
|
||
"Sejak rilis Liberty, OpenStack with RabbitMQ 3.4.x atau 3.6.x memiliki "
|
||
"masalah dengan database manajemen yang menggunakan memori yang dialokasikan "
|
||
"untuk RabbitMQ. Ini disebabkan oleh pengumpulan dan pemrosesan statistik. "
|
||
"Ketika satu node dengan RabbitMQ mencapai ambang memori, semua pertukaran "
|
||
"dan pemrosesan antrian dihentikan hingga alarm memori pulih."
|
||
|
||
msgid ""
|
||
"Slowness in the OpenStack :term:`Networking service <Networking service "
|
||
"(neutron)>` can be caused by services that it relies upon, but it can also "
|
||
"be related to either physical or virtual networking. For example: network "
|
||
"namespaces that do not exist or are not tied to interfaces correctly; DHCP "
|
||
"daemons that have hung or are not running; a cable being physically "
|
||
"disconnected; a switch not being configured correctly. When debugging "
|
||
"Networking service problems, begin by verifying all physical networking "
|
||
"functionality (switch configuration, physical cabling, etc.). After the "
|
||
"physical networking is verified, check to be sure all of the Networking "
|
||
"services are running (neutron-server, neutron-dhcp-agent, etc.), then check "
|
||
"on AMQP and SQL back ends."
|
||
msgstr ""
|
||
"Kelambatan pada OpenStack :term:`Networking service <Networking service "
|
||
"(neutron)>` dapat disebabkan oleh layanan yang diandalkannya, tetapi juga "
|
||
"dapat dikaitkan dengan jaringan fisik atau virtual. Misalnya: namespace "
|
||
"jaringan yang tidak ada atau tidak terikat ke interface dengan benar; Daemon "
|
||
"DHCP yang telah hang atau tidak berjalan; kabel terputus secara fisik; "
|
||
"sebuah switch tidak dikonfigurasikan dengan benar. Ketika debugging masalah "
|
||
"layanan Networking, mulailah dengan memverifikasi semua fungsi jaringan "
|
||
"fisik (konfigurasi switch, kabel fisik, dll.). Setelah jaringan fisik "
|
||
"diverifikasi, periksa untuk memastikan semua layanan Networking berjalan "
|
||
"(neutron-server, neutron-dhcp-agent, dll.), Lalu periksa AMQP dan SQL back "
|
||
"end."
|
||
|
||
msgid "So it was a qemu/kvm bug."
|
||
msgstr "Jadi itu adalah bug qemu/kvm."
|
||
|
||
msgid ""
|
||
"So, I found myself wondering what changed in the EC2 API on Havana that "
|
||
"might cause this to happen. Was it a bug or a normal behavior that I now "
|
||
"need to work around?"
|
||
msgstr ""
|
||
"Jadi, saya mendapati diri saya bertanya-tanya apa yang berubah dalam EC2 API "
|
||
"di Havana yang mungkin menyebabkan ini terjadi. Apakah itu bug atau perilaku "
|
||
"normal yang sekarang harus saya atasi?"
|
||
|
||
msgid "Software licensing"
|
||
msgstr "Lisensi perangkat lunak"
|
||
|
||
msgid "Some of the resources that you want to monitor include:"
|
||
msgstr "Beberapa sumber daya yang ingin Anda pantau meliputi:"
|
||
|
||
msgid "Some other examples for Intelligent Alerting include:"
|
||
msgstr "Beberapa contoh lain untuk Peringatan Intelligent meliputi:"
|
||
|
||
msgid ""
|
||
"Sometimes a compute node either crashes unexpectedly or requires a reboot "
|
||
"for maintenance reasons."
|
||
msgstr ""
|
||
"Kadang-kadang node komputasi macet secara tak terduga atau membutuhkan "
|
||
"reboot untuk alasan pemeliharaan."
|
||
|
||
msgid ""
|
||
"Sometimes a user and a group have a one-to-one mapping. This happens for "
|
||
"standard system accounts, such as cinder, glance, nova, and swift, or when "
|
||
"only one user is part of a group."
|
||
msgstr ""
|
||
"Terkadang pengguna dan grup memiliki pemetaan satu-ke-satu. Ini terjadi "
|
||
"untuk akun sistem standar, seperti cinder, glance, nova, dan swift, atau "
|
||
"ketika hanya satu pengguna yang merupakan bagian dari grup."
|
||
|
||
msgid ""
|
||
"Sometimes an instance is terminated but the floating IP was not correctly "
|
||
"disassociated from that instance. Because the database is in an inconsistent "
|
||
"state, the usual tools to disassociate the IP no longer work. To fix this, "
|
||
"you must manually update the database."
|
||
msgstr ""
|
||
"Terkadang sebuah instance dihentikan tetapi IP mengambang tidak dipisahkan "
|
||
"dengan benar dari instance itu. Karena database berada dalam keadaan tidak "
|
||
"konsisten, alat yang biasa digunakan untuk memisahkan IP tidak lagi "
|
||
"berfungsi. Untuk memperbaikinya, Anda harus memperbarui basis data secara "
|
||
"manual."
|
||
|
||
msgid "Source ``openrc`` to set up your environment variables for the CLI:"
|
||
msgstr "Sumber ``openrc`` untuk mengatur variabel lingkungan Anda untuk CLI:"
|
||
|
||
msgid "Source openrc to set up your environment variables for the CLI:"
|
||
msgstr "Sumber openrc untuk mengatur variabel lingkungan Anda untuk CLI:"
|
||
|
||
msgid "Specific Configuration Topics"
|
||
msgstr "Topik Konfigurasi Khusus"
|
||
|
||
msgid "StackTach"
|
||
msgstr "StackTach"
|
||
|
||
msgid ""
|
||
"StackTach is a tool that collects and reports the notifications sent by "
|
||
"nova. Notifications are essentially the same as logs but can be much more "
|
||
"detailed. Nearly all OpenStack components are capable of generating "
|
||
"notifications when significant events occur. Notifications are messages "
|
||
"placed on the OpenStack queue (generally RabbitMQ) for consumption by "
|
||
"downstream systems. An overview of notifications can be found at `System "
|
||
"Usage Data <https://wiki.openstack.org/wiki/SystemUsageData>`_."
|
||
msgstr ""
|
||
"StackTach adalah alat yang mengumpulkan dan melaporkan pemberitahuan yang "
|
||
"dikirim oleh nova. Notifikasi pada dasarnya sama dengan log tetapi bisa "
|
||
"lebih detail. Hampir semua komponen OpenStack mampu menghasilkan notifikasi "
|
||
"ketika peristiwa signifikan terjadi. Notifikasi adalah pesan yang "
|
||
"ditempatkan pada antrian OpenStack (umumnya RabbitMQ) untuk dikonsumsi oleh "
|
||
"sistem hilir. Tinjauan umum pemberitahuan dapat ditemukan di `System Usage "
|
||
"Data <https://wiki.openstack.org/wiki/SystemUsageData>`_."
|
||
|
||
msgid ""
|
||
"Standard backup best practices apply when creating your OpenStack backup "
|
||
"policy. For example, how often to back up your data is closely related to "
|
||
"how quickly you need to recover from data loss."
|
||
msgstr ""
|
||
"Praktik terbaik cadangan standar berlaku saat membuat kebijakan cadangan "
|
||
"OpenStack Anda. Misalnya, seberapa sering membuat cadangan data Anda terkait "
|
||
"erat dengan seberapa cepat Anda perlu pulih dari kehilangan data."
|
||
|
||
msgid "Start the ``nova-compute`` service:"
|
||
msgstr "Mulai layanan ``nova-compute``:"
|
||
|
||
msgid "Stop all OpenStack services."
|
||
msgstr "Hentikan semua layanan OpenStack."
|
||
|
||
msgid "Stop the ``nova-compute`` service:"
|
||
msgstr "Hentikan layanan ``nova-compute``:"
|
||
|
||
msgid "Storage Node Failures and Maintenance"
|
||
msgstr "Kegagalan Storage Node dan Pemeliharaan"
|
||
|
||
msgid ""
|
||
"Strengthen the system against incidents, generally by reducing if not "
|
||
"actually eliminating vulnerabilities."
|
||
msgstr ""
|
||
"Perkuat sistem terhadap insiden, umumnya dengan mengurangi jika tidak benar-"
|
||
"benar menghilangkan kerentanan."
|
||
|
||
msgid "Summary"
|
||
msgstr "Ringkasan"
|
||
|
||
msgid ""
|
||
"Support for global clustering of object storage servers is available for all "
|
||
"supported releases. You would implement these global clusters to ensure "
|
||
"replication across geographic areas in case of a natural disaster and also "
|
||
"to ensure that users can write or access their objects more quickly based on "
|
||
"the closest data center. You configure a default region with one zone for "
|
||
"each cluster, but be sure your network (WAN) can handle the additional "
|
||
"request and response load between zones as you add more zones and build a "
|
||
"ring that handles more zones. Refer to `Geographically Distributed Swift "
|
||
"Considerations <https://docs.openstack.org/swift/latest/admin_guide."
|
||
"html#geographically-distributed-swift-considerations>`_ in the documentation "
|
||
"for additional information."
|
||
msgstr ""
|
||
"Dukungan untuk pengelompokan global server penyimpanan objek tersedia untuk "
|
||
"semua rilis yang didukung. Anda akan mengimplementasikan kluster global ini "
|
||
"untuk memastikan replikasi di seluruh wilayah geografis jika terjadi bencana "
|
||
"alam dan juga untuk memastikan bahwa pengguna dapat menulis atau mengakses "
|
||
"objek mereka lebih cepat berdasarkan pusat data terdekat. Anda "
|
||
"mengonfigurasikan wilayah default dengan satu zona untuk setiap cluster, "
|
||
"tetapi pastikan jaringan Anda (WAN) dapat menangani permintaan tambahan dan "
|
||
"respons di antara zona saat Anda menambahkan lebih banyak zona dan membangun "
|
||
"cincin yang menangani lebih banyak zona. Mengacu pada `Geographically "
|
||
"Distributed Swift Considerations <https://docs.openstack.org/swift/latest/"
|
||
"admin_guide.html#geographically-distributed-swift-considerations>`_ dalam "
|
||
"dokumentasi untuk informasi tambahan."
|
||
|
||
msgid ""
|
||
"Sure enough, the user had been periodically refreshing the console log page "
|
||
"on the dashboard and the 5G file was traversing the Rabbit cluster to get to "
|
||
"the dashboard."
|
||
msgstr ""
|
||
"Benar saja, pengguna telah secara berkala me-refresh halaman log konsol di "
|
||
"dashboard dan file 5G melintasi cluster Rabbit untuk sampai ke dashboard."
|
||
|
||
msgid ""
|
||
"Suspend the instance using the :command:`virsh` command, taking note of the "
|
||
"internal ID:"
|
||
msgstr ""
|
||
"Tangguhkan instance menggunakan perintah :command:`virsh` , perhatikan ID "
|
||
"internal:"
|
||
|
||
msgid "Suspend the instance using the ``virsh`` command."
|
||
msgstr "Tangguhkan instance menggunakan perintah ``virsh``."
|
||
|
||
msgid ""
|
||
"Swap space to free up memory for processes, as an independent area of the "
|
||
"physical disk used only for swapping and nothing else."
|
||
msgstr ""
|
||
"Tukar ruang untuk membebaskan memori untuk proses, sebagai area independen "
|
||
"dari disk fisik yang hanya digunakan untuk bertukar dan tidak ada yang lain."
|
||
|
||
msgid ""
|
||
"Swift should notice the new disk and that no data exists. It then begins "
|
||
"replicating the data to the disk from the other existing replicas."
|
||
msgstr ""
|
||
"Swift harus memperhatikan disk baru dan tidak ada data. Kemudian mulai "
|
||
"mereplikasi data ke disk dari replika lain yang ada."
|
||
|
||
msgid ""
|
||
"Switch back to the ``n-sch`` screen. Among the log statements, you'll see "
|
||
"the line:"
|
||
msgstr ""
|
||
"Beralih kembali ke layar ``n-sch``. Di antara pernyataan log, Anda akan "
|
||
"melihat baris:"
|
||
|
||
msgid "Syslog choices"
|
||
msgstr "Pilihan syslog"
|
||
|
||
msgid "Systems Administration"
|
||
msgstr "Systems Administration (administrasi sistem)"
|
||
|
||
msgid ""
|
||
"Sébastien Han has written excellent blogs and generously gave his permission "
|
||
"for re-use."
|
||
msgstr ""
|
||
"Sébastien Han telah menulis blog yang luar biasa dan dengan murah hati "
|
||
"memberikan izin untuk digunakan kembali."
|
||
|
||
msgid "Table OpenStack log locations"
|
||
msgstr "Tabel lokasi log OpenStack"
|
||
|
||
msgid "Table. Example service restoration priority list"
|
||
msgstr "Table. Contoh daftar prioritas pemulihan layanan"
|
||
|
||
msgid "Table. OpenStack default flavors"
|
||
msgstr "Table. flavor standar OpenStack"
|
||
|
||
msgid "Table. OpenStack segregation methods"
|
||
msgstr "Table. Metode segregasi OpenStack"
|
||
|
||
msgid "Table: Block Storage quota descriptions"
|
||
msgstr "Table: Deskripsi kuota Block Storage"
|
||
|
||
msgid "Tailing Logs"
|
||
msgstr "Tailing Logs"
|
||
|
||
msgid ""
|
||
"Taking the first 11 characters, we can construct a device name of "
|
||
"tapff387e54-9e from this output."
|
||
msgstr ""
|
||
"Mengambil 11 karakter pertama, kita dapat membuat nama perangkat "
|
||
"tapff387e54-9e dari output ini."
|
||
|
||
msgid "Tales From the Cryp^H^H^H^H Cloud"
|
||
msgstr "Tales From the Cryp^H^H^H^H Cloud"
|
||
|
||
msgid "Telemetry"
|
||
msgstr "Telemetry"
|
||
|
||
msgid "Telemetry Service"
|
||
msgstr "Layanan Telemetry"
|
||
|
||
msgid ""
|
||
"Telemetry service - In typical environments, updating the Telemetry service "
|
||
"only requires restarting the service."
|
||
msgstr ""
|
||
"Layanan Telemetry - Dalam lingkungan tipikal, update layanan Telemetry hanya "
|
||
"membutuhkan restarting layanan."
|
||
|
||
msgid ""
|
||
"Tenants in multi-site installations need isolation from each other. The main "
|
||
"challenge is ensuring tenant networks function across regions which is not "
|
||
"currently supported in OpenStack Networking (neutron). Therefore an external "
|
||
"system may be required to manage mapping. Tenant networks may contain "
|
||
"sensitive information requiring accurate and consistent mapping to ensure "
|
||
"that a tenant in one site does not connect to a different tenant in another "
|
||
"site."
|
||
msgstr ""
|
||
"Penyewa di instalasi multi-situs membutuhkan isolasi satu sama lain. "
|
||
"Tantangan utama adalah memastikan fungsi jaringan penyewa di seluruh wilayah "
|
||
"yang saat ini tidak didukung di OpenStack Networking (neutron). Oleh karena "
|
||
"itu sistem eksternal mungkin diperlukan untuk mengelola pemetaan. Jaringan "
|
||
"penyewa dapat berisi informasi sensitif yang membutuhkan pemetaan yang "
|
||
"akurat dan konsisten untuk memastikan bahwa penyewa di satu situs tidak "
|
||
"terhubung ke penyewa yang lain di situs lain."
|
||
|
||
msgid "Terminal 1:"
|
||
msgstr "Terminal 1:"
|
||
|
||
msgid "Terminal 2:"
|
||
msgstr "Terminal 2:"
|
||
|
||
msgid ""
|
||
"Test the middleware from outside DevStack on a remote machine that has "
|
||
"access to your DevStack instance:"
|
||
msgstr ""
|
||
"Uji middleware dari luar DevStack pada mesin jarak jauh yang memiliki akses "
|
||
"ke instance DevStack Anda:"
|
||
|
||
msgid ""
|
||
"Test your middleware with the ``swift`` CLI. Start by switching to the shell "
|
||
"screen and finish by switching back to the ``swift-proxy`` screen to check "
|
||
"the log output:"
|
||
msgstr ""
|
||
"Uji middleware Anda dengan CLI ``swift``. Mulailah dengan beralih ke layar "
|
||
"shell dan selesai dengan beralih kembali ke layar ``swift-proxy`` untuk "
|
||
"memeriksa output log:"
|
||
|
||
msgid ""
|
||
"Test your scheduler with the nova CLI. Start by switching to the ``shell`` "
|
||
"screen and finish by switching back to the ``n-sch`` screen to check the log "
|
||
"output:"
|
||
msgstr ""
|
||
"Uji penjadwal Anda dengan nova CLI. Mulailah dengan beralih ke layar "
|
||
"``shell`` dan selesai dengan beralih kembali ke layar ``n-sch`` untuk "
|
||
"memeriksa output log:"
|
||
|
||
msgid "That made no sense."
|
||
msgstr "Itu tidak masuk akal."
|
||
|
||
msgid "The 1gb NIC was still alive and active"
|
||
msgstr "NIC 1GB masih hidup dan aktif"
|
||
|
||
msgid ""
|
||
"The :command:`nova reboot` command wasn't working, so I used :command:"
|
||
"`virsh`, but it immediately came back with an error saying it was unable to "
|
||
"find the backing disk. In this case, the backing disk is the Glance image "
|
||
"that is copied to ``/var/lib/nova/instances/_base`` when the image is used "
|
||
"for the first time. Why couldn't it find it? I checked the directory and "
|
||
"sure enough it was gone."
|
||
msgstr ""
|
||
"Perintah :command: `nova reboot` tidak berfungsi, jadi saya gunakan :command:"
|
||
"`virsh`, tetapi segera kembali dengan kesalahan yang mengatakan itu tidak "
|
||
"dapat menemukan backing disk. Dalam hal ini, disk pendukung adalah Glance "
|
||
"image yang disalin ke ``/var/lib/nova/instances/_base`` saat image digunakan "
|
||
"untuk pertama kalinya. Mengapa tidak bisa menemukannya? Saya memeriksa "
|
||
"direktori dan cukup yakin sudah hilang."
|
||
|
||
msgid ""
|
||
"The :command:`openstack image create` command provides a large set of "
|
||
"options for working with your image. For example, the ``--min-disk`` option "
|
||
"is useful for images that require root disks of a certain size (for example, "
|
||
"large Windows images). To view these options, run:"
|
||
msgstr ""
|
||
"Perintah :command:`openstack image create` menyediakan sejumlah besar opsi "
|
||
"untuk bekerja dengan image Anda. Sebagai contoh, opsi ``--min-disk`` berguna "
|
||
"untuk image yang membutuhkan disket root dengan ukuran tertentu (misalnya, "
|
||
"image Windows besar). Untuk melihat opsi ini, jalankan:"
|
||
|
||
msgid ""
|
||
"The CSAIL cloud is currently 64 physical nodes with a total of 768 physical "
|
||
"cores and 3,456 GB of RAM. Persistent data storage is largely outside the "
|
||
"cloud on NFS, with cloud resources focused on compute resources. There are "
|
||
"more than 130 users in more than 40 projects, typically running 2,000–2,500 "
|
||
"vCPUs in 300 to 400 instances."
|
||
msgstr ""
|
||
"Cloud CSAIL saat ini adalah 64 node fisik dengan total 768 core fisik dan "
|
||
"3.456 GB RAM. Penyimpanan data yang persisten sebagian besar berada di luar "
|
||
"cloud di NFS, dengan sumber daya cloud terfokus pada sumber daya komputasi. "
|
||
"Ada lebih dari 130 pengguna di lebih dari 40 proyek, biasanya menjalankan "
|
||
"2.000–2.500 vCPU dalam 300 hingga 400 instance."
|
||
|
||
msgid "The I/O statistics of your storage services"
|
||
msgstr "Statistik I/O dari layanan penyimpanan Anda"
|
||
|
||
msgid ""
|
||
"The Modular Layer 2 plug-in is a framework allowing OpenStack Networking to "
|
||
"simultaneously utilize the variety of layer-2 networking technologies found "
|
||
"in complex real-world data centers. It currently works with the existing "
|
||
"Open vSwitch, Linux Bridge, and Hyper-V L2 agents and is intended to replace "
|
||
"and deprecate the monolithic plug-ins associated with those L2 agents."
|
||
msgstr ""
|
||
"Plug-in Modular Layer 2 adalah kerangka kerja yang memungkinkan OpenStack "
|
||
"Networking untuk secara simultan memanfaatkan berbagai teknologi jaringan "
|
||
"layer-2 yang ditemukan di pusat data dunia nyata yang kompleks. Saat ini "
|
||
"bekerja dengan agen Open vSwitch, Linux Bridge, dan Hyper-V L2 yang ada dan "
|
||
"dimaksudkan untuk mengganti dan mencabut plug-in monolitik yang terkait "
|
||
"dengan agen L2 tersebut."
|
||
|
||
msgid ""
|
||
"The Open vSwitch driver should and usually does manage this automatically, "
|
||
"but it is useful to know how to do this by hand with the :command:`ovs-"
|
||
"vsctl` command. This command has many more subcommands than we will use "
|
||
"here; see the man page or use :command:`ovs-vsctl --help` for the full "
|
||
"listing."
|
||
msgstr ""
|
||
"Driver Open vSwitch harus dan biasanya mengelola ini secara otomatis, tetapi "
|
||
"berguna untuk mengetahui bagaimana melakukan ini dengan tangan dengan "
|
||
"perintah :command: `ovs-vsctl`. Perintah ini memiliki lebih banyak sub "
|
||
"perintah daripada yang akan kita gunakan di sini; lihat halaman manual atau "
|
||
"gunakan :command:`ovs-vsctl --help` untuk daftar lengkap."
|
||
|
||
msgid ""
|
||
"The OpenStack Foundation supported the creation of this book with plane "
|
||
"tickets to Austin, lodging (including one adventurous evening without power "
|
||
"after a windstorm), and delicious food. For about USD $10,000, we could "
|
||
"collaborate intensively for a week in the same room at the Rackspace Austin "
|
||
"office. The authors are all members of the OpenStack Foundation, which you "
|
||
"can join. Go to the `Foundation web site <https://www.openstack.org/join>`_."
|
||
msgstr ""
|
||
"OpenStack Foundation mendukung pembuatan buku ini dengan tiket pesawat ke "
|
||
"Austin, penginapan (termasuk satu malam yang penuh petualangan tanpa "
|
||
"kekuatan setelah angin topan), dan makanan lezat. Untuk sekitar USD $ "
|
||
"10.000, kami bisa berkolaborasi secara intensif selama seminggu di ruangan "
|
||
"yang sama di kantor Rackspace Austin. Para penulis adalah semua anggota "
|
||
"OpenStack Foundation, yang dapat Anda ikuti. Pergi ke `Foundation web site "
|
||
"<https://www.openstack.org/join>`_."
|
||
|
||
msgid "The OpenStack command-line client can provide some additional details:"
|
||
msgstr ""
|
||
"Klien command-line OpenStack dapat memberikan beberapa detail tambahan:"
|
||
|
||
msgid ""
|
||
"The OpenStack community has had a database-as-a-service tool in development "
|
||
"for some time, and we saw the first integrated release of it in Icehouse. "
|
||
"From its release it was able to deploy database servers out of the box in a "
|
||
"highly available way, initially supporting only MySQL. Juno introduced "
|
||
"support for Mongo (including clustering), PostgreSQL and Couchbase, in "
|
||
"addition to replication functionality for MySQL. In Kilo, more advanced "
|
||
"clustering capability was delivered, in addition to better integration with "
|
||
"other OpenStack components such as Networking."
|
||
msgstr ""
|
||
"Komunitas OpenStack telah memiliki alat basis data sebagai layanan dalam "
|
||
"pengembangan selama beberapa waktu, dan kami melihat rilis terintegrasi "
|
||
"pertama di Icehouse. Dari rilisnya, ia dapat menggunakan server database "
|
||
"dengan cara yang sangat tersedia, awalnya hanya mendukung MySQL. Juno "
|
||
"memperkenalkan dukungan untuk Mongo (termasuk pengelompokan), PostgreSQL dan "
|
||
"Couchbase, di samping fungsi replikasi untuk MySQL. Di Kilo, kemampuan "
|
||
"pengelompokan yang lebih maju disampaikan, selain integrasi yang lebih baik "
|
||
"dengan komponen OpenStack lainnya seperti Networking."
|
||
|
||
msgid ""
|
||
"The OpenStack dashboard (horizon) can be configured to use multiple regions. "
|
||
"This can be configured through the ``AVAILABLE_REGIONS`` parameter."
|
||
msgstr ""
|
||
"Dasbor OpenStack (horizon) dapat dikonfigurasi untuk menggunakan banyak "
|
||
"wilayah. Ini dapat dikonfigurasi melalui parameter ``AVAILABLE_REGIONS``."
|
||
|
||
msgid ""
|
||
"The OpenStack processes that should be monitored depend on the specific "
|
||
"configuration of the environment, but can include:"
|
||
msgstr ""
|
||
"Proses OpenStack yang harus dipantau tergantung pada konfigurasi lingkungan "
|
||
"tertentu, tetapi dapat mencakup:"
|
||
|
||
msgid ""
|
||
"The RabbitMQ service name may vary depending on your operating system or "
|
||
"vendor who supplies your RabbitMQ service."
|
||
msgstr ""
|
||
"Nama layanan RabbitMQ dapat bervariasi tergantung pada sistem operasi atau "
|
||
"vendor Anda yang memasok layanan RabbitMQ Anda."
|
||
|
||
msgid ""
|
||
"The RabbitMQ web management interface is accessible on your cloud controller "
|
||
"at *http://localhost:55672*."
|
||
msgstr ""
|
||
"Antarmuka manajemen web RabbitMQ dapat diakses di cloud controller Anda di "
|
||
"*http://localhost:55672*."
|
||
|
||
msgid ""
|
||
"The Real Estate team at Rackspace in Austin, also known as \"The Victors,\" "
|
||
"were super responsive."
|
||
msgstr ""
|
||
"Tim Real Estat di Rackspace di Austin, juga dikenal sebagai \"The Victors,\" "
|
||
"sangat responsif."
|
||
|
||
msgid ""
|
||
"The TAP device is connected to the integration bridge, ``br-int``. This "
|
||
"bridge connects all the instance TAP devices and any other bridges on the "
|
||
"system. In this example, we have ``int-br-eth1`` and ``patch-tun``. ``int-br-"
|
||
"eth1`` is one half of a veth pair connecting to the bridge ``br-eth1``, "
|
||
"which handles VLAN networks trunked over the physical Ethernet device "
|
||
"``eth1``. ``patch-tun`` is an Open vSwitch internal port that connects to "
|
||
"the ``br-tun`` bridge for GRE networks."
|
||
msgstr ""
|
||
"Perangkat TAP terhubung ke jembatan integrasi, ``br-int``. Jembatan ini "
|
||
"menghubungkan semua perangkat TAP instance dan jembatan lainnya pada sistem. "
|
||
"Dalam contoh ini, kita memiliki ``int-br-eth1`` dan ``patch-tun``. ``int-br-"
|
||
"eth1`` adalah setengah dari pasangan yang terhubung ke jembatan ``br-eth1``, "
|
||
"yang menangani jaringan VLAN yang di-trunking melalui perangkat Ethernet "
|
||
"fisik ``eth1``. ``patch-tun`` adalah port internal Open vSwitch yang "
|
||
"menghubungkan ke jembatan ``br-tun`` untuk jaringan GRE."
|
||
|
||
msgid ""
|
||
"The TAP device name is constructed using the first 11 characters of the port "
|
||
"ID (10 hex digits plus an included '-'), so another means of finding the "
|
||
"device name is to use the :command:`neutron` command. This returns a pipe-"
|
||
"delimited list, the first item of which is the port ID. For example, to get "
|
||
"the port ID associated with IP address 10.0.0.10, do this:"
|
||
msgstr ""
|
||
"Nama perangkat TAP dibuat menggunakan 11 karakter pertama port ID (10 hex "
|
||
"digits plus an included '-'), jadi cara lain untuk menemukan nama perangkat "
|
||
"adalah dengan menggunakan perintah :command:`neutron`. Ini mengembalikan "
|
||
"pipe-delimited list, item pertama di antaranya adalah port ID. Misalnya, "
|
||
"untuk mendapatkan ID port yang terkait dengan alamat IP 10.0.0.10, lakukan "
|
||
"ini:"
|
||
|
||
msgid ""
|
||
"The TAP devices and veth devices are normal Linux network devices and may be "
|
||
"inspected with the usual tools, such as :command:`ip` and :command:"
|
||
"`tcpdump`. Open vSwitch internal devices, such as ``patch-tun``, are only "
|
||
"visible within the Open vSwitch environment. If you try to run :command:"
|
||
"`tcpdump -i patch-tun`, it will raise an error, saying that the device does "
|
||
"not exist."
|
||
msgstr ""
|
||
"Perangkat TAP dan perangkat veth adalah perangkat jaringan Linux normal dan "
|
||
"dapat diperiksa dengan alat yang biasa, seperti :command:`ip` dan :command:"
|
||
"`tcpdump`. Buka perangkat internal vSwitch, seperti ``patch-tun``, hanya "
|
||
"terlihat dalam lingkungan Open vSwitch. Jika Anda mencoba menjalankan :"
|
||
"command:`tcpdump -i patch-tun`, itu akan memunculkan kesalahan, mengatakan "
|
||
"bahwa perangkat tidak ada."
|
||
|
||
msgid ""
|
||
"The Telemetry service (:term:`ceilometer`) collects metering and event data "
|
||
"relating to OpenStack services. Data collected by the Telemetry service "
|
||
"could be used for billing. Depending on deployment configuration, collected "
|
||
"data may be accessible to users based on the deployment configuration. You "
|
||
"can read more about the module in the `Ceilometer Administrator Guide "
|
||
"<https://docs.openstack.org/ceilometer/latest/admin/index.html>`_ or in the "
|
||
"`Ceilometer Contributor Guide <https://docs.openstack.org/ceilometer/latest/"
|
||
"contributor/index.html>`_."
|
||
msgstr ""
|
||
"Layanan Telemetry (:term: `ceilometer`) mengumpulkan data pengukuran dan "
|
||
"peristiwa yang berkaitan dengan layanan OpenStack. Data yang dikumpulkan "
|
||
"oleh layanan Telemetry dapat digunakan untuk penagihan. Bergantung pada "
|
||
"konfigurasi penempatan, data yang dikumpulkan dapat diakses oleh pengguna "
|
||
"berdasarkan konfigurasi penempatan. Anda dapat membaca lebih lanjut tentang "
|
||
"modul di `Ceilometer Administrator Guide <https://docs.openstack.org/"
|
||
"ceilometer/latest/admin/index.html>` _ atau di `Ceilometer Contributor Guide "
|
||
"<https: // docs. openstack.org/ceilometer/latest/contributor/index.html>`_."
|
||
|
||
msgid "The Valentine's Day Compute Node Massacre"
|
||
msgstr ""
|
||
"The Valentine's Day Compute Node Massacre (Hari Valentine Menghitung "
|
||
"Pembantaian Node)"
|
||
|
||
msgid ""
|
||
"The `OpenStack High Availability Guide <https://docs.openstack.org/ha-guide/"
|
||
"index.html>`_ offers suggestions for elimination of a single point of "
|
||
"failure that could cause system downtime. While it is not a completely "
|
||
"prescriptive document, it offers methods and techniques for avoiding "
|
||
"downtime and data loss."
|
||
msgstr ""
|
||
"The `OpenStack High Availability Guide <https://docs.openstack.org/ha-guide/"
|
||
"index.html>`_ menawarkan saran untuk menghilangkan satu titik kegagalan yang "
|
||
"dapat menyebabkan gangguan sistem. Meskipun ini bukan dokumen yang "
|
||
"sepenuhnya preskriptif, ia menawarkan metode dan teknik untuk menghindari "
|
||
"downtime dan kehilangan data."
|
||
|
||
msgid ""
|
||
"The `OpenStack Security Guide <https://docs.openstack.org/security-guide/>`_ "
|
||
"provides a deep dive into securing an OpenStack cloud, including SSL/TLS, "
|
||
"key management, PKI and certificate management, data transport and privacy "
|
||
"concerns, and compliance."
|
||
msgstr ""
|
||
"The `OpenStack Security Guide <https://docs.openstack.org/security-guide/>`_ "
|
||
"menyediakan penyelaman mendalam untuk mengamankan cloud OpenStack, termasuk "
|
||
"SSL/TLS, manajemen utama, PKI dan manajemen sertifikat, transportasi data "
|
||
"dan masalah privasi, dan kepatuhan."
|
||
|
||
msgid ""
|
||
"The ``-H`` flag is required when running the daemons with sudo because some "
|
||
"daemons will write files relative to the user's home directory, and this "
|
||
"write may fail if ``-H`` is left off."
|
||
msgstr ""
|
||
"Flag ``-H`` diperlukan ketika menjalankan daemon dengan sudo karena beberapa "
|
||
"daemon akan menulis file relatif ke direktori home pengguna, dan penulisan "
|
||
"ini mungkin gagal jika ``-H`` ditinggalkan."
|
||
|
||
msgid ""
|
||
"The ``-s flag`` used in the cURL commands above are used to prevent "
|
||
"the progress meter from being shown. If you are having trouble running cURL "
|
||
"commands, you'll want to remove it. Likewise, to help you troubleshoot cURL "
|
||
"commands, you can include the ``-v`` flag to show you the verbose output. "
|
||
"There are many more extremely useful features in cURL; refer to the man page "
|
||
"for all the options."
|
||
msgstr ""
|
||
"``-s flag`` yang digunakan dalam perintah cURL di atas digunakan untuk "
|
||
"mencegah meteran progres tidak ditampilkan. Jika Anda mengalami kesulitan "
|
||
"menjalankan perintah cURL, Anda ingin menghapusnya. Demikian juga, untuk "
|
||
"membantu Anda memecahkan masalah perintah cURL, Anda dapat menyertakan flag "
|
||
"``-v`` untuk menunjukkan kepada Anda output verbose. Ada banyak fitur yang "
|
||
"sangat berguna di cURL; lihat halaman manual untuk semua opsi."
|
||
|
||
msgid ""
|
||
"The ``/etc/nova`` directory on both the cloud controller and compute nodes "
|
||
"should be regularly backed up."
|
||
msgstr ""
|
||
"Direktori ``/etc/nova`` pada cloud controller dan compute node harus secara "
|
||
"teratur dicadangkan."
|
||
|
||
msgid ""
|
||
"The ``nova.quota_usages`` table keeps track of how many resources the tenant "
|
||
"currently has in use:"
|
||
msgstr ""
|
||
"Tabel ``nova.quota_usages`` melacak berapa banyak sumber daya yang digunakan "
|
||
"penyewa saat ini:"
|
||
|
||
msgid ""
|
||
"The ``nova.quotas`` and ``nova.quota_usages`` tables store quota "
|
||
"information. If a tenant's quota is different from the default quota "
|
||
"settings, its quota is stored in the ``nova.quotas`` table. For example:"
|
||
msgstr ""
|
||
"``nova.quotas`` dan ``nova.quota_usages`` tabel menyimpan informasi kuota. "
|
||
"Jika kuota penyewa berbeda dari pengaturan kuota default, kuota disimpan "
|
||
"dalam tabel ``nova.quotas``. Sebagai contoh:"
|
||
|
||
msgid ""
|
||
"The ``qg-<n>`` interface in the l3-agent router namespace sends the packet "
|
||
"on to its next hop through device ``eth2`` on the external bridge ``br-ex``. "
|
||
"This bridge is constructed similarly to ``br-eth1`` and may be inspected in "
|
||
"the same way."
|
||
msgstr ""
|
||
"Antarmuka ``qg- <n> `` di namespace router l3-agent mengirim paket ke hop "
|
||
"berikutnya melalui perangkat ``eth2`` di jembatan eksternal ``br-ex``. "
|
||
"Jembatan ini dibangun mirip dengan ``br-eth1`` dan dapat diperiksa dengan "
|
||
"cara yang sama."
|
||
|
||
msgid ""
|
||
"The ``tcpdump`` looked very, very weird. In short, it looked as though "
|
||
"network communication stopped before the instance tried to renew its IP. "
|
||
"Since there is so much DHCP chatter from a one minute lease, it's very hard "
|
||
"to confirm it, but even with only milliseconds difference between packets, "
|
||
"if one packet arrives first, it arrived first, and if that packet reported "
|
||
"network issues, then it had to have happened before DHCP."
|
||
msgstr ""
|
||
"``tcpdump`` terlihat sangat, sangat aneh. Singkatnya, sepertinya komunikasi "
|
||
"jaringan terhenti sebelum instance mencoba memperbarui IP-nya. Karena ada "
|
||
"begitu banyak obrolan DHCP dari sewa satu menit, sangat sulit untuk "
|
||
"mengkonfirmasinya, tetapi bahkan dengan hanya perbedaan milidetik antara "
|
||
"paket, jika satu paket tiba terlebih dahulu, itu tiba terlebih dahulu, dan "
|
||
"jika paket itu melaporkan masalah jaringan, maka ia memiliki telah terjadi "
|
||
"sebelum DHCP."
|
||
|
||
msgid ""
|
||
"The asterisk * indicates which screen window you are viewing. This example "
|
||
"shows we are viewing the key (for keystone) screen window:"
|
||
msgstr ""
|
||
"Tanda bintang * menunjukkan jendela layar yang Anda lihat. Contoh ini "
|
||
"menunjukkan kita sedang melihat jendela key kunci (untuk keystone):"
|
||
|
||
msgid ""
|
||
"The bare-metal deployment has been widely lauded, and development continues. "
|
||
"The Juno release brought the OpenStack Bare metal drive into the Compute "
|
||
"project, and it was aimed to deprecate the existing bare-metal driver in "
|
||
"Kilo. If you are a current user of the bare metal driver, a particular "
|
||
"blueprint to follow is `Deprecate the bare metal driver <https://blueprints."
|
||
"launchpad.net/nova/+spec/deprecate-baremetal-driver>`_"
|
||
msgstr ""
|
||
"Penggunaan bare-metal telah dipuji secara luas, dan pengembangan terus "
|
||
"berlanjut. Rilis Juno membawa OpenStack Bare metal drive ke proyek Compute, "
|
||
"dan itu bertujuan untuk menurunkan (deprecate) driver bare-metal yang ada di "
|
||
"Kilo. Jika Anda adalah pengguna saat ini dari driver bare metal, cetak biru "
|
||
"tertentu untuk diikuti adalah `Deprecate the bare metal driver <https://"
|
||
"blueprints.launchpad.net/nova/+spec/deprecate-baremetal-driver>`_"
|
||
|
||
msgid "The bonded 10gb network device (bond0) was in a DOWN state"
|
||
msgstr "Perangkat jaringan 10gb terikat (bond0) dalam keadaan DOWN"
|
||
|
||
msgid ""
|
||
"The chances of failure for the server's hardware are high at the start and "
|
||
"the end of its life. As a result, dealing with hardware failures while in "
|
||
"production can be avoided by appropriate burn-in testing to attempt to "
|
||
"trigger the early-stage failures. The general principle is to stress the "
|
||
"hardware to its limits. Examples of burn-in tests include running a CPU or "
|
||
"disk benchmark for several days."
|
||
msgstr ""
|
||
"Peluang kegagalan untuk perangkat keras server menjadi tinggi pada awal dan "
|
||
"akhir masa pakainya. Akibatnya, berurusan dengan kegagalan perangkat keras "
|
||
"saat dalam produksi dapat dihindari dengan pengujian burn-in yang tepat "
|
||
"untuk mencoba memicu kegagalan tahap awal. Prinsip umum adalah menekankan "
|
||
"perangkat keras hingga batasnya. Contoh tes burn-in termasuk menjalankan "
|
||
"benchmark CPU atau disk selama beberapa hari."
|
||
|
||
msgid ""
|
||
"The choice of central logging engine will be dependent on the operating "
|
||
"system in use as well as any organizational requirements for logging tools."
|
||
msgstr ""
|
||
"Pilihan mesin logging pusat akan tergantung pada sistem operasi yang "
|
||
"digunakan serta persyaratan organisasi untuk alat logging."
|
||
|
||
msgid ""
|
||
"The cloud controller and storage proxy are very similar to each other when "
|
||
"it comes to expected and unexpected downtime. One of each server type "
|
||
"typically runs in the cloud, which makes them very noticeable when they are "
|
||
"not running."
|
||
msgstr ""
|
||
"Pengontrol cloud dan proksi penyimpanan sangat mirip satu sama lain dalam "
|
||
"hal penghentian yang diharapkan dan tidak terduga. Salah satu dari setiap "
|
||
"jenis server biasanya berjalan di cloud, yang membuat mereka sangat terlihat "
|
||
"ketika mereka tidak berjalan."
|
||
|
||
msgid ""
|
||
"The cloud controller could completely fail if, for example, its motherboard "
|
||
"goes bad. Users will immediately notice the loss of a cloud controller since "
|
||
"it provides core functionality to your cloud environment. If your "
|
||
"infrastructure monitoring does not alert you that your cloud controller has "
|
||
"failed, your users definitely will. Unfortunately, this is a rough "
|
||
"situation. The cloud controller is an integral part of your cloud. If you "
|
||
"have only one controller, you will have many missing services if it goes "
|
||
"down."
|
||
msgstr ""
|
||
"Pengontrol cloud bisa gagal total, misalnya, motherboard-nya rusak. Pengguna "
|
||
"akan segera melihat hilangnya pengontrol cloud karena menyediakan "
|
||
"fungsionalitas inti ke lingkungan cloud Anda. Jika pemantauan infrastruktur "
|
||
"Anda tidak memberi tahu Anda bahwa pengendali cloud Anda telah gagal, "
|
||
"pengguna Anda pasti akan melakukannya. Sayangnya, ini adalah situasi yang "
|
||
"sulit. Pengontrol cloud adalah bagian integral dari cloud Anda. Jika Anda "
|
||
"hanya memiliki satu pengontrol, Anda akan memiliki banyak layanan yang "
|
||
"hilang jika turun."
|
||
|
||
msgid ""
|
||
"The cloud controller receives the ``255.255.255.255`` request and sends a "
|
||
"third response."
|
||
msgstr ""
|
||
"Pengontrol cloud menerima permintaan `` 255.255.255.255`` dan mengirimkan "
|
||
"respons ketiga."
|
||
|
||
msgid ""
|
||
"The code for OpenStack lives in ``/opt/stack``, so go to the ``nova`` "
|
||
"directory and edit your scheduler module. Change to the directory where "
|
||
"``nova`` is installed:"
|
||
msgstr ""
|
||
"Kode untuk OpenStack hidup di ``/opt/stack``, jadi buka direktori ``nova`` "
|
||
"dan edit modul penjadwal Anda. Ubah ke direktori tempat ``nova`` diinstal:"
|
||
|
||
msgid ""
|
||
"The code shown below is a driver that will schedule servers to hosts based "
|
||
"on IP address as explained at the beginning of the section. Copy the code "
|
||
"into ``ip_scheduler.py``. When you are done, save and close the file."
|
||
msgstr ""
|
||
"Kode yang ditunjukkan di bawah ini adalah driver yang akan menjadwalkan "
|
||
"server ke host berdasarkan alamat IP seperti yang dijelaskan di awal bagian. "
|
||
"Salin kode ke ``ip_scheduler.py``. Setelah selesai, simpan dan tutup file."
|
||
|
||
msgid ""
|
||
"The command output lists the currently installed version of the package, "
|
||
"newest candidate version, and all versions along with the repository that "
|
||
"contains each version. Look for the appropriate release version— "
|
||
"``2:14.0.1-0ubuntu1~cloud0`` in this case. The process of manually picking "
|
||
"through this list of packages is rather tedious and prone to errors. You "
|
||
"should consider using a script to help with this process. For example:"
|
||
msgstr ""
|
||
"Output perintah mencantumkan versi paket yang saat ini diinstal, versi "
|
||
"kandidat terbaru, dan semua versi beserta repositori yang berisi setiap "
|
||
"versi. Cari versi rilis yang sesuai— ``2:14.0.1-0ubuntu1~cloud0`` dalam "
|
||
"kasus ini. Proses memilih secara manual daftar paket ini agak membosankan "
|
||
"dan rentan terhadap kesalahan. Anda harus mempertimbangkan untuk menggunakan "
|
||
"skrip untuk membantu proses ini. Sebagai contoh:"
|
||
|
||
msgid ""
|
||
"The command-line tools can be made to show the OpenStack API calls they make "
|
||
"by passing the ``--debug`` flag to them. For example:"
|
||
msgstr ""
|
||
"Alat-alat command-line dapat dibuat untuk menunjukkan panggilan OpenStack "
|
||
"API yang mereka buat dengan mengirimkan flag ``--debug`` kepada mereka. "
|
||
"Sebagai contoh:"
|
||
|
||
msgid "The connection strings take this format:"
|
||
msgstr "String koneksi menggunakan format ini:"
|
||
|
||
msgid ""
|
||
"The currently implemented hypervisors are listed on the `OpenStack "
|
||
"Configuration Reference <https://docs.openstack.org/ocata/config-reference/"
|
||
"compute/hypervisors.html>`__. You can see a matrix of the various features "
|
||
"in OpenStack Compute (nova) hypervisor drivers at the `Hypervisor support "
|
||
"matrix page <https://docs.openstack.org/nova/latest/user/support-matrix."
|
||
"html>`_."
|
||
msgstr ""
|
||
"Hypervisor yang saat ini diterapkan tercantum pada `OpenStack Configuration "
|
||
"Reference <https://docs.openstack.org/ocata/config-reference/compute/"
|
||
"hypervisors.html>` __. Anda dapat melihat matriks berbagai fitur di driver "
|
||
"hypervisor OpenStack Compute (nova) di `Hypervisor support matrix page "
|
||
"<https://docs.openstack.org/nova/latest/user/support-matrix.html>`_."
|
||
|
||
msgid ""
|
||
"The dashboard is based on the Python `Django <https://www.djangoproject.com/"
|
||
">`_ web application framework. To know how to build your Dashboard, see "
|
||
"`Building a Dashboard using Horizon <https://docs.openstack.org/horizon/"
|
||
"latest/>`_."
|
||
msgstr ""
|
||
"Dasbor didasarkan pada Python `Django <https://www.djangoproject.com/>`_ "
|
||
"kerangka kerja aplikasi web. Untuk mengetahui cara membangun Dasbor Anda, "
|
||
"lihat `Building a Dashboard using Horizon <https://docs.openstack.org/"
|
||
"horizon/latest/>`_."
|
||
|
||
msgid ""
|
||
"The data security domain is primarily concerned with information pertaining "
|
||
"to the storage services within OpenStack. The data that crosses this network "
|
||
"has high integrity and confidentiality requirements and, depending on the "
|
||
"type of deployment, may also have strong availability requirements. The "
|
||
"trust level of this network is heavily dependent on other deployment "
|
||
"decisions."
|
||
msgstr ""
|
||
"Domain keamanan data terutama berkaitan dengan informasi yang berkaitan "
|
||
"dengan layanan penyimpanan dalam OpenStack. Data yang melintasi jaringan ini "
|
||
"memiliki persyaratan integritas dan kerahasiaan yang tinggi dan, tergantung "
|
||
"pada jenis penyebaran, mungkin juga memiliki persyaratan ketersediaan yang "
|
||
"kuat. Tingkat kepercayaan jaringan ini sangat tergantung pada keputusan "
|
||
"penempatan lainnya."
|
||
|
||
msgid ""
|
||
"The decisions you make with respect to provisioning and deployment will "
|
||
"affect your maintenance of the cloud. Your configuration management will be "
|
||
"able to evolve over time. However, more thought and design need to be done "
|
||
"for upfront choices about deployment, disk partitioning, and network "
|
||
"configuration."
|
||
msgstr ""
|
||
"Keputusan yang Anda buat sehubungan dengan penyediaan dan penyebaran akan "
|
||
"memengaruhi pemeliharaan cloud Anda. Manajemen konfigurasi Anda akan dapat "
|
||
"berkembang seiring waktu. Namun, lebih banyak pemikiran dan desain perlu "
|
||
"dilakukan untuk pilihan awal tentang penyebaran, partisi disk, dan "
|
||
"konfigurasi jaringan."
|
||
|
||
msgid ""
|
||
"The default Keystone configuration assumes that Keystone is in the local "
|
||
"host, and it uses ``http://localhost:5000/v3`` as the endpoint URL, which is "
|
||
"specified in ``glance-api.conf`` and ``nova-api.conf`` files:"
|
||
msgstr ""
|
||
"Konfigurasi Keystone default mengasumsikan Keystone ada di host lokal, dan "
|
||
"menggunakan ``http://localhost:5000/v3`` sebagai URL endpoint, yang "
|
||
"ditentukan dalam ``glance-api.conf`` dan ``file nova-api.conf``:"
|
||
|
||
msgid ""
|
||
"The default OpenStack flavors are shown in :ref:`table_default_flavors`."
|
||
msgstr ""
|
||
"Flavor OpenStack default ditampilkan di :ref: `table_default_flavours`."
|
||
|
||
msgid ""
|
||
"The definition of what constitutes a site in the relevant licenses, as the "
|
||
"term does not necessarily denote a geographic or otherwise physically "
|
||
"isolated location."
|
||
msgstr ""
|
||
"Definisi dari apa yang merupakan situs dalam lisensi yang relevan, karena "
|
||
"istilah tersebut tidak selalu menunjukkan lokasi geografis atau lokasi yang "
|
||
"terisolasi secara fisik."
|
||
|
||
msgid ""
|
||
"The environment is largely based on Scientific Linux 6, which is Red Hat "
|
||
"compatible. We use KVM as our primary hypervisor, although tests are ongoing "
|
||
"with Hyper-V on Windows Server 2008."
|
||
msgstr ""
|
||
"Lingkungan sebagian besar didasarkan pada Scientific Linux 6, yang "
|
||
"kompatibel dengan Red Hat. Kami menggunakan KVM sebagai hypervisor utama "
|
||
"kami, meskipun tes sedang berlangsung dengan Hyper-V pada Windows Server "
|
||
"2008."
|
||
|
||
msgid ""
|
||
"The example OpenStack architecture designates the cloud controller as the "
|
||
"MySQL server. This MySQL server hosts the databases for nova, glance, "
|
||
"cinder, and keystone. With all of these databases in one place, it's very "
|
||
"easy to create a database backup:"
|
||
msgstr ""
|
||
"Contoh arsitektur OpenStack menunjuk pengontrol cloud sebagai server MySQL. "
|
||
"Server MySQL ini meng-host basis data untuk nova, glance, cinder, dan "
|
||
"keystone. Dengan semua basis data ini di satu tempat, sangat mudah untuk "
|
||
"membuat cadangan basis data:"
|
||
|
||
msgid ""
|
||
"The existence of the ``*-manage`` tools is a legacy issue. It is a goal of "
|
||
"the OpenStack project to eventually migrate all of the remaining "
|
||
"functionality in the ``*-manage`` tools into the API-based tools. Until that "
|
||
"day, you need to SSH into the :term:`cloud controller node` to perform some "
|
||
"maintenance operations that require one of the ``*-manage`` tools."
|
||
msgstr ""
|
||
"Keberadaan alat `` * -manage`` adalah masalah warisan. Merupakan tujuan dari "
|
||
"proyek OpenStack untuk akhirnya memigrasi semua fungsionalitas yang tersisa "
|
||
"di alat `` * -manage`` ke alat berbasis API. Sampai hari itu, Anda perlu SSH "
|
||
"ke :term: `cloud controller node` untuk melakukan beberapa operasi "
|
||
"pemeliharaan yang memerlukan salah satu alat ``* -manage``."
|
||
|
||
msgid ""
|
||
"The first is the ``_base`` directory. This contains all the cached base "
|
||
"images from glance for each unique image that has been launched on that "
|
||
"compute node. Files ending in ``_20`` (or a different number) are the "
|
||
"ephemeral base images."
|
||
msgstr ""
|
||
"Yang pertama adalah direktori ``_base``. Ini berisi semua image dasar yang "
|
||
"di-cache dari glance untuk setiap image unik yang telah diluncurkan pada "
|
||
"node komputasi itu. File yang diakhiri dengan ``_20`` (atau nomor yang "
|
||
"berbeda) adalah image dasar fana."
|
||
|
||
msgid ""
|
||
"The first place to look is the log file related to the command you are "
|
||
"trying to run. For example, if ``openstack server list`` is failing, try "
|
||
"tailing a nova log file and running the command again:"
|
||
msgstr ""
|
||
"Tempat pertama yang harus dilihat adalah file log yang terkait dengan "
|
||
"perintah yang Anda coba jalankan. Sebagai contoh, jika ``openstack server "
|
||
"list`` gagal, coba tailing file log nova dan jalankan perintah lagi:"
|
||
|
||
msgid ""
|
||
"The first step in finding the source of an error is typically to search for "
|
||
"a CRITICAL, or ERROR message in the log starting at the bottom of the log "
|
||
"file."
|
||
msgstr ""
|
||
"Langkah pertama dalam menemukan sumber kesalahan biasanya untuk mencari "
|
||
"pesan CRITICAL, atau ERROR dalam log mulai dari bagian bawah file log."
|
||
|
||
msgid ""
|
||
"The first step is setting the aggregate metadata keys "
|
||
"``cpu_allocation_ratio`` and ``ram_allocation_ratio`` to a floating-point "
|
||
"value. The filter schedulers ``AggregateCoreFilter`` and "
|
||
"``AggregateRamFilter`` will use those values rather than the global defaults "
|
||
"in ``nova.conf`` when scheduling to hosts in the aggregate. Be cautious when "
|
||
"using this feature, since each host can be in multiple aggregates, but "
|
||
"should have only one allocation ratio for each resources. It is up to you to "
|
||
"avoid putting a host in multiple aggregates that define different values for "
|
||
"the same resource."
|
||
msgstr ""
|
||
"Langkah pertama adalah mengatur kunci metadata agregat "
|
||
"``cpu_allocation_ratio`` dan ``ram_allocation_ratio`` ke nilai floating-"
|
||
"point. Penjadwal filter ``AggregateCoreFilter`` dan ``AggregateRamFilter`` "
|
||
"akan menggunakan nilai-nilai itu daripada standar global di ``nova.conf`` "
|
||
"saat menjadwalkan host di agregat. Berhati-hatilah saat menggunakan fitur "
|
||
"ini, karena setiap host dapat terdiri dari beberapa agregat, tetapi harus "
|
||
"hanya memiliki satu rasio alokasi untuk setiap sumber daya. Terserah Anda "
|
||
"untuk menghindari menempatkan host dalam beberapa agregat yang menentukan "
|
||
"nilai yang berbeda untuk sumber daya yang sama."
|
||
|
||
msgid ""
|
||
"The first thing you must do is authenticate with the cloud using your "
|
||
"credentials to get an :term:`authentication token`."
|
||
msgstr ""
|
||
"Hal pertama yang harus Anda lakukan adalah mengautentikasi dengan cloud "
|
||
"menggunakan kredensial Anda untuk mendapatkan :term:`authentication token`."
|
||
|
||
msgid ""
|
||
"The flag verify_glance_signatures enables Compute to automatically validate "
|
||
"signed instances prior to its launch. This validation feature is enabled "
|
||
"when the value is set to TRUE"
|
||
msgstr ""
|
||
"Flag verifikasi_glance_signatures memungkinkan Compute untuk secara otomatis "
|
||
"memvalidasi signed instance sebelum diluncurkan. Fitur validasi ini "
|
||
"diaktifkan ketika nilainya diatur ke TRUE"
|
||
|
||
msgid ""
|
||
"The following are steps needed to create the signature used for the signed "
|
||
"images:"
|
||
msgstr ""
|
||
"Berikut ini adalah langkah-langkah yang diperlukan untuk membuat signature "
|
||
"yang digunakan untuk signed image:"
|
||
|
||
msgid ""
|
||
"The following command requires you to have your shell environment configured "
|
||
"with the proper administrative variables:"
|
||
msgstr ""
|
||
"Perintah berikut ini mengharuskan Anda untuk mengkonfigurasi lingkungan "
|
||
"shell Anda dengan variabel administratif yang tepat:"
|
||
|
||
msgid "The following comments are added to the rule set as appropriate:"
|
||
msgstr "Komentar berikut ditambahkan ke aturan yang ditetapkan sesuai:"
|
||
|
||
msgid ""
|
||
"The following implicit values are being used to create the signature in this "
|
||
"example:"
|
||
msgstr ""
|
||
"Nilai implisit berikut ini digunakan untuk membuat signature dalam contoh "
|
||
"ini:"
|
||
|
||
msgid "The following options are currently supported:"
|
||
msgstr "Opsi berikut saat ini didukung:"
|
||
|
||
msgid ""
|
||
"The following procedure is a possible workaround to retrieve an IP address "
|
||
"when an instance has been deleted with the port still attached:"
|
||
msgstr ""
|
||
"Prosedur berikut adalah solusi yang mungkin untuk mengambil alamat IP ketika "
|
||
"sebuah instance telah dihapus dengan port masih terpasang:"
|
||
|
||
msgid "The following security controls are described below."
|
||
msgstr "Kontrol keamanan berikut dijelaskan di bawah ini."
|
||
|
||
msgid "The following signature properties are used:"
|
||
msgstr "Properti signature berikut digunakan:"
|
||
|
||
msgid ""
|
||
"The following steps described for Ubuntu have worked on at least one "
|
||
"production environment, but they might not work for all environments."
|
||
msgstr ""
|
||
"Langkah-langkah berikut yang dijelaskan untuk Ubuntu telah bekerja pada "
|
||
"setidaknya satu lingkungan produksi, tetapi mereka mungkin tidak bekerja "
|
||
"untuk semua lingkungan."
|
||
|
||
msgid ""
|
||
"The frequency is defined separately for each periodic task. Therefore, to "
|
||
"disable every periodic task in OpenStack Compute (nova), you would need to "
|
||
"set a number of configuration options to zero. The current list of "
|
||
"configuration options you would need to set to zero are:"
|
||
msgstr ""
|
||
"Frekuensi didefinisikan secara terpisah untuk setiap tugas berkala. Oleh "
|
||
"karena itu, untuk menonaktifkan setiap tugas berkala di OpenStack Compute "
|
||
"(nova), Anda perlu mengatur sejumlah opsi konfigurasi ke nol. Daftar opsi "
|
||
"konfigurasi saat ini yang perlu Anda atur ke nol adalah:"
|
||
|
||
msgid ""
|
||
"The general case for this is setting key-value pairs in the aggregate "
|
||
"metadata and matching key-value pairs in flavor's ``extra_specs`` metadata. "
|
||
"The ``AggregateInstanceExtraSpecsFilter`` in the filter scheduler will "
|
||
"enforce that instances be scheduled only on hosts in aggregates that define "
|
||
"the same key to the same value."
|
||
msgstr ""
|
||
"Kasus umum untuk ini adalah pengaturan pasangan key-value dalam metadata "
|
||
"agregat dan pasangan key-value yang cocok dalam metadata ``extra_specs`` "
|
||
"flavor. ``AggregateInstanceExtraSpecsFilter`` di penjadwal filter akan "
|
||
"memastikan bahwa instance hanya dijadwalkan pada host dalam agregat yang "
|
||
"menentukan key yang sama dengan value yang sama."
|
||
|
||
msgid "The generated file looks something like this:"
|
||
msgstr "File yang dihasilkan terlihat seperti ini:"
|
||
|
||
msgid ""
|
||
"The good news: OpenStack has unprecedented transparency when it comes to "
|
||
"providing information about what's coming up. The bad news: each release "
|
||
"moves very quickly. The purpose of this appendix is to highlight some of the "
|
||
"useful pages to track, and take an educated guess at what is coming up in "
|
||
"the next release and perhaps further afield."
|
||
msgstr ""
|
||
"Berita baiknya: OpenStack memiliki transparansi yang belum pernah terjadi "
|
||
"sebelumnya ketika datang untuk memberikan informasi tentang apa yang akan "
|
||
"terjadi. Berita buruknya: setiap rilis bergerak sangat cepat. Tujuan dari "
|
||
"lampiran ini adalah untuk menyoroti beberapa halaman yang berguna untuk "
|
||
"dilacak, dan mengambil tebakan yang terpelajar tentang apa yang akan terjadi "
|
||
"pada rilis berikutnya dan mungkin lebih jauh."
|
||
|
||
msgid ""
|
||
"The guest security domain handles compute data generated by instances on the "
|
||
"cloud, but not services that support the operation of the cloud, such as API "
|
||
"calls. Public cloud providers and private cloud providers who do not have "
|
||
"stringent controls on instance use or who allow unrestricted internet access "
|
||
"to instances should consider this domain to be untrusted. Private cloud "
|
||
"providers may want to consider this network as internal and therefore "
|
||
"trusted only if they have controls in place to assert that they trust "
|
||
"instances and all their tenants."
|
||
msgstr ""
|
||
"Domain keamanan guest menangani data komputasi yang dihasilkan oleh instance "
|
||
"di cloud, tetapi bukan layanan yang mendukung operasi cloud, seperti "
|
||
"panggilan API. Penyedia cloud publik dan penyedia cloud pribadi yang tidak "
|
||
"memiliki kontrol ketat pada penggunaan instance atau yang memungkinkan akses "
|
||
"internet tidak terbatas ke instance harus menganggap domain ini tidak dapat "
|
||
"dipercaya. Penyedia cloud swasta mungkin ingin mempertimbangkan jaringan ini "
|
||
"sebagai internal dan karenanya hanya dipercaya jika mereka memiliki kontrol "
|
||
"untuk menegaskan bahwa mereka mempercayai mesin virtual dan semua penyewa "
|
||
"mereka."
|
||
|
||
msgid "The horizon dashboard web application"
|
||
msgstr "Aplikasi web dasbor horizon"
|
||
|
||
msgid ""
|
||
"The hypervisor also requires a security assessment. In a public cloud, "
|
||
"organizations typically do not have control over the choice of hypervisor. "
|
||
"Properly securing your hypervisor is important. Attacks made upon the "
|
||
"unsecured hypervisor are called a **hypervisor breakout**. Hypervisor "
|
||
"breakout describes the event of a compromised or malicious instance breaking "
|
||
"out of the resource controls of the hypervisor and gaining access to the "
|
||
"bare metal operating system and hardware resources."
|
||
msgstr ""
|
||
"Hypervisor juga membutuhkan penilaian keamanan. Dalam cloud publik, "
|
||
"organisasi biasanya tidak memiliki kendali atas pilihan hypervisor. "
|
||
"Mengamankan hypervisor dengan benar adalah penting. Serangan yang dilakukan "
|
||
"pada hypervisor yang tidak aman disebut sebagai **hypervisor breakout**. "
|
||
"Hypervisor breakout menggambarkan peristiwa yang berkompromi atau berbahaya "
|
||
"yang memecah kontrol sumber daya dari hypervisor dan mendapatkan akses ke "
|
||
"sistem operasi bare metal dan sumber daya perangkat keras."
|
||
|
||
msgid ""
|
||
"The initial implementation of OpenStack Compute had its own authentication "
|
||
"system and used the term ``project``. When authentication moved into the "
|
||
"OpenStack Identity (keystone) project, it used the term ``tenant`` to refer "
|
||
"to a group of users. Because of this legacy, some of the OpenStack tools "
|
||
"refer to projects and some refer to tenants."
|
||
msgstr ""
|
||
"Implementasi awal OpenStack Compute memiliki sistem otentikasi sendiri dan "
|
||
"menggunakan istilah ``project``. Ketika otentikasi pindah ke proyek "
|
||
"OpenStack Identity (keystone), ia menggunakan istilah ``tenant`` untuk "
|
||
"merujuk ke sekelompok pengguna. Karena warisan ini, beberapa alat OpenStack "
|
||
"merujuk ke proyek dan beberapa merujuk ke penyewa."
|
||
|
||
msgid "The instance finally gives up."
|
||
msgstr "Instance akhirnya menyerah."
|
||
|
||
msgid ""
|
||
"The instance generates a packet and places it on the virtual NIC inside the "
|
||
"instance, such as eth0."
|
||
msgstr ""
|
||
"Instance menghasilkan paket dan menempatkannya di NIC virtual di dalam "
|
||
"instance, seperti eth0."
|
||
|
||
msgid ""
|
||
"The instance generates a packet and places it on the virtual Network "
|
||
"Interface Card (NIC) inside the instance, such as ``eth0``."
|
||
msgstr ""
|
||
"Mesin virtual menghasilkan paket dan menempatkannya pada Network Interface "
|
||
"Card (NIC) virtual di dalam mesin virtual, seperti ``eth0``."
|
||
|
||
msgid ""
|
||
"The internal availability zone is hidden in euca-describe-availability_zones "
|
||
"(nonverbose)."
|
||
msgstr ""
|
||
"Zona ketersediaan internal disembunyikan di euca-description-"
|
||
"availability_zones (nonverbose)."
|
||
|
||
msgid "The keystone processes are run within Apache as WSGI applications."
|
||
msgstr "Proses keystone dijalankan dalam Apache sebagai aplikasi WSGI."
|
||
|
||
msgid "The keystone service"
|
||
msgstr "Layanan keystone"
|
||
|
||
msgid "The load shot up to 8 right before I received the alert"
|
||
msgstr "Muatan naik hingga 8 tepat sebelum saya menerima peringatan"
|
||
|
||
msgid ""
|
||
"The management security domain is where services interact. Sometimes "
|
||
"referred to as the control plane, the networks in this domain transport "
|
||
"confidential data such as configuration parameters, user names, and "
|
||
"passwords. In most deployments this domain is considered trusted when it is "
|
||
"behind an organization's firewall."
|
||
msgstr ""
|
||
"Domain keamanan manajemen adalah tempat layanan berinteraksi. Kadang-kadang "
|
||
"disebut sebagai bidang kontrol, jaringan dalam domain ini mengangkut data "
|
||
"rahasia seperti parameter konfigurasi, nama pengguna, dan kata sandi. Dalam "
|
||
"sebagian besar penggunaan, domain ini dianggap tepercaya saat berada di "
|
||
"belakang firewall organisasi."
|
||
|
||
msgid ""
|
||
"The many different forms of license agreements for software are often "
|
||
"written with the use of dedicated hardware in mind. This model is relevant "
|
||
"for the cloud platform itself, including the hypervisor operating system, "
|
||
"supporting software for items such as database, RPC, backup, and so on. "
|
||
"Consideration must be made when offering Compute service instances and "
|
||
"applications to end users of the cloud, since the license terms for that "
|
||
"software may need some adjustment to be able to operate economically in the "
|
||
"cloud."
|
||
msgstr ""
|
||
"Berbagai bentuk perjanjian lisensi untuk perangkat lunak sering ditulis "
|
||
"dengan menggunakan perangkat keras khusus. Model ini relevan untuk platform "
|
||
"cloud itu sendiri, termasuk sistem operasi hypervisor, perangkat lunak "
|
||
"pendukung untuk item seperti basis data, RPC, cadangan, dan sebagainya. "
|
||
"Pertimbangan harus dibuat ketika menawarkan layanan Compute instance dan "
|
||
"aplikasi untuk end users cloud, karena persyaratan lisensi untuk perangkat "
|
||
"lunak itu mungkin memerlukan beberapa penyesuaian untuk dapat beroperasi "
|
||
"secara ekonomis di cloud."
|
||
|
||
msgid "The maximum image signature character limit is 255."
|
||
msgstr "Batas karakter image signature maksimum adalah 255."
|
||
|
||
msgid ""
|
||
"The most important step is the pre-upgrade testing. If you are upgrading "
|
||
"immediately after release of a new version, undiscovered bugs might hinder "
|
||
"your progress. Some deployers prefer to wait until the first point release "
|
||
"is announced. However, if you have a significant deployment, you might "
|
||
"follow the development and testing of the release to ensure that bugs for "
|
||
"your use cases are fixed."
|
||
msgstr ""
|
||
"Langkah paling penting adalah pengujian pra-upgrade. Jika Anda upgrade "
|
||
"segera setelah rilis versi baru, bug yang belum ditemukan mungkin menghambat "
|
||
"kemajuan Anda. Beberapa penyebar lebih suka menunggu sampai rilis poin "
|
||
"pertama diumumkan. Namun, jika Anda memiliki penyebaran yang signifikan, "
|
||
"Anda dapat mengikuti pengembangan dan pengujian rilis untuk memastikan bahwa "
|
||
"bug untuk kasus penggunaan Anda diperbaiki."
|
||
|
||
msgid ""
|
||
"The networking chapter of the `OpenStack Administrator Guide <https://docs."
|
||
"openstack.org/admin-guide/>`_ shows a variety of networking scenarios and "
|
||
"their connection paths. The purpose of this section is to give you the tools "
|
||
"to troubleshoot the various components involved however they are plumbed "
|
||
"together in your environment."
|
||
msgstr ""
|
||
"Bab jaringan dari `OpenStack Administrator Guide <https://docs.openstack."
|
||
"org/admin-guide/>`_ menampilkan berbagai skenario jaringan dan jalur "
|
||
"koneksinya. Tujuan dari bagian ini adalah untuk memberi Anda alat untuk "
|
||
"memecahkan masalah berbagai komponen yang terlibat namun mereka diselami "
|
||
"bersama di lingkungan Anda."
|
||
|
||
msgid ""
|
||
"The next best approach is to use a configuration-management tool, such as "
|
||
"Puppet, to automatically build a cloud controller. This should not take more "
|
||
"than 15 minutes if you have a spare server available. After the controller "
|
||
"rebuilds, restore any backups taken (see :doc:`ops-backup-recovery`)."
|
||
msgstr ""
|
||
"Pendekatan terbaik berikutnya adalah menggunakan alat manajemen konfigurasi, "
|
||
"seperti Puppet, untuk secara otomatis membangun pengendali cloud. Seharusnya "
|
||
"tidak lebih dari 15 menit jika Anda memiliki server cadangan. Setelah "
|
||
"pengontrol membangun kembali, pulihkan semua cadangan yang diambil (lihat :"
|
||
"doc:`ops-backup-recovery`)."
|
||
|
||
msgid ""
|
||
"The next step depends on whether the virtual network is configured to use "
|
||
"802.1q VLAN tags or GRE:"
|
||
msgstr ""
|
||
"Langkah selanjutnya tergantung pada apakah jaringan virtual dikonfigurasi "
|
||
"untuk menggunakan tag VLAN 802.1q atau GRE:"
|
||
|
||
msgid "The nova scheduler service"
|
||
msgstr "Layanan penjadwal nova"
|
||
|
||
msgid "The nova services"
|
||
msgstr "Layanan nova"
|
||
|
||
msgid "The number of Object Storage requests each hour"
|
||
msgstr "Jumlah permintaan Object Storage setiap jam"
|
||
|
||
msgid "The number of ``nova-api`` requests each hour"
|
||
msgstr "Jumlah ``nova-api`` permintaan setiap jam"
|
||
|
||
msgid "The number of instances on each compute node"
|
||
msgstr "Jumlah instance pada setiap node komputasi"
|
||
|
||
msgid ""
|
||
"The number of virtual machines (VMs) you expect to run, ``((overcommit "
|
||
"fraction × cores) / virtual cores per instance)``"
|
||
msgstr ""
|
||
"Jumlah virtual machine (VM) yang Anda harapkan untuk dijalankan, "
|
||
"``((overcommit fraction × cores) / virtual cores per instance)`"
|
||
|
||
msgid "The number of volumes in use"
|
||
msgstr "Jumlah volume yang digunakan"
|
||
|
||
msgid ""
|
||
"The order you should upgrade services, and any changes from the general "
|
||
"upgrade process is described below:"
|
||
msgstr ""
|
||
"Urutan yang harus Anda upgrade layanan, dan setiap perubahan dari proses "
|
||
"upgrade umum dijelaskan di bawah ini:"
|
||
|
||
msgid ""
|
||
"The other directories are titled ``instance-xxxxxxxx``. These directories "
|
||
"correspond to instances running on that compute node. The files inside are "
|
||
"related to one of the files in the ``_base`` directory. They're essentially "
|
||
"differential-based files containing only the changes made from the original "
|
||
"``_base`` directory."
|
||
msgstr ""
|
||
"Direktori lain berjudul ``instance-xxxxxxxx``. Direktori-direktori ini "
|
||
"berhubungan dengan instance yang berjalan pada node komputasi itu. File-file "
|
||
"di dalamnya terkait dengan salah satu file di direktori ``_base``. Mereka "
|
||
"pada dasarnya adalah file berbasis diferensial yang hanya berisi perubahan "
|
||
"yang dibuat dari direktori ``_base`` asli."
|
||
|
||
msgid "The output looks like the following:"
|
||
msgstr "Outputnya terlihat seperti berikut:"
|
||
|
||
msgid "The output looks something like the following:"
|
||
msgstr "Outputnya terlihat seperti berikut:"
|
||
|
||
msgid ""
|
||
"The output of this command varies depending on the hypervisor because "
|
||
"hypervisors support different attributes. The following demonstrates the "
|
||
"difference between the two most popular hypervisors. Here is example output "
|
||
"when the hypervisor is Xen:"
|
||
msgstr ""
|
||
"Output dari perintah ini bervariasi tergantung pada hypervisor karena "
|
||
"hypervisors mendukung atribut yang berbeda. Berikut ini menunjukkan "
|
||
"perbedaan antara dua hypervisor paling populer. Berikut adalah contoh output "
|
||
"ketika hypervisor adalah Xen:"
|
||
|
||
msgid ""
|
||
"The output shows that there are five compute nodes and one cloud controller. "
|
||
"You see all the services in the up state, which indicates that the services "
|
||
"are up and running. If a service is in a down state, it is no longer "
|
||
"available. This is an indication that you should troubleshoot why the "
|
||
"service is down."
|
||
msgstr ""
|
||
"Output menunjukkan bahwa ada lima node komputasi dan satu pengendali cloud. "
|
||
"Anda melihat semua layanan dalam status naik, yang menunjukkan bahwa layanan "
|
||
"sudah berjalan dan berjalan. Jika suatu layanan dalam keadaan down, itu "
|
||
"tidak lagi tersedia. Ini merupakan indikasi bahwa Anda harus memecahkan "
|
||
"masalah mengapa layanan ini mati."
|
||
|
||
msgid ""
|
||
"The output shows three different dnsmasq processes. The dnsmasq process that "
|
||
"has the DHCP subnet range of 192.168.122.0 belongs to libvirt and can be "
|
||
"ignored. The other two dnsmasq processes belong to ``nova-network``. The two "
|
||
"processes are actually related—one is simply the parent process of the "
|
||
"other. The arguments of the dnsmasq processes should correspond to the "
|
||
"details you configured ``nova-network`` with."
|
||
msgstr ""
|
||
"Output menunjukkan tiga proses dnsmasq yang berbeda. Proses dnsmasq yang "
|
||
"memiliki rentang subnet DHCP 192.168.122.0 milik libvirt dan dapat "
|
||
"diabaikan. Dua proses dnsmasq lainnya adalah milik ``nova-network``. Kedua "
|
||
"proses itu sebenarnya saling terkait — yang satu hanyalah proses induk dari "
|
||
"yang lain. Argumen proses dnsmasq harus sesuai dengan detail yang Anda "
|
||
"konfigurasikan ``nova-network`` dengan."
|
||
|
||
msgid ""
|
||
"The packet is then received on the network node. Note that any traffic to "
|
||
"the l3-agent or dhcp-agent will be visible only within their network "
|
||
"namespace. Watching any interfaces outside those namespaces, even those that "
|
||
"carry the network traffic, will only show broadcast packets like Address "
|
||
"Resolution Protocols (ARPs), but unicast traffic to the router or DHCP "
|
||
"address will not be seen. See :ref:`dealing_with_network_namespaces` for "
|
||
"detail on how to run commands within these namespaces."
|
||
msgstr ""
|
||
"Paket tersebut kemudian diterima pada node jaringan. Perhatikan bahwa lalu "
|
||
"lintas apa pun ke l3-agent atau dhcp-agent hanya akan terlihat dalam "
|
||
"namespace jaringan mereka. Menonton antarmuka apa pun di luar namespace itu, "
|
||
"bahkan yang membawa lalu lintas jaringan, hanya akan menampilkan paket "
|
||
"siaran seperti Address Resolution Protocols (ARPs), tetapi lalu lintas "
|
||
"unicast ke router atau alamat DHCP tidak akan terlihat. Lihat :ref:"
|
||
"`dealing_with_network_namespaces` untuk detail tentang cara menjalankan "
|
||
"perintah di dalam namespaces ini."
|
||
|
||
msgid ""
|
||
"The packet then makes it to the l3-agent. This is actually another TAP "
|
||
"device within the router's network namespace. Router namespaces are named in "
|
||
"the form ``qrouter-<router-uuid>``. Running :command:`ip a` within the "
|
||
"namespace will show the TAP device name, qr-e6256f7d-31 in this example:"
|
||
msgstr ""
|
||
"Paket kemudian menuju ke l3-agent. Ini sebenarnya adalah perangkat TAP lain "
|
||
"dalam namespace jaringan router. Namespace router diberi nama dalam bentuk "
|
||
"``qrouter- <router-uuid> ``. Menjalankan :command:`ip a` dalam namespace "
|
||
"akan menampilkan nama perangkat TAP, qr-e6256f7d-31 dalam contoh ini:"
|
||
|
||
msgid ""
|
||
"The packet transfers to a Test Access Point (TAP) device on the compute "
|
||
"host, such as tap690466bc-92. You can find out what TAP is being used by "
|
||
"looking at the ``/etc/libvirt/qemu/instance-xxxxxxxx.xml`` file."
|
||
msgstr ""
|
||
"Paket transfer ke perangkat Test Access Point (TAP) pada host komputasi, "
|
||
"seperti tap690466bc-92. Anda dapat mengetahui TAP apa yang sedang digunakan "
|
||
"dengan melihat file ``/etc/libvirt/qemu/instance-xxxxxxxx.xml``."
|
||
|
||
msgid ""
|
||
"The packet transfers to the main NIC of the compute node. You can also see "
|
||
"this NIC in the :command:`brctl` output, or you can find it by referencing "
|
||
"the ``flat_interface`` option in ``nova.conf``."
|
||
msgstr ""
|
||
"Paket transfer ke NIC utama dari node komputasi. Anda juga dapat melihat NIC "
|
||
"ini dalam :command:`brctl` output, atau Anda dapat menemukannya dengan "
|
||
"merujuk opsi ``flat_interface`` di ``nova.conf``."
|
||
|
||
msgid ""
|
||
"The packet transfers to the virtual NIC of the compute host, such as, "
|
||
"``vnet1``. You can find out what vnet NIC is being used by looking at the ``/"
|
||
"etc/libvirt/qemu/instance-xxxxxxxx.xml`` file."
|
||
msgstr ""
|
||
"Paket transfer ke NIC virtual host komputasi, seperti, ``vnet1``. Anda dapat "
|
||
"mengetahui apa vnet NIC yang digunakan dengan melihat file ``/etc/libvirt/"
|
||
"qemu/instance-xxxxxxxx.xml``."
|
||
|
||
msgid ""
|
||
"The pip utility is used to manage package installation from the PyPI archive "
|
||
"and is available in the python-pip package in most Linux distributions. "
|
||
"While each OpenStack project has its own client, they are being deprecated "
|
||
"in favour of a common OpenStack client. It is generally recommended to "
|
||
"install the OpenStack client."
|
||
msgstr ""
|
||
"Utilitas pip digunakan untuk mengelola instalasi paket dari arsip PyPI dan "
|
||
"tersedia dalam paket python-pip di sebagian besar distribusi Linux. "
|
||
"Sementara setiap proyek OpenStack memiliki klien sendiri, mereka tidak lagi "
|
||
"digunakan untuk klien OpenStack yang umum. Umumnya disarankan untuk "
|
||
"menginstal klien OpenStack."
|
||
|
||
msgid ""
|
||
"The point we are trying to make here is that just because an option exists "
|
||
"doesn't mean that option is relevant to your driver choices. Normally, the "
|
||
"documentation notes which drivers the configuration applies to."
|
||
msgstr ""
|
||
"Poin yang kami coba sampaikan di sini adalah hanya karena ada opsi, tidak "
|
||
"berarti opsi itu relevan dengan pilihan driver Anda. Biasanya, dokumentasi "
|
||
"mencatat driver yang berlaku untuk konfigurasi."
|
||
|
||
msgid ""
|
||
"The preceding information was generated by using a custom script that can be "
|
||
"found on `GitHub <https://github.com/cybera/novac/blob/dev/libexec/novac-"
|
||
"quota-report>`_."
|
||
msgstr ""
|
||
"Informasi sebelumnya dihasilkan dengan menggunakan skrip khusus yang dapat "
|
||
"ditemukan di `GitHub <https://github.com/cybera/novac/blob/dev/libexec/novac-"
|
||
"quota-report>`_."
|
||
|
||
msgid ""
|
||
"The preceding output has been truncated to show only two services. You will "
|
||
"see one service entry for each service that your cloud provides. Note how "
|
||
"the endpoint domain can be different depending on the endpoint type. "
|
||
"Different endpoint domains per type are not required, but this can be done "
|
||
"for different reasons, such as endpoint privacy or network traffic "
|
||
"segregation."
|
||
msgstr ""
|
||
"Output sebelumnya telah terpotong untuk hanya menampilkan dua layanan. Anda "
|
||
"akan melihat satu entri layanan untuk setiap layanan yang disediakan cloud "
|
||
"Anda. Perhatikan bagaimana domain endpoint dapat berbeda tergantung pada "
|
||
"jenis endpoint. Domain endpoint yang berbeda per jenis tidak diperlukan, "
|
||
"tetapi ini dapat dilakukan karena alasan yang berbeda, seperti privasi "
|
||
"endpoint atau pemisahan lalu lintas jaringan."
|
||
|
||
msgid ""
|
||
"The public security domain can refer to the internet as a whole or networks "
|
||
"over which you have no authority. This domain is considered untrusted. For "
|
||
"example, in a hybrid cloud deployment, any information traversing between "
|
||
"and beyond the clouds is in the public domain and untrustworthy."
|
||
msgstr ""
|
||
"Domain keamanan publik dapat merujuk ke internet secara keseluruhan atau "
|
||
"jaringan di mana Anda tidak memiliki wewenang. Domain ini dianggap tidak "
|
||
"tepercaya. Misalnya, dalam penyebaran cloud hybrid, setiap informasi yang "
|
||
"melintasi antara dan di luar cloud berada dalam domain publik dan tidak "
|
||
"dapat dipercaya."
|
||
|
||
msgid ""
|
||
"The purpose of automatic configuration management is to establish and "
|
||
"maintain the consistency of a system without using human intervention. You "
|
||
"want to maintain consistency in your deployments so that you can have the "
|
||
"same cloud every time, repeatably. Proper use of automatic configuration-"
|
||
"management tools ensures that components of the cloud systems are in "
|
||
"particular states, in addition to simplifying deployment, and configuration "
|
||
"change propagation."
|
||
msgstr ""
|
||
"Tujuan dari manajemen konfigurasi otomatis adalah untuk membangun dan "
|
||
"memelihara konsistensi sistem tanpa menggunakan intervensi manusia. Anda "
|
||
"ingin mempertahankan konsistensi dalam penerapan Anda sehingga Anda dapat "
|
||
"memiliki cloud yang sama setiap saat, berulang-ulang. Penggunaan yang tepat "
|
||
"dari alat manajemen konfigurasi otomatis memastikan bahwa komponen sistem "
|
||
"cloud berada dalam kondisi tertentu, selain menyederhanakan deployment, dan "
|
||
"propagasi perubahan konfigurasi."
|
||
|
||
msgid "The purpose of the screen windows are as follows:"
|
||
msgstr "Tujuan dari layar windows adalah sebagai berikut:"
|
||
|
||
msgid ""
|
||
"The qemu-nbd device tries to export the instance disk's different partitions "
|
||
"as separate devices. For example, if vda is the disk and vda1 is the root "
|
||
"partition, qemu-nbd exports the device as ``/dev/nbd0`` and ``/dev/nbd0p1``, "
|
||
"respectively:"
|
||
msgstr ""
|
||
"Perangkat qemu-nbd mencoba untuk mengekspor partisi disk yang berbeda "
|
||
"sebagai perangkat yang terpisah. Misalnya, jika vda adalah disk dan vda1 "
|
||
"adalah partisi root, qemu-nbd mengekspor perangkat sebagai ``/dev/nbd0`` dan "
|
||
"``/dev/nbd0p1``, masing-masing:"
|
||
|
||
msgid ""
|
||
"The roadmap for the next release as it is developed can be seen at `Releases "
|
||
"<https://releases.openstack.org>`_."
|
||
msgstr ""
|
||
"Roadmap untuk rilis berikutnya yang sedang dikembangkan dapat dilihat di "
|
||
"`Releases <https://releases.openstack.org>`_."
|
||
|
||
msgid ""
|
||
"The simplest option to get started is to use one hard drive with two "
|
||
"partitions:"
|
||
msgstr ""
|
||
"Opsi paling sederhana untuk memulai adalah menggunakan satu hard drive "
|
||
"dengan dua partisi:"
|
||
|
||
msgid ""
|
||
"The simplest place to start testing the next version of OpenStack is by "
|
||
"setting up a new environment inside your own cloud. This might seem odd, "
|
||
"especially the double virtualization used in running compute nodes. But it "
|
||
"is a sure way to very quickly test your configuration."
|
||
msgstr ""
|
||
"Tempat paling sederhana untuk mulai menguji versi OpenStack berikutnya "
|
||
"adalah dengan mengatur lingkungan baru di dalam cloud Anda sendiri. Ini "
|
||
"mungkin tampak aneh, terutama virtualisasi ganda yang digunakan dalam "
|
||
"menjalankan node komputasi. Tetapi ini adalah cara yang pasti untuk menguji "
|
||
"konfigurasi Anda dengan sangat cepat."
|
||
|
||
msgid ""
|
||
"The simplest way to identify that this is the problem with your instance is "
|
||
"to look at the console output of your instance. If DHCP failed, you can "
|
||
"retrieve the console log by doing:"
|
||
msgstr ""
|
||
"Cara paling sederhana untuk mengidentifikasi bahwa ini adalah masalah dengan "
|
||
"instance Anda adalah dengan melihat output konsol instance Anda. Jika DHCP "
|
||
"gagal, Anda dapat mengambil log konsol dengan melakukan:"
|
||
|
||
msgid ""
|
||
"The software stack is still Ubuntu 12.04 LTS, but now with OpenStack Havana "
|
||
"from the Ubuntu Cloud Archive. KVM is the hypervisor, deployed using `FAI "
|
||
"<http://fai-project.org/>`_ and Puppet for configuration management. The FAI "
|
||
"and Puppet combination is used lab-wide, not only for OpenStack. There is a "
|
||
"single cloud controller node, which also acts as network controller, with "
|
||
"the remainder of the server hardware dedicated to compute nodes."
|
||
msgstr ""
|
||
"Tumpukan perangkat lunak masih Ubuntu 12,04 LTS, tetapi sekarang dengan "
|
||
"OpenStack Havana dari Ubuntu Cloud Archive. KVM adalah hypervisor, "
|
||
"dikerahkan menggunakan `FAI <http://fai-project.org/>`_ dan Puppet untuk "
|
||
"manajemen konfigurasi. Kombinasi FAI dan Puppet digunakan di seluruh lab, "
|
||
"tidak hanya untuk OpenStack. Ada node cloud controller tunggal, yang juga "
|
||
"bertindak sebagai pengontrol jaringan, dengan sisa perangkat keras server "
|
||
"yang didedikasikan untuk komputasi node."
|
||
|
||
msgid ""
|
||
"The source files are located in ``/usr/lib/python2.7/dist-packages/nova``."
|
||
msgstr "File sumber terletak di ``/usr/lib/python2.7/dist-packages/nova``."
|
||
|
||
msgid ""
|
||
"The starting point is the core count of your cloud. By applying some ratios, "
|
||
"you can gather information about:"
|
||
msgstr ""
|
||
"Titik awalnya adalah jumlah core cloud Anda. Dengan menerapkan beberapa "
|
||
"rasio, Anda dapat mengumpulkan informasi tentang:"
|
||
|
||
msgid "The swift services"
|
||
msgstr "Layanan swift"
|
||
|
||
msgid ""
|
||
"The take away from this is if you observe an OpenStack process that appears "
|
||
"to \"stop\" for a while and then continue to process normally, you should "
|
||
"check that periodic tasks aren't the problem. One way to do this is to "
|
||
"disable the periodic tasks by setting their interval to zero. Additionally, "
|
||
"you can configure how often these periodic tasks run—in some cases, it might "
|
||
"make sense to run them at a different frequency from the default."
|
||
msgstr ""
|
||
"Kelemahan dari ini adalah jika Anda mengamati proses OpenStack yang "
|
||
"tampaknya \"stop\" untuk sementara waktu dan kemudian melanjutkan proses "
|
||
"secara normal, Anda harus memeriksa bahwa tugas-tugas berkala bukanlah "
|
||
"masalahnya. Salah satu cara untuk melakukan ini adalah menonaktifkan tugas "
|
||
"berkala dengan mengatur intervalnya ke nol. Selain itu, Anda dapat "
|
||
"mengonfigurasi seberapa sering tugas-tugas berkala ini dijalankan — dalam "
|
||
"beberapa kasus, mungkin masuk akal untuk menjalankannya pada frekuensi yang "
|
||
"berbeda dari standarnya."
|
||
|
||
msgid ""
|
||
"The third version of the Compute API was broadly discussed and worked on "
|
||
"during the Havana and Icehouse release cycles. Current discussions indicate "
|
||
"that the V2 API will remain for many releases, and the next iteration of the "
|
||
"API will be denoted v2.1 and have similar properties to the existing v2.0, "
|
||
"rather than an entirely new v3 API. This is a great time to evaluate all API "
|
||
"and provide comments while the next generation APIs are being defined. A new "
|
||
"working group was formed specifically to `improve OpenStack APIs <https://"
|
||
"wiki.openstack.org/wiki/API_Working_Group>`_ and create design guidelines, "
|
||
"which you are welcome to join."
|
||
msgstr ""
|
||
"Versi ketiga dari Compute API dibahas secara luas dan dikerjakan selama "
|
||
"siklus rilis Havana dan Icehouse. Diskusi saat ini menunjukkan bahwa V2 API "
|
||
"akan tetap untuk banyak rilis, dan iterasi API berikutnya akan dilambangkan "
|
||
"v2.1 dan memiliki sifat yang mirip dengan v2.0 yang ada, daripada API v3 "
|
||
"yang sama sekali baru. Ini adalah waktu yang tepat untuk mengevaluasi semua "
|
||
"API dan memberikan komentar ketika API generasi berikutnya sedang "
|
||
"didefinisikan. Kelompok kerja baru dibentuk secara khusus untuk `improve "
|
||
"OpenStack APIs <https://wiki.openstack.org/wiki/API_Working_Group>` _ dan "
|
||
"membuat pedoman desain, yang dapat Anda ikuti."
|
||
|
||
msgid ""
|
||
"The tunnel bridge, ``br-tun``, contains the ``patch-int`` interface and "
|
||
"``gre-<N>`` interfaces for each peer it connects to via GRE, one for each "
|
||
"compute and network node in your cluster:"
|
||
msgstr ""
|
||
"Bridge tunnel, ``br-tun``, berisi antarmuka ``patch-int`` dan antarmuka "
|
||
"``gre- <N> `` untuk setiap peer yang terhubung melalui GRE, satu untuk "
|
||
"setiap komputasi dan node jaringan di kluster Anda:"
|
||
|
||
msgid "The types of flavors in use"
|
||
msgstr "Jenis flavor yang digunakan"
|
||
|
||
msgid ""
|
||
"The typical hardware recommended for use with OpenStack is the standard "
|
||
"value-for-money offerings that most hardware vendors stock. It should be "
|
||
"straightforward to divide your procurement into building blocks such as "
|
||
"\"compute,\" \"object storage,\" and \"cloud controller,\" and request as "
|
||
"many of these as you need. Alternatively, any existing servers you have that "
|
||
"meet performance requirements and virtualization technology are likely to "
|
||
"support OpenStack."
|
||
msgstr ""
|
||
"Perangkat keras khas yang direkomendasikan untuk digunakan dengan OpenStack "
|
||
"adalah penawaran value-for-money standar yang disediakan oleh sebagian besar "
|
||
"vendor perangkat keras. Harus mudah untuk membagi pengadaan Anda ke dalam "
|
||
"blok bangunan seperti \"compute,\" \"object storage,\" dan \"cloud "
|
||
"controller,\" dan meminta sebanyak mungkin yang Anda butuhkan. Atau, setiap "
|
||
"server yang Anda miliki yang memenuhi persyaratan kinerja dan teknologi "
|
||
"virtualisasi cenderung mendukung OpenStack."
|
||
|
||
msgid ""
|
||
"The typical way is to trace the UUID associated with an instance across the "
|
||
"service logs."
|
||
msgstr ""
|
||
"Cara tipikal adalah melacak UUID yang terkait dengan instance di seluruh log "
|
||
"layanan."
|
||
|
||
msgid "Then it all made sense…"
|
||
msgstr "Kemudian semuanya masuk akal ..."
|
||
|
||
msgid ""
|
||
"Then, if you use SSH to log into your instance and try ``ping openstack."
|
||
"org``, you should see something like:"
|
||
msgstr ""
|
||
"Kemudian, jika Anda menggunakan SSH untuk masuk ke instance Anda dan mencoba "
|
||
"``ping openstack.org``, Anda akan melihat sesuatu seperti:"
|
||
|
||
msgid ""
|
||
"There are a large number of syslogs engines available, each have differing "
|
||
"capabilities and configuration requirements."
|
||
msgstr ""
|
||
"Ada sejumlah besar mesin syslog yang tersedia, masing-masing memiliki "
|
||
"kemampuan dan persyaratan konfigurasi yang berbeda."
|
||
|
||
msgid ""
|
||
"There are also several :command:`*-manage` command-line tools. These are "
|
||
"installed with the project's services on the cloud controller and do not "
|
||
"need to be installed separately:"
|
||
msgstr ""
|
||
"Ada juga beberapa :command:`*-manage` command-line tools. Ini diinstal "
|
||
"dengan layanan proyek pada pengontrol cloud dan tidak perlu diinstal secara "
|
||
"terpisah:"
|
||
|
||
msgid "There are currently two categories of quotas for Object Storage:"
|
||
msgstr "Saat ini ada dua kategori kuota untuk Object Storage:"
|
||
|
||
msgid "There are four major layers in Logstash setup which are:"
|
||
msgstr "Ada empat lapisan utama dalam pengaturan Logstash yaitu:"
|
||
|
||
msgid ""
|
||
"There are other services worth considering that provide a bare metal "
|
||
"instance instead of a cloud. In other cases, it is possible to replicate a "
|
||
"second private cloud by integrating with a private Cloud-as-a-Service "
|
||
"deployment. The organization does not buy the hardware, but also does not "
|
||
"share with other tenants. It is also possible to use a provider that hosts a "
|
||
"bare-metal public cloud instance for which the hardware is dedicated only to "
|
||
"one customer, or a provider that offers private Cloud-as-a-Service."
|
||
msgstr ""
|
||
"Ada layanan lain yang layak dipertimbangkan yang menyediakan contoh bare "
|
||
"metal bukan cloud. Dalam kasus lain, dimungkinkan untuk mereplikasi cloud "
|
||
"pribadi kedua dengan mengintegrasikannya dengan penyebaran Cloud-as-a-"
|
||
"Service pribadi. Organisasi tidak membeli perangkat keras, tetapi juga tidak "
|
||
"berbagi dengan penyewa lain. Dimungkinkan juga untuk menggunakan penyedia "
|
||
"yang meng-host instance cloud publik bare-metal yang perangkatnya "
|
||
"didedikasikan hanya untuk satu pelanggan, atau penyedia yang menawarkan "
|
||
"Cloud-as-a-Service pribadi."
|
||
|
||
msgid ""
|
||
"There are several good sources of information available that you can use to "
|
||
"track your OpenStack development desires."
|
||
msgstr ""
|
||
"Ada beberapa sumber informasi yang tersedia yang dapat Anda gunakan untuk "
|
||
"melacak keinginan pengembangan OpenStack Anda."
|
||
|
||
msgid ""
|
||
"There are three clouds currently running at CERN, totaling about 4,700 "
|
||
"compute nodes, with approximately 120,000 cores. The CERN IT cloud aims to "
|
||
"expand to 300,000 cores by 2015."
|
||
msgstr ""
|
||
"Ada tiga awan yang saat ini berjalan di CERN, dengan total sekitar 4.700 "
|
||
"node komputasi, dengan sekitar 120.000 core. The CERN IT cloud bertujuan "
|
||
"untuk memperluas ke 300.000 core pada tahun 2015."
|
||
|
||
msgid ""
|
||
"There are two types of monitoring: watching for problems and watching usage "
|
||
"trends. The former ensures that all services are up and running, creating a "
|
||
"functional cloud. The latter involves monitoring resource usage over time in "
|
||
"order to make informed decisions about potential bottlenecks and upgrades."
|
||
msgstr ""
|
||
"Ada dua jenis pemantauan: mengawasi masalah dan mengamati tren penggunaan. "
|
||
"Yang pertama memastikan bahwa semua layanan aktif dan berjalan, menciptakan "
|
||
"cloud fungsional. Yang terakhir melibatkan pemantauan penggunaan sumber daya "
|
||
"dari waktu ke waktu untuk membuat keputusan berdasarkan informasi tentang "
|
||
"potensi kemacetan dan peningkatan."
|
||
|
||
msgid ""
|
||
"There are two ways to ensure stability with this directory. The first is to "
|
||
"make sure this directory is run on a RAID array. If a disk fails, the "
|
||
"directory is available. The second way is to use a tool such as rsync to "
|
||
"replicate the images to another server:"
|
||
msgstr ""
|
||
"Ada dua cara untuk memastikan stabilitas dengan direktori ini. Yang pertama "
|
||
"adalah memastikan direktori ini dijalankan pada array RAID. Jika disk gagal, "
|
||
"direktori tersedia. Cara kedua adalah menggunakan alat seperti rsync untuk "
|
||
"mereplikasi image ke server lain:"
|
||
|
||
msgid ""
|
||
"There is a configuration option in ``/etc/glance/glance-api.conf`` that "
|
||
"limits the number of members allowed per image, called "
|
||
"``image_member_quota``, set to 128 by default. That setting is a different "
|
||
"quota from the storage quota."
|
||
msgstr ""
|
||
"Ada opsi konfigurasi di ``/etc/glance/glance-api.conf`` yang membatasi "
|
||
"jumlah anggota yang diizinkan per image, yang disebut "
|
||
"``image_member_quota``, yang diatur ke 128 secara default. Pengaturan itu "
|
||
"adalah kuota yang berbeda dari kuota penyimpanan."
|
||
|
||
msgid ""
|
||
"There is a lot of useful information in ``context``, ``request_spec``, and "
|
||
"``filter_properties`` that you can use to decide where to schedule the "
|
||
"instance. To find out more about what properties are available, you can "
|
||
"insert the following log statements into the ``schedule_run_instance`` "
|
||
"method of the scheduler above:"
|
||
msgstr ""
|
||
"Ada banyak informasi berguna dalam ``context``, ``request_spec``, dan "
|
||
"``filter_properties`` yang dapat Anda gunakan untuk memutuskan di mana harus "
|
||
"menjadwalkan instance. Untuk mengetahui lebih lanjut tentang properti apa "
|
||
"yang tersedia, Anda dapat memasukkan pernyataan log berikut ke dalam metode "
|
||
"``schedule_run_instance`` dari penjadwal di atas:"
|
||
|
||
msgid ""
|
||
"There is a lot of useful information in ``env`` and ``conf`` that you can "
|
||
"use to decide what to do with the request. To find out more about what "
|
||
"properties are available, you can insert the following log statement into "
|
||
"the ``__init__`` method:"
|
||
msgstr ""
|
||
"Ada banyak informasi berguna dalam ``env`` dan ``conf`` yang dapat Anda "
|
||
"gunakan untuk memutuskan apa yang harus dilakukan dengan permintaan "
|
||
"tersebut. Untuk mengetahui lebih lanjut tentang properti apa yang tersedia, "
|
||
"Anda dapat memasukkan pernyataan log berikut ke dalam metode ``__init__``:"
|
||
|
||
msgid ""
|
||
"Therefore, the fastest way to get your feature request up for consideration "
|
||
"is to create an Etherpad with your ideas and propose a session to the PTG. "
|
||
"If the PTG has already passed, you may also create a blueprint directly. "
|
||
"Read this `blog post about how to work with blueprints <http://"
|
||
"vmartinezdelacruz.com/how-to-work-with-blueprints-without-losing-your-mind/"
|
||
">`_ the perspective of Victoria Martínez, a developer intern."
|
||
msgstr ""
|
||
"Karena itu, cara tercepat untuk mempertimbangkan permintaan fitur Anda "
|
||
"adalah dengan membuat Etherpad dengan ide-ide Anda dan mengusulkan sesi ke "
|
||
"PTG. Jika PTG telah lulus, Anda juga dapat membuat cetak biru secara "
|
||
"langsung. Baca ini `blog post about how to work with blueprints <http://"
|
||
"vmartinezdelacruz.com/how-to-work-with-blueprints-without-losing-your-mind/"
|
||
">`_ perspektif Victoria Martínez, pengembang intern."
|
||
|
||
msgid ""
|
||
"These actions effectively take the storage node out of the storage cluster."
|
||
msgstr ""
|
||
"Tindakan ini secara efektif mengambil node penyimpanan dari cluster "
|
||
"penyimpanan."
|
||
|
||
msgid ""
|
||
"These changes have facilitated the first proper OpenStack upgrade guide, "
|
||
"found in :doc:`ops-upgrades`, and will continue to improve in the next "
|
||
"release."
|
||
msgstr ""
|
||
"Perubahan ini telah memfasilitasi panduan peningkatan OpenStack pertama yang "
|
||
"tepat, ditemukan di :doc:`ops-upgradeades`, dan akan terus meningkat pada "
|
||
"rilis berikutnya."
|
||
|
||
msgid ""
|
||
"These security domains can be individually or collectively mapped to an "
|
||
"OpenStack deployment. The cloud operator should be aware of the appropriate "
|
||
"security concerns. Security domains should be mapped out against your "
|
||
"specific OpenStack deployment topology. The domains and their trust "
|
||
"requirements depend upon whether the cloud instance is public, private, or "
|
||
"hybrid."
|
||
msgstr ""
|
||
"Domain keamanan ini dapat dipetakan secara individual atau kolektif ke "
|
||
"penyebaran OpenStack. Operator cloud harus mengetahui masalah keamanan yang "
|
||
"sesuai. Domain keamanan harus dipetakan terhadap topologi penyebaran "
|
||
"OpenStack spesifik Anda. Domain dan persyaratan kepercayaan mereka "
|
||
"bergantung pada apakah mesin virtual tersebut publik, pribadi, atau hibrid."
|
||
|
||
msgid ""
|
||
"These steps depend on your underlying distribution, but in general you "
|
||
"should be looking for :command:`purge` commands in your package manager, "
|
||
"like :command:`aptitude purge ~c $package`. Following this, you can look for "
|
||
"orphaned files in the directories referenced throughout this guide. To "
|
||
"uninstall the database properly, refer to the manual appropriate for the "
|
||
"product in use."
|
||
msgstr ""
|
||
"Langkah-langkah ini tergantung pada distribusi mendasar Anda, tetapi secara "
|
||
"umum Anda harus mencari perintah :command:`purge` di manajer paket Anda, "
|
||
"seperti :command:`aptitude purge ~c $package`. Setelah ini, Anda dapat "
|
||
"mencari file-file tanpa induk (orphaned) di direktori yang dirujuk di "
|
||
"seluruh panduan ini. Untuk menghapus instalan database dengan benar, lihat "
|
||
"manual yang sesuai untuk produk yang digunakan."
|
||
|
||
msgid ""
|
||
"These tools also make it possible to test and roll back changes, as they are "
|
||
"fully repeatable. Conveniently, a large body of work has been done by the "
|
||
"OpenStack community in this space. Puppet, a configuration management tool, "
|
||
"even provides official modules for OpenStack projects in an OpenStack "
|
||
"infrastructure system known as `Puppet OpenStack <https://wiki.openstack.org/"
|
||
"wiki/Puppet>`_. Chef configuration management is provided within `OpenStack "
|
||
"Chef Repo <https://git.openstack.org/cgit/openstack/openstack-chef-repo>`_. "
|
||
"Additional configuration management systems include Juju, Ansible, and Salt. "
|
||
"Also, PackStack is a command-line utility for Red Hat Enterprise Linux and "
|
||
"derivatives that uses Puppet modules to support rapid deployment of "
|
||
"OpenStack on existing servers over an SSH connection."
|
||
msgstr ""
|
||
"Alat-alat ini juga memungkinkan untuk menguji dan mengembalikan perubahan, "
|
||
"karena sepenuhnya dapat diulang. Dengan mudah, banyak pekerjaan telah "
|
||
"dilakukan oleh komunitas OpenStack di ruang ini. Puppet, alat manajemen "
|
||
"konfigurasi, bahkan menyediakan modul resmi untuk proyek OpenStack dalam "
|
||
"sistem infrastruktur OpenStack yang dikenal sebagai `Puppet OpenStack "
|
||
"<https://wiki.openstack.org/wiki/Puppet>` _. Manajemen konfigurasi chef "
|
||
"disediakan dalam `OpenStack Chef Repo <https://git.openstack.org/cgit/"
|
||
"openstack/openstack-chef-repo>` _. Sistem manajemen konfigurasi tambahan "
|
||
"termasuk Juju, Ansible, dan Salt. Selain itu, PackStack adalah utilitas "
|
||
"command-line untuk Red Hat Enterprise Linux dan turunannya yang menggunakan "
|
||
"modul Puppet untuk mendukung deployment OpenStack yang cepat pada server "
|
||
"yang ada melalui koneksi SSH."
|
||
|
||
msgid ""
|
||
"These tunnels use the regular routing tables on the host to route the "
|
||
"resulting GRE packet, so there is no requirement that GRE endpoints are all "
|
||
"on the same layer-2 network, unlike VLAN encapsulation."
|
||
msgstr ""
|
||
"Terowongan ini menggunakan tabel routing biasa pada host untuk merutekan "
|
||
"paket GRE yang dihasilkan, jadi tidak ada persyaratan bahwa endpoint GRE "
|
||
"semua pada jaringan layer-2 yang sama, tidak seperti enkapsulasi VLAN."
|
||
|
||
msgid ""
|
||
"These two statements are produced by our middleware and show that the "
|
||
"request was sent from our DevStack instance and was allowed."
|
||
msgstr ""
|
||
"Kedua pernyataan ini diproduksi oleh middleware kami dan menunjukkan bahwa "
|
||
"permintaan dikirim dari instance DevStack kami dan diizinkan."
|
||
|
||
msgid ""
|
||
"Thinking it was just a one-off issue, I terminated the instance and launched "
|
||
"a new one. By then, the conference call ended and I was off to the data "
|
||
"center."
|
||
msgstr ""
|
||
"Berpikir itu hanya masalah satu kali, saya menghentikan instance dan "
|
||
"meluncurkan yang baru. Pada saat itu, panggilan konferensi berakhir dan saya "
|
||
"pergi ke pusat data."
|
||
|
||
msgid ""
|
||
"This allows for a single API server being used to control access to multiple "
|
||
"cloud installations. Introducing a second level of scheduling (the cell "
|
||
"selection), in addition to the regular ``nova-scheduler`` selection of "
|
||
"hosts, provides greater flexibility to control where virtual machines are "
|
||
"run."
|
||
msgstr ""
|
||
"Ini memungkinkan server API tunggal digunakan untuk mengontrol akses ke "
|
||
"beberapa instalasi cloud. Memperkenalkan penjadwalan tingkat kedua "
|
||
"(pemilihan sel), sebagai tambahan dari pemilihan host `` nova-scheduler`` "
|
||
"reguler, memberikan fleksibilitas yang lebih besar untuk mengontrol di mana "
|
||
"mesin virtual dijalankan."
|
||
|
||
msgid ""
|
||
"This appendix contains a small selection of use cases from the community, "
|
||
"with more technical detail than usual. Further examples can be found on the "
|
||
"`OpenStack website <https://www.openstack.org/user-stories/>`_."
|
||
msgstr ""
|
||
"Apendiks ini berisi sejumlah kecil kasus penggunaan dari komunitas, dengan "
|
||
"lebih banyak detail teknis dari biasanya. Contoh lebih lanjut dapat "
|
||
"ditemukan di `OpenStack website <https://www.openstack.org/user-stories/>`_."
|
||
|
||
msgid ""
|
||
"This bug report was the key to everything: `KVM images lose connectivity "
|
||
"with bridged network <https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/"
|
||
"+bug/997978>`_."
|
||
msgstr ""
|
||
"Laporan bug ini adalah kunci dari segalanya: `KVM images lose connectivity "
|
||
"with bridged network <https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/"
|
||
"+bug/997978>`_."
|
||
|
||
msgid ""
|
||
"This chapter describes only how to back up configuration files and databases "
|
||
"that the various OpenStack components need to run. This chapter does not "
|
||
"describe how to back up objects inside Object Storage or data contained "
|
||
"inside Block Storage. Generally these areas are left for users to back up on "
|
||
"their own."
|
||
msgstr ""
|
||
"Bab ini hanya menjelaskan cara mencadangkan file konfigurasi dan database "
|
||
"yang harus dijalankan oleh berbagai komponen OpenStack. Bab ini tidak "
|
||
"menjelaskan cara membuat cadangan objek di dalam Object Storage atau data "
|
||
"yang terkandung di dalam Block Storage. Umumnya area ini dibiarkan bagi "
|
||
"pengguna untuk membuat cadangan sendiri."
|
||
|
||
msgid ""
|
||
"This chapter focuses on the second path for customizing OpenStack by "
|
||
"providing two examples for writing new features. The first example shows how "
|
||
"to modify Object Storage service (swift) middleware to add a new feature, "
|
||
"and the second example provides a new scheduler feature for Compute service "
|
||
"(nova). To customize OpenStack this way you need a development environment. "
|
||
"The best way to get an environment up and running quickly is to run DevStack "
|
||
"within your cloud."
|
||
msgstr ""
|
||
"Bab ini berfokus pada jalur kedua untuk menyesuaikan OpenStack dengan "
|
||
"memberikan dua contoh untuk menulis fitur baru. Contoh pertama menunjukkan "
|
||
"bagaimana mengubah layanan Object Storage (swift) middleware untuk "
|
||
"menambahkan fitur baru, dan contoh kedua menyediakan fitur penjadwal baru "
|
||
"untuk layanan Compute (nova). Untuk menyesuaikan OpenStack dengan cara ini, "
|
||
"Anda memerlukan lingkungan pengembangan. Cara terbaik untuk mendapatkan "
|
||
"lingkungan dan berjalan cepat adalah menjalankan DevStack di cloud Anda."
|
||
|
||
msgid ""
|
||
"This chapter helps you set up your working environment and use it to take a "
|
||
"look around your cloud."
|
||
msgstr ""
|
||
"Bab ini membantu Anda mengatur lingkungan kerja Anda dan menggunakannya "
|
||
"untuk melihat-lihat cloud Anda."
|
||
|
||
msgid ""
|
||
"This command creates a project named ``demo``. Optionally, you can add a "
|
||
"description string by appending ``--description PROJECT_DESCRIPTION``, which "
|
||
"can be very useful. You can also create a project in a disabled state by "
|
||
"appending ``--disable`` to the command. By default, projects are created in "
|
||
"an enabled state."
|
||
msgstr ""
|
||
"Perintah ini membuat proyek bernama ``demo``. Secara opsional, Anda dapat "
|
||
"menambahkan string deskripsi dengan menambahkan ``--deskripsi "
|
||
"PROJECT_DESCRIPTION``, yang dapat sangat berguna. Anda juga dapat membuat "
|
||
"proyek dalam keadaan dinonaktifkan dengan menambahkan ``--disable`` ke "
|
||
"perintah. Secara default, proyek dibuat dalam keadaan diaktifkan."
|
||
|
||
msgid ""
|
||
"This command displays a list of how many instances a tenant has running and "
|
||
"some light usage statistics about the combined instances. This command is "
|
||
"useful for a quick overview of your cloud, but it doesn't really get into a "
|
||
"lot of details."
|
||
msgstr ""
|
||
"Perintah ini menampilkan daftar berapa banyak instance yang telah dijalankan "
|
||
"penyewa dan beberapa statistik penggunaan ringan tentang instance gabungan. "
|
||
"Perintah ini berguna untuk tinjauan umum cepat cloud Anda, tetapi tidak "
|
||
"terlalu banyak detail."
|
||
|
||
msgid ""
|
||
"This configuration will result in a separate log file for each compute node "
|
||
"as well as an aggregated log file that contains nova logs from all nodes."
|
||
msgstr ""
|
||
"Konfigurasi ini akan menghasilkan file log terpisah untuk setiap node "
|
||
"komputasi serta file log gabungan yang berisi log nova dari semua node."
|
||
|
||
msgid ""
|
||
"This does not save your password in plain text, which is a good thing. But "
|
||
"when you source or run the script, it prompts you for your password and then "
|
||
"stores your response in the environment variable ``OS_PASSWORD``. It is "
|
||
"important to note that this does require interactivity. It is possible to "
|
||
"store a value directly in the script if you require a noninteractive "
|
||
"operation, but you then need to be extremely cautious with the security and "
|
||
"permissions of this file."
|
||
msgstr ""
|
||
"Ini tidak menyimpan kata sandi Anda dalam teks biasa, yang merupakan hal "
|
||
"yang baik. Tetapi ketika Anda bersumber atau menjalankan skrip, itu meminta "
|
||
"Anda untuk kata sandi Anda dan kemudian menyimpan respons Anda dalam "
|
||
"variabel lingkungan ``OS_PASSWORD``. Penting untuk dicatat bahwa ini memang "
|
||
"membutuhkan interaktivitas. Dimungkinkan untuk menyimpan nilai secara "
|
||
"langsung dalam skrip jika Anda memerlukan operasi non-aktif, tetapi Anda "
|
||
"kemudian harus sangat berhati-hati dengan keamanan dan izin file ini."
|
||
|
||
msgid ""
|
||
"This enables you to arrange OpenStack compute hosts into logical groups and "
|
||
"provides a form of physical isolation and redundancy from other availability "
|
||
"zones, such as by using a separate power supply or network equipment."
|
||
msgstr ""
|
||
"Ini memungkinkan Anda untuk mengatur host komputasi OpenStack ke dalam grup "
|
||
"logis dan menyediakan bentuk isolasi fisik dan redundansi dari zona "
|
||
"ketersediaan lainnya, seperti dengan menggunakan catu daya atau peralatan "
|
||
"jaringan yang terpisah."
|
||
|
||
msgid ""
|
||
"This enables you to partition OpenStack Compute deployments into logical "
|
||
"groups for load balancing and instance distribution. You can use host "
|
||
"aggregates to further partition an availability zone. For example, you might "
|
||
"use host aggregates to partition an availability zone into groups of hosts "
|
||
"that either share common resources, such as storage and network, or have a "
|
||
"special property, such as trusted computing hardware."
|
||
msgstr ""
|
||
"Ini memungkinkan Anda untuk mempartisi penyebaran OpenStack Compute ke dalam "
|
||
"grup logis untuk penyeimbangan beban dan distribusi instance. Anda dapat "
|
||
"menggunakan agregat host untuk lebih lanjut mempartisi zona ketersediaan. "
|
||
"Misalnya, Anda dapat menggunakan agregat host untuk mempartisi zona "
|
||
"ketersediaan ke dalam grup host yang berbagi sumber daya bersama, seperti "
|
||
"penyimpanan dan jaringan, atau memiliki properti khusus, seperti perangkat "
|
||
"keras komputasi tepercaya."
|
||
|
||
msgid "This example assumes that ``/dev/sdb`` has failed."
|
||
msgstr "Contoh ini mengasumsikan bahwa ``/dev/sdb`` telah gagal."
|
||
|
||
msgid ""
|
||
"This example configuration handles the nova service only. It first "
|
||
"configures rsyslog to act as a server that runs on port 514. Next, it "
|
||
"creates a series of logging templates. Logging templates control where "
|
||
"received logs are stored. Using the last example, a nova log from c01."
|
||
"example.com goes to the following locations:"
|
||
msgstr ""
|
||
"Contoh konfigurasi ini hanya menangani layanan nova. Pertama-tama "
|
||
"mengkonfigurasi rsyslog untuk bertindak sebagai server yang berjalan pada "
|
||
"port 514. Selanjutnya, ia menciptakan serangkaian templat logging. Templat "
|
||
"logging mengontrol di mana log yang diterima disimpan. Menggunakan contoh "
|
||
"terakhir, log nova dari c01.example.com pergi ke lokasi berikut:"
|
||
|
||
msgid ""
|
||
"This example is for illustrative purposes only. It should not be used as a "
|
||
"container IP whitelist solution without further development and extensive "
|
||
"security testing."
|
||
msgstr ""
|
||
"Contoh ini hanya untuk tujuan ilustrasi. Seharusnya tidak digunakan sebagai "
|
||
"solusi daftar putih IP kontainer tanpa pengembangan lebih lanjut dan "
|
||
"pengujian keamanan yang luas."
|
||
|
||
msgid ""
|
||
"This example is for illustrative purposes only. It should not be used as a "
|
||
"scheduler for Compute without further development and testing."
|
||
msgstr ""
|
||
"Contoh ini hanya untuk tujuan ilustrasi. Seharusnya tidak digunakan sebagai "
|
||
"scheduler untuk Compute tanpa pengembangan dan pengujian lebih lanjut."
|
||
|
||
msgid ""
|
||
"This example shows the HTTP requests from the client and the responses from "
|
||
"the endpoints, which can be helpful in creating custom tools written to the "
|
||
"OpenStack API."
|
||
msgstr ""
|
||
"Contoh ini menunjukkan permintaan HTTP dari klien dan respons dari endpoint, "
|
||
"yang dapat membantu dalam membuat alat khusus yang ditulis ke OpenStack API."
|
||
|
||
msgid ""
|
||
"This external bridge also includes a physical network interface, ``eth2`` in "
|
||
"this example, which finally lands the packet on the external network "
|
||
"destined for an external router or destination."
|
||
msgstr ""
|
||
"Jembatan eksternal ini juga menyertakan antarmuka jaringan fisik, ``eth2`` "
|
||
"dalam contoh ini, yang akhirnya mendaratkan paket pada jaringan eksternal "
|
||
"yang ditujukan untuk router atau tujuan eksternal."
|
||
|
||
msgid ""
|
||
"This formatting is used to support translation of logging messages into "
|
||
"different languages using the `gettext <https://docs.python.org/2/library/"
|
||
"gettext.html>`_ internationalization library. You don't need to do this for "
|
||
"your own custom log messages. However, if you want to contribute the code "
|
||
"back to the OpenStack project that includes logging statements, you must "
|
||
"surround your log messages with underscores and parentheses."
|
||
msgstr ""
|
||
"Pemformatan ini digunakan untuk mendukung terjemahan pesan logging ke bahasa "
|
||
"yang berbeda menggunakan `gettext <https://docs.python.org/2/library/gettext."
|
||
"html>` _ perpustakaan internasionalisasi. Anda tidak perlu melakukan ini "
|
||
"untuk pesan log kustom Anda sendiri. Namun, jika Anda ingin berkontribusi "
|
||
"kode kembali ke proyek OpenStack yang mencakup pernyataan logging, Anda "
|
||
"harus mengelilingi pesan log Anda dengan garis bawah dan tanda kurung."
|
||
|
||
msgid ""
|
||
"This functionality is an important piece of the puzzle when it comes to live "
|
||
"upgrades and is conceptually similar to the existing API versioning that "
|
||
"allows OpenStack services of different versions to communicate without issue."
|
||
msgstr ""
|
||
"Fungsionalitas ini adalah bagian penting dari teka-teki (puzzle) ketika "
|
||
"datang ke peningkatan langsung dan secara konsep mirip dengan versi API yang "
|
||
"ada yang memungkinkan layanan OpenStack dari berbagai versi untuk "
|
||
"berkomunikasi tanpa masalah."
|
||
|
||
msgid ""
|
||
"This guide is for OpenStack operators and does not seek to be an exhaustive "
|
||
"reference for users, but as an operator, you should have a basic "
|
||
"understanding of how to use the cloud facilities. This chapter looks at "
|
||
"OpenStack from a basic user perspective, which helps you understand your "
|
||
"users' needs and determine, when you get a trouble ticket, whether it is a "
|
||
"user issue or a service issue. The main concepts covered are images, "
|
||
"flavors, security groups, block storage, shared file system storage, and "
|
||
"instances."
|
||
msgstr ""
|
||
"Panduan ini diperuntukkan bagi operator OpenStack dan tidak mencari "
|
||
"referensi lengkap bagi pengguna, tetapi sebagai operator, Anda harus "
|
||
"memiliki pemahaman dasar tentang cara menggunakan fasilitas cloud. Bab ini "
|
||
"membahas tentang OpenStack dari perspektif pengguna dasar, yang membantu "
|
||
"Anda memahami kebutuhan pengguna Anda dan menentukan, ketika Anda "
|
||
"mendapatkan tiket masalah, apakah itu masalah pengguna atau masalah layanan. "
|
||
"Konsep utama yang dicakup adalah images, flavors, security groups, block "
|
||
"storage, shared file system storage, dan instances."
|
||
|
||
msgid "This guide provides information about operating OpenStack clouds."
|
||
msgstr ""
|
||
"Panduan ini memberikan informasi tentang pengoperasian cloud OpenStack."
|
||
|
||
msgid ""
|
||
"This guide uses the term ``project``, unless an example shows interaction "
|
||
"with a tool that uses the term ``tenant``."
|
||
msgstr ""
|
||
"Panduan ini menggunakan istilah ``project``, kecuali jika contoh menunjukkan "
|
||
"interaksi dengan alat yang menggunakan istilah ``tenant``."
|
||
|
||
msgid ""
|
||
"This infrastructure includes systems to automatically install the operating "
|
||
"system's initial configuration and later coordinate the configuration of all "
|
||
"services automatically and centrally, which reduces both manual effort and "
|
||
"the chance for error. Examples include Ansible, CFEngine, Chef, Puppet, and "
|
||
"Salt. You can even use OpenStack to deploy OpenStack, named TripleO "
|
||
"(OpenStack On OpenStack)."
|
||
msgstr ""
|
||
"Infrastruktur ini mencakup sistem untuk secara otomatis menginstal "
|
||
"konfigurasi awal sistem operasi dan kemudian mengoordinasikan konfigurasi "
|
||
"semua layanan secara otomatis dan terpusat, yang mengurangi upaya manual dan "
|
||
"kemungkinan kesalahan. Contohnya termasuk Ansible, CFEngine, Chef, Puppet, "
|
||
"dan Salt. Anda bahkan dapat menggunakan OpenStack untuk menggunakan "
|
||
"OpenStack, bernama TripleO (OpenStack On OpenStack)."
|
||
|
||
msgid ""
|
||
"This instructs rsyslog to send all logs to the IP listed. In this example, "
|
||
"the IP points to the cloud controller."
|
||
msgstr ""
|
||
"Ini menginstruksikan rsyslog untuk mengirim semua log ke IP yang terdaftar. "
|
||
"Dalam contoh ini, IP menunjuk ke pengontrol cloud."
|
||
|
||
msgid ""
|
||
"This is a collection of ideas from experienced operators on common things to "
|
||
"look at that may be the cause of slowness. It is not, however, designed to "
|
||
"be an exhaustive list."
|
||
msgstr ""
|
||
"Ini adalah kumpulan ide dari operator berpengalaman tentang hal-hal umum "
|
||
"untuk dilihat yang mungkin menjadi penyebab kelambatan. Namun, ini tidak "
|
||
"dirancang untuk menjadi daftar lengkap."
|
||
|
||
msgid "This is an example of such legal frameworks:"
|
||
msgstr "Ini adalah contoh kerangka hukum tersebut:"
|
||
|
||
msgid ""
|
||
"This is an ongoing and hot topic in networking circles —especially with the "
|
||
"raise of virtualization and virtual switches."
|
||
msgstr ""
|
||
"Ini adalah topik yang sedang berlangsung dan panas di lingkaran jaringan — "
|
||
"terutama dengan peningkatan virtualisasi dan virtual switch."
|
||
|
||
msgid ""
|
||
"This is the first half of the equation. To get flavor types that are "
|
||
"guaranteed a particular ratio, you must set the ``extra_specs`` in the "
|
||
"flavor type to the key-value pair you want to match in the aggregate. For "
|
||
"example, if you define ``extra_specs`` ``cpu_allocation_ratio`` to \"1.0\", "
|
||
"then instances of that type will run in aggregates only where the metadata "
|
||
"key ``cpu_allocation_ratio`` is also defined as \"1.0.\" In practice, it is "
|
||
"better to define an additional key-value pair in the aggregate metadata to "
|
||
"match on rather than match directly on ``cpu_allocation_ratio`` or "
|
||
"``core_allocation_ratio``. This allows better abstraction. For example, by "
|
||
"defining a key ``overcommit`` and setting a value of \"high,\" \"medium,\" "
|
||
"or \"low,\" you could then tune the numeric allocation ratios in the "
|
||
"aggregates without also needing to change all flavor types relating to them."
|
||
msgstr ""
|
||
"Ini adalah bagian pertama dari persamaan. Untuk mendapatkan jenis flavor "
|
||
"yang dijamin dengan rasio tertentu, Anda harus mengatur ``extra_specs`` "
|
||
"dalam jenis flavor ke pasangan nilai kunci yang ingin Anda cocokkan dalam "
|
||
"agregat. Misalnya, jika Anda mendefinisikan ``extra_specs`` "
|
||
"``cpu_allocation_ratio`` ke \"1.0\", maka instance jenis itu akan berjalan "
|
||
"dalam agregat hanya di mana kunci metadata ``cpu_allocation_ratio`` juga "
|
||
"didefinisikan sebagai \"1.0.\" Dalam praktiknya, lebih baik untuk menentukan "
|
||
"pasangan nilai kunci tambahan dalam metadata agregat untuk dicocokkan "
|
||
"daripada mencocokkan secara langsung pada ``cpu_allocation_ratio`` atau "
|
||
"``core_allocation_ratio``. Ini memungkinkan abstraksi yang lebih baik. "
|
||
"Misalnya, dengan mendefinisikan kunci ``overcommit`` dan menetapkan nilai "
|
||
"\"high,\" \"medium,\" atau \"low,\" Anda kemudian dapat menyetel rasio "
|
||
"alokasi numerik dalam agregat tanpa juga perlu mengubah semua jenis flavor "
|
||
"yang terkait ke mereka."
|
||
|
||
msgid "This is useful, as logs from c02.example.com go to:"
|
||
msgstr "Ini berguna, karena log dari c02.example.com masuk ke:"
|
||
|
||
msgid ""
|
||
"This leaves you with an important point of decision when designing your "
|
||
"cloud. OpenStack Networking is robust enough to use with a small number of "
|
||
"limitations (performance issues in some scenarios, only basic high "
|
||
"availability of layer 3 systems) and provides many more features than ``nova-"
|
||
"network``. However, if you do not have the more complex use cases that can "
|
||
"benefit from fuller software-defined networking capabilities, or are "
|
||
"uncomfortable with the new concepts introduced, ``nova-network`` may "
|
||
"continue to be a viable option for the next 12 months."
|
||
msgstr ""
|
||
"Ini membuat Anda memiliki titik keputusan penting saat merancang cloud Anda. "
|
||
"OpenStack Networking cukup kuat untuk digunakan dengan sejumlah kecil "
|
||
"pembatasan (masalah kinerja dalam beberapa skenario, hanya ketersediaan "
|
||
"tinggi dasar layer 3 systems) dan menyediakan banyak fitur lebih banyak "
|
||
"daripada ``nova-network``. Namun, jika Anda tidak memiliki kasus penggunaan "
|
||
"yang lebih kompleks yang dapat mengambil manfaat dari kemampuan jaringan "
|
||
"yang ditentukan perangkat lunak lebih lengkap, atau tidak nyaman dengan "
|
||
"konsep-konsep baru yang diperkenalkan, ``nova-network`` dapat terus menjadi "
|
||
"opsi yang layak untuk 12 berikutnya bulan."
|
||
|
||
msgid ""
|
||
"This list will change between releases, so please refer to your "
|
||
"configuration guide for up-to-date information."
|
||
msgstr ""
|
||
"Daftar ini akan berubah di antara rilis, jadi silakan merujuk ke panduan "
|
||
"konfigurasi Anda untuk informasi terbaru."
|
||
|
||
msgid ""
|
||
"This may be a dnsmasq and/or ``nova-network`` related issue. (For the "
|
||
"preceding example, the problem happened to be that dnsmasq did not have any "
|
||
"more IP addresses to give away because there were no more fixed IPs "
|
||
"available in the OpenStack Compute database.)"
|
||
msgstr ""
|
||
"Ini mungkin masalah dnsmasq dan/atau ``nova-network`` terkait. (Sebagai "
|
||
"contoh sebelumnya, masalahnya adalah bahwa dnsmasq tidak memiliki alamat IP "
|
||
"untuk diberikan karena tidak ada lagi IP tetap yang tersedia di basis data "
|
||
"OpenStack Compute.)"
|
||
|
||
msgid "This might print the error and cause of the problem."
|
||
msgstr "Ini mungkin mencetak kesalahan dan penyebab masalah."
|
||
|
||
msgid ""
|
||
"This output shows that an instance named ``devstack`` was created from an "
|
||
"Ubuntu 12.04 image using a flavor of ``m1.small`` and is hosted on the "
|
||
"compute node ``c02.example.com``."
|
||
msgstr ""
|
||
"Output ini menunjukkan bahwa instance bernama ``devstack`` telah dibuat dari "
|
||
"image Ubuntu 12.04 menggunakan flavor ``m1.small`` dan di-host pada compute "
|
||
"node ``c02.example.com``."
|
||
|
||
msgid ""
|
||
"This output shows that two networks are configured, each network containing "
|
||
"255 IPs (a /24 subnet). The first network has been assigned to a certain "
|
||
"project, while the second network is still open for assignment. You can "
|
||
"assign this network manually; otherwise, it is automatically assigned when a "
|
||
"project launches its first instance."
|
||
msgstr ""
|
||
"Output ini menunjukkan bahwa dua jaringan telah dikonfigurasi, masing-masing "
|
||
"jaringan berisi 255 IP (a / 24 subnet). Jaringan pertama telah ditetapkan "
|
||
"untuk proyek tertentu, sedangkan jaringan kedua masih terbuka untuk "
|
||
"penugasan. Anda dapat menetapkan jaringan ini secara manual; jika tidak, ia "
|
||
"secara otomatis ditetapkan ketika proyek meluncurkan instance pertamanya."
|
||
|
||
msgid ""
|
||
"This past Valentine's Day, I received an alert that a compute node was no "
|
||
"longer available in the cloud—meaning,"
|
||
msgstr ""
|
||
"Hari Valentine yang lalu, saya menerima peringatan bahwa node komputasi "
|
||
"tidak lagi tersedia di cloud — artinya,"
|
||
|
||
msgid ""
|
||
"This project continues to improve and you may consider using it for "
|
||
"greenfield deployments, though according to the latest user survey results "
|
||
"it remains to see widespread uptake."
|
||
msgstr ""
|
||
"Proyek ini terus membaik dan Anda dapat mempertimbangkan menggunakannya "
|
||
"untuk penyebaran greenfield, meskipun menurut hasil survei pengguna terbaru, "
|
||
"masih ada untuk melihat serapan luas."
|
||
|
||
msgid ""
|
||
"This request took over two minutes to process, but executed quickly on "
|
||
"another co-existing Grizzly deployment using the same hardware and system "
|
||
"configuration."
|
||
msgstr ""
|
||
"Permintaan ini membutuhkan waktu dua menit untuk diproses, tetapi dieksekusi "
|
||
"dengan cepat pada penyebaran Grizzly yang ada bersama (co-existing) "
|
||
"menggunakan perangkat keras dan konfigurasi sistem yang sama."
|
||
|
||
msgid ""
|
||
"This script dumps the entire MySQL database and deletes any backups older "
|
||
"than seven days."
|
||
msgstr ""
|
||
"Skrip ini membuang seluruh database MySQL dan menghapus cadangan yang lebih "
|
||
"lama dari tujuh hari."
|
||
|
||
msgid ""
|
||
"This script is specific to a certain OpenStack installation and must be "
|
||
"modified to fit your environment. However, the logic should easily be "
|
||
"transferable."
|
||
msgstr ""
|
||
"Skrip ini khusus untuk instalasi OpenStack tertentu dan harus dimodifikasi "
|
||
"agar sesuai dengan lingkungan Anda. Namun, logikanya harus mudah "
|
||
"dipindahtangankan."
|
||
|
||
msgid ""
|
||
"This section covers specific examples of configuration options you might "
|
||
"consider tuning. It is by no means an exhaustive list."
|
||
msgstr ""
|
||
"Bagian ini mencakup contoh spesifik opsi konfigurasi yang dapat Anda "
|
||
"pertimbangkan untuk penyetelan. Ini tidak berarti daftar lengkap."
|
||
|
||
msgid ""
|
||
"This section describes the process to upgrade a basic OpenStack deployment "
|
||
"based on the basic two-node architecture in the `Installation Tutorials and "
|
||
"Guides <https://docs.openstack.org/rocky/install/>`_. All nodes must run a "
|
||
"supported distribution of Linux with a recent kernel and the current release "
|
||
"packages."
|
||
msgstr ""
|
||
"Bagian ini menjelaskan proses untuk upgrade penyebaran OpenStack dasar "
|
||
"berdasarkan arsitektur two-node dasar di `Installation Tutorials and Guides "
|
||
"<https://docs.openstack.org/rocky/install/>` _. Semua node harus menjalankan "
|
||
"distribusi Linux yang didukung dengan kernel terbaru dan paket rilis saat "
|
||
"ini."
|
||
|
||
msgid ""
|
||
"This section discusses which files and directories should be backed up "
|
||
"regularly, organized by service."
|
||
msgstr ""
|
||
"Bagian ini membahas file dan direktori mana yang harus didukung secara "
|
||
"teratur, yang diatur oleh layanan."
|
||
|
||
msgid ""
|
||
"This section provides guidance for rolling back to a previous release of "
|
||
"OpenStack. All distributions follow a similar procedure."
|
||
msgstr ""
|
||
"Bagian ini memberikan panduan untuk memutar kembali (rolling back) ke rilis "
|
||
"OpenStack sebelumnya. Semua distribusi mengikuti prosedur serupa."
|
||
|
||
msgid "This section provides tips on resolving common RabbitMQ issues."
|
||
msgstr ""
|
||
"Bagian ini memberikan tips untuk menyelesaikan masalah-masalah umum RabbitMQ."
|
||
|
||
msgid ""
|
||
"This step applies if you have already restarted only the OpenStack "
|
||
"components, and cannot connect to the RabbitMQ service."
|
||
msgstr ""
|
||
"Langkah ini berlaku jika Anda telah memulai kembali hanya komponen "
|
||
"OpenStack, dan tidak dapat terhubung ke layanan RabbitMQ."
|
||
|
||
msgid ""
|
||
"This step completes the rollback procedure. You should remove the upgrade "
|
||
"release repository and run :command:`apt-get update` to prevent accidental "
|
||
"upgrades until you solve whatever issue caused you to roll back your "
|
||
"environment."
|
||
msgstr ""
|
||
"Langkah ini melengkapi prosedur rollback. Anda harus menghapus repositori "
|
||
"rilis upgrade dan menjalankan :command:`apt-get update`untuk mencegah "
|
||
"upgrade yang tidak disengaja sampai Anda memecahkan masalah apa pun yang "
|
||
"menyebabkan Anda roll back lingkungan Anda."
|
||
|
||
msgid "This user was the only user on the node (new node)"
|
||
msgstr "Pengguna ini adalah satu-satunya pengguna pada node (node baru)"
|
||
|
||
msgid ""
|
||
"Thoroughly review the `release notes <https://releases.openstack.org/>`_ to "
|
||
"learn about new, updated, and deprecated features. Find incompatibilities "
|
||
"between versions."
|
||
msgstr ""
|
||
"Tinjau sepenuhnya `release notes <https://releases.openstack.org/>` _ untuk "
|
||
"mempelajari tentang fitur-fitur baru, yang diperbarui, dan usang. Temukan "
|
||
"ketidaksesuaian antar versi."
|
||
|
||
msgid ""
|
||
"Though many successfully use the various python-\\*client code as an "
|
||
"effective SDK for interacting with OpenStack, consistency between the "
|
||
"projects and documentation availability waxes and wanes. To combat this, an "
|
||
"`effort to improve the experience <https://wiki.openstack.org/wiki/"
|
||
"PythonOpenStackSDK>`_ has started. Cross-project development efforts in "
|
||
"OpenStack have a checkered history, such as the `unified client project "
|
||
"<https://wiki.openstack.org/wiki/OpenStackClient>`_ having several false "
|
||
"starts. However, the early signs for the SDK project are promising, and we "
|
||
"expect to see results during the Juno cycle."
|
||
msgstr ""
|
||
"Meskipun banyak yang berhasil menggunakan berbagai kode python-\\*client "
|
||
"sebagai SDK yang efektif untuk berinteraksi dengan OpenStack, konsistensi "
|
||
"antara proyek dan ketersediaan dokumentasi semakin berkurang. Untuk "
|
||
"mengatasi ini, sebuah `effort to improve the experience <https://wiki."
|
||
"openstack.org/wiki/PythonOpenStackSDK>`_ telah dimulai. Upaya pengembangan "
|
||
"lintas proyek di OpenStack memiliki sejarah kotak-kotak (checkered history), "
|
||
"seperti `unified client project <https://wiki.openstack.org/wiki/"
|
||
"OpenStackClient>`_ memiliki beberapa kesalahan awal. Namun, tanda-tanda awal "
|
||
"untuk proyek SDK cukup menjanjikan, dan kami berharap dapat melihat hasilnya "
|
||
"selama siklus Juno."
|
||
|
||
msgid ""
|
||
"Through ``nova-network`` or ``neutron``, OpenStack Compute automatically "
|
||
"manages iptables, including forwarding packets to and from instances on a "
|
||
"compute node, forwarding floating IP traffic, and managing security group "
|
||
"rules. In addition to managing the rules, comments (if supported) will be "
|
||
"inserted in the rules to help indicate the purpose of the rule."
|
||
msgstr ""
|
||
"Melalui ``nova-network`` atau ``neutron``, OpenStack Compute secara otomatis "
|
||
"mengelola iptables, termasuk meneruskan paket ke dan dari instance pada node "
|
||
"komputasi, meneruskan lalu lintas IP mengambang, dan mengatur aturan grup "
|
||
"keamanan. Selain mengelola aturan, komentar (jika didukung) akan dimasukkan "
|
||
"dalam aturan untuk membantu menunjukkan tujuan aturan."
|
||
|
||
msgid ""
|
||
"Tim Bell from CERN gave us feedback on the outline before we started and "
|
||
"reviewed it mid-week."
|
||
msgstr ""
|
||
"Tim Bell dari CERN memberi kami umpan balik tentang garis besar sebelum kami "
|
||
"memulai dan meninjaunya pertengahan minggu."
|
||
|
||
msgid ""
|
||
"To access the instance's disk (``/var/lib/nova/instances/instance-xxxxxx/"
|
||
"disk``), use the following steps:"
|
||
msgstr ""
|
||
"Untuk mengakses disk instance (``/var/lib/nova/instances/instance-xxxxxx/"
|
||
"disk``), gunakan langkah-langkah berikut:"
|
||
|
||
msgid "To add a DEBUG logging statement, you would do:"
|
||
msgstr "Untuk menambahkan pernyataan logging DEBUG, Anda harus melakukan:"
|
||
|
||
msgid ""
|
||
"To add a project through the command line, you must use the OpenStack "
|
||
"command line client."
|
||
msgstr ""
|
||
"Untuk menambahkan proyek melalui command line, Anda harus menggunakan klien "
|
||
"command line OpenStack."
|
||
|
||
msgid ""
|
||
"To add logging statements, the following line should be near the top of the "
|
||
"file. For most files, these should already be there:"
|
||
msgstr ""
|
||
"Untuk menambahkan pernyataan logging, baris berikut harus di dekat bagian "
|
||
"atas file. Untuk sebagian besar file, ini seharusnya sudah ada:"
|
||
|
||
msgid "To address this issue:"
|
||
msgstr "Untuk mengatasi masalah ini:"
|
||
|
||
msgid "To apply or update account quotas on a project:"
|
||
msgstr "Untuk menerapkan atau memperbarui kuota akun pada suatu proyek:"
|
||
|
||
msgid ""
|
||
"To avoid this situation, create a highly available cloud controller cluster. "
|
||
"This is outside the scope of this document, but you can read more in the "
|
||
"`OpenStack High Availability Guide <https://docs.openstack.org/ha-guide/"
|
||
"index.html>`_."
|
||
msgstr ""
|
||
"Untuk menghindari situasi ini, buat kluster pengendali cloud yang sangat "
|
||
"tersedia. Ini di luar ruang lingkup dokumen ini, tetapi Anda dapat membaca "
|
||
"lebih lanjut di `OpenStack High Availability Guide <https://docs.openstack."
|
||
"org/ha-guide/index.html>`_."
|
||
|
||
msgid ""
|
||
"To begin, configure all OpenStack components to log to the syslog log file "
|
||
"in addition to their standard log file location. Also, configure each "
|
||
"component to log to a different syslog facility. This makes it easier to "
|
||
"split the logs into individual components on the central server:"
|
||
msgstr ""
|
||
"Untuk memulai, konfigurasikan semua komponen OpenStack untuk masuk ke file "
|
||
"log syslog di samping lokasi file log standar mereka. Juga, konfigurasikan "
|
||
"setiap komponen untuk masuk ke fasilitas syslog yang berbeda. Ini membuatnya "
|
||
"lebih mudah untuk membagi log menjadi komponen-komponen tersendiri di server "
|
||
"pusat:"
|
||
|
||
msgid ""
|
||
"To create a development environment, you can use DevStack. DevStack is "
|
||
"essentially a collection of shell scripts and configuration files that "
|
||
"builds an OpenStack development environment for you. You use it to create "
|
||
"such an environment for developing a new feature."
|
||
msgstr ""
|
||
"Untuk membuat lingkungan pengembangan, Anda dapat menggunakan DevStack. "
|
||
"DevStack pada dasarnya adalah kumpulan skrip shell dan file konfigurasi yang "
|
||
"membangun lingkungan pengembangan OpenStack untuk Anda. Anda menggunakannya "
|
||
"untuk membuat lingkungan seperti itu untuk mengembangkan fitur baru."
|
||
|
||
msgid "To create a project through the OpenStack dashboard:"
|
||
msgstr "Untuk membuat proyek melalui dasbor OpenStack:"
|
||
|
||
msgid ""
|
||
"To create a scheduler, you must inherit from the class ``nova.scheduler."
|
||
"driver.Scheduler``. Of the five methods that you can override, you *must* "
|
||
"override the two methods marked with an asterisk (\\*) below:"
|
||
msgstr ""
|
||
"Untuk membuat penjadwal, Anda harus mewarisi dari kelas ``nova.scheduler."
|
||
"driver.Scheduler``. Dari lima metode yang dapat Anda timpa, Anda *must* "
|
||
"mengganti dua metode yang ditandai dengan tanda bintang (\\*) di bawah ini:"
|
||
|
||
msgid ""
|
||
"To demonstrate customizing OpenStack, we'll create an example of a Compute "
|
||
"scheduler that randomly places an instance on a subset of hosts, depending "
|
||
"on the originating IP address of the request and the prefix of the hostname. "
|
||
"Such an example could be useful when you have a group of users on a subnet "
|
||
"and you want all of their instances to start within some subset of your "
|
||
"hosts."
|
||
msgstr ""
|
||
"Untuk mendemonstrasikan penyesuaian OpenStack, kami akan membuat contoh "
|
||
"penjadwal Compute yang secara acak menempatkan instance pada subset host, "
|
||
"tergantung pada alamat IP asal permintaan dan awalan nama host. Contoh "
|
||
"seperti itu bisa berguna ketika Anda memiliki sekelompok pengguna di subnet "
|
||
"dan Anda ingin semua instance mereka dimulai dalam beberapa subset dari host "
|
||
"Anda."
|
||
|
||
msgid ""
|
||
"To determine the potential features going in to future releases, or to look "
|
||
"at features implemented previously, take a look at the existing blueprints "
|
||
"such as `OpenStack Compute (nova) Blueprints <https://blueprints.launchpad."
|
||
"net/nova>`_, `OpenStack Identity (keystone) Blueprints <https://blueprints."
|
||
"launchpad.net/keystone>`_, and release notes."
|
||
msgstr ""
|
||
"Untuk menentukan fitur potensial yang masuk ke rilis mendatang, atau untuk "
|
||
"melihat fitur yang diterapkan sebelumnya, lihat cetak biru yang ada seperti "
|
||
"`OpenStack Compute (nova) Blueprints <https://blueprints.launchpad.net/"
|
||
"nova>`_, `OpenStack Identity (keystone) Blueprints <https://blueprints."
|
||
"launchpad.net/keystone>`_, dan catatan rilis."
|
||
|
||
msgid ""
|
||
"To disable DEBUG-level logging, edit ``/etc/nova/nova.conf`` file as follows:"
|
||
msgstr ""
|
||
"Untuk menonaktifkan logging tingkat DEBUG, edit file ``/etc/nova/nova.conf`` "
|
||
"sebagai berikut:"
|
||
|
||
msgid ""
|
||
"To discover how API requests should be structured, read the `OpenStack API "
|
||
"Reference <https://developer.openstack.org/api-guide/quick-start/index."
|
||
"html>`_. To chew through the responses using jq, see the `jq Manual <http://"
|
||
"stedolan.github.io/jq/manual/>`_."
|
||
msgstr ""
|
||
"Untuk mengetahui bagaimana permintaan API harus disusun, baca `OpenStack API "
|
||
"Reference <https://developer.openstack.org/api-guide/quick-start/index."
|
||
"html>`_. Untuk mengunyah tanggapan menggunakan jq, lihat `jq Manual <http://"
|
||
"stedolan.github.io/jq/manual/>`_."
|
||
|
||
msgid ""
|
||
"To do this, generate a list of instance UUIDs that are hosted on the failed "
|
||
"node by running the following query on the nova database:"
|
||
msgstr ""
|
||
"Untuk melakukan ini, buat daftar instance UUID yang di-host pada node gagal "
|
||
"dengan menjalankan query berikut pada database nova:"
|
||
|
||
msgid ""
|
||
"To enable nova to send notifications, add the following to the ``nova.conf`` "
|
||
"configuration file:"
|
||
msgstr ""
|
||
"Untuk mengaktifkan nova untuk mengirim pemberitahuan, tambahkan berikut ini "
|
||
"ke file konfigurasi ``nova.conf``:"
|
||
|
||
msgid ""
|
||
"To enable this feature, edit the ``/etc/glance/glance-api.conf`` file, and "
|
||
"under the ``[DEFAULT]`` section, add:"
|
||
msgstr ""
|
||
"Untuk mengaktifkan fitur ini, edit file ``/etc/glance/glance-api.conf``, dan "
|
||
"di bawah bagian ``[DEFAULT] ``, tambahkan:"
|
||
|
||
msgid ""
|
||
"To examine the secondary or ephemeral disk, use an alternate mount point if "
|
||
"you want both primary and secondary drives mounted at the same time:"
|
||
msgstr ""
|
||
"Untuk memeriksa disk sekunder atau sementara, gunakan titik pemasangan "
|
||
"alternatif jika Anda ingin drive primer dan sekunder dipasang pada saat yang "
|
||
"bersamaan:"
|
||
|
||
msgid "To find out whether any floating IPs are available in your cloud, run:"
|
||
msgstr ""
|
||
"Untuk mengetahui apakah IP mengambang tersedia di cloud Anda, jalankan:"
|
||
|
||
msgid ""
|
||
"To help understand how OpenStack works, this section describes the end-to-"
|
||
"end process and interaction of components when provisioning an instance on "
|
||
"OpenStack."
|
||
msgstr ""
|
||
"Untuk membantu memahami cara kerja OpenStack, bagian ini menjelaskan proses "
|
||
"uend-to-end dan interaksi komponen ketika menyediakan instance pada "
|
||
"OpenStack."
|
||
|
||
msgid ""
|
||
"To list the bridges on a system, use :command:`ovs-vsctl list-br`. This "
|
||
"example shows a compute node that has an internal bridge and a tunnel "
|
||
"bridge. VLAN networks are trunked through the ``eth1`` network interface:"
|
||
msgstr ""
|
||
"Untuk daftar jembatan pada suatu sistem, gunakan :command:`ovs-vsctl list-"
|
||
"br`. . Contoh ini menunjukkan node komputasi yang memiliki jembatan internal "
|
||
"dan jembatan terowongan. Jaringan VLAN trunked melalui antarmuka jaringan "
|
||
"``eth1``:"
|
||
|
||
msgid ""
|
||
"To make working with subsequent requests easier, store the token in an "
|
||
"environment variable:"
|
||
msgstr ""
|
||
"Untuk membuat bekerja dengan permintaan berikutnya lebih mudah, simpan token "
|
||
"dalam variabel lingkungan:"
|
||
|
||
msgid ""
|
||
"To plug this middleware into the swift Paste pipeline, you edit one "
|
||
"configuration file, ``/etc/swift/proxy-server.conf``:"
|
||
msgstr ""
|
||
"Untuk menghubungkan middleware ini ke swift Paste pipeline, Anda mengedit "
|
||
"satu file konfigurasi, ``/etc/swift/proxy-server.conf``:"
|
||
|
||
msgid ""
|
||
"To plug this scheduler into nova, edit one configuration file, ``/etc/nova/"
|
||
"nova.conf``:"
|
||
msgstr ""
|
||
"Untuk menghubungkan penjadwal ini ke nova, edit satu file konfigurasi, ``/"
|
||
"etc/nova/nova.conf``:"
|
||
|
||
msgid ""
|
||
"To prevent system capacities from being exhausted without notification, you "
|
||
"can set up :term:`quotas <quota>`. Quotas are operational limits. For "
|
||
"example, the number of gigabytes allowed per tenant can be controlled to "
|
||
"ensure that a single tenant cannot consume all of the disk space. Quotas are "
|
||
"currently enforced at the tenant (or project) level, rather than the user "
|
||
"level."
|
||
msgstr ""
|
||
"Agar kapasitas sistem tidak kehabisan tanpa pemberitahuan, Anda dapat "
|
||
"mengatur :term:`quotas <quota>`. Kuota adalah batasan operasional. Misalnya, "
|
||
"jumlah gigabyte yang diizinkan per penyewa dapat dikontrol untuk memastikan "
|
||
"bahwa penyewa tunggal tidak dapat mengkonsumsi semua ruang disk. Kuota saat "
|
||
"ini ditegakkan di tingkat penyewa (atau proyek), daripada tingkat pengguna."
|
||
|
||
msgid ""
|
||
"To provide a chain of trust from an end user to the Image service, and the "
|
||
"Image service to Compute, an end user can import signed images that can be "
|
||
"initially verified in the Image service, and later verified in the Compute "
|
||
"service. Appropriate Image service properties need to be set to enable this "
|
||
"signature feature."
|
||
msgstr ""
|
||
"Untuk memberikan rantai kepercayaan dari end user ke layanan Image, dan "
|
||
"layanan Image untuk Compute, end user dapat mengimpor signed image yang pada "
|
||
"awalnya dapat diverifikasi dalam layanan Image, dan kemudian diverifikasi "
|
||
"dalam layanan Compute. Properti layanan Image yang tepat perlu diatur untuk "
|
||
"mengaktifkan fitur signature ini."
|
||
|
||
msgid ""
|
||
"To put the EC2 credentials into your environment, source the ``ec2rc.sh`` "
|
||
"file."
|
||
msgstr ""
|
||
"Untuk memasukkan kredensial EC2 ke lingkungan Anda, sumber file ``ec2rc.sh``."
|
||
|
||
msgid "To schedule a group of hosts with common features."
|
||
msgstr "Untuk menjadwalkan sekelompok host dengan fitur-fitur umum."
|
||
|
||
msgid "To see a list of projects that have been added to the cloud, run:"
|
||
msgstr "Untuk melihat daftar proyek yang telah ditambahkan ke cloud, jalankan:"
|
||
|
||
msgid "To see a list of running instances, run:"
|
||
msgstr "Untuk melihat daftar instance yang berjalan, jalankan:"
|
||
|
||
msgid "To see a list of users, run:"
|
||
msgstr "Untuk melihat daftar pengguna, jalankan:"
|
||
|
||
msgid "To see whether you are using namespaces, run :command:`ip netns`:"
|
||
msgstr ""
|
||
"Untuk melihat apakah Anda menggunakan namespace, jalankan :command:`ip "
|
||
"netns`:"
|
||
|
||
msgid "To see which bridge the packet will use, run the command:"
|
||
msgstr ""
|
||
"Untuk melihat bridge mana yang akan digunakan paket, jalankan perintah:"
|
||
|
||
msgid ""
|
||
"To see which fixed IP networks are configured in your cloud, you can use "
|
||
"the :command:`openstack` command-line client to get the IP ranges:"
|
||
msgstr ""
|
||
"Untuk melihat jaringan IP tetap mana yang dikonfigurasikan di cloud Anda, "
|
||
"Anda dapat menggunakan klien command-line :command:`openstack` untuk "
|
||
"mendapatkan rentang IP:"
|
||
|
||
msgid ""
|
||
"To set a configuration option to zero, include a line such as "
|
||
"``image_cache_manager_interval=0`` in your ``nova.conf`` file."
|
||
msgstr ""
|
||
"Untuk mengatur opsi konfigurasi ke nol, sertakan baris seperti file "
|
||
"``image_cache_manager_interval=0`` in your ``nova.conf``."
|
||
|
||
msgid "To set up the test environment, you can use one of several methods:"
|
||
msgstr ""
|
||
"Untuk mengatur lingkungan pengujian, Anda dapat menggunakan salah satu dari "
|
||
"beberapa metode:"
|
||
|
||
msgid ""
|
||
"To take advantage of either container quotas or account quotas, your Object "
|
||
"Storage proxy server must have ``container_quotas`` or ``account_quotas`` "
|
||
"(or both) added to the ``[pipeline:main]`` pipeline. Each quota type also "
|
||
"requires its own section in the ``proxy-server.conf`` file:"
|
||
msgstr ""
|
||
"Untuk memanfaatkan kuota container atau kuota akun, server proksi Object "
|
||
"Storage Anda harus memiliki ``container_quotas`` atau ``account_quotas`` "
|
||
"(atau keduanya) ditambahkan ke pipaline ``[pipeline: main] ``. Setiap jenis "
|
||
"kuota juga memerlukan bagiannya sendiri di file ``proxy-server.conf``:"
|
||
|
||
msgid ""
|
||
"To take the first path, you can modify the OpenStack code directly. Learn "
|
||
"`how to contribute <https://wiki.openstack.org/wiki/How_To_Contribute>`_, "
|
||
"follow the `Developer's Guide <https://docs.openstack.org/infra/manual/"
|
||
"developers.html>`_, make your changes, and contribute them back to the "
|
||
"upstream OpenStack project. This path is recommended if the feature you need "
|
||
"requires deep integration with an existing project. The community is always "
|
||
"open to contributions and welcomes new functionality that follows the "
|
||
"feature-development guidelines. This path still requires you to use DevStack "
|
||
"for testing your feature additions, so this chapter walks you through the "
|
||
"DevStack environment."
|
||
msgstr ""
|
||
"Untuk mengambil jalur pertama, Anda dapat memodifikasi kode OpenStack secara "
|
||
"langsung. Belajar `how to contribute <https://wiki.openstack.org/wiki/"
|
||
"How_To_Contribute>`_, ikuti `Developer's Guide <https://docs.openstack.org/"
|
||
"infra/manual/developers.html>`_, buat perubahan Anda, dan kontribusikan "
|
||
"kembali ke proyek OpenStack hulu. Jalur ini disarankan jika fitur yang Anda "
|
||
"butuhkan memerlukan integrasi yang mendalam dengan proyek yang ada. "
|
||
"Komunitas selalu terbuka untuk kontribusi dan menyambut fungsionalitas baru "
|
||
"yang mengikuti panduan pengembangan fitur. Jalur ini masih mengharuskan Anda "
|
||
"untuk menggunakan DevStack untuk menguji penambahan fitur Anda, jadi bab ini "
|
||
"menuntun Anda melalui lingkungan DevStack."
|
||
|
||
msgid ""
|
||
"To this day, `the issue <https://bugs.launchpad.net/nova/+bug/832507>`__ "
|
||
"doesn't have a permanent resolution, but we look forward to the discussion "
|
||
"at the next summit."
|
||
msgstr ""
|
||
"Sampai hari ini, `the issue <https://bugs.launchpad.net/nova/+bug/832507>`__ "
|
||
"tidak memiliki resolusi permanen, tetapi kami menantikan diskusi di "
|
||
"pertemuan berikutnya."
|
||
|
||
msgid ""
|
||
"To update a default value for a new tenant, update the property in the ``/"
|
||
"etc/cinder/cinder.conf`` file."
|
||
msgstr ""
|
||
"Untuk memperbarui nilai default untuk penyewa baru, perbarui properti di "
|
||
"file ``/etc/cinder/cinder.conf``."
|
||
|
||
msgid ""
|
||
"To update a service on each node, you generally modify one or more "
|
||
"configuration files, stop the service, synchronize the database schema, and "
|
||
"start the service. Some services require different steps. We recommend "
|
||
"verifying operation of each service before proceeding to the next service."
|
||
msgstr ""
|
||
"Untuk update layanan pada setiap node, Anda biasanya memodifikasi satu atau "
|
||
"lebih file konfigurasi, menghentikan layanan, menyinkronkan skema database, "
|
||
"dan memulai layanan. Beberapa layanan memerlukan langkah-langkah berbeda. "
|
||
"Kami merekomendasikan verifikasi operasi setiap layanan sebelum melanjutkan "
|
||
"ke layanan berikutnya."
|
||
|
||
msgid "To verify the quota, run the :command:`swift stat` command again:"
|
||
msgstr ""
|
||
"Untuk memverifikasi kuota, jalankan kembali perintah :command:`swift stat``:"
|
||
|
||
msgid "To view a list of options for the ``nova quota-update`` command, run:"
|
||
msgstr ""
|
||
"Untuk melihat daftar opsi untuk perintah ``nova quota-update``, jalankan:"
|
||
|
||
msgid "To view account quotas placed on a project:"
|
||
msgstr "Untuk melihat kuota akun yang ditempatkan pada proyek:"
|
||
|
||
msgid "To view all tenants, run:"
|
||
msgstr "Untuk melihat semua penyewa, jalankan:"
|
||
|
||
msgid ""
|
||
"To view and update Object Storage quotas, use the :command:`swift` command "
|
||
"provided by the ``python-swiftclient`` package. Any user included in the "
|
||
"project can view the quotas placed on their project. To update Object "
|
||
"Storage quotas on a project, you must have the role of ResellerAdmin in the "
|
||
"project that the quota is being applied to."
|
||
msgstr ""
|
||
"Untuk melihat dan memperbarui kuota Object Storage, gunakan perintah :"
|
||
"command:`swift` yang disediakan oleh paket ``python-swiftclient``. Setiap "
|
||
"pengguna yang termasuk dalam proyek dapat melihat kuota yang ditempatkan "
|
||
"pada proyek mereka. Untuk memperbarui kuota Object Storage pada proyek, Anda "
|
||
"harus memiliki peran ResellerAdmin dalam proyek yang sedang diterapkan kuota."
|
||
|
||
msgid "Tools for automated neutron diagnosis"
|
||
msgstr "Alat untuk diagnosis neutron otomatis"
|
||
|
||
msgid "Topics to consider include:"
|
||
msgstr "Topik yang perlu dipertimbangkan meliputi:"
|
||
|
||
msgid "Total Cloud Controller Failure"
|
||
msgstr "Total Kegagalan Pengontrol Cloud"
|
||
|
||
msgid "Total Compute Node Failure"
|
||
msgstr "kegagalan total Compute Node"
|
||
|
||
msgid "Toward a Python SDK"
|
||
msgstr "Menuju SDK Python"
|
||
|
||
msgid "Tracing Instance Requests"
|
||
msgstr "Melacak Permintaan Instance"
|
||
|
||
msgid "Trending"
|
||
msgstr "Tren"
|
||
|
||
msgid ""
|
||
"Trending can give you great insight into how your cloud is performing day to "
|
||
"day. You can learn, for example, if a busy day was simply a rare occurrence "
|
||
"or if you should start adding new compute nodes."
|
||
msgstr ""
|
||
"Tren dapat memberi Anda wawasan hebat tentang kinerja cloud Anda dari hari "
|
||
"ke hari. Anda dapat belajar, misalnya, jika hari yang sibuk hanyalah "
|
||
"kejadian langka atau jika Anda harus mulai menambahkan node komputasi baru."
|
||
|
||
msgid ""
|
||
"Trending takes a slightly different approach than alerting. While alerting "
|
||
"is interested in a binary result (whether a check succeeds or fails), "
|
||
"trending records the current state of something at a certain point in time. "
|
||
"Once enough points in time have been recorded, you can see how the value has "
|
||
"changed over time."
|
||
msgstr ""
|
||
"Tren mengambil pendekatan yang sedikit berbeda dari yang mengingatkan. "
|
||
"Sementara peringatan tertarik pada hasil biner (apakah cek berhasil atau "
|
||
"gagal), tren mencatat kondisi saat ini dari sesuatu pada titik waktu "
|
||
"tertentu. Setelah titik waktu yang cukup telah dicatat, Anda dapat melihat "
|
||
"bagaimana nilainya berubah dari waktu ke waktu."
|
||
|
||
msgid "Troubleshooting Open vSwitch"
|
||
msgstr "Pemecahan masalah Open vSwitch"
|
||
|
||
msgid ""
|
||
"Try executing the :command:`openstack server reboot` command again. You "
|
||
"should see an error message about why the instance was not able to boot."
|
||
msgstr ""
|
||
"Coba jalankan perintah :command:`openstack server reboot` lagi. Anda akan "
|
||
"melihat pesan kesalahan tentang mengapa instance tidak bisa boot."
|
||
|
||
msgid ""
|
||
"Typically reduce the threat level by informing potential attackers that "
|
||
"there will be adverse consequences for them if they proceed."
|
||
msgstr ""
|
||
"Biasanya mengurangi tingkat ancaman dengan memberi tahu penyerang potensial "
|
||
"bahwa akan ada konsekuensi yang merugikan bagi mereka jika mereka "
|
||
"melanjutkan."
|
||
|
||
msgid ""
|
||
"Typically, default values are changed because a tenant requires more than "
|
||
"the OpenStack default of 10 volumes per tenant, or more than the OpenStack "
|
||
"default of 1 TB of disk space on a compute node."
|
||
msgstr ""
|
||
"Biasanya, nilai standar diubah karena penyewa membutuhkan lebih dari standar "
|
||
"OpenStack 10 volume per penyewa, atau lebih dari standar OpenStack 1 TB "
|
||
"ruang disk pada node komputasi."
|
||
|
||
msgid ""
|
||
"Ubuntu 12.04 installs RabbitMQ version 2.7.1, which uses port 55672. "
|
||
"RabbitMQ versions 3.0 and above use port 15672 instead. You can check which "
|
||
"version of RabbitMQ you have running on your local Ubuntu machine by doing:"
|
||
msgstr ""
|
||
"Ubuntu 12.04 menginstal RabbitMQ versi 2.7.1, yang menggunakan port 55672. "
|
||
"Sebaliknya, RabbitMQ versi 3.0 dan di atasnya menggunakan port 15672. Anda "
|
||
"dapat memeriksa versi RabbitMQ mana yang telah Anda jalankan di mesin Ubuntu "
|
||
"lokal Anda dengan melakukan:"
|
||
|
||
msgid "Under Identity tab, click :guilabel:`Projects`."
|
||
msgstr "Di bawah tab Identity, klik :guilabel:`Projects`."
|
||
|
||
msgid ""
|
||
"Underlying the use of the command-line tools is the OpenStack API, which is "
|
||
"a RESTful API that runs over HTTP. There may be cases where you want to "
|
||
"interact with the API directly or need to use it because of a suspected bug "
|
||
"in one of the CLI tools. The best way to do this is to use a combination "
|
||
"of `cURL <https://curl.haxx.se/>`_ and another tool, such as `jq <http://"
|
||
"stedolan.github.io/jq/>`_, to parse the JSON from the responses."
|
||
msgstr ""
|
||
"Yang mendasari penggunaan alat command-line adalah OpenStack API, yang "
|
||
"merupakan RESTful API yang berjalan di atas HTTP. Mungkin ada kasus di mana "
|
||
"Anda ingin berinteraksi dengan API secara langsung atau perlu menggunakannya "
|
||
"karena bug yang dicurigai di salah satu alat CLI. Cara terbaik untuk "
|
||
"melakukan ini adalah dengan menggunakan kombinasi `cURL <https://curl.haxx."
|
||
"se/>`_ dan alat lain, seperti `jq <http://stedolan.github.io/jq/>`_, untuk "
|
||
"mengurai JSON dari tanggapan."
|
||
|
||
msgid ""
|
||
"Unfortunately, sometimes the error is not apparent from the log files. In "
|
||
"this case, switch tactics and use a different command; maybe run the service "
|
||
"directly on the command line. For example, if the ``glance-api`` service "
|
||
"refuses to start and stay running, try launching the daemon from the command "
|
||
"line:"
|
||
msgstr ""
|
||
"Sayangnya, terkadang kesalahan tidak terlihat dari file log. Dalam hal ini, "
|
||
"alihkan taktik dan gunakan perintah yang berbeda; mungkin menjalankan "
|
||
"layanan langsung pada command line. Misalnya, jika layanan ``glance-api`` "
|
||
"menolak untuk memulai dan tetap berjalan, coba luncurkan daemon dari command "
|
||
"line:"
|
||
|
||
msgid ""
|
||
"Unfortunately, this command does not tell you various details about the "
|
||
"running instances, such as what compute node the instance is running on, "
|
||
"what flavor the instance is, and so on. You can use the following command to "
|
||
"view details about individual instances:"
|
||
msgstr ""
|
||
"Sayangnya, perintah ini tidak memberi tahu Anda berbagai perincian tentang "
|
||
"instance yang sedang berjalan, seperti apa yang komputasi node instance yang "
|
||
"sedang berjalan, apa flavor instance itu, dan sebagainya. Anda dapat "
|
||
"menggunakan perintah berikut untuk melihat detail tentang setiap kejadian:"
|
||
|
||
msgid ""
|
||
"Unfortunately, this story has an open ending... we're still looking into why "
|
||
"the CentOS image was sending out spanning tree packets. Further, we're "
|
||
"researching a proper way on how to mitigate this from happening. It's a "
|
||
"bigger issue than one might think. While it's extremely important for "
|
||
"switches to prevent spanning tree loops, it's very problematic to have an "
|
||
"entire compute node be cut from the network when this happens. If a compute "
|
||
"node is hosting 100 instances and one of them sends a spanning tree packet, "
|
||
"that instance has effectively DDOS'd the other 99 instances."
|
||
msgstr ""
|
||
"Sayangnya, cerita ini memiliki akhiran yang terbuka ... kita masih mencari "
|
||
"tahu mengapa image CentOS mengirim paket spanning tree. Lebih lanjut, kami "
|
||
"sedang meneliti cara yang tepat tentang bagaimana mengurangi hal ini "
|
||
"terjadi. Ini masalah yang lebih besar dari yang mungkin dipikirkan. Meskipun "
|
||
"sangat penting bagi switch untuk mencegah spanning tree loop, sangat "
|
||
"problematis untuk membuat seluruh node komputasi dipotong dari jaringan saat "
|
||
"ini terjadi. Jika sebuah node komputasi menampung 100 instance dan salah "
|
||
"satunya mengirimkan paket spanning tree, instance tersebut secara efektif "
|
||
"telah melakukan DDOS terhadap 99 instance lainnya."
|
||
|
||
msgid "Uninstalling"
|
||
msgstr "Uninstalling (menghapus instalasi)"
|
||
|
||
msgid ""
|
||
"Unlike having a single API endpoint, regions have a separate API endpoint "
|
||
"per installation, allowing for a more discrete separation. Users wanting to "
|
||
"run instances across sites have to explicitly select a region. However, the "
|
||
"additional complexity of a running a new service is not required."
|
||
msgstr ""
|
||
"Tidak seperti memiliki satu endpoint API, kawasan memiliki endpoint API "
|
||
"terpisah per pemasangan, memungkinkan pemisahan yang lebih terpisah. "
|
||
"Pengguna yang ingin menjalankan instance di situs harus secara eksplisit "
|
||
"memilih suatu wilayah. Namun, kompleksitas tambahan menjalankan layanan baru "
|
||
"tidak diperlukan."
|
||
|
||
msgid ""
|
||
"Unlike the CLI tools mentioned above, the :command:`*-manage` tools must be "
|
||
"run from the cloud controller, as root, because they need read access to the "
|
||
"config files such as ``/etc/nova/nova.conf`` and to make queries directly "
|
||
"against the database rather than against the OpenStack :term:`API endpoints "
|
||
"<API endpoint>`."
|
||
msgstr ""
|
||
"Tidak seperti alat CLI yang disebutkan di atas, :command:`*-manage` tools "
|
||
"harus dijalankan dari pengendali cloud, sebagai root, karena mereka "
|
||
"membutuhkan akses baca ke file konfigurasi seperti ``/etc/nova/nova.conf`` "
|
||
"dan untuk membuat pertanyaan langsung terhadap basis data dan bukan terhadap "
|
||
"OpenStack :term:`API endpoints <API endpoint>`."
|
||
|
||
msgid "Unmount the device after inspecting."
|
||
msgstr "Lepaskan (unmount) perangkat setelah memeriksa."
|
||
|
||
msgid "Update a particular quota value, as follows:"
|
||
msgstr "Perbarui nilai kuota tertentu, sebagai berikut:"
|
||
|
||
msgid ""
|
||
"Update all ``.ini`` files to match passwords and pipelines as required for "
|
||
"the OpenStack release in your environment."
|
||
msgstr ""
|
||
"Update semua file ``.ini`` untuk mencocokkan kata sandi dan pipeline "
|
||
"seperti yang diperlukan untuk rilis OpenStack di lingkungan Anda."
|
||
|
||
msgid "Update services"
|
||
msgstr "Update layanan"
|
||
|
||
msgid "Update the new port with the IPv4 address:"
|
||
msgstr "Perbarui port baru dengan alamat IPv4:"
|
||
|
||
msgid "Update the repository database."
|
||
msgstr "Update basis data repositori."
|
||
|
||
msgid "Upgrade Levels"
|
||
msgstr "Tingkat Upgrade"
|
||
|
||
msgid "Upgrade OpenStack."
|
||
msgstr "Tingkatkan OpenStack."
|
||
|
||
msgid ""
|
||
"Upgrade levels are a feature added to OpenStack Compute since the Grizzly "
|
||
"release to provide version locking on the RPC (Message Queue) communications "
|
||
"between the various Compute services."
|
||
msgstr ""
|
||
"Tingkat upgrade adalah fitur yang ditambahkan ke OpenStack Compute sejak "
|
||
"rilis Grizzly untuk menyediakan penguncian versi pada komunikasi RPC "
|
||
"(Message Queue) antara berbagai layanan Compute."
|
||
|
||
msgid "Upgrade packages on each node"
|
||
msgstr "Upgrade paket pada setiap node"
|
||
|
||
msgid "Upgrade planning"
|
||
msgstr "Upgrade perencanaan"
|
||
|
||
msgid "Upgrade process"
|
||
msgstr "Proses Upgrade"
|
||
|
||
msgid "Upgrades"
|
||
msgstr "Upgrade"
|
||
|
||
msgid "Upload Certificate in DER format to Castellan"
|
||
msgstr "Unggah Sertifikat dalam format DER ke Castellan"
|
||
|
||
msgid "Upload Image to Image service, with Signature Metadata"
|
||
msgstr "Unggah Image ke layanan Image, dengan Signature Metadata"
|
||
|
||
msgid "Use Cases"
|
||
msgstr "Use Case (kasus penggunaan)"
|
||
|
||
msgid ""
|
||
"Use ``openstack-nova-network`` on RHEL/CentOS/Fedora but ``nova-network`` on "
|
||
"Ubuntu/Debian."
|
||
msgstr ""
|
||
"Gunakan ``openstack-nova-network`` di RHEL / CentOS / Fedora tetapi ``nova-"
|
||
"network`` di Ubuntu / Debian."
|
||
|
||
msgid "Use a public cloud"
|
||
msgstr "Gunakan cloud publik"
|
||
|
||
msgid ""
|
||
"Use ping to quickly find where a failure exists in the network path. In an "
|
||
"instance, first see whether you can ping an external host, such as google."
|
||
"com. If you can, then there shouldn't be a network problem at all."
|
||
msgstr ""
|
||
"Gunakan ping untuk menemukan dengan cepat di mana ada kegagalan di jalur "
|
||
"jaringan. Dalam sebuah instance, pertama-tama lihat apakah Anda dapat "
|
||
"melakukan ping host eksternal, seperti google.com. Jika Anda bisa, maka "
|
||
"seharusnya tidak ada masalah jaringan sama sekali."
|
||
|
||
msgid "Use private key to create a signature of the image"
|
||
msgstr "Gunakan private key untuk membuat signature of image"
|
||
|
||
msgid ""
|
||
"Use the :command:`apt-get install` command to install specific versions of "
|
||
"each package by specifying ``<package-name>=<version>``. The script in the "
|
||
"previous step conveniently created a list of ``package=version`` pairs for "
|
||
"you:"
|
||
msgstr ""
|
||
"Gunakan perintah :command:`apt-get install` untuk menginstal versi spesifik "
|
||
"dari setiap paket dengan menentukan ``<package-name>=<version>``. Script "
|
||
"pada langkah sebelumnya dengan mudah membuat daftar pasangan "
|
||
"``package=version`` untuk Anda:"
|
||
|
||
msgid "Use the port when creating an instance:"
|
||
msgstr "Gunakan port saat membuat instance:"
|
||
|
||
msgid ""
|
||
"Use this example priority list to ensure that user-affected services are "
|
||
"restored as soon as possible, but not before a stable environment is in "
|
||
"place. Of course, despite being listed as a single-line item, each step "
|
||
"requires significant work. For example, just after starting the database, "
|
||
"you should check its integrity, or, after starting the nova services, you "
|
||
"should verify that the hypervisor matches the database and fix any "
|
||
"mismatches."
|
||
msgstr ""
|
||
"Gunakan contoh daftar prioritas ini untuk memastikan bahwa layanan yang "
|
||
"dipengaruhi pengguna dipulihkan sesegera mungkin, tetapi tidak sebelum "
|
||
"lingkungan yang stabil ada. Tentu saja, meskipun terdaftar sebagai item "
|
||
"baris tunggal, setiap langkah membutuhkan pekerjaan yang signifikan. "
|
||
"Misalnya, tepat setelah memulai database, Anda harus memeriksa "
|
||
"integritasnya, atau, setelah memulai layanan nova, Anda harus memverifikasi "
|
||
"bahwa hypervisor cocok dengan database dan memperbaiki ketidakcocokan."
|
||
|
||
msgid "Use your own cloud"
|
||
msgstr "Gunakan cloud Anda sendiri"
|
||
|
||
msgid ""
|
||
"User authentication requests include sensitive information including "
|
||
"usernames, passwords, and authentication tokens. It is strongly recommended "
|
||
"to place API services behind hardware that performs SSL termination."
|
||
msgstr ""
|
||
"Permintaan otentikasi pengguna mencakup informasi sensitif termasuk nama "
|
||
"pengguna, kata sandi, dan token otentikasi. Sangat disarankan untuk "
|
||
"menempatkan layanan API di belakang perangkat keras yang melakukan "
|
||
"penghentian SSL."
|
||
|
||
msgid "User quotas"
|
||
msgstr "Kuota pengguna"
|
||
|
||
msgid "User virtual machines"
|
||
msgstr "Mesin virtual pengguna"
|
||
|
||
msgid "User-Facing Operations"
|
||
msgstr "Operasi Menghadapi Pengguna"
|
||
|
||
msgid "Users and Projects"
|
||
msgstr "Pengguna dan Proyek"
|
||
|
||
msgid ""
|
||
"Users and groups are managed through Active Directory and imported into the "
|
||
"Identity service using LDAP. CLIs are available for nova and Euca2ools to do "
|
||
"this."
|
||
msgstr ""
|
||
"Pengguna dan grup dikelola melalui Active Directory dan diimpor ke layanan "
|
||
"Identity menggunakan LDAP. CLI tersedia untuk nova dan Euca2ools untuk "
|
||
"melakukan ini."
|
||
|
||
msgid ""
|
||
"Users being able to retrieve console logs from running instances is a boon "
|
||
"for support—many times they can figure out what's going on inside their "
|
||
"instance and fix what's going on without bothering you. Unfortunately, "
|
||
"sometimes overzealous logging of failures can cause problems of its own."
|
||
msgstr ""
|
||
"Pengguna yang dapat mengambil log konsol dari menjalankan instance adalah "
|
||
"anugerah untuk dukungan — sering kali mereka dapat mengetahui apa yang "
|
||
"terjadi di dalam instance mereka dan memperbaiki apa yang terjadi tanpa "
|
||
"mengganggu Anda. Sayangnya, terkadang logging kegagalan yang terlalu banyak "
|
||
"dapat menyebabkan masalah tersendiri."
|
||
|
||
msgid ""
|
||
"Users must be associated with at least one project, though they may belong "
|
||
"to many. Therefore, you should add at least one project before adding users."
|
||
msgstr ""
|
||
"Pengguna harus dikaitkan dengan setidaknya satu proyek, meskipun mereka "
|
||
"mungkin milik banyak. Karena itu, Anda harus menambahkan setidaknya satu "
|
||
"proyek sebelum menambahkan pengguna."
|
||
|
||
msgid ""
|
||
"Using Image API v1 requires '-w 0' above, since multiline image properties "
|
||
"are not supported."
|
||
msgstr ""
|
||
"Menggunakan Image API v1 memerlukan '-w 0' di atas, karena properti image "
|
||
"multiline tidak didukung."
|
||
|
||
msgid ""
|
||
"Using OpenStack Compute cells, the NeCTAR Research Cloud spans eight sites "
|
||
"with approximately 4,000 cores per site."
|
||
msgstr ""
|
||
"Menggunakan sel OpenStack Compute, NeCTAR Research Cloud mencakup delapan "
|
||
"situs dengan sekitar 4.000 core per situs."
|
||
|
||
msgid ""
|
||
"Using administrator credentials, confirm the lost IP address is still "
|
||
"available:"
|
||
msgstr ""
|
||
"Menggunakan kredensial administrator, konfirmasi alamat IP yang hilang masih "
|
||
"tersedia:"
|
||
|
||
msgid "Using cURL for further inspection"
|
||
msgstr "Menggunakan cURL untuk pemeriksaan lebih lanjut"
|
||
|
||
msgid "Using ip a to Check Interface States"
|
||
msgstr "Menggunakan IP untuk Memeriksa Status Antarmuka"
|
||
|
||
msgid ""
|
||
"Using remote resources for collection, processing, storage, and retrieval "
|
||
"provides potential benefits to businesses. With the rapid growth of data "
|
||
"within organizations, businesses need to be proactive about their data "
|
||
"storage strategies from a compliance point of view."
|
||
msgstr ""
|
||
"Menggunakan sumber daya jarak jauh untuk pengumpulan, pemrosesan, "
|
||
"penyimpanan, dan pengambilan memberikan potensi keuntungan bagi bisnis. "
|
||
"Dengan pertumbuhan data yang cepat di dalam organisasi, bisnis harus "
|
||
"proaktif tentang strategi penyimpanan data mereka dari sudut pandang "
|
||
"kepatuhan."
|
||
|
||
msgid "Using the OpenStack Dashboard for Administration"
|
||
msgstr "Menggunakan OpenStack Dashboard untuk Administrasi"
|
||
|
||
msgid ""
|
||
"Using the command-line interface, you can manage quotas for the OpenStack "
|
||
"Compute service and the Block Storage service."
|
||
msgstr ""
|
||
"Menggunakan antarmuka ommand-line, Anda dapat mengelola kuota untuk layanan "
|
||
"OpenStack Compute dan layanan Block Storage."
|
||
|
||
msgid ""
|
||
"Using this functionality, ideally one would lock the RPC version to the "
|
||
"OpenStack version being upgraded from on nova-compute nodes, to ensure that, "
|
||
"for example X+1 version nova-compute processes will continue to work with X "
|
||
"version nova-conductor processes while the upgrade completes. Once the "
|
||
"upgrade of nova-compute processes is complete, the operator can move onto "
|
||
"upgrading nova-conductor and remove the version locking for nova-compute in "
|
||
"``nova.conf``."
|
||
msgstr ""
|
||
"Dengan menggunakan fungsi ini, idealnya seseorang akan mengunci versi RPC ke "
|
||
"versi OpenStack yang upgraded dari pada nova-compute nodes, untuk memastikan "
|
||
"bahwa, misalnya X+1 versi proses nova-compute akan terus bekerja dengan "
|
||
"versi X proses nova-conductor sementara upgrade selesai. Setelah upgrade "
|
||
"proses nova-compute selesai, operator dapat beralih ke upgrading nova-"
|
||
"conductor dan menghapus penguncian versi untuk nova-compute di ``nova."
|
||
"conf``."
|
||
|
||
msgid "VCPUs"
|
||
msgstr "VCPU"
|
||
|
||
msgid ""
|
||
"VLAN tags are translated between the external tag defined in the network "
|
||
"settings, and internal tags in several places. On the ``br-int``, incoming "
|
||
"packets from the ``int-br-eth1`` are translated from external tags to "
|
||
"internal tags. Other translations also happen on the other bridges and will "
|
||
"be discussed in those sections."
|
||
msgstr ""
|
||
"Tag VLAN diterjemahkan antara tag eksternal yang ditentukan dalam pengaturan "
|
||
"jaringan, dan tag internal di beberapa tempat. Pada ``br-int``, paket yang "
|
||
"masuk dari ``int-br-eth1`` diterjemahkan dari tag eksternal ke tag internal. "
|
||
"Terjemahan lain juga terjadi di jembatan lain dan akan dibahas di bagian-"
|
||
"bagian tersebut."
|
||
|
||
msgid ""
|
||
"VLAN-based networks are received as tagged packets on a physical network "
|
||
"interface, ``eth1`` in this example. Just as on the compute node, this "
|
||
"interface is a member of the ``br-eth1`` bridge."
|
||
msgstr ""
|
||
"Jaringan berbasis VLAN diterima sebagai paket yang ditandai pada antarmuka "
|
||
"jaringan fisik, ``eth1`` dalam contoh ini. Sama seperti pada node komputasi, "
|
||
"antarmuka ini adalah anggota dari jembatan ``br-eth1``."
|
||
|
||
msgid ""
|
||
"VLAN-based networks exit the integration bridge via veth interface ``int-br-"
|
||
"eth1`` and arrive on the bridge ``br-eth1`` on the other member of the veth "
|
||
"pair ``phy-br-eth1``. Packets on this interface arrive with internal VLAN "
|
||
"tags and are translated to external tags in the reverse of the process "
|
||
"described above:"
|
||
msgstr ""
|
||
"Jaringan berbasis VLAN keluar dari jembatan integrasi melalui antarmuka veth "
|
||
"``int-br-eth1`` dan tiba di jembatan ``br-eth1`` pada anggota lain dari "
|
||
"pasangan veth ``phy-br-eth1``. Paket pada antarmuka ini tiba dengan tag VLAN "
|
||
"internal dan diterjemahkan ke tag eksternal sebagai kebalikan dari proses "
|
||
"yang dijelaskan di atas:"
|
||
|
||
msgid "Verify RabbitMQ processes are running:"
|
||
msgstr "Verifikasi proses RabbitMQ berjalan:"
|
||
|
||
msgid ""
|
||
"Verify proper operation of your environment. Then, notify your users that "
|
||
"their cloud is operating normally again."
|
||
msgstr ""
|
||
"Verifikasi pengoperasian lingkungan Anda dengan benar. Lalu, beri tahu "
|
||
"pengguna Anda bahwa cloud mereka beroperasi secara normal lagi."
|
||
|
||
msgid "Verify that all hosted instances have been moved off the node:"
|
||
msgstr ""
|
||
"Verifikasi bahwa semua instance yang dihosting telah dipindahkan dari simpul:"
|
||
|
||
msgid "Verify the Keystone URL"
|
||
msgstr "Verifikasi URL Keystone"
|
||
|
||
msgid "Verify the instance has the correct IP address:"
|
||
msgstr "Pastikan instance memiliki alamat IP yang benar:"
|
||
|
||
msgid "Verify your alert mechanisms are still working."
|
||
msgstr "Verifikasi mekanisme peringatan Anda masih berfungsi."
|
||
|
||
msgid "View and update Block Storage quotas for a tenant (project)"
|
||
msgstr "Lihat dan perbarui kuota Block Storage untuk tenant (project)"
|
||
|
||
msgid "View quotas for the tenant, as follows:"
|
||
msgstr "Lihat kuota untuk tenant, sebagai berikut:"
|
||
|
||
msgid "Virtual cores"
|
||
msgstr "Virtual cores"
|
||
|
||
msgid "Virtualization"
|
||
msgstr "Virtualization (virtualisasi)"
|
||
|
||
msgid "Visualizing OpenStack Networking Service Traffic in the Cloud"
|
||
msgstr "Memvisualisasikan OpenStack Networking Service Traffic di Cloud"
|
||
|
||
msgid "Visualizing nova-network Traffic in the Cloud"
|
||
msgstr "Memvisualisasikan nova-network Traffic di Cloud"
|
||
|
||
msgid ""
|
||
"VlanManager is used extensively for network management. All servers have two "
|
||
"bonded 10GbE NICs that are connected to two redundant switches. DAIR is set "
|
||
"up to use single-node networking where the cloud controller is the gateway "
|
||
"for all instances on all compute nodes. Internal OpenStack traffic (for "
|
||
"example, storage traffic) does not go through the cloud controller."
|
||
msgstr ""
|
||
"VlanManager digunakan secara luas untuk manajemen jaringan. Semua server "
|
||
"memiliki dua NIC 10GbE terikat yang terhubung ke dua sakelar switch. DAIR "
|
||
"diatur untuk menggunakan jaringan node tunggal di mana pengontrol cloud "
|
||
"adalah gateway untuk semua instance pada semua node komputasi. Lalu lintas "
|
||
"OpenStack internal (misalnya, lalu lintas penyimpanan) tidak melalui "
|
||
"pengontrol cloud."
|
||
|
||
msgid "Volumes"
|
||
msgstr "Volumes"
|
||
|
||
msgid "Wash, rinse, and repeat until you find the core cause of the problem."
|
||
msgstr ""
|
||
"Cuci, bilas, dan ulangi sampai Anda menemukan inti penyebab masalahnya."
|
||
|
||
msgid "Watch the network"
|
||
msgstr "Amati jaringannya"
|
||
|
||
msgid "We also had some excellent input from outside of the room:"
|
||
msgstr ""
|
||
"Kami juga memiliki beberapa masukan yang sangat baik dari luar ruangan:"
|
||
|
||
msgid ""
|
||
"We approximate the older ``nova-network`` multi-host HA setup by using "
|
||
"\"provider VLAN networks\" that connect instances directly to existing "
|
||
"publicly addressable networks and use existing physical routers as their "
|
||
"default gateway. This means that if our network controller goes down, "
|
||
"running instances still have their network available, and no single Linux "
|
||
"host becomes a traffic bottleneck. We are able to do this because we have a "
|
||
"sufficient supply of IPv4 addresses to cover all of our instances and thus "
|
||
"don't need NAT and don't use floating IP addresses. We provide a single "
|
||
"generic public network to all projects and additional existing VLANs on a "
|
||
"project-by-project basis as needed. Individual projects are also allowed to "
|
||
"create their own private GRE based networks."
|
||
msgstr ""
|
||
"Kami memperkirakan pengaturan HA multi-host ``nova-network `` yang lebih "
|
||
"lama dengan menggunakan \"provider VLAN networks\" yang menghubungkan "
|
||
"instance secara langsung ke jaringan yang dapat dialamatkan secara publik "
|
||
"yang ada dan menggunakan router fisik yang ada sebagai gateway default "
|
||
"mereka. Ini berarti bahwa jika pengontrol jaringan kami turun, instance yang "
|
||
"berjalan masih memiliki jaringan mereka, dan tidak ada satu pun host Linux "
|
||
"yang menjadi penghambat lalu lintas. Kami dapat melakukan ini karena kami "
|
||
"memiliki pasokan alamat IPv4 yang cukup untuk menutupi semua instance kami "
|
||
"dan karenanya tidak perlu NAT dan tidak menggunakan alamat IP mengambang. "
|
||
"Kami menyediakan jaringan publik generik tunggal ke semua proyek dan "
|
||
"tambahan VLAN yang ada berdasarkan proyek per proyek sesuai kebutuhan. "
|
||
"Proyek individu juga diperbolehkan untuk membuat jaringan pribadi berbasis "
|
||
"GRE mereka sendiri."
|
||
|
||
msgid ""
|
||
"We called them and asked them to stop for a while, and they were happy to "
|
||
"abandon the horribly broken VM. After that, we started monitoring the size "
|
||
"of console logs."
|
||
msgstr ""
|
||
"Kami memanggil mereka dan meminta mereka untuk berhenti sebentar, dan mereka "
|
||
"senang meninggalkan VM yang rusak parah. Setelah itu, kami mulai memonitor "
|
||
"ukuran log konsol."
|
||
|
||
msgid ""
|
||
"We couldn't have pulled it off without so much supportive help and "
|
||
"encouragement."
|
||
msgstr ""
|
||
"Kami tidak akan berhasil tanpa bantuan dan dorongan yang begitu mendukung."
|
||
|
||
msgid ""
|
||
"We decided to have ``tcpdump`` run on this instance and see if we could "
|
||
"catch it in action again. Sure enough, we did."
|
||
msgstr ""
|
||
"Kami memutuskan untuk menjalankan ``tcpdump`` pada instance ini dan melihat "
|
||
"apakah kami dapat menjalankannya kembali. Cukup yakin, kami melakukannya."
|
||
|
||
msgid ""
|
||
"We hope you have enjoyed this quick tour of your working environment, "
|
||
"including how to interact with your cloud and extract useful information. "
|
||
"From here, you can use the `OpenStack Administrator Guide <https://docs."
|
||
"openstack.org/latest/admin/>`_ as your reference for all of the command-line "
|
||
"functionality in your cloud."
|
||
msgstr ""
|
||
"Kami harap Anda menikmati tur singkat ini di lingkungan kerja Anda, termasuk "
|
||
"bagaimana berinteraksi dengan cloud Anda dan mengekstrak informasi yang "
|
||
"berguna. Dari sini, Anda dapat menggunakan `OpenStack Administrator Guide "
|
||
"<https://docs.openstack.org/latest/admin/>`_ sebagai referensi Anda untuk "
|
||
"semua fungsi baris perintah di cloud Anda."
|
||
|
||
msgid ""
|
||
"We initially deployed on Ubuntu 12.04 with the Essex release of OpenStack "
|
||
"using FlatDHCP multi-host networking."
|
||
msgstr ""
|
||
"Kami awalnya digunakan di Ubuntu 12.04 dengan rilis Essex OpenStack "
|
||
"menggunakan jaringan multi-host FlatDHCP."
|
||
|
||
msgid ""
|
||
"We reached out for help. A networking engineer suggested it was an MTU "
|
||
"issue. Great! MTU! Something to go on! What's MTU and why would it cause a "
|
||
"problem?"
|
||
msgstr ""
|
||
"Kami mencari bantuan. Seorang insinyur jaringan menyarankan itu adalah "
|
||
"masalah MTU. Besar! MTU! Sesuatu untuk terus berlanjut! Apa itu MTU dan "
|
||
"mengapa itu menyebabkan masalah?"
|
||
|
||
msgid ""
|
||
"We recommend that you choose one of the following multiple disk options:"
|
||
msgstr ""
|
||
"Kami menyarankan Anda memilih salah satu dari beberapa opsi disk berikut:"
|
||
|
||
msgid ""
|
||
"We recommend that you turn to the `Installation Tutorials and Guides "
|
||
"<https://docs.openstack.org/install/>`_, which contains a step-by-step guide "
|
||
"on how to manually install the OpenStack packages and dependencies on your "
|
||
"cloud."
|
||
msgstr ""
|
||
"Kami menyarankan Anda beralih ke `Installation Tutorials and Guides <https://"
|
||
"docs.openstack.org/install/>`_, yang berisi panduan langkah demi langkah "
|
||
"tentang cara menginstal paket OpenStack dan dependensi secara manual pada "
|
||
"cloud Anda."
|
||
|
||
msgid ""
|
||
"We recommend that you use the same hardware for new compute and block "
|
||
"storage nodes. At the very least, ensure that the CPUs are similar in the "
|
||
"compute nodes to not break live migration."
|
||
msgstr ""
|
||
"Kami menyarankan Anda menggunakan perangkat keras yang sama untuk komputasi "
|
||
"dan memblokir node penyimpanan baru. Paling tidak, pastikan bahwa CPU serupa "
|
||
"dalam node komputasi untuk tidak memutuskan migrasi langsung."
|
||
|
||
msgid ""
|
||
"We recommend using a combination of the OpenStack command-line interface "
|
||
"(CLI) tools and the OpenStack dashboard for administration. Some users with "
|
||
"a background in other cloud technologies may be using the EC2 Compatibility "
|
||
"API, which uses naming conventions somewhat different from the native API."
|
||
msgstr ""
|
||
"Kami merekomendasikan penggunaan kombinasi alat command-line interface (CLI) "
|
||
"OpenStack dan dashboard OpenStack untuk administrasi. Beberapa pengguna "
|
||
"dengan latar belakang dalam teknologi cloud lain mungkin menggunakan EC2 "
|
||
"Compatibility API, yang menggunakan konvensi penamaan yang agak berbeda dari "
|
||
"API asli."
|
||
|
||
msgid ""
|
||
"We reviewed both sets of logs. The one thing that stood out the most was "
|
||
"DHCP. At the time, OpenStack, by default, set DHCP leases for one minute "
|
||
"(it's now two minutes). This means that every instance contacts the cloud "
|
||
"controller (DHCP server) to renew its fixed IP. For some reason, this "
|
||
"instance could not renew its IP. We correlated the instance's logs with the "
|
||
"logs on the cloud controller and put together a conversation:"
|
||
msgstr ""
|
||
"Kami meninjau kedua set log. Satu hal yang paling menonjol adalah DHCP. Pada "
|
||
"saat itu, OpenStack, secara default, mengatur penyewaan DHCP selama satu "
|
||
"menit (sekarang dua menit). Ini berarti bahwa setiap instance menghubungi "
|
||
"pengendali cloud (server DHCP) untuk memperbarui IP tetapnya. Untuk beberapa "
|
||
"alasan, instance ini tidak dapat memperbarui IP-nya. Kami mengkorelasikan "
|
||
"log instance dengan log pada pengontrol cloud dan membuat percakapan:"
|
||
|
||
msgid ""
|
||
"We use the Puppet Labs OpenStack modules to configure Compute, Image "
|
||
"service, Identity, and dashboard. Puppet is used widely for instance "
|
||
"configuration, and Foreman is used as a GUI for reporting and instance "
|
||
"provisioning."
|
||
msgstr ""
|
||
"Kami menggunakan modul Puppet Labs OpenStack untuk mengonfigurasikan "
|
||
"Compute, Image service, Identity, dan dashboard. Puppet digunakan secara "
|
||
"luas untuk konfigurasi instance, dan Foreman digunakan sebagai GUI untuk "
|
||
"pelaporan dan penyediaan instance."
|
||
|
||
msgid ""
|
||
"We want to acknowledge our excellent host Rackers at Rackspace in Austin:"
|
||
msgstr ""
|
||
"Kami ingin mengakui tuan rumah terbaik kami Rackers di Rackspace di Austin:"
|
||
|
||
msgid "Weekly"
|
||
msgstr "Mingguan"
|
||
|
||
msgid "What to Back Up"
|
||
msgstr "Yang Harus Dicadangkan"
|
||
|
||
msgid "What to do when things are running slowly"
|
||
msgstr "Apa yang harus dilakukan ketika segalanya berjalan lambat"
|
||
|
||
msgid ""
|
||
"When an instance fails to behave properly, you will often have to trace "
|
||
"activity associated with that instance across the log files of various "
|
||
"``nova-*`` services and across both the cloud controller and compute nodes."
|
||
msgstr ""
|
||
"Ketika sebuah instance gagal untuk berperilaku dengan benar, Anda akan "
|
||
"sering harus melacak aktivitas yang terkait dengan instance tersebut di "
|
||
"seluruh file log dari berbagai layanan ``nova- * `` dan di seluruh cloud "
|
||
"controller dan compute nodes."
|
||
|
||
msgid ""
|
||
"When debugging DNS issues, start by making sure that the host where the "
|
||
"dnsmasq process for that instance runs is able to correctly resolve. If the "
|
||
"host cannot resolve, then the instances won't be able to either."
|
||
msgstr ""
|
||
"Ketika men-debug masalah DNS, mulailah dengan memastikan bahwa host tempat "
|
||
"proses dnsmasq untuk instance berjalan dapat menyelesaikan dengan benar. "
|
||
"Jika host tidak dapat menyelesaikan, maka instance tidak akan bisa baik."
|
||
|
||
msgid ""
|
||
"When deploying OpenStack in an enterprise as a private cloud, it is usually "
|
||
"behind the firewall and within the trusted network alongside existing "
|
||
"systems. Users are employees that are bound by the company security "
|
||
"requirements. This tends to drive most of the security domains towards a "
|
||
"more trusted model. However, when deploying OpenStack in a public facing "
|
||
"role, no assumptions can be made and the attack vectors significantly "
|
||
"increase."
|
||
msgstr ""
|
||
"Ketika menggunakan OpenStack di perusahaan sebagai cloud pribadi, biasanya "
|
||
"di balik firewall dan di dalam jaringan tepercaya bersama sistem yang ada. "
|
||
"Pengguna adalah karyawan yang terikat oleh persyaratan keamanan perusahaan. "
|
||
"Ini cenderung mendorong sebagian besar domain keamanan ke arah model yang "
|
||
"lebih tepercaya. Namun, ketika menggunakan OpenStack dalam peran publik, "
|
||
"tidak ada asumsi yang dapat dibuat dan vektor serangan meningkat secara "
|
||
"signifikan."
|
||
|
||
msgid ""
|
||
"When operating an OpenStack cloud, you may discover that your users can be "
|
||
"quite demanding. If OpenStack doesn't do what your users need, it may be up "
|
||
"to you to fulfill those requirements. This chapter provided you with some "
|
||
"options for customization and gave you the tools you need to get started."
|
||
msgstr ""
|
||
"Saat mengoperasikan cloud OpenStack, Anda mungkin menemukan bahwa pengguna "
|
||
"Anda bisa sangat menuntut. Jika OpenStack tidak melakukan apa yang "
|
||
"dibutuhkan pengguna Anda, mungkin terserah Anda untuk memenuhi persyaratan "
|
||
"itu. Bab ini memberi Anda beberapa opsi untuk penyesuaian dan memberi Anda "
|
||
"alat yang Anda butuhkan untuk memulai."
|
||
|
||
msgid ""
|
||
"When the node is able to rejoin the cluster, just add it back to the ring. "
|
||
"The exact syntax you use to add a node to your swift cluster with ``swift-"
|
||
"ring-builder`` heavily depends on the original options used when you "
|
||
"originally created your cluster. Please refer back to those commands."
|
||
msgstr ""
|
||
"Ketika node dapat bergabung kembali dengan cluster, tambahkan saja kembali "
|
||
"ke ring. Sintaks yang tepat yang Anda gunakan untuk menambahkan node ke "
|
||
"cluster swift Anda dengan ``swift-ring-builder`` sangat tergantung pada opsi "
|
||
"asli yang digunakan saat Anda awalnya membuat cluster Anda. Silakan merujuk "
|
||
"kembali ke perintah itu."
|
||
|
||
msgid ""
|
||
"When this node fully booted, I ran through the same scenario of seeing what "
|
||
"instances were running so I could turn them back on. There were a total of "
|
||
"four. Three booted and one gave an error. It was the same error as before: "
|
||
"unable to find the backing disk. Seriously, what?"
|
||
msgstr ""
|
||
"Ketika node ini sepenuhnya boot, saya menjalankan skenario yang sama untuk "
|
||
"melihat instance apa yang sedang berjalan sehingga saya bisa menyalakannya "
|
||
"kembali. Ada total empat. Tiga boot dan satu memberikan kesalahan. Itu "
|
||
"kesalahan yang sama seperti sebelumnya: tidak dapat menemukan backing disk. "
|
||
"Serius, apa?"
|
||
|
||
msgid ""
|
||
"When users provision resources, they can specify from which availability "
|
||
"zone they want their instance to be built. This allows cloud consumers to "
|
||
"ensure that their application resources are spread across disparate machines "
|
||
"to achieve high availability in the event of hardware failure."
|
||
msgstr ""
|
||
"Ketika pengguna menyediakan sumber daya, mereka dapat menentukan dari zona "
|
||
"ketersediaan mana mereka ingin instance mereka dibangun. Hal ini "
|
||
"memungkinkan konsumen cloud untuk memastikan bahwa sumber daya aplikasi "
|
||
"mereka tersebar di berbagai mesin yang berbeda untuk mencapai ketersediaan "
|
||
"tinggi jika terjadi kegagalan perangkat keras."
|
||
|
||
msgid ""
|
||
"When you are getting slow responses from various services, it can be hard to "
|
||
"know where to start looking. The first thing to check is the extent of the "
|
||
"slowness: is it specific to a single service, or varied among different "
|
||
"services? If your problem is isolated to a specific service, it can "
|
||
"temporarily be fixed by restarting the service, but that is often only a fix "
|
||
"for the symptom and not the actual problem."
|
||
msgstr ""
|
||
"Ketika Anda mendapatkan respons lambat dari berbagai layanan, mungkin sulit "
|
||
"untuk mengetahui di mana harus mulai mencari. Hal pertama yang perlu "
|
||
"diperiksa adalah tingkat kelambatan: apakah spesifik untuk satu layanan, "
|
||
"atau beragam di antara layanan yang berbeda? Jika masalah Anda diisolasi "
|
||
"untuk layanan tertentu, sementara itu dapat diperbaiki dengan memulai "
|
||
"kembali layanan, tetapi itu seringkali hanya perbaikan untuk gejala dan "
|
||
"bukan masalah yang sebenarnya."
|
||
|
||
msgid ""
|
||
"When you create a deployment plan, focus on a few vital areas because they "
|
||
"are very hard to modify post deployment. The next two sections talk about "
|
||
"configurations for:"
|
||
msgstr ""
|
||
"Saat Anda membuat rencana penempatan, fokuslah pada beberapa area penting "
|
||
"karena sangat sulit untuk memodifikasi penempatan setelah itu. Dua bagian "
|
||
"berikutnya berbicara tentang konfigurasi untuk:"
|
||
|
||
msgid ""
|
||
"When you join the screen session that ``stack.sh`` starts with ``screen -r "
|
||
"stack``, you are greeted with many screen windows:"
|
||
msgstr ""
|
||
"Ketika Anda bergabung dengan sesi layar yang ``stack.sh`` dimulai dengan "
|
||
"``screen -r stack``, Anda akan disambut dengan banyak jendela layar (screen "
|
||
"windows):"
|
||
|
||
msgid ""
|
||
"When you join the screen session that ``stack.sh`` starts with ``screen -r "
|
||
"stack``, you see a screen for each service running, which can be a few or "
|
||
"several, depending on how many services you configured DevStack to run."
|
||
msgstr ""
|
||
"Ketika Anda bergabung dengan sesi layar yang ``stack.sh`` dimulai dengan "
|
||
"``screen -r stack``, Anda melihat layar untuk setiap layanan yang berjalan, "
|
||
"yang bisa beberapa atau beberapa, tergantung pada berapa banyak layanan yang "
|
||
"Anda konfigurasi DevStack untuk berlari."
|
||
|
||
msgid ""
|
||
"When you reboot a compute node, first verify that it booted successfully. "
|
||
"This includes ensuring that the ``nova-compute`` service is running:"
|
||
msgstr ""
|
||
"Ketika Anda me-reboot node komputasi, pertama-tama pastikan itu berhasil "
|
||
"boot. Ini termasuk memastikan bahwa layanan ``nova-compute`` sedang berjalan:"
|
||
|
||
msgid ""
|
||
"When you run any of the following operations, the services appear in their "
|
||
"own internal availability zone (CONF.internal_service_availability_zone):"
|
||
msgstr ""
|
||
"Ketika Anda menjalankan salah satu dari operasi berikut, layanan muncul di "
|
||
"zona ketersediaan internal mereka sendiri (CONF."
|
||
"internal_service_avilities_zone):"
|
||
|
||
msgid ""
|
||
"When your middleware is done, we encourage you to open source it and let the "
|
||
"community know on the OpenStack mailing list. Perhaps others need the same "
|
||
"functionality. They can use your code, provide feedback, and possibly "
|
||
"contribute. If enough support exists for it, perhaps you can propose that it "
|
||
"be added to the official swift `middleware <https://git.openstack.org/cgit/"
|
||
"openstack/swift/tree/swift/common/middleware>`_."
|
||
msgstr ""
|
||
"Ketika middleware Anda selesai, kami menganjurkan Anda untuk membuka "
|
||
"sumbernya dan memberi tahu komunitas di milis OpenStack. Mungkin orang lain "
|
||
"membutuhkan fungsi yang sama. Mereka dapat menggunakan kode Anda, memberikan "
|
||
"umpan balik, dan mungkin berkontribusi. Jika ada cukup dukungan untuk itu, "
|
||
"mungkin Anda dapat mengusulkan agar ditambahkan ke swift resmi `middleware "
|
||
"<https://git.openstack.org/cgit/openstack/swift/tree/swift/common/"
|
||
"middleware>`_."
|
||
|
||
msgid ""
|
||
"When your scheduler is done, we encourage you to open source it and let the "
|
||
"community know on the OpenStack mailing list. Perhaps others need the same "
|
||
"functionality. They can use your code, provide feedback, and possibly "
|
||
"contribute. If enough support exists for it, perhaps you can propose that it "
|
||
"be added to the official Compute `schedulers <https://git.openstack.org/cgit/"
|
||
"openstack/nova/tree/nova/scheduler>`_."
|
||
msgstr ""
|
||
"Ketika penjadwal Anda selesai, kami menganjurkan Anda untuk membuka "
|
||
"sumbernya dan memberi tahu komunitas di milis OpenStack. Mungkin orang lain "
|
||
"membutuhkan fungsi yang sama. Mereka dapat menggunakan kode Anda, memberikan "
|
||
"umpan balik, dan mungkin berkontribusi. Jika ada cukup dukungan untuk itu, "
|
||
"mungkin Anda dapat mengusulkan agar ditambahkan ke Compute resmi `schedulers "
|
||
"<https://git.openstack.org/cgit/openstack/nova/tree/nova/scheduler>`_."
|
||
|
||
msgid "Where Are the Logs?"
|
||
msgstr "Dimana Log-nya?"
|
||
|
||
msgid ""
|
||
"Where do you even begin troubleshooting something like this? An instance "
|
||
"that just randomly locks up when a command is issued. Is it the image? Nope—"
|
||
"it happens on all images. Is it the compute node? Nope—all nodes. Is the "
|
||
"instance locked up? No! New SSH connections work just fine!"
|
||
msgstr ""
|
||
"Di mana Anda bahkan mulai memecahkan masalah seperti ini? instance yang "
|
||
"hanya terkunci secara acak ketika perintah dikeluarkan. Apakah itu image? "
|
||
"Tidak — ini terjadi pada semua image. Apakah ini node komputasi? Tidak — "
|
||
"semua node. Apakah instance terkunci? Tidak! Koneksi SSH baru berfungsi "
|
||
"dengan baik!"
|
||
|
||
msgid ""
|
||
"Whether you use SQLite or an RDBMS (such as MySQL), SQL interoperability is "
|
||
"essential to a functioning OpenStack environment. A large or fragmented "
|
||
"SQLite file can cause slowness when using files as a back end. A locked or "
|
||
"long-running query can cause delays for most RDBMS services. In this case, "
|
||
"do not kill the query immediately, but look into it to see if it is a "
|
||
"problem with something that is hung, or something that is just taking a long "
|
||
"time to run and needs to finish on its own. The administration of an RDBMS "
|
||
"is outside the scope of this document, but it should be noted that a "
|
||
"properly functioning RDBMS is essential to most OpenStack services."
|
||
msgstr ""
|
||
"Apakah Anda menggunakan SQLite atau RDBMS (seperti MySQL), interoperabilitas "
|
||
"SQL sangat penting untuk lingkungan OpenStack yang berfungsi. File SQLite "
|
||
"yang besar atau terfragmentasi dapat menyebabkan kelambatan saat menggunakan "
|
||
"file sebagai ujung belakang. Kueri yang terkunci atau berjalan lama dapat "
|
||
"menyebabkan penundaan untuk sebagian besar layanan RDBMS. Dalam hal ini, "
|
||
"jangan langsung membunuh kueri, tetapi periksa ke dalamnya untuk melihat "
|
||
"apakah itu adalah masalah dengan sesuatu yang digantung, atau sesuatu yang "
|
||
"hanya membutuhkan waktu lama untuk dijalankan dan harus selesai sendiri. "
|
||
"Administrasi RDBMS berada di luar ruang lingkup dokumen ini, tetapi harus "
|
||
"dicatat bahwa RDBMS yang berfungsi dengan baik sangat penting untuk sebagian "
|
||
"besar layanan OpenStack."
|
||
|
||
msgid ""
|
||
"While OpenStack is composed of many components and moving parts, backing up "
|
||
"the critical data is quite simple."
|
||
msgstr ""
|
||
"Sementara OpenStack terdiri dari banyak komponen dan komponen yang bergerak, "
|
||
"membuat cadangan data penting cukup sederhana."
|
||
|
||
msgid ""
|
||
"While bouncing this idea around in our heads, I was randomly typing commands "
|
||
"on the compute node:"
|
||
msgstr ""
|
||
"Saat memantulkan ide ini di kepala kami, saya mengetik perintah secara acak "
|
||
"di compute node:"
|
||
|
||
msgid ""
|
||
"While it is important for an operator to be familiar with the steps involved "
|
||
"in deploying OpenStack, we also strongly encourage you to evaluate "
|
||
"`OpenStack deployment tools <https://docs.openstack.org/rocky/deploy/>`_ and "
|
||
"configuration-management tools, such as :term:`Puppet` or :term:`Chef`, "
|
||
"which can help automate this deployment process."
|
||
msgstr ""
|
||
"Meskipun penting bagi operator untuk memahami langkah-langkah yang terlibat "
|
||
"dalam penerapan OpenStack, kami juga sangat menyarankan Anda untuk "
|
||
"mengevaluasi `OpenStack deployment tools <https://docs.openstack.org/rocky/"
|
||
"deploy/>`_ dan alat manajemen konfigurasi, seperti :term:`Puppet` or :term:"
|
||
"`Chef`, yang dapat membantu mengotomatiskan proses penyebaran ini."
|
||
|
||
msgid ""
|
||
"While monitoring system resources, I noticed a significant increase in "
|
||
"memory consumption while the EC2 API processed this request. I thought it "
|
||
"wasn't handling memory properly—possibly not releasing memory. If the API "
|
||
"received several of these requests, memory consumption quickly grew until "
|
||
"the system ran out of RAM and began using swap. Each node has 48 GB of RAM "
|
||
"and the \"nova-api\" process would consume all of it within minutes. Once "
|
||
"this happened, the entire system would become unusably slow until I "
|
||
"restarted the nova-api service."
|
||
msgstr ""
|
||
"Saat memantau sumber daya sistem, saya melihat peningkatan konsumsi memori "
|
||
"yang signifikan sementara EC2 API memproses permintaan ini. Saya pikir itu "
|
||
"tidak menangani memori dengan benar — mungkin tidak melepaskan memori. Jika "
|
||
"API menerima beberapa permintaan ini, konsumsi memori cepat tumbuh hingga "
|
||
"sistem kehabisan RAM dan mulai menggunakan swap. Setiap node memiliki 48 GB "
|
||
"RAM dan proses \"nova-api\" akan menghabiskan semuanya dalam beberapa menit. "
|
||
"Setelah ini terjadi, seluruh sistem akan menjadi sangat lambat sampai saya "
|
||
"me-restart layanan nova-api."
|
||
|
||
msgid ""
|
||
"While several resources already exist to help with deploying and installing "
|
||
"OpenStack, it's very important to make sure that you have your deployment "
|
||
"planned out ahead of time. This guide presumes that you have set aside a "
|
||
"rack for the OpenStack cloud but also offers suggestions for when and what "
|
||
"to scale."
|
||
msgstr ""
|
||
"Sementara beberapa sumber daya sudah ada untuk membantu dalam menggunakan "
|
||
"dan menginstal OpenStack, sangat penting untuk memastikan bahwa Anda "
|
||
"memiliki penyebaran yang direncanakan sebelumnya. Panduan ini mengandaikan "
|
||
"bahwa Anda telah menyiapkan rak untuk cloud OpenStack tetapi juga menawarkan "
|
||
"saran kapan dan apa untuk skala."
|
||
|
||
msgid ""
|
||
"While the command should work with any hypervisor that is controlled through "
|
||
"libvirt (KVM, QEMU, or LXC), it has been tested only with KVM. Here is the "
|
||
"example output when the hypervisor is KVM:"
|
||
msgstr ""
|
||
"Sementara perintah harus bekerja dengan hypervisor apa pun yang dikontrol "
|
||
"melalui libvirt (KVM, QEMU, atau LXC), itu telah diuji hanya dengan KVM. "
|
||
"Berikut adalah contoh output ketika hypervisor adalah KVM:"
|
||
|
||
msgid ""
|
||
"While we'd always recommend using your automated deployment system to "
|
||
"reinstall systems from scratch, sometimes you do need to remove OpenStack "
|
||
"from a system the hard way. Here's how:"
|
||
msgstr ""
|
||
"Meskipun kami selalu merekomendasikan menggunakan sistem penyebaran otomatis "
|
||
"Anda untuk menginstal ulang sistem dari awal, kadang-kadang Anda harus "
|
||
"menghapus OpenStack dari sistem dengan cara yang sulit. Begini caranya:"
|
||
|
||
msgid ""
|
||
"While you might end up with unused partitions, such as partition 1 in disk "
|
||
"three and four of this example, this option allows for maximum utilization "
|
||
"of disk space. I/O performance might be an issue as a result of all disks "
|
||
"being used for all tasks."
|
||
msgstr ""
|
||
"Meskipun Anda mungkin berakhir dengan partisi yang tidak digunakan, seperti "
|
||
"partisi 1 di disk tiga dan empat dari contoh ini, opsi ini memungkinkan "
|
||
"pemanfaatan ruang disk secara maksimal. Kinerja I/O mungkin menjadi masalah "
|
||
"karena semua disk digunakan untuk semua tugas."
|
||
|
||
msgid ""
|
||
"Who uses it: DAIR is an integrated virtual environment that leverages the "
|
||
"CANARIE network to develop and test new information communication technology "
|
||
"(ICT) and other digital technologies. It combines such digital "
|
||
"infrastructure as advanced networking and cloud computing and storage to "
|
||
"create an environment for developing and testing innovative ICT "
|
||
"applications, protocols, and services; performing at-scale experimentation "
|
||
"for deployment; and facilitating a faster time to market."
|
||
msgstr ""
|
||
"Siapa yang menggunakannya: DAIR adalah lingkungan virtual terintegrasi yang "
|
||
"memanfaatkan jaringan CANARIE untuk mengembangkan dan menguji t information "
|
||
"communication technology (ICT) dan teknologi digital lainnya. Ini "
|
||
"menggabungkan infrastruktur digital seperti jaringan dan komputasi awan "
|
||
"serta penyimpanan canggih untuk menciptakan lingkungan untuk mengembangkan "
|
||
"dan menguji aplikasi ICT, protokol, dan layanan yang inovatif; melakukan "
|
||
"eksperimen at-scale untuk pengerahan; dan memfasilitasi waktu yang lebih "
|
||
"cepat ke pasar."
|
||
|
||
msgid ""
|
||
"Who uses it: researchers at CERN (European Organization for Nuclear "
|
||
"Research) conducting high-energy physics research."
|
||
msgstr ""
|
||
"Siapa yang menggunakannya: peneliti di CERN (European Organization for "
|
||
"Nuclear Research) yang melakukan penelitian fisika energi tinggi."
|
||
|
||
msgid ""
|
||
"Who uses it: researchers from the Australian publicly funded research "
|
||
"sector. Use is across a wide variety of disciplines, with the purpose of "
|
||
"instances ranging from running simple web servers to using hundreds of cores "
|
||
"for high-throughput computing."
|
||
msgstr ""
|
||
"Siapa yang menggunakannya: peneliti dari sektor penelitian yang didanai "
|
||
"publik Australia. Penggunaannya melintasi berbagai disiplin ilmu, dengan "
|
||
"tujuan mulai dari menjalankan server web sederhana hingga menggunakan "
|
||
"ratusan core untuk komputasi high-throughput."
|
||
|
||
msgid ""
|
||
"Who uses it: researchers from the MIT Computer Science and Artificial "
|
||
"Intelligence Lab."
|
||
msgstr ""
|
||
"Siapa yang menggunakannya: peneliti dari MIT Computer Science and Artificial "
|
||
"Intelligence Lab."
|
||
|
||
msgid ""
|
||
"With ``nova-network``, the nova database table contains a few tables with "
|
||
"networking information:"
|
||
msgstr ""
|
||
"Dengan ``nova-network``, tabel database nova berisi beberapa tabel dengan "
|
||
"informasi jaringan:"
|
||
|
||
msgid ""
|
||
"With our upgrade to Grizzly in August 2013, we moved to OpenStack "
|
||
"Networking, neutron (quantum at the time). Compute nodes have two-gigabit "
|
||
"network interfaces and a separate management card for IPMI management. One "
|
||
"network interface is used for node-to-node communications. The other is used "
|
||
"as a trunk port for OpenStack managed VLANs. The controller node uses two "
|
||
"bonded 10g network interfaces for its public IP communications. Big pipes "
|
||
"are used here because images are served over this port, and it is also used "
|
||
"to connect to iSCSI storage, back-ending the image storage and database. The "
|
||
"controller node also has a gigabit interface that is used in trunk mode for "
|
||
"OpenStack managed VLAN traffic. This port handles traffic to the dhcp-agent "
|
||
"and metadata-proxy."
|
||
msgstr ""
|
||
"Dengan peningkatan kami ke Grizzly pada Agustus 2013, kami pindah ke "
|
||
"OpenStack Networking, neutron (kuantum pada saat itu). Compute nodes "
|
||
"memiliki antarmuka jaringan dua gigabit dan kartu manajemen yang terpisah "
|
||
"untuk manajemen IPMI. Satu antarmuka jaringan digunakan untuk komunikasi "
|
||
"node-to-node. Yang lain digunakan sebagai port trunk untuk VLAN yang "
|
||
"dikelola OpenStack. Node pengontrol menggunakan dua antarmuka jaringan 10g "
|
||
"terikat untuk komunikasi IP publiknya. Pipa besar digunakan di sini karena "
|
||
"image disajikan melalui port ini, dan juga digunakan untuk terhubung ke "
|
||
"penyimpanan iSCSI, back-ending penyimpanan image dan basis data. Node "
|
||
"pengontrol juga memiliki antarmuka gigabit yang digunakan dalam mode trunk "
|
||
"untuk lalu lintas VLAN yang dikelola OpenStack. Port ini menangani lalu "
|
||
"lintas ke agen dhcp dan metadata-proxy."
|
||
|
||
msgid ""
|
||
"With the exception of Object Storage, upgrading from one version of "
|
||
"OpenStack to another can take a great deal of effort. This chapter provides "
|
||
"some guidance on the operational aspects that you should consider for "
|
||
"performing an upgrade for an OpenStack environment."
|
||
msgstr ""
|
||
"Dengan pengecualian Object Storage, memutakhirkan dari satu versi OpenStack "
|
||
"ke yang lain dapat membutuhkan banyak usaha. Bab ini memberikan beberapa "
|
||
"panduan tentang aspek operasional yang harus Anda pertimbangkan untuk "
|
||
"melakukan peningkatan (upgrade) untuk lingkungan OpenStack."
|
||
|
||
msgid ""
|
||
"With the introduction of the full software-defined networking stack provided "
|
||
"by OpenStack Networking (neutron) in the Folsom release, development effort "
|
||
"on the initial networking code that remains part of the Compute component "
|
||
"has gradually lessened. While many still use ``nova-network`` in production, "
|
||
"there has been a long-term plan to remove the code in favor of the more "
|
||
"flexible and full-featured OpenStack Networking."
|
||
msgstr ""
|
||
"Dengan diperkenalkannya full software-defined networking stack (tumpukan "
|
||
"jaringan yang ditentukan oleh perangkat lunak lengkap) yang disediakan oleh "
|
||
"OpenStack Networking (neutron) dalam rilis Folsom, upaya pengembangan pada "
|
||
"kode jaringan awal yang tetap menjadi bagian dari komponen Compute secara "
|
||
"bertahap berkurang. Sementara banyak yang masih menggunakan ``nova-network`` "
|
||
"dalam produksi, telah ada rencana jangka panjang untuk menghapus kode yang "
|
||
"mendukung OpenStack Networking yang lebih fleksibel dan berfitur lengkap."
|
||
|
||
msgid ""
|
||
"With these two tables, you now have a good overview of what servers and "
|
||
"services make up your cloud."
|
||
msgstr ""
|
||
"Dengan dua tabel ini, Anda sekarang memiliki gambaran umum yang baik tentang "
|
||
"server dan layanan apa yang membentuk cloud Anda."
|
||
|
||
msgid ""
|
||
"With this information in hand, we were sure that the problem had to do with "
|
||
"DHCP. We thought that for some reason, the instance wasn't getting a new IP "
|
||
"address and with no IP, it shut itself off from the network."
|
||
msgstr ""
|
||
"Dengan informasi ini di tangan, kami yakin bahwa masalahnya ada pada DHCP. "
|
||
"Kami berpikir bahwa karena alasan tertentu, mesin virtual tidak mendapatkan "
|
||
"alamat IP baru dan tanpa IP, itu mematikan sendiri dari jaringan."
|
||
|
||
msgid ""
|
||
"With this option, you can assign different partitions to different RAID "
|
||
"arrays. You can allocate partition 1 of disk one and two to the ``/boot`` "
|
||
"partition mirror. You can make partition 2 of all disks the root partition "
|
||
"mirror. You can use partition 3 of all disks for a ``cinder-volumes`` LVM "
|
||
"partition running on a RAID 10 array."
|
||
msgstr ""
|
||
"Dengan opsi ini, Anda dapat menetapkan partisi yang berbeda untuk array RAID "
|
||
"yang berbeda. Anda dapat mengalokasikan partisi 1 disk satu dan dua ke "
|
||
"cermin partisi ``/boot`` . Anda dapat menjadikan partisi 2 dari semua disk "
|
||
"sebagai partisi root. Anda dapat menggunakan partisi 3 dari semua disk untuk "
|
||
"partisi LVM ``cinder-volume`` yang berjalan pada array RAID 10."
|
||
|
||
msgid ""
|
||
"Within this scope, you must complete these steps to successfully roll back "
|
||
"your environment:"
|
||
msgstr ""
|
||
"Dalam lingkup ini, Anda harus menyelesaikan langkah-langkah ini untuk "
|
||
"berhasil mengembalikan lingkungan Anda:"
|
||
|
||
msgid ""
|
||
"Without upgrade levels, an X+1 version Compute service can receive and "
|
||
"understand X version RPC messages, but it can only send out X+1 version RPC "
|
||
"messages. For example, if a nova-conductor process has been upgraded to X+1 "
|
||
"version, then the conductor service will be able to understand messages from "
|
||
"X version nova-compute processes, but those compute services will not be "
|
||
"able to understand messages sent by the conductor service."
|
||
msgstr ""
|
||
"Tanpa tingkat upgrade, layanan Compute versi X + 1 dapat menerima dan "
|
||
"memahami pesan RPC versi X, tetapi hanya dapat mengirim pesan RPC versi X"
|
||
"+1. Misalnya, jika proses nova-conductor telah ditingkatkan ke versi X+1, "
|
||
"maka layanan konduktor akan dapat memahami pesan dari proses penghitungan "
|
||
"nova versi X, tetapi layanan komputasi tersebut tidak akan dapat memahami "
|
||
"pesan yang dikirim oleh layanan konduktor."
|
||
|
||
msgid ""
|
||
"Working from the physical interface inwards, we can see the chain of ports "
|
||
"and bridges. First, the bridge ``eth1-br``, which contains the physical "
|
||
"network interface ``eth1`` and the virtual interface ``phy-eth1-br``:"
|
||
msgstr ""
|
||
"Bekerja dari antarmuka fisik ke dalam, kita dapat melihat rantai port dan "
|
||
"jembatan. Pertama, jembatan ``eth1-br``, yang berisi antarmuka jaringan "
|
||
"fisik ``eth1`` dan antarmuka virtual ``phy-eth1-br``:"
|
||
|
||
msgid "Working with Hardware"
|
||
msgstr "Bekerja dengan Perangkat Keras"
|
||
|
||
msgid "Working with Roadmaps"
|
||
msgstr "Bekerja dengan Roadmap"
|
||
|
||
msgid ""
|
||
"You are prompted for a project name and an optional, but recommended, "
|
||
"description. Select the check box at the bottom of the form to enable this "
|
||
"project. By default, it is enabled, as shown below:"
|
||
msgstr ""
|
||
"Anda diminta untuk nama proyek dan deskripsi opsional, tetapi disarankan. "
|
||
"Pilih kotak centang di bagian bawah formulir untuk mengaktifkan proyek ini. "
|
||
"Secara default, ini diaktifkan, seperti yang ditunjukkan di bawah ini:"
|
||
|
||
msgid "You can also restore backed-up nova directories:"
|
||
msgstr "Anda juga dapat mengembalikan direktori nova yang didukung:"
|
||
|
||
msgid ""
|
||
"You can also use the Identity service (keystone) to see what services are "
|
||
"available in your cloud as well as what endpoints have been configured for "
|
||
"the services."
|
||
msgstr ""
|
||
"Anda juga dapat menggunakan layanan Identity (keystone) untuk melihat "
|
||
"layanan apa yang tersedia di cloud Anda serta endpoint apa yang telah "
|
||
"dikonfigurasi untuk layanan tersebut."
|
||
|
||
msgid ""
|
||
"You can configure some services, such as ``nova-api`` and ``glance-api``, to "
|
||
"use multiple processes by changing a flag in their configuration file "
|
||
"allowing them to share work between multiple cores on the one machine."
|
||
msgstr ""
|
||
"Anda dapat mengkonfigurasi beberapa layanan, seperti ``nova-api`` dan "
|
||
"``glance-api``, untuk menggunakan beberapa proses dengan mengubah tanda pada "
|
||
"file konfigurasi mereka yang memungkinkan mereka untuk berbagi kerja antara "
|
||
"beberapa core pada satu mesin."
|
||
|
||
msgid ""
|
||
"You can create a list of instances that are hosted on the compute node by "
|
||
"performing the following command:"
|
||
msgstr ""
|
||
"Anda dapat membuat daftar instance yang dihosting di node komputasi dengan "
|
||
"melakukan perintah berikut:"
|
||
|
||
msgid ""
|
||
"You can create automated alerts for critical processes by using Nagios and "
|
||
"NRPE. For example, to ensure that the ``nova-compute`` process is running on "
|
||
"the compute nodes, create an alert on your Nagios server:"
|
||
msgstr ""
|
||
"Anda dapat membuat lansiran otomatis untuk proses kritis dengan menggunakan "
|
||
"Nagios dan NRPE. Misalnya, untuk memastikan bahwa proses ``nova-compute`` "
|
||
"sedang berjalan di node komputasi, buat peringatan di server Nagios Anda:"
|
||
|
||
msgid ""
|
||
"You can determine the package versions available for reversion by using the "
|
||
"``apt-cache policy`` command. For example:"
|
||
msgstr ""
|
||
"Anda dapat menentukan versi paket yang tersedia untuk pembalikan dengan "
|
||
"menggunakan perintah ``apt-cache policy``. Sebagai contoh:"
|
||
|
||
msgid ""
|
||
"You can easily automate this process by creating a cron job that runs the "
|
||
"following script once per day:"
|
||
msgstr ""
|
||
"Anda dapat dengan mudah mengotomatiskan proses ini dengan membuat tugas cron "
|
||
"yang menjalankan skrip berikut sekali sehari:"
|
||
|
||
msgid ""
|
||
"You can facilitate the horizontal expansion of your cloud by adding nodes. "
|
||
"Adding compute nodes is straightforward since they are easily picked up by "
|
||
"the existing installation. However, you must consider some important points "
|
||
"when you design your cluster to be highly available."
|
||
msgstr ""
|
||
"Anda dapat memfasilitasi ekspansi horisontal cloud Anda dengan menambahkan "
|
||
"node. Menambahkan node komputasi sangat mudah karena mudah diambil oleh "
|
||
"instalasi yang ada. Namun, Anda harus mempertimbangkan beberapa poin penting "
|
||
"ketika Anda mendesain cluster Anda menjadi sangat tersedia."
|
||
|
||
msgid ""
|
||
"You can find the version of the Compute installation by using the OpenStack "
|
||
"command-line client:"
|
||
msgstr ""
|
||
"Anda dapat menemukan versi instalasi Compute dengan menggunakan klien "
|
||
"command-line OpenStack:"
|
||
|
||
msgid ""
|
||
"You can follow a similar pattern in other projects that use the Python Paste "
|
||
"framework. Simply create a middleware module and plug it in through "
|
||
"configuration. The middleware runs in sequence as part of that project's "
|
||
"pipeline and can call out to other services as necessary. No project core "
|
||
"code is touched. Look for a ``pipeline`` value in the project's ``conf`` or "
|
||
"``ini`` configuration files in ``/etc/<project>`` to identify projects that "
|
||
"use Paste."
|
||
msgstr ""
|
||
"Anda bisa mengikuti pola serupa di proyek lain yang menggunakan framework "
|
||
"Python Paste. Cukup buat modul middleware dan pasang melalui konfigurasi. "
|
||
"Middleware berjalan secara berurutan sebagai bagian dari project's pipeline "
|
||
"itu dan dapat memanggil layanan lain yang diperlukan. Tidak ada kode inti "
|
||
"proyek yang disentuh. Cari nilai ``pipeline`` di file konfigurasi ``conf`` "
|
||
"atau ``ini`` proyek di ``/etc/<project>`` untuk mengidentifikasi proyek yang "
|
||
"menggunakan Paste."
|
||
|
||
msgid ""
|
||
"You can follow the progress being made on IPV6 support by watching the "
|
||
"`neutron IPv6 Subteam at work <https://wiki.openstack.org/wiki/Meetings/"
|
||
"Neutron-IPv6-Subteam>`_."
|
||
msgstr ""
|
||
"Anda dapat mengikuti kemajuan yang dibuat pada dukungan IPV6 dengan melihat "
|
||
"`neutron IPv6 Subteam at work <https://wiki.openstack.org/wiki/Meetings/"
|
||
"Neutron-IPv6-Subteam>`_."
|
||
|
||
msgid ""
|
||
"You can modify this example script on each node to handle different services."
|
||
msgstr ""
|
||
"Anda dapat memodifikasi skrip contoh ini di setiap node untuk menangani "
|
||
"layanan yang berbeda."
|
||
|
||
msgid ""
|
||
"You can now access the contents of ``/mnt``, which correspond to the first "
|
||
"partition of the instance's disk."
|
||
msgstr ""
|
||
"Anda sekarang dapat mengakses konten ``/mnt``, yang sesuai dengan partisi "
|
||
"pertama dari disk instance."
|
||
|
||
msgid "You can now get the related floating IP entry:"
|
||
msgstr "Anda sekarang bisa mendapatkan entri IP mengambang terkait:"
|
||
|
||
msgid ""
|
||
"You can obtain extra information about virtual machines that are running—"
|
||
"their CPU usage, the memory, the disk I/O or network I/O—per instance, by "
|
||
"running the :command:`nova diagnostics` command with a server ID:"
|
||
msgstr ""
|
||
"Anda dapat memperoleh informasi tambahan tentang mesin virtual yang sedang "
|
||
"berjalan —their CPU usage, the memory, the disk I/O or network I/O—per "
|
||
"instance, dengan menjalankan perintah :command:`nova diagnostics` dengan ID "
|
||
"server:"
|
||
|
||
msgid ""
|
||
"You can obtain further statistics by looking for the number of successful "
|
||
"requests:"
|
||
msgstr ""
|
||
"Anda dapat memperoleh statistik lebih lanjut dengan mencari jumlah "
|
||
"permintaan yang berhasil:"
|
||
|
||
msgid "You can optionally also deallocate the IP from the user's pool:"
|
||
msgstr ""
|
||
"Secara opsional Anda juga dapat membatalkan alokasi IP dari kumpulan "
|
||
"pengguna:"
|
||
|
||
msgid ""
|
||
"You can perform a couple of tricks with the database to either more quickly "
|
||
"retrieve information or fix a data inconsistency error—for example, an "
|
||
"instance was terminated, but the status was not updated in the database. "
|
||
"These tricks are discussed throughout this book."
|
||
msgstr ""
|
||
"Anda dapat melakukan beberapa trik dengan database untuk mengambil informasi "
|
||
"lebih cepat atau memperbaiki kesalahan inkonsistensi data — misalnya, sebuah "
|
||
"instance dihentikan, tetapi statusnya tidak diperbarui dalam database. Trik "
|
||
"ini dibahas di seluruh buku ini."
|
||
|
||
msgid "You can re-enable the ``nova-compute`` service by undoing the commands:"
|
||
msgstr ""
|
||
"Anda dapat mengaktifkan kembali layanan ``nova-compute`` dengan membatalkan "
|
||
"perintah:"
|
||
|
||
msgid ""
|
||
"You can restrict a project's image storage by total number of bytes. "
|
||
"Currently, this quota is applied cloud-wide, so if you were to set an Image "
|
||
"quota limit of 5 GB, then all projects in your cloud will be able to store "
|
||
"only 5 GB of images and snapshots."
|
||
msgstr ""
|
||
"Anda dapat membatasi penyimpanan image proyek dengan jumlah total byte. Saat "
|
||
"ini, kuota ini diterapkan secara cloud-wide, jadi jika Anda menetapkan batas "
|
||
"kuota image 5 GB, maka semua proyek di cloud Anda akan dapat menyimpan hanya "
|
||
"5 GB image dan snapshot."
|
||
|
||
msgid ""
|
||
"You can safely ignore the state of ``virbr0``, which is a default bridge "
|
||
"created by libvirt and not used by OpenStack."
|
||
msgstr ""
|
||
"Anda dapat dengan aman mengabaikan status ``virbr0``, yang merupakan "
|
||
"jembatan default yang dibuat oleh libvirt dan tidak digunakan oleh OpenStack."
|
||
|
||
msgid ""
|
||
"You can save resources by looking at the best fit for the hardware you have "
|
||
"in place already. You might have some high-density storage hardware "
|
||
"available. You could format and repurpose those servers for OpenStack Object "
|
||
"Storage. All of these considerations and input from users help you build "
|
||
"your use case and your deployment plan."
|
||
msgstr ""
|
||
"Anda dapat menghemat sumber daya dengan melihat yang paling cocok untuk "
|
||
"perangkat keras yang Anda miliki. Anda mungkin memiliki beberapa perangkat "
|
||
"keras penyimpanan kepadatan tinggi yang tersedia. Anda bisa memformat dan "
|
||
"menggunakan kembali server-server itu untuk OpenStack Object Storage. Semua "
|
||
"pertimbangan dan masukan dari pengguna ini membantu Anda membangun kasus "
|
||
"penggunaan (use case) dan rencana penerapan Anda."
|
||
|
||
msgid ""
|
||
"You can save time by understanding the use cases for the cloud you want to "
|
||
"create. Use cases for OpenStack are varied. Some include object storage "
|
||
"only; others require preconfigured compute resources to speed development-"
|
||
"environment set up; and others need fast provisioning of compute resources "
|
||
"that are already secured per tenant with private networks. Your users may "
|
||
"have need for highly redundant servers to make sure their legacy "
|
||
"applications continue to run. Perhaps a goal would be to architect these "
|
||
"legacy applications so that they run on multiple instances in a cloudy, "
|
||
"fault-tolerant way, but not make it a goal to add to those clusters over "
|
||
"time. Your users may indicate that they need scaling considerations because "
|
||
"of heavy Windows server use."
|
||
msgstr ""
|
||
"Anda dapat menghemat waktu dengan memahami kasus penggunaan untuk cloud yang "
|
||
"ingin Anda buat. Kasus penggunaan untuk OpenStack bervariasi. Beberapa hanya "
|
||
"menyertakan penyimpanan objek; yang lain membutuhkan sumber daya komputasi "
|
||
"yang telah dikonfigurasikan sebelumnya untuk mempercepat pengaturan "
|
||
"lingkungan pengembangan; dan yang lainnya membutuhkan penyediaan sumber daya "
|
||
"komputasi yang cepat yang sudah diamankan per penyewa dengan jaringan "
|
||
"pribadi. Pengguna Anda mungkin perlu server yang sangat berlebihan untuk "
|
||
"memastikan aplikasi lawas mereka terus berjalan. Mungkin tujuannya adalah "
|
||
"untuk merancang aplikasi-aplikasi warisan ini sehingga aplikasi-aplikasi "
|
||
"tersebut dijalankan pada banyak instance di cloud, secara toleran kesalahan, "
|
||
"tetapi tidak menjadikannya suatu tujuan untuk ditambahkan ke kluster-kluster "
|
||
"tersebut dari waktu ke waktu. Pengguna Anda mungkin mengindikasikan bahwa "
|
||
"mereka perlu pertimbangan penskalaan karena penggunaan server Windows yang "
|
||
"berat."
|
||
|
||
msgid ""
|
||
"You can use availability zones, host aggregates, or both to partition a nova "
|
||
"deployment. Both methods are configured and implemented in a similar way."
|
||
msgstr ""
|
||
"Anda dapat menggunakan zona ketersediaan, agregat host, atau keduanya untuk "
|
||
"mempartisi penyebaran nova. Kedua metode dikonfigurasikan dan "
|
||
"diimplementasikan dengan cara yang serupa."
|
||
|
||
msgid ""
|
||
"You can use these ratios to determine how much additional infrastructure you "
|
||
"need to support your cloud."
|
||
msgstr ""
|
||
"Anda dapat menggunakan rasio ini untuk menentukan berapa banyak "
|
||
"infrastruktur tambahan yang Anda butuhkan untuk mendukung cloud Anda."
|
||
|
||
msgid ""
|
||
"You define the availability zone in which a specified compute host resides "
|
||
"locally on each server. An availability zone is commonly used to identify a "
|
||
"set of servers that have a common attribute. For instance, if some of the "
|
||
"racks in your data center are on a separate power source, you can put "
|
||
"servers in those racks in their own availability zone. Availability zones "
|
||
"can also help separate different classes of hardware."
|
||
msgstr ""
|
||
"Anda menentukan zona ketersediaan tempat host komputasi tertentu berada "
|
||
"secara lokal di setiap server. Zona ketersediaan biasanya digunakan untuk "
|
||
"mengidentifikasi satu set server yang memiliki atribut umum. Misalnya, jika "
|
||
"beberapa rak di pusat data Anda berada di sumber daya yang terpisah, Anda "
|
||
"dapat menempatkan server di rak tersebut di zona ketersediaannya sendiri. "
|
||
"Zona ketersediaan juga dapat membantu memisahkan berbagai kelas perangkat "
|
||
"keras."
|
||
|
||
msgid ""
|
||
"You may find that you can automate the partitioning itself. For example, MIT "
|
||
"uses `Fully Automatic Installation (FAI) <http://fai-project.org/>`_ to do "
|
||
"the initial PXE-based partition and then install using a combination of min/"
|
||
"max and percentage-based partitioning."
|
||
msgstr ""
|
||
"Anda mungkin menemukan bahwa Anda dapat mengotomatisasi partisi itu sendiri. "
|
||
"Sebagai contoh, MIT menggunakan `Fully Automatic Installation (FAI) <http://"
|
||
"fai-project.org/>` _ untuk melakukan partisi awal berbasis PXE dan kemudian "
|
||
"menginstal menggunakan kombinasi dari partisi min/max dan berbasis "
|
||
"persentase."
|
||
|
||
msgid ""
|
||
"You may need to explicitly install the ``ipset`` package if your "
|
||
"distribution does not install it as a dependency."
|
||
msgstr ""
|
||
"Anda mungkin perlu menginstal paket ``ipset`` secara eksplisit jika "
|
||
"distribusi Anda tidak menginstalnya sebagai dependensi."
|
||
|
||
msgid ""
|
||
"You may notice that all the existing logging messages are preceded by an "
|
||
"underscore and surrounded by parentheses, for example:"
|
||
msgstr ""
|
||
"Anda mungkin memperhatikan bahwa semua pesan logging yang ada didahului "
|
||
"dengan garis bawah dan dikelilingi oleh tanda kurung, misalnya:"
|
||
|
||
msgid "You might also see a message such as this:"
|
||
msgstr "Anda mungkin juga melihat pesan seperti ini:"
|
||
|
||
msgid ""
|
||
"You must also consider key hardware specifications for the performance of "
|
||
"user VMs, as well as budget and performance needs, including storage "
|
||
"performance (spindles/core), memory availability (RAM/core), network "
|
||
"bandwidth hardware specifications and (Gbps/core), and overall CPU "
|
||
"performance (CPU/core)."
|
||
msgstr ""
|
||
"Anda juga harus mempertimbangkan spesifikasi perangkat keras utama untuk "
|
||
"kinerja VM pengguna, serta kebutuhan anggaran dan kinerja, termasuk kinerja "
|
||
"penyimpanan (spindles/core), ketersediaan memori (RAM/core), spesifikasi "
|
||
"perangkat keras bandwidth jaringan dan (Gbps/core), dan kinerja CPU secara "
|
||
"keseluruhan (CPU/core)."
|
||
|
||
msgid ""
|
||
"You must complete the following configurations on the server's hard drives:"
|
||
msgstr "Anda harus menyelesaikan konfigurasi berikut pada hard drive server:"
|
||
|
||
msgid ""
|
||
"You must have the appropriate credentials if you want to use the command-"
|
||
"line tools to make queries against your OpenStack cloud. By far, the easiest "
|
||
"way to obtain :term:`authentication` credentials to use with command-line "
|
||
"clients is to use the OpenStack dashboard. Select :guilabel:`Project`, click "
|
||
"the :guilabel:`Project` tab, and click :guilabel:`Access & Security` on the :"
|
||
"guilabel:`Compute` category. On the :guilabel:`Access & Security` page, "
|
||
"click the :guilabel:`API Access` tab to display two buttons, :guilabel:"
|
||
"`Download OpenStack RC File` and :guilabel:`Download EC2 Credentials`, which "
|
||
"let you generate files that you can source in your shell to populate the "
|
||
"environment variables the command-line tools require to know where your "
|
||
"service endpoints and your authentication information are. The user you "
|
||
"logged in to the dashboard dictates the filename for the openrc file, such "
|
||
"as ``demo-openrc.sh``. When logged in as admin, the file is named ``admin-"
|
||
"openrc.sh``."
|
||
msgstr ""
|
||
"Anda harus memiliki kredensial yang sesuai jika Anda ingin menggunakan alat "
|
||
"command-line untuk membuat kueri terhadap OpenStack cloud Anda. Sejauh ini, "
|
||
"cara termudah untuk mendapatkan kredensial :term:`authentication` untuk "
|
||
"digunakan dengan klien command-line adalah dengan menggunakan dasbor "
|
||
"OpenStack. Pilih :guilabel:`Project`, klik tab :guilabel:`Project`, dan "
|
||
"klik :guilabel:`Access & Security` pada kategory :guilabel:`Compute`. Pada "
|
||
"halaman :guilabel:`Access & Security`, klik tab :guilabel:`API Access` untuk "
|
||
"menampilkan dua tombol, :guilabel:`Download OpenStack RC File` dan :guilabel:"
|
||
"`Download EC2 Credentials`, yang memungkinkan Anda menghasilkan file yang "
|
||
"Anda dapat sumber dalam shell Anda untuk mengisi variabel lingkungan alat "
|
||
"command-line perlu tahu di mana endpoint layanan Anda dan informasi "
|
||
"otentikasi Anda. Pengguna yang Anda masuk ke dasbor menentukan nama file "
|
||
"untuk file openrc, seperti ``demo-openrc.sh``. Saat masuk sebagai admin, "
|
||
"file tersebut dinamai ``admin-openrc.sh``."
|
||
|
||
msgid ""
|
||
"You must remove the image after each test. Even better, test whether you can "
|
||
"successfully delete an image from the Image service."
|
||
msgstr ""
|
||
"Anda harus menghapus image setelah setiap tes. Lebih baik lagi, uji apakah "
|
||
"Anda berhasil menghapus image dari layanan Image."
|
||
|
||
msgid ""
|
||
"You should be doing sanity checks on the interfaces using command such as :"
|
||
"command:`ip a` and :command:`brctl show` to ensure that the interfaces are "
|
||
"actually up and configured the way that you think that they are."
|
||
msgstr ""
|
||
"Anda harus melakukan pemeriksaan kewarasan pada antarmuka menggunakan "
|
||
"perintah seperti :command:`ip a` dan :command:`brctl show` untuk memastikan "
|
||
"bahwa antarmuka benar-benar siap (up) dan mengkonfigurasi cara Anda berpikir "
|
||
"bahwa mereka."
|
||
|
||
msgid ""
|
||
"You should load balance user-facing services such as dashboard, ``nova-"
|
||
"api``, or the Object Storage proxy. Use any standard HTTP load-balancing "
|
||
"method (DNS round robin, hardware load balancer, or software such as Pound "
|
||
"or HAProxy). One caveat with dashboard is the VNC proxy, which uses the "
|
||
"WebSocket protocol— something that an L7 load balancer might struggle with. "
|
||
"See also `Horizon session storage <https://docs.openstack.org/horizon/latest/"
|
||
"admin/sessions.html>`_."
|
||
msgstr ""
|
||
"Anda harus memuat keseimbangan layanan yang menghadap pengguna seperti "
|
||
"dasbor, ``nova-api``, atau proksi Object Storage. Gunakan metode "
|
||
"penyeimbangan beban HTTP standar (round robin DNS, penyeimbang beban "
|
||
"perangkat keras, atau perangkat lunak seperti Pound atau HAProxy). Satu "
|
||
"peringatan dengan dashboard adalah proksi VNC, yang menggunakan protokol "
|
||
"WebSocket — sesuatu yang mungkin dihadapi oleh penyeimbang beban L7. Lihat "
|
||
"juga `Horizon session storage <https://docs.openstack.org/horizon/latest/"
|
||
"admin/sessions.html>`_."
|
||
|
||
msgid "You should see a message about ``/dev/sdb``."
|
||
msgstr "Anda harus melihat pesan tentang ``/dev/sdb``."
|
||
|
||
msgid "You should see a result similar to the following:"
|
||
msgstr "Anda akan melihat hasil yang serupa dengan yang berikut:"
|
||
|
||
msgid ""
|
||
"You should verify that you have the requisite backups to restore. Rolling "
|
||
"back upgrades is a tricky process because distributions tend to put much "
|
||
"more effort into testing upgrades than downgrades. Broken downgrades take "
|
||
"significantly more effort to troubleshoot and, resolve than broken upgrades. "
|
||
"Only you can weigh the risks of trying to push a failed upgrade forward "
|
||
"versus rolling it back. Generally, consider rolling back as the very last "
|
||
"option."
|
||
msgstr ""
|
||
"Anda harus memverifikasi bahwa Anda memiliki backup yang diperlukan untuk "
|
||
"restore. Rolling back upgrade adalah proses yang sulit karena distribusi "
|
||
"cenderung berupaya lebih banyak untuk menguji upgrade daripada downgrade "
|
||
"versi. Downgrade rusak membutuhkan upaya lebih besar untuk memecahkan "
|
||
"masalah dan, menyelesaikan daripada upgrade yang rusak. Hanya Anda yang "
|
||
"dapat mempertimbangkan risiko mencoba mendorong upgrade yang gagal ke depan "
|
||
"dibandingkan mengembalikannya. Secara umum, pertimbangkan rolling back "
|
||
"sebagai opsi terakhir."
|
||
|
||
msgid ""
|
||
"You want to keep an eye on the areas improving within OpenStack. The best "
|
||
"way to \"watch\" roadmaps for each project is to look at the blueprints that "
|
||
"are being approved for work on milestone releases. You can also learn from "
|
||
"PTL webinars that follow the OpenStack summits twice a year."
|
||
msgstr ""
|
||
"Anda ingin mengawasi area yang meningkat dalam OpenStack. Cara terbaik untuk "
|
||
"\"watch\" peta jalan untuk setiap proyek adalah dengan melihat cetak biru "
|
||
"yang disetujui untuk bekerja pada rilis tonggak. Anda juga dapat belajar "
|
||
"dari webinar PTL yang mengikuti KTT OpenStack dua kali setahun."
|
||
|
||
msgid ""
|
||
"Your credentials are a combination of username, password, and tenant "
|
||
"(project). You can extract these values from the ``openrc.sh`` discussed "
|
||
"above. The token allows you to interact with your other service endpoints "
|
||
"without needing to reauthenticate for every request. Tokens are typically "
|
||
"good for 24 hours, and when the token expires, you are alerted with a 401 "
|
||
"(Unauthorized) response and you can request another token."
|
||
msgstr ""
|
||
"Kredensial Anda adalah kombinasi nama pengguna, kata sandi, dan penyewa "
|
||
"(proyek). Anda dapat mengekstraksi nilai-nilai ini dari ``openrc.sh`` yang "
|
||
"dibahas di atas. Token memungkinkan Anda untuk berinteraksi dengan endpoint "
|
||
"layanan Anda yang lain tanpa perlu mengautentikasi ulang untuk setiap "
|
||
"permintaan. Token biasanya baik selama 24 jam, dan ketika token berakhir, "
|
||
"Anda diberitahu dengan respons 401 (Unauthorized) dan Anda dapat meminta "
|
||
"token lainnya."
|
||
|
||
msgid "\\* ``schedule_run_instance``"
|
||
msgstr "\\* ``schedule_run_instance``"
|
||
|
||
msgid "\\* ``select_destinations``"
|
||
msgstr "\\* ``select_destinations``"
|
||
|
||
msgid ""
|
||
"`A breakdown of current features under development, with their target "
|
||
"milestone <https://status.openstack.org/release/>`_"
|
||
msgstr ""
|
||
"`A breakdown of current features under development, with their target "
|
||
"milestone <https://status.openstack.org/release/>`_"
|
||
|
||
msgid ""
|
||
"`A list of all features, including those not yet under development <https://"
|
||
"blueprints.launchpad.net/openstack>`_"
|
||
msgstr ""
|
||
"`A list of all features, including those not yet under development <https://"
|
||
"blueprints.launchpad.net/openstack>`_"
|
||
|
||
msgid ""
|
||
"`A tcpdump Tutorial and Primer <https://danielmiessler.com/study/tcpdump/>`_"
|
||
msgstr ""
|
||
"`A tcpdump Tutorial and Primer <https://danielmiessler.com/study/tcpdump/>`_"
|
||
|
||
msgid ""
|
||
"`Ansible <https://www.ansible.com/>`_, with `OpenStack Ansible <https://"
|
||
"github.com/openstack/openstack-ansible>`_"
|
||
msgstr ""
|
||
"`Ansible <https://www.ansible.com/>`_, with `OpenStack Ansible <https://"
|
||
"github.com/openstack/openstack-ansible>`_"
|
||
|
||
msgid ""
|
||
"`Bare Metal service (ironic) upgrades <https://docs.openstack.org/ironic/"
|
||
"latest/admin/upgrade-guide.html>`_"
|
||
msgstr ""
|
||
"`Bare Metal service (ironic) upgrades <https://docs.openstack.org/ironic/"
|
||
"latest/admin/upgrade-guide.html>`_"
|
||
|
||
msgid ""
|
||
"`Block Storage service (cinder) upgrades <https://docs.openstack.org/cinder/"
|
||
"latest/upgrade.html>`_"
|
||
msgstr ""
|
||
"`Block Storage service (cinder) upgrades <https://docs.openstack.org/cinder/"
|
||
"latest/upgrade.html>`_"
|
||
|
||
msgid ""
|
||
"`CERN Cloud Infrastructure User Guide <http://information-technology.web."
|
||
"cern.ch/book/cern-private-cloud-user-guide>`_"
|
||
msgstr ""
|
||
"`CERN Cloud Infrastructure User Guide <http://information-technology.web."
|
||
"cern.ch/book/cern-private-cloud-user-guide>`_"
|
||
|
||
msgid "`CSAIL homepage <https://www.csail.mit.edu/>`_"
|
||
msgstr "`CSAIL homepage <https://www.csail.mit.edu/>`_"
|
||
|
||
msgid ""
|
||
"`Chef <https://www.chef.io/chef/>`_, with available `OpenStack Chef recipes "
|
||
"<https://github.com/openstack/openstack-chef-repo>`_"
|
||
msgstr ""
|
||
"`Chef <https://www.chef.io/chef/>`_, with available `OpenStack Chef recipes "
|
||
"<https://github.com/openstack/openstack-chef-repo>`_"
|
||
|
||
msgid ""
|
||
"`Compute service (nova) upgrades <https://docs.openstack.org/nova/latest/"
|
||
"user/upgrade.html>`_"
|
||
msgstr ""
|
||
"`Compute service (nova) upgrades <https://docs.openstack.org/nova/latest/"
|
||
"user/upgrade.html>`_"
|
||
|
||
msgid "`DAIR homepage <https://www.canarie.ca/cloud/>`__"
|
||
msgstr "`DAIR homepage <https://www.canarie.ca/cloud/>`__"
|
||
|
||
msgid "`Dive Into Python (Apress) <http://www.diveintopython.net/>`_"
|
||
msgstr "`Dive Into Python (Apress) <http://www.diveintopython.net/>`_"
|
||
|
||
msgid ""
|
||
"`Don <https://github.com/openstack/python-don>`_ is another convenient "
|
||
"network analysis and diagnostic system that provides a completely automated "
|
||
"service for verifying and diagnosing the networking functionality provided "
|
||
"by OVS."
|
||
msgstr ""
|
||
"`Don <https://github.com/openstack/python-don>`_ adalah analisis jaringan "
|
||
"dan sistem diagnostik yang nyaman yang menyediakan layanan yang sepenuhnya "
|
||
"otomatis untuk memverifikasi dan mendiagnosis fungsionalitas jaringan yang "
|
||
"disediakan oleh OVS."
|
||
|
||
msgid ""
|
||
"`Identity service (keystone) upgrades <https://docs.openstack.org/keystone/"
|
||
"latest/admin/identity-upgrading.html>`_"
|
||
msgstr ""
|
||
"`Identity service (keystone) upgrades <https://docs.openstack.org/keystone/"
|
||
"latest/admin/identity-upgrading.html>`_"
|
||
|
||
msgid ""
|
||
"`Image service (glance) database upgrades <https://docs.openstack.org/glance/"
|
||
"latest/admin/db.html>`_"
|
||
msgstr ""
|
||
"`Image service (glance) database upgrades <https://docs.openstack.org/glance/"
|
||
"latest/admin/db.html>`_"
|
||
|
||
msgid ""
|
||
"`List of OpenStack releases and release notes <https://releases.openstack."
|
||
"org/>`_"
|
||
msgstr ""
|
||
"`List of OpenStack releases and release notes <https://releases.openstack."
|
||
"org/>`_"
|
||
|
||
msgid ""
|
||
"`List of individual code changes under review <https://review.openstack.org/"
|
||
">`_"
|
||
msgstr ""
|
||
"`List of individual code changes under review <https://review.openstack.org/"
|
||
">`_"
|
||
|
||
msgid "`NeCTAR-RC GitHub <https://github.com/NeCTAR-RC/>`_"
|
||
msgstr "`NeCTAR-RC GitHub <https://github.com/NeCTAR-RC/>`_"
|
||
|
||
msgid ""
|
||
"`Networking service (neutron) upgrades <https://docs.openstack.org/neutron/"
|
||
"latest/contributor/internals/upgrade.html>`_"
|
||
msgstr ""
|
||
"`Networking service (neutron) upgrades <https://docs.openstack.org/neutron/"
|
||
"latest/contributor/internals/upgrade.html>`_"
|
||
|
||
msgid ""
|
||
"`Object Storage service (swift) upgrades <https://docs.openstack.org/swift/"
|
||
"latest/overview_policies.html#upgrading-and-confirming-functionality>`_"
|
||
msgstr ""
|
||
"`Object Storage service (swift) upgrades <https://docs.openstack.org/swift/"
|
||
"latest/overview_policies.html#upgrading-and-confirming-functionality>`_"
|
||
|
||
msgid ""
|
||
"`OpenStack Administrator Guide <https://docs.openstack.org/admin-guide/>`_"
|
||
msgstr ""
|
||
"`OpenStack Administrator Guide <https://docs.openstack.org/admin-guide/>`_"
|
||
|
||
msgid "`OpenStack Cloud Computing Cookbook <https://openstackcookbook.com/>`_"
|
||
msgstr "`OpenStack Cloud Computing Cookbook <https://openstackcookbook.com/>`_"
|
||
|
||
msgid ""
|
||
"`OpenStack Installation Tutorial for Red Hat Enterprise Linux and CentOS "
|
||
"<https://docs.openstack.org/ocata/install-guide-rdo/>`_"
|
||
msgstr ""
|
||
"`OpenStack Installation Tutorial for Red Hat Enterprise Linux and CentOS "
|
||
"<https://docs.openstack.org/ocata/install-guide-rdo/>`_"
|
||
|
||
msgid ""
|
||
"`OpenStack Installation Tutorial for Ubuntu Server <https://docs.openstack."
|
||
"org/ocata/install-guide-ubuntu/>`_"
|
||
msgstr ""
|
||
"`OpenStack Installation Tutorial for Ubuntu Server <https://docs.openstack."
|
||
"org/ocata/install-guide-ubuntu/>`_"
|
||
|
||
msgid ""
|
||
"`OpenStack Installation Tutorial for openSUSE and SUSE Linux Enterprise "
|
||
"Server <https://docs.openstack.org/ocata/install-guide-obs/>`_"
|
||
msgstr ""
|
||
"`OpenStack Installation Tutorial for openSUSE and SUSE Linux Enterprise "
|
||
"Server <https://docs.openstack.org/ocata/install-guide-obs/>`_"
|
||
|
||
msgid ""
|
||
"`OpenStack in Production: A tale of 3 OpenStack Clouds <https://openstack-in-"
|
||
"production.blogspot.de/2013/09/a-tale-of-3-openstack-clouds-50000.html>`_"
|
||
msgstr ""
|
||
"`OpenStack in Production: A tale of 3 OpenStack Clouds <https://openstack-in-"
|
||
"production.blogspot.de/2013/09/a-tale-of-3-openstack-clouds-50000.html>`_"
|
||
|
||
msgid "`Pro Puppet (Apress) <https://www.apress.com/9781430230571>`_"
|
||
msgstr "`Pro Puppet (Apress) <https://www.apress.com/9781430230571>`_"
|
||
|
||
msgid ""
|
||
"`Problem with Heavy Network IO and Dnsmasq <https://www.gossamer-threads.com/"
|
||
"lists/openstack/operators/18197>`_."
|
||
msgstr ""
|
||
"`Problem with Heavy Network IO and Dnsmasq <https://www.gossamer-threads.com/"
|
||
"lists/openstack/operators/18197>`_."
|
||
|
||
msgid ""
|
||
"`Puppet <https://puppet.com/>`_, with available `OpenStack Puppet modules "
|
||
"<https://github.com/puppetlabs/puppetlabs-openstack>`_"
|
||
msgstr ""
|
||
"`Puppet <https://puppet.com/>`_, with available `OpenStack Puppet modules "
|
||
"<https://github.com/puppetlabs/puppetlabs-openstack>`_"
|
||
|
||
msgid "`Puppet Labs Documentation <https://docs.puppet.com/>`_"
|
||
msgstr "`Puppet Labs Documentation <https://docs.puppet.com/>`_"
|
||
|
||
msgid ""
|
||
"`Review of CERN Data Centre Infrastructure <http://cds.cern.ch/"
|
||
"record/1457989/files/chep%202012%20CERN%20infrastructure%20final.pdf?"
|
||
"version=1>`_"
|
||
msgstr ""
|
||
"`Review of CERN Data Centre Infrastructure <http://cds.cern.ch/"
|
||
"record/1457989/files/chep%202012%20CERN%20infrastructure%20final.pdf?"
|
||
"version=1>`_"
|
||
|
||
msgid ""
|
||
"`Rough-draft design discussions (\"etherpads\") from the last design summit "
|
||
"<https://wiki.openstack.org/wiki/Summit/Kilo/Etherpads>`_"
|
||
msgstr ""
|
||
"`Rough-draft design discussions (\"etherpads\") from the last design summit "
|
||
"<https://wiki.openstack.org/wiki/Summit/Kilo/Etherpads>`_"
|
||
|
||
msgid ""
|
||
"`TCP/IP Illustrated, Volume 1: The Protocols, 2/E (Pearson) <https://www."
|
||
"pearsonhighered.com/educator/product/TCPIP-Illustrated-Volume-1-The-"
|
||
"Protocols/9780321336316.page>`_"
|
||
msgstr ""
|
||
"`TCP/IP Illustrated, Volume 1: The Protocols, 2/E (Pearson) <https://www."
|
||
"pearsonhighered.com/educator/product/TCPIP-Illustrated-Volume-1-The-"
|
||
"Protocols/9780321336316.page>`_"
|
||
|
||
msgid ""
|
||
"`Telemetry service (ceilometer) upgrades <https://docs.openstack.org/"
|
||
"ceilometer/ocata/install/upgrade.html>`_"
|
||
msgstr ""
|
||
"`Telemetry service (ceilometer) upgrades <https://docs.openstack.org/"
|
||
"ceilometer/ocata/install/upgrade.html>`_"
|
||
|
||
msgid ""
|
||
"`The Book of Xen (No Starch Press) <https://nostarch.com/releases/xen.html>`_"
|
||
msgstr ""
|
||
"`The Book of Xen (No Starch Press) <https://nostarch.com/releases/xen.html>`_"
|
||
|
||
msgid ""
|
||
"`The NIST Definition of Cloud Computing <https://nvlpubs.nist.gov/nistpubs/"
|
||
"Legacy/SP/nistspecialpublication800-145.pdf>`_"
|
||
msgstr ""
|
||
"`The NIST Definition of Cloud Computing <https://nvlpubs.nist.gov/nistpubs/"
|
||
"Legacy/SP/nistspecialpublication800-145.pdf>`_"
|
||
|
||
msgid ""
|
||
"`The TCP/IP Guide (No Starch Press) <https://www.nostarch.com/tcpip.htm>`_"
|
||
msgstr ""
|
||
"`The TCP/IP Guide (No Starch Press) <https://www.nostarch.com/tcpip.htm>`_"
|
||
|
||
msgid ""
|
||
"`UNIX and Linux Systems Administration Handbook (Prentice Hall) <https://www."
|
||
"admin.com/>`_"
|
||
msgstr ""
|
||
"`UNIX and Linux Systems Administration Handbook (Prentice Hall) <https://www."
|
||
"admin.com/>`_"
|
||
|
||
msgid ""
|
||
"``/etc/cinder`` and ``/var/log/cinder`` follow the same rules as other "
|
||
"components."
|
||
msgstr ""
|
||
"``/etc/cinder`` and ``/var/log/cinder`` ikuti aturan yang sama dengan "
|
||
"komponen lainnya."
|
||
|
||
msgid ""
|
||
"``/etc/glance`` and ``/var/log/glance`` follow the same rules as their nova "
|
||
"counterparts."
|
||
msgstr ""
|
||
"``/etc/glance`` and ``/var/log/glance`` ikuti aturan yang sama dengan "
|
||
"counterpart Nova mereka."
|
||
|
||
msgid ""
|
||
"``/etc/keystone`` and ``/var/log/keystone`` follow the same rules as other "
|
||
"components."
|
||
msgstr ""
|
||
"``/etc/keystone`` and ``/var/log/keystone`` ikuti aturan yang sama dengan "
|
||
"komponen lainnya."
|
||
|
||
msgid ""
|
||
"``/etc/neutron`` and ``/var/log/neutron`` follow the same rules as other "
|
||
"components."
|
||
msgstr ""
|
||
"``/etc/neutron`` and ``/var/log/neutron`` ikuti aturan yang sama dengan "
|
||
"komponen lainnya."
|
||
|
||
msgid ""
|
||
"``/etc/swift`` is very important to have backed up. This directory contains "
|
||
"the swift configuration files as well as the ring files and ring :term:"
|
||
"`builder files <builder file>`, which if lost, render the data on your "
|
||
"cluster inaccessible. A best practice is to copy the builder files to all "
|
||
"storage nodes along with the ring files. Multiple backup copies are spread "
|
||
"throughout your storage cluster."
|
||
msgstr ""
|
||
"``/etc/swift`` sangat penting untuk didukung. Direktori ini berisi file "
|
||
"konfigurasi swift serta file ring dan ring :term:`builder files <builder "
|
||
"file>`, yang jika hilang, membuat data di cluster Anda tidak dapat diakses. "
|
||
"Praktik terbaik adalah menyalin file pembangun ke semua node penyimpanan "
|
||
"bersama dengan file ring. Beberapa salinan cadangan tersebar di seluruh "
|
||
"kluster penyimpanan Anda."
|
||
|
||
msgid "``/var/lib/cinder`` should also be backed up."
|
||
msgstr "``/var/lib/cinder`` juga harus didukung."
|
||
|
||
msgid ""
|
||
"``/var/lib/glance`` should also be backed up. Take special notice of ``/var/"
|
||
"lib/glance/images``. If you are using a file-based back end of glance, ``/"
|
||
"var/lib/glance/images`` is where the images are stored and care should be "
|
||
"taken."
|
||
msgstr ""
|
||
"``/var/lib/glance`` juga harus didukung. Perhatikan ``/var/lib/glance/"
|
||
"images``.Jika Anda menggunakan back end berbasis file dari glance, ``/var/"
|
||
"lib/glance/images`` Di sinilah image disimpan dan perawatan harus diambil."
|
||
|
||
msgid ""
|
||
"``/var/lib/keystone``, although it should not contain any data being used, "
|
||
"can also be backed up just in case."
|
||
msgstr ""
|
||
"``/var/lib/keystone``, meskipun tidak boleh berisi data apa pun yang "
|
||
"digunakan, juga dapat dicadangkan untuk berjaga-jaga."
|
||
|
||
msgid "``/var/lib/neutron`` should also be backed up."
|
||
msgstr "``/var/lib/neutron`` juga harus didukung."
|
||
|
||
msgid "``/var/lib/nova/instances/instance-<instance id>/console.log``"
|
||
msgstr "``/var/lib/nova/instances/instance-<instance id>/console.log``"
|
||
|
||
msgid "``/var/lib/nova/instances`` contains two types of directories."
|
||
msgstr "``/var/lib/nova/instances`` berisi dua jenis direktori."
|
||
|
||
msgid ""
|
||
"``/var/lib/nova`` is another important directory to back up. The exception "
|
||
"to this is the ``/var/lib/nova/instances`` subdirectory on compute nodes. "
|
||
"This subdirectory contains the KVM images of running instances. You would "
|
||
"want to back up this directory only if you need to maintain backup copies of "
|
||
"all instances. Under most circumstances, you do not need to do this, but "
|
||
"this can vary from cloud to cloud and your service levels. Also be aware "
|
||
"that making a backup of a live KVM instance can cause that instance to not "
|
||
"boot properly if it is ever restored from a backup."
|
||
msgstr ""
|
||
"``/var/lib/nova`` adalah direktori penting lainnya untuk dicadangkan. "
|
||
"Pengecualian untuk hal ini adalah subdirektori ``/var/lib/nova/instances`` "
|
||
"pada compute node. Subdirektori ini berisi image KVM dari instance yang "
|
||
"sedang berjalan. Anda ingin mencadangkan direktori ini hanya jika Anda perlu "
|
||
"mempertahankan salinan cadangan dari semua instance. Dalam sebagian besar "
|
||
"keadaan, Anda tidak perlu melakukan ini, tetapi ini dapat bervariasi dari "
|
||
"cloud ke cloud dan tingkat layanan Anda. Perlu diketahui juga bahwa membuat "
|
||
"cadangan instance KVM langsung dapat menyebabkan instance tersebut tidak "
|
||
"bisa boot dengan benar jika pernah dipulihkan dari cadangan."
|
||
|
||
msgid "``/var/log/apache2/``"
|
||
msgstr "``/var/log/apache2/``"
|
||
|
||
msgid "``/var/log/cinder/cinder-volume.log``"
|
||
msgstr "``/var/log/cinder/cinder-volume.log``"
|
||
|
||
msgid "``/var/log/cinder``"
|
||
msgstr "``/var/log/cinder``"
|
||
|
||
msgid "``/var/log/glance``"
|
||
msgstr "``/var/log/glance``"
|
||
|
||
msgid "``/var/log/keystone``"
|
||
msgstr "``/var/log/keystone``"
|
||
|
||
msgid "``/var/log/libvirt/libvirtd.log``"
|
||
msgstr "``/var/log/libvirt/libvirtd.log``"
|
||
|
||
msgid "``/var/log/neutron``"
|
||
msgstr "``/var/log/neutron``"
|
||
|
||
msgid "``/var/log/nova``"
|
||
msgstr "``/var/log/nova``"
|
||
|
||
msgid ""
|
||
"``/var/log/nova`` does not need to be backed up if you have all logs going "
|
||
"to a central area. It is highly recommended to use a central logging server "
|
||
"or back up the log directory."
|
||
msgstr ""
|
||
"``/var/log/nova`` tidak perlu dicadangkan jika semua log masuk ke area "
|
||
"pusat. Sangat disarankan untuk menggunakan server logging pusat atau membuat "
|
||
"cadangan direktori log."
|
||
|
||
msgid "``/var/log/rsyslog/c01.example.com/nova.log``"
|
||
msgstr "``/var/log/rsyslog/c01.example.com/nova.log``"
|
||
|
||
msgid "``/var/log/rsyslog/c02.example.com/nova.log``"
|
||
msgstr "``/var/log/rsyslog/c02.example.com/nova.log``"
|
||
|
||
msgid "``/var/log/rsyslog/nova.log``"
|
||
msgstr "``/var/log/rsyslog/nova.log``"
|
||
|
||
msgid "``/var/log/syslog``"
|
||
msgstr "``/var/log/syslog``"
|
||
|
||
msgid "``bandwidth_poll_interval``"
|
||
msgstr "``bandwidth_poll_interval``"
|
||
|
||
msgid "``cinder-*``"
|
||
msgstr "``cinder-*``"
|
||
|
||
msgid "``cinder-api``"
|
||
msgstr "``cinder-api``"
|
||
|
||
msgid "``cinder-scheduler``"
|
||
msgstr "``cinder-scheduler``"
|
||
|
||
msgid "``cinder.conf``:"
|
||
msgstr "``cinder.conf``:"
|
||
|
||
msgid "``cores``"
|
||
msgstr "``cores``"
|
||
|
||
msgid "``fixed-ips``"
|
||
msgstr "``fixed-ips``"
|
||
|
||
msgid "``fixed_ips``"
|
||
msgstr "``fixed_ips``"
|
||
|
||
msgid "``floating-ips``"
|
||
msgstr "``floating-ips``"
|
||
|
||
msgid "``floating_ips``"
|
||
msgstr "``floating_ips``"
|
||
|
||
msgid "``glance-*``"
|
||
msgstr "``glance-*``"
|
||
|
||
msgid "``glance-api.conf`` and ``glance-registry.conf``:"
|
||
msgstr "``glance-api.conf`` and ``glance-registry.conf``:"
|
||
|
||
msgid "``group_hosts``"
|
||
msgstr "``group_hosts``"
|
||
|
||
msgid "``heal_instance_info_cache_interval``"
|
||
msgstr "``heal_instance_info_cache_interval``"
|
||
|
||
msgid "``horizon``"
|
||
msgstr "``horizon``"
|
||
|
||
msgid "``host_state_interval``"
|
||
msgstr "``host_state_interval``"
|
||
|
||
msgid "``hosts_up``"
|
||
msgstr "``hosts_up``"
|
||
|
||
msgid "``image_cache_manager_interval``"
|
||
msgstr "``image_cache_manager_interval``"
|
||
|
||
msgid "``injected-file-content-bytes``"
|
||
msgstr "``injected-file-content-bytes``"
|
||
|
||
msgid "``injected-file-path-bytes``"
|
||
msgstr "``injected-file-path-bytes``"
|
||
|
||
msgid "``injected-files``"
|
||
msgstr "``injected-files``"
|
||
|
||
msgid "``instance_delete_interval``"
|
||
msgstr "``instance_delete_interval``"
|
||
|
||
msgid "``instances``"
|
||
msgstr "``instances``"
|
||
|
||
msgid "``key*``"
|
||
msgstr "``key*``"
|
||
|
||
msgid "``key-pairs``"
|
||
msgstr "``key-pairs``"
|
||
|
||
msgid "``key``"
|
||
msgstr "``key``"
|
||
|
||
msgid "``keystone-*``"
|
||
msgstr "``keystone-*``"
|
||
|
||
msgid "``keystone.conf``:"
|
||
msgstr "``keystone.conf``:"
|
||
|
||
msgid "``metadata-items``"
|
||
msgstr "``metadata-items``"
|
||
|
||
msgid "``n-sch``"
|
||
msgstr "``n-sch``"
|
||
|
||
msgid "``n-{name}``"
|
||
msgstr "``n-{name}``"
|
||
|
||
msgid "``neutron-*``"
|
||
msgstr "``neutron-*``"
|
||
|
||
msgid "``nova-*``"
|
||
msgstr "``nova-*``"
|
||
|
||
msgid "``nova-api`` services"
|
||
msgstr "layanan ``nova-api``"
|
||
|
||
msgid "``nova-compute``, cinder hosts"
|
||
msgstr "``nova-compute``, cinder hosts"
|
||
|
||
msgid "``nova-scheduler`` services"
|
||
msgstr "Layanan ``nova-scheduler`"
|
||
|
||
msgid "``nova.conf``:"
|
||
msgstr "``nova.conf``:"
|
||
|
||
msgid "``ram``"
|
||
msgstr "``ram``"
|
||
|
||
msgid "``reclaim_instance_interval``"
|
||
msgstr "``reclaim_instance_interval``"
|
||
|
||
msgid "``s-{name}``"
|
||
msgstr "``s-{name}``"
|
||
|
||
msgid "``security-group-rules``"
|
||
msgstr "``security-group-rules``"
|
||
|
||
msgid "``security-groups``"
|
||
msgstr "``security-groups``"
|
||
|
||
msgid "``shell``"
|
||
msgstr "``shell``"
|
||
|
||
msgid "``shelved_offload_time``"
|
||
msgstr "``shelved_offload_time``"
|
||
|
||
msgid "``shelved_poll_interval``"
|
||
msgstr "``shelved_poll_interval``"
|
||
|
||
msgid "``sync_power_state_interval``"
|
||
msgstr "``sync_power_state_interval``"
|
||
|
||
msgid "``update_service_capabilities``"
|
||
msgstr "``update_service_capabilities``"
|
||
|
||
msgid "``volume_usage_poll_interval``"
|
||
msgstr "``volume_usage_poll_interval``"
|
||
|
||
msgid ""
|
||
"`easyOVS <https://github.com/yeasy/easyOVS>`_ is a useful tool when it comes "
|
||
"to operating your OpenvSwitch bridges and iptables on your OpenStack "
|
||
"platform. It automatically associates the virtual ports with the VM MAC/IP, "
|
||
"VLAN tag and namespace information, as well as the iptables rules for VMs."
|
||
msgstr ""
|
||
"`easyOVS <https://github.com/yeasy/easyOVS>`_adalah alat yang berguna untuk "
|
||
"mengoperasikan jembatan dan iptables OpenvSwitch Anda pada platform "
|
||
"OpenStack Anda. Secara otomatis mengaitkan port virtual dengan VM MAC/IP, "
|
||
"tag VLAN dan informasi namespace, serta aturan iptables untuk VM."
|
||
|
||
msgid ""
|
||
"`instances losing IP address while running, due to No DHCPOFFER <https://www."
|
||
"gossamer-threads.com/lists/openstack/dev/14696>`_."
|
||
msgstr ""
|
||
"`instances losing IP address while running, due to No DHCPOFFER <https://www."
|
||
"gossamer-threads.com/lists/openstack/dev/14696>`_."
|
||
|
||
msgid "and the following log statement into the ``__call__`` method:"
|
||
msgstr "dan pernyataan log berikut ke dalam metode ``__call__``:"
|
||
|
||
msgid "cinder-api"
|
||
msgstr "cinder-api"
|
||
|
||
msgid "cinder-scheduler"
|
||
msgstr "cinder-scheduler"
|
||
|
||
msgid "cinder-volume"
|
||
msgstr "cinder-volume"
|
||
|
||
msgid "gigabytes"
|
||
msgstr "gigabytes"
|
||
|
||
msgid "glance-api"
|
||
msgstr "glance-api"
|
||
|
||
msgid "glance-registry"
|
||
msgstr "glance-registry"
|
||
|
||
msgid "horizon"
|
||
msgstr "horizon"
|
||
|
||
msgid "img_signature uses the signature called signature_64"
|
||
msgstr "img_signature menggunakan signature yang disebut signature_64"
|
||
|
||
msgid ""
|
||
"img_signature_certificate_uuid uses the value from cert_uuid in section 5 "
|
||
"above"
|
||
msgstr ""
|
||
"img_signature_certificate_uuid menggunakan nilai dari cert_uuid di bagian 5 "
|
||
"di atas"
|
||
|
||
msgid "img_signature_hash_method matches 'SHA-256' in section 2 above"
|
||
msgstr "img_signature_hash_method cocok dengan 'SHA-256' di bagian 2 di atas"
|
||
|
||
msgid "img_signature_key_type matches 'RSA-PSS' in section 2 above"
|
||
msgstr "img_signature_key_type cocok dengan 'RSA-PSS' di bagian 2 di atas"
|
||
|
||
msgid "iptables"
|
||
msgstr "iptables"
|
||
|
||
msgid "libvirt"
|
||
msgstr "libvirt"
|
||
|
||
msgid "m1.large"
|
||
msgstr "m1.large"
|
||
|
||
msgid "m1.medium"
|
||
msgstr "m1.medium"
|
||
|
||
msgid "m1.small"
|
||
msgstr "m1.small"
|
||
|
||
msgid "m1.tiny"
|
||
msgstr "m1.tiny"
|
||
|
||
msgid "m1.xlarge"
|
||
msgstr "m1.xlarge"
|
||
|
||
msgid "misc (swift, dnsmasq)"
|
||
msgstr "misc (swift, dnsmasq)"
|
||
|
||
msgid "neutron-api"
|
||
msgstr "neutron-api"
|
||
|
||
msgid "neutron-dhcp-agent"
|
||
msgstr "neutron-dhcp-agent"
|
||
|
||
msgid "neutron-l3-agent"
|
||
msgstr "neutron-l3-agent"
|
||
|
||
msgid "neutron-metadata-agent"
|
||
msgstr "neutron-metadata-agent"
|
||
|
||
msgid "neutron-openvswitch-agent"
|
||
msgstr "neutron-openvswitch-agent"
|
||
|
||
msgid "neutron-server"
|
||
msgstr "neutron-server"
|
||
|
||
msgid "nova-api"
|
||
msgstr "nova-api"
|
||
|
||
msgid "nova-compute"
|
||
msgstr "nova-compute"
|
||
|
||
msgid "nova-compute servers first need to be updated by the following steps:"
|
||
msgstr ""
|
||
"server nova-compute terlebih dahulu perlu diperbarui dengan langkah-langkah "
|
||
"berikut:"
|
||
|
||
msgid "nova-conductor"
|
||
msgstr "nova-conductor"
|
||
|
||
msgid "nova-novncproxy"
|
||
msgstr "nova-novncproxy"
|
||
|
||
msgid "nova-scheduler"
|
||
msgstr "nova-scheduler"
|
||
|
||
msgid "rsyslog"
|
||
msgstr "rsyslog"
|
||
|
||
msgid "rsyslog client configuration"
|
||
msgstr "konfigurasi klien rsyslog"
|
||
|
||
msgid "rsyslog server configuration"
|
||
msgstr "konfigurasi server rsyslog"
|
||
|
||
msgid "showed this particular node in a down state."
|
||
msgstr "menunjukkan node khusus ini dalam kondisi turun."
|
||
|
||
msgid "snapshots"
|
||
msgstr "snapshots"
|
||
|
||
msgid "tcpdump"
|
||
msgstr "tcpdump"
|
||
|
||
msgid ""
|
||
"vlan20 is the VLAN that the data center gave us for outgoing Internet "
|
||
"access. It's a correct VLAN and is also attached to bond0."
|
||
msgstr ""
|
||
"vlan20 adalah VLAN yang diberikan pusat data kepada kami untuk akses "
|
||
"Internet keluar. Ini adalah VLAN yang benar dan juga melekat pada bond0."
|
||
|
||
msgid "where ``nova`` is the database you want to back up."
|
||
msgstr "di mana ``nova`` adalah basis data yang ingin Anda buat cadangannya."
|
||
|
||
msgid ""
|
||
"will keep the RPC version locked across the specified services to the RPC "
|
||
"version used in X+1. As all instances of a particular service are upgraded "
|
||
"to the newer version, the corresponding line can be removed from ``nova."
|
||
"conf``."
|
||
msgstr ""
|
||
"akan membuat versi RPC terkunci di seluruh layanan yang ditentukan ke versi "
|
||
"RPC yang digunakan dalam X+1. Karena semua instance layanan tertentu "
|
||
"ditingkatkan (upgraded) ke versi yang lebih baru, baris yang sesuai dapat "
|
||
"dihapus dari ``nova.conf``."
|
||
|
||
msgid ""
|
||
"“The Cloud” has been described as a volatile environment where servers can "
|
||
"be created and terminated at will. While this may be true, it does not mean "
|
||
"that your servers must be volatile. Ensuring that your cloud's hardware is "
|
||
"stable and configured correctly means that your cloud environment remains up "
|
||
"and running."
|
||
msgstr ""
|
||
"\"The Cloud\" telah dideskripsikan sebagai lingkungan yang tidak stabil di "
|
||
"mana server dapat dibuat dan diakhiri sesuka hati. Meskipun ini mungkin "
|
||
"benar, itu tidak berarti bahwa server Anda harus tidak stabil. Memastikan "
|
||
"perangkat keras cloud Anda stabil dan terkonfigurasi dengan benar berarti "
|
||
"bahwa lingkungan cloud Anda tetap aktif dan berjalan."
|