Commit aac21c9a authored by Maiken's avatar Maiken

Merge branch 'arc6installguide' into 'master'

installation guide improvements

See merge request !5
parents 8d2acb92 57280c14
Pipeline #5516 passed with stages
in 4 minutes and 2 seconds
......@@ -64,6 +64,7 @@ This process is called :ref:`mapping <reference_mapping>`.
Installation
************
This section assumes you have already enabled the :doc:`Nordugrid repositories </common/repos/repository>` for your package utility (yum/dnf/apt).
Install ARC CE core packages from repositories:
......@@ -93,27 +94,30 @@ To deploy IGTF CA certificates to ARC CE host, run [#]_:
Configuration
*************
Configuration of ARC CE can be done by means of modifying pre-shipped 'zero configuration' available at ``/etc/arc.conf``.
Configuration of ARC CE can be done by means of modifying the pre-shipped 'zero configuration' available at ``/etc/arc.conf``.
The purpose of this 'zero configuration' is to offer a minimalistic working computing element out-of-the box right after packages
The purpose of this 'zero configuration' is to offer a minimalistic working computing element out-of-the box right after package
installation with zero additional configuration needed.
For production deployment you will need to customize the configuration in accordance to your actual setup and operations mode.
The ultimate information about available configuration options can be found in :doc:`reference` which is also available locally as ``/usr/share/doc/nordugrid-arc-*/arc.conf.reference``.
.. note::
ARC services must be restarted when changes have been made to arc.conf.
The ultimate information about available configuration options can be found in the :doc:`reference` which is also available locally as ``/usr/share/doc/nordugrid-arc-*/arc.conf.reference``.
The most common configuration steps are the following:
The most common configuration steps are the explained below.
Configure Authorization Rules
-----------------------------
Authorization rules define who can access the computing element (execute jobs, query info, etc).
ARC CE authorization rules use the concept of *authgroups* configured with :ref:`[authgroup] <reference_authgroup>` blocks.
ARC CE authorization rules use the concept of *authgroups* configured by :ref:`[authgroup] <reference_authgroup>` blocks.
Each authgroup represents a set of users, whose identities are matched to configured rules.
Authorization as well as mapping are then configured based on authgroup membership.
Authorization as well as :ref:`mapping <mapping_section>` are then configured based on authgroup membership.
Once defined, authgroups can be applied to filter access to the CE per interface (:ref:`[arex/ws/jobs] <reference_arex_ws_jobs>`, :ref:`[gridftpd/jobs] <reference_gridftpd_jobs>`) and per queue. The ``allowaccess`` option in the corresponding interface block defines the allowed authgroups.
......@@ -186,6 +190,8 @@ For more information about possible authgroup options, including LCAS integratio
.. [#] In this example and in what follows, a simplified configuration is shown. An actual configuration will in most cases include different authgroups for different VO groups and roles.
.. _mapping_section:
Configure mapping
-----------------
......@@ -328,13 +334,13 @@ More detailed technical documentation on ARC data features and advanced features
RunTime Environments
````````````````````
RunTime Environments can modify job execution cycle and are used for advertising software or features offered by the computing facility.
RunTime Environments can modify the job execution cycle and are used for advertising software or features offered by the computing facility.
ARC ships several RTEs that are ready to be used and classified as system-defined.
One can add own directories with so-called user-defined RTEs using the :ref:`reference_arex_runtimedir` configuration option in the ``[arex]`` block.
One can add ones own directories with so-called user-defined RTEs using the :ref:`reference_arex_runtimedir` configuration option in the ``[arex]`` block.
In ARC6, both system- and user-defined directories are local to the ARC CE node and *SHOULD NOT* be shared to worker nodes.
In ARC6, both system- and user-defined directories are local to the ARC CE node and *SHOULD NOT* be shared to worker nodes (unlike in ARC 5).
To use an installed RTE, one should additionally **enable** this RTE with :ref:`arcctl`.
For example, to enable the system-defined ``ENV/PROXY`` RTE, run:
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment