Release notes v7.0.0 We are happy to announce the release of ARC 7.0.0, with REST as the primary interface, and with token support in addition to x509. ARC 7 is backwards compatible with ARC 6 except for the deprecated components. This means that your arc configuration file will not need major changes. But pay attention when you restart your services after update, so that you can remove any blocks and options that are no longer supported. The larger internal change in ARC 7 is the restructuring of the job metadata folder, the ARC control directory. The restructuring will be done seamlessly from your ARC 6 control directory to the new restructured ARC 7 control directory. If you have any custom scripts that use per-job metadata files, make sure to update these to the new structure. You can use the arcctl tool to fetch the directory path: arcctl job path . For more details about the changes in ARC 7 read here. To upgrade from ARC 6, consult the migration guide. Highlights in this release Tokens Major improvements and added features compared to the token preview in ARC 6 Extended support for using token information (scopes) for authorization and identity mapping Token based authentication is now enabled by default together with x509 Token information is part of the accounting records Token claims can be used to link a token to a VO for accounting - either automatically if the claim wlcg.group is present, or manually in arc.conf with the vomsless_vo option (see below). New or changed options in arc.conf usetokenforvoms: whether claims from WLCG compliant tokens should be used as VOMS attributes - currently wlcg.group claim is supported tokenscopes: assigns JWT token scopes to perform specific actions authtokenmap: map your token claims to some custom chosen attribute name for accounting authtokensgen: advanced possibility using logical expression in order to map claims in a token to an authgroup tlsserverorder: force priority order of ciphers for TLS connections to be decided on server side vomsless_vo: Added additional option to vomsless_vo configuration command. It is now possible to assign VO to jobs submitted without VOMS proxy differently for users matching different authgroups. This means that you can use this to assign an authgroup to a certain VO. For the token use-case you would first match a token to an authgroup using any of the available methods, and then use the vomsless_vo to assign the authgroup to the appropriate VO. New blocks in arc.conf infosys/accesscontrol: AREX allows to control access to public information for non-authorized users. If this block contains no entries, public information is available to anyone. The allowaccess and denyaccess options are used to control access. The ldap interface is still present in ARC 7, but marked as legacy. The ARC server can use operating system provided CA bundles instead of the traditional IGTF CAs via the configurable x509_cert_policy in the common block in arc.conf. An ARC-CE must currently use either the default grid option or the system option. REST 1.1 A new optional delegation parameter type extension to support tokens A new optional queue parameter to define the default queue of the compute element Support for bulk job submission of identical jobs A tidy up has been done to gain consistent handling of the benchmark parameters over the various arc.conf blocks A restructured controldir for increased scalability When upgrading from ARC 6 to ARC 7, the controldir will seamlessly restructure itself. The ARC Control Tool (arcctl) has several new capabilites. test token issuer (test-jwt) - similar to the test CA functionality (test-ca) cleanup functionality, to cleanup job metadata in controldir, test-jwt and test-ca related files and accounting database arcctl config verify behaviour has changed, it now only verifies arc.conf arcctl service verify behaves as arcctl config verify earlier did, checks arc.conf, time sync and certificiates The accounting subsystem in ARC7 is updated to improve operational efficiency - the database has undergone a redesign. Please see complete changes documentation for details. Removed and obsoleted components Server-side gridftp-based ARC solutions both for job management and data storage Both server and client-side support for EMIES job management interface- ARC Cache Index (ACIX), that was a distributed system that maintained a catalog of locations of cached files stored in various A-REX caches. userlists generation and mapping support by nordugridmap utility Archiving of the JURA accounting service (got removed already in the 6.8.0 release) GLUE1 and site-BDII support within the LDAP-based components of the ARC information system Remote batch system backend support via SSH Python-based LRMS backend framework (it never progressed beyond technology preview status) Support for ARGUS via AREX/WS component Support for python2 LDAP information system support in the ARC7 clients EGIS resource discovery in the ARC 7 clients The following components and functionalities have been kept but labelled as DEPRECATED and target for near-future removal: OBSOLETED: LDAP-based server-side information system with GLUE2 and nordugrid schema rendering OBSOLETED: gridftp protocol for data staging (still available in ARC 7 and provided as a separate plugin package) OBSOLETED: Support for Loadleveler and LSF batch systems Backwards compatibilities and incompatibilities ARC7 still supports x509 proxies in addition to tokens. Both authtokens and x509 authentication are enabled by default. Support for the EMIES interface and the gridftp job interface was completely removed. Publishing cluster information via REST interface is enabled by default, [arex/ws/publicinfo] block is added to zero.conf No incompatible changes in the ARC7 accounting subsystem. APEL and SGAS supported. The internal structure of the controldir files have been changed, ARC internal scripts were updated but note that any custom scripts may break because of the changed file structure in the controldir. ARC 7 supports XRSL and ADL as job description languages, no backward incompatible changes were introduced, all ARC6 job files should work with ARC7. ARC 7 fully supports the SLURM, Condor and the fork batch systems and community efforts were made to provide some maintenance for OpenPBS as well. The other batch systems from ARC6 are kept in ARC7 but their status is unclear. Documentation The ARC 7 documentation can be found at this location. If you miss something or have questions, please contact us! Installing ARC 7 We recommend to install ARC release using the Nordugrid repository. Start with the basics: token-version or x509-version. Get production ready There is also a nice ARC tutorial which you can follow if you are new to ARC. We provide binary builds for all supported versions of Debian, Ubuntu, Fedora, Rocky (compatible with AlmaLinux), and CentOS Stream. Contributing You can submit pull requests to our public repo which mirrors our GitLab repo. The pull requests will be automatically copied over to our Gitlab repo where they will be merged into the source-code if accepted. Getting in touch If you need help with the configuration file or have any other questions related to ARC 6, please contact us via Email: nordugrid-discuss@nordugrid.org (Subscribe) You can still reach us on our channel dedicated to ARC support We will eventually be migrating to another service since Skype is shutting down in May, the new contact info will be announced later. Future support of ARC 6-series Now that ARC 7.0.0 is released, we expect one final ARC 6 release, but after that we will only provide security updates of ARC 6. In particular: No new feature development is planned or going on for ARC6 and no bug-fixing development will happen on ARC6 code base in the future except for security issues. Security fixes for ARC6 will be provided till end of March 2026. Production Sites already running ARC 6 will be able to get deployment and configuration troubleshooting help via GGUS Helpdesk till end March 2027. This we call "operational site support". In EPEL ARC packages have their major release number as part of the package name, arc6 and arc7 packages can not be confused. In the Nordugrid repository, you have to specifically enable the ARC 7 repo to get the ARC 7 update. See repository info. Previous releases Details of previous releases can be found at the ARC Releases page

Web site: https://www.nordugrid.org/ Nightly builds: https://builds.nordugrid.org/nordugrid-arc/master/ Binary packages: Linux repositories and upstream