1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
1187
1188
1189
1190
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284
1285
1286
1287
1288
1289
1290
1291
1292
1293
1294
1295
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340
1341
1342
1343
1344
1345
1346
1347
1348
1349
1350
1351
1352
1353
1354
1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396
1397
1398
1399
1400
1401
1402
1403
1404
1405
1406
1407
1408
1409
1410
1411
1412
1413
1414
1415
1416
1417
1418
1419
1420
1421
1422
1423
1424
|
# SOME DESCRIPTIVE TITLE.
# Copyright (C) Ansible project contributors
# This file is distributed under the same license as the Ansible package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2022.
#
msgid ""
msgstr ""
"Project-Id-Version: Ansible devel\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2023-03-01 20:16+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.9.0\n"
#: ../../rst/inventory_guide/connection_details.rst:5
msgid "Connection methods and details"
msgstr "æ¥ç¶æ¹æ³ããã³è©³çŽ°"
#: ../../rst/inventory_guide/connection_details.rst:7
msgid "This section shows you how to expand and refine the connection methods Ansible uses for your inventory."
msgstr "ãã®ã»ã¯ã·ã§ã³ã§ã¯ãAnsible ãã€ã³ãã³ããªãŒã«äœ¿çšããæ¥ç¶æ¹æ³ãæ¡åŒµããã³æ¹è¯ããæ¹æ³ã瀺ããŸãã"
#: ../../rst/inventory_guide/connection_details.rst:10
msgid "ControlPersist and paramiko"
msgstr "ControlPersist ããã³ paramiko"
#: ../../rst/inventory_guide/connection_details.rst:12
msgid "By default, Ansible uses native OpenSSH, because it supports ControlPersist (a performance feature), Kerberos, and options in ``~/.ssh/config`` such as Jump Host setup. If your control machine uses an older version of OpenSSH that does not support ControlPersist, Ansible will fallback to a Python implementation of OpenSSH called 'paramiko'."
msgstr "ããã©ã«ãã§ã¯ãAnsible ã¯ãã€ãã£ãã® OpenSSH ã䜿çšããŸããããã¯ãControlPersist (ããã©ãŒãã³ã¹æ©èœ)ãKerberosãããã³ Jump Host èšå®ãªã©ã® ``~/.ssh/config`` ã®ãªãã·ã§ã³ããµããŒãããŠããããã§ããã³ã³ãããŒã«ãã·ã³ã ControlPersist ããµããŒãããŠããªãå€ãããŒãžã§ã³ã® OpenSSH ã䜿çšããŠããå ŽåãAnsible ã¯ãparamikoããšåŒã°ãã Python ã«ãã OpenSSH ã®å®è£
ã«ãã©ãŒã«ããã¯ããŸãã"
#: ../../rst/inventory_guide/connection_details.rst:17
msgid "Setting a remote user"
msgstr "ãªã¢ãŒããŠãŒã¶ãŒã®èšå®"
#: ../../rst/inventory_guide/connection_details.rst:19
msgid "By default, Ansible connects to all remote devices with the user name you are using on the control node. If that user name does not exist on a remote device, you can set a different user name for the connection. If you just need to do some tasks as a different user, look at :ref:`become`. You can set the connection user in a playbook:"
msgstr "ããã©ã«ãã§ã¯ãAnsible ã¯ãã¹ãŠã®ãªã¢ãŒãããã€ã¹ã«ãã³ã³ãããŒã«ããŒãã§äœ¿çšããŠãããŠãŒã¶ãŒåã§æ¥ç¶ããŸãããªã¢ãŒãããã€ã¹ã«ãã®ãŠãŒã¶ãŒåãååšããªãå Žåã¯ãæ¥ç¶ã«å¥ã®ãŠãŒã¶ãŒåãèšå®ããããšãã§ããŸããå¥ã®ãŠãŒã¶ãŒãšããŠããã€ãã®ã¿ã¹ã¯ãå®è¡ããã ãã®å Žåã¯ãã:ref:`become`ããåç
§ããŠãã ãããPlaybookã§æ¥ç¶ãŠãŒã¶ãŒãèšå®ããããšãã§ããŸãã"
#: ../../rst/inventory_guide/connection_details.rst:32
msgid "as a host variable in inventory:"
msgstr "ã€ã³ãã³ããªãŒã®ãã¹ãå€æ°ã§ã¯ã以äžã®ããã«ãªããŸãã"
#: ../../rst/inventory_guide/connection_details.rst:39
msgid "or as a group variable in inventory:"
msgstr "ãŸããã€ã³ãã³ããªãŒã®ã°ããŒãã«å€æ°ã§ã¯ã以äžã®ããã«ãªããŸãã"
#: ../../rst/inventory_guide/connection_details.rst:52
msgid ":ref:`ssh_connection`"
msgstr ":ref:`ssh_connection`"
#: ../../rst/inventory_guide/connection_details.rst:53
msgid "Details on the ``remote_user`` keyword and ``ansible_user`` variable."
msgstr "``remote_user`` ããŒã¯ãŒãããã³ ``ansible_user`` å€æ°ã®è©³çŽ°ã"
#: ../../rst/inventory_guide/connection_details.rst:54
msgid ":ref:`general_precedence_rules`"
msgstr ":ref:`general_precedence_rules`"
#: ../../rst/inventory_guide/connection_details.rst:55
msgid "Details on Ansible precedence rules."
msgstr "Ansible ã®åªå
床ã«ãŒã«ã®è©³çŽ°ã"
#: ../../rst/inventory_guide/connection_details.rst:58
msgid "Setting up SSH keys"
msgstr "SSH ããŒã®èšå®"
#: ../../rst/inventory_guide/connection_details.rst:60
msgid "By default, Ansible assumes you are using SSH keys to connect to remote machines. SSH keys are encouraged, but you can use password authentication if needed with the ``--ask-pass`` option. If you need to provide a password for :ref:`privilege escalation <become>` (sudo, pbrun, and so on), use ``--ask-become-pass``."
msgstr "ããã©ã«ãã§ã¯ãAnsible 㯠SSH éµã䜿çšããŠãªã¢ãŒããã·ã³ã«æ¥ç¶ããããšãæ³å®ããŠããŸããSSH ããŒãæšå¥šãããŸãããå¿
èŠã«å¿ã㊠``--ask-pass`` ãªãã·ã§ã³ã䜿çšããŠãã¹ã¯ãŒãèªèšŒã䜿çšã§ããŸãã:ref:`privilege escalation <become>` (sudoãpbrun ãªã©) ã®ãã¹ã¯ãŒããæäŸããå¿
èŠãããå Žåã¯ã``--ask-become-pass`` ã䜿çšããŸãã"
#: ../../rst/inventory_guide/shared_snippets/SSH_password_prompt.txt:2
msgid "Ansible does not expose a channel to allow communication between the user and the ssh process to accept a password manually to decrypt an ssh key when using the ssh connection plugin (which is the default). The use of ``ssh-agent`` is highly recommended."
msgstr "Ansible ã¯ãssh connection ãã©ã°ã€ã³ã䜿çšããŠããå Žå (ãããããã©ã«ãã§ã)ã¯ããŠãŒã¶ãŒãš ssh ããã»ã¹ã®éã®éä¿¡ãå¯èœã«ãããã£ã³ãã«ãå
¬éããŠããããssh éµã埩å·ããããã®ãã¹ã¯ãŒããæåã§åãå
¥ããããšãã§ããŸããã``ssh-agent`` ã䜿çšããããšã匷ãæšå¥šãããŸãã"
#: ../../rst/inventory_guide/connection_details.rst:64
msgid "To set up SSH agent to avoid retyping passwords, you can do:"
msgstr "ãã¹ã¯ãŒããåå
¥åããªãããã« SSH ãšãŒãžã§ã³ããã»ããã¢ããããã«ã¯ã次ã®ããã«ããŸãã"
#: ../../rst/inventory_guide/connection_details.rst:71
msgid "Depending on your setup, you may wish to use Ansible's ``--private-key`` command line option to specify a pem file instead. You can also add the private key file:"
msgstr "ã»ããã¢ããã«ãã£ãŠã¯ã代ããã« Ansible ã® ``--private-key`` ã³ãã³ãã©ã€ã³ãªãã·ã§ã³ã䜿çšã㊠pem ãã¡ã€ã«ãæå®ããããšãã§ããŸããç§å¯éµãã¡ã€ã«ãè¿œå ããããšãã§ããŸãã"
#: ../../rst/inventory_guide/connection_details.rst:78
msgid "Another way to add private key files without using ssh-agent is using ``ansible_ssh_private_key_file`` in an inventory file as explained here: :ref:`intro_inventory`."
msgstr "ssh-agent ã䜿çšããã«ç§å¯éµãã¡ã€ã«ãè¿œå ããå¥ã®æ¹æ³ã¯ãã:ref:`intro_inventory`ãã§èª¬æããããã«ãã€ã³ãã³ããªãŒãã¡ã€ã«ã§ ``ansible_ssh_private_key_file`` ã䜿çšããããšã§ãã"
#: ../../rst/inventory_guide/connection_details.rst:81
msgid "Running against localhost"
msgstr "ããŒã«ã«ãã¹ãã«å¯ŸããŠå®è¡"
#: ../../rst/inventory_guide/connection_details.rst:83
msgid "You can run commands against the control node by using \"localhost\" or \"127.0.0.1\" for the server name:"
msgstr "ãµãŒããŒåã«ãlocalhostããŸãã¯ã127.0.0.1ãã䜿çšããŠãã³ã³ãããŒã«ããŒãã«ã³ãã³ããå®è¡ã§ããŸãã"
#: ../../rst/inventory_guide/connection_details.rst:89
msgid "You can specify localhost explicitly by adding this to your inventory file:"
msgstr "ãããã€ã³ãã³ããªãŒãã¡ã€ã«ã«è¿œå ããŠãlocalhost ãæ瀺çã«æå®ã§ããŸãã"
#: ../../rst/inventory_guide/connection_details.rst:98
msgid "Managing host key checking"
msgstr "ãã¹ãéµã®ç¢ºèªã®ç®¡ç"
#: ../../rst/inventory_guide/connection_details.rst:100
msgid "Ansible enables host key checking by default. Checking host keys guards against server spoofing and man-in-the-middle attacks, but it does require some maintenance."
msgstr "Ansible ã¯ãããã©ã«ãã§ãã¹ãéµã®ç¢ºèªãæå¹ã«ããŸãããã¹ãéµã確èªãããšããµãŒããŒã®ãªãããŸããäžéè
æ»æããä¿è·ãããŸãããã¡ã³ããã³ã¹ãå¿
èŠã§ãã"
#: ../../rst/inventory_guide/connection_details.rst:102
msgid "If a host is reinstalled and has a different key in 'known_hosts', this will result in an error message until corrected. If a new host is not in 'known_hosts' your control node may prompt for confirmation of the key, which results in an interactive experience if using Ansible, from say, cron. You might not want this."
msgstr "ãã¹ããåã€ã³ã¹ããŒã«ããããknown_hostsãã«ç°ãªãããŒãããå Žåã¯ãä¿®æ£ããããŸã§ãšã©ãŒã¡ãã»ãŒãžã衚瀺ãããŸããæ°ãããã¹ãããknown_hostsãã«ãªãå Žåãã³ã³ãããŒã«ããŒãã¯ããŒã®ç¢ºèªãæ±ãããããããŸãããããã㯠Ansible ã cron ãªã©ãã䜿çšããŠããå Žåã¯ãã€ã³ã¿ã©ã¯ãã£ããªæäœã«ãªããŸãããã®ããã«åäœããªãããã«ãããå ŽåããããŸãã"
#: ../../rst/inventory_guide/connection_details.rst:104
msgid "If you understand the implications and wish to disable this behavior, you can do so by editing ``/etc/ansible/ansible.cfg`` or ``~/.ansible.cfg``:"
msgstr "ãã®åäœãç¡å¹ã«ããå Žåã®åœ±é¿ãç解ããç¡å¹ã«ããå Žåã¯ã``/etc/ansible/ansible.cfg`` ãŸã㯠``~/.ansible.cfg`` ç·šéããŸãã"
#: ../../rst/inventory_guide/connection_details.rst:111
msgid "Alternatively this can be set by the :envvar:`ANSIBLE_HOST_KEY_CHECKING` environment variable:"
msgstr "ãŸããããã¯ã:envvar:`ANSIBLE_HOST_KEY_CHECKING` ç°å¢å€æ°ã«ããèšå®ã§ããŸãã"
#: ../../rst/inventory_guide/connection_details.rst:117
msgid "Also note that host key checking in paramiko mode is reasonably slow, therefore switching to 'ssh' is also recommended when using this feature."
msgstr "ãŸããparamiko ã¢ãŒãã§ã®ãã¹ãããŒãã§ãã¯ã¯ããªãé
ãããããã®æ©èœã䜿çšããå Žåã¯ãsshãã«åãæ¿ããããšãæšå¥šãããŸãã"
#: ../../rst/inventory_guide/connection_details.rst:120
msgid "Other connection methods"
msgstr "ãã®ä»ã®æ¥ç¶æ¹æ³"
#: ../../rst/inventory_guide/connection_details.rst:122
msgid "Ansible can use a variety of connection methods beyond SSH. You can select any connection plugin, including managing things locally and managing chroot, lxc, and jail containers. A mode called 'ansible-pull' can also invert the system and have systems 'phone home' via scheduled git checkouts to pull configuration directives from a central repository."
msgstr "Ansible ã§ã¯ãSSH 以å€ã«ãããŸããŸãªæ¥ç¶æ¹æ³ãå©çšããããšãã§ããŸããããŒã«ã«ã§ã®ç®¡çãchroot ã³ã³ãããŒãlxc ã³ã³ãããŒãããã³ jail ã³ã³ãããŒã®ç®¡çãªã©ãä»»æã® connection ãã©ã°ã€ã³ãéžæã§ããŸãããansible-pullããšåŒã°ããã¢ãŒãã§ã¯ãã·ã¹ãã ãå転ãããŠãã¹ã±ãžã¥ãŒã«ããã git ãã§ãã¯ã¢ãŠããä»ããŠã·ã¹ãã ããphone homeããããäžå€®ã®ãªããžããªãŒããèšå®ãã£ã¬ã¯ãã£ããåŒãåºãããšãã§ããŸãã"
#: ../../rst/inventory_guide/index.rst:5
msgid "Building Ansible inventories"
msgstr "Ansible ã€ã³ãã³ããªãŒã®æ§ç¯"
#: ../../rst/inventory_guide/index.rst:9
msgid "**Making Open Source More Inclusive**"
msgstr "**å€æ§æ§ãåãå
¥ãããªãŒãã³ãœãŒã¹ã®åŒ·å**"
#: ../../rst/inventory_guide/index.rst:11
msgid "Red Hat is committed to replacing problematic language in our code, documentation, and web properties. We are beginning with these four terms: master, slave, blacklist, and whitelist. We ask that you open an issue or pull request if you come upon a term that we have missed. For more details, see `our CTO Chris Wright's message <https://www.redhat.com/en/blog/making-open-source-more-inclusive-eradicating-problematic-language>`_."
msgstr "Red Hat ã§ã¯ãã³ãŒããããã¥ã¡ã³ããWeb ããããã£ãŒã«ãããé
æ
®ã«æ¬ ããçšèªã®çœ®ãæãã«åãçµãã§ããŸãããŸãã¯ããã¹ã¿ãŒ (master)ãã¹ã¬ãŒã (slave)ããã©ãã¯ãªã¹ã (blacklist)ããã¯ã€ããªã¹ã (whitelist) ã® 4 ã€ã®çšèªã®çœ®ãæãããå§ããŸããåé¡ã®ããçšèªãèŠã€ããå Žåã¯ãåé¡ãäœæãããããã«èŠæ±ãäœæããŠãã ããã詳现ã¯ã`åŒç€Ÿ ã® CTOãChris Wright ã®ã¡ãã»ãŒãž <https://www.redhat.com/en/blog/making-open-source-more-inclusive-eradicating-problematic-language>`_ ãåç
§ããŠãã ããã"
#: ../../rst/inventory_guide/index.rst:13
msgid "Welcome to the guide to building Ansible inventories. An inventory is a list of managed nodes, or hosts, that Ansible deploys and configures. This guide introduces you to inventories and covers the following topics:"
msgstr "Ansible ã€ã³ãã³ããªãŒã®æ§ç¯ã¬ã€ããžãããããã€ã³ãã³ããªãŒã¯ãAnsible ããããã€ããã³èšå®ãã管ç察象ããŒããŸãã¯ãã¹ãã®ãªã¹ãã§ãããã®ã¬ã€ãã§ã¯ãã€ã³ãã³ããªãŒã ãã§ãªãã次ã®ãããã¯ã«ã€ããŠã説æããŸãã"
#: ../../rst/inventory_guide/index.rst:17
msgid "Creating inventories to track list of servers and devices that you want to automate."
msgstr "ã€ã³ãã³ããªãŒãäœæããŠãèªååãããµãŒããŒããã³ããã€ã¹ã®äžèŠ§ã远跡ããã"
#: ../../rst/inventory_guide/index.rst:18
msgid "Using dynamic inventories to track cloud services with servers and devices that are constantly starting and stopping."
msgstr "åçã€ã³ãã³ããªãŒã䜿çšããŠãåžžã«èµ·åãšåæ¢ãè¡ããµãŒããŒããã³ããã€ã¹ãå«ãŸããã¯ã©ãŠããµãŒãã¹ã远跡ããã"
#: ../../rst/inventory_guide/index.rst:19
msgid "Using patterns to automate specific sub-sets of an inventory."
msgstr "ãã¿ãŒã³ã䜿çšããŠãã€ã³ãã³ããªãŒã®ç¹å®ã®ãµãã»ãããèªååããã"
#: ../../rst/inventory_guide/index.rst:20
msgid "Expanding and refining the connection methods Ansible uses for your inventory."
msgstr "Ansible ãã€ã³ãã³ããªãŒã«äœ¿çšããæ¥ç¶æ¹æ³ãæ¡åŒµããŠèª¿æŽããã"
#: ../../rst/inventory_guide/intro_dynamic_inventory.rst:6
msgid "Working with dynamic inventory"
msgstr "åçã€ã³ãã³ããªãŒã®äœ¿çš"
#: ../../rst/inventory_guide/intro_dynamic_inventory.rst:11
msgid "If your Ansible inventory fluctuates over time, with hosts spinning up and shutting down in response to business demands, the static inventory solutions described in :ref:`inventory` will not serve your needs. You may need to track hosts from multiple sources: cloud providers, LDAP, `Cobbler <https://cobbler.github.io>`_, and/or enterprise CMDB systems."
msgstr "Ansible ã®ã€ã³ãã³ããªãŒããããžãã¹äžã®èŠæ±ã«å¿ããŠãã¹ãã®å転ãåæ¢ãªã©ãæéãšãšãã«å€åããå Žåã¯ãã:ref:`inventory`ãã§èª¬æããŠããéçãªã€ã³ãã³ããªãŒãœãªã¥ãŒã·ã§ã³ã§ã¯ããŒãºã«å¿ããããŸãããã¯ã©ãŠããããã€ããŒãLDAPã`Cobbler <https://cobbler.github.io>`_ããšã³ã¿ãŒãã©ã€ãº CMDB ã·ã¹ãã ãªã©ãè€æ°ã®ãœãŒã¹ããã®ãã¹ãã®è¿œè·¡ãå¿
èŠã«ãªãå ŽåããããŸãã"
#: ../../rst/inventory_guide/intro_dynamic_inventory.rst:14
msgid "Ansible integrates all of these options through a dynamic external inventory system. Ansible supports two ways to connect with external inventory: :ref:`inventory_plugins` and `inventory scripts`."
msgstr "Ansible ã¯ãåçãªå€éšã€ã³ãã³ããªãŒã·ã¹ãã ãéããŠããããã®ãªãã·ã§ã³ããã¹ãŠçµ±åããŸããAnsible ã¯ãå€éšã€ã³ãã³ããªãŒã«æ¥ç¶ãã 2 ã€ã®æ¹æ³ (:ref:`inventory_plugins` ããã³ `inventory scripts`) ããµããŒãããŠããŸãã"
#: ../../rst/inventory_guide/intro_dynamic_inventory.rst:17
msgid "Inventory plugins take advantage of the most recent updates to the Ansible core code. We recommend plugins over scripts for dynamic inventory. You can :ref:`write your own plugin <developing_inventory>` to connect to additional dynamic inventory sources."
msgstr "ã€ã³ãã³ããªãŒãã©ã°ã€ã³ã¯ãAnsible ã³ã¢ã³ãŒãã®ææ°ã®æŽæ°ãå©çšããŠããŸããåçã€ã³ãã³ããªãŒã«ã¯ãã¹ã¯ãªããããããã©ã°ã€ã³ãæšå¥šãããŸãã:ref:`ç¬èªã®ãã©ã°ã€ã³ãèšè¿° <developing_inventory>` ããŠãè¿œå ã®åçã€ã³ãã³ããªãŒãœãŒã¹ã«æ¥ç¶ããããšãã§ããŸãã"
#: ../../rst/inventory_guide/intro_dynamic_inventory.rst:21
msgid "You can still use inventory scripts if you choose. When we implemented inventory plugins, we ensured backwards compatibility through the script inventory plugin. The examples below illustrate how to use inventory scripts."
msgstr "ãŸããã€ã³ãã³ããªãŒã¹ã¯ãªããã䜿çšããããšãã§ããŸããã€ã³ãã³ããªãŒãã©ã°ã€ã³ãå®è£
ããéã«ãã¹ã¯ãªããã€ã³ãã³ããªãŒãã©ã°ã€ã³ã«ããåŸæ¹äºææ§ã確ä¿ããŸããã以äžã®äŸã§ã¯ãã€ã³ãã³ããªãŒã¹ã¯ãªããã®äœ¿çšæ¹æ³ã説æããŠããŸãã"
#: ../../rst/inventory_guide/intro_dynamic_inventory.rst:25
msgid "If you prefer a GUI for handling dynamic inventory, the inventory database on AWX or :ref:`ansible_platform` syncs with all your dynamic inventory sources, provides web and REST access to the results, and offers a graphical inventory editor. With a database record of all of your hosts, you can correlate past event history and see which hosts have had failures on their last playbook runs."
msgstr "åçã€ã³ãã³ããªãŒã GUI ã§æäœãããå Žåã¯ãAWX ãŸã㯠:ref:`ansible_platform` ã®ã€ã³ãã³ããªãŒããŒã¿ããŒã¹ããã¹ãŠã®åçã€ã³ãã³ããªãŒãœãŒã¹ãšåæãããã®çµæã« Web ããã³ REST ã¢ã¯ã»ã¹ãæäŸããã°ã©ãã£ã«ã«ã€ã³ãã³ããªãŒãšãã£ã¿ãŒãæäŸããŸãããã¹ãŠã®ãã¹ãã®ããŒã¿ããŒã¹ã¬ã³ãŒãã䜿çšããŠãéå»ã®ã€ãã³ãå±¥æŽãé¢é£ä»ããæåŸã® Playbook ã®å®è¡ã§ã©ã®ãã¹ãã«é害ãçºçãããã確èªã§ããŸãã"
#: ../../rst/inventory_guide/intro_dynamic_inventory.rst:31
msgid "Inventory script example: Cobbler"
msgstr "ã€ã³ãã³ããªãŒã¹ã¯ãªããã®äŸ: Cobbler"
#: ../../rst/inventory_guide/intro_dynamic_inventory.rst:33
msgid "Ansible integrates seamlessly with `Cobbler <https://cobbler.github.io>`_, a Linux installation server originally written by Michael DeHaan and now led by James Cammarata, who works for Ansible."
msgstr "Ansible ã¯ãLinux ã€ã³ã¹ããŒã«ãµãŒã㌠`Cobbler <https://cobbler.github.io>`_ (æåã« Michael DeHaan æ°ãäœæããçŸåšã¯ Ansible ã«æå±ãã James Cammarata ãçããŠããŸã) ãšã·ãŒã ã¬ã¹ã«çµ±åãããŸãã"
#: ../../rst/inventory_guide/intro_dynamic_inventory.rst:35
msgid "While primarily used to kickoff OS installations and manage DHCP and DNS, Cobbler has a generic layer that can represent data for multiple configuration management systems (even at the same time) and serve as a 'lightweight CMDB'."
msgstr "Cobbler ã¯äž»ã« OS ã®ã€ã³ã¹ããŒã«ãéå§ããDHCP ãš DNS ã管çããããã«äœ¿çšãããŸãããè€æ°ã®æ§æ管çã·ã¹ãã ã®ããŒã¿ã (åæã«ã§ã) è¡šçŸããã軜éCMDBããšããŠæ©èœããæ±çšã¬ã€ã€ãŒããããŸãã"
#: ../../rst/inventory_guide/intro_dynamic_inventory.rst:38
msgid "To tie your Ansible inventory to Cobbler, copy `this script <https://raw.githubusercontent.com/ansible-community/contrib-scripts/main/inventory/cobbler.py>`_ to ``/etc/ansible`` and ``chmod +x`` the file. Run ``cobblerd`` any time you use Ansible and use the ``-i`` command line option (for example, ``-i /etc/ansible/cobbler.py``) to communicate with Cobbler using Cobbler's XMLRPC API."
msgstr "Ansible ã€ã³ãã³ããªãŒã Cobbler ã«é¢é£ä»ããã«ã¯ã`ãã®ã¹ã¯ãªãã <https://raw.githubusercontent.com/ansible-community/contrib-scripts/main/inventory/cobbler.py>`_ ã ``/etc/ansible`` ã«ã³ããŒããŠãã³ããŒãããã¡ã€ã«ã« ``chmod +x`` ãä»äžããŸããAnsible ã䜿çšã㊠``cobblerd`` ãå®è¡ãã``-i`` ã³ãã³ãã©ã€ã³ãªãã·ã§ã³ (äŸ: ``-i /etc/ansible/cobbler.py``) ãä»ããŠãCobbler ã® XMLRPC API 䜿çšã㊠Cobbler ãšéä¿¡ããŸãã"
#: ../../rst/inventory_guide/intro_dynamic_inventory.rst:40
msgid "Add a ``cobbler.ini`` file in ``/etc/ansible`` so Ansible knows where the Cobbler server is and some cache improvements can be used. For example:"
msgstr "Ansible ã Cobbler ãµãŒããŒã®å Žæãšãã£ãã·ã¥ã®æ¹è¯ã«äœ¿çšã§ãããã®ãèªèã§ããããã«ã``/etc/ansible`` ã« ``cobbler.ini`` ãã¡ã€ã«ãè¿œå ããŸãã以äžã«äŸã瀺ããŸãã"
#: ../../rst/inventory_guide/intro_dynamic_inventory.rst:63
msgid "First test the script by running ``/etc/ansible/cobbler.py`` directly. You should see some JSON data output, but it may not have anything in it just yet."
msgstr "ãŸã ``/etc/ansible/cobbler.py`` ãçŽæ¥å®è¡ããŠã¹ã¯ãªããããã¹ãããŸããJSON ããŒã¿åºåã衚瀺ãããŸããããŸã äœãå«ãŸããŠããªãå ŽåããããŸãã"
#: ../../rst/inventory_guide/intro_dynamic_inventory.rst:65
msgid "Let's explore what this does. In Cobbler, assume a scenario somewhat like the following:"
msgstr "ããã§äœãã§ããã®ãèŠãŠã¿ãŸããããCobbler ã§ã次ã®ãããªã·ããªãªãæ³å®ããŸãã"
#: ../../rst/inventory_guide/intro_dynamic_inventory.rst:74
msgid "In the example above, the system 'foo.example.com' is addressable by ansible directly, but is also addressable when using the group names 'webserver' or 'atlanta'. Since Ansible uses SSH, it contacts system foo over 'foo.example.com', only, never just 'foo'. Similarly, if you tried \"ansible foo\", it would not find the system... but \"ansible 'foo*'\" would do, because the system DNS name starts with 'foo'."
msgstr "äžã®äŸã§ã¯ãã·ã¹ãã ãfoo.example.comãã¯ãansible ãçŽæ¥ã¢ãã¬ã¹ãæå®ã§ããã ãã§ãªããã°ã«ãŒãåãwebserverãããatlantaãã䜿çšããŠãã¢ãã¬ã¹ãæå®ã§ããŸããAnsible 㯠SSH ã䜿çšããŠããããããfoo.example.comããçµç±ããŠã·ã¹ãã foo ã«æ¥ç¶ããŸããã決ããŠãfooãã ãã§ã¯ãããŸãããåæ§ã«ããansible fooããšå
¥åããŠããã·ã¹ãã ãèŠã€ããããšã¯ã§ããŸãããããansible 'foo'*ããšå
¥åãããšãã·ã¹ãã ã® DNS åã 'foo' ã§å§ãŸããããã·ã¹ãã ãèŠã€ããããšãã§ããŸãã"
#: ../../rst/inventory_guide/intro_dynamic_inventory.rst:76
msgid "The script provides more than host and group info. In addition, as a bonus, when the 'setup' module is run (which happens automatically when using playbooks), the variables 'a', 'b', and 'c' will all be auto-populated in the templates:"
msgstr "ãã®ã¹ã¯ãªããã¯ããã¹ããšã°ã«ãŒãã®æ
å ±ä»¥å€ã«ãããŸããŸãªæ
å ±ãæäŸããŸããããã«ã(Playbook ã䜿çšããéã«èªåçã«å®è¡ããã)ãsetupãã¢ãžã¥ãŒã«ãå®è¡ãããšãå€æ°ãaãããbããããã³ãcãã¯ãã¹ãŠãã³ãã¬ãŒãã«èªåå
¥åãããããã«ãªããŸãã"
#: ../../rst/inventory_guide/intro_dynamic_inventory.rst:83
msgid "Which could be executed just like this:"
msgstr "ããã¯ä»¥äžã®ããã«å®è¡ã§ããŸãã"
#: ../../rst/inventory_guide/intro_dynamic_inventory.rst:91
msgid "The name 'webserver' came from Cobbler, as did the variables for the config file. You can still pass in your own variables like normal in Ansible, but variables from the external inventory script will override any that have the same name."
msgstr "ãwebserverããšããååã¯ãèšå®ãã¡ã€ã«ã®å€æ°ãšåæ§ã«ãCobbler ããæ¥ãŠããŸããAnsible ã§ã¯éåžžã®ããã«ç¬èªã®å€æ°ãæž¡ãããšãã§ããŸãããå€éšã®ã€ã³ãã³ããªãŒã¹ã¯ãªããããã®å€æ°ã¯ãåãååã®ãã®ãäžæžãããŸãã"
#: ../../rst/inventory_guide/intro_dynamic_inventory.rst:96
msgid "So, with the template above (``motd.j2``), this results in the following data being written to ``/etc/motd`` for system 'foo':"
msgstr "ãã®ãããäžèšã®ãã³ãã¬ãŒã (``motd.j2``) ã䜿çšãããšã以äžã®ããŒã¿ãã·ã¹ãã ãfooãçšã« ``/etc/motd`` ã«æžã蟌ãŸããŸãã"
#: ../../rst/inventory_guide/intro_dynamic_inventory.rst:102
msgid "And on system 'bar' (bar.example.com):"
msgstr "ã·ã¹ãã ãbarã(bar.example.com) ã¯ã以äžã®ããã«ãªããŸãã"
#: ../../rst/inventory_guide/intro_dynamic_inventory.rst:108
msgid "And technically, though there is no major good reason to do it, this also works:"
msgstr "æè¡çã«ã¯ããããè¡ã倧ããªæ£åœãªçç±ã¯ãããŸãããããããæ©èœããŸãã"
#: ../../rst/inventory_guide/intro_dynamic_inventory.rst:114
msgid "So, in other words, you can use those variables in arguments/actions as well."
msgstr "ã€ãŸããåŒæ°ãã¢ã¯ã·ã§ã³ã§ãã®å€æ°ã䜿çšããããšãã§ããŸãã"
#: ../../rst/inventory_guide/intro_dynamic_inventory.rst:119
msgid "Inventory script example: OpenStack"
msgstr "ã€ã³ãã³ããªãŒã¹ã¯ãªããã®äŸ: OpenStack"
#: ../../rst/inventory_guide/intro_dynamic_inventory.rst:121
msgid "If you use an OpenStack-based cloud, instead of manually maintaining your own inventory file, you can use the ``openstack_inventory.py`` dynamic inventory to pull information about your compute instances directly from OpenStack."
msgstr "ç¬èªã®ã€ã³ãã³ããªãŒãã¡ã€ã«ãæåã§ç®¡çãã代ããã«ãOpenStack ããŒã¹ã®ã¯ã©ãŠãã䜿çšããå Žåã¯ãåçã€ã³ãã³ããªãŒ ``openstack_inventory.py`` ã䜿çšããŠãOpenStack ããçŽæ¥ Compute ã€ã³ã¹ã¿ã³ã¹ã«é¢ããæ
å ±ãååŸã§ããŸãã"
#: ../../rst/inventory_guide/intro_dynamic_inventory.rst:123
msgid "You can download the latest version of the OpenStack inventory script `here <https://raw.githubusercontent.com/openstack/ansible-collections-openstack/master/scripts/inventory/openstack_inventory.py>`_."
msgstr "ææ°ããŒãžã§ã³ã® OpenStack ã€ã³ãã³ããªãŒã¹ã¯ãªããã¯ã`ãã¡ã <https://raw.githubusercontent.com/openstack/ansible-collections-openstack/master/scripts/inventory/openstack_inventory.py>`_ ããããŠã³ããŒãã§ããŸãã"
#: ../../rst/inventory_guide/intro_dynamic_inventory.rst:125
msgid "You can use the inventory script explicitly (by passing the `-i openstack_inventory.py` argument to Ansible) or implicitly (by placing the script at `/etc/ansible/hosts`)."
msgstr "(`-i openstack_inventory.py` åŒæ°ã Ansible ã«æž¡ãããšã§) ã€ã³ãã³ããªãŒã¹ã¯ãªãããæ瀺çã«äœ¿çšãããã(ã¹ã¯ãªããã `/etc/ansible/hosts` ã«ãããŠ) æé»çã«äœ¿çšã§ããŸãã"
#: ../../rst/inventory_guide/intro_dynamic_inventory.rst:128
msgid "Explicit use of OpenStack inventory script"
msgstr "OpenStack ã€ã³ãã³ããªãŒã¹ã¯ãªããã®æ瀺çãªäœ¿çš"
#: ../../rst/inventory_guide/intro_dynamic_inventory.rst:130
msgid "Download the latest version of the OpenStack dynamic inventory script and make it executable."
msgstr "ææ°ããŒãžã§ã³ã® OpenStack ã®åçã€ã³ãã³ããªãŒã¹ã¯ãªãããããŠã³ããŒãããå®è¡å¯èœã«ããŸãã"
#: ../../rst/inventory_guide/intro_dynamic_inventory.rst:138
msgid "Do not name it `openstack.py`. This name will conflict with imports from openstacksdk."
msgstr "`openstack.py` ãšããååã¯ã€ããªãã§ãã ããããã®ååã¯ãopenstacksdk ããã®ã€ã³ããŒããšç«¶åããŸãã"
#: ../../rst/inventory_guide/intro_dynamic_inventory.rst:140
msgid "Source an OpenStack RC file:"
msgstr "OpenStack RC ãã¡ã€ã«ãèªã¿èŸŒã¿ãŸãã"
#: ../../rst/inventory_guide/intro_dynamic_inventory.rst:148
msgid "An OpenStack RC file contains the environment variables required by the client tools to establish a connection with the cloud provider, such as the authentication URL, user name, password and region name. For more information on how to download, create or source an OpenStack RC file, please refer to `Set environment variables using the OpenStack RC file <https://docs.openstack.org/user-guide/common/cli_set_environment_variables_using_openstack_rc.html>`_."
msgstr "OpenStack RC ãã¡ã€ã«ã«ã¯ãèªèšŒ URLããŠãŒã¶ãŒåããã¹ã¯ãŒãããªãŒãžã§ã³åãªã©ãã¯ã©ãŠããããã€ããŒãšã®æ¥ç¶ã確ç«ããããã«ã¯ã©ã€ã¢ã³ãããŒã«ã§å¿
èŠãªç°å¢å€æ°ãå«ãŸããŠããŸããOpenStack RC ãã¡ã€ã«ã®ããŠã³ããŒããäœæããŸãã¯ãœãŒã¹ã«é¢ãã詳现ã¯ãã`Set environment variables using the OpenStack RC file <https://docs.openstack.org/user-guide/common/cli_set_environment_variables_using_openstack_rc.html>`_ããåç
§ããŠãã ããã"
#: ../../rst/inventory_guide/intro_dynamic_inventory.rst:150
msgid "You can confirm the file has been successfully sourced by running a simple command, such as `nova list` and ensuring it returns no errors."
msgstr "`nova list` ãªã©ã®åçŽãªã³ãã³ããå®è¡ããŠãšã©ãŒãè¿ããªãããã«ããããšã§ããã¡ã€ã«ãæ£åžžã«èªã¿èŸŒãŸããããšã確èªã§ããŸãã"
#: ../../rst/inventory_guide/intro_dynamic_inventory.rst:154
msgid "The OpenStack command line clients are required to run the `nova list` command. For more information on how to install them, please refer to `Install the OpenStack command-line clients <https://docs.openstack.org/user-guide/common/cli_install_openstack_command_line_clients.html>`_."
msgstr "`nova list` ã³ãã³ããå®è¡ããã«ã¯ãOpenStack ã³ãã³ãã©ã€ã³ã¯ã©ã€ã¢ã³ããå¿
èŠã§ããã€ã³ã¹ããŒã«æ¹æ³ã®è©³çŽ°ã¯ãã`Install the OpenStack command-line clients <https://docs.openstack.org/user-guide/common/cli_install_openstack_command_line_clients.html>`_ããåç
§ããŠãã ããã"
#: ../../rst/inventory_guide/intro_dynamic_inventory.rst:156
#: ../../rst/inventory_guide/intro_dynamic_inventory.rst:189
msgid "You can test the OpenStack dynamic inventory script manually to confirm it is working as expected:"
msgstr "OpenStack åçã€ã³ãã³ããªãŒã¹ã¯ãªãããæåã§ãã¹ãããŠãæ³å®ã©ããã«æ©èœããŠããããšã確èªããŸãã"
#: ../../rst/inventory_guide/intro_dynamic_inventory.rst:162
#: ../../rst/inventory_guide/intro_dynamic_inventory.rst:195
msgid "After a few moments you should see some JSON output with information about your compute instances."
msgstr "ãã°ãããããšãCompute ã€ã³ã¹ã¿ã³ã¹ã«é¢ããæ
å ±ãå«ãŸãã JSON åºåã衚瀺ãããŸãã"
#: ../../rst/inventory_guide/intro_dynamic_inventory.rst:164
msgid "Once you confirm the dynamic inventory script is working as expected, you can tell Ansible to use the `openstack_inventory.py` script as an inventory file, as illustrated below:"
msgstr "åçã€ã³ãã³ããªãŒã¹ã¯ãªãããæ³å®ã©ããã«æ©èœããŠããããšã確èªãããã以äžã®ããã« Ansible ã `openstack_inventory.py` ã¹ã¯ãªãããã€ã³ãã³ããªãŒãã¡ã€ã«ãšããŠäœ¿çšããããã«æå®ããŸãã"
#: ../../rst/inventory_guide/intro_dynamic_inventory.rst:171
msgid "Implicit use of OpenStack inventory script"
msgstr "OpenStack ã€ã³ãã³ããªãŒã¹ã¯ãªããã®æé»çãªäœ¿çš"
#: ../../rst/inventory_guide/intro_dynamic_inventory.rst:173
msgid "Download the latest version of the OpenStack dynamic inventory script, make it executable and copy it to `/etc/ansible/hosts`:"
msgstr "ææ°ããŒãžã§ã³ã® OpenStack åçã€ã³ãã³ããªãŒã¹ã¯ãªãããããŠã³ããŒãããå®è¡å¯èœã«ããããã `/etc/ansible/hosts` ã«ã³ããŒããŸãã"
#: ../../rst/inventory_guide/intro_dynamic_inventory.rst:181
msgid "Download the sample configuration file, modify it to suit your needs and copy it to `/etc/ansible/openstack.yml`:"
msgstr "ãµã³ãã«èšå®ãã¡ã€ã«ãããŠã³ããŒãããå¿
èŠã«å¿ããŠå€æŽããããã `/etc/ansible/openstack.yml` ã«ã³ããŒããŸãã"
#: ../../rst/inventory_guide/intro_dynamic_inventory.rst:198
msgid "Refreshing the cache"
msgstr "ãã£ãã·ã¥ã®æŽæ°"
#: ../../rst/inventory_guide/intro_dynamic_inventory.rst:200
msgid "Note that the OpenStack dynamic inventory script will cache results to avoid repeated API calls. To explicitly clear the cache, you can run the openstack_inventory.py (or hosts) script with the ``--refresh`` parameter:"
msgstr "OpenStack åçã€ã³ãã³ããªãŒã¹ã¯ãªããã¯ãAPI åŒã³åºããç¹°ãè¿ãè¡ãããã®ãé²ãããã«ãçµæããã£ãã·ã¥ããããšã«æ³šæããŠãã ããããã£ãã·ã¥ãæ瀺çã«æ¶å»ããã«ã¯ã``--refresh`` ãã©ã¡ãŒã¿ãŒã䜿çšã㊠openstack_inventory.py (ãŸã㯠hosts) ã¹ã¯ãªãããå®è¡ããŸãã"
#: ../../rst/inventory_guide/intro_dynamic_inventory.rst:209
msgid "Other inventory scripts"
msgstr "ãã®ä»ã®ã€ã³ãã³ããªãŒã¹ã¯ãªãã"
#: ../../rst/inventory_guide/intro_dynamic_inventory.rst:211
msgid "In Ansible 2.10 and later, inventory scripts moved to their associated collections. Many are now in the `ansible-community/contrib-scripts repository <https://github.com/ansible-community/contrib-scripts/tree/main/inventory>`_. We recommend you use :ref:`inventory_plugins` instead."
msgstr "Ansible 2.10 以éã§ã¯ãã€ã³ãã³ããªãŒã¹ã¯ãªããã¯é¢é£ããã³ã¬ã¯ã·ã§ã³ã«ç§»åããŸãããçŸåšãå€ãã®ã¹ã¯ãªãã㯠`ansible-community/contrib-scripts repository <https://github.com/ansible-community/contrib-scripts/tree/main/inventory>`_ ã«ãããŸãã代ããã« :ref:`inventory_plugins` ã䜿çšããããšãæšå¥šãããŸãã"
#: ../../rst/inventory_guide/intro_dynamic_inventory.rst:216
msgid "Using inventory directories and multiple inventory sources"
msgstr "ã€ã³ãã³ããªãŒãã£ã¬ã¯ããªãŒããã³è€æ°ã®ã€ã³ãã³ããªãŒãœãŒã¹ã®äœ¿çš"
#: ../../rst/inventory_guide/intro_dynamic_inventory.rst:218
msgid "If the location given to ``-i`` in Ansible is a directory (or as so configured in ``ansible.cfg``), Ansible can use multiple inventory sources at the same time. When doing so, it is possible to mix both dynamic and statically managed inventory sources in the same ansible run. Instant hybrid cloud!"
msgstr "Ansible 㧠``-i`` ã«æå®ãããå Žæããã£ã¬ã¯ããªãŒã®å Žå (ãŸã㯠``ansible.cfg`` ã§ãã®ããã«èšå®ãããŠããå Žå)ãAnsible ã¯è€æ°ã®ã€ã³ãã³ããªãŒãœãŒã¹ãåæã«äœ¿çšã§ããŸãããããå®è¡ããå Žåã¯ãåã Ansible å®è¡ã§åçããã³éçã«ç®¡çãããŠããã€ã³ãã³ããªãŒãœãŒã¹ãæ··åšãããããšãã§ããŸãã"
#: ../../rst/inventory_guide/intro_dynamic_inventory.rst:222
msgid "In an inventory directory, executable files are treated as dynamic inventory sources and most other files as static sources. Files which end with any of the following are ignored:"
msgstr "ã€ã³ãã³ããªãŒãã£ã¬ã¯ããªã§ã¯ãå®è¡ãã¡ã€ã«ã¯åçã€ã³ãã³ããªãŒãœãŒã¹ãšããŠããã®ä»ã®ã»ãšãã©ã®ãã¡ã€ã«ã¯éçãœãŒã¹ãšããŠæ±ãããŸãã以äžã®ããããã§çµãããã¡ã€ã«ã¯ç¡èŠãããŸãã"
#: ../../rst/inventory_guide/intro_dynamic_inventory.rst:228
msgid "You can replace this list with your own selection by configuring an ``inventory_ignore_extensions`` list in ``ansible.cfg``, or setting the :envvar:`ANSIBLE_INVENTORY_IGNORE` environment variable. The value in either case must be a comma-separated list of patterns, as shown above."
msgstr "ãã®äžèŠ§ã¯ã``ansible.cfg`` 㧠``inventory_ignore_extensions`` äžèŠ§ãèšå®ãããã:envvar:`ANSIBLE_INVENTORY_IGNORE` ç°å¢å€æ°ãèšå®ããŠç¬èªã®éžæã«çœ®ãæããããšãã§ããŸãããããã®å€ããäžèšã®ããã«ãã¿ãŒã³ã®ã³ã³ãåºåãã®äžèŠ§ã§ããå¿
èŠããããŸãã"
#: ../../rst/inventory_guide/intro_dynamic_inventory.rst:230
msgid "Any ``group_vars`` and ``host_vars`` subdirectories in an inventory directory are interpreted as expected, making inventory directories a powerful way to organize different sets of configurations. See :ref:`using_multiple_inventory_sources` for more information."
msgstr "ã€ã³ãã³ããªãŒãã£ã¬ã¯ããªãŒã® ``group_vars`` ãµããã£ã¬ã¯ããªãŒããã³ ``host_vars`` ãµããã£ã¬ã¯ããªãŒã¯æ³å®ã©ããã«è§£éããããããã€ã³ãã³ããªãŒãã£ã¬ã¯ããªãŒã¯ããŸããŸãªæ§æã»ãããæŽçããããã®åŒ·åãªæ¹æ³ã«ãªããŸãã詳现ã¯ãã:ref:`using_multiple_inventory_sources`ããåç
§ããŠãã ããã"
#: ../../rst/inventory_guide/intro_dynamic_inventory.rst:235
msgid "Static groups of dynamic groups"
msgstr "åçã°ã«ãŒãã®éçã°ã«ãŒã"
#: ../../rst/inventory_guide/intro_dynamic_inventory.rst:237
msgid "When defining groups of groups in the static inventory file, the child groups must also be defined in the static inventory file, otherwise ansible returns an error. If you want to define a static group of dynamic child groups, define the dynamic groups as empty in the static inventory file. For example:"
msgstr "éçã€ã³ãã³ããªãŒãã¡ã€ã«ã§ã°ã«ãŒãã®ã°ã«ãŒããå®çŸ©ããå Žåã¯ãåã°ã«ãŒããéçã€ã³ãã³ããªãŒãã¡ã€ã«ã§å®çŸ©ãããŠããªããã°ãAnsible ã¯ãšã©ãŒãè¿ããŸããåçãªåã°ã«ãŒãã®éçã°ã«ãŒããå®çŸ©ããå Žåã¯ãéçã€ã³ãã³ããªãŒãã¡ã€ã«ã§åçã°ã«ãŒãã空ã«å®çŸ©ããŠãã ããã以äžã«äŸã瀺ããŸãã"
#: ../../rst/inventory_guide/intro_dynamic_inventory.rst:255
msgid ":ref:`intro_inventory`"
msgstr ":ref:`intro_inventory`"
#: ../../rst/inventory_guide/intro_dynamic_inventory.rst:256
msgid "All about static inventory files"
msgstr "éçã€ã³ãã³ããªãŒãã¡ã€ã«ã®è©³çŽ°"
#: ../../rst/inventory_guide/intro_dynamic_inventory.rst:257
#: ../../rst/inventory_guide/intro_inventory.rst:838
#: ../../rst/inventory_guide/intro_patterns.rst:250
msgid "`Mailing List <https://groups.google.com/group/ansible-project>`_"
msgstr "`Mailing List <https://groups.google.com/group/ansible-project>`_"
#: ../../rst/inventory_guide/intro_dynamic_inventory.rst:258
#: ../../rst/inventory_guide/intro_inventory.rst:839
#: ../../rst/inventory_guide/intro_patterns.rst:251
msgid "Questions? Help? Ideas? Stop by the list on Google Groups"
msgstr "ã質åã¯ããããŸããããµããŒããå¿
èŠã§ããããææ¡ã¯ããããŸãããGoogle ã°ã«ãŒãã®äžèŠ§ãã芧ãã ããã"
#: ../../rst/inventory_guide/intro_dynamic_inventory.rst:259
#: ../../rst/inventory_guide/intro_inventory.rst:840
#: ../../rst/inventory_guide/intro_patterns.rst:252
msgid ":ref:`communication_irc`"
msgstr ":ref:`communication_irc`"
#: ../../rst/inventory_guide/intro_dynamic_inventory.rst:260
#: ../../rst/inventory_guide/intro_inventory.rst:841
#: ../../rst/inventory_guide/intro_patterns.rst:253
msgid "How to join Ansible chat channels"
msgstr "Ansible ãã£ãããã£ã³ãã«ãžã®åå æ¹æ³"
#: ../../rst/inventory_guide/intro_inventory.rst:6
msgid "How to build your inventory"
msgstr "ã€ã³ãã³ããªãŒã®æ§ç¯æ¹æ³"
#: ../../rst/inventory_guide/intro_inventory.rst:8
msgid "Ansible automates tasks on managed nodes or \"hosts\" in your infrastructure, using a list or group of lists known as inventory. You can pass host names at the command line, but most Ansible users create inventory files. Your inventory defines the managed nodes you automate, with groups so you can run automation tasks on multiple hosts at the same time. Once your inventory is defined, you use :ref:`patterns <intro_patterns>` to select the hosts or groups you want Ansible to run against."
msgstr "Ansible ã¯ãã€ã³ãã³ããªãŒãšåŒã°ãããªã¹ããŸãã¯ãªã¹ãã®ã°ã«ãŒãã䜿çšããŠãã€ã³ãã©ã¹ãã©ã¯ãã£ãŒå
ã®ç®¡ç察象ããŒããŸãã¯ãã¹ãã§ã®ã¿ã¹ã¯ãèªååããŸããã³ãã³ãã©ã€ã³ã§ãã¹ãåãæž¡ãããšãã§ããŸãããã»ãšãã©ã® Ansible ãŠãŒã¶ãŒã¯ã€ã³ãã³ããªãŒãã¡ã€ã«ãäœæããŸããã€ã³ãã³ããªãŒã¯ãèªååãã管ç察象ããŒããã°ã«ãŒãã§å®çŸ©ãããããè€æ°ã®ãã¹ãã§åæã«èªååã¿ã¹ã¯ãå®è¡ã§ããŸããã€ã³ãã³ããªãŒãå®çŸ©ããããã:ref:`patterns <intro_patterns>` ã䜿çšããŠãAnsible ãå®è¡ãããã¹ããŸãã¯ã°ã«ãŒããéžæããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:11
msgid "The simplest inventory is a single file with a list of hosts and groups. The default location for this file is ``/etc/ansible/hosts``. You can specify a different inventory file at the command line using the ``-i <path>`` option or in configuration using ``inventory``."
msgstr "æãåçŽãªã€ã³ãã³ããªãŒã¯ããã¹ããšã°ã«ãŒãã®äžèŠ§ãå«ãŸããåäžãã¡ã€ã«ã§ãããã®ãã¡ã€ã«ã®ããã©ã«ãã®å Žæ㯠``/etc/ansible/hosts`` ã§ãã``-i <path>`` ãªãã·ã§ã³ã䜿çšãããã``inventory`` ã䜿çšããŠèšå®ã§å¥ã®ã€ã³ãã³ããªãŒãã¡ã€ã«ãæå®ã§ããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:14
msgid "Ansible :ref:`inventory_plugins` support a range of formats and sources to make your inventory flexible and customizable. As your inventory expands, you may need more than a single file to organize your hosts and groups. Here are three options beyond the ``/etc/ansible/hosts`` file: - You can create a directory with multiple inventory files. See :ref:`inventory_directory`. These can use different formats (YAML, ini, and so on). - You can pull inventory dynamically. For example, you can use a dynamic inventory plugin to list resources in one or more cloud providers. See :ref:`intro_dynamic_inventory`. - You can use multiple sources for inventory, including both dynamic inventory and static files. See :ref:`using_multiple_inventory_sources`."
msgstr "Ansible :ref:`inventory_plugins` ã¯ãã€ã³ãã³ããªãŒãæè»ãã€ã«ã¹ã¿ãã€ãºå¯èœãªãã®ã«ããããã®ããŸããŸãªåœ¢åŒããã³ãœãŒã¹ããµããŒãããŸããã€ã³ãã³ããªãŒãæ¡åŒµããããããã¹ããšã°ã«ãŒããæŽçããããã«ã1 ã€ä»¥äžã®ãã¡ã€ã«ãå¿
èŠã«ãªãå ŽåããããŸãã ``/etc/ansible/hosts`` ãã¡ã€ã«ä»¥å€ã« 3 ã€ã®ãªãã·ã§ã³ããããŸãã- è€æ°ã®ã€ã³ãã³ããªãŒãã¡ã€ã«ãå«ããã£ã¬ã¯ããªãŒãäœæã§ããŸãã:ref:`inventory_directory` ãåç
§ããŠãã ããããããã¯å¥ã®åœ¢åŒ (YAMLãini ãªã©) ã䜿çšã§ããŸããã€ã³ãã³ããªãŒã¯åçã«ãã«ã§ããŸããããšãã°ãåçã€ã³ãã³ããªãŒãã©ã°ã€ã³ã䜿çšããŠã1 ã€ä»¥äžã®ã¯ã©ãŠããããã€ããŒã®ãªãœãŒã¹ãäžèŠ§è¡šç€ºã§ããŸãã:ref:`intro_dynamic_inventory` ãåç
§ããŠãã ããã - åçã€ã³ãã³ããªãŒãšéçãã¡ã€ã«ã®äž¡æ¹ãå«ããã€ã³ãã³ããªãŒã®è€æ°ãœãŒã¹ã䜿çšã§ããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:25
msgid "Inventory basics: formats, hosts, and groups"
msgstr "ã€ã³ãã³ããªãŒã®åºæ¬: 圢åŒããã¹ããããã³ã°ã«ãŒã"
#: ../../rst/inventory_guide/intro_inventory.rst:27
msgid "You can create your inventory file in one of many formats, depending on the inventory plugins you have. The most common formats are INI and YAML. A basic INI ``/etc/ansible/hosts`` might look like this:"
msgstr "ã€ã³ãã³ããªãŒãã¡ã€ã«ã¯ãææããã€ã³ãã³ããªãŒãã©ã°ã€ã³ã«å¿ããŠãå€æ°ãã圢åŒã®äžãã 1 ã€éžæããŠäœæã§ããŸããæãäžè¬çãªåœ¢åŒã¯ INI ããã³ YAML ã§ããåºæ¬ç㪠INI ``/etc/ansible/hosts`` ã¯ä»¥äžã®ããã«ãªããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:43
msgid "The headings in brackets are group names, which are used in classifying hosts and deciding what hosts you are controlling at what times and for what purpose. Group names should follow the same guidelines as :ref:`valid_variable_names`."
msgstr "æ¬åŒ§å
ã®èŠåºãã¯ã°ã«ãŒãåã§ããã¹ããåé¡ããã©ã®æç¹ã§ãã©ã®ãããªç®çã§ãã©ã®ãã¹ããå¶åŸ¡ãããã決å®ããã®ã«äœ¿çšãããŸããã°ã«ãŒãåã¯ã:ref:`valid_variable_names` ãšåãã¬ã€ãã©ã€ã³ã«åŸã£ãŠãã ããã"
#: ../../rst/inventory_guide/intro_inventory.rst:47
msgid "Here's that same basic inventory file in YAML format:"
msgstr "以äžã¯ãåãåºæ¬çãªã€ã³ãã³ããªãŒãã¡ã€ã«ã® YAML 圢åŒã§ãã"
#: ../../rst/inventory_guide/intro_inventory.rst:68
msgid "Default groups"
msgstr "ããã©ã«ãã®ã°ã«ãŒã"
#: ../../rst/inventory_guide/intro_inventory.rst:70
msgid "Even if you do not define any groups in your inventory file, Ansible creates two default groups: ``all`` and ``ungrouped``. The ``all`` group contains every host. The ``ungrouped`` group contains all hosts that don't have another group aside from ``all``. Every host will always belong to at least 2 groups (``all`` and ``ungrouped`` or ``all`` and some other group). For example, in the basic inventory above, the host ``mail.example.com`` belongs to the ``all`` group and the ``ungrouped`` group; the host ``two.example.com`` belongs to the ``all`` group and the ``dbservers`` group. Though ``all`` and ``ungrouped`` are always present, they can be implicit and not appear in group listings like ``group_names``."
msgstr "ã€ã³ãã³ããªãŒãã¡ã€ã«ã§ã°ã«ãŒããäœãæå®ããªãå Žåã§ããAnsible 㯠``all`` ãš ``ungrouped`` ã®ããã©ã«ãã®ã°ã«ãŒããäœæããŸãã``all`` ã°ã«ãŒãã«ã¯å
šãã¹ããå«ãŸããŸãã``ungrouped`` ã°ã«ãŒãã«ã¯ã``all`` 以å€ã®å¥ã®ã°ã«ãŒããæããªããã¹ããã¹ãŠãå«ãŸããŸããå
šãã¹ãã¯åžžã«æäœã§ã 2 ã€ã®ã°ã«ãŒã (``all`` ããã³ ``ungrouped`` ãŸã㯠``all`` ãšä»ã®ã°ã«ãŒã) ã«æå±ããŸããããšãã°ãäžèšã®åºæ¬çãªã€ã³ãã³ããªãŒã§ã¯ã``mail.example.com`` ãã¹ã㯠``all`` ã°ã«ãŒããš ``ungrouped`` ã°ã«ãŒãã«æå±ãã``two.example.com`` ãã¹ã㯠``all`` ã°ã«ãŒããš ``dbservers`` ã°ã«ãŒãã«æå±ããŸãã``all`` ãš ``ungrouped`` ã¯åžžã«ååšããŸãããæé»çãªå Žåãããã``group_names`` ãªã©ã®ã°ã«ãŒããªã¹ãã«è¡šç€ºãããªãå ŽåããããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:77
msgid "Hosts in multiple groups"
msgstr "è€æ°ã°ã«ãŒãå
ã®ãã¹ã"
#: ../../rst/inventory_guide/intro_inventory.rst:79
msgid "You can (and probably will) put each host in more than one group. For example a production webserver in a datacenter in Atlanta might be included in groups called ``[prod]`` and ``[atlanta]`` and ``[webservers]``. You can create groups that track:"
msgstr "åãã¹ããè€æ°ã®ã°ã«ãŒãã«é
眮ã§ããŸããããšãã°ãAtlanta ã®ããŒã¿ã»ã³ã¿ãŒã®å®çšŒå Web ãµãŒããŒã¯ã``[prod]``ã``[atlanta]`` ããã³ ``[webservers]`` ãšåŒã°ããã°ã«ãŒãã«è¿œå ã§ããŸãã以äžã远跡ããã°ã«ãŒããäœæã§ããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:81
msgid "What - An application, stack or microservice (for example, database servers, web servers, and so on)."
msgstr "ãªã«ã - ã¢ããªã±ãŒã·ã§ã³ãã¹ã¿ãã¯ããŸãã¯ãã€ã¯ããµãŒãã¹ (ããšãã°ãããŒã¿ããŒã¹ãµãŒããŒãWeb ãµãŒããŒãªã©)ã"
#: ../../rst/inventory_guide/intro_inventory.rst:82
msgid "Where - A datacenter or region, to talk to local DNS, storage, and so on (for example, east, west)."
msgstr "ã©ã㧠- ããŒã¿ã»ã³ã¿ãŒãŸãã¯ãªãŒãžã§ã³ã§ãããŒã«ã«ã® DNS ãã¹ãã¬ãŒãžãªã©ãšéä¿¡ããŸã (äŸ: eastãwest)ã"
#: ../../rst/inventory_guide/intro_inventory.rst:83
msgid "When - The development stage, to avoid testing on production resources (for example, prod, test)."
msgstr "ã〠- éçºæ®µéã§ãå®çšŒåãªãœãŒã¹ã§ã®ãã¹ããåé¿ãããã (äŸ: prodãtest)ã"
#: ../../rst/inventory_guide/intro_inventory.rst:85
msgid "Extending the previous YAML inventory to include what, when, and where would look like this:"
msgstr "以åã® YAML ã€ã³ãã³ããªãŒãæ¡åŒµããŠãäžè¿°ã®ããã€ãã©ãã§ããªã«ãããå«ãŸããããã«ããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:121
msgid "You can see that ``one.example.com`` exists in the ``dbservers``, ``east``, and ``prod`` groups."
msgstr "``one.example.com`` ã ``dbservers``ã``east``ãããã³ ``prod`` ã°ã«ãŒãã«ååšããããšã確èªã§ããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:126
msgid "Grouping groups: parent/child group relationships"
msgstr "ã°ã«ãŒãã®åé¡: 芪åã°ã«ãŒãã®é¢ä¿"
#: ../../rst/inventory_guide/intro_inventory.rst:128
msgid "You can create parent/child relationships among groups. Parent groups are also known as nested groups or groups of groups. For example, if all your production hosts are already in groups such as ``atlanta_prod`` and ``denver_prod``, you can create a ``production`` group that includes those smaller groups. This approach reduces maintenance because you can add or remove hosts from the parent group by editing the child groups."
msgstr "ã°ã«ãŒãéã§èŠª/åé¢ä¿ãäœæã§ããŸãã芪ã°ã«ãŒãã¯ããã¹ããããã°ã«ãŒããŸãã¯ã°ã«ãŒãã®ã°ã«ãŒããšãåŒã°ããŸããããšãã°ããã¹ãŠã®å®çšŒåãã¹ãã ``atlanta_prod`` ã ``denver_prod`` ãªã©ã®ã°ã«ãŒãã«ãã§ã«ããå Žåã¯ããããã®å°èŠæš¡ãªã°ã«ãŒããå«ã ``production`` ã°ã«ãŒããäœæã§ããŸãããã®æ¹æ³ã§ã¯ãåã°ã«ãŒããç·šéããŠèŠªã°ã«ãŒããããã¹ããè¿œå ãŸãã¯åé€ã§ãããããã¡ã³ããã³ã¹ã軜æžãããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:130
msgid "To create parent/child relationships for groups:"
msgstr "ã°ã«ãŒãã®èŠªåé¢ä¿ãäœæããã«ã¯ä»¥äžãå®è¡ããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:132
msgid "in INI format, use the ``:children`` suffix"
msgstr "INI 圢åŒã®å Žåã¯ã``:children`` æ¥å°ŸèŸã䜿çšããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:133
msgid "in YAML format, use the ``children:`` entry"
msgstr "YAML 圢åŒã®å Žåã¯ã``children:``ãšã³ããªãŒã䜿çšããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:135
msgid "Here is the same inventory as shown above, simplified with parent groups for the ``prod`` and ``test`` groups. The two inventory files give you the same results:"
msgstr "``prod`` ããã³ ``test`` ã°ã«ãŒãã®èŠªã°ã«ãŒãã䜿çšããŠç°¡çŽ åãããäžèšãšåãã€ã³ãã³ããªãŒã瀺ããŸãã2 ã€ã®ã€ã³ãã³ããªãŒãã¡ã€ã«ã§ã¯ãåãçµæãåŸãããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:168
msgid "Child groups have a couple of properties to note:"
msgstr "åã°ã«ãŒãã«ã¯ã泚æãã¹ã以äžã®ããããã£ãŒããããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:170
msgid "Any host that is member of a child group is automatically a member of the parent group."
msgstr "åã°ã«ãŒãã®ã¡ã³ããŒã§ãããã¹ãã¯ãèªåçã«èŠªã°ã«ãŒãã®ã¡ã³ããŒã«ãªããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:171
msgid "Groups can have multiple parents and children, but not circular relationships."
msgstr "ã°ã«ãŒãã«è€æ°ã®èŠªãšåãè¿œå ããããšã¯ã§ããŸããã埪ç°é¢ä¿ã¯èšå®ã§ããŸããã"
#: ../../rst/inventory_guide/intro_inventory.rst:172
msgid "Hosts can also be in multiple groups, but there will only be **one** instance of a host at runtime. Ansible merges the data from the multiple groups."
msgstr "ãã¹ãã¯è€æ°ã®ã°ã«ãŒãã«å±ããããšãã§ããŸããããã¹ãã®ã€ã³ã¹ã¿ã³ã¹ã¯ **1 ã€** ã ãã§ãããAnsible ã¯è€æ°ã®ã°ã«ãŒãããã®ããŒã¿ãããŒãžããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:175
msgid "Adding ranges of hosts"
msgstr "ãã¹ãç¯å²ã®è¿œå "
#: ../../rst/inventory_guide/intro_inventory.rst:177
msgid "If you have a lot of hosts with a similar pattern, you can add them as a range rather than listing each hostname separately:"
msgstr "åæ§ã®ãã¿ãŒã³ãæã€ãã¹ããå€æ°ããå Žåã¯ãåãã¹ãåãåå¥ã«è¡šç€ºããã®ã§ã¯ãªãããã¹ããç¯å²ãšããŠè¿œå ã§ããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:179
#: ../../rst/inventory_guide/intro_inventory.rst:197
#: ../../rst/inventory_guide/intro_inventory.rst:298
#: ../../rst/inventory_guide/intro_inventory.rst:344
#: ../../rst/inventory_guide/intro_inventory.rst:384
#: ../../rst/inventory_guide/intro_inventory.rst:417
msgid "In INI:"
msgstr "INI ã®å Žåã¯ã以äžã®ããã«ãªããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:186
#: ../../rst/inventory_guide/intro_inventory.rst:204
#: ../../rst/inventory_guide/intro_inventory.rst:306
#: ../../rst/inventory_guide/intro_inventory.rst:350
#: ../../rst/inventory_guide/intro_inventory.rst:396
#: ../../rst/inventory_guide/intro_inventory.rst:445
msgid "In YAML:"
msgstr "YAML ã®å Žåã¯ã以äžã®ããã«ãªããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:195
msgid "You can specify a stride (increments between sequence numbers) when defining a numeric range of hosts:"
msgstr "ãã¹ãã®æ°å€ç¯å²ãå®çŸ©ããéã«ãstride (ã·ãŒã±ã³ã¹çªå·éã®å¢å) ãæå®ããããšãã§ããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:213
msgid "The example above would make the subdomains www01, www03, www05, ..., www49 match, but not www00, www02, www50 and so on, because the stride (increment) is 2 units each step."
msgstr "äžèšã®äŸã§ã¯ãstride (å¢å) ã¯ã¹ãããããšã« 2 ãŠãããã§ããããããµããã¡ã€ã³ www01ãwww03ãwww05ã..ãwww49 ã¯äžèŽããŸãããwww00ãwww02ãwww50 ãªã©ã¯äžèŽããŸããã"
#: ../../rst/inventory_guide/intro_inventory.rst:215
msgid "For numeric patterns, leading zeros can be included or removed, as desired. Ranges are inclusive. You can also define alphabetic ranges:"
msgstr "æ°å€ã®ãã¿ãŒã³ã§ã¯ãå¿
èŠã«å¿ããŠå
é ã«ãŒããå«ãããããŸãã¯åé€ã§ããŸããç¯å²ã¯å
å«çç¯å²ãå®çŸ©ã§ããŸãããŸããã¢ã«ãã¡ãããã®ç¯å²ãå®çŸ©ã§ããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:225
msgid "Passing multiple inventory sources"
msgstr "è€æ°ã®ã€ã³ãã³ããªãŒãœãŒã¹ã®æå®"
#: ../../rst/inventory_guide/intro_inventory.rst:227
msgid "You can target multiple inventory sources (directories, dynamic inventory scripts or files supported by inventory plugins) at the same time by giving multiple inventory parameters from the command line or by configuring :envvar:`ANSIBLE_INVENTORY`. This can be useful when you want to target normally separate environments, like staging and production, at the same time for a specific action."
msgstr "ã³ãã³ãã©ã€ã³ããè€æ°ã®ã€ã³ãã³ããªãŒãã©ã¡ãŒã¿ãŒãæå®ãããã:envvar:`ANSIBLE_INVENTORY` ãèšå®ããããšã§ãè€æ°ã®ã€ã³ãã³ããªãŒãªãœãŒã¹ (ãã£ã¬ã¯ããªãŒãåçã€ã³ãã³ããªãŒã¹ã¯ãªããããŸãã¯ã€ã³ãã³ããªãŒãã©ã°ã€ã³ã«ãããµããŒãããããã¡ã€ã«) ãåæã«å¯Ÿè±¡ã«æå®ã§ããŸããããã¯ãã¹ããŒãžç°å¢ãå®çšŒåç°å¢ãªã©ãéåžžã¯ç°ãªãç°å¢ãåæã«å¯Ÿè±¡ã«æå®ã«ããŠç¹å®ã®ã¢ã¯ã·ã§ã³ãå®è¡ãããå Žåã«äŸ¿å©ã§ãã"
#: ../../rst/inventory_guide/intro_inventory.rst:232
msgid "To target two inventory sources from the command line:"
msgstr "ã³ãã³ãã©ã€ã³ãã 2 ã€ã®ãœã€ãã³ããªãŒãœãŒã¹ã察象ãšããã«ã¯ä»¥äžãå®è¡ããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:241
msgid "Organizing inventory in a directory"
msgstr "ãã£ã¬ã¯ããªãŒå
ã®ã€ã³ãã³ããªãŒã®æŽç"
#: ../../rst/inventory_guide/intro_inventory.rst:243
msgid "You can consolidate multiple inventory sources in a single directory. The simplest version of this is a directory with multiple files instead of a single inventory file. A single file gets difficult to maintain when it gets too long. If you have multiple teams and multiple automation projects, having one inventory file per team or project lets everyone easily find the hosts and groups that matter to them."
msgstr "è€æ°ã®ã€ã³ãã³ããªãŒãœãŒã¹ã 1 ã€ã®ãã£ã¬ã¯ããªãŒã«çµ±åã§ããŸããããã®æãåçŽãªããŒãžã§ã³ã¯ãåäžã®ã€ã³ãã³ããªãŒãã¡ã€ã«ã§ã¯ãªããè€æ°ã®ãã¡ã€ã«ãå«ããã£ã¬ã¯ããªãŒã§ãã1 ã€ã®ãã¡ã€ã«ãé·ããªãããããšã管çãé£ãããªããŸããè€æ°ã®ããŒã ãšè€æ°ã®èªååãããžã§ã¯ããããå ŽåãããŒã ãŸãã¯ãããžã§ã¯ãããšã« 1 ã€ã®ã€ã³ãã³ããªãŒãã¡ã€ã«ã䜿çšãããšã誰ã§ãéèŠãªãã¹ããšã°ã«ãŒããç°¡åã«èŠã€ããããšãã§ããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:245
msgid "You can also combine multiple inventory source types in an inventory directory. This can be useful for combining static and dynamic hosts and managing them as one inventory. The following inventory directory combines an inventory plugin source, a dynamic inventory script, and a file with static hosts:"
msgstr "ãŸããè€æ°ã®ã€ã³ãã³ããªãŒãœãŒã¹ããœãŒã¹ã¿ã€ãã 1 ã€ã®ãã£ã¬ã¯ããªãŒäžã«ã€ã³ãã³ããªãŒãçµ±åã§ããŸããããã¯ãéçãã¹ããšåçãã¹ããçµã¿åãããŠã1 ã€ã®ã€ã³ãã³ããªãŒãšããŠç®¡çããã®ã«äŸ¿å©ã§ãã次ã®ã€ã³ãã³ããªãŒãã£ã¬ã¯ããªãŒã¯ãã€ã³ãã³ããªãŒãã©ã°ã€ã³ãœãŒã¹ãåçã€ã³ãã³ããªãŒã¹ã¯ãªãããããã³éçãã¹ãã®ãã¡ã€ã«ãçµã¿åããããã®ã§ãã"
#: ../../rst/inventory_guide/intro_inventory.rst:257
msgid "You can target this inventory directory as follows:"
msgstr "ãã®ã€ã³ãã³ããªãŒãã£ã¬ã¯ããªãŒã¯ã次ã®ããã«ç°¡åã«å¯Ÿè±¡ã«èšå®ã§ããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:263
msgid "You can also configure the inventory directory in your ``ansible.cfg`` file. See :ref:`intro_configuration` for more details."
msgstr "``ansible.cfg`` ãã¡ã€ã«ã§ inventory ãã£ã¬ã¯ããªãŒãèšå®ããããšãã§ããŸãã詳现ã¯ã:ref:`intro_configuration` ãåç
§ããŠãã ããã"
#: ../../rst/inventory_guide/intro_inventory.rst:266
msgid "Managing inventory load order"
msgstr "ã€ã³ãã³ããªãŒã®èªã¿èŸŒã¿é åºã®ç®¡ç"
#: ../../rst/inventory_guide/intro_inventory.rst:268
msgid "Ansible loads inventory sources in ASCII order according to the filenames. If you define parent groups in one file or directory and child groups in other files or directories, the files that define the child groups must be loaded first. If the parent groups are loaded first, you will see the error ``Unable to parse /path/to/source_of_parent_groups as an inventory source``."
msgstr "Ansible ã¯ããã¡ã€ã«åã«åŸã£ãŠãã€ã³ãã³ããªãŒãœãŒã¹ã ASCII é ã«èªã¿èŸŒã¿ãŸãã芪ã°ã«ãŒããä»ã®ãã¡ã€ã«ãŸãã¯ãã£ã¬ã¯ããªãŒã® 1 ã€ãŸãã¯ãã£ã¬ã¯ããªãŒã§å®çŸ©ããåã°ã«ãŒããå®çŸ©ãããã¡ã€ã«ãå
ã«èªã¿èŸŒãå¿
èŠããããŸãã芪ã°ã«ãŒããæåã«èªã¿èŸŒãŸãããšã``Unable to parse /path/to/source_of_parent_groups as an inventory source`` ãšãããšã©ãŒã衚瀺ãããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:270
msgid "For example, if you have a file called ``groups-of-groups`` that defines a ``production`` group with child groups defined in a file called ``on-prem``, Ansible cannot parse the ``production`` group. To avoid this problem, you can control the load order by adding prefixes to the files:"
msgstr "ããšãã°ã``on-prem`` ãšãããã¡ã€ã«ã§å®çŸ©ãããåã°ã«ãŒããæ〠``production`` ã°ã«ãŒããå®çŸ©ãã ``groups-of-groups`` ãšãããã¡ã€ã«ãããå ŽåãAnsible 㯠``production`` ã°ã«ãŒãã解æã§ããŸããããã®åé¡ãåé¿ããã«ã¯ããã¡ã€ã«ã«æ¥é èŸãè¿œå ããŠãèªã¿èŸŒã¿é åºãå¶åŸ¡ã§ããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:280
msgid "You can find examples of how to organize your inventories and group your hosts in :ref:`inventory_setup_examples`."
msgstr "ã€ã³ãã³ããªãŒãæŽçãããã¹ããã°ã«ãŒãåããæ¹æ³ã¯ã:ref:`inventory_setup_examples` ãåç
§ããŠãã ããã"
#: ../../rst/inventory_guide/intro_inventory.rst:285
msgid "Adding variables to inventory"
msgstr "ã€ã³ãã³ããªãŒãžã®å€æ°ã®è¿œå "
#: ../../rst/inventory_guide/intro_inventory.rst:287
msgid "You can store variable values that relate to a specific host or group in inventory. To start with, you may add variables directly to the hosts and groups in your main inventory file."
msgstr "ã€ã³ãã³ããªãŒã®ç¹å®ã®ãã¹ããŸãã¯ã°ã«ãŒãã«é¢é£ããå€æ°å€ãä¿åããããšãã§ããŸãããŸãã¯ãã¡ã€ã³ã®ã€ã³ãã³ããªãŒãã¡ã€ã«ã®ãã¹ãããã³ã°ã«ãŒãã«å€æ°ãçŽæ¥è¿œå ã§ããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:289
msgid "We document adding variables in the main inventory file for simplicity. However, storing variables in separate host and group variable files is a more robust approach to describing your system policy. Setting variables in the main inventory file is only a shorthand. See :ref:`splitting_out_vars` for guidelines on storing variable values in individual files in the 'host_vars' directory. See :ref:`splitting_out_vars` for details."
msgstr "ç°¡ç¥åã®ç®çã§ãã¡ã€ã³ã®ã€ã³ãã³ããªãŒãã¡ã€ã«ã«å€æ°ãè¿œå ããæ¹æ³ã«ã€ããŠèª¬æããŸãããã ããå€æ°ãå¥ã
ã®ãã¹ãå€æ°ãã¡ã€ã«ãšã°ã«ãŒãå€æ°ãã¡ã€ã«ã«æ ŒçŽããæ¹ãããã確å®ã«ã·ã¹ãã ããªã·ãŒãèšè¿°ã§ããŸããã¡ã€ã³ã®ã€ã³ãã³ããªãŒãã¡ã€ã«ã«å€æ°ãèšå®ããããšã¯ãçç¥åœ¢ã«éããŸããã'host_vars' ãã£ã¬ã¯ããªãŒã®åå¥ãã¡ã€ã«ã«å€æ°ãä¿åããã¬ã€ãã©ã€ã³ã¯ã:ref:`splitting_out_vars` ãåç
§ããŠãã ããã詳现ã¯ã:ref:`splitting_out_vars` ãåç
§ããŠãã ããã"
#: ../../rst/inventory_guide/intro_inventory.rst:294
msgid "Assigning a variable to one machine: host variables"
msgstr "ãããã·ã³ãžã®å€æ°ã®å²ãåœãŠ: ãã¹ãå€æ°"
#: ../../rst/inventory_guide/intro_inventory.rst:296
msgid "You can easily assign a variable to a single host, then use it later in playbooks. You can do this directly in your inventory file."
msgstr "1 å°ã®ãã¹ãã«å€æ°ãç°¡åã«å²ãåœãŠããšãåŸã§ Playbook ã§äœ¿çšã§ããŸããã€ã³ãã³ããªãŒãã¡ã€ã«ã§çŽæ¥ãããå®è¡ã§ããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:319
msgid "Unique values like non-standard SSH ports work well as host variables. You can add them to your Ansible inventory by adding the port number after the hostname with a colon:"
msgstr "éæšæºã® SSH ããŒãã®ãããªäžæãªå€ã¯ããã¹ãå€æ°ãšããŠããŸãæ©èœããŸãããã¹ãåã®åŸã«ã³ãã³ãä»ããŠããŒãçªå·ãè¿œå ããããšã§ãAnsible ã€ã³ãã³ããªãŒã«è¿œå ããããšãã§ããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:325
msgid "Connection variables also work well as host variables:"
msgstr "æ¥ç¶å€æ°ããã¹ãå€æ°ãšããŠæ©èœããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:335
msgid "If you list non-standard SSH ports in your SSH config file, the ``openssh`` connection will find and use them, but the ``paramiko`` connection will not."
msgstr "SSH èšå®ãã¡ã€ã«å
ã«éæšæºã® SSH ããŒãã®äžèŠ§ã衚瀺ããå Žåã``openssh`` æ¥ç¶ã¯ãã®ããŒããèŠã€ããŠäœ¿çšããŸããã``paramiko`` æ¥ç¶ã¯è¡ãããŸããã"
#: ../../rst/inventory_guide/intro_inventory.rst:340
msgid "Inventory aliases"
msgstr "ã€ã³ãã³ããªãŒãšã€ãªã¢ã¹"
#: ../../rst/inventory_guide/intro_inventory.rst:342
msgid "You can also define aliases in your inventory using host variables:"
msgstr "ãã¹ãå€æ°ã䜿çšããŠã€ã³ãã³ããªãŒã§ãšã€ãªã¢ã¹ãå®çŸ©ããããšãã§ããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:360
msgid "In this example, running Ansible against the host alias \"jumper\" will connect to 192.0.2.50 on port 5555. See :ref:`behavioral inventory parameters <behavioral_parameters>` to further customize the connection to hosts."
msgstr "ãã®äŸã§ã¯ããã¹ãã®å¥åãjumperãã«å¯Ÿã㊠Ansible ãå®è¡ãããšãããŒã 5555 ã® 192.0.2.50 ã«æ¥ç¶ãããŸãããã¹ããžã®æ¥ç¶ãããã«ã«ã¹ã¿ãã€ãºããã«ã¯ãã:ref:`behavioral inventory parameters <behavioral_parameters>`ããåç
§ããŠãã ããã"
#: ../../rst/inventory_guide/intro_inventory.rst:363
msgid "Defining variables in INI format"
msgstr "INI 圢åŒã§ã®å€æ°ã®å®çŸ©"
#: ../../rst/inventory_guide/intro_inventory.rst:365
msgid "Values passed in the INI format using the ``key=value`` syntax are interpreted differently depending on where they are declared:"
msgstr "``key=value`` æ§æã䜿çšã㊠INI 圢åŒã§æž¡ãããå€ã解éãããæ¹æ³ã¯ã宣èšãããå Žæã«å¿ããŠç°ãªããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:367
msgid "When declared inline with the host, INI values are interpreted as Python literal structures (strings, numbers, tuples, lists, dicts, booleans, None). Host lines accept multiple ``key=value`` parameters per line. Therefore they need a way to indicate that a space is part of a value rather than a separator. Values that contain whitespace can be quoted (single or double). See the `Python shlex parsing rules`_ for details."
msgstr "ãã¹ãã®ã€ã³ã©ã€ã³ã§å®£èšãããšãINI å€ã¯ Pythonã® ãªãã©ã«æ§é (æååãæ°å€ãã¿ãã«ããªã¹ãããã£ã¯ã·ã§ããªãŒãããŒã«å€ããªã) ãšããŠè§£éãããŸãããã¹ãã®è¡ã¯ã1 è¡ã«ã€ãè€æ°ã® ``key=value`` ãã©ã¡ãŒã¿ãŒãåãä»ããŸãããã®ãããã¹ããŒã¹ãåºåãæåã§ã¯ãªãå€ã®äžéšã§ããããšã瀺ãæ¹æ³ãå¿
èŠã§ããã¹ããŒã¹ãå«ãŸããå€ãåŒçšç¬Š(äžéãŸãã¯äºé)ã§å²ãããšãã§ããŸãã詳现ã¯ã `Python shlex 解æã«ãŒã«`_ãåç
§ããŠãã ããã"
#: ../../rst/inventory_guide/intro_inventory.rst:369
msgid "When declared in a ``:vars`` section, INI values are interpreted as strings. For example ``var=FALSE`` would create a string equal to 'FALSE'. Unlike host lines, ``:vars`` sections accept only a single entry per line, so everything after the ``=`` must be the value for the entry."
msgstr "``:vars`` ã»ã¯ã·ã§ã³ã§å®£èšãããšãINI ã®å€ã¯æååãšããŠè§£éãããŸããããšãã°ã``var=FALSE`` 㯠FALSE ãšçããæååãäœæããŸãããã¹ãè¡ãšã¯ç°ãªãã``:vars`` ã»ã¯ã·ã§ã³ã¯è¡ããšã« 1 ã€ã®ãšã³ããªãŒã®ã¿ãèš±å¯ããããã``=`` ã®åŸã«ç¶ããã¹ãŠã®ãã®ããšã³ããªãŒã®å€ã§ããå¿
èŠããããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:371
msgid "If a variable value set in an INI inventory must be a certain type (for example, a string or a boolean value), always specify the type with a filter in your task. Do not rely on types set in INI inventories when consuming variables."
msgstr "INI ã€ã³ãã³ããªãŒã«èšå®ãããŠããå€æ°ã®å€ãç¹å®ã®å (æååãããŒã«å€ãªã©) ã§ãªããã°ãªããªãå Žåã¯ãå¿
ãã¿ã¹ã¯ã®ãã£ã«ã¿ãŒã§åãæå®ããŠãã ãããå€æ°ã䜿çšããéã«ãINI ã€ã³ãã³ããªãŒã«èšå®ãããŠããåã«é Œããªãã§ãã ããã"
#: ../../rst/inventory_guide/intro_inventory.rst:373
msgid "Consider using YAML format for inventory sources to avoid confusion on the actual type of a variable. The YAML inventory plugin processes variable values consistently and correctly."
msgstr "å€æ°ã®å®éã®ã¿ã€ãã«é¢ããæ··ä¹±ãåé¿ããããã«ãã€ã³ãã³ããªãŒãœãŒã¹ã« YAML 圢åŒã䜿çšããããšãæ€èšããŠãã ãããYAML ã€ã³ãã³ããªãŒãã©ã°ã€ã³ã¯å€æ°ã®å€ãäžè²«ããŠãæ£ããåŠçããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:380
msgid "Assigning a variable to many machines: group variables"
msgstr "å€ãã®ãã·ã³ãžã®å€æ°ã®å²ãåœãŠ: ã°ã«ãŒãå€æ°"
#: ../../rst/inventory_guide/intro_inventory.rst:382
msgid "If all hosts in a group share a variable value, you can apply that variable to an entire group at once."
msgstr "ã°ã«ãŒãå
ã®ãã¹ãŠã®ãã¹ããå€æ°ã®å€ãå
±æããŠããå Žåã¯ããã®å€æ°ãã°ã«ãŒãå
šäœã«äžåºŠã«é©çšããããšãã§ããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:408
msgid "Group variables are a convenient way to apply variables to multiple hosts at once. Before executing, however, Ansible always flattens variables, including inventory variables, to the host level. If a host is a member of multiple groups, Ansible reads variable values from all of those groups. If you assign different values to the same variable in different groups, Ansible chooses which value to use based on internal :ref:`rules for merging <how_we_merge>`."
msgstr "ã°ã«ãŒãå€æ°ã¯ãè€æ°ã®ãã¹ãã«äžåºŠã«å€æ°ãé©çšãã䟿å©ãªæ¹æ³ã§ããããããAnsible ã¯å®è¡åã«ãã€ã³ãã³ããªãŒå€æ°ãå«ãå€æ°ãåžžã«ãã¹ãã¬ãã«ã«ãã©ããåããŸãããã¹ããè€æ°ã®ã°ã«ãŒãã«å±ããŠããå ŽåãAnsible ã¯ãããã®ã°ã«ãŒãã®ãã¹ãŠããå€æ°ã®å€ãèªã¿åããŸããç°ãªãã°ã«ãŒãã§åãå€æ°ã«ç°ãªãå€ãå²ãåœãŠãå ŽåãAnsible ã¯å
éš :ref:`ããŒãžã®ã«ãŒã« <how_we_merge>` ã«åºã¥ããŠã©ã®å€ã䜿çšããããéžæããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:413
msgid "Inheriting variable values: group variables for groups of groups"
msgstr "å€æ°å€ã®ç¶æ¿: ã°ã«ãŒãã®ã°ã«ãŒãçšã°ã«ãŒãå€æ°"
#: ../../rst/inventory_guide/intro_inventory.rst:415
msgid "You can apply variables to parent groups (nested groups or groups of groups) as well as to child groups. The syntax is the same: ``:vars`` for INI format and ``vars:`` for YAML format:"
msgstr "åã°ã«ãŒãã ãã§ãªãã芪ã°ã«ãŒã (ãã¹ããããã°ã«ãŒããŸãã¯ã°ã«ãŒãã®ã°ã«ãŒã) ã«ãå€æ°ãé©çšã§ããŸããæ§æã¯åãã§ã (INI 圢åŒã¯ ``:vars``ãYAML 圢åŒã¯ ``vars:``)ã"
#: ../../rst/inventory_guide/intro_inventory.rst:472
msgid "A child group's variables will have higher precedence (override) a parent group's variables."
msgstr "åã°ã«ãŒãã®å€æ°ã¯ã芪ã°ã«ãŒãã®å€æ°ãããåªå
床ãé«ããªããŸã (ãªãŒãã©ã€ã)ã"
#: ../../rst/inventory_guide/intro_inventory.rst:477
msgid "Organizing host and group variables"
msgstr "ãã¹ãå€æ°ãšã°ã«ãŒãå€æ°ã®æŽç"
#: ../../rst/inventory_guide/intro_inventory.rst:479
msgid "Although you can store variables in the main inventory file, storing separate host and group variables files may help you organize your variable values more easily. You can also use lists and hash data in host and group variables files, which you cannot do in your main inventory file."
msgstr "å€æ°ã¯ã¡ã€ã³ã€ã³ãã³ããªãŒãã¡ã€ã«ã«ä¿åã§ããŸããããã¹ãå€æ°ãã¡ã€ã«ãšã°ã«ãŒãå€æ°ãã¡ã€ã«ãå¥ã
ã«ä¿åãããšãå€æ°å€ãããç°¡åã«æŽçã§ããå ŽåããããŸãããã¹ãå€æ°ãã¡ã€ã«ãšã°ã«ãŒãå€æ°ãã¡ã€ã«ã§ãªã¹ããšããã·ã¥ããŒã¿ã䜿çšããããšãã§ããŸãããããã¯ã¡ã€ã³ã®ã€ã³ãã³ããªãŒãã¡ã€ã«ã§ã¯äœ¿çšã§ããŸããã"
#: ../../rst/inventory_guide/intro_inventory.rst:481
msgid "Host and group variable files must use YAML syntax. Valid file extensions include '.yml', '.yaml', '.json', or no file extension. See :ref:`yaml_syntax` if you are new to YAML."
msgstr "ãã¹ãããã³ã°ã«ãŒãå€æ°ãã¡ã€ã«ã¯ãYAML æ§æã䜿çšããå¿
èŠããããŸããæå¹ãªãã¡ã€ã«æ¡åŒµåã«ã¯ã.ymlã.yamlã.json ãå«ãŸãããããã¡ã€ã«æ¡åŒµåããããŸãããYAML ã䜿çšããããšããªãå Žåã«ã¯ã:ref:`yaml_syntax` ãåç
§ããŠãã ããã"
#: ../../rst/inventory_guide/intro_inventory.rst:483
msgid "Ansible loads host and group variable files by searching paths relative to the inventory file or the playbook file. If your inventory file at ``/etc/ansible/hosts`` contains a host named 'foosball' that belongs to two groups, 'raleigh' and 'webservers', that host will use variables in YAML files at the following locations:"
msgstr "Ansible ã¯ãã€ã³ãã³ããªãŒãã¡ã€ã«ãŸã㯠Playbook ãã¡ã€ã«ããã®çžå¯Ÿãã¹ãæ€çŽ¢ããŠããã¹ãããã³ã°ã«ãŒãå€æ°ãã¡ã€ã«ãèªã¿èŸŒã¿ãŸãã``/etc/ansible/hosts`` ã®ã€ã³ãã³ããªãŒãã¡ã€ã«ã«ãfoosballããšããååã®ãã¹ãããããããããraleighããšãwebserversããšãã 2 ã€ã®ã°ã«ãŒãã«æå±ããŠããå Žåããã®ãã¹ãã¯ä»¥äžã®å Žæã«ãã YAML ãã¡ã€ã«ã®å€æ°ã䜿çšããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:491
msgid "For example, if you group hosts in your inventory by datacenter, and each datacenter uses its own NTP server and database server, you can create a file called ``/etc/ansible/group_vars/raleigh`` to store the variables for the ``raleigh`` group:"
msgstr "ããšãã°ãã€ã³ãã³ããªãŒå
ã®ãã¹ããããŒã¿ã»ã³ã¿ãŒããšã«ãŸãšããåããŒã¿ã»ã³ã¿ãŒãç¬èªã® NTP ãµãŒããŒããã³ããŒã¿ããŒã¹ãµãŒããŒã䜿çšããå Žåã¯ã``/etc/ansible/group_vars/raleigh`` ãšããååã®ãã¡ã€ã«ãäœæããŠã``raleigh`` ã°ã«ãŒãã®å€æ°ãä¿åã§ããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:499
msgid "You can also create *directories* named after your groups or hosts. Ansible will read all the files in these directories in lexicographical order. An example with the 'raleigh' group:"
msgstr "ãŸããã°ã«ãŒããŸãã¯ãã¹ãã®ååãä»ãããã *ãã£ã¬ã¯ããªãŒ* ãäœæã§ããŸããAnsible ã¯ããããã®ãã£ã¬ã¯ããªãŒã«å«ãŸãããã¹ãŠã®ãã¡ã€ã«ããã£ã¯ã·ã§ããªãŒã®é ã«èªã¿èŸŒã¿ãŸããäŸã§ã¯ããraleighãã°ã«ãŒãã䜿çšããŠããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:506
msgid "All hosts in the 'raleigh' group will have the variables defined in these files available to them. This can be very useful to keep your variables organized when a single file gets too big, or when you want to use :ref:`Ansible Vault<playbooks_vault>` on some group variables."
msgstr "ãraleighãã°ã«ãŒãã®ãã¹ãŠã®ãã¹ãã¯ããããã®ãã¡ã€ã«ã§å®çŸ©ãããå€æ°ãå©çšã§ããããã«ãªããŸããããã¯ã1 ã€ã®ãã¡ã€ã«ã倧ãããªãããããšãã«ãå€æ°ãæŽçããŠããã®ã«éåžžã«äŸ¿å©ã§ãããŸããããã€ãã®ã°ã«ãŒãå€æ°ã« :ref:`Ansible Vault<playbooks_vault>` ã䜿çšãããå Žåã«ã䟿å©ã§ãã"
#: ../../rst/inventory_guide/intro_inventory.rst:510
msgid "For ``ansible-playbook`` you can also add ``group_vars/`` and ``host_vars/`` directories to your playbook directory. Other Ansible commands (for example, ``ansible``, ``ansible-console``, and so on) will only look for ``group_vars/`` and ``host_vars/`` in the inventory directory. If you want other commands to load group and host variables from a playbook directory, you must provide the ``--playbook-dir`` option on the command line. If you load inventory files from both the playbook directory and the inventory directory, variables in the playbook directory will override variables set in the inventory directory."
msgstr "``ansible-playbook`` ã«é¢ããŠããã£ã¬ã¯ããªãŒ ``group_vars/``ããã³ ``host_vars/`` ã Playbook ãã£ã¬ã¯ããªãŒã«è¿œå ããããšãã§ããŸããä»ã® Ansible ã³ãã³ã (ããšãã°ã``ansible``ã``ansible-console`` ãªã©) ã¯ãã€ã³ãã³ããªãŒãã£ã¬ã¯ããªãŒå
ã® ``group_vars/`` ãš ``host_vars/`` ã®ã¿ãæ¢ããŸããä»ã®ã³ãã³ã㧠Playbook ãã£ã¬ã¯ããªãŒããã°ã«ãŒãå€æ°ããã¹ãå€æ°ãèªã¿èŸŒãå Žåã¯ãã³ãã³ãã©ã€ã³ã§ ``--playbook-dir`` ãªãã·ã§ã³ãæå®ããå¿
èŠããããŸããPlaybook ãã£ã¬ã¯ããªãŒãš inventory ãã£ã¬ã¯ããªãŒã®äž¡æ¹ããã€ã³ãã³ããªãŒãã¡ã€ã«ãèªã¿èŸŒãã å ŽåãPlaybook ãã£ã¬ã¯ããªãŒã®å€æ°ã¯ã€ã³ãã³ããªãŒãã£ã¬ã¯ããªãŒã§èšå®ãããå€æ°ãããåªå
ãããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:513
msgid "Keeping your inventory file and variables in a git repo (or other version control) is an excellent way to track changes to your inventory and host variables."
msgstr "git ãªããžããªãŒ (ãŸãã¯ä»ã®ããŒãžã§ã³ç®¡ç) ã§ã€ã³ãã³ããªãŒãã¡ã€ã«ããã³å€æ°ãç¶æããããšã¯ãã€ã³ãã³ããªãŒããã³ãã¹ãå€æ°ãžã®å€æŽã远跡ããåªããæ¹æ³ã§ãã"
#: ../../rst/inventory_guide/intro_inventory.rst:519
msgid "How variables are merged"
msgstr "å€æ°ãããŒãžããæ¹æ³"
#: ../../rst/inventory_guide/intro_inventory.rst:521
msgid "By default variables are merged/flattened to the specific host before a play is run. This keeps Ansible focused on the Host and Task, so groups don't really survive outside of inventory and host matching. By default, Ansible overwrites variables including the ones defined for a group and/or host (see :ref:`DEFAULT_HASH_BEHAVIOUR<DEFAULT_HASH_BEHAVIOUR>`). The order/precedence is (from lowest to highest):"
msgstr "ããã©ã«ãã§ã¯ããã¬ã€ãå®è¡ãããåã«ãå€æ°ãç¹å®ã®ãã¹ãã«ããŒãž/ãã©ããåãããŸããããã«ãããAnsible ã¯ãã¹ããšã¿ã¹ã¯ã«çŠç¹ãåœãŠãŠãããããã°ã«ãŒãã¯ã€ã³ãã³ããªãŒãšãã¹ãã®äžèŽä»¥å€ã§ã¯å®éã«ã¯åç¶ããŸãããããã©ã«ãã§ã¯ãAnsible ã¯ã°ã«ãŒãããã¹ãã«å®çŸ©ããããã®ãå«ãå€æ°ãäžæžãããŸã (ã:ref:`DEFAULT_HASH_BEHAVIOUR<DEFAULT_HASH_BEHAVIOUR>`ããåç
§)ããã®é åº/åªå
é äœã¯ (äœããã®ããé«ããã®ãž) ãšãªã£ãŠããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:523
msgid "all group (because it is the 'parent' of all other groups)"
msgstr "ãã¹ãŠã®ã°ã«ãŒã (ä»ã®ãã¹ãŠã®ã°ã«ãŒãã®ã芪ãã§ãããã)"
#: ../../rst/inventory_guide/intro_inventory.rst:524
msgid "parent group"
msgstr "芪ã°ã«ãŒã"
#: ../../rst/inventory_guide/intro_inventory.rst:525
msgid "child group"
msgstr "åã°ã«ãŒã"
#: ../../rst/inventory_guide/intro_inventory.rst:526
msgid "host"
msgstr "host"
#: ../../rst/inventory_guide/intro_inventory.rst:528
msgid "By default Ansible merges groups at the same parent/child level in ASCII order, and variables from the last group loaded overwrite variables from the previous groups. For example, an a_group will be merged with b_group and b_group vars that match will overwrite the ones in a_group."
msgstr "ããã©ã«ãã§ã¯ãAnsible ã¯åã芪åã¬ãã«ã®ã°ã«ãŒãã ASCII é ã«ããŒãžããæåŸã«èªã¿èŸŒãŸããã°ã«ãŒãã®å€æ°ããã以åã®ã°ã«ãŒãããã®å€æ°ãäžæžãããŸããããšãã°ãa_group 㯠b_group ã«ããŒãžãããäžèŽãã b_group ã®å€æ°ã a_group ã®å€æ°ãäžæžãããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:530
msgid "You can change this behavior by setting the group variable ``ansible_group_priority`` to change the merge order for groups of the same level (after the parent/child order is resolved). The larger the number, the later it will be merged, giving it higher priority. This variable defaults to ``1`` if not set. For example:"
msgstr "ãã®åäœãå€æŽããã«ã¯ãã°ã«ãŒãå€æ° ``ansible_group_priority`` ãèšå®ããŠãåãã¬ãã«ã®ã°ã«ãŒãã®ããŒãžé åºãå€æŽããããšãã§ããŸã (芪åã®é åºã解決ãããåŸ)ãæ°åã倧ããã»ã©åŸã«ããŒãžãããåªå
é äœãé«ããªããŸãããã®å€æ°ãèšå®ãããŠããªãå Žåã®ããã©ã«ã㯠``1`` ã§ããããšãã°ã以äžã®ããã«ãªããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:542
msgid "In this example, if both groups have the same priority, the result would normally have been ``testvar == b``, but since we are giving the ``a_group`` a higher priority the result will be ``testvar == a``."
msgstr "ãã®äŸã§ã¯ãäž¡æ¹ã®ã°ã«ãŒãã®åªå
é äœãåãå Žåãçµæã¯éåžž ``testvar == b`` ã«ãªããŸããã``a_group`` ã®åªå
床ãé«ããããçµæ㯠``testvar == a`` ã«ãªããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:544
msgid "``ansible_group_priority`` can only be set in the inventory source and not in group_vars/, as the variable is used in the loading of group_vars."
msgstr "``ansible_group_priority`` ã¯ãgroup_vars ã®èªã¿èŸŒã¿ã§ãã®å€æ°ã䜿çšããããããã€ã³ãã³ããªãŒãœãŒã¹ã§ã®ã¿èšå®ã§ããgroup_vars/ ã§ã¯èšå®ã§ããŸããã"
#: ../../rst/inventory_guide/intro_inventory.rst:547
msgid "Managing inventory variable load order"
msgstr "ã€ã³ãã³ããªãŒå€æ°ã®èªã¿èŸŒã¿é åºã®ç®¡ç"
#: ../../rst/inventory_guide/intro_inventory.rst:549
msgid "When using multiple inventory sources, keep in mind that any variable conflicts are resolved according to the rules described in :ref:`how_we_merge` and :ref:`ansible_variable_precedence`. You can control the merging order of variables in inventory sources to get the variable value you need."
msgstr "è€æ°ã®ã€ã³ãã³ããªãŒãœãŒã¹ã䜿çšããå Žåã¯ãvariable ããã³ :ref:`how_we_merge` ãš :ref:`ansible_variable_precedence` ã§èª¬æãããŠããã«ãŒã«ã«åŸã£ãŠå€æ°ã®ç«¶åã解決ãããããšã«æ³šæããŠãã ãããã€ã³ãã³ããªãŒãœãŒã¹ã§å€æ°ã®ããŒãžé åºãå¶åŸ¡ããå¿
èŠãªå€æ°ã®å€ãååŸã§ããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:552
msgid "When you pass multiple inventory sources at the command line, Ansible merges variables in the order you pass those parameters. If ``[all:vars]`` in staging inventory defines ``myvar = 1`` and production inventory defines ``myvar = 2``, then:"
msgstr "ã³ãã³ãã©ã€ã³ã§è€æ°ã®ã€ã³ãã³ããªãŒãœãŒã¹ãæž¡ããšãAnsible ã¯ãããã®ãã©ã¡ãŒã¿ãŒãæž¡ãé åºã§å€æ°ãããŒãžããŸããã¹ããŒãžã³ã°ã€ã³ãã³ããªãŒã® ``[all:vars]`` ã ``myvar = 1`` ãå®çŸ©ããå®çšŒåã€ã³ãã³ããªãŒã ``myvar = 2`` ãå®çŸ©ããŠããå Žåã«ã¯ã"
#: ../../rst/inventory_guide/intro_inventory.rst:554
msgid "Pass ``-i staging -i production`` to run the playbook with ``myvar = 2``."
msgstr "* ``-i staging -i production`` ãæž¡ã㊠``myvar = 2`` ãæå®ã㊠Playbook ãå®è¡ããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:555
msgid "Pass ``-i production -i staging`` to run the playbook with ``myvar = 1``."
msgstr "* ``-i production -i staging`` ãæž¡ã㊠``myvar = 1`` ãæå®ã㊠Playbook ãå®è¡ããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:557
msgid "When you put multiple inventory sources in a directory, Ansible merges them in ASCII order according to the filenames. You can control the load order by adding prefixes to the files:"
msgstr "ãã£ã¬ã¯ããªãŒã«è€æ°ã®ã€ã³ãã³ããªãŒãœãŒã¹ãé
眮ãããšãAnsible ã¯ãã¡ã€ã«åã«åŸã£ãŠ ASCII é ã§ããŒãžããŸãããã¡ã€ã«ã«æ¥é èŸãè¿œå ããããšã§ãèªã¿èŸŒã¿é åºãå¶åŸ¡ã§ããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:568
msgid "If ``01-openstack.yml`` defines ``myvar = 1`` for the group ``all``, ``02-dynamic-inventory.py`` defines ``myvar = 2``, and ``03-static-inventory`` defines ``myvar = 3``, the playbook will be run with ``myvar = 3``."
msgstr "``01-openstack.yml`` ãã°ã«ãŒã ``all`` ã«å¯Ÿã㊠``myvar = 1`` ãå®çŸ©ãã``02-dynamic-inventory.py`` ã ``myvar = 2`` ãå®çŸ©ãã``03-static-inventory`` ã ``myvar = 3`` ãå®çŸ©ããå Žåã¯ãPlaybook ã ``myvar = 3`` ã§å®è¡ããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:571
msgid "For more details on inventory plugins and dynamic inventory scripts see :ref:`inventory_plugins` and :ref:`intro_dynamic_inventory`."
msgstr "ã€ã³ãã³ããªãŒãã©ã°ã€ã³ããã³åçã€ã³ãã³ããªãŒã¹ã¯ãªããã®è©³çŽ°ã¯ãã:ref:`inventory_plugins`ãããã³ã:ref:`intro_dynamic_inventory`ããåç
§ããŠãã ããã"
#: ../../rst/inventory_guide/intro_inventory.rst:576
msgid "Connecting to hosts: behavioral inventory parameters"
msgstr "ãã¹ããžã®æ¥ç¶: åäœçšã€ã³ãã³ããªãŒãã©ã¡ãŒã¿ãŒ"
#: ../../rst/inventory_guide/intro_inventory.rst:578
msgid "As described above, setting the following variables control how Ansible interacts with remote hosts."
msgstr "äžèšã®ããã«ã以äžã®å€æ°ãèšå®ããŠãAnsible ããªã¢ãŒããã¹ããšå¯Ÿè©±ããæ¹æ³ãå¶åŸ¡ããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:580
msgid "Host connection:"
msgstr "ãã¹ãæ¥ç¶:"
#: ../../rst/inventory_guide/intro_inventory.rst:585
msgid "ansible_connection"
msgstr "ansible_connection"
#: ../../rst/inventory_guide/intro_inventory.rst:585
msgid "Connection type to the host. This can be the name of any of ansible's connection plugins. SSH protocol types are ``smart``, ``ssh`` or ``paramiko``. The default is smart. Non-SSH based types are described in the next section."
msgstr "ãã¹ããžã®æ¥ç¶ã¿ã€ããããã¯ãAnsible ã® connection ãã©ã°ã€ã³ã®ååã§ããSSH ãããã³ã«ã¿ã€ã㯠``smart``ã``ssh``ããŸã㯠``paramiko`` ã§ããããã©ã«ã㯠smart ã§ããSSH ããŒã¹ä»¥å€ã®ã¿ã€ãã¯æ¬¡ã®ã»ã¯ã·ã§ã³ã§èª¬æããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:587
msgid "General for all connections:"
msgstr "ãã¹ãŠã®æ¥ç¶ã«å¯Ÿããäžè¬çãªèšå®:"
#: ../../rst/inventory_guide/intro_inventory.rst:589
#: ../../rst/inventory_guide/intro_inventory.rst:692
msgid "ansible_host"
msgstr "ansible_host"
#: ../../rst/inventory_guide/intro_inventory.rst:590
msgid "The name of the host to connect to, if different from the alias you wish to give to it."
msgstr "æ¥ç¶ãããã¹ãã®åå (å²ãåœãŠãããšã€ãªã¢ã¹ãšç°ãªãå Žå)ã"
#: ../../rst/inventory_guide/intro_inventory.rst:591
msgid "ansible_port"
msgstr "ansible_port"
#: ../../rst/inventory_guide/intro_inventory.rst:592
msgid "The connection port number, if not the default (22 for ssh)"
msgstr "ããã©ã«ãã§ã¯ãªãå Žå (ssh ã®å Žå㯠22) ã¯ãæ¥ç¶ããŒãçªå·ã"
#: ../../rst/inventory_guide/intro_inventory.rst:593
#: ../../rst/inventory_guide/intro_inventory.rst:694
msgid "ansible_user"
msgstr "ansible_user"
#: ../../rst/inventory_guide/intro_inventory.rst:594
msgid "The user name to use when connecting to the host"
msgstr "ãã¹ãã«æ¥ç¶ããéã«äœ¿çšãããŠãŒã¶ãŒåã"
#: ../../rst/inventory_guide/intro_inventory.rst:597
msgid "ansible_password"
msgstr "ansible_password"
#: ../../rst/inventory_guide/intro_inventory.rst:596
msgid "The password to use to authenticate to the host (never store this variable in plain text; always use a vault. See :ref:`tip_for_variables_and_vaults`)"
msgstr "ãã¹ããžã®èªèšŒã«äœ¿çšãããã¹ã¯ãŒã (ãã®å€æ°ãå¹³æã§ä¿åããªãã§ãã ãããåžžã« Valut ã䜿çšããŠãã ãããã:ref:`tip_for_variables_and_vaults`ããåç
§)ã"
#: ../../rst/inventory_guide/intro_inventory.rst:599
msgid "Specific to the SSH connection:"
msgstr "SSH æ¥ç¶ã«åºæ:"
#: ../../rst/inventory_guide/intro_inventory.rst:601
msgid "ansible_ssh_private_key_file"
msgstr "ansible_ssh_private_key_file"
#: ../../rst/inventory_guide/intro_inventory.rst:602
msgid "Private key file used by ssh. Useful if using multiple keys and you don't want to use SSH agent."
msgstr "ssh ã䜿çšããç§å¯éµãã¡ã€ã«ãè€æ°ã®éµã䜿çšããSSH ãšãŒãžã§ã³ãã䜿çšããããªãå Žåã«äŸ¿å©ã§ãã"
#: ../../rst/inventory_guide/intro_inventory.rst:605
msgid "ansible_ssh_common_args"
msgstr "ansible_ssh_common_args"
#: ../../rst/inventory_guide/intro_inventory.rst:604
msgid "This setting is always appended to the default command line for :command:`sftp`, :command:`scp`, and :command:`ssh`. Useful to configure a ``ProxyCommand`` for a certain host (or group)."
msgstr "ãã®èšå®ã¯ãåžžã« :command:`sftp`ã:command:`scp`ãããã³ :command:`ssh` ã®ããã©ã«ãã®ã³ãã³ãã©ã€ã³ã«è¿œå ãããŸããç¹å®ã®ãã¹ã (ãŸãã¯ã°ã«ãŒã) ã« ``ProxyCommand`` ãèšå®ããŠãã ããã"
#: ../../rst/inventory_guide/intro_inventory.rst:607
msgid "ansible_sftp_extra_args"
msgstr "ansible_sftp_extra_args"
#: ../../rst/inventory_guide/intro_inventory.rst:608
msgid "This setting is always appended to the default :command:`sftp` command line."
msgstr "ãã®èšå®ã¯ãããã©ã«ãã® :command:`sftp` ã³ãã³ãã©ã€ã³ã«åžžã«ä»å ãããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:609
msgid "ansible_scp_extra_args"
msgstr "ansible_scp_extra_args"
#: ../../rst/inventory_guide/intro_inventory.rst:610
msgid "This setting is always appended to the default :command:`scp` command line."
msgstr "ãã®èšå®ã¯ãããã©ã«ãã® :command:`scp` ã³ãã³ãã©ã€ã³ã«åžžã«ä»å ãããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:611
msgid "ansible_ssh_extra_args"
msgstr "ansible_ssh_extra_args"
#: ../../rst/inventory_guide/intro_inventory.rst:612
msgid "This setting is always appended to the default :command:`ssh` command line."
msgstr "ãã®èšå®ã¯ãããã©ã«ãã® :command:`ssh` ã³ãã³ãã©ã€ã³ã«åžžã«ä»å ãããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:613
msgid "ansible_ssh_pipelining"
msgstr "ansible_ssh_pipelining"
#: ../../rst/inventory_guide/intro_inventory.rst:614
msgid "Determines whether or not to use SSH pipelining. This can override the ``pipelining`` setting in :file:`ansible.cfg`."
msgstr "SSH ãã€ãã©ã€ã³ã䜿çšãããã©ããã決å®ããŸãããã㯠:file:`ansible.cfg` ã® ``pipelining`` ã®èšå®ãäžæžãããããšãã§ããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:617
msgid "ansible_ssh_executable (added in version 2.2)"
msgstr "ansible_ssh_executable (ããŒãžã§ã³ 2.2 ã§è¿œå )"
#: ../../rst/inventory_guide/intro_inventory.rst:616
msgid "This setting overrides the default behavior to use the system :command:`ssh`. This can override the ``ssh_executable`` setting in :file:`ansible.cfg`."
msgstr "ãã®èšå®ã«ãããã·ã¹ãã ã® :command:`ssh` ã䜿çšããããã«ããã©ã«ãã®åäœãäžæžããããŸããããã«ããã:file:`ansible.cfg` ã® ``ssh_executable`` èšå®ãäžæžãã§ããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:619
msgid "Privilege escalation (see :ref:`Ansible Privilege Escalation<become>` for further details):"
msgstr "æš©éã®ææ Œ (詳现ã¯ã:ref:`Ansible æš©éææ Œ<become>`ããåç
§):"
#: ../../rst/inventory_guide/intro_inventory.rst:621
#: ../../rst/inventory_guide/intro_inventory.rst:696
msgid "ansible_become"
msgstr "ansible_become"
#: ../../rst/inventory_guide/intro_inventory.rst:622
msgid "Equivalent to ``ansible_sudo`` or ``ansible_su``, allows to force privilege escalation"
msgstr "``ansible_sudo`` ãŸã㯠``ansible_su`` ãšåçã§ããããã«ãããæš©éææ Œã匷å¶ã§ããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:623
msgid "ansible_become_method"
msgstr "ansible_become_method"
#: ../../rst/inventory_guide/intro_inventory.rst:624
msgid "Allows to set privilege escalation method"
msgstr "æš©éææ Œã¡ãœããã®èšå®ãèš±å¯ããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:625
msgid "ansible_become_user"
msgstr "ansible_become_user"
#: ../../rst/inventory_guide/intro_inventory.rst:626
msgid "Equivalent to ``ansible_sudo_user`` or ``ansible_su_user``, allows to set the user you become through privilege escalation"
msgstr "``ansible_sudo_user`` ãŸã㯠``ansible_su_user`` ãšåçã§ãæš©éææ Œã«ãã become ãè¡ããŠãŒã¶ãŒãèšå®ã§ããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:627
msgid "ansible_become_password"
msgstr "ansible_become_password"
#: ../../rst/inventory_guide/intro_inventory.rst:628
msgid "Equivalent to ``ansible_sudo_password`` or ``ansible_su_password``, allows you to set the privilege escalation password (never store this variable in plain text; always use a vault. See :ref:`tip_for_variables_and_vaults`)"
msgstr "``ansible_sudo_password`` ãŸã㯠``ansible_su_password`` ãšåçã§ãç¹æš©ææ Œãã¹ã¯ãŒããèšå®ã§ããŸã (ãã®å€æ°ãå¹³æã§ä¿åãããåžžã« vault ã䜿çšããŠãã ãããã:ref:`tip_for_variables_and_vaults`ããåç
§ããŠãã ãã)ã"
#: ../../rst/inventory_guide/intro_inventory.rst:629
msgid "ansible_become_exe"
msgstr "ansible_become_exe"
#: ../../rst/inventory_guide/intro_inventory.rst:630
msgid "Equivalent to ``ansible_sudo_exe`` or ``ansible_su_exe``, allows you to set the executable for the escalation method selected"
msgstr "``ansible_sudo_exe`` ãŸã㯠``ansible_su_exe`` ãšåçã§ãéžæããææ Œã¡ãœããã®å®è¡ãã¡ã€ã«ãèšå®ã§ããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:632
msgid "ansible_become_flags"
msgstr "ansible_become_flags"
#: ../../rst/inventory_guide/intro_inventory.rst:632
msgid "Equivalent to ``ansible_sudo_flags`` or ``ansible_su_flags``, allows you to set the flags passed to the selected escalation method. This can be also set globally in :file:`ansible.cfg` in the ``sudo_flags`` option"
msgstr "``ansible_sudo_flags`` ãŸã㯠``ansible_su_flags`` ãšåçã§ãéžæãããææ Œæ¹æ³ã«æž¡ããããã©ã°ãèšå®ããããšãã§ããŸãããã㯠``sudo_flags`` ãªãã·ã§ã³ã® :file:`ansible.cfg` ã§ãã°ããŒãã«ã«èšå®ã§ããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:634
msgid "Remote host environment parameters:"
msgstr "ãªã¢ãŒããã¹ãç°å¢ãã©ã¡ãŒã¿ãŒ:"
#: ../../rst/inventory_guide/intro_inventory.rst:642
msgid "ansible_shell_type"
msgstr "ansible_shell_type"
#: ../../rst/inventory_guide/intro_inventory.rst:639
msgid "The shell type of the target system. You should not use this setting unless you have set the :ref:`ansible_shell_executable<ansible_shell_executable>` to a non-Bourne (sh) compatible shell. By default commands are formatted using ``sh``-style syntax. Setting this to ``csh`` or ``fish`` will cause commands executed on target systems to follow those shell's syntax instead."
msgstr "ã¿ãŒã²ããã·ã¹ãã ã®ã·ã§ã«ã¿ã€ãã:ref:`ansible_shell_executable<ansible_shell_executable>` ã Bourne (sh) 以å€ã®äºæã·ã§ã«ã«èšå®ããªãéãããã®èšå®ã¯äœ¿çšããªãã§ãã ãããããã©ã«ãã§ã¯ãã³ãã³ã㯠``sh`` ã¹ã¿ã€ã«ã®æ§æã䜿çšããŠãã©ãŒããããããŸããããã ``csh`` ãŸã㯠``fish`` ã«èšå®ãããšãã¿ãŒã²ããã·ã¹ãã ã§å®è¡ããã³ãã³ããã·ã§ã«ã®æ§æã«åŸããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:651
msgid "ansible_python_interpreter"
msgstr "ansible_python_interpreter"
#: ../../rst/inventory_guide/intro_inventory.rst:647
msgid "The target host python path. This is useful for systems with more than one Python or not located at :command:`/usr/bin/python` such as \\*BSD, or where :command:`/usr/bin/python` is not a 2.X series Python. We do not use the :command:`/usr/bin/env` mechanism as that requires the remote user's path to be set right and also assumes the :program:`python` executable is named python, where the executable might be named something like :program:`python2.6`."
msgstr "ã¿ãŒã²ãããã¹ãã® Python ãã¹ãããã¯ãè€æ°ã® Python ãããã·ã¹ãã ã\\*BSD ãªã©ã® :command:`/usr/bin/python` ã«ãªãã·ã¹ãã ã:command:`/usr/bin/python` ã 2.X ã·ãªãŒãºã® Python 以å€ã®ã·ã¹ãã ã«åœ¹ç«ã¡ãŸãããªã¢ãŒããŠãŒã¶ãŒã®ãã¹ãæ£ããèšå®ããå¿
èŠãããã:program:`python` å®è¡ãã¡ã€ã«ã®ååã python ã§ãããšæ³å®ããããã:command:`/usr/bin/env` ã¡ã«ããºã ã¯äœ¿çšããŸãããå®è¡ãã¡ã€ã«ã®åå㯠:program:`python2.6` ã®ããã«ãªããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:655
msgid "ansible_*_interpreter"
msgstr "ansible_*_interpreter"
#: ../../rst/inventory_guide/intro_inventory.rst:654
msgid "Works for anything such as ruby or perl and works just like :ref:`ansible_python_interpreter<ansible_python_interpreter>`. This replaces shebang of modules which will run on that host."
msgstr "ruby ã perl ãªã©ã®ãããããã®ã§åäœãã:ref:`ansible_python_interpreter<ansible_python_interpreter>` ã®ããã«æ©èœããŸããããã¯ããã®ãã¹ãã§å®è¡ãããã¢ãžã¥ãŒã«ã®ã·ãã³ã«ä»£ãããã®ã§ãã"
#: ../../rst/inventory_guide/intro_inventory.rst:666
msgid "ansible_shell_executable"
msgstr "ansible_shell_executable"
#: ../../rst/inventory_guide/intro_inventory.rst:662
msgid "This sets the shell the ansible controller will use on the target machine, overrides ``executable`` in :file:`ansible.cfg` which defaults to :command:`/bin/sh`. You should really only change it if is not possible to use :command:`/bin/sh` (in other words, if :command:`/bin/sh` is not installed on the target machine or cannot be run from sudo.)."
msgstr "ããã«ãããAnsible ã³ã³ãããŒã©ãŒãã¿ãŒã²ãããã·ã³ã§äœ¿çšããã·ã§ã«ãèšå®ãã:file:`ansible.cfg` ã® ``executable`` ãäžæžãããŸããããã©ã«ã㯠:command:`/bin/sh` ã§ãã:command:`/bin/sh` ã䜿çšã§ããªãå Žåã«ã®ã¿å€æŽããå¿
èŠããããŸã (ã€ãŸãã:command:`/bin/sh` ãã¿ãŒã²ãããã·ã³ã«ã€ã³ã¹ããŒã«ãããŠããªãå ŽåããŸã㯠sudo ããå®è¡ã§ããªãå Žå)ã"
#: ../../rst/inventory_guide/intro_inventory.rst:668
msgid "Examples from an Ansible-INI host file:"
msgstr "Ansible-INI ãã¹ããã¡ã€ã«ã®äŸ:"
#: ../../rst/inventory_guide/intro_inventory.rst:678
msgid "Non-SSH connection types"
msgstr "SSH 以å€ã®æ¥ç¶ã¿ã€ã"
#: ../../rst/inventory_guide/intro_inventory.rst:680
msgid "As stated in the previous section, Ansible executes playbooks over SSH but it is not limited to this connection type. With the host specific parameter ``ansible_connection=<connector>``, the connection type can be changed. The following non-SSH based connectors are available:"
msgstr "åã®ã»ã¯ã·ã§ã³ã§èª¬æããããã«ãAnsible 㯠SSH 㧠Playbook ãå®è¡ããŸããããã®æ¥ç¶ã¿ã€ãã¯å¶éãããŠããŸããããã¹ãåºæã®ãã©ã¡ãŒã¿ãŒ ``ansible_connection=<connector>`` ã§ã¯ãæ¥ç¶ã¿ã€ããå€æŽã§ããŸãã次㮠SSH 以å€ã®ã³ãã¯ã¿ãŒãå©çšã§ããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:684
msgid "**local**"
msgstr "**local**"
#: ../../rst/inventory_guide/intro_inventory.rst:686
msgid "This connector can be used to deploy the playbook to the control machine itself."
msgstr "ãã®ã³ãã¯ã¿ãŒã¯ãPlaybook ãã³ã³ãããŒã«ãã·ã³èªäœã«ãããã€ããããã«äœ¿çšã§ããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:688
msgid "**docker**"
msgstr "**docker**"
#: ../../rst/inventory_guide/intro_inventory.rst:690
msgid "This connector deploys the playbook directly into Docker containers using the local Docker client. The following parameters are processed by this connector:"
msgstr "ãã®ã³ãã¯ã¿ãŒã¯ãããŒã«ã«ã® Docker ã¯ã©ã€ã¢ã³ãã䜿çšã㊠Playbook ãçŽæ¥ Docker ã³ã³ãããŒã«ãããã€ããŸãã以äžã®ãã©ã¡ãŒã¿ãŒã¯ãã®ã³ãã¯ã¿ãŒã«ãã£ãŠåŠçãããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:693
msgid "The name of the Docker container to connect to."
msgstr "æ¥ç¶å
ã® Docker ã³ã³ãããŒã®ååã"
#: ../../rst/inventory_guide/intro_inventory.rst:695
msgid "The user name to operate within the container. The user must exist inside the container."
msgstr "ã³ã³ãããŒå
ã§æäœããããã®ãŠãŒã¶åããŠãŒã¶ãŒã¯ã³ã³ãããŒå
ã«ååšããŠããå¿
èŠããããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:697
msgid "If set to ``true`` the ``become_user`` will be used to operate within the container."
msgstr "``true`` ã«èšå®ãããšã``become_user`` ã¯ã³ã³ãããŒå
ã§åäœããããã«äœ¿çšãããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:699
msgid "ansible_docker_extra_args"
msgstr "ansible_docker_extra_args"
#: ../../rst/inventory_guide/intro_inventory.rst:699
msgid "Could be a string with any additional arguments understood by Docker, which are not command specific. This parameter is mainly used to configure a remote Docker daemon to use."
msgstr "Docker ãèªèããè¿œå ã®åŒæ°ãæã€æååãæå®ã§ããŸãããããã¯ã³ãã³ãåºæã§ã¯ãããŸããããã®ãã©ã¡ãŒã¿ãŒã¯äž»ã«ã䜿çšãããªã¢ãŒã Docker ããŒã¢ã³ãèšå®ããããã«äœ¿çšãããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:701
msgid "Here is an example of how to instantly deploy to created containers:"
msgstr "以äžã¯ãäœæãããã³ã³ãããŒã«å³æã«ãããã€ããäŸã瀺ããŠããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:725
msgid "For a full list with available plugins and examples, see :ref:`connection_plugin_list`."
msgstr "å©çšå¯èœãªãã©ã°ã€ã³ãšãµã³ãã«ã®äžèŠ§ã¯ãã:ref:`connection_plugin_list`ããåç
§ããŠãã ããã"
#: ../../rst/inventory_guide/intro_inventory.rst:727
msgid "If you're reading the docs from the beginning, this may be the first example you've seen of an Ansible playbook. This is not an inventory file. Playbooks will be covered in great detail later in the docs."
msgstr "ããã¥ã¡ã³ããæåããèªãã§ããå Žåããã㯠Ansible Playbook ãåããŠç¢ºèªããäŸã§ããããã¯ã€ã³ãã³ããªãŒãã¡ã€ã«ã§ã¯ãããŸãããPlaybook ã¯ãããã¥ã¡ã³ãã§åŸã»ã©è©³çŽ°ã«èª¬æããŠããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:733
msgid "Inventory setup examples"
msgstr "ã€ã³ãã³ããªãŒã®èšå®äŸ"
#: ../../rst/inventory_guide/intro_inventory.rst:735
msgid "See also :ref:`sample_setup`, which shows inventory along with playbooks and other Ansible artifacts."
msgstr "Playbook ããã³ãã®ä»ã® Ansible ã¢ãŒãã£ãã¡ã¯ããšãšãã«ã€ã³ãã³ããªãŒã衚瀺ããã:ref:`sample_setup`ããåç
§ããŠãã ããã"
#: ../../rst/inventory_guide/intro_inventory.rst:740
msgid "Example: One inventory per environment"
msgstr "äŸ: åç°å¢ã« 1 ã€ã®ã€ã³ãã³ããªãŒ"
#: ../../rst/inventory_guide/intro_inventory.rst:742
msgid "If you need to manage multiple environments it's sometimes prudent to have only hosts of a single environment defined per inventory. This way, it is harder to, for instance, accidentally change the state of nodes inside the \"test\" environment when you actually wanted to update some \"staging\" servers."
msgstr "è€æ°ã®ç°å¢ã管çããå¿
èŠãããå Žåãã€ã³ãã³ããªãŒããšã« 1 ã€ã®ç°å¢ã®ãã¹ãã®ã¿ãå®çŸ©ããããšãè³¢æãªå ŽåããããŸããããããããšã§ãããšãã°ãå®éã«ã¯ãã¹ããŒãžã³ã°ããµãŒããŒãæŽæ°ãããã®ã«ã誀ã£ãŠããã¹ããç°å¢å
ã®ããŒãã®ç¶æ
ãå€æŽããŠããŸãããšãèµ·ããã«ãããªããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:748
msgid "For the example mentioned above you could have an :file:`inventory_test` file:"
msgstr "åè¿°ã®äŸã§ã¯ã:file:`inventory_test` ãšãããã¡ã€ã«ããããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:762
msgid "That file only includes hosts that are part of the \"test\" environment. Define the \"staging\" machines in another file called :file:`inventory_staging`:"
msgstr "ãã®ãã¡ã€ã«ã«ã¯ãããã¹ããç°å¢ã«å«ãŸãããã¹ãã®ã¿ãå«ãŸããŸãã:file:`inventory_staging` ãšåŒã°ããå¥ã®ãã¡ã€ã«ã®ãã¹ããŒãžã³ã°ããã·ã³ãå®çŸ©ããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:777
msgid "To apply a playbook called :file:`site.yml` to all the app servers in the test environment, use the following command:"
msgstr "`site.yml` ãšããååã® Playbook ããã¹ãç°å¢ã®ãã¹ãŠã®ã¢ããªã±ãŒã·ã§ã³ãµãŒããŒã«é©çšããã«ã¯ã次ã®ã³ãã³ãã䜿çšããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:788
msgid "Example: Group by function"
msgstr "äŸ: æ©èœå¥ã«ã°ã«ãŒãå"
#: ../../rst/inventory_guide/intro_inventory.rst:790
msgid "In the previous section you already saw an example for using groups in order to cluster hosts that have the same function. This allows you, for instance, to define firewall rules inside a playbook or role affecting only database servers:"
msgstr "åã»ã¯ã·ã§ã³ã§ã¯ãåãæ©èœãæã€ãã¹ããã¯ã©ã¹ã¿ãŒåããããã«ãã°ã«ãŒãã䜿çšããäŸããã§ã«æ瀺ããŠããŸããããã«ãããããŒã¿ããŒã¹ãµãŒããŒã ãã«åœ±é¿ãã Playbook ãŸãã¯ããŒã«å
ã§ãã¡ã€ã¢ãŠã©ãŒã«ã«ãŒã«ãå®çŸ©ã§ããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:808
msgid "Example: Group by location"
msgstr "äŸ: å Žæå¥ã«ã°ã«ãŒãå"
#: ../../rst/inventory_guide/intro_inventory.rst:810
msgid "Other tasks might be focused on where a certain host is located. Let's say that ``db01.test.example.com`` and ``app01.test.example.com`` are located in DC1 while ``db02.test.example.com`` is in DC2:"
msgstr "ãŸããç¹å®ã®ãã¹ããã©ãã«ãããã«çŠç¹ãåœãŠãã¿ã¹ã¯ããããŸããããšãã°ã``db01.test.example.com`` ãš ``app01.test.example.com`` ã DC1 ã«ããã``db02.test.example.com`` ã DC2 ã«ãããšããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:823
msgid "In practice, you might even end up mixing all these setups as you might need to, on one day, update all nodes in a specific data center while, on another day, update all the application servers no matter their location."
msgstr "å®éã«ã¯ãããšãã°ç¹å®ã®ããŒã¿ã»ã³ã¿ãŒå
ã®ãã¹ãŠã®ããŒããæŽæ°ããæ¥ãšã眮ãããŠããå Žæã«é¢ä¿ãªããã¹ãŠã®ã¢ããªã±ãŒã·ã§ã³ãµãŒããŒãæŽæ°ããæ¥ãå¿
èŠã«ãªããããããããã¹ãŠã®èšå®ãçµã¿åãããŠäœ¿çšããããšããããŸãã"
#: ../../rst/inventory_guide/intro_inventory.rst:830
msgid ":ref:`inventory_plugins`"
msgstr ":ref:`inventory_plugins`"
#: ../../rst/inventory_guide/intro_inventory.rst:831
msgid "Pulling inventory from dynamic or static sources"
msgstr "åçãœãŒã¹ãŸãã¯éçãœãŒã¹ããã®ã€ã³ãã³ããªãŒã®ãã«"
#: ../../rst/inventory_guide/intro_inventory.rst:832
msgid ":ref:`intro_dynamic_inventory`"
msgstr ":ref:`intro_dynamic_inventory`"
#: ../../rst/inventory_guide/intro_inventory.rst:833
msgid "Pulling inventory from dynamic sources, such as cloud providers"
msgstr "ã¯ã©ãŠããããã€ããŒãªã©ã®åçãœãŒã¹ããã®ã€ã³ãã³ããªãŒã®ãã«"
#: ../../rst/inventory_guide/intro_inventory.rst:834
#: ../../rst/inventory_guide/intro_patterns.rst:246
msgid ":ref:`intro_adhoc`"
msgstr ":ref:`intro_adhoc`"
#: ../../rst/inventory_guide/intro_inventory.rst:835
#: ../../rst/inventory_guide/intro_patterns.rst:247
msgid "Examples of basic commands"
msgstr "åºæ¬ã³ãã³ãã®äŸ"
#: ../../rst/inventory_guide/intro_inventory.rst:836
#: ../../rst/inventory_guide/intro_patterns.rst:248
msgid ":ref:`working_with_playbooks`"
msgstr ":ref:`working_with_playbooks`"
#: ../../rst/inventory_guide/intro_inventory.rst:837
msgid "Learning Ansible's configuration, deployment, and orchestration language."
msgstr "Ansible ã®èšå®ããããã€ã¡ã³ããããã³ãªãŒã±ã¹ãã¬ãŒã·ã§ã³èšèªã«ã€ããŠ"
#: ../../rst/inventory_guide/intro_patterns.rst:4
msgid "Patterns: targeting hosts and groups"
msgstr "ãã¿ãŒã³: ãã¹ãããã³ã°ã«ãŒãã察象ãšãã"
#: ../../rst/inventory_guide/intro_patterns.rst:6
msgid "When you execute Ansible through an ad hoc command or by running a playbook, you must choose which managed nodes or groups you want to execute against. Patterns let you run commands and playbooks against specific hosts and/or groups in your inventory. An Ansible pattern can refer to a single host, an IP address, an inventory group, a set of groups, or all hosts in your inventory. Patterns are highly flexible - you can exclude or require subsets of hosts, use wildcards or regular expressions, and more. Ansible executes on all inventory hosts included in the pattern."
msgstr "ã¢ãããã¯ã³ãã³ããŸã㯠Playbook ãã Ansible ãå®è¡ããå Žåã¯ãå®è¡ãã管çããŒããŸãã¯ã°ã«ãŒããéžæããå¿
èŠããããŸãããã¿ãŒã³ã«ãããã€ã³ãã³ããªãŒå
ã®ç¹å®ã®ãã¹ããã°ã«ãŒãã«å¯ŸããŠã³ãã³ããš Playbook ãå®è¡ã§ããŸããAnsible ãã¿ãŒã³ã¯ã1 å°ã®ãã¹ããIP ã¢ãã¬ã¹ãã€ã³ãã³ããªãŒã°ã«ãŒããã°ã«ãŒãã»ããããŸãã¯ã€ã³ãã³ããªãŒå
ã®ãã¹ãŠã®ãã¹ããåç
§ã§ããŸãããã¿ãŒã³ã¯æè»æ§ãé«ãããã¹ãã®ãµãã»ãããé€å€ãŸãã¯èŠæ±ããããã¯ã€ã«ãã«ãŒããæ£èŠè¡šçŸã䜿çšãããã§ããŸããAnsible ã¯ããã¿ãŒã³ã«å«ãŸãããã¹ãŠã®ã€ã³ãã³ããªãŒãã¹ãã§å®è¡ããŸãã"
#: ../../rst/inventory_guide/intro_patterns.rst:16
msgid "Using patterns"
msgstr "ãã¿ãŒã³ã®äœ¿çš"
#: ../../rst/inventory_guide/intro_patterns.rst:18
msgid "You use a pattern almost any time you execute an ad hoc command or a playbook. The pattern is the only element of an :ref:`ad hoc command<intro_adhoc>` that has no flag. It is usually the second element:"
msgstr "ã¢ãããã¯ã³ãã³ããŸã㯠Playbook ãå®è¡ããéã¯ãã»ãŒåžžã«ãã¿ãŒã³ã䜿çšããŸãããã¿ãŒã³ã¯ããã©ã°ã®ãªã :ref:`ã¢ãããã¯ã³ãã³ã<intro_adhoc>` ã®å¯äžã®èŠçŽ ã§ããé垞㯠2 çªç®ã®èŠçŽ ã«ãªããŸãã"
#: ../../rst/inventory_guide/intro_patterns.rst:24
#: ../../rst/inventory_guide/intro_patterns.rst:37
msgid "For example:"
msgstr "äŸ:"
#: ../../rst/inventory_guide/intro_patterns.rst:30
msgid "In a playbook the pattern is the content of the ``hosts:`` line for each play:"
msgstr "Playbook ã§ã¯ããã¿ãŒã³ã¯åãã¬ã€ã® ``hosts:`` è¡ã®å
容ã«ãªããŸãã"
#: ../../rst/inventory_guide/intro_patterns.rst:44
msgid "Since you often want to run a command or playbook against multiple hosts at once, patterns often refer to inventory groups. Both the ad hoc command and the playbook above will execute against all machines in the ``webservers`` group."
msgstr "å€ãã®å Žåã¯ãã³ãã³ããŸã㯠Playbook ãè€æ°ã®ãã¹ãã«å¯ŸããŠäžåºŠã«å®è¡ããããããã¿ãŒã³ã¯å€ãã®å Žåã€ã³ãã³ããªãŒã°ã«ãŒããåç
§ããŸããã¢ãããã¯ã³ãã³ããšäžèšã® Playbook ã¯ã``webservers`` ã°ã«ãŒãã®ãã¹ãŠã®ãã·ã³ã«å¯ŸããŠå®è¡ãããŸãã"
#: ../../rst/inventory_guide/intro_patterns.rst:49
msgid "Common patterns"
msgstr "äžè¬çãªãã¿ãŒã³"
#: ../../rst/inventory_guide/intro_patterns.rst:51
msgid "This table lists common patterns for targeting inventory hosts and groups."
msgstr "以äžã®è¡šã¯ãã€ã³ãã³ããªãŒãã¹ãããã³ã°ã«ãŒãã察象ã«èšå®ããäžè¬çãªãã¿ãŒã³ã瀺ããŠããŸãã"
#: ../../rst/inventory_guide/intro_patterns.rst:57
msgid "Description"
msgstr "説æ"
#: ../../rst/inventory_guide/intro_patterns.rst:57
msgid "Pattern(s)"
msgstr "ãã¿ãŒã³"
#: ../../rst/inventory_guide/intro_patterns.rst:57
msgid "Targets"
msgstr "ã¿ãŒã²ãã"
#: ../../rst/inventory_guide/intro_patterns.rst:59
msgid "All hosts"
msgstr "ãã¹ãŠã®ãã¹ã"
#: ../../rst/inventory_guide/intro_patterns.rst:59
msgid "all (or \\*)"
msgstr "all (ãŸã㯠\\*)"
#: ../../rst/inventory_guide/intro_patterns.rst:61
msgid "One host"
msgstr "1 å°ã®ãã¹ã"
#: ../../rst/inventory_guide/intro_patterns.rst:61
msgid "host1"
msgstr "host1"
#: ../../rst/inventory_guide/intro_patterns.rst:63
msgid "Multiple hosts"
msgstr "è€æ°ã®ãã¹ã"
#: ../../rst/inventory_guide/intro_patterns.rst:63
msgid "host1:host2 (or host1,host2)"
msgstr "host1:host2 (ãŸã㯠host1,host2)"
#: ../../rst/inventory_guide/intro_patterns.rst:65
msgid "One group"
msgstr "1 ã€ã®ã°ã«ãŒã"
#: ../../rst/inventory_guide/intro_patterns.rst:65
msgid "webservers"
msgstr "webservers"
#: ../../rst/inventory_guide/intro_patterns.rst:67
msgid "Multiple groups"
msgstr "è€æ°ã°ã«ãŒã"
#: ../../rst/inventory_guide/intro_patterns.rst:67
msgid "webservers:dbservers"
msgstr "webservers:dbservers"
#: ../../rst/inventory_guide/intro_patterns.rst:67
msgid "all hosts in webservers plus all hosts in dbservers"
msgstr "webservers äžã®ãã¹ãŠã®ãã¹ããšãdbservers äžã®ãã¹ãŠã®ãã¹ã"
#: ../../rst/inventory_guide/intro_patterns.rst:69
msgid "Excluding groups"
msgstr "ã°ã«ãŒãã®é€å€"
#: ../../rst/inventory_guide/intro_patterns.rst:69
msgid "webservers:!atlanta"
msgstr "webservers:!atlanta"
#: ../../rst/inventory_guide/intro_patterns.rst:69
msgid "all hosts in webservers except those in atlanta"
msgstr "atlanta äžã®ãã¹ããé€ã webservers ã®ãã¹ãŠã®ãã¹ã"
#: ../../rst/inventory_guide/intro_patterns.rst:71
msgid "Intersection of groups"
msgstr "ã°ã«ãŒãã®äº€å·®éšå"
#: ../../rst/inventory_guide/intro_patterns.rst:71
msgid "webservers:&staging"
msgstr "webservers:&staging"
#: ../../rst/inventory_guide/intro_patterns.rst:71
msgid "any hosts in webservers that are also in staging"
msgstr "ã¹ããŒãžç¶æ
ã«ãã webservers ã®ãã¹ãŠã®ãã¹ã"
#: ../../rst/inventory_guide/intro_patterns.rst:74
msgid "You can use either a comma (``,``) or a colon (``:``) to separate a list of hosts. The comma is preferred when dealing with ranges and IPv6 addresses."
msgstr "ãã¹ãã®ãªã¹ããåé¢ããã«ã¯ãã³ã³ã (``,``) ãŸãã¯ã³ãã³ (``:``) ã®ããããã䜿çšã§ããŸããã³ã³ãã¯ãç¯å²ããã³ IPv6 ã¢ãã¬ã¹ãåŠçããå Žåã«æšå¥šãããŸãã"
#: ../../rst/inventory_guide/intro_patterns.rst:76
msgid "Once you know the basic patterns, you can combine them. This example:"
msgstr "åºæ¬çãªãã¿ãŒã³ãææ¡ãããããããçµã¿åãããããšãã§ããŸãã以äžã«äŸã瀺ããŸãã"
#: ../../rst/inventory_guide/intro_patterns.rst:82
msgid "targets all machines in the groups 'webservers' and 'dbservers' that are also in the group 'staging', except any machines in the group 'phoenix'."
msgstr "ãphoenixãã°ã«ãŒãã®ãã·ã³ãé€ãããstagingãã°ã«ãŒãã«ãããwebserversãã°ã«ãŒãããã³ãdbserversãã°ã«ãŒãã«ãããã¹ãŠã®ãã·ã³ã察象ãšããŸãã"
#: ../../rst/inventory_guide/intro_patterns.rst:85
msgid "You can use wildcard patterns with FQDNs or IP addresses, as long as the hosts are named in your inventory by FQDN or IP address:"
msgstr "ãã¹ããã€ã³ãã³ããªãŒã§ FQDN ãŸã㯠IP ã¢ãã¬ã¹ã«ããååãä»ããããŠããéããFQDN ãŸã㯠IP ã¢ãã¬ã¹ã§ã¯ã€ã«ãã«ãŒããã¿ãŒã³ã䜿çšã§ããŸãã"
#: ../../rst/inventory_guide/intro_patterns.rst:93
msgid "You can mix wildcard patterns and groups at the same time:"
msgstr "ã¯ã€ã«ãã«ãŒããã¿ãŒã³ããã³ã°ã«ãŒããåæã«çµã¿åãããããšãã§ããŸãã"
#: ../../rst/inventory_guide/intro_patterns.rst:100
msgid "Limitations of patterns"
msgstr "ãã¿ãŒã³ã®å¶é"
#: ../../rst/inventory_guide/intro_patterns.rst:102
msgid "Patterns depend on inventory. If a host or group is not listed in your inventory, you cannot use a pattern to target it. If your pattern includes an IP address or hostname that does not appear in your inventory, you will see an error like this:"
msgstr "ãã¿ãŒã³ã¯ã€ã³ãã³ããªãŒã«ãã£ãŠç°ãªããŸãããã¹ããŸãã¯ã°ã«ãŒããã€ã³ãã³ããªãŒã«èšèŒãããŠããªãå Žåã¯ãã¿ãŒã²ããã«ãã¿ãŒã³ã䜿çšããããšã¯ã§ããŸãããã€ã³ãã³ããªãŒã«è¡šç€ºãããªã IP ã¢ãã¬ã¹ãŸãã¯ãã¹ãåããã¿ãŒã³ã«å«ãŸããŠããå Žåã¯ã以äžã®ãããªãšã©ãŒã衚瀺ãããŸãã"
#: ../../rst/inventory_guide/intro_patterns.rst:109
msgid "Your pattern must match your inventory syntax. If you define a host as an :ref:`alias<inventory_aliases>`:"
msgstr "ã䜿ãã®ãã¿ãŒã³ã¯ã€ã³ãã³ããªãŒæ§æã«äžèŽããå¿
èŠããããŸãããã¹ãã :ref:`ãšã€ãªã¢ã¹<inventory_aliases>` ãšããŠå®çŸ©ããå Žåã¯ã以äžãæå®ããŸãã"
#: ../../rst/inventory_guide/intro_patterns.rst:119
msgid "you must use the alias in your pattern. In the example above, you must use ``host1`` in your pattern. If you use the IP address, you will once again get the error:"
msgstr "ãã¿ãŒã³ã§ãšã€ãªã¢ã¹ã䜿çšããå¿
èŠããããŸããäžèšã®äŸã§ã¯ããã¿ãŒã³ã§ ``host1`` ã䜿çšããå¿
èŠããããŸããIP ã¢ãã¬ã¹ã䜿çšããå Žåã¯ããšã©ãŒãå床衚瀺ãããŸãã"
#: ../../rst/inventory_guide/intro_patterns.rst:126
msgid "Pattern processing order"
msgstr "ãã¿ãŒã³åŠçã®é åº"
#: ../../rst/inventory_guide/intro_patterns.rst:128
msgid "The processing is a bit special and happens in the following order:"
msgstr "åŠçã¯å°ãç¹æ®ã§ã以äžã®é åºã§è¡ãããŸãã"
#: ../../rst/inventory_guide/intro_patterns.rst:130
msgid "``:`` and ``,``"
msgstr "``:`` ããã³ ``,``"
#: ../../rst/inventory_guide/intro_patterns.rst:131
msgid "``&``"
msgstr "``&``"
#: ../../rst/inventory_guide/intro_patterns.rst:132
msgid "``!``"
msgstr "``!``"
#: ../../rst/inventory_guide/intro_patterns.rst:134
msgid "This positioning only accounts for processing order inside each operation: ``a:b:&c:!d:!e == &c:a:!d:b:!e == !d:a:!e:&c:b``"
msgstr "ãã®é
眮ã¯ã``a:b:&c:!d:!e == &c:a:!d:b:!e == !d:a:!e:&c:b`` ãªã©ã®ããã«ãåæäœå
ã®åŠçé åºã®ã¿ãèæ
®ããŠããŸãã"
#: ../../rst/inventory_guide/intro_patterns.rst:137
msgid "All of these result in the following:"
msgstr "ããããã¹ãŠã¯ã以äžã®ããã«ãªããŸãã"
#: ../../rst/inventory_guide/intro_patterns.rst:139
msgid "Host in/is (a or b) AND host in/is all(c) AND host NOT in/is all(d, e)."
msgstr "Host in/is (a or b) AND host in/is all(c) AND host NOT in/is all(d, e)."
#: ../../rst/inventory_guide/intro_patterns.rst:141
msgid "Now ``a:b:!e:!d:&c`` is a slight change as the ``!e`` gets processed before the ``!d``, though this doesn't make much of a difference:"
msgstr "``!e`` ã ``!d`` ããåã«åŠçãããããã«ãªãã``a:b:!e:!d:&c`` ã¯å°ãå€åããŸããããããã¯ç¹ã«å€§ããªéãã¯ãããŸããã"
#: ../../rst/inventory_guide/intro_patterns.rst:143
msgid "Host in/is (a or b) AND host in/is all(c) AND host NOT in/is all(e, d)."
msgstr "Host in/is (a or b) AND host in/is all(c) AND host NOT in/is all(e, d)."
#: ../../rst/inventory_guide/intro_patterns.rst:146
msgid "Advanced pattern options"
msgstr "詳现ãªãã¿ãŒã³ãªãã·ã§ã³"
#: ../../rst/inventory_guide/intro_patterns.rst:148
msgid "The common patterns described above will meet most of your needs, but Ansible offers several other ways to define the hosts and groups you want to target."
msgstr "äžèšã®äžè¬çãªãã¿ãŒã³ã¯ã»ãšãã©ã®ããŒãºã«å¯Ÿå¿ããŸãããAnsible ã§ã¯ã察象ãšãããã¹ãããã³ã°ã«ãŒããå®çŸ©ããä»ã®æ¹æ³ãããã€ãæäŸããŸãã"
#: ../../rst/inventory_guide/intro_patterns.rst:151
msgid "Using variables in patterns"
msgstr "ãã¿ãŒã³ã«ãããå€æ°ã®äœ¿çš"
#: ../../rst/inventory_guide/intro_patterns.rst:153
msgid "You can use variables to enable passing group specifiers via the ``-e`` argument to ansible-playbook:"
msgstr "å€æ°ã䜿ããšãansible-playbook ã® ``-e`` åŒæ°ã§ã°ã«ãŒãæå®åãæž¡ããããã«ãªããŸãã"
#: ../../rst/inventory_guide/intro_patterns.rst:160
msgid "Using group position in patterns"
msgstr "ãã¿ãŒã³ã«ãããã°ã«ãŒãã®äœçœ®ã®äœ¿çš"
#: ../../rst/inventory_guide/intro_patterns.rst:162
msgid "You can define a host or subset of hosts by its position in a group. For example, given the following group:"
msgstr "ã°ã«ãŒãå
ã®äœçœ®ã«ãã£ãŠããã¹ãããã¹ãã®ãµãã»ãããå®çŸ©ããããšãã§ããŸããããšãã°ã次ã®ãããªã°ã«ãŒããæå®ãããå Žåã§ãã"
#: ../../rst/inventory_guide/intro_patterns.rst:171
msgid "you can use subscripts to select individual hosts or ranges within the webservers group:"
msgstr "subscripts ã䜿çšããŠãwebservers ã°ã«ãŒãå
ã®ãã¹ããŸãã¯ç¯å²ãåå¥ã«éžæã§ããŸãã"
#: ../../rst/inventory_guide/intro_patterns.rst:183
msgid "Using regexes in patterns"
msgstr "ãã¿ãŒã³ã§æ£èŠè¡šçŸã®äœ¿çš"
#: ../../rst/inventory_guide/intro_patterns.rst:185
msgid "You can specify a pattern as a regular expression by starting the pattern with ``~``:"
msgstr "ãã¿ãŒã³ãæ£èŠè¡šçŸãšããŠæå®ããã«ã¯ã``~`` ã§ãã¿ãŒã³ãéå§ããŸãã"
#: ../../rst/inventory_guide/intro_patterns.rst:192
msgid "Patterns and ad-hoc commands"
msgstr "ãã¿ãŒã³ããã³ã¢ãããã¯ã³ãã³ã"
#: ../../rst/inventory_guide/intro_patterns.rst:194
msgid "You can change the behavior of the patterns defined in ad-hoc commands using command-line options. You can also limit the hosts you target on a particular run with the ``--limit`` flag."
msgstr "ã³ãã³ãã©ã€ã³ãªãã·ã§ã³ã䜿çšããŠãã¢ãããã¯ã³ãã³ãã§å®çŸ©ããããã¿ãŒã³ã®åäœãå€æŽã§ããŸãããŸãã``--limit`` ãã©ã°ã䜿çšããŠãç¹å®ã®å®è¡ã§å¯Ÿè±¡ãšãããã¹ããå¶éããããšãã§ããŸãã"
#: ../../rst/inventory_guide/intro_patterns.rst:197
msgid "Limit to one host"
msgstr "1 å°ã®ãã¹ãã«å¶éãã"
#: ../../rst/inventory_guide/intro_patterns.rst:203
msgid "Limit to multiple hosts"
msgstr "è€æ°ã®ãã¹ãã«å¶éãã"
#: ../../rst/inventory_guide/intro_patterns.rst:209
msgid "Negated limit. Note that single quotes MUST be used to prevent bash interpolation."
msgstr "åŠå®çãªå¶éãbash ã®è£éãé²ãããã«ãäžéåŒçšç¬Šã䜿çšããå¿
èŠããããŸãã"
#: ../../rst/inventory_guide/intro_patterns.rst:215
msgid "Limit to host group"
msgstr "ãã¹ãã°ã«ãŒãã«å¶éãã"
#: ../../rst/inventory_guide/intro_patterns.rst:222
msgid "Patterns and ansible-playbook flags"
msgstr "ãã¿ãŒã³ããã³ ansible-playbook ãã©ã°"
#: ../../rst/inventory_guide/intro_patterns.rst:224
msgid "You can change the behavior of the patterns defined in playbooks using command-line options. For example, you can run a playbook that defines ``hosts: all`` on a single host by specifying ``-i 127.0.0.2,`` (note the trailing comma). This works even if the host you target is not defined in your inventory, but this method will NOT read your inventory for variables tied to this host and any variables required by the playbook will need to be specified manually at the command line. You can also limit the hosts you target on a particular run with the ``--limit`` flag, which will reference your inventory:"
msgstr "ã³ãã³ãã©ã€ã³ãªãã·ã§ã³ã䜿çšã㊠Playbook ã§å®çŸ©ãããã¿ãŒã³ã®åäœãå€æŽã§ããŸããããšãã°ã``-i 127.0.0.2,`` (æ«å°Ÿã®ã³ã³ã) ãæå®ããŠãåäžã®ãã¹ã㧠``hosts: all`` ãå®çŸ©ãã Playbook ãå®è¡ããããšãã§ããŸããããã¯ã察象ãšãããã¹ããã€ã³ãã³ããªãŒã«å®çŸ©ãããŠããªãå Žåã§ãæå¹ã§ãããã ãããã®ææ³ã§ã¯ãã®ãã¹ãã«çµã³ä»ããããå€æ°ã®ã€ã³ãã³ããªãŒãèªã¿åããããPlaybookãå¿
èŠãšãããã¹ãŠã®å€æ°ãã³ãã³ãã©ã€ã³ã§æåã§æå®ããå¿
èŠããããŸãããŸãã``--limit`` ãã©ã°ã䜿çšããŠãç¹å®ã®å®è¡ã§å¯Ÿè±¡ãšãããã¹ããå¶éããããšãã§ããŸããããã«ãããã€ã³ãã³ããªãŒãåç
§ãããŸãã"
#: ../../rst/inventory_guide/intro_patterns.rst:230
msgid "Finally, you can use ``--limit`` to read the list of hosts from a file by prefixing the file name with ``@``:"
msgstr "æåŸã« ``--limit`` ã䜿çšããŠããã¡ã€ã«åã®åã« ``@`` ãä»ããããšã§ããã¡ã€ã«ãããã¹ãã®ãªã¹ããèªã¿èŸŒãããšãã§ããŸãã"
#: ../../rst/inventory_guide/intro_patterns.rst:236
msgid "If :ref:`RETRY_FILES_ENABLED` is set to ``True``, a ``.retry`` file will be created after the ``ansible-playbook`` run containing a list of failed hosts from all plays. This file is overwritten each time ``ansible-playbook`` finishes running."
msgstr ":ref:`RETRY_FILES_ENABLED` ã ``True`` ã«èšå®ãããŠããå Žåã¯ã``ansible-playbook`` ã®å®è¡åŸã«ããã¹ãŠã®ãã¬ã€ã§å€±æãããã¹ãã®ãªã¹ããå«ã ``.retry`` ãã¡ã€ã«ãäœæãããŸãããã®ãã¡ã€ã«ã¯ã``ansible-playbook`` ã®å®è¡ãçµäºãããã³ã«äžæžããããŸãã"
#: ../../rst/inventory_guide/intro_patterns.rst:242
msgid "To apply your knowledge of patterns with Ansible commands and playbooks, read :ref:`intro_adhoc` and :ref:`playbooks_intro`."
msgstr "Ansible ã³ãã³ãããã³ Playbook ã§ãã¿ãŒã³ã«é¢ããç¥èã掻çšããã«ã¯ãã:ref:`intro_adhoc`ãããã³ã:ref:`playbooks_intro`ããåç
§ããŠãã ããã"
#: ../../rst/inventory_guide/intro_patterns.rst:249
msgid "Learning the Ansible configuration management language"
msgstr "Ansible ã®èšå®ç®¡çèšèªã«ã€ããŠ"
#~ msgid "In Ansible 2.10 and later, inventory scripts moved to their associated collections. Many are now in the `community.general scripts/inventory directory <https://github.com/ansible-collections/community.general/tree/main/scripts/inventory>`_. We recommend you use :ref:`inventory_plugins` instead."
#~ msgstr "Ansible 2.10 以éã§ã¯ãã€ã³ãã³ããªãŒã¹ã¯ãªããã¯é¢é£ããã³ã¬ã¯ã·ã§ã³ã«ç§»åããŸãããçŸåšãå€ãã®ã¹ã¯ãªãã㯠`community.general scripts/inventory directory <https://github.com/ansible-collections/community.general/tree/main/scripts/inventory>`_ ã«ãããŸãã代ããã« :ref:`inventory_plugins` ã䜿çšããããšãæšå¥šãããŸãã"
#~ msgid "To create parent/child relationships for groups: * in INI format, use the ``:children`` suffix * in YAML format, use the ``children:`` entry"
#~ msgstr "ã°ã«ãŒãã®èŠª/åã®é¢ä¿ãäœæããã«ã¯ã * INI 圢åŒã®å Žåã«ã¯ ``:children`` ã®æ¥å°ŸèŸãã * YAML 圢åŒã®å Žå㯠``children:`` ãšã³ããªãŒã䜿çšããŸãã"
|