/usr/share/arc/examples/arc.conf.reference is in libarccommon3v5 5.0.5-1ubuntu1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
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 1425 1426 1427 1428 1429 1430 1431 1432 1433 1434 1435 1436 1437 1438 1439 1440 1441 1442 1443 1444 1445 1446 1447 1448 1449 1450 1451 1452 1453 1454 1455 1456 1457 1458 1459 1460 1461 1462 1463 1464 1465 1466 1467 1468 1469 1470 1471 1472 1473 1474 1475 1476 1477 1478 1479 1480 1481 1482 1483 1484 1485 1486 1487 1488 1489 1490 1491 1492 1493 1494 1495 1496 1497 1498 1499 1500 1501 1502 1503 1504 1505 1506 1507 1508 1509 1510 1511 1512 1513 1514 1515 1516 1517 1518 1519 1520 1521 1522 1523 1524 1525 1526 1527 1528 1529 1530 1531 1532 1533 1534 1535 1536 1537 1538 1539 1540 1541 1542 1543 1544 1545 1546 1547 1548 1549 1550 1551 1552 1553 1554 1555 1556 1557 1558 1559 1560 1561 1562 1563 1564 1565 1566 1567 1568 1569 1570 1571 1572 1573 1574 1575 1576 1577 1578 1579 1580 1581 1582 1583 1584 1585 1586 1587 1588 1589 1590 1591 1592 1593 1594 1595 1596 1597 1598 1599 1600 1601 1602 1603 1604 1605 1606 1607 1608 1609 1610 1611 1612 1613 1614 1615 1616 1617 1618 1619 1620 1621 1622 1623 1624 1625 1626 1627 1628 1629 1630 1631 1632 1633 1634 1635 1636 1637 1638 1639 1640 1641 1642 1643 1644 1645 1646 1647 1648 1649 1650 1651 1652 1653 1654 1655 1656 1657 1658 1659 1660 1661 1662 1663 1664 1665 1666 1667 1668 1669 1670 1671 1672 1673 1674 1675 1676 1677 1678 1679 1680 1681 1682 1683 1684 1685 1686 1687 1688 1689 1690 1691 1692 1693 1694 1695 1696 1697 1698 1699 1700 1701 1702 1703 1704 1705 1706 1707 1708 1709 1710 1711 1712 1713 1714 1715 1716 1717 1718 1719 1720 1721 1722 1723 1724 1725 1726 1727 1728 1729 1730 1731 1732 1733 1734 1735 1736 1737 1738 1739 1740 1741 1742 1743 1744 1745 1746 1747 1748 1749 1750 1751 1752 1753 1754 1755 1756 1757 1758 1759 1760 1761 1762 1763 1764 1765 1766 1767 1768 1769 1770 1771 1772 1773 1774 1775 1776 1777 1778 1779 1780 1781 1782 1783 1784 1785 1786 1787 1788 1789 1790 1791 1792 1793 1794 1795 1796 1797 1798 1799 1800 1801 1802 1803 1804 1805 1806 1807 1808 1809 1810 1811 1812 1813 1814 1815 1816 1817 1818 1819 1820 1821 1822 1823 1824 1825 1826 1827 1828 1829 1830 1831 1832 1833 1834 1835 1836 1837 1838 1839 1840 1841 1842 1843 1844 1845 1846 1847 1848 1849 1850 1851 1852 1853 1854 1855 1856 1857 1858 1859 1860 1861 1862 1863 1864 1865 1866 1867 1868 1869 1870 1871 1872 1873 1874 1875 1876 1877 1878 1879 1880 1881 1882 1883 1884 1885 1886 1887 1888 1889 1890 1891 1892 1893 1894 1895 1896 1897 1898 1899 1900 1901 1902 1903 1904 1905 1906 1907 1908 1909 1910 1911 1912 1913 1914 1915 1916 1917 1918 1919 1920 1921 1922 1923 1924 1925 1926 1927 1928 1929 1930 1931 1932 1933 1934 1935 1936 1937 1938 1939 1940 1941 1942 1943 1944 1945 1946 1947 1948 1949 1950 1951 1952 1953 1954 1955 1956 1957 1958 1959 1960 1961 1962 1963 1964 1965 1966 1967 1968 1969 1970 1971 1972 1973 1974 1975 1976 1977 1978 1979 1980 1981 1982 1983 1984 1985 1986 1987 1988 1989 1990 1991 1992 1993 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 2026 2027 2028 2029 2030 2031 2032 2033 2034 2035 2036 2037 2038 2039 2040 2041 2042 2043 2044 2045 2046 2047 2048 2049 2050 2051 2052 2053 2054 2055 2056 2057 2058 2059 2060 2061 2062 2063 2064 2065 2066 2067 2068 2069 2070 2071 2072 2073 2074 2075 2076 2077 2078 2079 2080 2081 2082 2083 2084 2085 2086 2087 2088 2089 2090 2091 2092 2093 2094 2095 2096 2097 2098 2099 2100 2101 2102 2103 2104 2105 2106 2107 2108 2109 2110 2111 2112 2113 2114 2115 2116 2117 2118 2119 2120 2121 2122 2123 2124 2125 2126 2127 2128 2129 2130 2131 2132 2133 2134 2135 2136 2137 2138 2139 2140 2141 2142 2143 2144 2145 2146 2147 2148 2149 2150 2151 2152 2153 2154 2155 2156 2157 2158 2159 2160 2161 2162 2163 2164 2165 2166 2167 2168 2169 2170 2171 2172 2173 2174 2175 2176 2177 2178 2179 2180 2181 2182 2183 2184 2185 2186 2187 2188 2189 2190 2191 2192 2193 2194 2195 2196 2197 2198 2199 2200 2201 2202 2203 2204 2205 2206 2207 2208 2209 2210 2211 2212 2213 2214 2215 2216 2217 2218 2219 2220 2221 2222 2223 2224 2225 2226 2227 2228 2229 2230 2231 2232 2233 2234 2235 2236 2237 2238 2239 2240 2241 2242 2243 2244 2245 2246 2247 2248 2249 2250 2251 2252 2253 2254 2255 2256 2257 2258 2259 2260 2261 2262 2263 2264 2265 2266 2267 2268 2269 2270 2271 2272 2273 2274 2275 2276 2277 2278 2279 2280 2281 2282 2283 2284 2285 2286 2287 2288 2289 2290 2291 2292 2293 2294 2295 2296 2297 2298 2299 2300 2301 2302 2303 2304 2305 2306 2307 2308 2309 2310 2311 2312 2313 2314 2315 2316 2317 2318 2319 2320 2321 2322 2323 2324 2325 2326 2327 2328 2329 2330 2331 2332 2333 2334 2335 2336 2337 2338 2339 2340 2341 2342 2343 2344 2345 2346 2347 2348 2349 2350 2351 2352 2353 2354 2355 2356 2357 2358 2359 2360 2361 2362 2363 2364 2365 2366 2367 2368 2369 2370 2371 2372 2373 2374 2375 2376 2377 2378 | ####################################################################
##
## Configuration blocks and variables for the ARC services via the arc.conf.
##
## NEVER USE THIS DOCUMENT AS A CONFIGURATION FILE!
## There are out-of-the-box minimal configuration templates provided
## for all services.
##
## The arc.conf configuration file consists of blocks like
## [common], [grid-manager], [gridftpd], [gridftpd/name], [group],
## [data-staging], [nordugridmap], [vo], [cluster], [queue/name],
## [infosys], [infosys/index/name], [infosys/index/name/registration/name].
##
## A block is identified by its blockname. A blockname consists of
## keywords and optionally block identifiers: [gridftpd/jobs] here 'gridftpd' is
## a keyword while 'jobs' is an identifier. Block names must be UNIQUE ([vo] is
## the only exception). A block starts with a unique [blockname] and ends with
## the next [blockname] directive. Currently the following keywords are used in
## the block names: common, grid-manager, gridftpd, group, data-staging,
## nordugridmap, vo, infosys, registration, cluster, queue, logger, acix
##
## Some parts of the configuration file are order-dependent, blocks may require
## other blocks be defined earlier (especially the authorization blocks).
##
## The arc.conf configures all the ARC services, and enabling an ARC service on
## a resource requires the presence of the appropriate configuration blocks.
## The ARC services are the following: gridftpd, A-REX (grid-manager block),
## infosys, infosys registration. The nordugridmap utility is also configured by
## the [nordugridmap] and [vo] block(s) of this file.
##
## For example, to connect a computing cluster to the grid and for it to
## accept grid jobs you should have at least the [common], [grid-manager],
## [infosys], [cluster], [queue/queue_name], [infosys/cluster/registration/name]
## blocks configured. For classic setup with GridFTP interface [gridftpd] and
## [gridftpd/jobs] section are also necessary.
##
## As another example we give the necessary blocks for an Index Service:
## [infosys], [infosys/index/name], [infosys/index/name/registration/name]
##
## Configuration blocks contain (variable, variable value) pairs following the
## syntax: variable="the variable value comes in quotes".
## The quotes around the variable value are a MUST!
## Note that the variable names are CASE-SENSITIVE!
## Unset configuration options (variables) take the default values.
##
## Below we give a detailed description of all the configuration options of the
## different configuration blocks.
##
## WARNING: this file will not work as a configuration template!
##
## Developers: This file is parsed by configuration validation scripts and so
## it is important that it follows the correct syntax. For each block or
## option please add explanatory text with two ## and a space at the
## beginning of the line and then an example with a single # and no spaces at
## the beginning of the line.
##
#####################################################################
### The [common] block ##############################################
## The parameters set within this block are available for all the other blocks.
## These are the config parameters shared by the different components of ARC
## (e.g. grid-manager, infosys)
#[common]
## hostname - the FQDN of the frontend node, optional in the common block but
## MUST be set in the cluster block
#hostname="myhost.org"
## x509_voms_dir path - the path to the directory containing *.lsc files
## needed for checking validity of VOMS extensions. If not specified default
## value /etc/grid-security/vomsdir is used.
#x509_voms_dir="/etc/grid-security/vomsdir"
### LRMS
## ARC supports various LRMS flavours, as listed in this section. For detailed
## description of options please refer to ARC CE sysadmin guide:
## http://www.nordugrid.org/documents/arc-ce-sysadm-guide.pdf
## ONLY ONE LRMS IS ALLOWED. MULTIPLE lrms ENTRIES WILL TRIGGER UNEXPECTED
## BEHAVIOUR.
##
## lrms sets the type of the Local Resource Management System (queue system),
## and optionally - the default queue name, separated with a blank space:
## "lrmstype queue_name". For lrmstype, the following systems are supported
## and can be chosen (one per server):
## fork - simple forking of jobs to the same node as the server
## sge - (Sun/Oracle) Grid Engine
## condor - Condor
## pbs - PBS
## lsf - LSF
## ll - LoadLeveler
## slurm - SLURM
## boinc - Boinc
## PBS has many flavours, ARC currenly supports OpenPBS, PBSPro, ScalablePBS
## and Torque (the official name for ScalablePBS). There is no need to specify
## the flavour or the version number of the PBS, simply write 'pbs'. Similarly,
## there is no need to specify (Sun/Oracle) Grid Engine versions and flavours.
## "lrmstype" MUST be set here, it is a MANDATORY parameter!
## The optional "queue" parameter specifies the default Grid queue of the
## LRMS. Jobs will be submitted to this queue if they do not specify queue
## name in job description. Queue name must match one of the [queue/queue_name]
## block labels, see below.
##
### PBS
#lrms="pbs gridlong"
#lrms="pbs"
## the path to the qstat,pbsnodes,qmgr etc PBS binaries,
## no need to set if PBS is not used
#pbs_bin_path="/usr/bin"
## the path of the PBS server logfiles which are used by A-REX to determine
## whether a PBS job is completed. If not specified, A-REX will use qstat for that.
#pbs_log_path="/var/spool/pbs/server_logs"
### Condor
#lrms="condor"
## condor_rank - If you are not happy with the way Condor picks nodes when
## running jobs, you can define your own ranking algorithm by optionally
## setting the condor_rank attribute. condor_rank should be set to a
## ClassAd float expression that you could use in the Rank attribute
## in a Condor job description.
## Obviously no need to set if Condor is not used. An example:
#condor_rank="(1-LoadAvg/2)*(1-LoadAvg/2)*Memory/1000*KFlops/1000000"
## condor_bin_path - Path to Condor binaries. Must be set if Condor
## is used.
#condor_bin_path=/opt/condor/bin
## condor_bin_path - Path to Condor config file. Must be set if Condor
## is used and the config file is not in its default location
## (/etc/condor/condor_config or ~/condor/condor_config).
## The full path to the file should be given.
#condor_config=/opt/condor/etc/condor_config
### SGE
#lrms="sge"
## sge_bin_path - Path to Sun Grid Engine (SGE) binaries,
## MUST be set if SGE is the LRMS used
#sge_bin_path="/opt/n1ge6/bin/lx24-x86"
## sge_root - Path to SGE installation directory. MUST be set if SGE is used.
#sge_root="/opt/n1ge6"
## sge_cell - The name of the SGE cell to use. This option is only necessary
## in case SGE is set up with a cell name different from 'default'
#sge_cell="default"
## sge_qmaster_port, sge_execd_port - these options should be used in case SGE
## command line clients requre SGE_QMASTER_PORT and SGE_EXECD_PORT environment
## variables to be set. Usually they are not necessary.
#sge_qmaster_port="536"
#sge_execd_port="537"
### SLURM
#lrms="slurm"
## slurm_bin_path - Path to SLURM binaries, must be set if installed
## outside of normal $PATH
#slurm_bin_path="/usr/bin"
## How long should infosys wait before querying SLURM for new data (seconds)
#slurm_wakeupperiod="15"
## Should ARC use sacct instead of scontrol to get information about finished jobs
#slurm_use_sacct="yes"
### LSF
#lrms="lsf"
## the PATH to LSF bin folder
## no need to set if LSF is not used
#lsf_bin_path="/usr/local/lsf/bin/"
## the PATH to profile.lsf
## no need to set if LSF is not used
#lsf_profile_path="/usr/share/lsf/conf"
### LoadLeveler
#lrms="ll"
## the PATH to the LoadLeveler bin folder
## no need to set if LoadLeveler is not used
#ll_bin_path="/opt/ibmll/LoadL/full/bin"
## support for a LoadLeveler setup using Consumable Resources
## no need to set if LoadLeveler is not used
#ll_consumable_resources="yes"
### Desktop Bridge
#lrms="dgbridge"
## Desktop Bridge www publish dir
#dgbridge_stage_dir="/var/www/DGBridge"
## Desktop Bridge url prefix pointing to dgbridge_stage_dir
#dgbridge_stage_prepend="http://edgi-bridge.example.com/DGBridge/"
### Boinc
#lrms="boinc"
## Connection strings for the boinc database
#boinc_db_host="localhost"
#boinc_db_port="3306"
#boinc_db_name="myproject"
#boinc_db_user="boinc"
#boinc_db_pass="password"
### Globus specifics
## globus_tcp_port_range, globus_udp_port_range - Firewall configuration
## In a firewalled environment the software which uses GSI needs to know what
## ports are available. The full documentation can be found at:
## http://dev.globus.org/wiki/FirewallHowTo
## These variable are similar to the Globus enviroment variables:
## GLOBUS_TCP_PORT_RANGE and GLOBUS_UDP_PORT_RANGE.
## These variables are not limited to [common], but can be set individually
## for each service in corresponding section: [grid-manager], [gridftpd]
## Example:
#globus_tcp_port_range="9000,12000"
#globus_udp_port_range="9000,12000"
### Certificates
## x509_user_cert, x509_user_key - Server credentials location.
## These variables are similar to the GSI enviroment variables:
## X509_USER_KEY and X509_USER_CERT
## These variables are not limited to [common], but can be set individually
## for each service in corresponding section: [grid-manager], [gridftpd], [nordugridmap]
#x509_user_key="/etc/grid-security/hostkey.pem"
#x509_user_cert="/etc/grid-security/hostcert.pem"
## x509_cert_dir - Location of trusted CA certificates
## This variable is similar to the GSI enviroment variable: X509_CERT_DIR
## This variable is not limited to [common], but can be set individually
## for each service in corresponding section: [grid-manager], [gridftpd]
#x509_cert_dir="/etc/grid-security/certificates"
### Authorization
## gridmap - The gridmap file location
## This variable is similar to the GSI enviroment variable: GRIDMAP
## This variable is not limited to [common], but can be set individually
## for each service in corresponding section: [grid-manager], [gridftpd]
## The default is /etc/grid-security/grid-mapfile
#gridmap="/etc/grid-security/grid-mapfile"
## voms_processing - Defines how to behave if errors in VOMS AC processing detected.
## relaxed - use everything that passed validation.
## standard - same as relaxed but fail if parsing errors took place and
## VOMS extension is marked as critical. This is a default.
## strict - fail if any parsing error was discovered.
## noerrors - fail if any parsing or validation error happened.
## This command can also be used in [grid-manager] and [griftpd] blocks.
#voms_processing="standard"
## voms_trust_chain - Define the DN chain that the host services trust when the
## voms AC from peer voms proxy certificate is parsed and validated.
## There can be multiple "voms_trust_chain" existing, each one corresponds to a voms server.
## This variable is similar to the information in *.lsc file, but with two differences:
## 1, you don't need to create a *.lsc file per VOMS server, but create a chain per VOMS server;
## 2, the regular expression is support when matching the DNs.
## This variable is not limited to [common], but can be used in [grid-manager]
## and [gridftpd] blocks.
## This variable should be used together with voms_processing.
## This variable will overwrite the information in *.lsc if *.lsc exists.
#voms_trust_chain = "/O=Grid/O=NorduGrid/CN=host/arthur.hep.lu.se" "/O=Grid/O=NorduGrid/CN=NorduGrid Certification Authority"
#voms_trust_chain = "/O=Grid/O=NorduGrid/CN=host/emi-arc.eu" "/O=Grid/O=NorduGrid/CN=NorduGrid Certification Authority"
#voms_trust_chain = "^/O=Grid/O=NorduGrid"
### [vo] block #####################################################
##
## [vo] block is used to define VOs and generate mapfiles from user
## list maintained by VO databases. VO block is a configuration block
## for the nordugridmap utility.
## Please note that [vo] block processing by nordugridmap utility
## depend on parameters defined in the [nordugridmap] block.
## [vo] block by itself does not affect authorization of client/user. For
## that label defined by vo="" atribute may be used in [group] block with
## 'vo' rule. Also mapfiles generated by nordugridmap utility can be used
## with 'file' rule.
##
#[vo]
## id blockid - specifies the unique configuration block id (this does not
## affect nordugridmap utility)
#id="vo_1"
## vo vo_name - specifies the VO name, this name can be used in other blocks.
## MUST be given.
#vo="nordugrid"
## file path - output gridmap-file where GENERATED mapping list will be
## stored. See parameters below to define how to generate this file.
## If the same file specified as output for different [vo] blocks,
## nordugridmap will automatically merge enrties in given blocks order.
## Default is '/etc/grid-security/gridmapfile'.
#file="/etc/grid-security/VOs/atlas-users"
## source url - the URL of the VO database which is assigned to this VO.
## The nordugridmap will use this URL to automatically generate and keep
## up-to-date userlist (mapfile) specified by the 'file' attribute.
##
## url is a multivalued attribute, several sources can be specified for
## the [vo] block and all the users from those sources will be merged
## into the same file. The source URLs are processed in the given order.
##
## Currently supported URL types are:
## http(s):// - URL to plain text file. File should contain a list
## of DNs with optional issuer certificate authority DN
## (see require_issuerdn): "user DN" ["issuer DN"]
## voms(s):// - URL to VOMS-Admin interface
## nordugrid - add NorduGrid VO members
## ldap:// - expect LDAP-schema formatted VO Group
## file:// - local file (stand-alone or dynamicaly generated by
## nordugridmap). File should contain a list of DNs with
## optional mapped unixid: "user DN" [mapped user ID]
## Result of optional mapped unixid processing depend
## on mapuser_processing option settings.
## vo:// - reference to another [vo] configuration block
## edg-mkgridmap://
## - local configuration file used by edg-mkgridmap tool.
## nordugridmap will parse configuration from file and
## process it as additional [vo] block that will be refered
## authomatically in place URL specified. This allow
## easy migration from edg-mkgridmap solution without
## rewriting your previous configuration (NOTE that rarely
## used 'auth' directive and 'AUTO' mapping options are not
## supported)
##
## You can use either vo:// or file:// entries to specify dependencies
## between [vo] blocks, but using vo:// is a recommended way.
##
## For each separate source URL it is possible to override some parameters
## value. You can use the following syntax to perform this:
## source="URL < parameter1=value1 parameter2=value2"
## You can override the following parameters:
## mapped_unixid for http(s),voms(s),ldap and file URLs
## cache_enable for http(s),voms(s),ldap and file URLs
## voms_method for voms(s) URLs
## mapuser_processing for file URLs with mapped_unixid='<unixid>' overrided
## (control mapped_unixid overriding behaviour for URL)
#source="vomss://voms.ndgf.org:8443/voms/nordugrid.org"
#source="vomss://lcg-voms.cern.ch:8443/voms/atlas?/atlas/Role=VO-Admin < mapped_unixid=atlasadmin"
#source="vomss://kuiken.nikhef.nl:8443/voms/gin.ggf.org < voms_method=get"
#source="http://www.nordugrid.org/developers.dn"
#source="ldap://grid-vo.nikhef.nl/ou=lcg1,o=atlas,dc=eu-datagrid,dc=org"
#source="file:///etc/grid-security/priviliged_users.dn"
#source="vo://nordugrid_community"
#source="nordugrid"
## mapped_unixid unixid - the local UNIXID which is used in the generated
## grid-mapfile by the nordugridmap utility.
##
## If any of the sources have already provided mapping information (file://
## or vo://) behavior depends on 'mapuser_processing' [nordugridmap] block
## conguration:
## mapuser_processing = 'overwrite': ignore already provided mapping and
## apply mapped_unixid for all sources
## mapuser_processing = 'keep': apply mapped_unixid only for sources that
## does not already has mapping information
##
## [vo] block can only have one UNIXID
## If 'mapped_unixid' is not specified behavior depends on 'allow_empty_unixid'
## [nordugridmap] block conguration value:
## allow_empty_unixid = 'yes': empty value will be used for mapped_unixid
## which means that nordugridmap will generate only
## the list of DNs without mapping (consider using
## mapuser_processing='overwrite' along with this
## option or sources that does not provide previously
## defined mapping information)
## allow_empty_unixid = 'no': skip users without mapping information (if
## no mapping information provided by sources)
##
#mapped_unixid="gridtest"
## voms_fqan_map fqan unixid - the local UNIXID which is used to map voms(s)
## sources with specific FQAN given.
##
## Several voms_fqan_map can be specified for a [vo] block.
## For each voms(s) sources in [vo] block and every voms_fqan_map record
## separate source record will be authomatically generated with mapped_unixid
## overrided to specified one.
##
## Sources are generated in a given voms_fqan_map order. Original voms(s) source
## URL are processed LAST.
##
## This allows to simplify configuration, especially in redundancy cases when
## several VOMS servers are used for the same VO.
##
#voms_fqan_map="/atlas/Role=VO-Admin atlasadmin"
#voms_fqan_map="/atlas/Role=production atlasprod"
## require_issuerdn yes/no - another nordugridmap option. YES would map only
## those DNs obtained from the urls which have the corresponding public CA
## packages installed. Default is 'no'.
##
## Note, that some sources does not provide issuer information (like
## voms(s):// or file://). If this sources are used within [vo] block
## and require_issuerdn is set to 'yes' behavior depends on issuer_processing
## [nordugridmap] block conguration:
## issuer_processing = 'relaxed': check only those records that have issuer
## information provided, allow other sources
## issuer_processing = 'strict': if issuer information was not found record
## is filtered and will not be passed into mapfile
##
#require_issuerdn="no"
## filter ACL string - An ACL filter for the nordugridmap utility. Multiple
## allow/deny statements are possible. The fetched DNs are filtered against
## the specified rules before they are added to the generated mapfile.
##
## * can be used as a wildcard. You may run the nordugridmap with the --test
## command line option to see how the filters you specified work.
##
## If at least one allow filter is specified implicit deny is used at the end
## of ACL. If only deny filters are present - implicit allow used at the end.
#filter="deny *infn*"
#filter="allow *NorduGrid*"
######################################################################
### [group] Authorisation block ######################################
##
## These configuration blocks define rules used to define to which
## authorization group a user belongs. The group should not be mistaken
## for a virtual organisation (VO). A group may match a single vo if
## only a single check (rule) on vo membership is perfomed. It is
## however more common to allow multiple VOs in a single group. ARC
## also allows many other ways to assign users to groups. Technically,
## permissions are only granted to groups, not directly to VOs.
##
## The block specifies single authorization group. Ther may be multiple
## [group] blocks in configuration defining multiple authorization
## groups.
##
## The block can be specified in two ways - either using [group/group1]
## like subblock decalration per group or just [group]. The two formats
## are equivalent. Every block (till the beginning of next block or the
## end of the file) defines one authorization group.
##
## IMPORTANT: Rules in a group are processed in their order of appearance.
## The first matching rule decides the membership of a the user to a group
## and the processing STOPS. There are positively and negatively matching
## rules. If a rule is matched positively then the user tested is accepted
## into the respective group and further processing is stopped. Upon a
## negative match the user would be rejected for that group - processing
## stops too. The sign of rule is determined by prepending the rule with
## '+' (for positive) or '-' (for negative) signs. '+' is default and can
## be omitted. A rule may also be prepended with '!' to invert result of rule,
## which will let the rule match the complement of users. That complement
## operator ('!') may be combined with the operator for positive or negative
## matching.
##
## A group MUST be defined before it may be used. In this respect the
## arc.conf is ORDER SENSITIVE.
##
## The authorization groups can be used in [gridftpd]
## and in its sub-blocks. The syntax of their specification varies with
## the service they are used for.
## For using authorization groups and VO blocks in HED framework please
## read "Security Framework of ARC" at
## http://www.nordugrid.org/documents/arc-security-documentation.pdf
##
#[group]
## name group_name - Specify name of group. If there is no such command
## in block, name of subblock is used instead (that is what subblocks
## are used for). For example [group/users]
#name="users"
## subject certificate_subject - Rule to match specific subject of user's
## X.509 certificate. No masks, patterns and regular expressions are allowed.
## For more information about X.509 refer to http://www.wikipedia.org/wiki/X509
#subject="/O=Grid/O=Big VO/CN=Main Boss"
## file path - Start reading rules from another file. That file has a bit
## different format. It can't contain blocks and commands are separated
## from arguments by space. Also word "subject" in subject command may be
## skipped. That makes it convinient to directly add gridmap-like lists to
## authorization group.
#file="/etc/grid-security/local_users"
## voms vo group role capabilities - Match VOMS attribute in user's credential.
## Use '*' to match any value. More information about VOMS can be found at
## http://grid-auth.infn.it
#voms="nordugrid Guests * *"
## group group_name [group_name ...] - Match user already belonging to one
## of specified groups. Groups refered here must be defined earlier in
## configuration file. Multiple group names may be specified for this rule.
## That allows creating hierarchical structure of authorization groups like
## 'clients' are those which are 'users' and 'admins'.
#group="local_admins"
## plugin timeout path [argument ...] - Run external executable or
## function from shared library. Rule is matched if plugin returns 0.
## In arguments following substitutions are supported:
## %D - subject of certicate
## %P - path to proxy
## For more about plugins read documentation.
#plugin="10 /opt/external/bin/permis %P"
## lcas library directory database - Call LCAS functions to check rule.
## Here library is path to shared library of LCAS, either absolute or
## relative to directory; directory is path to LCAS installation directory,
## equivalent of LCAS_DIR variable; database is path to LCAS database,
## equivalent to LCAS_DB_FILE variable. Each arguments except library is
## optional and may be either skipped or replaced with ’*’.
#lcas=""
## remote URL ... - Check user's credentials against remote service. Only
## DN groups stored at LDAP directories are supported. Multiple URLs are
## allowed in this rule.
#remote="ldap://grid-vo.nordugrid.org/ou=People,dc=nordugrid,dc=org"
## vo vo_name ... - Match user belonging to VO specified by "vo=vo_name" as
## configured in one of PREVIOUSLY defined [vo] blocks. Multiple VO names
## are allowed for this rule.
#vo="nordugrid"
## all - Matches any user identity. This command requires no arguments but
## still can be written as all="" or all= for consistency.
#all=""
######################################################################
### The [grid-manager] block #########################################
## The [grid-manager] block configures the part of A-REX service hosted
## in *arched* and taking care of the grid tasks on the frontend
## (stagein/stageout, LRMS job submission, caching, etc..). Name of this
## block is historical and comes from times then this functionality was
## handled by separate process called grid-manager. This section also
## configures WS interfaces of A-REX service also hosted by same container.
#[grid-manager]
## controldir path - The directory of the A-REX's internal job log files,
## not needed on the nodes. <must be set>
#controldir="/var/spool/nordugrid/jobstatus"
## sessiondir path [drain] - the directory which holds the sessiondirs of the grid jobs.
## Multiple session directories may be specified by specifying multiple sessiondir
## commands. In this case jobs are spread evenly over the session directories.
## If sessiondir="*" is set, the session directory will be spread over the
## ${HOME}/.jobs directories of every locally mapped unix user. It is preferred
## to use common session directories. The path may be followed by "drain", in
## which case no new jobs will be assigned to that sessiondir, but current jobs
## will still be processed and accessible. <sessiondir must be set>
#sessiondir="/scratch/grid"
#sessiondir="/mnt/grid drain"
## runtimedir path - The directory which holds the runtimeenvironment scripts,
## should be available on the nodes as well! the runtimeenvironments are
## automatically detected and advertised in the information system.
#runtimedir="/SOFTWARE/runtime"
## scratchdir path - path on computing node to move session directory to before
## execution. If defined should contain the path to the directory on the
## computing node which can be used to store a jobs' files during execution.
## Sets the environment variable RUNTIME_LOCAL_SCRATCH_DIR. Default is not to
## move session directory before execution.
#scratchdir="/local/scratch/"
## shared_scratch path - path on frontend where scratchdir can be found. If
## defined should contain the path corresponding to that set in scratchdir as
## seen on the frontend machine. Sets the environment variable
## RUNTIME_FRONTEND_SEES_NODE.
#shared_scratch="/mnt/scratch"
## nodename path - command to obtain hostname of computing node.
#nodename="/bin/hostname"
## cachedir cache_path [link_path] - specifies a directory to store cached
## data. Multiple cache directories may be specified by specifying multiple
## cachedir commands. Cached data will be distributed evenly over the caches.
## Specifying no cachedir command or commands with an empty path disables caching.
## Optional link_path specifies the path at which the cache_path is accessible on
## computing nodes, if it is different from the path on the A-REX host.
## Example: cache="/shared/cache /frontend/jobcache"
## If "link-path" is set to '.' files are not soft-linked, but copied to session
## directory. If a cache directory needs to be drained, then cachedir
## should specify "drain" as the link path, in which case no new files will be
## added to the cache.
#cachedir="/scratch/cache"
#cachedir="/fs1/cache drain"
## remotecachedir cache_path [link_path] - specifies caches which are under
## the control of other A-REXs, but which this A-REX can have read-only access to.
## Multiple remote cache directories may be specified by specifying multiple
## remotecachedir commands. If a file is not available in paths specified by
## cachedir, A-REX looks in remote caches. link_path has the same meaning as in
## cachedir, but the special path ``replicate'' means files will
## be replicated from remote caches to local caches when they are requested.
#remotecachedir="/mnt/fs1/cache replicate"
## cachesize max min - specifies high and low watermarks for space used
## by cache, as a percentage of the space on the file system on which
## the cache directory is located. When the max is exceeded, files will
## be deleted to bring the used space down to the min level. It is a
## good idea to have the cache on its own separate file system. To turn
## off this feature "cachesize" without parameters can be specified.
#cachesize="80 70"
## If cache cleaning is enabled, files accessed less recently than the given
## time period will be deleted. Example values of this option are 1800, 90s, 24h,
## 30d. When no suffix is given the unit is seconds.
#cachelifetime="30d"
## cacheshared yes|no - specifies whether the caches share a filesystem with
## other data. If set to yes then cache-clean calculates the size of the cache
## instead of using filesystem used space.
#cacheshared="yes"
## cachespacetool path [options] - specifies an alternative tool to "df" that
## cache-clean should use to obtain space information on the cache file system.
## The output of this command must be "total_bytes used_bytes". The cache
## directory is passed as the last argument to this command.
#cachespacetool="/etc/getspace.sh"
## cachelogfile path - specifies the filename where output of the cache-clean
## tool should be logged. Defaults to /var/log/arc/cache-clean.log.
#cachelogfile="/tmp/cache-clean.log"
## cacheloglevel level - specifies the level of logging by the cache-clean
## tool, between 0 (FATAL) and 5 (DEBUG). Defaults to 3 (INFO).
#cacheloglevel="4"
## cachecleantimeout time - the timeout in seconds for running the cache-clean
## tool. If using a large cache or slow file system this value can be
## increased to allow the cleaning to complete. Defaults to 3600 (1 hour).
#cachecleantimeout="10000"
## cacheaccess rule - rules for allowing access to files in the cache remotely
## through the A-REX web interface. A rule has three parts:
## 1. Regular expression defining a URL pattern
## 2. Credential attribute to match against a client's credential
## 3. Credential value to match against a client's credential
## A client is allowed to access the cached file if a URL pattern matches the
## cached file URL and the client's credential has the attribute and value
## required for that pattern. Possible values for credential attribute are dn,
## voms:vo, voms:role and voms:group. Remote cache access requires that the
## A-REX web interface is enabled via arex_mount_point.
#cacheaccess="gsiftp://host.org/private/data/.* voms:vo myvo:production"
#cacheaccess="gsiftp://host.org/private/data/bob/.* dn /O=Grid/CN=Bob"
## enable_cache_service yes|no - Turn on or off the cache service interface.
## If turned on the cache service must be installed and the A-REX WS interface
## must be enabled via arex_mount_point The interface is accessible at the same
## host and port as given in arex_mount_point with path /cacheservice. Default
## is off.
#enable_cache_service="yes"
## user user[:group] - Switch to a non root user/group after startup.
## Use with caution.
#user="grid"
## debug debuglevel - Set debug level of the arched daemon hosting A-REX service,
## between 0 (FATAL) and 5 (DEBUG). Defaults to 3 (INFO).
#debug="2"
## logfile path - Specify A-REX log file location. If using an external log
## rotation tool be careful to make sure it matches the path specified here.
## Default log file is /var/log/arc/grid-manager.log
#logfile="/var/log/arc/grid-manager.log"
## wslogfile path - Specify log file location for WS-interface operations. This
## file is only created if the WS-interface is enabled through the
## arex_mount_point option. The logsize, logreopen and debug options also apply
## to this file. If using an external log rotation tool be careful to make sure
## it matches the path specified here. It is possible to specify the same file
## as logfile to combine the logs. Default is /var/log/arc/ws-interface.log
#wslogfile="/var/log/arc/ws-interface.log"
## logsize size [number] - 'Size' specifies in bytes how big log file is
## allowed to grow (approximately). If log file exceeds specified size
## it is renamed into logfile.0. And logfile.0 is renamed into
## logfile.1, etc. up to 'number' logfiles. Don't set logsize if you don't
## want to enable the ARC logrotation because another logrotation tool is used.
#logsize="100000 2"
## logreopen yes|no - Specifies if log file must be closed after each record is
## added. By default arched keeps log file open. This option can be used to
## make behavior of arched compatible with external log rotation utilities.
#logreopen="no"
## pidfile path - Specify location of file containing PID of daemon process.
## This is useful for automatic start/stop scripts.
#pidfile="/var/run/arched-arex.pid"
## the gnu time command, default /usr/bin/time
#gnu_time="/usr/bin/time"
## if computing node can access session directory at frontend, defaults to 'yes'
#shared_filesystem="yes"
## specifies the email address from where the notification mails are sent, <must
## be specified>
#mail="grid.support@somewhere.org"
## joblog path - specifies where to store specialized log about started
## and finished jobs. If path is empty or no such command - log is not written.
## This log is not used by any other part of ARC, so keep it disabled unless
## needed.
#joblog="/var/log/arc/gm-jobs.log"
## jobreport [url ...] [timeout] - tells to report all started and finished jobs
## to logger service at 'url'. Multiple urls and multiple jobreport commands
## are allowed. In that case the job info will be sent to all of them.
## Timeout specifies how long (in days) to try to pass information before
## give up. Suggested value is 30 days.
#jobreport="https://grid.uio.no:8001/logger"
## jobreport_vo_filters [VO URL[,VO URL]...] - it is a filter option
## where can be set which VO will be send to the configured jobreport server.
## When add new URL here (that no exist in the list of jobreport) need to
## add this URL into the jobreport element. Multiple VO's are allowed BUT
## only just one jobreport_vo_filters is allowed.
#jobreport_vo_filters="vo1 url1, vo2 url2"
## jobreport publisher - name of the accounting records publisher.
#jobreport_publisher="jura"
## jobreport credentials path [key_file [cert_file [ca_dir]]] - specifies the
## credentials for accessing the accounting service.
#jobreport_credentials="/etc/grid-security/hostkey.pem /etc/grid-security/hostcert.pem /etc/grid-security/certificates"
## jobreport options [name:value, ...]- specifies additional parameters for
## the jobreporter.
#jobreport_options="urbatch:50,archiving:/tmp/archive,topic:/topic/global.accounting.cpu.central
# gocdb_name:GRID_UIO_NO,benchmark_type:HEPSPEC,benchmark_value:2.0,use_ssl:false,
# localid_prefix:prefix_for_SGAS"
# options element can be the followings:
# - urbatch:size
# default size: 50 by SGAS
# 1000 by APEL
# - archiving:directory for the archiving files
# - topic:name of the topic
# - gocdb_name:GOCDB name of CE
# - benchmark_type:type of benchmark (Si2k, Sf2k, HEPSPEC)
# - benchmark_value:value of benchmark
# - benchmark_description:additional description for a benchmark
# - use_ssl:true or false
# default value: false
# - localid_prefix:prefix string for the SGAS records
## jobreport logfile - name of the file to store stderr of the publisher executable.
#jobreport_logfile="/var/log/arc/jura.log"
## max_job_control_requests number - max number of simultaneously processed job management
## requests over WS interface - like job submission, cancel, status check etc.
## Default value is 100.
#max_job_control_requests="100"
## max_infosys_requests number - max number of simultaneously processed resource info
## requests over WS interface. Default value is 1.
#max_infosys_requests="1"
## max_data_transfer_requests number - max number of simultaneously processed data transfer
## requests over WS interface - like data staging.
## Default value is 100.
#max_data_transfer_requests="100"
## maxjobs number1 number2 number3 number4 - specifies maximum allowed number of jobs.
## number1 - jobs which are not in FINISHED state (jobs tracked in RAM)
## number2 - jobs being run (SUBMITTING, INLRMS states)
## number3 - jobs being processed per DN
## number4 - jobs in whole system
## Missing number or -1 means no limit.
#maxjobs="10000 10 2000"
## wakeupperiod time - specifies how often A-REX cheks for new jobs
## arrived, job state change requests, etc. That is resposivity of
## A-REX. 'time' is time period in seconds. Default is 3 minutes.
## Usually this command is not needed because important state changes
## are also trigering out-of-schedule checks.
## NOTE: This parameter does not affect responsivity of backend scripts -
## especially scan-*-job. That means that upper estimation of time for
## detecting job finished executing is sum of responsivity of backend
## script + wakeupperiod.
#wakeupperiod="180"
## defaultttl [ttl [ttr]] - ttl is the time in seconds for how long a session
## directory will survive after job execution has finished. If not specified
## the default is 1 week. ttr is how long information about a job will be kept
## after the session directory is deleted. If not specified, the ttr default is
## one month.
#defaultttl="259200"
## authplugin state options plugin_path - Every time job goes to 'state'
## run 'plugin_path' executable. Options consist of key=value pairs separated
## by ','. Possible keys are
## timeout - wait for result no longer that 'value' seconds (timeout= can be
## omitted).
## onsuccess,onfailure,ontimeout - what to do if plugin exited with exit
## code 0, not 0, timeout achieved. Possible actions are:
## pass - continue executing job,
## fail - cancel job,
## log - write to log fail about problem and continue executing job.
#authplugin="ACCEPTED timeout=10 /usr/libexec/arc/bank %C/job.%I.local %S"
## ARC is distributed with the plugin "inputcheck". It's purpose is
## to check if input files requested in job's RSL are accessible
## from this machine. It is better to run it before job enters cluster.
## It accepts 2 arguments: names of files containing RSL and credentials'
## proxy. This plugin is only guaranteed to work for job submitted through
## the legacy GridFTP interface, as this is the only interface for which
## credentials in the form of proxy certificate files are guaranteed to
## exist.
#authplugin="ACCEPTED 60 /usr/libexec/arc/inputcheck %C/job.%I.description %C/job.%I.proxy"
## ARC is distributed with the plugin "arc-vomsac-check". It's purpose is to enforce
## per-queue access policies based on VOMS attributes present in user's
## proxy-certificate. Plugin should be run before job enters the cluster.
## It requires 2 argments: path to job information .local file and path to
## credentials file.
## Enforced per-queue access policies are configured with 'ac_policy' option
## in the [queue/name] configuration block.
#authplugin="ACCEPTED 60 /usr/libexec/arc/arc-vomsac-check -L %C/job.%I.local -P %C/job.%I.proxy"
## localcred timeout plugin_path - Every time an external executable
## is run this plugin will be called. Its purpose is to set non-unix
## permissions/credentials on running tasks. Note: the process itself
## can still be run under the root account. If plugin_path looks like
## somename@somepath, then function 'somename' from the shared library
## located at 'somepath' will be called (timeout is not effective in
## that case).
## A-REX must be run as root to use this option.
## Comment it out unless you really know what you are doing.
#localcred="0 acquire@/opt/nordugrid/lib/afs.so %C/job.%I.proxy"
## norootpower yes|no - if set to yes, all job management proccesses
## will switch to mapped user's identity while accessing session
## directory. This is useful if session directory is on NFS
## root squashing turned on. Default is no.
#norootpower="yes"
## allowsubmit [group ...] - list of authorization groups of users allowed
## to submit new jobs while "allownew=no" is active in jobplugin
## configuration. Multiple commands are allowed.
#allowsubmit="mygroup"
#allowsubmit="yourgroup"
## helper user executable arguments - associates an external program with
## A-REX. This program will be kept running under the account of the user
## specified by username. Currently only ’.’ is supported as username,
## corresponding to the user running A-REX. Every time this executable finishes
## it will be started again. This helper plugin mechanism can be used as an
## alternative to /etc/init.d or cron to (re)start external processes.
#helper=". /usr/local/bin/myutility"
## tmpdir - used by the A-REX, default is /tmp
#tmpdir="/tmp"
## maxrerun - specifies how many times job can be rerun if it failed in LRMS.
## Default value is 5. This is only an upper limit, the actual rerun value is set
## by the user in his xrsl.
#maxrerun="5"
## globus_tcp_port_range, globus_udp_port_range - Firewall configuration.
#globus_tcp_port_range="9000,12000"
#globus_udp_port_range="9000,12000"
## x509_user_cert, x509_user_key - Location of credentials for service.
## These may be used by any module or external utility which need to
## contact another service not on behalf of user who submited job.
#x509_user_key="/etc/grid-security/hostkey.pem"
#x509_user_cert="/etc/grid-security/hostcert.pem"
## x509_cert_dir - Location of trusted CA certificates
#x509_cert_dir="/etc/grid-security/certificates"
## http_proxy - http proxy server location
#http_proxy="proxy.mydomain.org:3128"
## fixdirectories yes|missing|no - specifies during startup A-REX should
## create all directories needed for it operation and set suitable default
## permissions. If "no" is specified then A-REX does nothing to prepare its
## operational environment. In case of "missing" A-REX only creates and
## sets permissions for directories which are not present yet. For "yes"
## all directories are created and permisisons for all used directories are
## set to default safe values. Default behavior is as if "yes" is specified.
#fixdirectories="yes"
## arex_mount_point - enables web services interfaces, including
## job execution and information system. The argument is
## an https URL defining the endpoint port and path:
## https://<hostname>:<port>/<path>
## In order to submit job a client must specify the exact published
## path. Make sure the chosen port is not blocked by firewall
## or other security rules.
#arex_mount_point="https://piff.hep.lu.se:60000/arex"
## enable_arc_interface yes|no - turns on or off the ARC own WS interface
## based on OGSA BES and WSRF. If enabled the interface can be accessed at
## the URL specified by arex_mount_point (this option must also be
## specified). Default is yes.
#enable_arc_interface="yes"
## enable_emies_interface - enable the EMI Execution Service interface. If
## enabled the interface can be accessed at the URL specified in
## arex_mount_point (this option must also be specified)
#enable_emies_interface="yes"
## arguspep_endpoint - specifies URL of Argus PEPD service to use for
## authorization and user mapping.
## It is worth to mention that "requireClientCertAuthentication" (default is false)
## item of pepd.ini (configuration of Argus PEPD service) is set to be 'true', then
## https should be used, otherwise http is proper.
## If specified Argus is contacted for every operation requested
## through WS interface (see arex_mount_point).
#arguspep_endpoint="https://somehost.somedomain:8154/authz"
## arguspep_profile - defines which communication profile to use while communicationg
## with Argus PEPD service. Possible values are:
## direct - pass all authorization attributes (only for debugging)
## subject - pass only subject name of client
## cream - makes A-REX pretend it is gLite CREAM service. This is
## recommended profile for interoperability with gLite.
## emi - new profile devloped in EMI project. This is default option.
#arguspep_profile="cream"
## arguspep_usermap - specifies whether response from Argus service may define mapping
## of client to local account. Possible values are 'yes' and 'no'. Default is 'no'.
## Argus is contacted after all other user mapping is performed. Hence it can
## overwrite all other decisions.
#arguspep_usermap="no"
## arguspdp_endpoint - specifies URL of Argus PDP service to use for
## authorization and user mapping.
## It is worth to mention that "requireClientCertAuthentication" (default is false)
## item of pdp.ini (configuration of Argus PDP service) is set to be 'true', then
## https should be used, otherwise http is proper.
## If specified Argus is contacted for every operation requested
## through WS interface (see arex_mount_point).
#arguspdp_endpoint="https://somehost.somedomain:8152/authz"
## arguspdp_profile - defines which communication profile to use while communicationg
## with Argus PDP service. Possible values are:
## subject - pass only subject name of client
## cream - makes A-REX pretend it is gLite CREAM service. This is
## recommended profile for interoperability with gLite.
## emi - new profile devloped in EMI project. This is default option.
#arguspdp_profile="cream"
## arguspdp_accpetnotapplicable - specify if the "NotApplicable" decision returned by Argus
## PDP service is treated as reason to deny request. Default is 'no', which treats
## "NotApplicable" as reson to deny request.
#arguspdp_acceptnotapplicable="no"
## watchdog - specifies if additinal watchdog processes is spawned to restart
## main process if it is stuck or dies. Possible values are 'yes' and 'no'.
## Default is 'no'.
#watchdog="no"
####################################################################
### [data-staging] block ###########################################
##
## [data-staging] block configures DTR data staging parameters
##
#[data-staging]
## debug - Log level for transfer logging in job.id.errors files, between
## 0 (FATAL) and 5 (DEBUG). Default is to use value set by debug option in
## [grid-manager] section.
#debug="4"
## maxdelivery - Maximum number of concurrent file transfers, i.e. active
## transfers using network bandwidth. This is the total number for the whole
## system including any remote staging hosts. Default is 10.
#maxdelivery="40"
## maxprocessor - Maximum number of concurrent files in each pre- and post-
## processing state, eg cache check or replica resolution. Default is 10.
#maxprocessor="20"
## maxemergency - Maximum "emergency" slots which can be assigned to transfer
## shares when all slots up to the limits configured by the above two options
## are used by other shares. This ensures shares cannot be blocked by others.
## Default is 1.
#maxemergency="5"
## maxprepared - Maximum number of files in a prepared state, i.e. pinned on a
## remote storage such as SRM for transfer. A good value is a small multiple of
## maxdelivery. Default is 200.
#maxprepared="250"
## sharetype - Scheme to assign transfer shares. Possible values are dn,
## voms:vo, voms:role and voms:group.
#sharetype="voms:role"
## definedshare - Defines a share with a fixed priority, different from the
## default (50). Priority is an integer between 1 (lowest) and 100 (highest).
#definedshare="myvo:production 80"
#definedshare="myvo:student 20"
## dtrlog - A file in which data staging state information (for monitoring and
## recovery purposes) is periodically dumped. Default is controldir/dtrstate.log
#dtrlog="/tmp/dtrstate.log"
## The following 4 options are used to configure multi-host data staging.
##
## deliveryservice - URL to a data delivery service which can perform remote
## data staging
#deliveryservice="https://myhost.org:60003/datadeliveryservice"
## localdelivery - If any deliveryservice is defined, this option determines
## whether local data transfer is also performed. Default is no.
#localdelivery="yes"
## remotesizelimit - Lower limit on file size (in bytes) of files that remote
## hosts should transfer. Can be used to increase performance by transferring
## small files using local processes.
#remotesizelimit="100000"
## usehostcert - Whether the A-REX host certificate should be used for
## communication with remote hosts instead of the users' proxies. Default is no.
#usehostcert="yes"
## acix_endpoint URL - the ARC Cache Index specified here will be queried for
## every input file specified in a job description and any replicas found in
## sites with accessible caches will be added to the replica list of the input
## file. The replicas will be tried in the order specified by preferredpattern.
#acix_endpoint="https://cacheindex.ndgf.org:6443/data/index"
## securetransfer yes|no - if data connection allows to choose use
## secure|non-secure data transfer. Currently only works for gridftp.
## default is no
#securetransfer="no"
## passivetransfer yes|no - If yes, gridftp transfers are passive. Setting
## this option to yes can solve transfer problems caused by firewalls.
## default is no
#passivetransfer="no"
## localtransfer yes|no - If yes, then the data download from Grid to the
## session directory (stagein) will be part of the batch job (prior to the
## execution of the binary). Default is no.
#localtransfer="no"
## httpgetpartial yes|no - If yes, HTTP GET transfers may transfer data in
## chunks/parts. If no - data is always transfered in one piece.
## default is yes
#httpgetpartial="yes"
## speedcontrol min_speed min_time min_average_speed max_inactivity - specifies
## how slow data transfer must be to trigger error. Tranfer is canceled if
## speed is below min_speed bytes per second for at least min_time seconds,
## or if average rate is below min_average_speed bytes per second, or no data
## was transfered for longer than max_inactivity seconds. Value of zero turns
## feature off. Default is "0 300 0 300"
#speedcontrol="0 300 0 300"
## preferredpattern pattern - specifies a preferred pattern on which
## to sort multiple replicas of an input file. It consists of one or
## more patterns separated by a pipe character (|) listed in order of
## preference. Replicas will be ordered by the earliest match. If the
## dollar character ($) is used at the end of a pattern, the pattern
## will be matched to the end of the hostname of the replica.
#preferredpattern="srm://myhost.ac.uk|.uk$|ndgf.org$"
## copyurl url_head local_path - specifies that URLs, starting from 'url_head'
## should be accessed in a different way (most probaly unix open). The
## 'url_head' part of the URL will be replaced with 'local_path' and
## file from obtained path will be copied to the session directory.
## NOTE: 'local_path' can also be of URL type.
## you can have several copyurl lines
#copyurl="gsiftp://example.org:2811/data/ gsiftp://example.org/data/"
#copyurl="gsiftp://example2.org:2811/data/ gsiftp://example2.org/data/"
## linkurl url_head local_path [node_path] - identical to 'copyurl', only
## file won't be copied, but soft-link will be created. The 'local_path'
## specifies the way to access the file from the gatekeeper, and is used
## to check permissions. The 'node_path' specifies how the file can be
## accessed from computing nodes, and will be used for soft-link creation.
## If 'node_path' is missing - 'local_path' will be used.
## you can have multiple linkurl settings
#linkurl="gsiftp://somewhere.org/data /data"
#linkurl="gsiftp://example.org:2811/data/ /scratch/data/"
## maxtransfertries - the maximum number of times download and upload will
## be attempted per job (retries are only performed if an error is judged
## to be temporary)
#maxtransfertries="10"
####################################################################
##
### [gridftpd] block configures the gridftpd server ################
##
##
#[gridftpd]
## user user[:group] - Switch to a non root user/group after startup
## WARNING: Make sure that the certificate files are owned by the user/group
## specified by this option. Default value is root.
#user="grid"
## debug debuglevel - Set debug level of the gridftpd daemon, between
## 0 (FATAL) and 5 (DEBUG). Default is 3 (INFO).
#debug="2"
## daemon yes|no - Whether GFS is run in daemon mode. Default is yes.
#daemon="yes"
## logfile path - Set logfile location
#logfile="/var/log/arc/gridftpd.log"
## logsize size [number] - 'Size' specifies in bytes how big log file is
## allowed to grow (approximately). If log file exceeds specified size
## it is renamed into logfile.0. And logfile.0 is renamed into
## logfile.1, etc. up to 'number' logfiles. Don't set logsize if you don't
## want to enable the ARC logrotation because another logrotation tool is used.
#logsize="100000 2"
## pidfile path - Specify location of file containig PID of daemon process.
## This is useful for automatic star/stop scripts.
#pidfile="/var/run/gridftpd.pid"
## port bindport - Port to listen on (default 2811)
#port="2811"
## pluginpath - directory where the plugin libraries are installed, default is
## $ARC_LOCATION/lib(64)/arc
#pluginpath="/usr/lib/arc/"
## encryption yes|no - should data encryption be allowed, default is no,
## encryption is very heavy
#encryption="no"
## include - Include contents of another config file.
#include="path"
## allowunknown yes|no - if no, check user subject against grid-mapfile and
## reject if missing. By default unknown (not in the grid-mapfile) grid users
## are rejected
#allowunknown="no"
## maxconnections - maximum number of connections accepted by a gridftpd server.
## Default is 100.
#maxconnections="200"
## defaultbuffer size - defines size of every buffer for data
## reading/writing. Default is 65536. The actual value may decrease if the
## cumulative size of all buffers exceeds value specified by maxbuffer.
#defaultbuffer="65536"
## maxbuffer size - defines maximal amount of memory in bytes to be
## allocated for all data reading/writing buffers. Default is 640kB.
## The number of buffers is (max {3, min {41, 2P + 1}}), where P is the
## parallelism level requested by the client. Hence, even without parallel
## streams enabled number of buffers will be 3.
#maxbuffer="655360"
## globus_tcp_port_range, globus_udp_port_range - Firewall configuration
#globus_tcp_port_range="9000,12000"
#globus_udp_port_range="9000,12000"
## firewall - hostname or IP addres to use in response to PASV command
## instead of IP address of a network interface of computer.
#firewall="hostname"
## x509_user_cert, x509_user_key - Server credentials location
#x509_user_key="/etc/grid-security/hostkey.pem"
#x509_user_cert="/etc/grid-security/hostcert.pem"
## x509_cert_dir - Location of trusted CA certificates
#x509_cert_dir="/etc/grid-security/certificates"
## gridmap - The gridmap file location
## The default is /etc/grid-security/grid-mapfile
#gridmap="/etc/grid-security/grid-mapfile"
## unixmap [unixname][:unixgroup] rule - more sophisticated way to map
## Grid identity of client to local account. If client matches 'rule'
## it's assigned specified unix identity or one generated by rule.
## Mapping commands are processed sequentially and processing stops
## at first successful one (like in [group] section). For possible rules
## read "ARC Computing Element. System Administrator guide" manual. All
## rules defined in [group] section canbe used. There are also additional
## rules which produce not only yes/no result but also give back user and
## group names to which mapping should happen. The way it works is quite
## complex so it is better to read full documentation.
## For safety reasons if sophisticated mapping is used it is better to
## finish mapping sequence with default mapping to nonexistent or safe
## account.
#unixmap="nobody:nogroup all"
## unixgroup group rule - do mapping only for users belonging to
## specified authorization 'group'. It is similar to an additional filter
## for unixmap command which filters out all users not belonging to specified
## authorization group. Only rules which generate unix user and group names
## may be used in this command. Please read "ARC Computing Element System
## Administrator Guide" for more information.
#unixgroup="users simplepool /etc/grid-security/pool/users"
## unixvo vo rule - do mapping only for users belonging to specified VO.
## Only rules which generate unix identity name may be used in this command.
## Please read "ARC Computing Element. System Administrator Guide" for more
## information. This command is similar to 'unixgroup' described above and
## exists for convenience for setups which base mapping on VOs users belong to.
#unixvo="ATLAS unixuser atlas:atlas"
############################################################
##
### [gridftpd/filedir] block #####################################
##
## [gridftpd/filedir] "fileplugin" storage block
## subblock for "exporting" a directory using the gridftpd's fileplugin plugin.
## gridftp plugins are shared libraries.
## "filedir" is a unique label. The access control is set by using the
## "dir" config option
##
#[gridftpd/filedir]
## plugin name - specifies name of shared library to be loaded relative to
## "pluginpath".
## The next line is MUST for a gridftp file server with "fileplugin", don't
## change anything
#plugin="fileplugin.so"
## groupcfg group_name [group_name ...] - specifies authorization groups
## for which this plugin is activated. In case groupcfg is not used the
## plugin is loaded for every mapped grid user. Multiple names were
## may be specified delimited by blank space. Group names are as specified
## in [group] sections.
#groupcfg="users"
## the name of the virtual directory served by the gridftp server, REQUIRED
## the exported storage area is accessible as gsiftp://my_server/topdir.
## "topdir" is just an example, call the virtual path anything you like,
## even "/" is a valid choice.
#path="/topdir"
## the physical directory corresponding to the virtual one:
## gsiftp://my_server/topdir will give access to the
## /scratch/grid directory on my_server, REQUIRED
#mount="/scratch/grid"
## dir - this is the access control parameter, you can have several "dir" lines
## controlling different directories within then same block
##
## dir path options - specifies access rules for accessing files in 'path'
## (relative to virtual and real path) and all the files and directories below.
## 'options' are:
## nouser - do not use local file system rights, only use those
## specifies in this line
## owner - check only file owner access rights
## group - check only group access rights
## other - check only "others" access rights
## if none of the above specified usual unix access rights are applied.
## read - allow reading files
## delete - allow deleting files
## append - allow appending files (does not allow creation)
## overwrite - allow overwriting already existing files (does not
## allow creation, file attributes are not changed)
## dirlist - allow obtaining list of the files
## cd - allow to make this directory current
## create owner:group permissions_or:permissions_and - allow creating
## new files. File will be owned by 'owner' and owning group
## will be 'group'. If '*' is used, the user/group to which
## connected user is mapped will be used. The permissions
## will be set to permissions_or & permissions_and. (second
## number is reserved for the future usage).
##
## mkdir owner:group permissions_or:permissions_and - allow creating new directories.
## some examples:
## Set permissions on mounted directory
#dir="/ nouser read cd dirlist delete create *:* 664:664 mkdir *:* 775:775"
## Adjust permissions on some subdirectories
#dir="/section1 nouser read mkdir *:* 700:700 cd dirlist"
#dir="/section2 nouser read mkdir *:* 700:700 cd dirlist"
############################################################
##
### [gridftpd/jobs] subblock ###############################
## [gridftpd/jobs] subblock which creates the jobsubmission interface,
## using the jobplugin of the gridftpd service.
## gridftp plugins are shared libraries. 'jobs' is a unique label.
#[gridftpd/jobs]
## the path to the virtual gridftpd directory which is used during the
## job submission. MUST be set.
#path="/jobs"
## plugin name - specifies name of shared library to be loaded relative to
## "pluginpath".
## The next line is MUST for a job submission service via gridftpd
## "jobplugin", don't change anything!
#plugin="jobplugin.so"
## groupcfg group_name [group_name ...] - specifies authorization groups
## for which this plugin is activated. In case groupcfg is not used the
## plugin is loaded for every mapped grid user.
#groupcfg="users"
## The 'allownew' config parameter sets if the grid resource accepts
## submission of new jobs. This parameter can be used to close down a grid.
## The default is yes
#allownew="yes"
## remotegmdirs controldir sessiondir - Specifies control
## and session directories to which jobs can be submitted but which are
## under the control of another A-REX. The corresponding controldir and
## sessiondir parameters must be defined in another A-REX's
## configuration. Multiple remotegmdirs can be specified.
#remotegmdirs="/mnt/host1/control /mnt/host1/session"
## maxjobdesc size - specifies maximal allowed size of job description
## in bytes. Default value is 5MB. If value is missing or 0 size is not
## limited.
#maxjobdesc="5242880"
## configfile service_configuration_path - If [gridftpd] and [grid-manager]
## configuration parts are located in separate files this configuration
## option allows to link them. The service_configuration_path points
## to configuration file containing [grid-manager] section.
## Use this option only if You really know what You are doing.
#configfile="/etc/arc.conf"
####################################################################
##
### [infosys] block ################################################
## [infosys] block configures the hosting environment of the
## Information services (Local Info Tree, Index Service, Registrations,
## see the Information System manual) provided by the
## OpenLDAP slapd server.
#[infosys]
## infosys_compat - Setting this variable will cause ARC to use the old
## infoproviders.
## NOTE: this only applies to ARC < 13.11. Old infoproviders
## have been REMOVED from release 13.11 on.
##Basically, the new version uses A-REX to create LDIF
## while the old version uses a BDII provider-script to do it. The new
## version is required for GLUE2 output.
#infosys_compat="disable"
## infoproviders_timeout - this only applies to new infoproviders.
## it changes A-REX behaviour with respect to a single infoprovider run.
## Increase this value if you have many jobs in the controldir and
## infoproviders need more time to process.
## The value is in seconds.
## Default is 1200 seconds.
#infoproviders_timeout="1200"
## validity_ttl - allows the sysadmin to define a specific validity
## time for the records in the information system. The number is in
## seconds. This number appears "as is" in the GLUE2 Validity fields.
## Default is 600 seconds.
#validity_ttl="600"
## debug - sets the debug level/verbosity of the startup script {0 or 1}.
## Default is 0.
#debug="1"
### Openldap specifics
## hostname - the hostname of the machine running the slapd service
## will be the bind for slapd. If not present, will be
## taken from the [common] block or guessed
#hostname="my.testbox"
## port - the port where the slapd service runs. Default infosys port is 2135.
#port="2135"
## slapd_loglevel - sets the native slapd loglevel (see man slapd).
## Slapd logs via syslog. The default is set to no-logging (0) and it is
## RECOMMENDED not to be changed in a production environment.
## Non-zero slap_loglevel value causes serious performance decrease.
#slapd_loglevel="0"
## slapd_hostnamebind - may be used to set the hostname part of the
## network interface to which the slapd process will bind. Most of
## the cases no need to set since the hostname config parameter is already
## sufficient. The default is empty. The example below will bind the slapd
## process to all the network interfaces available on the server.
#slapd_hostnamebind="*"
## threads - the native slapd threads parameter, default is 32. If you run an
## Index service too you should modify this value.
#threads="128"
## timelimit - the native slapd timelimit parameter. Maximum number of seconds
## the slapd server will spend answering a search request. Default is 3600.
## You probably want a much lower value.
#timelimit="1800"
## idletimeout - the native slapd idletimeout parameter. Maximum number of
## seconds the slapd server will wait before forcibly closing idle client
## connections. It's value must be larger than the value of "timelimit" option.
## If not set, it defaults to timelimit + 1.
#idletimeout="1800"
## ldap_schema_dir - allows to explicitly specify a path to the schema
## files. Note that this doesn't override standard location, but adds
## the specified path to the standard locations /etc/ldap and /etc/openldap.
## If you plan to relocate Glue1 and GLUE2 schemas, all these should be
## in the same directory that you specify here.
## this option does NOT apply to nordugrid.schema file. Such file has a
## release dependent location.
## Default is to use only standard locations described above.
#ldap_schema_dir="/nfs/ldap/schema/"
## oldconfsuffix .suffix - sets the suffix of the backup files of the
## low-level slapd config files in case they are regenerated. Default is
## ".oldconfig".
#oldconfsuffix=".oldconfig"
## overwrite_config yes|no - determines if the infosys startup scripts
## should generate new low-level slapd configuration files. By default the
## low-level configuration files are regenerated with every server startup
## making use of the values specified in the arc.conf.
#overwrite_config="yes"
### Logging
## registrationlog path - specifies the logfile for the registration processes
## initiated by your machine. Default is "/var/log/arc/inforegistration.log"
#registrationlog="/var/log/arc/inforegistration.log"
## providerlog path - Specifies log file location for the information
## provider scripts. The feature is only available with >= 0.5.26 tag.
## Default is "/var/log/arc/infoprovider.log"
#providerlog="/var/log/arc/infoprovider.log"
## provider_loglevel - loglevel for the infoprovider scripts (0-5).
## The default is 1 (critical errors are logged)
#provider_loglevel="2"
### Other
## user unix_user - the unix user running the infosys processes such as
## the slapd, the registrations and infoprovider scripts.
## By default the ldap-user is used, you can run it as root if you wish.
## In case of non-root value you must make sure that the A-REX
## directories and their content are readable by the 'user' and the 'user'
## has access to the full LRMS information including jobs submitted by
## other users. The A-REX directories (controldir, sessiondir
## runtimedir, cachedir) are specified in the [grid-manager] block
#user="root"
## giis_location - If giis_location is not set, ARC_LOCATION will be
## used instead.
#giis_location="/usr/"
## infosys_ldap_run_dir - path where NorduGrid/GLUE2 LDAP ldif file
## will be generated, and where the fifo to sync between infoproviders
## and BDII will be generated. Default: /var/run/arc/infosys/
#infosys_ldap_run_dir="/var/run/arc/infosys/"
## These three variables decide which schema should be used for
## publishing data. They can all be enabled at the same time. Default is
## to enable nordugrid mds and disable glue.
## infosys_nordugrid - Enables NorduGrid schema
#infosys_nordugrid="enable"
## infosys_glue12 - Enables glue1.2/1.3 schema
## If infosys_glue12 is enabled, then resource_location,
## resource_latitude and resource_longitude need to be set in the
## [infosys/glue12] block. These variables do not have default values.
## The rest of the variables defaults are showcased below.
#infosys_glue12="disable"
## infosys_glue2 - Enables GLUE2 schema
#infosys_glue2_ldap="disable"
## infosys_glue2_ldap_showactivities - Enables GLUE2 ComputingActivities
## to appear in the LDAP rendering
## they're currently disabled by default.
#infosys_glue2_ldap_showactivities="disable"
## infosys_glue2_service_qualitylevel - Allows a sysadmin to define a
## different GLUE2 QualityLevel for A-REX.
## This can be used for operations.
## default: production
## Allowed value is one of: "production", "pre-production", "testing",
## "development"
## Refer to GLUE2 documentation for the meaning of these strings.
#infosys_glue2_service_qualitylevel="production"
### Slapd specific
## slapd - Configure where the slapd command is located, default is:
## /usr/sbin/slapd
#slapd="/usr/sbin/slapd"
## slapadd - Configure where the slapadd command is located, default is:
## /usr/sbin/slapadd
#slapadd="/usr/sbin/slapadd"
### BDII specific
## Starting from 11.05, Nordugrid ARC only supports BDII5.
## These variables are usually automatically set by ARC, and
## are here mostly for debug purposes and to tweak exotic
## BDII5 installations. In general, a sysadmin should not set these.
## bdii_debug_level - set the following to DEBUG to check bdii errors
## in bdii-update.log
## useful not to enable slapd logs reducing performance issues.
#bdii_debug_level="ERROR"
## provider_timeout - This variable allows a system administrator to
## modify the behaviour of bdii-update. This is the time BDII waits
## for the scripts generated by A-REX infoproviders to produce
## their output.
## Default is 300 seconds.
#provider_timeout=300
## infosys_debug - This variable disables/enables an ldap-database
## containing information about the ldap database itself on "o=infosys"
## it is very useful for debugging. Default is enabled.
#infosys_debug="disable"
## BDII5 uses these variables. These might change depending on BDII version.
## ARC sets them by inspecting distributed bdii configuration files.
## DO NOT CHANGE UNLESS YOU KNOW WHAT YOU'RE DOING
## bdii_location - The installation directory for the BDII.
## Default is /usr
#bdii_location="/usr"
## bdii_var_dir - Contains BDII pid files and slapd pid files
#bdii_var_dir="/var/run/arc/bdii"
## bdii_log_dir - Contains infosys logs
#bdii_log_dir="/var/log/arc/bdii"
## bdii_tmp_dir - Contains provider scripts
#bdii_tmp_dir="/var/tmp/arc/bdii"
## bdii_lib_dir - Contains slapd databases
#bdii_lib_dir="/var/lib/arc/bdii"
## bdii_update_pid_file, slapd_pid_file - Allows to change bdii-update
## and slapd pidfiles filename and location
#bdii_update_pid_file="/var/run/arc/bdii-update.pid"
#slapd_pid_file="$bdii_var_dir/db/slapd.pid"
## bdii_database - Configure what ldap database backend should be used,
## default is: bdb
#bdii_database="bdb"
## The following options are for tweaking only. Usually one should not
## configure them. They change the BDII configuration file generated
## by ARC.
## Please consult BDII manual for details.
## bdii_conf - Location of the bdii config file.
## ARC modifies the original and sets it
## as default /var/run/arc/infosys/bdii.conf
#bdii_conf="/var/run/arc/infosys/bdii.conf"
## Command line options used to run bdii-update.
## ARC finds it looking into bdii configuration.
## default: ${bdii_location}/sbin/bdii-update
#bdii_update_cmd
#bdii_archive_size
#bdii_db_config
#bdii_breathe_time
#bdii_delete_delay
#bdii_read_timeout
#bdii_run_dir
#bindmethod
#cachettl
#db_archive
#db_checkpoint
## EGIIS-related commands
## giis_fifo - path to fifo used by EGIIS.
## default is /var/run/arc/giis-fifo
## This file is automatically created by ARC, the option
## is only for tweaking.
#giis_fifo=/var/run/arc/giis-fifo
## LDAP parameters of the cluster.pl (old) infoprovider, use the defaults,
## do NOT change them unless you know what you are doing
## cachetime affects old infoproviders, and forces the validity time of the record.
#cachetime="30"
## sizelimit affects registration to egiis
#sizelimit="10"
## slapd_cron_checkpoint - LDAP checkpoint enable/disable
## This option was introduced to solve bug #2032, to reduce the number
## of log files produced by BDII. It is usually not needed,
## but if BDII produces large logs and huge number of files,
## should help solving the issues related to that.
#slapd_cron_checkpoint="enable"
####################################################################
##
### [infosys/glue12] block #########################################
##
## This block holds information that is needed by the glue 1.2
## generation. This is only necessary if infosys_glue12 is enabled.
##
#[infosys/glue12]
## These variables need to be set if infosys_glue12 is enabled.
## IMPORTANT: no slashes or backslashes here!
## Example: "Kastrup, Denmark"
#resource_location=""
## Example: "55.75000"
#resource_latitude=""
## Example: "12.41670"
#resource_longitude=""
## Example 2400
#cpu_scaling_reference_si00=""
## Example Cores=3,Benchmark=9.8-HEP-SPEC06
#processor_other_description=""
## Example http://www.ndgf.org
#glue_site_web=""
## Example NDGF-T1
#glue_site_unique_id=""
## This variable decides if the GlueSite should be published. In case
## you want to set up a more complicated setup with several publishers
## of data to a GlueSite, then you may wish to tweak this parameter.
#provide_glue_site_info="true"
####################################################################
##
### [infosys/site/sitename] block ##################################
##
## [infosys/site/sitename] Site BDII configuration block, this block is
## used to configure ARC to generate a site-bdii that can be registered
## in GOCDB etc to make it a part of a gLite network. The sitename
## part is to be declarative of the site-bdii being generated.
#[infosys/site/sitename]
## The unique id used to identify this site, eg "NDGF-T1"
#unique_id=""
## The url is on the format:
## ldap://host.domain:2170/mds-vo-name=something,o=grid and should
## point to the resource-bdii
#url=""
####################################################################
##
### [infosys/admindomain] block ##################################
##
## [infosys/admindomain] GLUE2 AdminDomain configuration block,
## to configure administrative items of the cluster. This values
## do not affect neither glue12 or nordugrid renderings.
## If the whole block is not specified, will default to an AdminDomain
## called UNDEFINEDVALUE.
#[infosys/admindomain]
## name - the Name attribute for the domain. This will show
## in top-BDII to group the resources belonging to this cluster.
## to group a bunch of clusters under the same AdminDomain,
## just use the same name.
## If not specified, will default to UNDEFINEDVALUE.
## Example:
#name="ARC-TESTDOMAIN"
## description - description of this domain. Not mandatory.
#description="ARC test Domain"
## www - url pointing at a site holding information about the
## AdminDomain. Not mandatory.
## Example:
#www="http://www.nordugrid.org/"
## distributed - set this to yes if the domain is distributed
## that means, if the resources belonging to the domain
## are considered geographically distributed.
#distributed=yes
## owner - contact email of a responsible
## subject for the domain
#owner=admin@nordugrid.org
## otherinfo - fills the OtherInfo GLUE2 field.
## no need to set, used only for future development.
#otherinfo=Test Other info
####################################################################
##
### [infosys/index/indexname] block ################################
##
## [infosys/index/indexname] Index Service block configures and enables
## an Information Index Service. A separate Index block is required for
## every Index Service you may run on the given machine.
## The 'indexname' constitutes to the
## 'mds-vo-name=indexname,o=grid' LDAP suffix characterizing the Index Service.
#[infosys/index/indexname]
## name - The unique (within the hosting machine) name of the
## Index Service. Its value becomes part of the LDAP suffix
## of the Index Service:
## (mds-vo-name=value of the name attribute, o=grid)
#name="indexname"
## allowregistration - Implements registration filtering within an Index Sevice
## Sets the Local Information Trees or lower level Index Services
## allowed to register to the Index Service. List each allowed registrants
## with the allowreg atribute.
## WARNING: specifying allowreg implies setting up a strict filtering,
## only the matching registrants will be able to register to the Index.
## The wildcard * can be used in allowreg. Several allowreg lines can be used.
## Some examples:
## -All the Swedish machines can register regardless they are resources or Indices
## allowreg="*.se:2135"
## -Cluster resources from Denmark can register
## allowreg="*.dk:2135/nordugrid-cluster-name=*, Mds-Vo-name=local, o=grid"
## -Storage resources from HIP, Finland can register
## allowreg="*hip.fi:2135/nordugrid-se-name=*, Mds-Vo-name=local, o=grid"
## -The index1.sweden.se can register as a Sweden Index (and only as a Sweden Index)
## allowreg="index1.sweden.se:2135/Mds-vo-Name=Sweden,o=Grid"
## -Any Index Service can register
## allowreg="*:2135/Mds-vo-Name=*,o=Grid"
#allowreg="trusted.host.org.se:2135/Mds-vo-Name=Trusted-Index,o=Grid"
####################################################################
##
### [infosys/index/indexname/registration/registrationname] block #
## [infosys/index/indexname/registration/registrationname]
## Index service registration block
## This block enables a registration process initiated by the
## 'indexname' Index Service (configured previuosly)
## to a target Index Service.
## NorduGrid maintains a webpage with information on major
## Index Services:
## http://www.nordugrid.org/NorduGridMDS/index_service.html
#[infosys/index/indexname/registration/registrationname]
## targethostname - the hostname of the machine running the registration target
## Index Service
#targethostname="index.myinstitute.org"
## targetport - the port on which the target Index Service is running.
## The default is the 2135 Infosys port.
#targetport="2135"
## targetsuffix - the LDAP suffix of the target Index Service
#targetsuffix="mds-vo-name=BigIndex,o=grid"
## regperiod - The registration period in seconds, the registration messages are
## continously sent according to the regperiod. Default is 120 sec.
#regperiod="300"
## registranthostname - the hostname of the machine sending the registrations.
## This attribute inherits its value from the [common] and [infosys] blocks,
## most cases no need to set.
#registranthostname="myhost.org"
## registrantport - the port of the slapd service hosting the
## registrant Index Service. The attribute inherits its value from the
## [infosys] block (and therefore defaults to 2135)
#registrantport="2135"
## registrantsuffix - the LDAP suffix of the registrant Index Service.
## It is automatically determined from the registration block name,
## therefore most of the cases no need to specify.
## In this case the default registrantsuffix will be:
## "Mds-Vo-name=indexname"
## please mind uppercase/lowercase characters in the above string
## when defining allowreg in an index!
## Don't set it unless you want to overwrite the default.
#registrantsuffix="mds-vo-name=indexname,o=grid"
## timeout - The suggested timeout to be included in the registration.
## Default: 120.
#timeout="120"
## ttl - The suggested TTL to be included in the registration. The default
## is twice the registration period.
#ttl="600"
####################################################################
#
### [cluster] block ################################################
## This block configures how your cluster is seen on the grid monitor (infosys
## point of view). Please consult the Infosys manual for detailed information
## on cluster attributes.
## If you want your cluster (configured below) to appear in the infosys
## (on the monitor) you also need to create a cluster registration block
## (see the next block).
#[cluster]
## hostname - the FQDN of the frontend node, if the hostname is not set already
## in the common block then it MUST be set here
#hostname="myhost.org"
## interactive_contactstring - the contact string for interactive logins, set this
## if the cluster supports some sort of grid-enabled interactive login (gsi-ssh),
## multivalued
#interactive_contactstring="gsissh://frontend.cluster:2200"
## alias - an arbitrary alias name of the cluster, optional
#cluster_alias="Big Blue Cluster in Nowhere"
## comment - a free text field for additional comments on the cluster in a single
## line, no newline character is allowed!
#comment="This cluster is specially designed for XYZ applications: www.xyz.org"
## cluster_location - The geographical location of the cluster, preferably
## specified as a postal code with a two letter country prefix
#cluster_location="DK-2100"
## cluster_owner - it can be used to indicate the owner of a resource, multiple
## entries can be used
#cluster_owner="World Grid Project"
#cluster_owner="University of NeverLand"
## authorizedvo - this attribute is used to advertise which VOs are authorized
## on the cluster. Multiple entries are allowed.
## Add only one VO for each authorizedvo entry. Multiple VOs in the same line
## will cause errors.
## These entries will be shown in all GLUE2 AccessPolicy and MappingPolicy
## objects, that is, they will apply for all Endpoints(Interfaces) and all
## Shares(currently queues).
#authorizedvo="developer.nordugrid.org"
#authorizedvo="community.nordugrid.org"
## clustersupport - this is the support email address of the resource, multiple
## entries can be used
#clustersupport="grid.support@mysite.org"
#clustersupport="grid.support@myproject.org"
## lrmsconfig - an optional free text field to describe the configuration of your
## Local Resource Management System (batch system).
#lrmsconfig="single job per processor"
## homogeneity - determines whether the cluster consists of identical NODES with
## respect to cputype, memory, installed software (opsys). The frontend is NOT
## needed to be homogeneous with the nodes. In case of inhomogeneous nodes, try
## to arrange the nodes into homogeneous groups assigned to a queue and use
## queue-level attributes. Possible values: True,False, the default is True.
## False will trigger multiple GLUE2 ExecutionEnvironments to be published
## if applicable.
#homogeneity="True"
## architecture - sets the hardware architecture of the NODES. The "architecture"
## is defined as the output of the "uname -m" (e.g. i686). Use this cluster
## attribute if only the NODES are homogeneous with respect to the architecture.
## Otherwise the queue-level attribute may be used for inhomogeneous nodes. If
## the frontend's architecture agrees to the nodes, the "adotf" (Automatically
## Determine On The Frontend) can be used to request automatic determination.
#architecture="adotf"
## opsys - this multivalued attribute is meant to describe the operating system
## of the computing NODES. Set it to the opsys distribution of the NODES and not
## the frontend! opsys can also be used to describe the kernel or libc version
## in case those differ from the originally shipped ones. The distribution name
## should be given as distroname-version.number, where spaces are not allowed.
## Kernel version should come in the form kernelname-version.number.
## If the NODES are inhomogeneous with respect to this attribute do NOT set it on
## cluster level, arrange your nodes into homogeneous groups assigned to a queue
## and use queue-level attributes.
## opsys will be used to fill GLUE2 OSName, OSVersion and OSFamily unless
## these values are explicitly defined. See below for their usage.
#opsys="Linux-2.6.18"
#opsys="glibc-2.5.58"
#opsys="CentOS-5.6"
## nodecpu - this is the cputype of the homogeneous nodes. The string is
## constructed from the /proc/cpuinfo as the value of "model name" and "@" and
## value of "cpu MHz". Do NOT set this attribute on cluster level if the NODES
## are inhomogeneous with respect to cputype, instead arrange the nodes into
## homogeneous groups assigned to a queue and use queue-level attributes. Setting
## the nodecpu="adotf" will result in Automatic Determination On The Frontend,
## which should only be used if the frontend has the same cputype as the
## homogeneous nodes.
#nodecpu="AMD Duron(tm) Processor @ 700 MHz"
## nodememory - this is the amount of memory (specified in MB) on the node
## which can be guaranteed to be available for the application. Please note
## in most cases it is less than the physical memory installed in the nodes.
## Do NOT set this attribute on cluster level if the NODES are inhomogeneous
## with respect to their memories, instead arrange the nodes into homogeneous
## groups assigned to a queue and use queue-level attributes.
#nodememory="512"
## defaultmemory - If a user submits a job without specifying how much
## memory should be used, this value will be taken first. The order is:
## xrsl -> defaultmemory -> nodememory -> 1GB. This is the amount of
## memory (specified in MB) that a job will request(per rank).
#defaultmemory="512"
## benchmark name value - this optional multivalued attribute can be used to
## specify benchmark results on the cluster level. Use this cluster attribute
## if only the NODES are homogeneous with respect to the benchmark performance.
## Otherwise the similar queue-level attribute should be used. Please try to
## use one of standard benchmark names given below if possible.
#benchmark="SPECINT2000 222"
#benchmark="SPECFP2000 333"
## middleware - the multivalued attribute shows the installed grid software on
## the cluster, nordugrid and globus-ng is automatically set, no need to specify
## middleware=nordugrid or middleware=globus
#middleware="my grid software"
## nodeaccess - determines how the nodes can connect to the internet. Not setting
## anything means the nodes are sitting on a private isolated network. "outbound"
## access means the nodes can connect to the outside world while "inbound" access
## means the nodes can be connected from outside. inbound & outbound access
## together means the nodes are sitting on a fully open network.
#nodeaccess="inbound"
#nodeaccess="outbound"
## dedicated_node_string - the string which is used in the PBS node config to
## distinguish the grid nodes from the rest. Suppose only a subset of nodes are
## available for grid jobs, and these nodes have a common "node property" string,
## this case the dedicated_node_string should be set to this value and only the
## nodes with the corresponding "pbs node property" are counted as grid enabled
## nodes. Setting the dedicated_node_string to the value of the "pbs node
## property" of the grid-enabled nodes will influence how the totalcpus, user
## freecpus is calculated. You don't need to set this attribute if your cluster
## is fully available for the grid and your cluster's PBS config does not use
## the "node property" method to assign certain nodes to grid queues. You
## shouldn't use this config option unless you make sure your PBS config makes
## use of the above described setup.
#dedicated_node_string="gridnode"
## localse - this multivalued parameter tells the BROKER that certain URLs (and
## locations below that) should be considered "locally" available to the cluster.
#localse="gsiftp://my.storage/data1/"
#localse="gsiftp://my.storage/data2/"
## gm_mount_point - this is the same as the "path" from the [gridftpd/jobs]
## block. The default is "/jobs". Will be cleaned up later, do NOT touch it.
#gm_mount_point="/jobs"
## gm_port - this is the same as the "port" from the [gridftpd] block. The
## default is "2811". Will be cleaned up later.
#gm_port="2811"
## cpudistribution - this is the CPU distribution over nodes
## given in the form: ncpu:m where
## n is the number of CPUs per machine
## m is the number of such computers
## Example: 1cpu:3,2cpu:4,4cpu:1 represents a cluster with
## 3 single CPU machines, 4 dual CPU machines, one machine with 4 CPUs.
## This command is needed to tweak and overwrite the values returned
## by the underlying LRMS. In general there is no need to configure it.
#cpudistribution=1cpu:3,2cpu:4,4cpu:1
### GLUE2 specific attributes
## OSName, OSVersion and OSFamily are a replacement for nordugrid opsys
## configuration variable. They define which operating system is running
## on the hardware (ExecutionEnvironment) behind a ComputingShare
## (a specific set of resources, for example a batch system queue)
## These strings are lowercase text and they should be
## listed and existing in the GLUE2 open enumerations at:
## https://github.com/OGF-GLUE/Enumerations
## However the sysadmin is free to enter new values if these are not
## present in the above registry.
## If defined, these commands will have the following effect:
## GLUE2 rendering: their values override whatever is defined in opsys
## NorduGrid: their value will be added as an new entry to
## existing nordugrid-cluster-opsys or nordugrid-queue-opsys new entry
## with the following format:
## nordugrid-queue-opsys: <OSName value>-<OSversion value>
## OSName - Name of the operating system distribution or product name. Lowercase.
## Example: centos
## Example: windowsxp
# OSName="Ubuntu"
## OSVersion - Vendor specific string that identifies the operating system
## version.
## Example: 6.6
# OSVersion="12.04"
## OSFamily - Name that identify a family of operating systems, e.g. linux
## kernel or windows kernel based. Lowercase.
## Example: solaris
## Example: windows
# OSFamily="linux"
####################################################################
##
## [infosys/cluster/registration/registrationname] block ############
## Computing resource (cluster) registration block
## configures and enables the registration process of a
## computing resource to an Index Service.
## A cluster can register to several Index Services this case
## each registration process should have its own block.
## NorduGrid maintains a webpage with information on major
## Index Services:
## http://www.nordugrid.org/NorduGridMDS/index_service.html
#[infosys/cluster/registration/registrationname]
## targethostname - see description earlier
#targethostname="index.myinstitute.org"
## targetport - see description earlier
#targetport="2135"
## targetsuffix - see description earlier
#targetsuffix="mds-vo-name=BigIndex,o=grid"
## regperiod - see description earlier
#regperiod="300"
## registranthostname - see description earlier
#registranthostname="myhost.org"
## registrantport - see description earlier
#registrantport="2135"
## registrantsuffix - the LDAP suffix of the registrant cluster resource
## It is automatically determined from the [infosys] block and the
## registration blockname. In this case the default registrantsuffix will be:
## "nordugrid-cluster-name=hostname,Mds-Vo-name=local,o=Grid"
## please mind uppercase/lowercase characters above if defining
## allowreg in an index!
## Don't set it unless you want to overwrite the default.
#registrantsuffix="nordugrid-cluster-name=myhost.org,Mds-Vo-name=local,o=grid"
## timeout - The suggested timeout to be included in the registration.
## Default: 45.
#timeout="45"
## ttl - The suggested TTL to be included in the registration. The default
## is twice the registration period.
#ttl="600"
####################################################################
##
### [queue/queue_name] block #######################################
##
## Each grid-enabled queue should have a separate queue block.
## The queuename should be used as a label in the block name.
## A queue can represent a PBS/LSF/SGE/SLURM/LL queue, a SGE pool, a Condor
## pool or a single machine in case 'fork' type of LRMS is specified in
## the [common] block.
## Queues don't need to be registerd (there is no queue registration block),
## once you configured your cluster to register to an Index Service
## the queue entries (configured with this block) automatically will be there.
## Please consult the ARC Information System manual for detailed information
## on queue attributes:
## http://www.nordugrid.org/documents/arc_infosys.pdf
##
## use the queue_name for labeling the block. The special name 'fork' should be
## used for labeling the queue block in case you specified 'fork' type of
## LRMS in the [common] block.
#[queue/gridlong]
## name sets the name of the grid-enabled queue. It MUST match the queue_name
## label of the corresponding queue block, see above.
## Use "fork" if you specified 'fork' type of LRMS in the [common] block.
## Queue name MUST be specified, even if the queue block is already correctly
## labeled.
#name="gridlong"
## homogeneity - determines whether the queue consists of identical NODES with
## respect to cputype, memory, installed software (opsys).
## In case of inhomogeneous nodes, try to arrange the nodes into homogeneous
## groups and assigned them to a queue.
## Possible values: True,False, the default is True.
#homogeneity="True"
## scheduling_policy - this optional parameter tells the schedulling policy of
## the queue, PBS by default offers the FIFO scheduller, many sites run the MAUI.
## At the moment FIFO & MAUI is supported. If you have a MAUI scheduller you
## should specify the "MAUI" value since it modifies the way the queue resources
## are calculated. BY default the "FIFO" sceduller is assumed.
#scheduling_policy="FIFO"
## comment - a free text field for additional comments on the queue in a single
## line, no newline character is allowed!
#comment="This queue is nothing more than a condor pool"
## maui_bin_path - set this parameter for the path of the maui commands like
## showbf in case you specified the "MAUI" scheduling_policy above. This
## parameter can be set in the [common] block as well.
#maui_bin_path="/usr/local/bin"
## queue_node_string - In PBS you can assign nodes to a queue (or a queue to
## nodes) by using the "node property" PBS node config method and asssigning the
## marked nodes to the queue (setting the resources_default.neednodes =
## queue_node_string for that queue). This parameter should contain the "node
## property" string of the queue-assigned nodes. Setting the queue_node_string
## changes how the queue-totalcpus, user freecpus are determined for this queue.
## Essentially, queue_node_string value is used to construct nodes= string in
## PBS script, such as nodes=count:queue_node_string where count is taken from
## the job description (1 if not specified). You shouldn't use this option unless
## you are sure that your PBS configuration makes use of the above configuration.
## Read NorduGrid PBS instructions for more information:
## http://www.nordugrid.org/documents/pbs-config.html
#queue_node_string="gridlong_nodes"
#queue_node_string="ppn=4:ib"
## sge_jobopts - additional SGE options to be used when submitting jobs to SGE
## from this queue. If in doubt, leave it commented out
#sge_jobopts="-P atlas -r yes"
## condor_requirements - only needed if using Condor. It needs to be defined for
## each queue. Use this option to determine which nodes belong to the current
## queue. The value of 'condor_requirements' must be a valid constraints string
## which is recognized by a condor_status -constraint '....' command. It can
## reference pre-defined ClassAd attributes (like Memory, Opsys, Arch, HasJava,
## etc) but also custom ClassAd attributes. To define a custom attribute on a
## condor node, just add two lines like the ones below in the `hostname`.local
## config file on the node:
## NORDUGRID_RESOURCE=TRUE
## STARTD_EXPRS = NORDUGRID_RESOURCE, $(STARTD_EXPRS)
## A job submitted to this queue is allowed to run on any node which satisfies
## the 'condor_requirements' constraint. If 'condor_requirements' is not set,
## jobs will be allowed to run on any of the nodes in the pool. When configuring
## multiple queues, you can differentiate them based on memory size or disk
## space, for example:
##
#condor_requirements="(OpSys == "linux" && NORDUGRID_RESOURCE && Memory >= 1000 && Memory < 2000)"
## CPU architecture to request when submitting jobs to LSF. Use only if you know
## what you are doing.
#lsf_architecture="PowerPC"
## totalcpus - manually sets the number of cpus assigned to the queue. No need to
## specify the parameter in case the queue_node_string method was used to assign
## nodes to the queue (this case it is dynamically calculated and the static
## value is overwritten) or when the queue have access to the entire cluster
## (this case the cluster level totalcpus is the relevant parameter). Use this
## static parameter only if some special method is applied to assign a subset of
## totalcpus to the queue.
#totalcpus="32"
## queue-level configuration parameters: nodecpu, nodememory, architecture, opsys
## and benchmark should be set if they are homogeneous over the nodes assigned
## to the queue AND they are different from the cluster-level value.
## Their meanings are described in the cluster block. Usage: this queue collects
## nodes with "nodememory=512" while another queue has nodes with
## "nodememory=256" -> don't set the cluster attributes but use the queue-level
## attributes. When the frontend's architecture or cputype agrees with the queue
## nodes, the "adotf" (Automatically Determine On The Frontend) can be used to
## request automatic determination of architecture or nodecpu.
## For GLUE2, fine tune configuration of OSName, OSVersion, OSFamily
## is allowed as described in the [cluster] block.
#nodecpu="adotf"
#nodememory="512"
#architecture="adotf"
#opsys="Fedora 16"
#opsys="Linux-3.0"
#OSName="Fedora"
#OSVersion="16"
#OSFamily="linux"
#benchmark="SPECINT2000 222"
#benchmark="SPECFP2000 333"
## queue access policy rules based on VOMS attributes in user's
## proxy certificate (requires the arc-vomsac-check plugin to be enabled).
## Matching rules have the following format:
## ac_policy="[+/-]VOMS: <FQAN>"
## Please read arc-vomsac-check manual page for more information.
#ac_policy="-VOMS: /badvo"
#ac_policy="VOMS: /.*/Role=production"
## maxslotsperjob - this configures the GLUE2 MaxSlotsPerJob value
## on a particular queue (see GLUE2 definition).
## This value is usually generated by LRMS
## infocollectors, but there are cases in which a system administrator
## might like to tweak it.
## Default is to publish what is returned by the LRMS, and if nothing is
## returned, NOT to publish the MaxSlotsPerJob attribute.
## If a system administrator sets the value here, that value will be
## published instead, regardless of what the LRMS returns.
## Each LRMS might have a different meaning for this value.
#maxslotsperjob="5"
## authorizedvo - this attribute is used to advertise which VOs are authorized
## on each specific queue. Multiple entries are allowed.
## Add only one VO for each authorizedvo entry. Multiple VOs in the same line
## will cause errors.
## These entries will be shown in the MappingPolicy objects, that is,
## they will apply for the Shares that corresponds to the queue.
## NOTE: if you have also configured authorizedvo in the [cluster] block,
## the result authorized VOs per queue is the union set of what is
## contained in the [cluster] and in this [queue] block.
#authorizedvo="LocalUsers"
#authorizedvo="atlas"
#authorizedvo="community.nordugrid.org"
## LDAP parameters of the queue+jobs+users.pl (old) infoprovider, use the defaults,
## do NOT change them unless you know what you are doing
## this affects old infoproviders, and forces the validity time of the record.
#cachetime="30"
## sizelimit affects registration to EGIIS
#sizelimit="5000"
####################################################################
##
### [registration/emir] block ######################################
##
## Services registration into EMIR block
## configures and enables the registration process of a
## services enabled in this configuration file into EMI
## indexing service (EMIR).
## Currently only implemented for A-REX.
##
#[registration/emir]
## List of URL separated by comma of EMIR services which are to accept
## registration. This is mandatory.
#emirurls="https://somehost:60002/emir"
## Time in seconds for which registration records should stay valid.
#validity=600
## Time in seconds how othen registration record should be sent to the
## registration service.
#period=60
## disablereg_xbes may be used to selectively disable registration of
## A-REX service. Possible values are yes and no. Default is no,
#disablereg_xbes="no"
####################################################################
### [nordugridmap] block ###########################################
##
## [nordugridmap] block configuration is used to fine-tune behavior
## of the nordugridmap - an ARC tool used to generate grid-mapfiles.
## Please refer to [vo] block description to find information how
## to specify VO sources for mapfile generation. This section setup
## general VO-independent parameters.
##
#[nordugridmap]
## x509_user_cert, x509_user_key - public certificate and privat key
## to be used when fetching sources over TLS (https:// and vomss://
## sources retrieval rely on this parameter)
## If not specified, values defined in [common] section will be used.
## If there is also no [common] section, X509_USER_{CERT,KEY} variables
## are used. Default is '/etc/grid-security/host{cert,key}.pem'
#x509_user_key="/etc/grid-security/hostkey.pem"
#x509_user_cert="/etc/grid-security/hostcert.pem"
## x509_cert_dir - the directory containing CA certificates.
## This information is needed by the 'require_issuerdn' [vo] block
## option. Default is '/etc/grid-security/certificates/'.
#x509_cert_dir="/etc/grid-security/certificates/"
## gridmap_owner username - owner of generated gridmapfiles.
## Default is a owner of grid-manager process (default is 'root').
#gridmap_owner="root"
## gridmap_group groupname - group of generated gridmapfiles.
## Default is 'root'
#gridmap_group="root"
## gridmap_permissions filemode - permissions of generated gridmapfiles.
## Default is '0600'
#gridmap_permissions="0600"
## generate_vomapfile - control is nordugridmap will generate
## vo-mapfile used by arc-ur-logger. Default is 'yes'.
#generate_vomapfile="yes"
## vomapfile - path to vo-mapfile location. Default is
## '/etc/grid-security/grid-vo-mapfile'
#vomapfile="/etc/grid-security/grid-vo-mapfile"
## log_to_file - control whether logging output of nordugridmap
## will be saved to file. Default is 'no' (STDERR is used).
#log_to_file="yes"
## logfile - specify the nordugridmap log file location when in use.
## Default is '/var/log/arc/nordugridmap.log'.
#logfile="/var/log/arc/nordugridmap.log"
## cache_enable - control whether caching of external sources
## will be used. Default is 'yes'.
#cache_enable="yes"
## cachedir - specify the path where cached sources will be stored.
## Default is '/var/spool/nordugrid/gridmapcache/'
#cachedir="/var/spool/nordugrid/gridmapcache/"
## cachetime - controls how many time (in seconds) cached information
## remains valid. Default is 259200 (3 days).
#cachetime="259200"
## issuer_processing - control the behavior of [vo] block require_issuerdn
## parameter. Valid values are 'relaxed' and 'strict'.
## Please see 'require_issuerdn' description in [vo] block for details.
## Default is 'relaxed'.
#issuer_processing="relaxed"
## mapuser_processing - control the behavior of [vo] block mapped_unixid
## parameter usage. Valid values are 'overwrite' and 'keep'.
## Please see 'mapped_unixid' description in [vo] block for details.
## Default is 'keep'.
#mapuser_processing="keep"
## allow_empty_unixid - control whether empty (or unspecified)
## 'mapped_unixid' [vo] block option is allowed to be used.
## Please see 'mapped_unixid' description of [vo] block for details.
## Default is 'no'
#allow_empty_unixid="no"
## voms_method - control how to get information from VOMS(S) sources.
## Valid values are:
## soap - call SOAP method directly using SOAP::Lite
## get - use old implementation that manually parses XML response
## Default is 'soap'.
#voms_method="soap"
## debug level - controls the verbosity of nordugridmap output. Valid
## values are:
## 0 - FATAL - only critical fatal error shown
## 1 - ERROR - errors, including non-critical are shown
## 2 - WARNING (default) - configuration errors that can be ignored
## 3 - INFO - processing information
## 4 - VERBOSE - a bit more processing information
## 5 - DEBUG - lot of processing information
##
## When test run is requested (--test command line option of the
## nordugridmap) debug level is automatically set to 5 (DEBUG).
## Default is 2 (WARNING)
#debug="4"
## fetch_timeout - control how many time (in seconds) nordugridmap will
## wait for external sources retrieval. Default is 15.
#fetch_timeout="15"
####################################################################
##
### The [acix/cacheserver] block ###################################
##
## The cache server component of ACIX runs alongside A-REX. It
## periodically scans the cache directories and composes a Bloom
## filter of cache content which can be pulled by an ACIX index
## server.
#[acix/cacheserver]
## Log file location for the cache server. Default is
## /var/log/arc/acix-cache.log
#logfile="/tmp/acix-cache.log"
####################################################################
##
### The [acix/indexserver] block ###################################
##
## The index server component of ACIX collects cache content filters
## from a set of cache servers configured in this block. The index
## server can be queried for the location of cached files.
#[acix/indexserver]
## ACIX cache servers from which to pull information
#cacheserver="https://some.host:5443/data/cache"
#cacheserver="https://another.host:5443/data/cache"
####################################################################
|