summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorOpenStack Proposal Bot <openstack-infra@lists.openstack.org>2019-01-27 07:47:31 +0000
committerOpenStack Proposal Bot <openstack-infra@lists.openstack.org>2019-01-27 07:47:31 +0000
commiteebd22a58db694ac02c4de1d1b4fee0f7dbbc86f (patch)
treeb9f96f3bfcbfe3b157979ad6f101bf7dbafb28c1
parentcd60edff981e80ad318c57b49665c8ba43fe2845 (diff)
Imported Translations from Zanata
For more information about this automatic import see: https://docs.openstack.org/i18n/latest/reviewing-translation-import.html Change-Id: Ie5bcb0da46ea087eafafde475eae4be6b875cce6
Notes
Notes (review): Code-Review+2: Andreas Jaeger <jaegerandi@gmail.com> Workflow+1: Andreas Jaeger <jaegerandi@gmail.com> Verified+2: Zuul Submitted-by: Zuul Submitted-at: Sun, 27 Jan 2019 16:33:51 +0000 Reviewed-on: https://review.openstack.org/633393 Project: openstack/operations-guide Branch: refs/heads/master
-rw-r--r--doc/source/locale/de/LC_MESSAGES/doc.po37
-rw-r--r--doc/source/locale/id/LC_MESSAGES/doc.po11557
2 files changed, 11583 insertions, 11 deletions
diff --git a/doc/source/locale/de/LC_MESSAGES/doc.po b/doc/source/locale/de/LC_MESSAGES/doc.po
index ea38d9a..64dcd99 100644
--- a/doc/source/locale/de/LC_MESSAGES/doc.po
+++ b/doc/source/locale/de/LC_MESSAGES/doc.po
@@ -6,11 +6,11 @@ msgid ""
6msgstr "" 6msgstr ""
7"Project-Id-Version: operations-guide\n" 7"Project-Id-Version: operations-guide\n"
8"Report-Msgid-Bugs-To: \n" 8"Report-Msgid-Bugs-To: \n"
9"POT-Creation-Date: 2019-01-25 14:46+0000\n" 9"POT-Creation-Date: 2019-01-26 12:01+0000\n"
10"MIME-Version: 1.0\n" 10"MIME-Version: 1.0\n"
11"Content-Type: text/plain; charset=UTF-8\n" 11"Content-Type: text/plain; charset=UTF-8\n"
12"Content-Transfer-Encoding: 8bit\n" 12"Content-Transfer-Encoding: 8bit\n"
13"PO-Revision-Date: 2019-01-25 10:56+0000\n" 13"PO-Revision-Date: 2019-01-26 12:14+0000\n"
14"Last-Translator: Andreas Jaeger <jaegerandi@gmail.com>\n" 14"Last-Translator: Andreas Jaeger <jaegerandi@gmail.com>\n"
15"Language-Team: German\n" 15"Language-Team: German\n"
16"Language: de\n" 16"Language: de\n"
@@ -5264,7 +5264,7 @@ msgid ""
5264msgstr "" 5264msgstr ""
5265"Wenn Sie einen Bug finden, den Sie nicht selbst beseitigen können oder Sie " 5265"Wenn Sie einen Bug finden, den Sie nicht selbst beseitigen können oder Sie "
5266"sind nicht sicher, ob es tatsächlich ein Fehler in den Docs ist, öffnen Sie " 5266"sind nicht sicher, ob es tatsächlich ein Fehler in den Docs ist, öffnen Sie "
5267"einen Bug im ` Storyboard <https://storyboard.openstack.org/#!/project/" 5267"einen Bug im `Storyboard <https://storyboard.openstack.org/#!/project/"
5268"openstack/operations-guide>`_. Sie können sich den Bug selbst zuweisen wenn " 5268"openstack/operations-guide>`_. Sie können sich den Bug selbst zuweisen wenn "
5269"Sie wissen, wie er zu beseitigen ist. Oder Mitglieder des OpenStack " 5269"Sie wissen, wie er zu beseitigen ist. Oder Mitglieder des OpenStack "
5270"Operations-doc Teams bewerten ihn bei einer Triage." 5270"Operations-doc Teams bewerten ihn bei einer Triage."
@@ -5538,7 +5538,7 @@ msgstr ""
5538"ist dies eine gute Möglichkeit, um mit der Teilnahme oder der Organisation " 5538"ist dies eine gute Möglichkeit, um mit der Teilnahme oder der Organisation "
5539"einer Schulung zu beginnen. Die OpenStack Foundation verfügt über einen " 5539"einer Schulung zu beginnen. Die OpenStack Foundation verfügt über einen "
5540"`Trainingsmarktplatz <https://www.openstack.org/marketplace/training>`_, auf " 5540"`Trainingsmarktplatz <https://www.openstack.org/marketplace/training>`_, auf "
5541"dem Sie nach Veranstaltungen in der Nähe suchen können. Außerdem arbeitet " 5541"dem Sie nach Veranstaltungen in der Nähe suchen können. Außerdem `arbeitet "
5542"die OpenStack-Community daran, <https://wiki.openstack.org/wiki/Training-" 5542"die OpenStack-Community daran, <https://wiki.openstack.org/wiki/Training-"
5543"guides>`_ Open-Source-Trainingsmaterialien zu erstellen." 5543"guides>`_ Open-Source-Trainingsmaterialien zu erstellen."
5544 5544
@@ -7495,7 +7495,7 @@ msgstr ""
7495"Open vSwitch, wie in den vorherigen OpenStack Networking-Beispielen " 7495"Open vSwitch, wie in den vorherigen OpenStack Networking-Beispielen "
7496"verwendet, ist ein vollwertiger mehrschichtiger virtueller Switch, der unter " 7496"verwendet, ist ein vollwertiger mehrschichtiger virtueller Switch, der unter "
7497"der Open-Source-Lizenz Apache 2.0 lizenziert ist. Die vollständige " 7497"der Open-Source-Lizenz Apache 2.0 lizenziert ist. Die vollständige "
7498"Dokumentation finden Sie auf der Website des Projekts <http://www." 7498"Dokumentation finden Sie auf der `Website des Projekts <http://www."
7499"openvswitch.org/>`_. In der Praxis ist es angesichts der vorhergehenden " 7499"openvswitch.org/>`_. In der Praxis ist es angesichts der vorhergehenden "
7500"Konfiguration am häufigsten der Fall, sicherzustellen, dass die " 7500"Konfiguration am häufigsten der Fall, sicherzustellen, dass die "
7501"erforderlichen Brücken (``br-int``, ``br-tun``, `br-tun`` und ``br-ex``) " 7501"erforderlichen Brücken (``br-int``, ``br-tun``, `br-tun`` und ``br-ex``) "
@@ -10094,6 +10094,21 @@ msgid "The connection strings take this format:"
10094msgstr "Die Verbindungszeichenketten haben dieses Format:" 10094msgstr "Die Verbindungszeichenketten haben dieses Format:"
10095 10095
10096msgid "" 10096msgid ""
10097"The currently implemented hypervisors are listed on the `OpenStack "
10098"Configuration Reference <https://docs.openstack.org/ocata/config-reference/"
10099"compute/hypervisors.html>`__. You can see a matrix of the various features "
10100"in OpenStack Compute (nova) hypervisor drivers at the `Hypervisor support "
10101"matrix page <https://docs.openstack.org/nova/latest/user/support-matrix."
10102"html>`_."
10103msgstr ""
10104"Die aktuell implementierten Hypervisoren sind in der `OpenStack "
10105"Configuration Reference <https://docs.openstack.org/ocata/config-reference/"
10106"compute/hypervisors.html>`__ aufgelistet. Eine Matrix der verschiedenen "
10107"Features in den OpenStack Compute (nova) Hypervisor-Treibern finden Sie auf "
10108"der `Hypervisor Supportmatrix-Seite <https://docs.openstack.org/nova/latest/"
10109"user/support-matrix.html>`_."
10110
10111msgid ""
10097"The dangerous possibility comes with the ability to change member roles. " 10112"The dangerous possibility comes with the ability to change member roles. "
10098"This is the dropdown list below the username in the :guilabel:`Project " 10113"This is the dropdown list below the username in the :guilabel:`Project "
10099"Members` list. In virtually all cases, this value should be set to :guilabel:" 10114"Members` list. In virtually all cases, this value should be set to :guilabel:"
@@ -12764,7 +12779,7 @@ msgid ""
12764"DevStack environment." 12779"DevStack environment."
12765msgstr "" 12780msgstr ""
12766"Um den ersten Pfad zu nehmen, können Sie den OpenStack-Code direkt ändern. " 12781"Um den ersten Pfad zu nehmen, können Sie den OpenStack-Code direkt ändern. "
12767"Erfahren Sie, wie Sie einen Beitrag leisten können <https://wiki.openstack." 12782"Erfahren Sie, `wie Sie einen Beitrag leisten können <https://wiki.openstack."
12768"org/wiki/How_To_Contribute>`_, folgen Sie dem `Developer's Guide <https://" 12783"org/wiki/How_To_Contribute>`_, folgen Sie dem `Developer's Guide <https://"
12769"docs.openstack.org/infra/manual/developers.html>`_, nehmen Sie Ihre " 12784"docs.openstack.org/infra/manual/developers.html>`_, nehmen Sie Ihre "
12770"Änderungen vor und tragen Sie sie wieder in das vorgelagerte OpenStack-" 12785"Änderungen vor und tragen Sie sie wieder in das vorgelagerte OpenStack-"
@@ -14397,7 +14412,7 @@ msgid ""
14397"admin-guide/cli-manage-projects-users-and-roles.html>`_ from the command-" 14412"admin-guide/cli-manage-projects-users-and-roles.html>`_ from the command-"
14398"line clients." 14413"line clients."
14399msgstr "" 14414msgstr ""
14400"Sie können auch Projekte, Benutzer und Rollen <https://docs.openstack.org/" 14415"Sie können auch `Projekte, Benutzer und Rollen <https://docs.openstack.org/"
14401"admin-guide/cli-manage-projects-users-and-roles.html>`_ über die " 14416"admin-guide/cli-manage-projects-users-and-roles.html>`_ über die "
14402"Befehlszeilen-Clients verwalten." 14417"Befehlszeilen-Clients verwalten."
14403 14418
@@ -15028,7 +15043,7 @@ msgid ""
15028"latest/overview_policies.html#upgrading-and-confirming-functionality>`_" 15043"latest/overview_policies.html#upgrading-and-confirming-functionality>`_"
15029msgstr "" 15044msgstr ""
15030"`Object Storage Service (swift) Upgrades <https://docs.openstack.org/swift/" 15045"`Object Storage Service (swift) Upgrades <https://docs.openstack.org/swift/"
15031"latest/overview_policies.html#Upgrade- und Bestätigungsfunktionalität>`_" 15046"latest/overview_policies.html#upgrading-and-confirming-functionality>`_"
15032 15047
15033msgid "" 15048msgid ""
15034"`OpenStack API Guide <https://developer.openstack.org/api-guide/quick-start/" 15049"`OpenStack API Guide <https://developer.openstack.org/api-guide/quick-start/"
@@ -15056,7 +15071,7 @@ msgid ""
15056"`OpenStack Configuration Reference <https://docs.openstack.org/ocata/config-" 15071"`OpenStack Configuration Reference <https://docs.openstack.org/ocata/config-"
15057"reference/>`_" 15072"reference/>`_"
15058msgstr "" 15073msgstr ""
15059"OpenStack-Konfigurationsreferenz <https://docs.openstack.org/ocata/config-" 15074"`OpenStack-Konfigurationsreferenz <https://docs.openstack.org/ocata/config-"
15060"reference/>`_" 15075"reference/>`_"
15061 15076
15062msgid "`OpenStack End User Guide <https://docs.openstack.org/user-guide/>`_" 15077msgid "`OpenStack End User Guide <https://docs.openstack.org/user-guide/>`_"
@@ -15081,7 +15096,7 @@ msgid ""
15081"`OpenStack Installation Tutorial for Ubuntu <https://docs.openstack.org/" 15096"`OpenStack Installation Tutorial for Ubuntu <https://docs.openstack.org/"
15082"ocata/install-guide-ubuntu/>`_" 15097"ocata/install-guide-ubuntu/>`_"
15083msgstr "" 15098msgstr ""
15084"OpenStack Installations-Tutorial für Ubuntu <https://docs.openstack.org/" 15099"`OpenStack Installations-Tutorial für Ubuntu <https://docs.openstack.org/"
15085"ocata/install-guide-ubuntu/>`_" 15100"ocata/install-guide-ubuntu/>`_"
15086 15101
15087msgid "" 15102msgid ""
@@ -15095,7 +15110,7 @@ msgid ""
15095"`OpenStack Installation Tutorial for openSUSE and SUSE Linux Enterprise " 15110"`OpenStack Installation Tutorial for openSUSE and SUSE Linux Enterprise "
15096"<https://docs.openstack.org/ocata/install-guide-obs/>`_" 15111"<https://docs.openstack.org/ocata/install-guide-obs/>`_"
15097msgstr "" 15112msgstr ""
15098"Tutorial zur OpenStack-Installation für openSUSE und SUSE Linux Enterprise " 15113"`Tutorial zur OpenStack-Installation für openSUSE und SUSE Linux Enterprise "
15099"<https://docs.openstack.org/ocata/install-guide-obs/>`_" 15114"<https://docs.openstack.org/ocata/install-guide-obs/>`_"
15100 15115
15101msgid "" 15116msgid ""
diff --git a/doc/source/locale/id/LC_MESSAGES/doc.po b/doc/source/locale/id/LC_MESSAGES/doc.po
new file mode 100644
index 0000000..6dca179
--- /dev/null
+++ b/doc/source/locale/id/LC_MESSAGES/doc.po
@@ -0,0 +1,11557 @@
1# suhartono <cloudsuhartono@gmail.com>, 2018. #zanata
2# suhartono <cloudsuhartono@gmail.com>, 2019. #zanata
3msgid ""
4msgstr ""
5"Project-Id-Version: operations-guide\n"
6"Report-Msgid-Bugs-To: \n"
7"POT-Creation-Date: 2019-01-26 12:01+0000\n"
8"MIME-Version: 1.0\n"
9"Content-Type: text/plain; charset=UTF-8\n"
10"Content-Transfer-Encoding: 8bit\n"
11"PO-Revision-Date: 2019-01-27 07:46+0000\n"
12"Last-Translator: suhartono <cloudsuhartono@gmail.com>\n"
13"Language-Team: Indonesian\n"
14"Language: id\n"
15"X-Generator: Zanata 4.3.3\n"
16"Plural-Forms: nplurals=1; plural=0\n"
17
18msgid "\"Hey Alvaro, can you run a VLAN on top of a VLAN?\""
19msgstr "\"Hey Alvaro, can you run a VLAN on top of a VLAN?\""
20
21msgid "\"If you did, you'd add an extra 4 bytes to the packet…\""
22msgstr "\"If you did, you'd add an extra 4 bytes to the packet…\""
23
24msgid "\"The Issue\""
25msgstr "\"The Issue\""
26
27msgid "**Block Storage service (cinder)**"
28msgstr "**Block Storage service (cinder)**"
29
30msgid "**Compute nodes**"
31msgstr "**Compute nodes**"
32
33msgid "**Compute service (nova)**"
34msgstr "**Compute service (nova)**"
35
36msgid "**Controller node**"
37msgstr "**Controller node**"
38
39msgid "**Create a port that can be reused**"
40msgstr "**Create a port that can be reused**"
41
42msgid "**Detach a port from an instance**"
43msgstr "**Detach a port from an instance**"
44
45msgid "**Example of Complexity**"
46msgstr "**Example of Complexity**"
47
48msgid "**Example**"
49msgstr "**Example**"
50
51msgid "**Identity service (keystone)**"
52msgstr "**Identity service (keystone)**"
53
54msgid "**Image service (glance)**"
55msgstr "**Image service (glance)**"
56
57msgid "**Networking service (neutron)**"
58msgstr "**Networking service (neutron)**"
59
60msgid "**Overhead**"
61msgstr "**Overhead**"
62
63msgid "**Provision an instance**"
64msgstr "**Provision an instance**"
65
66msgid ""
67"**Retrieve an IP address when an instance is deleted before detaching a "
68"port**"
69msgstr ""
70"**Retrieve an IP address when an instance is deleted before detaching a "
71"port**"
72
73msgid "**Shared services**"
74msgstr "**Shared services**"
75
76msgid "**Storage nodes**"
77msgstr "**Storage nodes**"
78
79msgid ""
80"**To capture packets from the patch-tun internal interface on integration "
81"bridge, br-int:**"
82msgstr ""
83"**To capture packets from the patch-tun internal interface on integration "
84"bridge, br-int:**"
85
86msgid ""
87"**To create the middleware and plug it in through Paste configuration:**"
88msgstr ""
89"**To create the middleware and plug it in through Paste configuration:**"
90
91msgid "**To create the scheduler and plug it in through configuration**"
92msgstr "**To create the scheduler and plug it in through configuration**"
93
94msgid ""
95"**To discover which internal VLAN tag is in use for a GRE tunnel by using "
96"the ovs-ofctl command**"
97msgstr ""
98"**To discover which internal VLAN tag is in use for a GRE tunnel by using "
99"the ovs-ofctl command**"
100
101msgid ""
102"**To discover which internal VLAN tag is in use for a given external VLAN by "
103"using the ovs-ofctl command**"
104msgstr ""
105"**To discover which internal VLAN tag is in use for a given external VLAN by "
106"using the ovs-ofctl command**"
107
108msgid "**To perform a rollback**"
109msgstr "**To perform a rollback**"
110
111msgid "**To update Block Storage quotas for a tenant (project)**"
112msgstr "**To update Block Storage quotas for a tenant (project)**"
113
114msgid "**To update quota values for a tenant (project)**"
115msgstr "**To update quota values for a tenant (project)**"
116
117msgid "**To view Block Storage quotas for a tenant (project)**"
118msgstr "**To view Block Storage quotas for a tenant (project)**"
119
120msgid "**To view and update default Block Storage quota values**"
121msgstr "**To view and update default Block Storage quota values**"
122
123msgid "**Use**"
124msgstr "**Use**"
125
126msgid "*Actions which delete things should not be enabled by default.*"
127msgstr "*Actions which delete things should not be enabled by default.*"
128
129msgid "/var/lib/nova/instances"
130msgstr "/var/lib/nova/instances"
131
132msgid "0 GB"
133msgstr "0 GB"
134
135msgid "1"
136msgstr "1"
137
138msgid "1 GB"
139msgstr "1 GB"
140
141msgid "10"
142msgstr "10"
143
144msgid "10 GB"
145msgstr "10 GB"
146
147msgid "100"
148msgstr "100"
149
150msgid "15"
151msgstr "15"
152
153msgid "16 GB"
154msgstr "16 GB"
155
156msgid "160 GB"
157msgstr "160 GB"
158
159msgid "2"
160msgstr "2"
161
162msgid "2 GB"
163msgstr "2 GB"
164
165msgid "20"
166msgstr "20"
167
168msgid "20 GB"
169msgstr "20 GB"
170
171msgid "200 physical cores."
172msgstr "200 physical cores."
173
174msgid "21"
175msgstr "21"
176
177msgid "22"
178msgstr "22"
179
180msgid "3"
181msgstr "3"
182
183msgid "4"
184msgstr "4"
185
186msgid "4 GB"
187msgstr "4 GB"
188
189msgid "40 GB"
190msgstr "40 GB"
191
192msgid "5"
193msgstr "5"
194
195msgid "512 MB"
196msgstr "512 MB"
197
198msgid "8"
199msgstr "8"
200
201msgid "8 GB"
202msgstr "8 GB"
203
204msgid "80 GB"
205msgstr "80 GB"
206
207msgid "98"
208msgstr "98"
209
210msgid "99"
211msgstr "99"
212
213msgid ":command:`cinder-manage`"
214msgstr ":command:`cinder-manage`"
215
216msgid ":command:`euca-describe-availability-zones verbose`"
217msgstr ":command:`euca-describe-availability-zones verbose`"
218
219msgid ":command:`glance-manage`"
220msgstr ":command:`glance-manage`"
221
222msgid ":command:`keystone-manage`"
223msgstr ":command:`keystone-manage`"
224
225msgid ":command:`nova-manage`"
226msgstr ":command:`nova-manage`"
227
228msgid ":command:`openstack compute service list`"
229msgstr ":command:`openstack compute service list`"
230
231msgid ":command:`openstack host list` (os-hosts)"
232msgstr ":command:`openstack host list` (os-hosts)"
233
234msgid ""
235":ref:`table_segregation_methods` provides a comparison view of each "
236"segregation method currently provided by OpenStack Compute."
237msgstr ""
238":ref:`table_segregation_methods` memberikan tampilan perbandingan setiap "
239"metode pemisahan yang saat ini disediakan oleh OpenStack Compute."
240
241msgid ""
242":term:`Availability zones <availability zone>` and host aggregates, which "
243"merely divide a single Compute deployment."
244msgstr ""
245":term:`Availability zones <availability zone>` dan host agregat, yang hanya "
246"membagi satu penyebaran Compute."
247
248msgid ""
249"A DHCP problem might be caused by a misbehaving dnsmasq process. First, "
250"debug by checking logs and then restart the dnsmasq processes only for that "
251"project (tenant). In VLAN mode, there is a dnsmasq process for each tenant. "
252"Once you have restarted targeted dnsmasq processes, the simplest way to rule "
253"out dnsmasq causes is to kill all of the dnsmasq processes on the machine "
254"and restart ``nova-network``. As a last resort, do this as root:"
255msgstr ""
256"Masalah DHCP mungkin disebabkan oleh proses dnsmasq yang salah. Pertama, "
257"debug dengan memeriksa log dan kemudian restart proses dnsmasq hanya untuk "
258"proyek itu (tenant). Dalam mode VLAN, ada proses dnsmasq untuk setiap "
259"tenant. Setelah Anda me-restart proses dnsmasq yang ditargetkan, cara paling "
260"sederhana untuk mengesampingkan penyebab dnsmasq adalah dengan mematikan "
261"semua proses dnsmasq pada mesin dan me-restart ``nova-network``. Sebagai "
262"upaya terakhir, lakukan ini sebagai root:"
263
264msgid ""
265"A NetApp appliance is used in each region for both block storage and "
266"instance storage. There are future plans to move the instances off the "
267"NetApp appliance and onto a distributed file system such as :term:`Ceph` or "
268"GlusterFS."
269msgstr ""
270"Alat NetApp digunakan di setiap wilayah untuk penyimpanan blok dan "
271"penyimpanan instance. Ada rencana di masa depan untuk memindahkan instance "
272"dari alat NetApp dan ke sistem file terdistribusi seperti :term: `Ceph` atau "
273"GlusterFS."
274
275msgid ""
276"A basic type of alert monitoring is to simply check and see whether a "
277"required process is running. For example, ensure that the ``nova-api`` "
278"service is running on the cloud controller:"
279msgstr ""
280"Jenis dasar pemantauan peringatan adalah dengan hanya memeriksa dan melihat "
281"apakah proses yang diperlukan sedang berjalan. Sebagai contoh, pastikan "
282"bahwa layanan ``nova-api`` berjalan pada pengontrol cloud:"
283
284msgid ""
285"A cloud controller node runs several different services. You can install "
286"services that communicate only using the message queue internally— ``nova-"
287"scheduler`` and ``nova-console`` on a new server for expansion. However, "
288"other integral parts require more care."
289msgstr ""
290"Node pengontrol cloud menjalankan beberapa layanan berbeda. Anda dapat "
291"menginstal layanan yang berkomunikasi hanya menggunakan antrian pesan secara "
292"internal— ``nova-scheduler`` dan `` nova-console`` pada server baru untuk "
293"ekspansi. Namun, bagian integral lainnya membutuhkan perawatan lebih."
294
295msgid ""
296"A cloud environment that is scaled to a certain size will require the file "
297"descriptor limits to be adjusted."
298msgstr ""
299"Lingkungan cloud yang diskalakan ke ukuran tertentu akan membutuhkan batas "
300"deskriptor file untuk disesuaikan."
301
302msgid ""
303"A cloud with multiple sites where you can schedule VMs \"anywhere\" or on a "
304"particular site."
305msgstr ""
306"Cloud dengan banyak situs tempat Anda dapat menjadwalkan VM \"anywhere\" "
307"atau di situs tertentu."
308
309msgid ""
310"A cloud with multiple sites, where you schedule VMs to a particular site and "
311"you want a shared infrastructure."
312msgstr ""
313"Cloud dengan banyak situs, tempat Anda menjadwalkan VM ke situs tertentu dan "
314"Anda menginginkan infrastruktur bersama."
315
316msgid ""
317"A common scenario is to take down production management services in "
318"preparation for an upgrade, completed part of the upgrade process, and "
319"discovered one or more problems not encountered during testing. As a "
320"consequence, you must roll back your environment to the original \"known good"
321"\" state. You also made sure that you did not make any state changes after "
322"attempting the upgrade process; no new instances, networks, storage volumes, "
323"and so on. Any of these new resources will be in a frozen state after the "
324"databases are restored from backup."
325msgstr ""
326"Skenario umum adalah menghapus layanan manajemen produksi dalam persiapan "
327"untuk upgrade, menyelesaikan bagian dari proses upgrade, dan menemukan satu "
328"atau lebih masalah yang tidak ditemukan selama pengujian. Sebagai akibatnya, "
329"Anda harus memutar kembali (roll back) lingkungan Anda ke keadaan \"known "
330"good\" yang asli. Anda juga memastikan bahwa Anda tidak membuat perubahan "
331"keadaan setelah mencoba proses upgrade; tidak ada instance baru, jaringan, "
332"volume penyimpanan, dan sebagainya. Sumber daya baru ini akan dalam keadaan "
333"beku setelah database dipulihkan dari cadangan."
334
335msgid ""
336"A common use of host aggregates is to provide information for use with the "
337"``nova-scheduler``. For example, you might use a host aggregate to group a "
338"set of hosts that share specific flavors or images."
339msgstr ""
340"Penggunaan agregat host yang umum adalah untuk memberikan informasi untuk "
341"digunakan dengan ``nova-scheduler``. Misalnya, Anda dapat menggunakan "
342"agregat host untuk mengelompokkan serangkaian host yang berbagi flavor atau "
343"image tertentu."
344
345msgid ""
346"A common way of dealing with the recovery from a full system failure, such "
347"as a power outage of a data center, is to assign each service a priority, "
348"and restore in order. :ref:`table_example_priority` shows an example."
349msgstr ""
350"Cara umum menangani pemulihan dari kegagalan sistem penuh, seperti pemadaman "
351"listrik pusat data, adalah menetapkan setiap layanan sebagai prioritas, dan "
352"memulihkannya secara berurutan. :ref: `table_example_priority` menampilkan "
353"contoh."
354
355msgid "A compute node"
356msgstr "Node komputasi "
357
358msgid ""
359"A critical part of a cloud's scalability is the amount of effort that it "
360"takes to run your cloud. To minimize the operational cost of running your "
361"cloud, set up and use an automated deployment and configuration "
362"infrastructure with a configuration management system, such as :term:"
363"`Puppet` or :term:`Chef`. Combined, these systems greatly reduce manual "
364"effort and the chance for operator error."
365msgstr ""
366"Bagian penting dari skalabilitas cloud adalah jumlah upaya yang diperlukan "
367"untuk menjalankan cloud Anda. Untuk meminimalkan biaya operasional "
368"menjalankan cloud Anda, atur dan gunakan penyebaran otomatis dan "
369"infrastruktur konfigurasi dengan sistem manajemen konfigurasi, seperti :term:"
370"`Puppet` atau :term:`Chef`. Digabungkan, sistem ini sangat mengurangi upaya "
371"manual dan kemungkinan kesalahan operator."
372
373msgid ""
374"A different API endpoint for every region. Each region has a full nova "
375"installation."
376msgstr ""
377"Endpoint API yang berbeda untuk setiap wilayah. Setiap wilayah memiliki "
378"instalasi nova lengkap."
379
380msgid ""
381"A feature was introduced in Essex to periodically check and see if there "
382"were any ``_base`` files not in use. If there were, OpenStack Compute would "
383"delete them. This idea sounds innocent enough and has some good qualities to "
384"it. But how did this feature end up turned on? It was disabled by default in "
385"Essex. As it should be. It was `decided to be turned on in Folsom <https://"
386"bugs.launchpad.net/nova/+bug/1029674>`_. I cannot emphasize enough that:"
387msgstr ""
388"Fitur diperkenalkan di Essex untuk secara berkala memeriksa dan melihat "
389"apakah ada ``_base`` file yang tidak digunakan. Jika ada, OpenStack Compute "
390"akan menghapusnya. Gagasan ini kedengarannya cukup polos dan memiliki "
391"kualitas yang bagus. Tetapi bagaimana fitur ini akhirnya dihidupkan? Itu "
392"dinonaktifkan secara default di Essex. Seperti seharusnya. Dulu `decided to "
393"be turned on in Folsom <https://bugs.launchpad.net/nova/+bug/1029674>`_. "
394"Saya tidak bisa cukup menekankan bahwa:"
395
396msgid "A few nights later, it happened again."
397msgstr "Beberapa malam kemudian, itu terjadi lagi."
398
399msgid ""
400"A long requested service, to provide the ability to manipulate DNS entries "
401"associated with OpenStack resources has gathered a following. The designate "
402"project was also released."
403msgstr ""
404"Layanan yang lama diminta, untuk menyediakan kemampuan untuk memanipulasi "
405"entri DNS yang terkait dengan sumber daya OpenStack telah mengumpulkan hal "
406"berikut. Proyek yang ditunjuk juga dirilis."
407
408msgid ""
409"A major quality push has occurred across drivers and plug-ins in Block "
410"Storage, Compute, and Networking. Particularly, developers of Compute and "
411"Networking drivers that require proprietary or hardware products are now "
412"required to provide an automated external testing system for use during the "
413"development process."
414msgstr ""
415"Peningkatan kualitas utama telah terjadi di seluruh driver dan plug-in di "
416"Block Storage, Compute, dan Networking. Khususnya, pengembang driver Compute "
417"dan Networking yang memerlukan produk-produk perangkat keras atau "
418"kepemilikan sekarang diminta untuk menyediakan sistem pengujian eksternal "
419"otomatis untuk digunakan selama proses pengembangan."
420
421msgid ""
422"A much-requested answer to big data problems, a dedicated team has been "
423"making solid progress on a Hadoop-as-a-Service project."
424msgstr ""
425"Jawaban yang banyak diminta untuk masalah big data, tim berdedikasi telah "
426"membuat kemajuan yang solid pada proyek Hadoop-as-a-Service."
427
428msgid ""
429"A note about DAIR's architecture: ``/var/lib/nova/instances`` is a shared "
430"NFS mount. This means that all compute nodes have access to it, which "
431"includes the ``_base`` directory. Another centralized area is ``/var/log/"
432"rsyslog`` on the cloud controller. This directory collects all OpenStack "
433"logs from all compute nodes. I wondered if there were any entries for the "
434"file that :command:`virsh` is reporting:"
435msgstr ""
436"Catatan tentang arsitektur DAIR: ``/var/lib/nova/instances`` adalah mount "
437"NFS bersama. Ini berarti bahwa semua node komputasi memiliki akses ke sana, "
438"yang mencakup direktori ``_base``. Area terpusat lainnya adalah ``/var/log/"
439"rsyslog`` pada pengontrol cloud. Direktori ini mengumpulkan semua log "
440"OpenStack dari semua node komputasi. Saya bertanya-tanya apakah ada entri "
441"untuk file yang :command:`virsh` melaporkan:"
442
443msgid ""
444"A number of operating systems use rsyslog as the default logging service. "
445"Since it is natively able to send logs to a remote location, you do not have "
446"to install anything extra to enable this feature, just modify the "
447"configuration file. In doing this, consider running your logging over a "
448"management network or using an encrypted VPN to avoid interception."
449msgstr ""
450"Sejumlah sistem operasi menggunakan rsyslog sebagai layanan logging standar. "
451"Karena secara asli dapat mengirim log ke lokasi yang jauh, Anda tidak perlu "
452"menginstal apa pun tambahan untuk mengaktifkan fitur ini, cukup modifikasi "
453"file konfigurasi. Dalam melakukan ini, pertimbangkan untuk menjalankan "
454"pendataan Anda melalui jaringan manajemen atau menggunakan VPN terenkripsi "
455"untuk menghindari intersepsi."
456
457msgid ""
458"A quick Google search turned up this: `DHCP lease errors in VLAN mode "
459"<https://lists.launchpad.net/openstack/msg11696.html>`_ which further "
460"supported our DHCP theory."
461msgstr ""
462"Pencarian Google cepat muncul ini: `DHCP lease errors in VLAN mode <https://"
463"lists.launchpad.net/openstack/msg11696.html>`_ yang selanjutnya mendukung "
464"teori DHCP kami."
465
466msgid ""
467"A quick way to check whether DNS is working is to resolve a hostname inside "
468"your instance by using the :command:`host` command. If DNS is working, you "
469"should see:"
470msgstr ""
471"Cara cepat untuk memeriksa apakah DNS berfungsi adalah dengan menyelesaikan "
472"nama host di dalam instance Anda dengan menggunakan perintah :command:"
473"`host`. Jika DNS berfungsi, Anda akan melihat:"
474
475msgid ""
476"A report came in: VMs were launching slowly, or not at all. Cue the standard "
477"checks—nothing on the Nagios, but there was a spike in network towards the "
478"current master of our RabbitMQ cluster. Investigation started, but soon the "
479"other parts of the queue cluster were leaking memory like a sieve. Then the "
480"alert came in—the master Rabbit server went down and connections failed over "
481"to the slave."
482msgstr ""
483"Sebuah laporan muncul: VM diluncurkan perlahan, atau tidak sama sekali. Beri "
484"tanda pada pemeriksaan standar — tidak ada apa pun di Nagios, tetapi ada "
485"lonjakan jaringan terhadap master saat ini dari kluster RabbitMQ kami. "
486"Investigasi dimulai, tetapi segera bagian-bagian lain dari antrian cluster "
487"membocorkan memori seperti saringan (sieve). Kemudian peringatan datang — "
488"server master Kelinci down dan koneksi gagal ke slave."
489
490msgid ""
491"A security domain comprises of users, applications, servers or networks that "
492"share common trust requirements and expectations within a system. Typically "
493"they have the same authentication and authorization requirements and users."
494msgstr ""
495"Domain keamanan terdiri dari pengguna, aplikasi, server atau jaringan yang "
496"berbagi persyaratan dan harapan kepercayaan bersama dalam suatu sistem. "
497"Biasanya mereka memiliki persyaratan dan pengguna otentikasi dan otorisasi "
498"yang sama."
499
500msgid "A service to provide queues of messages and notifications was released."
501msgstr "Layanan untuk menyediakan antrian pesan dan pemberitahuan dirilis."
502
503msgid "A shell where you can get some work done"
504msgstr "Shell tempat Anda bisa menyelesaikan pekerjaan"
505
506msgid ""
507"A similar pattern can be followed in other projects that use the driver "
508"architecture. Simply create a module and class that conform to the driver "
509"interface and plug it in through configuration. Your code runs when that "
510"feature is used and can call out to other services as necessary. No project "
511"core code is touched. Look for a \"driver\" value in the project's ``.conf`` "
512"configuration files in ``/etc/<project>`` to identify projects that use a "
513"driver architecture."
514msgstr ""
515"Pola serupa dapat diikuti dalam proyek lain yang menggunakan arsitektur "
516"driver. Cukup buat modul dan kelas yang sesuai dengan antarmuka driver dan "
517"hubungkan melalui konfigurasi. Kode Anda berjalan ketika fitur itu digunakan "
518"dan dapat memanggil layanan lain yang diperlukan. Tidak ada kode core proyek "
519"yang disentuh. Cari nilai \"driver\" di file konfigurasi ``.conf`` proyek di "
520"``/etc/<project>`` untuk mengidentifikasi proyek yang menggunakan arsitektur "
521"driver."
522
523msgid ""
524"A single :term:`API endpoint` for compute, or you require a second level of "
525"scheduling."
526msgstr ""
527"Single :term:`API endpoint` untuk komputasi, atau Anda memerlukan "
528"penjadwalan tingkat kedua."
529
530msgid "A single-site cloud with equipment fed by separate power supplies."
531msgstr ""
532"Single-site cloud dengan peralatan yang diumpankan oleh catu daya terpisah."
533
534msgid ""
535"A tangible example of this is the ``nova-compute`` process. In order to "
536"manage the image cache with libvirt, ``nova-compute`` has a periodic process "
537"that scans the contents of the image cache. Part of this scan is calculating "
538"a checksum for each of the images and making sure that checksum matches what "
539"``nova-compute`` expects it to be. However, images can be very large, and "
540"these checksums can take a long time to generate. At one point, before it "
541"was reported as a bug and fixed, ``nova-compute`` would block on this task "
542"and stop responding to RPC requests. This was visible to users as failure of "
543"operations such as spawning or deleting instances."
544msgstr ""
545"Contoh nyata dari ini adalah proses ``nova-compute``. Untuk mengelola cache "
546"image dengan libvirt, ``nova-compute`` memiliki proses periodik yang "
547"memindai isi cache image. Bagian dari pemindaian ini menghitung checksum "
548"untuk setiap image dan memastikan bahwa checksum cocok dengan apa yang "
549"diharapkan oleh ``nova-compute``. Namun, image bisa sangat besar, dan "
550"checksum ini dapat memakan waktu lama untuk dibuat. Pada satu titik, sebelum "
551"dilaporkan sebagai bug dan diperbaiki, ``nova-compute`` akan memblokir tugas "
552"ini dan berhenti merespons permintaan RPC. Ini terlihat oleh pengguna "
553"sebagai kegagalan operasi seperti memijah atau menghapus instance."
554
555msgid ""
556"A tool such as **collectd** can be used to store this information. While "
557"collectd is out of the scope of this book, a good starting point would be to "
558"use collectd to store the result as a COUNTER data type. More information "
559"can be found in `collectd's documentation <https://collectd.org/wiki/index."
560"php/Data_source>`_."
561msgstr ""
562"Alat seperti **collectd ** dapat digunakan untuk menyimpan informasi ini. "
563"Meskipun collectd berada di luar cakupan buku ini, titik awal yang baik "
564"adalah menggunakan collectd untuk menyimpan hasilnya sebagai tipe data "
565"COUNTER. Informasi lebih lanjut dapat ditemukan di `collectd's documentation "
566"<https://collectd.org/wiki/index.php/Data_source>`_."
567
568msgid "A user recently tried launching a CentOS instance on that node"
569msgstr ""
570"Seorang pengguna baru-baru ini mencoba meluncurkan instance CentOS pada node "
571"itu"
572
573msgid "AMQP broker"
574msgstr "AMQP broker"
575
576msgid "Abstract"
577msgstr "Abstrak"
578
579msgid "Account quotas"
580msgstr "Kuota akun"
581
582msgid "Acknowledgements"
583msgstr "Ucapan Terima Kasih"
584
585msgid ""
586"Adam Powell in Racker IT supplied us with bandwidth each day and second "
587"monitors for those of us needing more screens."
588msgstr ""
589"Adam Powell di Racker IT memberi kami bandwidth setiap hari dan monitor "
590"kedua bagi kami yang membutuhkan lebih banyak layar."
591
592msgid ""
593"Add all raw disks to one large RAID array, either hardware or software "
594"based. You can partition this large array with the boot, root, swap, and LVM "
595"areas. This option is simple to implement and uses all partitions. However, "
596"disk I/O might suffer."
597msgstr ""
598"Tambahkan semua disk baku ke satu array RAID besar, baik berbasis perangkat "
599"keras atau perangkat lunak. Anda dapat mempartisi array besar ini dengan "
600"area boot, root, swap, dan LVM. Opsi ini mudah diterapkan dan menggunakan "
601"semua partisi. Namun, disk I/O mungkin terbebani."
602
603msgid "Add device ``snooper0`` to bridge ``br-int``:"
604msgstr "Tambahkan perangkat ``snooper0`` untuk menjembatani ``br-int``:"
605
606msgid "Add metadata to the container to allow the IP:"
607msgstr "Tambahkan metadata ke kontainer untuk memungkinkan IP:"
608
609msgid "Add the repository for the new release packages."
610msgstr "Tambahkan repositori untuk paket rilis baru."
611
612msgid "Adding Custom Logging Statements"
613msgstr "Menambahkan Pernyataan Logging Kustom"
614
615msgid "Adding Images"
616msgstr "Menambahkan Images"
617
618msgid "Adding Projects"
619msgstr "Menambahkan Proyek"
620
621msgid "Adding Signed Images"
622msgstr "Menambahkan Signed Images"
623
624msgid "Adding a Compute Node"
625msgstr "Menambahkan Node Komputasi"
626
627msgid ""
628"Adding a new object storage node is different from adding compute or block "
629"storage nodes. You still want to initially configure the server by using "
630"your automated deployment and configuration-management systems. After that "
631"is done, you need to add the local disks of the object storage node into the "
632"object storage ring. The exact command to do this is the same command that "
633"was used to add the initial disks to the ring. Simply rerun this command on "
634"the object storage proxy server for all disks on the new object storage "
635"node. Once this has been done, rebalance the ring and copy the resulting "
636"ring files to the other storage nodes."
637msgstr ""
638"Menambahkan node penyimpanan objek baru berbeda dari menambahkan komputasi "
639"atau memblokir node penyimpanan. Anda masih ingin mengkonfigurasi server "
640"dengan menggunakan sistem manajemen konfigurasi dan penyebaran otomatis "
641"Anda. Setelah itu selesai, Anda perlu menambahkan disk lokal dari node "
642"penyimpanan objek ke dalam ring penyimpanan objek. Perintah yang tepat untuk "
643"melakukan ini adalah perintah yang sama yang digunakan untuk menambahkan "
644"disk awal ke ring. Cukup jalankan kembali perintah ini pada server proxy "
645"penyimpanan objek untuk semua disk pada node penyimpanan objek baru. Setelah "
646"ini selesai, menyeimbangkan ulang ring dan menyalin file ring yang "
647"dihasilkan ke node penyimpanan lainnya."
648
649msgid "Adding an Object Storage Node"
650msgstr "Menambahkan node penyimpanan objek ( Object Storage node)"
651
652msgid "Adding cloud controller nodes"
653msgstr "Menambahkan node pengontrol cloud"
654
655msgid ""
656"Adding to a RAID array (RAID stands for redundant array of independent "
657"disks), based on the number of disks you have available, so that you can add "
658"capacity as your cloud grows. Some options are described in more detail "
659"below."
660msgstr ""
661"Menambah array RAID (RAID adalah singkatan dari redundant array of "
662"independent disks), berdasarkan jumlah disk yang Anda miliki, sehingga Anda "
663"dapat menambah kapasitas saat cloud Anda tumbuh. Beberapa opsi dijelaskan "
664"secara lebih rinci di bawah ini."
665
666msgid ""
667"Additionally, for Identity-related issues, try the tips in :ref:"
668"`sql_backend`."
669msgstr ""
670"Selain itu, untuk masalah yang berkaitan dengan Identitas, cobalah kiat di :"
671"ref:`sql_backend`."
672
673msgid ""
674"Additionally, this instance in question was responsible for a very, very "
675"large backup job each night. While \"The Issue\" (as we were now calling it) "
676"didn't happen exactly when the backup happened, it was close enough (a few "
677"hours) that we couldn't ignore it."
678msgstr ""
679"Selain itu, instance ini bertanggung jawab atas pekerjaan backup yang "
680"sangat, sangat besar setiap malam. Sementara \"The Issue\" (seperti yang "
681"kita sebut sekarang) tidak terjadi tepat ketika backup terjadi, itu cukup "
682"dekat (beberapa jam) sehingga kami tidak bisa mengabaikannya."
683
684msgid ""
685"Additionally, you can refer to `neutron client <https://docs.openstack.org/"
686"python-neutronclient/latest/>`_ for more options."
687msgstr ""
688"Selain itu, Anda dapat merujuk `neutron client <https://docs.openstack.org/"
689"python-neutronclient/latest/>`_ untuk opsi lainnya."
690
691msgid ""
692"Adjust the appropriate limits in the ``/etc/security/limits.conf`` "
693"configuration file."
694msgstr ""
695"Sesuaikan batas yang sesuai dalam file konfigurasi ``/etc/security/limits."
696"conf``."
697
698msgid "Administrative Command-Line Tools"
699msgstr "Alat Command-Line Administratif"
700
701msgid "Advanced Configuration"
702msgstr "Konfigurasi Lanjutan"
703
704msgid "After a Compute Node Reboots"
705msgstr "Setelah node komputasi, reboot"
706
707msgid ""
708"After a cloud controller reboots, ensure that all required services were "
709"successfully started. The following commands use :command:`ps` and :command:"
710"`grep` to determine if nova, glance, and keystone are currently running:"
711msgstr ""
712"Setelah pengontrol cloud dinyalakan ulang, pastikan semua layanan yang "
713"diperlukan berhasil dimulai. Perintah berikut menggunakan :command:`ps` dan :"
714"command:`grep` untuk menentukan apakah nova, glance, dan keystone saat ini "
715"sedang berjalan:"
716
717msgid "After a few minutes of troubleshooting, I saw the following details:"
718msgstr "Setelah beberapa menit pemecahan masalah, saya melihat detail berikut:"
719
720msgid ""
721"After digging into the nova (OpenStack Compute) code, I noticed two areas in "
722"``api/ec2/cloud.py`` potentially impacting my system:"
723msgstr ""
724"Setelah menggali kode nova (OpenStack Compute), saya perhatikan dua area di "
725"``api/ec2/cloud.py`` yang berpotensi memengaruhi sistem saya:"
726
727msgid ""
728"After finding the instance ID we headed over to ``/var/lib/nova/instances`` "
729"to find the ``console.log``:"
730msgstr ""
731"Setelah menemukan ID instance kami menuju ke ``/var/lib/nova/instances`` "
732"untuk menemukan ``console.log``:"
733
734msgid ""
735"After migration, users see different results from :command:`openstack image "
736"list` and :command:`glance image-list`. To ensure users see the same images "
737"in the list commands, edit the :file:`/etc/glance/policy.json` file and :"
738"file:`/etc/nova/policy.json` file to contain ``\"context_is_admin\": \"role:"
739"admin\"``, which limits access to private images for projects."
740msgstr ""
741"Setelah migrasi, pengguna melihat hasil yang berbeda dari :command:"
742"`openstack image list` dan :command:`glance image-list`. Untuk memastikan "
743"pengguna melihat image yang sama dalam perintah daftar, edit file :file:`/"
744"etc/glance/policy.json` dan file :file:`/etc/nova/policy.json` yang berisi ``"
745"\"context_is_admin\": \"role:admin\"``, yang membatasi akses ke image "
746"pribadi untuk proyek."
747
748msgid ""
749"After reproducing the problem several times, I came to the unfortunate "
750"conclusion that this cloud did indeed have a problem. Even worse, my time "
751"was up in Kelowna and I had to return back to Calgary."
752msgstr ""
753"Setelah mereproduksi masalah beberapa kali, saya sampai pada kesimpulan yang "
754"tidak menguntungkan bahwa cloud ini memang memiliki masalah. Lebih buruk "
755"lagi, waktu saya habis di Kelowna dan saya harus kembali ke Calgary."
756
757msgid ""
758"After restarting the instance, everything was back up and running. We "
759"reviewed the logs and saw that at some point, network communication stopped "
760"and then everything went idle. We chalked this up to a random occurrence."
761msgstr ""
762"Setelah memulai kembali instance, semuanya kembali dan berjalan. Kami "
763"meninjau log dan melihat bahwa pada titik tertentu, komunikasi jaringan "
764"berhenti dan kemudian semuanya menjadi menganggur. Kami mencatat ini hingga "
765"kejadian acak."
766
767msgid ""
768"After that, use the :command:`openstack` command to reboot all instances "
769"that were on c01.example.com while regenerating their XML files at the same "
770"time:"
771msgstr ""
772"Setelah itu, gunakan perintah :command:`openstack` untuk me-reboot semua "
773"instance yang ada di c01.example.com saat membuat ulang file XML mereka pada "
774"saat yang sama:"
775
776msgid ""
777"After the compute node is successfully running, you must deal with the "
778"instances that are hosted on that compute node because none of them are "
779"running. Depending on your SLA with your users or customers, you might have "
780"to start each instance and ensure that they start correctly."
781msgstr ""
782"Setelah simpul komputasi berhasil dijalankan, Anda harus berurusan dengan "
783"instance yang dihosting pada simpul komputasi tersebut karena tidak ada "
784"satupun yang berjalan. Tergantung pada SLA Anda dengan pengguna atau "
785"pelanggan Anda, Anda mungkin harus memulai setiap instance dan memastikan "
786"bahwa mereka memulai dengan benar."
787
788msgid "After the dnsmasq processes start again, check whether DNS is working."
789msgstr "Setelah proses dnsmasq mulai lagi, periksa apakah DNS berfungsi."
790
791msgid ""
792"After the packet is on this NIC, it transfers to the compute node's default "
793"gateway. The packet is now most likely out of your control at this point. "
794"The diagram depicts an external gateway. However, in the default "
795"configuration with multi-host, the compute host is the gateway."
796msgstr ""
797"Setelah paket berada di NIC ini, ia mentransfer ke gateway default node "
798"komputasi. Paket sekarang kemungkinan besar di luar kendali Anda pada saat "
799"ini. Diagram menggambarkan gateway eksternal. Namun, dalam konfigurasi "
800"default dengan multi-host, host komputasi adalah gateway."
801
802msgid ""
803"After you consider these factors, you can determine how many cloud "
804"controller cores you require. A typical eight core, 8 GB of RAM server is "
805"sufficient for up to a rack of compute nodes — given the above caveats."
806msgstr ""
807"Setelah Anda mempertimbangkan faktor-faktor ini, Anda dapat menentukan "
808"berapa banyak core pengontrol cloud yang Anda butuhkan. Server delapan core, "
809"8 GB RAM biasanya cukup untuk satu rak node komputasi - mengingat peringatan "
810"di atas."
811
812msgid ""
813"After you establish that the instance booted properly, the task is to figure "
814"out where the failure is."
815msgstr ""
816"Setelah Anda memastikan bahwa instance boot dengan benar, tugasnya adalah "
817"mencari tahu di mana kegagalannya."
818
819msgid ""
820"After you have the list, you can use the :command:`openstack` command to "
821"start each instance:"
822msgstr ""
823"Setelah Anda memiliki daftar, Anda dapat menggunakan perintah :command:"
824"`openstack` untuk memulai setiap instance:"
825
826msgid ""
827"Again, it turns out that the image was a snapshot. The three other instances "
828"that successfully started were standard cloud images. Was it a problem with "
829"snapshots? That didn't make sense."
830msgstr ""
831"Sekali lagi, ternyata image itu adalah snapshot. Tiga instance lain yang "
832"berhasil dimulai adalah image cloud standar. Apakah itu masalah dengan foto? "
833"Itu tidak masuk akal."
834
835msgid ""
836"Again, the right answer depends on your environment. You have to make your "
837"decision based on the trade-offs between space utilization, simplicity, and "
838"I/O performance."
839msgstr ""
840"Sekali lagi, jawaban yang tepat tergantung pada lingkungan Anda. Anda harus "
841"membuat keputusan berdasarkan pertukaran antara pemanfaatan ruang, "
842"kesederhanaan, dan kinerja I/O."
843
844msgid "Ah-hah! So OpenStack was deleting it. But why?"
845msgstr "Ah-hah! Jadi OpenStack menghapusnya. Tapi kenapa?"
846
847msgid ""
848"All files and directories in ``/var/lib/nova/instances`` are uniquely named. "
849"The files in \\_base are uniquely titled for the glance image that they are "
850"based on, and the directory names ``instance-xxxxxxxx`` are uniquely titled "
851"for that particular instance. For example, if you copy all data from ``/var/"
852"lib/nova/instances`` on one compute node to another, you do not overwrite "
853"any files or cause any damage to images that have the same unique name, "
854"because they are essentially the same file."
855msgstr ""
856"Semua file dan direktori di ``/var/lib/nova/instances`` diberi nama unik. "
857"File-file di \\_base secara unik berjudul untuk glance image yang menjadi "
858"dasarnya, dan nama direktori ``instance-xxxxxxxx`` secara unik berjudul "
859"untuk instance tertentu. Misalnya, jika Anda menyalin semua data dari ``/"
860"var/lib/nova/instances`` pada satu node komputasi ke yang lain, Anda tidak "
861"menimpa file apa pun atau menyebabkan kerusakan pada image yang memiliki "
862"nama unik yang sama, karena mereka adalah dasarnya file yang sama."
863
864msgid ""
865"All in all, just issue the :command:`reboot` command. The operating system "
866"cleanly shuts down services and then automatically reboots. If you want to "
867"be very thorough, run your backup jobs just before you reboot."
868msgstr ""
869"Secara keseluruhan, cukup terbitkan perintah :command:`reboot` . Sistem "
870"operasi dengan bersih mematikan layanan dan kemudian secara otomatis reboot. "
871"Jika Anda ingin sangat teliti, jalankan pekerjaan cadangan Anda tepat "
872"sebelum Anda reboot."
873
874msgid ""
875"All interfaces on the ``br-tun`` are internal to Open vSwitch. To monitor "
876"traffic on them, you need to set up a mirror port as described above for "
877"``patch-tun`` in the ``br-int`` bridge."
878msgstr ""
879"Semua antarmuka pada ``br-tun`` bersifat internal ke Open vSwitch. Untuk "
880"memantau lalu lintas, Anda perlu mengatur port mirror seperti dijelaskan di "
881"atas untuk ``patch-tun`` di jembatan ``br-int``."
882
883msgid "All nodes"
884msgstr "All nodes"
885
886msgid ""
887"All of the alert types mentioned earlier can also be used for trend "
888"reporting. Some other trend examples include:"
889msgstr ""
890"Semua jenis peringatan yang disebutkan sebelumnya juga dapat digunakan untuk "
891"pelaporan tren. Beberapa contoh tren lainnya termasuk:"
892
893msgid ""
894"All of the code for OpenStack lives in ``/opt/stack``. Go to the swift "
895"directory in the ``shell`` screen and edit your middleware module."
896msgstr ""
897"Semua kode untuk OpenStack hidup di ``/opt/stack``. Buka direktori swift di "
898"layar ``shell`` dan edit modul middleware Anda."
899
900msgid ""
901"All sites are based on Ubuntu 14.04, with KVM as the hypervisor. The "
902"OpenStack version in use is typically the current stable version, with 5 to "
903"10 percent back-ported code from trunk and modifications."
904msgstr ""
905"Semua situs didasarkan pada Ubuntu 14.04, dengan KVM sebagai hypervisor. "
906"Versi OpenStack yang digunakan biasanya adalah versi stabil saat ini, dengan "
907"5 hingga 10 persen kode porting belakang dari trunk dan modifikasi."
908
909msgid ""
910"All translation of GRE tunnels to and from internal VLANs happens on this "
911"bridge."
912msgstr ""
913"Semua terjemahan terowongan GRE ke dan dari VLAN internal terjadi di "
914"jembatan ini."
915
916msgid "Allow DHCP client traffic."
917msgstr "Izinkan lalu lintas klien DHCP."
918
919msgid "Allow IPv6 ICMP traffic to allow RA packets."
920msgstr "Izinkan lalu lintas ICMP IPv6 untuk memungkinkan paket RA."
921
922msgid "Allow traffic from defined IP/MAC pairs."
923msgstr "Izinkan lalu lintas dari pasangan IP/MAC yang ditentukan."
924
925msgid ""
926"Almost all OpenStack components have an underlying database to store "
927"persistent information. Usually this database is MySQL. Normal MySQL "
928"administration is applicable to these databases. OpenStack does not "
929"configure the databases out of the ordinary. Basic administration includes "
930"performance tweaking, high availability, backup, recovery, and repairing. "
931"For more information, see a standard MySQL administration guide."
932msgstr ""
933"Hampir semua komponen OpenStack memiliki basis data untuk menyimpan "
934"informasi yang persisten. Biasanya database ini adalah MySQL. Administrasi "
935"MySQL normal berlaku untuk database ini. OpenStack tidak mengkonfigurasi "
936"basis data yang tidak biasa. Administrasi dasar mencakup penyesuaian "
937"kinerja, ketersediaan tinggi, cadangan, pemulihan, dan perbaikan. Untuk "
938"informasi lebih lanjut, lihat panduan administrasi MySQL standar."
939
940msgid ""
941"Also check that all services are functioning. The following set of commands "
942"sources the ``openrc`` file, then runs some basic glance, nova, and "
943"openstack commands. If the commands work as expected, you can be confident "
944"that those services are in working condition:"
945msgstr ""
946"Periksa juga apakah semua layanan berfungsi. Set perintah berikut sumber "
947"file ``openrc``, kemudian menjalankan beberapa perintah dasar glance, nova, "
948"dan openstack. Jika perintah berfungsi seperti yang diharapkan, Anda dapat "
949"yakin bahwa layanan tersebut dalam kondisi kerja:"
950
951msgid "Also check that it is functioning:"
952msgstr "Juga periksa apakah berfungsi:"
953
954msgid "Also ensure that it has successfully connected to the AMQP server:"
955msgstr "Juga memastikan bahwa ia telah berhasil terhubung ke server AMQP:"
956
957msgid ""
958"Also, in practice, the ``nova-compute`` services on the compute nodes do not "
959"always reconnect cleanly to rabbitmq hosted on the controller when it comes "
960"back up after a long reboot; a restart on the nova services on the compute "
961"nodes is required."
962msgstr ""
963"Juga, dalam praktiknya, layanan ``nova-compute`` pada node komputasi tidak "
964"selalu terhubung kembali dengan bersih ke rabbitmq yang dihosting pada "
965"pengontrol ketika ia kembali setelah boot ulang yang panjang; diperlukan "
966"restart layanan nova pada node komputasi."
967
968msgid "Alter the configuration until it works."
969msgstr "Ubah konfigurasi hingga berfungsi."
970
971msgid ""
972"Alternatively, it is possible to configure VLAN-based networks to use "
973"external routers rather than the l3-agent shown here, so long as the "
974"external router is on the same VLAN:"
975msgstr ""
976"Atau, dimungkinkan untuk mengkonfigurasi jaringan berbasis VLAN untuk "
977"menggunakan router eksternal daripada agen l3 yang ditunjukkan di sini, "
978"selama router eksternal berada di VLAN yang sama:"
979
980msgid ""
981"Although the title of this story is much more dramatic than the actual "
982"event, I don't think, or hope, that I'll have the opportunity to use "
983"\"Valentine's Day Massacre\" again in a title."
984msgstr ""
985"Meskipun judul cerita ini jauh lebih dramatis daripada peristiwa yang "
986"sebenarnya, saya tidak berpikir, atau berharap, bahwa saya akan memiliki "
987"kesempatan untuk menggunakan \"Valentine's Day Massacre\" lagi dalam sebuah "
988"judul."
989
990msgid ""
991"Although this method is not documented or supported, you can use it when "
992"your compute node is permanently offline but you have instances locally "
993"stored on it."
994msgstr ""
995"Meskipun metode ini tidak didokumentasikan atau didukung, Anda dapat "
996"menggunakannya saat node komputasi Anda offline secara permanen tetapi Anda "
997"memiliki instance yang disimpan secara lokal di dalamnya."
998
999msgid "Among the log statements you'll see the lines:"
1000msgstr "Di antara pernyataan log Anda akan melihat baris:"
1001
1002msgid ""
1003"An OpenStack cloud does not have much value without users. This chapter "
1004"covers topics that relate to managing users, projects, and quotas. This "
1005"chapter describes users and projects as described by version 2 of the "
1006"OpenStack Identity API."
1007msgstr ""
1008"Cloud OpenStack tidak memiliki banyak nilai tanpa pengguna. Bab ini mencakup "
1009"topik yang berhubungan dengan mengelola pengguna, proyek, dan kuota. Bab ini "
1010"menjelaskan pengguna dan proyek sebagaimana dijelaskan oleh versi 2 dari "
1011"OpenStack Identity API."
1012
1013msgid ""
1014"An advanced use of this general concept allows different flavor types to run "
1015"with different CPU and RAM allocation ratios so that high-intensity "
1016"computing loads and low-intensity development and testing systems can share "
1017"the same cloud without either starving the high-use systems or wasting "
1018"resources on low-utilization systems. This works by setting ``metadata`` in "
1019"your host aggregates and matching ``extra_specs`` in your flavor types."
1020msgstr ""
1021"Penggunaan lanjutan dari konsep umum ini memungkinkan jenis flavor berbeda "
1022"untuk dijalankan dengan rasio alokasi CPU dan RAM yang berbeda sehingga "
1023"beban komputasi intensitas tinggi dan pengembangan dan sistem pengujian "
1024"intensitas rendah dapat berbagi cloud yang sama tanpa penurunan (starving) "
1025"sistem penggunaan tinggi ataupun pemborosan. sumber daya pada sistem "
1026"pemanfaatan rendah. Ini bekerja dengan mengatur ``metadata`` di agregat host "
1027"Anda dan mencocokkan ``extra_specs`` dalam jenis flavor Anda."
1028
1029msgid ""
1030"An alternative to enabling the RabbitMQ web management interface is to use "
1031"the ``rabbitmqctl`` commands. For example, :command:`rabbitmqctl "
1032"list_queues| grep cinder` displays any messages left in the queue. If there "
1033"are messages, it's a possible sign that cinder services didn't connect "
1034"properly to rabbitmq and might have to be restarted."
1035msgstr ""
1036"Alternatif untuk mengaktifkan antarmuka manajemen web RabbitMQ adalah dengan "
1037"menggunakan perintah ``rabbitmqctl``. Sebagai contoh, :command:`rabbitmqctl "
1038"list_queues| grep cinder` menampilkan pesan apa pun yang tersisa di antrian. "
1039"Jika ada pesan, itu kemungkinan pertanda bahwa layanan cinder tidak "
1040"terhubung dengan benar ke rabbitmq dan mungkin harus dimulai ulang."
1041
1042msgid ""
1043"An attempt was made to deprecate ``nova-network`` during the Havana release, "
1044"which was aborted due to the lack of equivalent functionality (such as the "
1045"FlatDHCP multi-host high-availability mode mentioned in this guide), lack of "
1046"a migration path between versions, insufficient testing, and simplicity when "
1047"used for the more straightforward use cases ``nova-network`` traditionally "
1048"supported. Though significant effort has been made to address these "
1049"concerns, ``nova-network`` was not be deprecated in the Juno release. In "
1050"addition, to a limited degree, patches to ``nova-network`` have again begin "
1051"to be accepted, such as adding a per-network settings feature and SR-IOV "
1052"support in Juno."
1053msgstr ""
1054"Upaya telah dilakukan untuk menurunkan (deprecate) ``nova-network`` selama "
1055"rilis Havana, yang dibatalkan karena kurangnya fungsi yang setara (seperti "
1056"mode FlatDHCP multi-host high-availability yang disebutkan dalam panduan "
1057"ini), kurangnya migrasi jalur antara versi, pengujian yang tidak mencukupi, "
1058"dan kesederhanaan saat digunakan untuk kasus penggunaan yang lebih mudah "
1059"``nova-network`` yang didukung secara tradisional. Meskipun upaya signifikan "
1060"telah dilakukan untuk mengatasi masalah ini, ``nova-network`` tidak "
1061"ditinggalkan dalam rilis Juno. Selain itu, untuk tingkat yang terbatas, "
1062"patch ke ``nova-network`` telah mulai diterima lagi, seperti menambahkan "
1063"fitur pengaturan per-network dan dukungan SR-IOV di Juno."
1064
1065msgid ""
1066"An automated deployment system installs and configures operating systems on "
1067"new servers, without intervention, after the absolute minimum amount of "
1068"manual work, including physical racking, MAC-to-IP assignment, and power "
1069"configuration. Typically, solutions rely on wrappers around PXE boot and "
1070"TFTP servers for the basic operating system install and then hand off to an "
1071"automated configuration management system."
1072msgstr ""
1073"Sistem penyebaran otomatis menginstal dan mengkonfigurasi sistem operasi "
1074"pada server baru, tanpa intervensi, setelah jumlah minimum absolut dari "
1075"pekerjaan manual, termasuk pemerasan fisik, penugasan MAC-ke-IP, dan "
1076"konfigurasi daya. Biasanya, solusi mengandalkan pembungkus (wrapper) di "
1077"sekitar boot PXE dan server TFTP untuk instalasi sistem operasi dasar dan "
1078"kemudian diserahkan ke sistem manajemen konfigurasi otomatis."
1079
1080msgid "An external server outside of the cloud"
1081msgstr "Server eksternal di luar cloud"
1082
1083msgid ""
1084"An hour later I received the same alert, but for another compute node. Crap. "
1085"OK, now there's definitely a problem going on. Just like the original node, "
1086"I was able to log in by SSH. The bond0 NIC was DOWN but the 1gb NIC was "
1087"active."
1088msgstr ""
1089"Satu jam kemudian saya menerima peringatan yang sama, tetapi untuk node "
1090"komputasi lain. Crap. OK, sekarang pasti ada masalah yang terjadi. Sama "
1091"seperti node asli, saya bisa masuk oleh SSH. Bond0 NIC BAWAH tetapi 1gb NIC "
1092"aktif."
1093
1094msgid ""
1095"An initial idea was to just increase the lease time. If the instance only "
1096"renewed once every week, the chances of this problem happening would be "
1097"tremendously smaller than every minute. This didn't solve the problem, "
1098"though. It was just covering the problem up."
1099msgstr ""
1100"Gagasan awal adalah hanya menambah waktu sewa. Jika instance hanya "
1101"diperbarui sekali setiap minggu, peluang terjadinya masalah ini akan jauh "
1102"lebih kecil daripada setiap menit. Tapi ini tidak menyelesaikan masalah. Itu "
1103"hanya menutupi masalah."
1104
1105msgid "An instance running on that compute node"
1106msgstr "Sebuah instance berjalan pada node komputasi itu"
1107
1108msgid ""
1109"An integral part of a configuration-management system is the item that it "
1110"controls. You should carefully consider all of the items that you want, or "
1111"do not want, to be automatically managed. For example, you may not want to "
1112"automatically format hard drives with user data."
1113msgstr ""
1114"Bagian integral dari sistem manajemen konfigurasi adalah item yang "
1115"dikontrolnya. Anda harus hati-hati mempertimbangkan semua item yang Anda "
1116"inginkan, atau tidak ingin, dikelola secara otomatis. Misalnya, Anda mungkin "
1117"tidak ingin memformat hard drive dengan data pengguna secara otomatis."
1118
1119msgid ""
1120"An upgrade pre-testing system is excellent for getting the configuration to "
1121"work. However, it is important to note that the historical use of the system "
1122"and differences in user interaction can affect the success of upgrades."
1123msgstr ""
1124"Sistem pra-testing upgrade sangat baik untuk membuat konfigurasi berfungsi. "
1125"Namun, penting untuk dicatat bahwa penggunaan historis sistem dan perbedaan "
1126"dalam interaksi pengguna dapat mempengaruhi keberhasilan upgrade."
1127
1128msgid "And finally, you can disassociate the floating IP:"
1129msgstr "Dan akhirnya, Anda dapat melepaskan IP mengambang:"
1130
1131msgid ""
1132"And the best part: the same user had just tried creating a CentOS instance. "
1133"What?"
1134msgstr ""
1135"Dan bagian terbaiknya: pengguna yang sama baru saja mencoba membuat instance "
1136"CentOS. Apa?"
1137
1138msgid ""
1139"Another common concept across various OpenStack projects is that of periodic "
1140"tasks. Periodic tasks are much like cron jobs on traditional Unix systems, "
1141"but they are run inside an OpenStack process. For example, when OpenStack "
1142"Compute (nova) needs to work out what images it can remove from its local "
1143"cache, it runs a periodic task to do this."
1144msgstr ""
1145"Konsep umum lainnya di berbagai proyek OpenStack adalah tugas berkala. Tugas "
1146"berkala mirip dengan pekerjaan cron pada sistem Unix tradisional, tetapi "
1147"dijalankan di dalam proses OpenStack. Sebagai contoh, ketika OpenStack "
1148"Compute (nova) perlu mencari image apa yang dapat dihapus dari cache lokal, "
1149"itu menjalankan tugas berkala untuk melakukan ini."
1150
1151msgid ""
1152"Any time an instance shuts down unexpectedly, it might have problems on "
1153"boot. For example, the instance might require an ``fsck`` on the root "
1154"partition. If this happens, the user can use the dashboard VNC console to "
1155"fix this."
1156msgstr ""
1157"Setiap kali sebuah instance dimatikan secara tak terduga, mungkin ada "
1158"masalah saat boot. Sebagai contoh, instance mungkin memerlukan ``fsck`` di "
1159"partisi root. Jika ini terjadi, pengguna dapat menggunakan konsol VNC dasbor "
1160"untuk memperbaikinya."
1161
1162msgid "Appendix"
1163msgstr "Lampiran"
1164
1165msgid ""
1166"Armed with a patched qemu and a way to reproduce, we set out to see if we've "
1167"finally solved The Issue. After 48 hours straight of hammering the instance "
1168"with bandwidth, we were confident. The rest is history. You can search the "
1169"bug report for \"joe\" to find my comments and actual tests."
1170msgstr ""
1171"Dipersenjatai dengan qemu yang di-patch dan cara untuk mereproduksi, kami "
1172"berangkat untuk melihat apakah kami akhirnya telah menyelesaikan The Issue. "
1173"Setelah 48 jam terus-menerus memukul instance dengan bandwidth, kami yakin. "
1174"Sisanya (the rest) adalah sejarah. Anda dapat mencari \"bug\" laporan bug "
1175"untuk menemukan komentar saya dan tes yang sebenarnya."
1176
1177msgid ""
1178"Artificial scale testing can go only so far. After your cloud is upgraded, "
1179"you must pay careful attention to the performance aspects of your cloud."
1180msgstr ""
1181"Pengujian skala buatan hanya bisa sejauh ini. Setelah cloud Anda "
1182"ditingkatkan (upgraded), Anda harus memperhatikan aspek kinerja cloud Anda."
1183
1184msgid ""
1185"As a cloud administrative user, you can use the OpenStack dashboard to "
1186"create and manage projects, users, images, and flavors. Users are allowed to "
1187"create and manage images within specified projects and to share images, "
1188"depending on the Image service configuration. Typically, the policy "
1189"configuration allows admin users only to set quotas and create and manage "
1190"services. The dashboard provides an :guilabel:`Admin` tab with a :guilabel:"
1191"`System Panel` and an :guilabel:`Identity` tab. These interfaces give you "
1192"access to system information and usage as well as to settings for "
1193"configuring what end users can do. Refer to the `Horizon Administration "
1194"Guide <https://docs.openstack.org/horizon/latest/admin/>`_ for detailed how-"
1195"to information about using the dashboard as an admin user."
1196msgstr ""
1197"Sebagai pengguna cloud administrasi, Anda dapat menggunakan dasbor OpenStack "
1198"untuk membuat dan mengelola proyek, pengguna, image, dan flavor. Pengguna "
1199"diizinkan untuk membuat dan mengelola image dalam proyek yang ditentukan dan "
1200"untuk berbagi image, tergantung pada konfigurasi layanan Image. Biasanya, "
1201"konfigurasi kebijakan hanya mengizinkan pengguna admin untuk menetapkan "
1202"kuota dan membuat serta mengelola layanan. Dasbor menyediakan tab :guilabel: "
1203"`Admin` dengan :guilabel:` System Panel` dan sebuah tab :guilabel: "
1204"`Identity`. Antarmuka ini memberi Anda akses ke informasi dan penggunaan "
1205"sistem serta pengaturan untuk mengonfigurasi apa yang dapat dilakukan end "
1206"user. Mengacu kepada `Horizon Administration Guide <https://docs.openstack."
1207"org/horizon/latest/admin/>`_ untuk informasi rinci tentang cara menggunakan "
1208"dasbor sebagai pengguna admin."
1209
1210msgid ""
1211"As a last resort, our network admin (Alvaro) and myself sat down with four "
1212"terminal windows, a pencil, and a piece of paper. In one window, we ran "
1213"ping. In the second window, we ran ``tcpdump`` on the cloud controller. In "
1214"the third, ``tcpdump`` on the compute node. And the forth had ``tcpdump`` on "
1215"the instance. For background, this cloud was a multi-node, non-multi-host "
1216"setup."
1217msgstr ""
1218"Sebagai upaya terakhir, admin jaringan kami (Alvaro) dan saya sendiri duduk "
1219"dengan empat windows terminal, pensil, dan selembar kertas. Di satu jendela, "
1220"kami menjalankan ping. Di windows kedua, kami menjalankan ``tcpdump`` pada "
1221"pengontrol cloud. Pada yang ketiga, ``tcpdump`` pada compute node. Dan "
1222"keempat memiliki ``tcpdump`` pada instance. Sebagai latar belakang, cloud "
1223"ini merupakan pengaturan multi-node, non-multi-host."
1224
1225msgid ""
1226"As a specific example, compare a cloud that supports a managed web-hosting "
1227"platform with one running integration tests for a development project that "
1228"creates one VM per code commit. In the former, the heavy work of creating a "
1229"VM happens only every few months, whereas the latter puts constant heavy "
1230"load on the cloud controller. You must consider your average VM lifetime, as "
1231"a larger number generally means less load on the cloud controller."
1232msgstr ""
1233"Sebagai contoh spesifik, bandingkan cloud yang mendukung platform hosting "
1234"web yang dikelola dengan satu yang menjalankan tes integrasi untuk proyek "
1235"pengembangan yang membuat satu VM per komit kode. Dalam yang pertama, "
1236"pekerjaan berat menciptakan VM terjadi hanya setiap beberapa bulan, "
1237"sedangkan yang terakhir menempatkan beban berat konstan pada pengendali "
1238"cloud. Anda harus mempertimbangkan masa pakai VM rata-rata, karena jumlah "
1239"yang lebih besar umumnya berarti lebih sedikit beban pada pengontrol cloud."
1240
1241msgid ""
1242"As an OpenStack cloud is composed of so many different services, there are a "
1243"large number of log files. This chapter aims to assist you in locating and "
1244"working with them and describes other ways to track the status of your "
1245"deployment."
1246msgstr ""
1247"Karena cloud OpenStack terdiri dari begitu banyak layanan yang berbeda, ada "
1248"banyak file log. Bab ini bertujuan untuk membantu Anda menemukan dan bekerja "
1249"dengan mereka dan menjelaskan cara-cara lain untuk melacak status penempatan "
1250"Anda."
1251
1252msgid ""
1253"As an administrative user, you can update the Block Storage service quotas "
1254"for a tenant, as well as update the quota defaults for a new tenant. See :"
1255"ref:`table_block_storage_quota`."
1256msgstr ""
1257"Sebagai pengguna administratif, Anda dapat memperbarui kuota layanan Block "
1258"Storage untuk tenant, serta memperbarui kuota default untuk tenant baru. "
1259"Lihat :ref:`table_block_storage_quota`."
1260
1261msgid ""
1262"As an administrative user, you can update the Compute service quotas for an "
1263"existing tenant, as well as update the quota defaults for a new tenant. See :"
1264"ref:`table_compute_quota`."
1265msgstr ""
1266"Sebagai pengguna administratif, Anda dapat memperbarui kuota layanan Compute "
1267"untuk penyewa yang ada, serta memperbarui kuota default untuk penyewa baru. "
1268"Lihat :ref:`table_compute_quota`."
1269
1270msgid ""
1271"As an administrative user, you can use the :command:`cinder quota-*` "
1272"commands, which are provided by the ``python-cinderclient`` package, to view "
1273"and update tenant quotas."
1274msgstr ""
1275"Sebagai pengguna administratif, Anda dapat menggunakan perintah :command:"
1276"`cinder quota-*`, yang disediakan oleh paket ``python-cinderclient``, untuk "
1277"melihat dan memperbarui kuota tenant."
1278
1279msgid ""
1280"As an administrator, you have a few ways to discover what your OpenStack "
1281"cloud looks like simply by using the OpenStack tools available. This section "
1282"gives you an idea of how to get an overview of your cloud, its shape, size, "
1283"and current state."
1284msgstr ""
1285"Sebagai administrator, Anda memiliki beberapa cara untuk menemukan seperti "
1286"apa cloud OpenStack Anda hanya dengan menggunakan alat OpenStack yang "
1287"tersedia. Bagian ini memberi Anda gambaran tentang cara mendapatkan ikhtisar "
1288"cloud, bentuk, ukuran, dan kondisi saat ini."
1289
1290msgid ""
1291"As an example, recording ``nova-api`` usage can allow you to track the need "
1292"to scale your cloud controller. By keeping an eye on ``nova-api`` requests, "
1293"you can determine whether you need to spawn more ``nova-api`` processes or "
1294"go as far as introducing an entirely new server to run ``nova-api``. To get "
1295"an approximate count of the requests, look for standard INFO messages in ``/"
1296"var/log/nova/nova-api.log``:"
1297msgstr ""
1298"Sebagai contoh, merekam penggunaan ``nova-api`` dapat memungkinkan Anda "
1299"untuk melacak kebutuhan untuk meningkatkan skala pengontrol cloud Anda. "
1300"Dengan mengawasi permintaan ``nova-api``, Anda dapat menentukan apakah Anda "
1301"perlu menelurkan (spawn) lebih banyak proses ``nova-api`` atau sejauh "
1302"memperkenalkan server yang sama sekali baru untuk menjalankan ``nova-api`` . "
1303"Untuk mendapatkan perkiraan jumlah permintaan, cari pesan INFO standar di ``/"
1304"var/log/nova/nova-api.log``:"
1305
1306msgid ""
1307"As for your initial deployment, you should ensure that all hardware is "
1308"appropriately burned in before adding it to production. Run software that "
1309"uses the hardware to its limits—maxing out RAM, CPU, disk, and network. Many "
1310"options are available, and normally double as benchmark software, so you "
1311"also get a good idea of the performance of your system."
1312msgstr ""
1313"Apapun penyebaran awal Anda, Anda harus memastikan bahwa semua perangkat "
1314"keras dibakar (burned) secara tepat sebelum menambahkannya ke produksi. "
1315"Jalankan perangkat lunak yang menggunakan perangkat keras hingga batasnya — "
1316"memaksimalkan RAM, CPU, disk, dan jaringan. Banyak pilihan yang tersedia, "
1317"dan biasanya berfungsi ganda sebagai perangkat lunak benchmark, jadi Anda "
1318"juga mendapatkan ide bagus tentang kinerja sistem Anda."
1319
1320msgid ""
1321"As mentioned, there's currently no way to cleanly migrate from ``nova-"
1322"network`` to neutron. We recommend that you keep a migration in mind and "
1323"what that process might involve for when a proper migration path is released."
1324msgstr ""
1325"Seperti yang disebutkan, saat ini tidak ada cara untuk bermigrasi secara "
1326"bersih dari ``nova-network`` ke neutron. Kami menyarankan Anda mengingat "
1327"migrasi dan apa proses yang mungkin terlibat ketika jalur migrasi yang tepat "
1328"dirilis."
1329
1330msgid "As soon as this setting was fixed, everything worked."
1331msgstr "Segera setelah pengaturan ini diperbaiki, semuanya bekerja."
1332
1333msgid "As this would be the server's bonded NIC."
1334msgstr "Karena ini akan menjadi NIC yang terikat pada server."
1335
1336msgid ""
1337"As with most architecture choices, the right answer depends on your "
1338"environment. If you are using existing hardware, you know the disk density "
1339"of your servers and can determine some decisions based on the options above. "
1340"If you are going through a procurement process, your user's requirements "
1341"also help you determine hardware purchases. Here are some examples from a "
1342"private cloud providing web developers custom environments at AT&T. This "
1343"example is from a specific deployment, so your existing hardware or "
1344"procurement opportunity may vary from this. AT&T uses three types of "
1345"hardware in its deployment:"
1346msgstr ""
1347"As with most architecture choices, the right answer depends on your "
1348"environment. If you are using existing hardware, you know the disk density "
1349"of your servers and can determine some decisions based on the options above. "
1350"If you are going through a procurement process, your user's requirements "
1351"also help you determine hardware purchases. Here are some examples from a "
1352"private cloud providing web developers custom environments at AT&T. This "
1353"example is from a specific deployment, so your existing hardware or "
1354"procurement opportunity may vary from this. AT&T uses three types of "
1355"hardware in its deployment:"
1356
1357msgid ""
1358"As your cloud grows, MySQL is utilized more and more. If you suspect that "
1359"MySQL might be becoming a bottleneck, you should start researching MySQL "
1360"optimization. The MySQL manual has an entire section dedicated to this "
1361"topic: `Optimization Overview <https://dev.mysql.com/doc/refman/5.5/en/"
1362"optimize-overview.html>`_."
1363msgstr ""
1364"Seiring cloud Anda tumbuh, MySQL semakin banyak digunakan. Jika Anda "
1365"mencurigai bahwa MySQL mungkin menjadi hambatan, Anda harus mulai meneliti "
1366"optimasi MySQL. Manual MySQL memiliki seluruh bagian yang didedikasikan "
1367"untuk topik ini: `Optimization Overview <https://dev.mysql.com/doc/"
1368"refman/5.5/en/optimize-overview.html>`_."
1369
1370msgid ""
1371"As your focus turns to stable operations, we recommend that you do skim this "
1372"guide to get a sense of the content. Some of this content is useful to read "
1373"in advance so that you can put best practices into effect to simplify your "
1374"life in the long run. Other content is more useful as a reference that you "
1375"might turn to when an unexpected event occurs (such as a power failure), or "
1376"to troubleshoot a particular problem."
1377msgstr ""
1378"Saat fokus Anda beralih ke operasi yang stabil, kami sarankan Anda membaca "
1379"panduan ini untuk memahami kontennya. Beberapa konten ini bermanfaat untuk "
1380"dibaca terlebih dahulu sehingga Anda dapat menerapkan praktik terbaik untuk "
1381"menyederhanakan hidup Anda dalam jangka panjang. Konten lain lebih "
1382"bermanfaat sebagai referensi yang dapat Anda gunakan ketika terjadi "
1383"peristiwa tak terduga (seperti listrik mati), atau memecahkan masalah "
1384"tertentu."
1385
1386msgid ""
1387"Aside from connection failures, RabbitMQ log files are generally not useful "
1388"for debugging OpenStack related issues. Instead, we recommend you use the "
1389"RabbitMQ web management interface. Enable it on your cloud controller:"
1390msgstr ""
1391"Selain dari kegagalan koneksi, file log RabbitMQ umumnya tidak berguna untuk "
1392"debugging masalah terkait OpenStack. Sebagai gantinya, kami sarankan Anda "
1393"menggunakan antarmuka manajemen web RabbitMQ. Aktifkan di pengontrol cloud "
1394"Anda:"
1395
1396msgid ""
1397"Aside from the creation and termination of VMs, you must consider the impact "
1398"of users accessing the service particularly on ``nova-api`` and its "
1399"associated database. Listing instances garners a great deal of information "
1400"and, given the frequency with which users run this operation, a cloud with a "
1401"large number of users can increase the load significantly. This can occur "
1402"even without their knowledge. For example, leaving the OpenStack dashboard "
1403"instances tab open in the browser refreshes the list of VMs every 30 seconds."
1404msgstr ""
1405"Selain pembuatan dan penghentian VM, Anda harus mempertimbangkan dampak dari "
1406"pengguna yang mengakses layanan khususnya pada ``nova-api`` dan database "
1407"terkaitnya. Mendaftar instance mengumpulkan banyak informasi dan, mengingat "
1408"frekuensi pengguna menjalankan operasi ini, cloud dengan sejumlah besar "
1409"pengguna dapat meningkatkan beban secara signifikan. Ini dapat terjadi "
1410"bahkan tanpa sepengetahuan mereka. Misalnya, membiarkan tab instance dasbor "
1411"OpenStack terbuka di browser menyegarkan daftar VM setiap 30 detik."
1412
1413msgid ""
1414"Aside from the direct-to-blueprint pathway, there is another very well-"
1415"regarded mechanism to influence the development roadmap: the user survey. "
1416"Found at `OpenStack User Survey <https://www.openstack.org/user-survey/>`_, "
1417"it allows you to provide details of your deployments and needs, anonymously "
1418"by default. Each cycle, the user committee analyzes the results and produces "
1419"a report, including providing specific information to the technical "
1420"committee and project team leads."
1421msgstr ""
1422"Selain dari jalur direct-to-blueprint, ada mekanisme lain yang sangat "
1423"dipertimbangkan untuk memengaruhi roadmap pengembangan: survei pengguna. "
1424"Ditemukan di `OpenStack User Survey <https://www.openstack.org/user-survey/"
1425">` _, ini memungkinkan Anda untuk memberikan rincian penyebaran dan "
1426"kebutuhan Anda, secara anonim secara default. Setiap siklus, komite pengguna "
1427"menganalisis hasil dan menghasilkan laporan, termasuk memberikan informasi "
1428"spesifik kepada komite teknis dan pimpinan tim proyek."
1429
1430msgid "Aspects to Watch"
1431msgstr "Aspects to Watch (aspek untuk dilihat)"
1432
1433msgid "Assign a lost IPv4 address back to a project"
1434msgstr "Mengangkat alamat IPv4 yang hilang kembali ke proyek"
1435
1436msgid ""
1437"At that time, our control services were hosted by another team and we didn't "
1438"have much debugging information to determine what was going on with the "
1439"master, and we could not reboot it. That team noted that it failed without "
1440"alert, but managed to reboot it. After an hour, the cluster had returned to "
1441"its normal state and we went home for the day."
1442msgstr ""
1443"Pada saat itu, layanan kontrol kami dihosting oleh tim lain dan kami tidak "
1444"memiliki banyak informasi debug untuk menentukan apa yang terjadi dengan "
1445"master, dan kami tidak dapat mem-boot ulang. Tim itu mencatat bahwa ia gagal "
1446"tanpa peringatan, tetapi berhasil mem-boot ulangnya. Setelah satu jam, gugus "
1447"telah kembali ke keadaan normal dan kami pulang untuk hari itu."
1448
1449msgid ""
1450"At the data center, I was finishing up some tasks and remembered the lock-"
1451"up. I logged into the new instance and ran :command:`ps aux` again. It "
1452"worked. Phew. I decided to run it one more time. It locked up."
1453msgstr ""
1454"Di pusat data, saya menyelesaikan beberapa tugas dan mengingat "
1455"pengunciannya. Saya masuk ke instance baru dan menjalankan: command: `ps "
1456"aux` lagi. Itu berhasil. Fiuh. Saya memutuskan untuk menjalankannya sekali "
1457"lagi. Terkunci."
1458
1459msgid ""
1460"At the end of 2012, Cybera (a nonprofit with a mandate to oversee the "
1461"development of cyberinfrastructure in Alberta, Canada) deployed an updated "
1462"OpenStack cloud for their `DAIR project <https://www.canarie.ca/cloud/>`_. A "
1463"few days into production, a compute node locks up. Upon rebooting the node, "
1464"I checked to see what instances were hosted on that node so I could boot "
1465"them on behalf of the customer. Luckily, only one instance."
1466msgstr ""
1467"Pada akhir 2012, Cybera (sebuah organisasi nirlaba dengan mandat untuk "
1468"mengawasi pengembangan infrastruktur cyber di Alberta, Kanada) mengerahkan "
1469"OpenStack cloud yang diperbarui untuk proyek mereka `DAIR project <https://"
1470"www.canarie.ca/cloud/>` _ . Beberapa hari setelah produksi, sebuah node "
1471"komputasi terkunci. Setelah me-reboot node, saya memeriksa untuk melihat "
1472"instance apa yang di-host pada node itu sehingga saya bisa mem-bootnya atas "
1473"nama pelanggan. Untungnya, hanya satu instance."
1474
1475msgid ""
1476"At the end of August 2012, a post-secondary school in Alberta, Canada "
1477"migrated its infrastructure to an OpenStack cloud. As luck would have it, "
1478"within the first day or two of it running, one of their servers just "
1479"disappeared from the network. Blip. Gone."
1480msgstr ""
1481"Pada akhir Agustus 2012, sebuah sekolah pasca sekolah menengah di Alberta, "
1482"Kanada memigrasikan infrastrukturnya ke cloud OpenStack. Seperti "
1483"keberuntungan, dalam hari pertama atau kedua berjalan, salah satu server "
1484"mereka hilang dari jaringan. Blip. Hilang."
1485
1486msgid ""
1487"At the same time of finding the bug report, a co-worker was able to "
1488"successfully reproduce The Issue! How? He used ``iperf`` to spew a ton of "
1489"bandwidth at an instance. Within 30 minutes, the instance just disappeared "
1490"from the network."
1491msgstr ""
1492"Pada saat yang sama menemukan laporan bug, rekan kerja berhasil mereproduksi "
1493"The Issue! How? Dia menggunakan ``iperf`` untuk memuntahkan satu ton "
1494"bandwidth pada sebuah instance. Dalam 30 menit, instance baru saja "
1495"menghilang dari jaringan."
1496
1497msgid ""
1498"At the time of writing, OpenStack has more than 3,000 configuration options. "
1499"You can see them documented at the `OpenStack Configuration Reference "
1500"<https://docs.openstack.org/ocata/config-reference/config-overview.html>`_. "
1501"This chapter cannot hope to document all of these, but we do try to "
1502"introduce the important concepts so that you know where to go digging for "
1503"more information."
1504msgstr ""
1505"Pada saat penulisan, OpenStack memiliki lebih dari 3.000 opsi konfigurasi. "
1506"Anda dapat melihatnya didokumentasikan di `OpenStack Configuration Reference "
1507"<https://docs.openstack.org/ocata/config-reference/config-overview.html>`_. "
1508"Bab ini tidak dapat berharap untuk mendokumentasikan semua ini, tetapi kami "
1509"mencoba memperkenalkan konsep-konsep penting sehingga Anda tahu ke mana "
1510"harus mencari informasi lebih lanjut."
1511
1512msgid ""
1513"At the very base of any operating system are the hard drives on which the "
1514"operating system (OS) is installed."
1515msgstr ""
1516"Di bagian paling dasar dari setiap sistem operasi adalah hard drive tempat "
1517"sistem operasi (OS) diinstal."
1518
1519msgid ""
1520"Attack vectors increase further in a public facing OpenStack deployment. For "
1521"example, the API endpoints and the software behind it become vulnerable to "
1522"hostile entities attempting to gain unauthorized access or prevent access to "
1523"services. You should provide appropriate filtering and periodic security "
1524"auditing."
1525msgstr ""
1526"Vektor serangan meningkat lebih lanjut di publik yang menghadapi penyebaran "
1527"OpenStack. Misalnya, endpoint API dan perangkat lunak di belakangnya menjadi "
1528"rentan terhadap entitas yang bermusuhan yang berusaha mendapatkan akses "
1529"tidak sah atau mencegah akses ke layanan. Anda harus memberikan penyaringan "
1530"yang sesuai dan audit keamanan berkala."
1531
1532msgid "Attempt to boot a nova instance in the affected environment."
1533msgstr "Mencoba mem-boot instance nova di lingkungan yang terpengaruh."
1534
1535msgid "Attempt to list the objects in the ``middleware-test`` container:"
1536msgstr ""
1537"Cobalah untuk membuat daftar objek dalam kontainer ``middleware-test``:"
1538
1539msgid "Automated configuration"
1540msgstr "Konfigurasi otomatis"
1541
1542msgid "Automated deployment"
1543msgstr "Penyebaran otomatis"
1544
1545msgid "Availability zone"
1546msgstr "Zona ketersediaan"
1547
1548msgid "Availability zones"
1549msgstr "Availability zones"
1550
1551msgid "Availability zones and host aggregates"
1552msgstr "Zona ketersediaan dan agregat host"
1553
1554msgid "Available vCPUs"
1555msgstr "Available vCPUs"
1556
1557msgid ""
1558"Back in your DevStack instance on the shell screen, add some metadata to "
1559"your container to allow the request from the remote machine:"
1560msgstr ""
1561"Kembali ke instance DevStack Anda pada layar shell, tambahkan beberapa "
1562"metadata ke kontainer Anda untuk memungkinkan permintaan dari mesin jarak "
1563"jauh:"
1564
1565msgid ""
1566"Back up HOT template ``yaml`` files, and the ``/etc/heat/`` directory "
1567"containing Orchestration configuration files."
1568msgstr ""
1569"Buat cadangan file templat HOT ``yaml``, dan direktori ``/etc/heat/`` yang "
1570"berisi file konfigurasi Orchestration."
1571
1572msgid ""
1573"Back up the ``/etc/ceilometer`` directory containing Telemetry configuration "
1574"files."
1575msgstr ""
1576"Cadangkan direktori ``/etc/ceilometer`` yang berisi file konfigurasi "
1577"Telemetry."
1578
1579msgid "Backing storage services"
1580msgstr "Mendukung layanan penyimpanan"
1581
1582msgid "Backup and Recovery"
1583msgstr "Cadangan dan Pemulihan"
1584
1585msgid ""
1586"Backup and subsequent recovery is one of the first tasks system "
1587"administrators learn. However, each system has different items that need "
1588"attention. By taking care of your database, image service, and appropriate "
1589"file system locations, you can be assured that you can handle any event "
1590"requiring recovery."
1591msgstr ""
1592"Pencadangan dan pemulihan selanjutnya adalah salah satu tugas pertama yang "
1593"dipelajari oleh administrator sistem. Namun, setiap sistem memiliki item "
1594"berbeda yang perlu diperhatikan. Dengan menjaga basis data, layanan gambar, "
1595"dan lokasi sistem file yang sesuai, Anda dapat yakin bahwa Anda dapat "
1596"menangani segala peristiwa yang membutuhkan pemulihan."
1597
1598msgid "Bare metal Deployment (ironic)"
1599msgstr "Penggunaan bare-metal (ironic)"
1600
1601msgid "Baremetal security"
1602msgstr "Keamanan baremetal"
1603
1604msgid ""
1605"Be mindful of consistency when utilizing third party clouds to explore "
1606"authentication options."
1607msgstr ""
1608"Berhati-hatilah terhadap konsistensi saat menggunakan cloud pihak ketiga "
1609"untuk menjelajahi opsi otentikasi."
1610
1611msgid ""
1612"Be sure that the instance has successfully booted and is at a login screen "
1613"before doing the above."
1614msgstr ""
1615"Pastikan instance telah berhasil di-boot dan berada di layar login sebelum "
1616"melakukan hal di atas."
1617
1618msgid ""
1619"Because it is recommended to not use partitions on a swift disk, simply "
1620"format the disk as a whole:"
1621msgstr ""
1622"Karena disarankan untuk tidak menggunakan partisi pada swift disk, cukup "
1623"format disk secara keseluruhan:"
1624
1625msgid ""
1626"Because of the high redundancy of Object Storage, dealing with object "
1627"storage node issues is a lot easier than dealing with compute node issues."
1628msgstr ""
1629"Karena redundansi yang tinggi dari Object Storage, berurusan dengan masalah "
1630"node penyimpanan objek jauh lebih mudah daripada berurusan dengan masalah "
1631"node komputasi."
1632
1633msgid ""
1634"Because without sensible quotas a single tenant could use up all the "
1635"available resources, default quotas are shipped with OpenStack. You should "
1636"pay attention to which quota settings make sense for your hardware "
1637"capabilities."
1638msgstr ""
1639"Karena tanpa kuota yang masuk akal penyewa tunggal dapat menggunakan semua "
1640"sumber daya yang tersedia, kuota default dikirimkan dengan OpenStack. Anda "
1641"harus memperhatikan pengaturan kuota yang masuk akal untuk kemampuan "
1642"perangkat keras Anda."
1643
1644msgid ""
1645"Because your cloud is most likely composed of many servers, you must check "
1646"logs on each of those servers to properly piece an event together. A better "
1647"solution is to send the logs of all servers to a central location so that "
1648"they can all be accessed from the same area."
1649msgstr ""
1650"Karena cloud Anda kemungkinan besar terdiri dari banyak server, Anda harus "
1651"memeriksa log pada masing-masing server untuk menyatukan acara dengan benar. "
1652"Solusi yang lebih baik adalah dengan mengirim log dari semua server ke "
1653"lokasi pusat sehingga semuanya dapat diakses dari area yang sama."
1654
1655msgid ""
1656"Betsy Hagemeier, a Fanatical Executive Assistant, took care of a room "
1657"reshuffle and helped us settle in for the week."
1658msgstr ""
1659"Betsy Hagemeier, Asisten Eksekutif Fanatik, mengurus perombakan kamar dan "
1660"membantu kami menetap selama seminggu."
1661
1662msgid "Block Storage"
1663msgstr "Block Storage"
1664
1665msgid "Block Storage Improvements"
1666msgstr "Peningkatan Block Storage"
1667
1668msgid ""
1669"Block Storage is considered a stable project, with wide uptake and a long "
1670"track record of quality drivers. The team has discussed many areas of work "
1671"at the summits, including better error reporting, automated discovery, and "
1672"thin provisioning features."
1673msgstr ""
1674"Block Storage dianggap sebagai proyek yang stabil, dengan serapan luas dan "
1675"rekam jejak yang panjang mengenai driver berkualitas. Tim telah membahas "
1676"banyak bidang pekerjaan di puncak, termasuk pelaporan kesalahan yang lebih "
1677"baik, penemuan otomatis, dan fitur thin provisioning."
1678
1679msgid "Block Storage nodes"
1680msgstr "Block Storage nodes"
1681
1682msgid "Block Storage service"
1683msgstr "Layanan Block Storage"
1684
1685msgid ""
1686"Block Storage service - Updating the Block Storage service only requires "
1687"restarting the service."
1688msgstr ""
1689"Layanan Block Storage - Update layanan Block Storage hanya membutuhkan "
1690"restarting layanan."
1691
1692msgid "Boot a test server:"
1693msgstr "Boot server uji:"
1694
1695msgid ""
1696"Both Compute and Block Storage rely on schedulers to determine where to "
1697"place virtual machines or volumes. In Havana, the Compute scheduler "
1698"underwent significant improvement, while in Icehouse it was the scheduler in "
1699"Block Storage that received a boost. Further down the track, an effort "
1700"started this cycle that aims to create a holistic scheduler covering both "
1701"will come to fruition. Some of the work that was done in Kilo can be found "
1702"under the `Gantt project <https://wiki.openstack.org/wiki/Gantt/kilo>`_."
1703msgstr ""
1704"Compute dan Block Storage keduanya bergantung pada penjadwal untuk "
1705"menentukan di mana menempatkan mesin atau volume virtual. Di Havana, "
1706"penjadwal Compute mengalami peningkatan yang signifikan, sedangkan di "
1707"Icehouse itu penjadwal di Block Storage yang menerima dorongan. Lebih jauh "
1708"ke bawah jalur, upaya memulai siklus ini yang bertujuan untuk membuat "
1709"penjadwal holistik yang mencakup keduanya akan membuahkan hasil. Beberapa "
1710"pekerjaan yang dilakukan di Kilo dapat ditemukan di bawah `Gantt project "
1711"<https://wiki.openstack.org/wiki/Gantt/kilo>`_."
1712
1713msgid ""
1714"Both Ubuntu and Red Hat Enterprise Linux include mechanisms for configuring "
1715"the operating system, including preseed and kickstart, that you can use "
1716"after a network boot. Typically, these are used to bootstrap an automated "
1717"configuration system. Alternatively, you can use an image-based approach for "
1718"deploying the operating system, such as systemimager. You can use both "
1719"approaches with a virtualized infrastructure, such as when you run VMs to "
1720"separate your control services and physical infrastructure."
1721msgstr ""
1722"Ubuntu dan Red Hat Enterprise Linux menyertakan mekanisme untuk "
1723"mengkonfigurasi sistem operasi, termasuk preseed dan kickstart, yang dapat "
1724"Anda gunakan setelah boot jaringan. Biasanya, ini digunakan untuk mem-"
1725"bootstrap sistem konfigurasi otomatis. Atau, Anda dapat menggunakan "
1726"pendekatan berbasis image untuk menggunakan sistem operasi, seperti "
1727"systemimager. Anda dapat menggunakan kedua pendekatan dengan infrastruktur "
1728"tervirtualisasi, seperti ketika Anda menjalankan VM untuk memisahkan layanan "
1729"kontrol dan infrastruktur fisik Anda."
1730
1731msgid "Burn-in Testing"
1732msgstr "Burn-in Testing"
1733
1734msgid ""
1735"But how can you tell whether images are being successfully uploaded to the "
1736"Image service? Maybe the disk that Image service is storing the images on is "
1737"full or the S3 back end is down. You could naturally check this by doing a "
1738"quick image upload:"
1739msgstr ""
1740"Tetapi bagaimana Anda bisa tahu apakah image berhasil diunggah ke layanan "
1741"Image? Mungkin disk tempat layanan Image menyimpan image pada penuh atau S3 "
1742"back end turun. Anda secara alami dapat memeriksanya dengan melakukan "
1743"unggahan image cepat:"
1744
1745msgid ""
1746"By comparing a tenant's hard limit with their current resource usage, you "
1747"can see their usage percentage. For example, if this tenant is using 1 "
1748"floating IP out of 10, then they are using 10 percent of their floating IP "
1749"quota. Rather than doing the calculation manually, you can use SQL or the "
1750"scripting language of your choice and create a formatted report:"
1751msgstr ""
1752"Dengan membandingkan batas keras penyewa dengan penggunaan sumber daya "
1753"mereka saat ini, Anda dapat melihat persentase penggunaannya. Misalnya, jika "
1754"penyewa ini menggunakan 1 IP mengambang dari 10, maka mereka menggunakan 10 "
1755"persen kuota IP mengambang mereka. Daripada melakukan perhitungan secara "
1756"manual, Anda dapat menggunakan SQL atau bahasa scripting pilihan Anda dan "
1757"membuat laporan yang diformat:"
1758
1759msgid "By default, Object Storage logs to syslog."
1760msgstr "Secara default, Object Storage mencatat log ke syslog."
1761
1762msgid ""
1763"By mistake, I configured OpenStack to attach all tenant VLANs to vlan20 "
1764"instead of bond0 thereby stacking one VLAN on top of another. This added an "
1765"extra 4 bytes to each packet and caused a packet of 1504 bytes to be sent "
1766"out which would cause problems when it arrived at an interface that only "
1767"accepted 1500."
1768msgstr ""
1769"Secara tidak sengaja, saya mengkonfigurasi OpenStack untuk melampirkan semua "
1770"tenant VLAN ke vlan20 dan bukannya bond0 sehingga menumpuk satu VLAN di atas "
1771"yang lain. Ini menambahkan 4 byte tambahan untuk setiap paket dan "
1772"menyebabkan paket 1504 byte dikirim yang akan menyebabkan masalah ketika "
1773"tiba di antarmuka yang hanya menerima 1500."
1774
1775msgid ""
1776"By modifying your configuration setup, you can set up IPv6 when using ``nova-"
1777"network`` for networking, and a tested setup is documented for FlatDHCP and "
1778"a multi-host configuration. The key is to make ``nova-network`` think a "
1779"``radvd`` command ran successfully. The entire configuration is detailed in "
1780"a Cybera blog post, `“An IPv6 enabled cloud” <http://www.cybera.ca/news-and-"
1781"events/tech-radar/an-ipv6-enabled-cloud/>`_."
1782msgstr ""
1783"Dengan memodifikasi pengaturan konfigurasi Anda, Anda dapat mengatur IPv6 "
1784"saat menggunakan ``nova-network`` untuk jaringan, dan pengaturan yang diuji "
1785"didokumentasikan untuk FlatDHCP dan konfigurasi multi-host. Kuncinya adalah "
1786"membuat ``nova-network`` berpikir perintah ``radvd`` berhasil dijalankan. "
1787"Seluruh konfigurasi dirinci dalam posting blog Cybera, `“An IPv6 enabled "
1788"cloud” <http://www.cybera.ca/news-and-events/tech-radar/an-ipv6-enabled-"
1789"cloud/>`_."
1790
1791msgid ""
1792"By running this command periodically and keeping a record of the result, you "
1793"can create a trending report over time that shows whether your ``nova-api`` "
1794"usage is increasing, decreasing, or keeping steady."
1795msgstr ""
1796"Dengan menjalankan perintah ini secara berkala dan menyimpan catatan "
1797"hasilnya, Anda dapat membuat laporan trending dari waktu ke waktu yang "
1798"menunjukkan apakah penggunaan ``nova-api`` Anda meningkat, menurun, atau "
1799"tetap stabil."
1800
1801msgid ""
1802"By taking this script and rolling it into an alert for your monitoring "
1803"system (such as Nagios), you now have an automated way of ensuring that "
1804"image uploads to the Image Catalog are working."
1805msgstr ""
1806"Dengan mengambil skrip ini dan mengubahnya menjadi peringatan untuk sistem "
1807"pemantauan Anda (seperti Nagios), Anda sekarang memiliki cara otomatis untuk "
1808"memastikan bahwa unggahan image ke Image Catalog berfungsi."
1809
1810msgid "CERN"
1811msgstr "CERN"
1812
1813msgid ""
1814"CONF.node_availability_zone has been renamed to CONF."
1815"default_availability_zone and is used only by the ``nova-api`` and ``nova-"
1816"scheduler`` services."
1817msgstr ""
1818"CONF.node_available_zone telah diubah namanya menjadi CONF."
1819"default_available_zone dan hanya digunakan oleh layanan ``nova-api`` dan "
1820"``nova-scheduler``."
1821
1822msgid "CONF.node_availability_zone still works but is deprecated."
1823msgstr "CONF.node_avilities_zone masih berfungsi tetapi sudah usang."
1824
1825msgid "Can instances launch and be destroyed?"
1826msgstr "Bisakah instance diluncurkan dan dihancurkan?"
1827
1828msgid "Can objects be stored and deleted?"
1829msgstr "Bisakah benda disimpan dan dihapus?"
1830
1831msgid "Can users be created?"
1832msgstr "Bisakah pengguna dibuat?"
1833
1834msgid "Can volumes be created and destroyed?"
1835msgstr "Bisakah volume dibuat dan dimusnahkan?"
1836
1837msgid "Capacity Planning"
1838msgstr "Perencanaan Kapasitas"
1839
1840msgid "Capacity planning and scaling"
1841msgstr "Perencanaan dan penskalaan kapasitas"
1842
1843msgid "Cells"
1844msgstr "Cells"
1845
1846msgid "Cells and regions"
1847msgstr "Sel dan daerah"
1848
1849msgid ""
1850"Cells and regions, which segregate an entire cloud and result in running "
1851"separate Compute deployments."
1852msgstr ""
1853"Sel dan wilayah, yang memisahkan seluruh cloud dan menghasilkan menjalankan "
1854"penyebaran Compute yang terpisah."
1855
1856msgid "Centrally Managing Logs"
1857msgstr "Mengelola Log Secara terpusat"
1858
1859msgid ""
1860"Certain locations might require local vendors to provide support and "
1861"services for each site which may vary with the licensing agreement in place."
1862msgstr ""
1863"Lokasi tertentu mungkin memerlukan vendor lokal untuk memberikan dukungan "
1864"dan layanan untuk setiap situs yang mungkin berbeda dengan perjanjian "
1865"lisensi yang berlaku."
1866
1867msgid "Change to the directory where Object Storage is installed:"
1868msgstr "Ubah ke direktori tempat Object Storage diinstal:"
1869
1870msgid "Check cloud usage:"
1871msgstr "Periksa penggunaan cloud:"
1872
1873msgid "Check for instances in a failed or weird state and investigate why."
1874msgstr "Periksa instance dalam keadaan gagal atau aneh dan selidiki mengapa."
1875
1876msgid "Check for operator accounts that should be removed."
1877msgstr "Periksa akun operator yang harus dihapus."
1878
1879msgid "Check for security patches and apply them as needed."
1880msgstr "Periksa patch keamanan dan terapkan seperlunya."
1881
1882msgid "Check for user accounts that should be removed."
1883msgstr "Periksa akun pengguna yang harus dihapus."
1884
1885msgid "Check memory consumption:"
1886msgstr "Periksa konsumsi memori:"
1887
1888msgid "Check the port connection using the netcat utility:"
1889msgstr "Periksa koneksi port menggunakan utilitas netcat:"
1890
1891msgid "Check the ports for the lost IP address and update the name:"
1892msgstr "Periksa port untuk alamat IP yang hilang dan perbarui namanya:"
1893
1894msgid "Check usage and trends over the past month."
1895msgstr "Periksa penggunaan dan tren selama sebulan terakhir."
1896
1897msgid "Check your monitoring system for alerts and act on them."
1898msgstr ""
1899"Periksa sistem pemantauan Anda untuk peringatan dan menindaklanjutinya."
1900
1901msgid "Check your ticket queue for new tickets."
1902msgstr "Periksa antrean tiket Anda untuk tiket baru."
1903
1904msgid ""
1905"Clean up after an OpenStack upgrade (any unused or new services to be aware "
1906"of?)."
1907msgstr ""
1908"Bersihkan setelah upgrade OpenStack (layanan apa pun yang tidak digunakan "
1909"atau baru untuk diperhatikan?)."
1910
1911msgid ""
1912"Clean up by clearing all mirrors on ``br-int`` and deleting the dummy "
1913"interface:"
1914msgstr ""
1915"Bersihkan dengan menghapus semua mirror di ``br-int`` dan menghapus "
1916"antarmuka dummy:"
1917
1918msgid "Click the :guilabel:`Create Project` button."
1919msgstr "Klik tombol :guilabel:`Create Project`."
1920
1921msgid "Cloud (General)"
1922msgstr "Cloud (Umum)"
1923
1924msgid "Cloud Controller and Storage Proxy Failures and Maintenance"
1925msgstr "Kegagalan Pengontrol Cloud dan Proksi Penyimpanan dan Pemeliharaan"
1926
1927msgid "Cloud controller"
1928msgstr "Cloud controller"
1929
1930msgid "Cloud controller receives the renewal request and sends a response."
1931msgstr "Pengontrol cloud menerima permintaan pembaruan dan mengirim respons."
1932
1933msgid "Cloud controller receives the second request and sends a new response."
1934msgstr ""
1935"Pengontrol cloud menerima permintaan kedua dan mengirimkan respons baru."
1936
1937msgid "Cloud security architecture"
1938msgstr "Arsitektur keamanan cloud"
1939
1940msgid ""
1941"Cloud security architecture should recognize the issues that arise with "
1942"security management, which addresses these issues with security controls. "
1943"Cloud security controls are put in place to safeguard any weaknesses in the "
1944"system, and reduce the effect of an attack."
1945msgstr ""
1946"Arsitektur keamanan cloud harus mengenali masalah yang muncul dengan "
1947"manajemen keamanan, yang mengatasi masalah ini dengan kontrol keamanan. "
1948"Kontrol keamanan cloud diterapkan untuk melindungi segala kelemahan dalam "
1949"sistem, dan mengurangi efek serangan."
1950
1951msgid ""
1952"Cloud-based applications typically request more discrete hardware "
1953"(horizontal scaling) as opposed to traditional applications, which require "
1954"larger hardware to scale (vertical scaling)."
1955msgstr ""
1956"Aplikasi berbasis cloud biasanya meminta lebih banyak perangkat keras "
1957"diskrit (penskalaan horizontal) sebagai kebalikan dari aplikasi tradisional, "
1958"yang membutuhkan perangkat keras yang lebih besar untuk skala (penskalaan "
1959"vertikal)."
1960
1961msgid "Command-Line Tools"
1962msgstr "Command-Line Tools"
1963
1964msgid "Common areas of regulation include:"
1965msgstr "Area regulasi yang umum meliputi:"
1966
1967msgid "Compute"
1968msgstr "Compute"
1969
1970msgid "Compute Node Failures and Maintenance"
1971msgstr "Compute Node Failures dan Maintenance"
1972
1973msgid "Compute nodes"
1974msgstr "Compute nodes"
1975
1976msgid ""
1977"Compute nodes can fail the same way a cloud controller can fail. A "
1978"motherboard failure or some other type of hardware failure can cause an "
1979"entire compute node to go offline. When this happens, all instances running "
1980"on that compute node will not be available. Just like with a cloud "
1981"controller failure, if your infrastructure monitoring does not detect a "
1982"failed compute node, your users will notify you because of their lost "
1983"instances."
1984msgstr ""
1985"Compute Node bisa gagal dengan cara yang sama seperti cloud controller bisa "
1986"gagal. Kegagalan motherboard atau beberapa jenis kegagalan perangkat keras "
1987"lainnya dapat menyebabkan seluruh compute Nodei offline. Ketika ini terjadi, "
1988"semua instance yang berjalan pada compute Node itu tidak akan tersedia. "
1989"Seperti halnya kegagalan pengontrol cloud, jika pemantauan infrastruktur "
1990"Anda tidak mendeteksi compute Node yang gagal, pengguna Anda akan memberi "
1991"tahu Anda karena instans mereka yang hilang."
1992
1993msgid ""
1994"Compute nodes have 24 to 48 cores, with at least 4 GB of RAM per core and "
1995"approximately 40 GB of ephemeral storage per core."
1996msgstr ""
1997"Compute nodes memiliki 24 hingga 48 core, dengan setidaknya 4 GB RAM per "
1998"core dan sekitar 40 GB penyimpanan sesaat per core."
1999
2000msgid "Compute quota descriptions"
2001msgstr "Deskripsi kuota Compute"
2002
2003msgid "Compute service - Edit the configuration file and restart the service."
2004msgstr "Layanan Compute - Edit file konfigurasi dan restart layanan."
2005
2006msgid "Compute service, including networking components."
2007msgstr "Layanan Compute, termasuk komponen jaringan."
2008
2009msgid "Conclusion"
2010msgstr "Kesimpulan"
2011
2012msgid "Configuration Management"
2013msgstr "Configuration Management (manajemen konfigurasi)"
2014
2015msgid "Configuration changes to ``nova.conf``."
2016msgstr "Konfigurasi berubah menjadi ``nova.conf``."
2017
2018msgid "Connect the qemu-nbd device to the disk."
2019msgstr "Hubungkan perangkat qemu-nbd ke disk."
2020
2021msgid "Connect the qemu-nbd device to the disk:"
2022msgstr "Hubungkan perangkat qemu-nbd ke disk:"
2023
2024msgid ""
2025"Consider adopting structure and options from the service configuration files "
2026"and merging them with existing configuration files. The `OpenStack "
2027"Configuration Reference <https://docs.openstack.org/ocata/config-reference/"
2028">`_ contains new, updated, and deprecated options for most services."
2029msgstr ""
2030"Pertimbangkan untuk mengadopsi struktur dan opsi dari file konfigurasi "
2031"layanan dan menggabungkannya dengan file konfigurasi yang ada. `OpenStack "
2032"Configuration Reference <https://docs.openstack.org/ocata/config-reference/"
2033">` _ berisi opsi baru, yang diperbarui, dan tidak digunakan lagi untuk "
2034"sebagian besar layanan."
2035
2036msgid ""
2037"Consider security implications and requirements before designing the "
2038"physical and logical network topologies. Make sure that the networks are "
2039"properly segregated and traffic flows are going to the correct destinations "
2040"without crossing through locations that are undesirable. Consider the "
2041"following factors:"
2042msgstr ""
2043"Pertimbangkan implikasi dan persyaratan keamanan sebelum merancang topologi "
2044"jaringan fisik dan logis. Pastikan bahwa jaringan dipisahkan dengan baik dan "
2045"arus lalu lintas menuju ke tujuan yang benar tanpa melintasi lokasi yang "
2046"tidak diinginkan. Pertimbangkan faktor-faktor berikut:"
2047
2048msgid ""
2049"Consider the approach to upgrading your environment. You can perform an "
2050"upgrade with operational instances, but this is a dangerous approach. You "
2051"might consider using live migration to temporarily relocate instances to "
2052"other compute nodes while performing upgrades. However, you must ensure "
2053"database consistency throughout the process; otherwise your environment "
2054"might become unstable. Also, don't forget to provide sufficient notice to "
2055"your users, including giving them plenty of time to perform their own "
2056"backups."
2057msgstr ""
2058"Pertimbangkan pendekatan untuk upgrade lingkungan Anda. Anda dapat melakukan "
2059"upgrade dengan instance operasional, tetapi ini adalah pendekatan yang "
2060"berbahaya. Anda mungkin mempertimbangkan menggunakan migrasi langsung untuk "
2061"memindahkan sementara instance ke node komputasi lain saat melakukan "
2062"upgrade. Namun, Anda harus memastikan konsistensi database selama proses "
2063"berlangsung; jika tidak, lingkungan Anda mungkin menjadi tidak stabil. Juga, "
2064"jangan lupa untuk memberikan pemberitahuan yang cukup kepada pengguna Anda, "
2065"termasuk memberi mereka banyak waktu untuk melakukan backup sendiri."
2066
2067msgid "Consider the following example:"
2068msgstr "Perhatikan contoh berikut:"
2069
2070msgid "Consider the following security implications and requirements:"
2071msgstr "Pertimbangkan implikasi dan persyaratan keamanan berikut:"
2072
2073msgid ""
2074"Consider the impact of an upgrade to users. The upgrade process interrupts "
2075"management of your environment including the dashboard. If you properly "
2076"prepare for the upgrade, existing instances, networking, and storage should "
2077"continue to operate. However, instances might experience intermittent "
2078"network interruptions."
2079msgstr ""
2080"Pertimbangkan dampak upgrade ke pengguna. Proses upgrade mengganggu "
2081"manajemen lingkungan Anda termasuk dasbor. Jika Anda mempersiapkan upgrade "
2082"dengan benar, instance yang ada, jaringan, dan penyimpanan harus terus "
2083"beroperasi. Namun, instance mungkin mengalami gangguan jaringan terputus "
2084"putus (intermittent)."
2085
2086msgid ""
2087"Consider updating your SQL server configuration as described in the "
2088"`Installation Tutorials and Guides <https://docs.openstack.org/rocky/install/"
2089">`_."
2090msgstr ""
2091"Pertimbangkan memperbarui konfigurasi server SQL Anda seperti yang "
2092"dijelaskan dalam `Installation Tutorials and Guides <https://docs.openstack."
2093"org/rocky/install/>`_."
2094
2095msgid ""
2096"Consider using a public cloud to test the scalability limits of your cloud "
2097"controller configuration. Most public clouds bill by the hour, which means "
2098"it can be inexpensive to perform even a test with many nodes."
2099msgstr ""
2100"Pertimbangkan untuk menggunakan cloud publik untuk menguji batas "
2101"skalabilitas konfigurasi pengontrol cloud Anda. Sebagian besar awan publik "
2102"menagih per jam, yang berarti tidak mahal untuk melakukan bahkan pengujian "
2103"dengan banyak node."
2104
2105msgid ""
2106"Considered experimental. A new service, nova-cells. Each cell has a full "
2107"nova installation except nova-api."
2108msgstr ""
2109"Dianggap eksperimental. Layanan baru, nova-cells. Setiap sel memiliki "
2110"instalasi nova penuh kecuali nova-api."
2111
2112msgid "Console (boot up messages) for VM instances:"
2113msgstr "Console (boot up messages) for VM instances:"
2114
2115msgid "Container quotas"
2116msgstr "Kuota kontainer"
2117
2118msgid ""
2119"Contains each floating IP address that was added to Compute. This table is "
2120"related to the ``fixed_ips`` table by way of the ``floating_ips."
2121"fixed_ip_id`` column."
2122msgstr ""
2123"Berisi setiap alamat IP mengambang (floating IP) yang ditambahkan ke "
2124"Compute. Tabel ini terkait dengan tabel ``fix_ips`` melalui kolom "
2125"``floating_ips.fixed_ip_id``."
2126
2127msgid ""
2128"Contains each possible IP address for the subnet(s) added to Compute. This "
2129"table is related to the ``instances`` table by way of the ``fixed_ips."
2130"instance_uuid`` column."
2131msgstr ""
2132"Berisi setiap kemungkinan alamat IP untuk subnet yang ditambahkan ke "
2133"Compute. Tabel ini terkait dengan tabel ``instance`` melalui kolom "
2134"``fixed_ips.instance_uuid``."
2135
2136msgid "Contents"
2137msgstr "Isi"
2138
2139msgid ""
2140"Continuing the diagnosis the next morning was kick started by another "
2141"identical failure. We quickly got the message queue running again, and tried "
2142"to work out why Rabbit was suffering from so much network traffic. Enabling "
2143"debug logging on nova-api quickly brought understanding. A ``tail -f /var/"
2144"log/nova/nova-api.log`` was scrolling by faster than we'd ever seen before. "
2145"CTRL+C on that and we could plainly see the contents of a system log spewing "
2146"failures over and over again - a system log from one of our users' instances."
2147msgstr ""
2148"Melanjutkan diagnosis keesokan paginya tendangan dimulai (kick started) oleh "
2149"kegagalan lain yang identik. Kami dengan cepat menjalankan antrean pesan "
2150"lagi, dan mencoba mencari tahu mengapa Rabbit menderita begitu banyak lalu "
2151"lintas jaringan. Mengaktifkan debug logging di nova-api dengan cepat membawa "
2152"pemahaman. ``tail -f /var/log/nova/nova-api.log`` bergulir lebih cepat dari "
2153"yang pernah kami lihat sebelumnya. CTRL+C untuk itu dan kita bisa melihat "
2154"dengan jelas isi dari kegagalan log sistem yang memuntahkan berulang-ulang - "
2155"log sistem dari salah satu instance pengguna kami."
2156
2157msgid ""
2158"Copy contents of configuration backup directories that you created during "
2159"the upgrade process back to ``/etc/<service>`` directory."
2160msgstr ""
2161"Salin konten direktori cadangan konfigurasi yang Anda buat selama proses "
2162"upgrade kembali ke ``/etc/<service>`` directory."
2163
2164msgid ""
2165"Copy the code as shown below into ``ip_whitelist.py``. The following code is "
2166"a middleware example that restricts access to a container based on IP "
2167"address as explained at the beginning of the section. Middleware passes the "
2168"request on to another application. This example uses the swift \"swob\" "
2169"library to wrap Web Server Gateway Interface (WSGI) requests and responses "
2170"into objects for swift to interact with. When you're done, save and close "
2171"the file."
2172msgstr ""
2173"Salin kode seperti yang ditunjukkan di bawah ini ke ``ip_whitelist.py``. "
2174"Kode berikut adalah contoh middleware yang membatasi akses ke sebuah "
2175"kontainer berdasarkan alamat IP seperti yang dijelaskan di awal bagian. "
2176"Middleware meneruskan permintaan ke aplikasi lain. Contoh ini menggunakan "
2177"pustaka \"swob\" swift untuk membungkus permintaan dan respons Web Server "
2178"Gateway Interface (WSGI) menjadi objek untuk berinteraksi dengan swift. "
2179"Setelah selesai, simpan dan tutup file."
2180
2181msgid "Corrective controls:"
2182msgstr "Kontrol korektif:"
2183
2184msgid ""
2185"Create a clone of your automated configuration infrastructure with changed "
2186"package repository URLs."
2187msgstr ""
2188"Buat klon dari infrastruktur konfigurasi otomatis Anda dengan URL repositori "
2189"paket yang diubah."
2190
2191msgid "Create a container called ``middleware-test``:"
2192msgstr "Buat kontainer yang disebut ``middleware-test``:"
2193
2194msgid "Create a port on the ``Public_AGILE`` network:"
2195msgstr "Buat port di jaringan `` Public_AGILE``:"
2196
2197msgid "Create a port:"
2198msgstr "Membuat port:"
2199
2200msgid "Create an OpenStack Development Environment"
2201msgstr "Buat Lingkungan Pengembangan OpenStack"
2202
2203msgid "Create and bring up a dummy interface, ``snooper0``:"
2204msgstr "Membuat dan memunculkan antarmuka dummy, ``snooper0``:"
2205
2206msgid "Create context"
2207msgstr "Buat konteks"
2208
2209msgid ""
2210"Create mirror of ``patch-tun`` to ``snooper0`` (returns UUID of mirror port):"
2211msgstr ""
2212"Buat mirror dari ``patch-tun`` ke ``snooper0`` (mengembalikan UUID port "
2213"mirror):"
2214
2215msgid "Create the ``ip_scheduler.py`` Python source code file:"
2216msgstr "Buat file kode sumber Python ``ip_scheduler.py``:"
2217
2218msgid "Create the ``ip_whitelist.py`` Python source code file:"
2219msgstr "Buat file kode sumber Python ``ip_whitelist.py``:"
2220
2221msgid "Create ways to automatically test these actions."
2222msgstr "Buat cara untuk menguji tindakan ini secara otomatis."
2223
2224msgid "Customization"
2225msgstr "Kustomisasi"
2226
2227msgid "Customizing Object Storage (Swift) Middleware"
2228msgstr "Menyesuaikan Object Storage (Swift) Middleware"
2229
2230msgid "Customizing the Dashboard (Horizon)"
2231msgstr "Menyesuaikan Dasbor (Horizon)"
2232
2233msgid "Customizing the OpenStack Compute (nova) Scheduler"
2234msgstr "Menyesuaikan OpenStack Compute (nova) Scheduler"
2235
2236msgid "DAIR"
2237msgstr "DAIR"
2238
2239msgid ""
2240"DAIR is hosted at two different data centers across Canada: one in Alberta "
2241"and the other in Quebec. It consists of a cloud controller at each location, "
2242"although, one is designated the \"master\" controller that is in charge of "
2243"central authentication and quotas. This is done through custom scripts and "
2244"light modifications to OpenStack. DAIR is currently running Havana."
2245msgstr ""
2246"DAIR di-host di dua pusat data berbeda di Kanada: satu di Alberta dan yang "
2247"lainnya di Quebec. Ini terdiri dari pengontrol cloud di setiap lokasi, "
2248"meskipun, satu ditunjuk pengontrol \"master\" yang bertanggung jawab atas "
2249"otentikasi pusat dan kuota. Ini dilakukan melalui skrip khusus dan "
2250"modifikasi ringan ke OpenStack. DAIR saat ini menjalankan Havana."
2251
2252msgid ""
2253"DHCP agents running on OpenStack networks run in namespaces similar to the "
2254"l3-agents. DHCP namespaces are named ``qdhcp-<uuid>`` and have a TAP device "
2255"on the integration bridge. Debugging of DHCP issues usually involves working "
2256"inside this network namespace."
2257msgstr ""
2258"Agen DHCP yang berjalan pada jaringan OpenStack dijalankan dalam namespace "
2259"yang mirip dengan agen l3. Namespace DHCP diberi nama ``qdhcp- <uuid> `` "
2260"dan memiliki perangkat TAP di jembatan integrasi. Debugging masalah DHCP "
2261"biasanya melibatkan bekerja di dalam namespace jaringan ini."
2262
2263msgid ""
2264"DHCP traffic uses UDP. The client sends from port 68 to port 67 on the "
2265"server. Try to boot a new instance and then systematically listen on the "
2266"NICs until you identify the one that isn't seeing the traffic. To use "
2267"``tcpdump`` to listen to ports 67 and 68 on br100, you would do:"
2268msgstr ""
2269"Lalu lintas DHCP menggunakan UDP. Klien mengirim dari port 68 ke port 67 di "
2270"server. Cobalah untuk mem-boot instance baru dan kemudian secara sistematis "
2271"mendengarkan NIC sampai Anda mengidentifikasi yang tidak melihat lalu "
2272"lintas. Untuk menggunakan ``tcpdump`` untuk mendengarkan port 67 dan 68 di "
2273"br100, Anda harus:"
2274
2275msgid "DNS service (designate)"
2276msgstr "Layanan DNS (ditunjuk)"
2277
2278msgid "Daily"
2279msgstr "Harian"
2280
2281msgid ""
2282"Dashboard - In typical environments, updating Dashboard only requires "
2283"restarting the Apache HTTP service."
2284msgstr ""
2285"Dasbor - Dalam lingkungan umum, memperbarui Dasbor hanya membutuhkan "
2286"restarting layanan HTTP Apache."
2287
2288msgid "Dashboard node"
2289msgstr "Dashboard node"
2290
2291msgid ""
2292"Data compliance policies governing certain types of information needing to "
2293"reside in certain locations due to regulatory issues - and more importantly, "
2294"cannot reside in other locations for the same reason."
2295msgstr ""
2296"Kebijakan kepatuhan data yang mengatur jenis informasi tertentu yang perlu "
2297"berada di lokasi tertentu karena masalah peraturan - dan yang lebih penting, "
2298"tidak dapat berada di lokasi lain karena alasan yang sama."
2299
2300msgid ""
2301"Data location policies ensuring that the services deployed to the cloud are "
2302"used according to laws and regulations in place for the employees, foreign "
2303"subsidiaries, or third parties."
2304msgstr ""
2305"Kebijakan lokasi data yang memastikan bahwa layanan yang digunakan untuk "
2306"cloud digunakan sesuai dengan hukum dan peraturan yang berlaku untuk "
2307"karyawan, anak perusahaan asing, atau pihak ketiga."
2308
2309msgid ""
2310"Data ownership policies governing the possession and responsibility for data."
2311msgstr ""
2312"Kebijakan kepemilikan data yang mengatur kepemilikan dan tanggung jawab atas "
2313"data."
2314
2315msgid "Data processing service for OpenStack (sahara)"
2316msgstr "Layanan pemrosesan data untuk OpenStack (sahara)"
2317
2318msgid ""
2319"Data retention policies ensuring storage of persistent data and records "
2320"management to meet data archival requirements."
2321msgstr ""
2322"Kebijakan penyimpanan data memastikan penyimpanan data yang persisten dan "
2323"manajemen catatan untuk memenuhi persyaratan arsip data."
2324
2325msgid "Data security domains"
2326msgstr "Domain keamanan data"
2327
2328msgid ""
2329"Data sovereignty policies governing the storage of data in foreign countries "
2330"or otherwise separate jurisdictions."
2331msgstr ""
2332"Kebijakan kedaulatan data yang mengatur penyimpanan data di negara asing "
2333"atau yurisdiksi terpisah."
2334
2335msgid ""
2336"Data storage regulations in Europe are currently driven by provisions of the "
2337"`Data protection board <https://edpb.europa.eu/>`_. `Financial Industry "
2338"Regulatory Authority <http://finra.complinet.com/>`_ works on this in the "
2339"United States."
2340msgstr ""
2341"Peraturan penyimpanan data di Eropa saat ini didorong oleh ketentuan `Data "
2342"protection board <https://edpb.europa.eu/>`_. `Financial Industry Regulatory "
2343"Authority <http://finra.complinet.com/>`_ bekerja pada ini di Amerika "
2344"Serikat."
2345
2346msgid "Database Backups"
2347msgstr "Backup Database"
2348
2349msgid "Database Connectivity"
2350msgstr "Konektivitas Basis Data"
2351
2352msgid "Database as a Service (trove)"
2353msgstr "Database as a Service (trove)"
2354
2355msgid "Databases"
2356msgstr "Databases"
2357
2358msgid "Dealing with Network Namespaces"
2359msgstr "Berurusan dengan Network Namespaces"
2360
2361msgid "Debugging DHCP Issues with nova-network"
2362msgstr "Debugging Issue DHCP dengan nova-network"
2363
2364msgid "Debugging DNS Issues"
2365msgstr "Mendebug DNS Issues"
2366
2367msgid ""
2368"Decrease DHCP timeouts by modifying the :file:`/etc/nova/nova.conf` file on "
2369"the compute nodes back to the original value for your environment."
2370msgstr ""
2371"Kurangi waktu tunggu DHCP dengan memodifikasi file :file:`/etc/nova/nova."
2372"conf` pada komputasi nodes kembali ke nilai asli untuk lingkungan Anda."
2373
2374msgid ""
2375"Dedicate entire disks to certain partitions. For example, you could allocate "
2376"disk one and two entirely to the boot, root, and swap partitions under a "
2377"RAID 1 mirror. Then, allocate disk three and four entirely to the LVM "
2378"partition, also under a RAID 1 mirror. Disk I/O should be better because I/O "
2379"is focused on dedicated tasks. However, the LVM partition is much smaller."
2380msgstr ""
2381"Dedikasikan seluruh disk untuk partisi tertentu. Misalnya, Anda bisa "
2382"mengalokasikan disk satu dan dua seluruhnya untuk partisi boot, root, dan "
2383"swap di bawah mirror RAID 1. Kemudian, alokasikan disk tiga dan empat "
2384"seluruhnya ke partisi LVM, juga di bawah mirror RAID 1. Disk I/O harus lebih "
2385"baik karena I/O fokus pada tugas khusus. Namun, partisi LVM jauh lebih kecil."
2386
2387msgid ""
2388"Default CPU overcommit ratio (``cpu_allocation_ratio`` in the ``nova.conf`` "
2389"file) of 16:1."
2390msgstr ""
2391"Rasio overcommit CPU default (``cpu_allocation_ratio`` dalam file ``nova."
2392"conf``) dari 16: 1."
2393
2394msgid "Default drop rule for unmatched traffic."
2395msgstr "Aturan penurunan default untuk lalu lintas yang tidak cocok."
2396
2397msgid ""
2398"Delete the instance and create a new instance using the ``--nic port-id`` "
2399"option."
2400msgstr ""
2401"Hapus instance dan buat instance baru menggunakan opsi ``--nic port-id``."
2402
2403msgid "Delete the ports that are not needed:"
2404msgstr "Hapus port yang tidak diperlukan:"
2405
2406msgid ""
2407"Depending on the type of server, the contents and order of your package list "
2408"might vary from this example."
2409msgstr ""
2410"Bergantung pada jenis server, isi dan urutan daftar paket Anda mungkin "
2411"berbeda dari contoh ini."
2412
2413msgid ""
2414"Depending on your specific configuration, upgrading all packages might "
2415"restart or break services supplemental to your OpenStack environment. For "
2416"example, if you use the TGT iSCSI framework for Block Storage volumes and "
2417"the upgrade includes new packages for it, the package manager might restart "
2418"the TGT iSCSI services and impact connectivity to volumes."
2419msgstr ""
2420"Bergantung pada konfigurasi spesifik Anda, upgrading semua paket mungkin "
2421"restart atau merusak (break) layanan tambahan ke lingkungan OpenStack Anda. "
2422"Misalnya, jika Anda menggunakan framework TGT iSCSI untuk volume Block "
2423"Storage dan upgrade termasuk paket-paket baru untuk itu, manajer paket "
2424"mungkin restart layanan TGT iSCSI dan berdampak konektivitas ke volume."
2425
2426msgid "Deployment"
2427msgstr "Deployment"
2428
2429msgid "Deprecation of Nova Network"
2430msgstr "Penghentian Nova Network"
2431
2432msgid "Description"
2433msgstr "Deskripsi"
2434
2435msgid ""
2436"Designate a server as the central logging server. The best practice is to "
2437"choose a server that is solely dedicated to this purpose. Create a file "
2438"called ``/etc/rsyslog.d/server.conf`` with the following contents:"
2439msgstr ""
2440"Tentukan server sebagai server logging pusat. Praktik terbaik adalah memilih "
2441"server yang semata-mata didedikasikan untuk tujuan ini. Buat file bernama "
2442"``/etc/rsyslog.d/server.conf`` dengan konten berikut:"
2443
2444msgid "Detective controls:"
2445msgstr "Kontrol detektif:"
2446
2447msgid ""
2448"Determine which OpenStack packages are installed on your system. Use the :"
2449"command:`dpkg --get-selections` command. Filter for OpenStack packages, "
2450"filter again to omit packages explicitly marked in the ``deinstall`` state, "
2451"and save the final output to a file. For example, the following command "
2452"covers a controller node with keystone, glance, nova, neutron, and cinder:"
2453msgstr ""
2454"Tentukan paket OpenStack mana yang diinstal pada sistem Anda. Gunakan "
2455"perintah :command:`dpkg --get-selections`. Saring untuk paket OpenStack, "
2456"saring lagi untuk menghilangkan paket yang secara eksplisit ditandai dalam "
2457"keadaan ``deinstall``, dan simpan hasil akhir ke file. Misalnya, perintah "
2458"berikut ini mencakup node pengontrol dengan keystone, glance, nova, neutron, "
2459"dan cinder:"
2460
2461msgid "Determine which servers the RabbitMQ alarms are coming from."
2462msgstr "Tentukan dari server mana alarm RabbitMQ berasal."
2463
2464msgid "Determining Which Component Is Broken"
2465msgstr "Menentukan Komponen Yang Rusak"
2466
2467msgid "Determining cloud scalability"
2468msgstr "Menentukan skalabilitas cloud"
2469
2470msgid ""
2471"Determining the scalability of your cloud and how to improve it requires "
2472"balancing many variables. No one solution meets everyone's scalability "
2473"goals. However, it is helpful to track a number of metrics. You can define "
2474"virtual hardware templates called \"flavors\" in OpenStack, which will "
2475"impact your cloud scaling decisions. These templates define sizes for memory "
2476"in RAM, root disk size, amount of ephemeral data disk space available, and "
2477"the number of CPU cores."
2478msgstr ""
2479"Menentukan skalabilitas cloud Anda dan cara memperbaikinya memerlukan "
2480"penyeimbangan banyak variabel. Tidak ada solusi yang memenuhi sasaran "
2481"skalabilitas semua orang. Namun, melacak sejumlah metrik bermanfaat. Anda "
2482"dapat mendefinisikan template perangkat keras virtual yang disebut \"flavors"
2483"\" di OpenStack, yang akan memengaruhi keputusan penskalaan cloud Anda. "
2484"Template ini menentukan ukuran untuk memori dalam RAM, ukuran disket root, "
2485"jumlah ruang disk data sementara yang tersedia, dan jumlah core CPU."
2486
2487msgid "Deterrent controls:"
2488msgstr "Kontrol pencegah (deterrent):"
2489
2490msgid ""
2491"Develop an upgrade procedure and assess it thoroughly by using a test "
2492"environment similar to your production environment."
2493msgstr ""
2494"Kembangkan prosedur upgrade dan nilai secara menyeluruh dengan menggunakan "
2495"lingkungan pengujian yang serupa dengan lingkungan produksi Anda."
2496
2497msgid "Diagnose Your Compute Nodes"
2498msgstr "Diagnosis Node Komputasi Anda"
2499
2500msgid "Differences Between Various Drivers"
2501msgstr "Perbedaan Antara Berbagai Driver"
2502
2503msgid ""
2504"Differentiations between \"hot\" (active) and \"cold\" (inactive) sites, "
2505"where significant savings may be made in situations where one site is a cold "
2506"standby for disaster recovery purposes only."
2507msgstr ""
2508"Perbedaan antara situs \"hot\" (active) dan \"cold\" (inactive), di mana "
2509"penghematan yang signifikan dapat dilakukan dalam situasi di mana satu situs "
2510"siaga cold untuk tujuan pemulihan bencana saja."
2511
2512msgid "Direct incoming traffic from VM to the security group chain."
2513msgstr "Lalu lintas masuk langsung dari VM ke rantai grup keamanan."
2514
2515msgid "Direct packets associated with a known session to the RETURN chain."
2516msgstr ""
2517"Paket langsung yang terkait dengan sesi yang diketahui ke rantai RETURN."
2518
2519msgid "Direct traffic from the VM interface to the security group chain."
2520msgstr "Lalu lintas langsung dari antarmuka VM ke rantai grup keamanan."
2521
2522msgid ""
2523"Disable scheduling of new VMs to the node, optionally providing a reason "
2524"comment:"
2525msgstr ""
2526"Nonaktifkan penjadwalan VM baru ke node, opsional memberikan komentar alasan:"
2527
2528msgid "Disappearing Images"
2529msgstr "Gambar yang hilang"
2530
2531msgid ""
2532"Disaster recovery policies ensuring regular data backups and relocation of "
2533"cloud applications to another supplier in scenarios where a provider may go "
2534"out of business, or their data center could become inoperable."
2535msgstr ""
2536"Kebijakan pemulihan bencana memastikan pencadangan data berkala dan relokasi "
2537"aplikasi cloud ke pemasok lain dalam skenario di mana penyedia mungkin "
2538"keluar dari bisnis, atau pusat data mereka bisa menjadi tidak dapat "
2539"dioperasikan."
2540
2541msgid "Disconnect the qemu-nbd device."
2542msgstr "Putuskan sambungan perangkat qemu-nbd."
2543
2544msgid ""
2545"Discrete regions with separate API endpoints and no coordination between "
2546"regions."
2547msgstr ""
2548"Wilayah diskrit dengan endpoint API terpisah dan tidak ada koordinasi antar "
2549"wilayah."
2550
2551msgid "Disk"
2552msgstr "Disk"
2553
2554msgid "Disk partitioning and RAID"
2555msgstr "Partisi disk dan RAID"
2556
2557msgid "Disk partitioning and disk array setup for scalability"
2558msgstr "Partisi disk dan pengaturan array disk untuk skalabilitas"
2559
2560msgid "Disk space"
2561msgstr "Ruang disk"
2562
2563msgid "Disk space is cheap these days. Data recovery is not."
2564msgstr "Ruang disk bisa murah hari ini. Pemulihan data akan tidak."
2565
2566msgid "Disk usage"
2567msgstr "Disk usage"
2568
2569msgid "Distributed Virtual Router"
2570msgstr "Distributed Virtual Router (router virtual terdistribusi)"
2571
2572msgid ""
2573"Do a full manual install by using the `Installation Tutorials and Guides "
2574"<https://docs.openstack.org/rocky/install/>`_ for your platform. Review the "
2575"final configuration files and installed packages."
2576msgstr ""
2577"Lakukan instalasi manual lengkap dengan menggunakan `Installation Tutorials "
2578"and Guides <https://docs.openstack.org/rocky/install/>` _ untuk platform "
2579"Anda. Tinjau file konfigurasi akhir dan paket yang diinstal."
2580
2581msgid "Double VLAN"
2582msgstr "VLAN ganda"
2583
2584msgid "Down the Rabbit Hole"
2585msgstr "Down the Rabbit Hole (masuk kedalam lubang kelinci)"
2586
2587msgid "Downgrade OpenStack packages."
2588msgstr "Downgrade paket OpenStack."
2589
2590msgid ""
2591"Downgrading packages is by far the most complicated step; it is highly "
2592"dependent on the distribution and the overall administration of the system."
2593msgstr ""
2594"Paket penurunan versi sejauh ini merupakan langkah paling rumit; sangat "
2595"tergantung pada distribusi dan administrasi keseluruhan sistem."
2596
2597msgid ""
2598"Downtime, whether planned or unscheduled, is a certainty when running a "
2599"cloud. This chapter aims to provide useful information for dealing "
2600"proactively, or reactively, with these occurrences."
2601msgstr ""
2602"Waktu henti, baik yang direncanakan atau tidak, adalah kepastian saat "
2603"menjalankan cloud. Bab ini bertujuan untuk memberikan informasi yang berguna "
2604"untuk menangani kejadian ini secara proaktif, atau reaktif."
2605
2606msgid "Driver Quality Improvements"
2607msgstr "Peningkatan Kualitas Driver"
2608
2609msgid "Drop packets that are not associated with a state."
2610msgstr "Turunkan paket yang tidak terkait dengan keadaan."
2611
2612msgid "Drop traffic without an IP/MAC allow rule."
2613msgstr "Turunkan traffic tanpa aturan IP/MAC."
2614
2615msgid ""
2616"During an upgrade, operators can add configuration options to ``nova.conf`` "
2617"which lock the version of RPC messages and allow live upgrading of the "
2618"services without interruption caused by version mismatch. The configuration "
2619"options allow the specification of RPC version numbers if desired, but "
2620"release name alias are also supported. For example:"
2621msgstr ""
2622"Selama upgrade, operator dapat menambahkan opsi konfigurasi ke ``nova.conf`` "
2623"yang mengunci versi pesan RPC dan memungkinkan upgrade langsung layanan "
2624"tanpa gangguan yang disebabkan oleh ketidakcocokan versi. Opsi konfigurasi "
2625"memungkinkan spesifikasi nomor versi RPC jika diinginkan, tetapi nama alias "
2626"rilis juga didukung. Sebagai contoh:"
2627
2628msgid ""
2629"EC2 compatibility credentials can be downloaded by selecting :guilabel:"
2630"`Project`, then :guilabel:`Compute`, then :guilabel:`Access & Security`, "
2631"then :guilabel:`API Access` to display the :guilabel:`Download EC2 "
2632"Credentials` button. Click the button to generate a ZIP file with server "
2633"x509 certificates and a shell script fragment. Create a new directory in a "
2634"secure location because these are live credentials containing all the "
2635"authentication information required to access your cloud identity, unlike "
2636"the default ``user-openrc``. Extract the ZIP file here. You should have "
2637"``cacert.pem``, ``cert.pem``, ``ec2rc.sh``, and ``pk.pem``. The ``ec2rc.sh`` "
2638"is similar to this:"
2639msgstr ""
2640"Kredensial kompatibilitas EC2 dapat diunduh dengan memilih :guilabel:"
2641"`Project`, lalu :guilabel:`Compute`, lalu :guilabel:`Access & Security`, "
2642"lalu :guilabel:`API Access` untuk menampilkan tombol :guilabel:`Download EC2 "
2643"Credentials`. Klik tombol untuk membuat file ZIP dengan sertifikat server "
2644"x509 dan fragmen skrip shell. Buat direktori baru di lokasi yang aman karena "
2645"ini adalah kredensial langsung yang berisi semua informasi otentikasi yang "
2646"diperlukan untuk mengakses identitas cloud Anda, tidak seperti ``user-"
2647"openrc`` default. Ekstrak file ZIP di sini. Anda harus memiliki ``cacert."
2648"pem``, ``cert.pem``, ``ec2rc.sh``, dan ``pk.pem``. ``Ec2rc.sh`` mirip dengan "
2649"ini:"
2650
2651msgid ""
2652"Each OpenStack cloud is different even if you have a near-identical "
2653"architecture as described in this guide. As a result, you must still test "
2654"upgrades between versions in your environment using an approximate clone of "
2655"your environment."
2656msgstr ""
2657"Setiap cloud OpenStack berbeda bahkan jika Anda memiliki arsitektur yang "
2658"hampir sama seperti yang dijelaskan dalam panduan ini. Akibatnya, Anda masih "
2659"harus menguji upgrade antar versi di lingkungan Anda menggunakan klon "
2660"perkiraan lingkungan Anda."
2661
2662msgid ""
2663"Each cloud implements services differently. Understand the security "
2664"requirements of every cloud that handles the organization's data or "
2665"workloads."
2666msgstr ""
2667"Setiap cloud mengimplementasikan layanan secara berbeda. Memahami "
2668"persyaratan keamanan setiap cloud yang menangani data atau beban kerja "
2669"organisasi."
2670
2671msgid ""
2672"Each layer scales horizontally. As the number of logs grows you can add more "
2673"log pushers, more Logstash indexers, and more ElasticSearch nodes."
2674msgstr ""
2675"Setiap lapisan bersisik secara horizontal. Saat jumlah log bertambah, Anda "
2676"dapat menambahkan lebih banyak push log, lebih banyak pengindeks log, dan "
2677"lebih banyak node ElasticSearch."
2678
2679msgid ""
2680"Each method provides different functionality and can be best divided into "
2681"two groups:"
2682msgstr ""
2683"Setiap metode menyediakan fungsionalitas yang berbeda dan dapat dibagi "
2684"menjadi dua kelompok:"
2685
2686msgid ""
2687"Each site runs a different configuration, as a resource cells in an "
2688"OpenStack Compute cells setup. Some sites span multiple data centers, some "
2689"use off compute node storage with a shared file system, and some use on "
2690"compute node storage with a non-shared file system. Each site deploys the "
2691"Image service with an Object Storage back end. A central Identity, "
2692"dashboard, and Compute API service are used. A login to the dashboard "
2693"triggers a SAML login with Shibboleth, which creates an account in the "
2694"Identity service with an SQL back end. An Object Storage Global Cluster is "
2695"used across several sites."
2696msgstr ""
2697"Setiap situs menjalankan konfigurasi yang berbeda, sebagai sel sumber daya "
2698"dalam pengaturan sel OpenStack Compute. Beberapa situs menjangkau beberapa "
2699"pusat data, beberapa menggunakan penyimpanan node komputasi dengan sistem "
2700"file bersama, dan beberapa digunakan pada penyimpanan node komputasi dengan "
2701"sistem file yang tidak digunakan bersama. Setiap situs menyebarkan layanan "
2702"Image dengan back end Object Storage. Layanan Identity pokok, dashboard, dan "
2703"Compute API digunakan. Login ke dasbor memicu login SAML dengan Shibboleth, "
2704"yang membuat akun di layanan Identity dengan SQL back end. Object Storage "
2705"Global Cluster digunakan di beberapa situs."
2706
2707msgid ""
2708"Early indications are that it does do this well for a base set of scenarios, "
2709"such as using the ML2 plug-in with Open vSwitch, one flat external network "
2710"and VXLAN tenant networks. However, it does appear that there are problems "
2711"with the use of VLANs, IPv6, Floating IPs, high north-south traffic "
2712"scenarios and large numbers of compute nodes. It is expected these will "
2713"improve significantly with the next release, but bug reports on specific "
2714"issues are highly desirable."
2715msgstr ""
2716"Indikasi awal adalah bahwa ia melakukan ini dengan baik untuk serangkaian "
2717"skenario dasar, seperti menggunakan plug-in ML2 dengan Open vSwitch, satu "
2718"jaringan eksternal datar dan jaringan penyewa VXLAN. Namun, tampaknya ada "
2719"masalah dengan penggunaan VLAN, IPv6, Floating IPs, skenario lalu lintas "
2720"north-south yang tinggi dan sejumlah besar node komputasi. Diharapkan ini "
2721"akan meningkat secara signifikan dengan rilis berikutnya, tetapi laporan bug "
2722"tentang masalah spesifik sangat diinginkan."
2723
2724msgid "Easier Upgrades"
2725msgstr "Upgrade yang Lebih Mudah"
2726
2727msgid ""
2728"Edit the ``/etc/rabbitmq/rabbitmq.config`` configuration file, and change "
2729"the ``collect_statistics_interval`` parameter between 30000-60000 "
2730"milliseconds. Alternatively you can turn off statistics collection by "
2731"setting ``collect_statistics`` parameter to \"none\"."
2732msgstr ""
2733"Edit file konfigurasi ``/etc/rabbitmq/rabbitmq.config``, dan ubah parameter "
2734"``collect_statistics_interval`` antara 30000-60000 milidetik. Atau Anda "
2735"dapat mematikan pengumpulan statistik dengan mengatur parameter "
2736"``collect_statistics`` menjadi \"none\"."
2737
2738msgid ""
2739"Either approach is valid. Use the approach that matches your experience."
2740msgstr ""
2741"Semua pendekatan ini valid. Gunakan pendekatan yang sesuai dengan pengalaman "
2742"Anda."
2743
2744msgid "ElasticSearch"
2745msgstr "ElasticSearch"
2746
2747msgid ""
2748"Emma Richards of Rackspace Guest Relations took excellent care of our lunch "
2749"orders and even set aside a pile of sticky notes that had fallen off the "
2750"walls."
2751msgstr ""
2752"Emma Richards dari Rackspace Guest Relations merawat pesanan makan siang "
2753"kami dengan sangat baik dan bahkan menyisihkan setumpuk catatan tempel yang "
2754"jatuh dari dinding."
2755
2756msgid "Enable scheduling of VMs to the node:"
2757msgstr "Aktifkan penjadwalan VM ke node:"
2758
2759msgid "Enabling IPv6 Support"
2760msgstr "Mengaktifkan Dukungan IPv6"
2761
2762msgid "Encode certificate in DER format"
2763msgstr "Encode sertifikat dalam format DER"
2764
2765msgid ""
2766"Ensure that cryptsetup is installed, and ensure that ``pythin-"
2767"barbicanclient`` Python package is installed"
2768msgstr ""
2769"Pastikan cryptsetup diinstal, dan pastikan bahwa ``pythin-barbicanclient`` "
2770"Python package diinstal"
2771
2772msgid "Ensure that the operating system has recognized the new disk:"
2773msgstr "Pastikan sistem operasi telah mengenali disk baru:"
2774
2775msgid "Ephemeral"
2776msgstr "Ephemeral"
2777
2778msgid ""
2779"Even at smaller-scale testing, look for excess network packets to determine "
2780"whether something is going horribly wrong in inter-component communication."
2781msgstr ""
2782"Bahkan pada pengujian skala kecil, cari paket jaringan berlebih untuk "
2783"menentukan apakah ada sesuatu yang salah dalam komunikasi antar-komponen."
2784
2785msgid ""
2786"Ever have one of those days where all of the sudden you get the Google "
2787"results you were looking for? Well, that's what happened here. I was looking "
2788"for information on dhclient and why it dies when it can't renew its lease "
2789"and all of the sudden I found a bunch of OpenStack and dnsmasq discussions "
2790"that were identical to the problem we were seeing!"
2791msgstr ""
2792"Pernahkah mengalami salah satu dari hari-hari itu di mana tiba-tiba Anda "
2793"mendapatkan hasil Google yang Anda cari? Nah, itulah yang terjadi di sini. "
2794"Saya mencari informasi tentang dhclient dan mengapa ia mati ketika ia tidak "
2795"dapat memperpanjang sewa dan tiba-tiba saya menemukan banyak diskusi "
2796"OpenStack dan dnsmasq yang identik dengan masalah yang kami lihat!"
2797
2798msgid "Excessive database management memory consumption"
2799msgstr "Konsumsi memori manajemen database yang berlebihan"
2800
2801msgid "Factors affecting OpenStack deployment"
2802msgstr "Faktor-faktor yang mempengaruhi pengerahan OpenStack"
2803
2804msgid ""
2805"Failures of hardware are common in large-scale deployments such as an "
2806"infrastructure cloud. Consider your processes and balance time saving "
2807"against availability. For example, an Object Storage cluster can easily live "
2808"with dead disks in it for some period of time if it has sufficient capacity. "
2809"Or, if your compute installation is not full, you could consider live "
2810"migrating instances off a host with a RAM failure until you have time to "
2811"deal with the problem."
2812msgstr ""
2813"Kegagalan perangkat keras umum terjadi dalam penyebaran berskala besar "
2814"seperti cloud infrastruktur. Pertimbangkan proses Anda dan seimbangkan "
2815"penghematan waktu dengan ketersediaan. Sebagai contoh, sebuah cluster Object "
2816"Storage dapat dengan mudah hidup dengan disk mati di dalamnya untuk beberapa "
2817"periode waktu jika memiliki kapasitas yang cukup. Atau, jika instalasi "
2818"komputasi Anda tidak penuh, Anda dapat mempertimbangkan memigrasi instance "
2819"langsung dari host dengan kegagalan RAM hingga Anda punya waktu untuk "
2820"mengatasi masalah tersebut."
2821
2822msgid "Family Educational Rights and Privacy Act (FERPA)"
2823msgstr "Family Educational Rights and Privacy Act (FERPA)"
2824
2825msgid ""
2826"Feature requests typically start their life in Etherpad, a collaborative "
2827"editing tool, which is used to take coordinating notes at a design summit "
2828"session specific to the feature. This then leads to the creation of a "
2829"blueprint on the Launchpad site for the particular project, which is used to "
2830"describe the feature more formally. Blueprints are then approved by project "
2831"team members, and development can begin."
2832msgstr ""
2833"Permintaan fitur biasanya memulai kehidupannya di Etherpad, alat pengeditan "
2834"kolaboratif, yang digunakan untuk membuat catatan koordinasi pada sesi "
2835"puncak desain khusus untuk fitur tersebut. Ini kemudian mengarah pada "
2836"pembuatan cetak biru di situs Launchpad untuk proyek tertentu, yang "
2837"digunakan untuk menggambarkan fitur lebih formal. Cetak biru kemudian "
2838"disetujui oleh anggota tim proyek, dan pengembangan dapat dimulai."
2839
2840msgid ""
2841"Felix Lee of Academia Sinica Grid Computing Centre in Taiwan contributed "
2842"this story."
2843msgstr ""
2844"Felix Lee dari Academia Sinica Grid Computing Center di Taiwan menyumbangkan "
2845"cerita ini."
2846
2847msgid "Figure. Neutron network paths"
2848msgstr "Figur. Jalur jaringan neutron"
2849
2850msgid "Figure. Traffic route for ping packet"
2851msgstr "Angka. Rute lalu lintas untuk paket ping"
2852
2853msgid "File System Backups"
2854msgstr "Cadangan Sistem File"
2855
2856msgid "File descriptor limits when scaling a cloud environment"
2857msgstr "Batas deskriptor file saat menskala lingkungan cloud"
2858
2859msgid ""
2860"File system to store files and directories, where all the data lives, "
2861"including the root partition that starts and runs the system."
2862msgstr ""
2863"Sistem file untuk menyimpan file dan direktori, tempat semua data hidup, "
2864"termasuk partisi root yang memulai dan menjalankan sistem."
2865
2866msgid "Final steps"
2867msgstr "Langkah terakhir"
2868
2869msgid ""
2870"Finally, Alvaro noticed something. When a packet from the outside hits the "
2871"cloud controller, it should not be configured with a VLAN. We verified this "
2872"as true. When the packet went from the cloud controller to the compute node, "
2873"it should only have a VLAN if it was destined for an instance. This was "
2874"still true. When the ping reply was sent from the instance, it should be in "
2875"a VLAN. True. When it came back to the cloud controller and on its way out "
2876"to the Internet, it should no longer have a VLAN. False. Uh oh. It looked as "
2877"though the VLAN part of the packet was not being removed."
2878msgstr ""
2879"Akhirnya, Alvaro memperhatikan sesuatu. Ketika sebuah paket dari luar "
2880"mengenai pengendali cloud, itu tidak harus dikonfigurasikan dengan VLAN. "
2881"Kami memverifikasi ini sebagai benar. Ketika paket pergi dari cloud "
2882"controller ke compute node, seharusnya hanya memiliki VLAN jika ditakdirkan "
2883"untuk instance. Ini masih benar. Ketika balasan ping dikirim dari instance, "
2884"itu harus dalam VLAN. Benar. Ketika kembali ke pengontrol cloud dan dalam "
2885"perjalanan keluar ke Internet, seharusnya tidak lagi memiliki VLAN. Salah. "
2886"Uh oh. Tampaknya bagian VLAN dari paket itu tidak dihapus."
2887
2888msgid ""
2889"Finally, I checked StackTach and reviewed the user's events. They had "
2890"created and deleted several snapshots—most likely experimenting. Although "
2891"the timestamps didn't match up, my conclusion was that they launched their "
2892"instance and then deleted the snapshot and it was somehow removed from ``/"
2893"var/lib/nova/instances/_base``. None of that made sense, but it was the best "
2894"I could come up with."
2895msgstr ""
2896"Akhirnya, saya memeriksa StackTach dan meninjau acara pengguna. Mereka telah "
2897"membuat dan menghapus beberapa foto — kemungkinan besar bereksperimen. "
2898"Meskipun timestamp tidak cocok, kesimpulan saya adalah bahwa mereka "
2899"meluncurkan instance mereka dan kemudian menghapus snapshot dan entah "
2900"bagaimana dihapus dari ``/var/lib/nova/instances/_base``. Tidak ada yang "
2901"masuk akal, tapi itu yang terbaik yang bisa saya lakukan."
2902
2903msgid "Finally, mount the disk:"
2904msgstr "Akhirnya, pasang disk:"
2905
2906msgid ""
2907"Finally, reattach volumes using the same method described in the section :"
2908"ref:`volumes`."
2909msgstr ""
2910"Terakhir, pasang kembali volume menggunakan metode yang sama seperti yang "
2911"dijelaskan di bagian :ref:`volume`."
2912
2913msgid ""
2914"Find the ID for each instance by listing the server IDs using the following "
2915"command:"
2916msgstr ""
2917"Temukan ID untuk setiap instance dengan mendaftar ID server menggunakan "
2918"perintah berikut:"
2919
2920msgid ""
2921"Find the ``[filter:ratelimit]`` section in ``/etc/swift/proxy-server.conf``, "
2922"and copy in the following configuration section after it:"
2923msgstr ""
2924"Temukan bagian ``[filter: ratelimit] `` di ``/etc/swift/proxy-server.conf``, "
2925"dan salin di bagian konfigurasi berikut setelahnya:"
2926
2927msgid ""
2928"Find the ``[pipeline:main]`` section in ``/etc/swift/proxy-server.conf``, "
2929"and add ``ip_whitelist`` after ratelimit to the list like so. When you're "
2930"done, save and close the file:"
2931msgstr ""
2932"Temukan bagian ``[pipeline: main] `` di ``/etc/swift/proxy-server.conf``, "
2933"dan tambahkan ``ip_whitelist`` setelah ratelimit ke daftar seperti itu. "
2934"Setelah selesai, simpan dan tutup file:"
2935
2936msgid ""
2937"Find the ``provider:segmentation_id`` of the network you're interested in. "
2938"This is the same field used for the VLAN ID in VLAN-based networks:"
2939msgstr ""
2940"Temukan ``provider: segmentation_id`` dari jaringan yang Anda minati. Ini "
2941"adalah bidang yang sama dengan yang digunakan untuk ID VLAN di jaringan "
2942"berbasis VLAN:"
2943
2944msgid "Find the ``scheduler_driver`` config and change it like so:"
2945msgstr "Temukan konfigurasi ``scheduler_driver`` dan ubah seperti ini:"
2946
2947msgid ""
2948"Find the external VLAN tag of the network you're interested in. This is the "
2949"``provider:segmentation_id`` as returned by the networking service:"
2950msgstr ""
2951"Temukan tag VLAN eksternal dari jaringan yang Anda minati. Ini adalah "
2952"``provider:segmentation_id`` yang dikembalikan oleh layanan jaringan:"
2953
2954msgid "Find the port corresponding to the instance. For example:"
2955msgstr "Temukan port yang sesuai dengan instance. Sebagai contoh:"
2956
2957msgid "Finding a Failure in the Path"
2958msgstr "Menemukan Kegagalan di Path"
2959
2960msgid "Firewalls"
2961msgstr "Firewalls"
2962
2963msgid "First, find the UUID of the instance in question:"
2964msgstr "Pertama, temukan UUID dari instance yang dimaksud:"
2965
2966msgid "First, unmount the disk:"
2967msgstr "Pertama, lepaskan disk:"
2968
2969msgid ""
2970"First, you can discover what servers belong to your OpenStack cloud by "
2971"running:"
2972msgstr ""
2973"Pertama, Anda dapat menemukan server apa yang menjadi milik OpenStack cloud "
2974"Anda dengan menjalankan:"
2975
2976msgid "Fixed IPs"
2977msgstr "IP tetap"
2978
2979msgid "Floating IPs"
2980msgstr "IP mengambang"
2981
2982msgid "For Object Storage, each region has a swift environment."
2983msgstr "Untuk Object Storage, setiap wilayah memiliki lingkungan yang cepat."
2984
2985msgid ""
2986"For a discussion of metric tracking, including how to extract metrics from "
2987"your cloud, see the `OpenStack Operations Guide <https://docs.openstack.org/"
2988"operations-guide/ops-logging-monitoring.html>`_."
2989msgstr ""
2990"Untuk diskusi tentang pelacakan metrik, termasuk cara mengekstrak metrik "
2991"dari cloud Anda, lihat `OpenStack Operations Guide <https://docs.openstack."
2992"org/operations-guide/ops-logging-monitoring.html>`_."
2993
2994msgid ""
2995"For compute nodes, ``nova-scheduler`` will manage differences in sizing with "
2996"core count and RAM. However, you should consider that the user experience "
2997"changes with differing CPU speeds. When adding object storage nodes, a :term:"
2998"`weight` should be specified that reflects the :term:`capability` of the "
2999"node."
3000msgstr ""
3001"Untuk komputasi node, ``nova-scheduler`` akan mengatur perbedaan ukuran "
3002"dengan core count dan RAM. Namun, Anda harus mempertimbangkan bahwa "
3003"pengalaman pengguna berubah dengan kecepatan CPU yang berbeda. Saat "
3004"menambahkan node penyimpanan objek, :term: `weight` harus ditentukan yang "
3005"mencerminkan :term:` capability ` node."
3006
3007msgid ""
3008"For each compute node your environment, view the ``/etc/init.d`` directory "
3009"and check if it contains nova*, cinder*, neutron*, or glance*, Also check "
3010"RabbitMQ message queues that are growing without being consumed which will "
3011"indicate which OpenStack services are affected. Restart the affected "
3012"OpenStack services."
3013msgstr ""
3014"Untuk setiap node komputasi lingkungan Anda, lihat direktori ``/etc/init."
3015"d`` dan periksa apakah mengandung nova*, cinder*, neutron*, or glance*, "
3016"Juga periksa antrian pesan RabbitMQ yang tumbuh tanpa dikonsumsi yang akan "
3017"menunjukkan layanan OpenStack mana yang terpengaruh. Mulai ulang layanan "
3018"OpenStack yang terpengaruh."
3019
3020msgid ""
3021"For each controller node in your environment, view the ``/etc/init.d`` "
3022"directory to check it contains nova*, cinder*, neutron*, or glance*. Also "
3023"check RabbitMQ message queues that are growing without being consumed which "
3024"will indicate which OpenStack service is affected. Restart the affected "
3025"OpenStack service."
3026msgstr ""
3027"Untuk setiap node pengontrol di lingkungan Anda, lihat direktori ``/etc/init."
3028"d`` untuk memeriksanya berisi nova*, cinder*, neutron*, atau glance*. Juga "
3029"periksa antrian pesan RabbitMQ yang tumbuh tanpa dikonsumsi yang akan "
3030"menunjukkan layanan OpenStack mana yang terpengaruh. Mulai ulang layanan "
3031"OpenStack yang terpengaruh."
3032
3033msgid ""
3034"For environments using the OpenStack Networking service (neutron), verify "
3035"the release version of the database. For example:"
3036msgstr ""
3037"Untuk lingkungan yang menggunakan layanan OpenStack Networking (neutron), "
3038"verifikasi versi rilis dari database. Sebagai contoh:"
3039
3040msgid "For example, run the following command:"
3041msgstr "Misalnya, jalankan perintah berikut:"
3042
3043msgid "For example, to place a 5 GB quota on an account:"
3044msgstr "Misalnya, untuk menempatkan kuota 5 GB pada akun:"
3045
3046msgid "For example, to restrict a project's image storage to 5 GB, do this:"
3047msgstr ""
3048"Misalnya, untuk membatasi penyimpanan image proyek hingga 5 GB, lakukan ini:"
3049
3050msgid ""
3051"For example, you usually cannot configure NICs for VLANs when PXE booting. "
3052"Additionally, you usually cannot PXE boot with bonded NICs. If you run into "
3053"this scenario, consider using a simple 1 GB switch in a private network on "
3054"which only your cloud communicates."
3055msgstr ""
3056"Misalnya, Anda biasanya tidak dapat mengonfigurasi NIC untuk VLAN saat PXE "
3057"boot. Selain itu, Anda biasanya tidak dapat melakukan PXE boot dengan NIC "
3058"terikat. Jika Anda mengalami skenario ini, pertimbangkan untuk menggunakan "
3059"switch 1 GB sederhana di jaringan pribadi tempat cloud Anda berkomunikasi."
3060
3061msgid "For example:"
3062msgstr "Sebagai contoh:"
3063
3064msgid ""
3065"For further research about OpenStack deployment, investigate the supported "
3066"and documented preconfigured, prepackaged installers for OpenStack from "
3067"companies such as `Canonical <https://www.ubuntu.com/openstack>`_, `Cisco "
3068"<https://www.cisco.com/c/en/us/solutions/data-center-virtualization/"
3069"openstack-at-cisco/index.html>`_, `Cloudscaling <http://cloudscaling.com/"
3070"blog/>`_, `IBM <http://www-03.ibm.com/software/products/en/ibm-cloud-"
3071"orchestrator>`_, `Metacloud <http://www.cisco.com/c/en/us/products/cloud-"
3072"systems-management/metacloud/index.html>`_, `Mirantis <https://www.mirantis."
3073"com>`_, `Rackspace <https://www.rackspace.com/cloud/private>`_, `Red Hat "
3074"<https://www.redhat.com/openstack>`_, `SUSE <https://www.suse.com/products/"
3075"suse-openstack-cloud>`_, and `SwiftStack <https://www.swiftstack.com>`_."
3076msgstr ""
3077"Untuk penelitian lebih lanjut tentang penyebaran OpenStack, selidiki "
3078"installer prakonfigurasi yang didukung dan didokumentasikan, yang telah "
3079"dikemas untuk OpenStack dari perusahaan seperti `Canonical <https://www."
3080"ubuntu.com/openstack>`_, `Cisco <https://www.cisco.com/c/en/us/solutions/"
3081"data-center-virtualization/openstack-at-cisco/index.html>`_, `Cloudscaling "
3082"<http://cloudscaling.com/blog/>`_, `IBM <http://www-03.ibm.com/software/"
3083"products/en/ibm-cloud-orchestrator>`_, `Metacloud <http://www.cisco.com/c/en/"
3084"us/products/cloud-systems-management/metacloud/index.html>`_, `Mirantis "
3085"<https://www.mirantis.com>`_, `Rackspace <https://www.rackspace.com/cloud/"
3086"private>`_, `Red Hat <https://www.redhat.com/openstack>`_, `SUSE <https://"
3087"www.suse.com/products/suse-openstack-cloud>`_, dan `SwiftStack <https://www."
3088"swiftstack.com>`_."
3089
3090msgid ""
3091"For instructions on installing, upgrading, or removing command-line clients, "
3092"see the `Install the OpenStack command-line client <https://docs.openstack."
3093"org/python-openstackclient/latest/>`_."
3094msgstr ""
3095"Untuk instruksi tentang menginstal, memutakhirkan, atau menghapus klien "
3096"command-line client, lihat `Install the OpenStack command-line client "
3097"<https://docs.openstack.org/python-openstackclient/latest/>`_."
3098
3099msgid ""
3100"For more information OpenStack Security, see the `OpenStack Security Guide "
3101"<https://docs.openstack.org/security-guide/>`_."
3102msgstr ""
3103"Untuk informasi lebih lanjut, OpenStack Security, lihat `OpenStack Security "
3104"Guide <https://docs.openstack.org/security-guide/>`_."
3105
3106msgid ""
3107"For more information on installing DevStack, see the `DevStack <https://docs."
3108"openstack.org/devstack/latest/>`_ website."
3109msgstr ""
3110"Untuk informasi lebih lanjut tentang menginstal DevStack, lihat `DevStack "
3111"<https://docs.openstack.org/devstack/latest/>`_ situs web."
3112
3113msgid ""
3114"For more information, see See also `NIST Special Publication 800-53 <https://"
3115"web.nvd.nist.gov/view/800-53/>`_."
3116msgstr ""
3117"Untuk informasi lebih lanjut, lihat Lihat juga `NIST Special Publication "
3118"800-53 <https://web.nvd.nist.gov/view/800-53/>`_."
3119
3120msgid ""
3121"For more information, see `RabbitMQ documentation <https://www.rabbitmq.com/"
3122"partitions.html>`_."
3123msgstr ""
3124"Untuk informasi lebih lanjut, lihat `RabbitMQ documentation <https://www."
3125"rabbitmq.com/partitions.html>`_."
3126
3127msgid ""
3128"For resource alerting, for example, monitor disk capacity on a compute node "
3129"with Nagios, add the following to your Nagios configuration:"
3130msgstr ""
3131"Untuk peringatan sumber daya, misalnya, monitor kapasitas disk pada node "
3132"komputasi dengan Nagios, tambahkan yang berikut ini ke konfigurasi Nagios "
3133"Anda:"
3134
3135msgid ""
3136"For stable operations, you want to detect failure promptly and determine "
3137"causes efficiently. With a distributed system, it's even more important to "
3138"track the right items to meet a service-level target. Learning where these "
3139"logs are located in the file system or API gives you an advantage. This "
3140"chapter also showed how to read, interpret, and manipulate information from "
3141"OpenStack services so that you can monitor effectively."
3142msgstr ""
3143"Untuk operasi yang stabil, Anda ingin mendeteksi kegagalan dengan segera dan "
3144"menentukan penyebab secara efisien. Dengan sistem terdistribusi, bahkan "
3145"lebih penting untuk melacak item yang tepat untuk memenuhi target tingkat "
3146"layanan. Belajar di mana log ini berada di sistem file atau API memberi Anda "
3147"keuntungan. Bab ini juga menunjukkan cara membaca, menafsirkan, dan "
3148"memanipulasi informasi dari layanan OpenStack sehingga Anda dapat memonitor "
3149"secara efektif."
3150
3151msgid ""
3152"For the cloud controller, the good news is if your cloud is using the "
3153"FlatDHCP multi-host HA network mode, existing instances and volumes continue "
3154"to operate while the cloud controller is offline. For the storage proxy, "
3155"however, no storage traffic is possible until it is back up and running."
3156msgstr ""
3157"Untuk pengendali cloud, kabar baiknya adalah jika cloud Anda menggunakan "
3158"mode jaringan HA multi-host FlatDHCP, instance dan volume yang ada terus "
3159"beroperasi saat pengendali cloud sedang offline. Untuk proksi penyimpanan, "
3160"bagaimanapun, tidak ada lalu lintas penyimpanan yang mungkin sampai itu "
3161"kembali dan berjalan."
3162
3163msgid ""
3164"For the second path, you can write new features and plug them in using "
3165"changes to a configuration file. If the project where your feature would "
3166"need to reside uses the Python Paste framework, you can create middleware "
3167"for it and plug it in through configuration. There may also be specific ways "
3168"of customizing a project, such as creating a new scheduler driver for "
3169"Compute or a custom tab for the dashboard."
3170msgstr ""
3171"Untuk jalur kedua, Anda dapat menulis fitur baru dan menghubungkannya dengan "
3172"menggunakan perubahan pada file konfigurasi. Jika proyek tempat fitur Anda "
3173"harus berada menggunakan framework Python Paste, Anda dapat membuat "
3174"middleware untuk itu dan menghubungkannya melalui konfigurasi. Mungkin juga "
3175"ada cara-cara khusus untuk menyesuaikan proyek, seperti membuat driver "
3176"penjadwal baru untuk Compute atau tab khusus untuk dasbor."
3177
3178msgid ""
3179"For the storage proxy, ensure that the :term:`Object Storage service <Object "
3180"Storage service (swift)>` has resumed:"
3181msgstr ""
3182"Untuk proxy penyimpanan, pastikan bahwa :term:`Object Storage service "
3183"<Object Storage service (swift)>` telah dilanjutkan:"
3184
3185msgid ""
3186"For this example, we will use the Open vSwitch (OVS) back end. Other back-"
3187"end plug-ins will have very different flow paths. OVS is the most popularly "
3188"deployed network driver, according to the April 2016 OpenStack User Survey. "
3189"We'll describe each step in turn, with :ref:`network_paths` for reference."
3190msgstr ""
3191"Untuk contoh ini, kita akan menggunakan back end Open vSwitch (OVS). Plug-in "
3192"back-end lainnya akan memiliki jalur aliran yang sangat berbeda. OVS adalah "
3193"driver jaringan yang paling populer digunakan, menurut Survei Pengguna "
3194"OpenStack April 2016. Kami akan menjelaskan setiap langkah pada gilirannya, "
3195"dengan :ref:`network_paths` sebagai referensi."
3196
3197msgid ""
3198"From the vnet NIC, the packet transfers to a bridge on the compute node, "
3199"such as ``br100``."
3200msgstr ""
3201"Dari vnet NIC, paket mentransfer ke sebuah jembatan (bridge) di node "
3202"komputasi, seperti ``br100``."
3203
3204msgid ""
3205"From these tables, you can see that a floating IP is technically never "
3206"directly related to an instance; it must always go through a fixed IP."
3207msgstr ""
3208"Dari tabel ini, Anda dapat melihat bahwa IP mengambang secara teknis tidak "
3209"pernah terkait langsung dengan instance; itu harus selalu melalui IP tetap."
3210
3211msgid ""
3212"From this you see that the DHCP server on that network is using the "
3213"``tape6256f7d-31`` device and has an IP address of ``10.0.1.100``. Seeing "
3214"the address ``169.254.169.254``, you can also see that the dhcp-agent is "
3215"running a metadata-proxy service. Any of the commands mentioned previously "
3216"in this chapter can be run in the same way. It is also possible to run a "
3217"shell, such as ``bash``, and have an interactive session within the "
3218"namespace. In the latter case, exiting the shell returns you to the top-"
3219"level default namespace."
3220msgstr ""
3221"Dari sini Anda melihat bahwa server DHCP pada jaringan itu menggunakan "
3222"perangkat ``tape6256f7d-31`` dan memiliki alamat IP ``10.0.1.100``. Melihat "
3223"alamat ``169.254.169.254``, Anda juga dapat melihat bahwa agen dhcp "
3224"menjalankan layanan proxy-metadata. Perintah apa pun yang disebutkan "
3225"sebelumnya dalam bab ini dapat dijalankan dengan cara yang sama. "
3226"Dimungkinkan juga untuk menjalankan shell, seperti ``bash``, dan memiliki "
3227"sesi interaktif di dalam namespace. Dalam kasus terakhir, keluar dari shell "
3228"mengembalikan Anda ke namespace default tingkat atas."
3229
3230msgid ""
3231"Functional testing like this is not a replacement for proper unit and "
3232"integration testing, but it serves to get you started."
3233msgstr ""
3234"Pengujian fungsional seperti ini bukan pengganti untuk pengujian unit dan "
3235"integrasi yang tepat, tetapi berfungsi untuk membantu Anda memulai."
3236
3237msgid ""
3238"Further days go by and we catch The Issue in action more and more. We find "
3239"that dhclient is not running after The Issue happens. Now we're back to "
3240"thinking it's a DHCP issue. Running ``/etc/init.d/networking`` restart "
3241"brings everything back up and running."
3242msgstr ""
3243"Hari-hari selanjutnya berlalu dan kami terus menangkap isu ini. Kami "
3244"menemukan bahwa dhclient tidak berj