Authentication & authorization

• Go to WLCG cric server

• You should be able to list all CRIC entities (sites (GocDB /OIM and experiment-specific ones), federations, pledges, services, storage protocols and queues) without authentication. However, once you would like to see details of any particular entity, you would be asked to login.

• Those who are registered in the CERN DB, please, use SSO authentication. Authentication with certificate is not yet enabled on this instance, will come soon.

• Those who are not registered in the CERN DB would need to ask for CRIC local account. Please, send a mail to cric-devs@cernNOSPAMPLEASE.ch with your name, family name and mail address to be used by CRIC to communicate with you.

• As soon as you are logged in, you will be able to see details of any CRIC entity, however in order to edit information, one would need to get specific privileges.

• As soon as you are authenticated, you will see a green key ('Request privileges') on the top of the page next to your login name. Please, click on it and follow up the request procedure which allows to request global admin privileges, site admin privileges or federation admin privileges. Ask for sites admin privileges for your site. You will be shortly informed that your privileges are enabled. Please re-login.

CRIC main concepts and data models

• under construction

Editing storage info

• Once you login with appropriate privileges, you should be able to edit information about your site. At the moment we are particularly interested in storage info at your site, namely its implementation, implementation version and SRR URL when it enabled.

• CRIC creates virtual storage service per site/per VO/per media/per implementation. By default it creates 1 disk and 1 tape virtual storage for every VO which is served by a given T1 site. However, if for a given VO there are storage instances for the same media but different implementation (for example EOS and dCache instances for disk storage for ATLAS), CRIC should create two different disk virtual storage instances for this VO. Unfortunately, for the moment, there is no reliable primary source for this kind of information, so it is highly likely that only a single virtual storage will be created by CRIC in such cases. Would be great if you could correct it using CRIC UI and add other storage virtual instances with their implementation , implementation versions for your site and SRR URL when it is enabled. In the future we hope to get this information through SRR (Storage Resource Reporting).

• In the service table view, click on a particular service name
• You get a form with detailed information about service
• Click on the 'Edit' button under the first block of information
• You get another form. Please, correct 'Version' of your DPM implementation. In case Dome is enabled, please provide version number complemented 'with DOME' and provide "Resource Reporting URL" value
• Click on 'Check input data' and save info

Creating a new virtual storage instance in CRIC

• Staring from the entry page: https://wlcg-cric.cern.ch/
  • in the horizontal menu on the top of the page, select 'Core' -> 'Create Storage Service'. You get a form to fill in
• Keep service name field empty as the form suggests
• Select your site form the drop down menu
• Service type (SE) should not be touched
• Select Disk or Tape media in the "Architecture" filed drop down menu
• Provide value for implementation (EOS, Castor, Xrootd, dCache, DPM)
• Provide value for implementation version
• You can provide a value in the endpoint field or leave it empty if it does not make sense
• Please, select value for the VO name. As mentioned above, the virtual storage in CRIC is created for a single VO even though several VOs can share the same physical storage service of the site
• Leave 'ACTIVE' object state
• All other attributes are optional, you can leave them empty

Creating a new protocol for a given virtual storage in CRIC

• Currently, even if there is one single protocol shared by several virtual storage instance in CRIC, for each

• To create new protocol for a given virtual storage instance, select corresponding service in the service list and click on the name to get a detailed description of the virtual storage service
• Below the table with the list of protocols, click on the 'Add protocol' button. You will get a form to fill.
• Leave the name of the protocol empty, the system will generate it for you
• "Flavour" and "endpoint" are mandatory attributes, other fields could be empty

Deleting virtual storage instance from CRIC

For the time being , deletion from the UI is not allowed. Change the object state to "Disabled" in order to make it disappear from the listing

Deleting protocols from CRIC

The protocol attached to a particular virtual storage can be deleted from the protocol list from the detailed page describing the virtual storage service.