Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
public:cs1_data_policy [2007-07-17 09:59] – grit | public:cs1_data_policy [2017-03-08 15:27] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 2: | Line 2: | ||
16/07/2007, H.A. Holties | 16/07/2007, H.A. Holties | ||
+ | |||
===== Background ===== | ===== Background ===== | ||
Line 7: | Line 8: | ||
As for the future LOFAR system, the CS1 storage capacity is too small to store all data in a central location indefinitely. Moreover, the central storage location needs to provide storage not only for observation datasets, but also for (temporary) commissioning and analysis data. The policy below has been defined to allow efficient use of the offline storage cluster while providing as much support to people involved in the commissioning of LOAR CS1 as possible. | As for the future LOFAR system, the CS1 storage capacity is too small to store all data in a central location indefinitely. Moreover, the central storage location needs to provide storage not only for observation datasets, but also for (temporary) commissioning and analysis data. The policy below has been defined to allow efficient use of the offline storage cluster while providing as much support to people involved in the commissioning of LOAR CS1 as possible. | ||
- | NB: The policy as provided here applies principally to the data in the " | + | NB: The policy as provided here applies principally to the data in the " |
===== CS1 observation data policy ===== | ===== CS1 observation data policy ===== | ||
- | The datasets created with the LOFAR CS1 system are copied to the offline storage cluster after observations have finished. The available datasets and their locations can be found in the [[public: | + | The datasets created with the LOFAR CS1 system are copied to the offline storage cluster after observations have finished. The available datasets and their locations can be found in the [[public: |
Archived data will be moved to GRID based storage servers. Commissioning data will be owned by the /lofar/ops group and stored under the lfc directory / | Archived data will be moved to GRID based storage servers. Commissioning data will be owned by the /lofar/ops group and stored under the lfc directory / | ||
Line 19: | Line 21: | ||
- | ===== CS1 commissioning data (user data) policy ===== | ||
- | To allow commissioning analysis of datasets and testing of offline processing software, users may request usage of central strorage capacity. Requests should be directed to the CS1 system administrator (Teun Grit). The request should be accompanied by the capacity needed. Further information may be requested by the CS1 system administrator (such as motivation, expected period for which storage capacity is needed, etc). | ||
- | The CS1 system administrator will confirm the allocated storage capacity and the period for which it can be used. If demanded so for operational or commissioning purposes, the CS1 system administrator can ask users to (re) move their data. An overview of data capacity allocated to users is given in the following table: | ||
- | ^ **Useraccount** ^ **Storage directory** ^ **Allocated capacity** ^ **Used capacity (if larger)** ^ **Allocated until** ^ | ||
- | | brentjens | / | + | ===== CS1 commissioning data (user data) policy ===== |
- | | claw | / | + | |
- | | pandey | + | To allow commissioning analysis of datasets and testing of offline processing software, users may request usage of central strorage capacity. Requests should be directed to the observer on duty (observer at aston dot nl). The request should be accompanied by the capacity needed. Further information may be requested (such as motivation, expected period for which storage capacity is needed, etc). |
- | | rnijboer | + | |
- | | sarod | / | + | Operations personnel will confirm the allocated storage capacity and the period for which it can be used. If demanded so for operational or commissioning purposes, operations personnel can ask users to (re) move their data. An overview of data capacity allocated to users is given in the following table:\\ |
- | | diepen | + | |
- | | renting | + | ^ **Useraccount\\ ** ^ **Storage directory\\ ** ^ **Allocated capacity\\ ** ^ **Used capacity\\ (if more) ** ^ **Allocated until\\ ** ^ |
- | | renting | + | | brentjens | / |
- | | schoenma | + | | claw | / |
- | | omar | + | | diepen |
- | | ramesh | + | | omar |
- | | zwieten | + | | pandey |
+ | | ramesh | ||
+ | | renting | ||
+ | | renting | ||
+ | | rnijboer | ||
+ | | sarod | /lifs003/brentjens | ||
+ | | schoenma | ||
+ | | zwieten | ||
+ | \\ | ||
- | NB1: The CS1 offline storage servers provide storage on "best effort" | + | NB1: The CS1 offline storage servers provide storage on "best effort" |
- | NB2: There is no software used for accounting storage capacity. Please check the used capacity yourself. Manual checks will be carried out by the CS1 system administrator as well, in particular in situations where the available storage capacity becomes too small to allow planned operations and commissioning. Offenders will be notified and prompt action is expected in that case. In case there is no response, corrective actions may be taken by the CS1 system administrator. Offending users may be "named and shamed" | + | NB2: There is no software used for accounting |