The Persistency Framework code is currently maintained in SVN. User and admin documentation for the SVN repositories is provided below.

Persistency Framework SVN repository: User documentation

CVS to SVN migration

The CORAL and COOL repositories were moved in August 2013 from the AFS-based CERN Central CVS service ( and to the AFS-based CERN SVN Service. Incomplete documentation about the CVS to SVN migration is provided in the OLDPersistencyCvs2Svn page of this twiki.

The POOL software is now being maintained (as one of its many internal packages) by ATLAS, the only experiment that still uses POOL. A read-write SVN repository for POOL has been set up in ATLAS for that purpose. The historical CVS repository for POOL ( has in any case also been migrated to SVN, solely for data preservation purposes, i.e. with the goal of maintaining long term access to this software even when the CVS servers are switched off.

SVN Web interfaces

Web interfaces to the new SVN repositories are provided using both WebSVN and TRAC.

Note that the CMS experiment maintains its tools to build CORAL under github.

SVN client access

The recommended method for accessing the SVN repositories is svn+ssh. Guest access via http is also possible.

Note that the CORAL repository is named 'lcgcoral' (and COOL is now named 'lcgcool' for consistency) to avoid name clashes with the Compass experiment CORAL software framework.

Persistency Framework SVN repository: Admin documentation

SVN administration

The SVN administration section of the CERN SVN Service user guide describes in detal how to perform operations such as configuring access control or automatic emails on commits.

The SVN repositories are hosted on AFS. Their configuration is controlled by the conf and usr-hooks subdirectories of the /afs/<project> directories on AFS. These are only accessible to the librarian accounts for these SVN repositories(libcoral, libcool and libcoral for CORAL, COOL and POOL, respectively).

As described in the admin repository section of the CERN SVN Service user guide, as an alternative to changing configuration files on AFS, it is also possible to change these files in a special admin repository that is itself hosted in SVN. Any changes to the contents of this admin repository are automatically propagated to AFS. This is the recommended mechanism for CORAL and COOL, as it also allows version control for configuration changes. The admin repository can also be browsed (using the appropriate account) on WebSVN (but not on TRAC). In addition to the librarian accounts, the admin/lcgcoral, admin/lcgcool and admin/lcgpool directories can be read and modified by all members of the special egroups VC-librarians-lcgcoral, VC-librarians-lcgcool and VC-librarians-lcgpool, respectively (see RQF0574447); users valassi, avalassi and cdelort are now members of all these three egroups.

In particular, allowed writers (including valassi, avalassi and cdelort) and recipients of automatic emails on commits (including Andrea Valassi and Charles Delort) are defined in the following files:

TRAC administration

After the migration from CVS to SVN, TRAC interfaces were requested for lcgcoral and lcgcool ( RQF0234770) and also for lcgpool ( RQF0249689).

TRAC can be configured using the Web interfaces on, and Initially these three TRAC repositories could only be administered by their respective librarian accounts (lcgcoral, lcgcool and lcgcoral), but users valassi, avalassi and cdelort have now been granted TRAC_ADMIN privileges on all three. BROWSER_VIEW privileges have been granted to anonymous

Computing group administration

The following e-groups are relevant to the management and communication flow for CORAL/COOL activities. The list is non-exhaustive: in particular, it does not include the many "LCG PEB" e-groups that were used initially for the management of POOL/CORAL and COOL (e.g. project-lcg-peb-persistency and project-lcg-peb-conditionsdb) and that are no longer used, but have not been deleted.

E-group Owner Admin e-groupSorted ascending Description
coral-ai-admin A. Valassi - Puppet admins for coral and heposlibs AI nodes. Includes persistency-service e-group.
persistency-cluster-users A. Valassi - Puppet users for heposlibs AI nodes.
heposlibs-users A. Valassi - Mailing list for heposlibs rpm users.
persistency-service C. Delort persistency-service Top-level management e-group. CORAL/COOL FE team in SNOW. Admins of DBOD instances.
VC-librarians-lcgcoral C. Delort persistency-service SVN admins for lcgcoral.
VC-librarians-lcgcool C. Delort persistency-service SVN admins for lcgcool.
VC-librarians-lcgpool C. Delort persistency-service SVN admins for lcgpool.
The last three e-groups above should be cleaned up to cleanly separate private Puppet nodes, CORAL/COOL and heposlibs.

-- AndreaValassi - 2016-04-09

Edit | Attach | Watch | Print version | History: r20 < r19 < r18 < r17 < r16 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r20 - 2020-11-27 - CharlesDelort
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Persistency All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback