Difference between revisions of "Atlas:StorageRequirements"

Un article de lcgwiki.
Jump to: navigation, search
Ligne 7: Ligne 7:
 
* There is still an uncertainty with ATLASGROUPDISK due to a technical limitation in DPM. Atlas has contacted DPM developpers. The proper implementation is expected to be available in September.
 
* There is still an uncertainty with ATLASGROUPDISK due to a technical limitation in DPM. Atlas has contacted DPM developpers. The proper implementation is expected to be available in September.
  
-----
+
 
* Unless mentioned, the size is for a typical T2 with ~500 CPUfs and ~100 TB disk
+
* Unless mentioned, the size is for a typical T2 with ~500 CPUs and ~100 TB disk
 
* Site admin's are requested to create at least the space tokens. The namespace directories can be left to atlas production if the top directory is properly set up so that <code>/atlas/Role=production</code> is allowed to execute dpns-mkdir and dpns-setacl remotely. (Of course they are welcome to create them by themselves).
 
* Site admin's are requested to create at least the space tokens. The namespace directories can be left to atlas production if the top directory is properly set up so that <code>/atlas/Role=production</code> is allowed to execute dpns-mkdir and dpns-setacl remotely. (Of course they are welcome to create them by themselves).
 
* A T3 will need ATLASDATADISK if it would like to receive real data,  ATLASMCDISK to received simulated data, ATLASGROUPDISK to receive group analysis data, and ATLASPRODDISK to contribute official production.  ATLASUSERDISK is not necessary, but may be needed if the site contributes non-local user analysis.
 
* A T3 will need ATLASDATADISK if it would like to receive real data,  ATLASMCDISK to received simulated data, ATLASGROUPDISK to receive group analysis data, and ATLASPRODDISK to contribute official production.  ATLASUSERDISK is not necessary, but may be needed if the site contributes non-local user analysis.
Ligne 20: Ligne 20:
 
* On this page the top directory for ATLAS is represented by <code>.../atlas</code>. Each site should replace it according to their SE configuration.
 
* On this page the top directory for ATLAS is represented by <code>.../atlas</code>. Each site should replace it according to their SE configuration.
 
** eg. It is <code>lapp-se01.in2p3.fr:/dpm/in2p3.fr/home/atlas</code> for lapp.
 
** eg. It is <code>lapp-se01.in2p3.fr:/dpm/in2p3.fr/home/atlas</code> for lapp.
* this top directory is recommended to be configured so that an ordinary user cannot create a file/directory directly underneath.
+
 
* the default ACL of this top directory is recommended to have write permission to /atlas/Role=production and /atlas/Role=lcgadmin, so that new directories can be created by ATLAS administration.
+
* Although it is up to sites policies, but it is recommended
 +
** to have this top directory configured so that only /atlas/Role=production and /atlas/Role=lcgadmin can create files/directories underneath and but ordinary users cannot.
  
  
Ligne 89: Ligne 90:
  
 
== ATLASMCDISK ==
 
== ATLASMCDISK ==
* 15TB for a typical T2 with ~500 CPUfs and ~100 TB disk
+
* 15TB for a typical T2 with ~500 CPU?fs and ~100 TB disk
 
** 60TB for a T2 requesting for 100% AOD.
 
** 60TB for a T2 requesting for 100% AOD.
 
** The size may increase in case D1PD comes in this space.
 
** The size may increase in case D1PD comes in this space.
Ligne 110: Ligne 111:
  
 
== ATLASPRODDISK ==
 
== ATLASPRODDISK ==
* 2TB for a typical T2 with ~500 CPUfs (the size is to be re-visited)
+
* 2TB for a typical T2 with ~500 CPU?fs (the size is to be re-visited)
 
** scales with the CPU capacity of the site.
 
** scales with the CPU capacity of the site.
 
** will be larger if the reconstruction jobs run on the site.
 
** will be larger if the reconstruction jobs run on the site.
Ligne 129: Ligne 130:
  
 
== ATLASGROUPDISK ==
 
== ATLASGROUPDISK ==
* 6TB for a typical T2 with ~500 CPUfs and ~100 TB disk
+
* 6TB for a typical T2 with ~500 CPU?fs and ~100 TB disk
 
** The size may decrease in case D1PD goes into ATLASMCDISK.
 
** The size may decrease in case D1PD goes into ATLASMCDISK.
 
* namespaces to be created and their ACLs:
 
* namespaces to be created and their ACLs:
Ligne 152: Ligne 153:
  
 
== ATLASUSERDISK ==
 
== ATLASUSERDISK ==
* 5TB for a typical T2 with ~500 CPUfs and ~100 TB disk
+
* 5TB for a typical T2 with ~500 CPU?fs and ~100 TB disk
 
* namespace to be created: .../atlas/user
 
* namespace to be created: .../atlas/user
 
* ACL: write permission to all ATLAS users
 
* ACL: write permission to all ATLAS users

Version du 15:51, 7 juillet 2008

Introduction

  • There is still an uncertainty with ATLASGROUPDISK due to a technical limitation in DPM. Atlas has contacted DPM developpers. The proper implementation is expected to be available in September.


  • Unless mentioned, the size is for a typical T2 with ~500 CPUs and ~100 TB disk
  • Site admin's are requested to create at least the space tokens. The namespace directories can be left to atlas production if the top directory is properly set up so that /atlas/Role=production is allowed to execute dpns-mkdir and dpns-setacl remotely. (Of course they are welcome to create them by themselves).
  • A T3 will need ATLASDATADISK if it would like to receive real data, ATLASMCDISK to received simulated data, ATLASGROUPDISK to receive group analysis data, and ATLASPRODDISK to contribute official production. ATLASUSERDISK is not necessary, but may be needed if the site contributes non-local user analysis.


  • In general 'read' permission should be given to all ALL users everywhere.
  • In general 'write' permission should be given to /atlas/Role=production everywhere, so that the ATLAS central deletion tool can work.


ATLAS top directory

  • On this page the top directory for ATLAS is represented by .../atlas. Each site should replace it according to their SE configuration.
    • eg. It is lapp-se01.in2p3.fr:/dpm/in2p3.fr/home/atlas for lapp.
  • Although it is up to sites policies, but it is recommended
    • to have this top directory configured so that only /atlas/Role=production and /atlas/Role=lcgadmin can create files/directories underneath and but ordinary users cannot.


Summary table for Space token and Name space

space token voms group to be associated space to be reserved namespace directory(-ies) to be created
ATLASDATADISK /atlas/Role=production see below* .../atlas/atlasdatadisk
ATLASMCDISK /atlas/Role=production 15TB
(60TB for 100% AOD) see below*
.../atlas/atlasmcdisk
write permission only to atlas/Role=production
ATLASPRODDISK /atlas/Role=production 2TB (see below*) .../atlas/atlasproddisk
write permission only to atlas/Role=production
ATLASGROUPDISK /atlas 6TB (see below*) .../atlas/atlasgroupdisk
write permission to atlas/Role=production



.../atlas/atlasgroupdisk/$GROUP
write permission to atlas/Role=production and /atlas/$GROUP/Role=production

(see below*)

ATLASUSERDISK /atlas 5TB (see below*) .../atlas/user
write permission to all ATLAS users


write permission to /atlas/Role=production for central deletion

ATLASLOCALGROUPDISK /atlas/<locality>, <locality>=fr,ro,cn,jp,... sites to decide .../atlas/<locality>/user
write permission to local ATLAS users

ATLASDATADISK

  • Estimation of size comes later
  • group associated with the space token: /atlas/Role=production
  • namespace to be created: .../atlas/atlasdatadisk
    • Normally, sites already have this namespace created.
  • namespace acl:
# group: atlas/Role=production
user::rwx
group::rwx              #effective:rwx
group:atlas/Role=production:rwx         #effective:rwx
mask::rwx
other::r-x
default:user::rwx
default:group::rwx
default:group:atlas/Role=production:rwx
default:mask::rwx
default:other::r-x


ATLASMCDISK

  • 15TB for a typical T2 with ~500 CPU?fs and ~100 TB disk
    • 60TB for a T2 requesting for 100% AOD.
    • The size may increase in case D1PD comes in this space.
  • namespace to be created: /atlas/atlasmcdisk
    • Normally, sites already have this namespace created.
  • Namespace ACL:
    # group: atlas/Role=production
    user::rwx
    group::rwx              #effective:r-x
    group:atlas/Role=production:rwx         #effective:rwx
    mask::rwx
    other::r-x
    default:user::rwx
    default:group::rwx
    default:group:atlas/Role=production:rwx
    default:mask::rwx
    default:other::r-x
    

ATLASPRODDISK

  • 2TB for a typical T2 with ~500 CPU?fs (the size is to be re-visited)
    • scales with the CPU capacity of the site.
    • will be larger if the reconstruction jobs run on the site.
  • Namespace to be created and its ACL: .../atlas/atlasproddisk, write permission only to /atlas/Role=production
# group: atlas/Role=production
user::rwx
group::rwx              #effective:rwx
group:atlas/Role=production:rwx         #effective:rwx
mask::rwx
other::r-x
default:user::rwx
default:group::rwx
default:group:atlas/Role=production:rwx
default:mask::rwx
default:other::r-x

ATLASGROUPDISK

  • 6TB for a typical T2 with ~500 CPU?fs and ~100 TB disk
    • The size may decrease in case D1PD goes into ATLASMCDISK.
  • namespaces to be created and their ACLs:
    • .../atlas/atlasgroupdisk, write permission only to /atlas/Role=production
    • .../atlas/atlasgroupdisk/$GROUP, write permission to atlas/Role=production and /atlas/$GROUP/Role=production ($GROUP = phys-beauty, phys-exotics, phys-gener, phys-hi, phys-higgs, phys-lumin, phys-sm, phys-susy, phys-top, perf-egamma, perf-flavtag, perf-jets, perf-muons, perf-tau, etc.)
# group: atlas/Role=production
user::rwx
group::rwx              #effective:rwx
group:atlas/Role=production:rwx         #effective:rwx
group:atlas/phys-exotics/Role=production:rwx         #effective:rwx
mask::rwx
other::r-x
default:user::rwx
default:group::rwx
default:group:atlas/Role=production:rwx
default:group:atlas/phys-exotics/Role=production:rwx
default:mask::rwx
default:other::r-x
    • etc...

ATLASUSERDISK

  • 5TB for a typical T2 with ~500 CPU?fs and ~100 TB disk
  • namespace to be created: .../atlas/user
  • ACL: write permission to all ATLAS users
  • Normally, sites already have this namespace created by user analysis jobs so far.
  • example commands
    • dpns-mkdir .../atlas/user
    • dpns-setacl -m g:atlas:rwx,m:rwx,d:g:atlas:r-x .../atlas/user
    • dpns-getacl .../atlas/user
    # group: atlas
    user::rwx
    group::rwx              #effective:rwx
    group:atlas/Role=production:rwx         #effective:rwx
    mask::rwx
    other::r-x
    default:user::rwx
    default:group::r-x
    default:group:atlas/Role=production:rwx
    default:mask::rwx
    default:other::r-x
    


ATLASLOCALGROUPDISK

  • size to be decided by sites.
    • the resources not included in the pledge.
  • name space: .../atlas/fr/user (or .../atlas/ro/user, .../atlas/cn/user, .../atlas/jp/user, etc.)
  • ACL: write permission only to /atlas/fr group (or /atlas/ro, /atlas/cn, /atlas/jp correspondingly)
  • example ACL:
    # group: atlas/fr
    user::rwx
    group::rwx
    group:atlas/Role=production:rwx
    group:atlas/fr:rwx
    mask::rwx
    other::r-x
    default:user::rwx
    default:group::r-x
    default:group:atlas/Role=production:rwx
    default:mask::rwx
    default:other::r-x