lcgwiki - Contributions [en]

Draft of the scientific programm

2007-02-22T15:20:17Z

Grahal: /* Etat des lieux pour le calcul au LHC en France */

D.ation modèles de cP. 31/01/2007
==== Objectifs ====
LCG-France organise son 2ème colloque à Clermont-Ferrand les 14 et 15 mars 2007. Ces journées sont destinées à tous les acteurs de la grille de calcul au LHC (gestionnaires de site et utilisateurs) de l'IN2P3 et du Dapnia. Elles ont pour objectifs d’offrir un lieu d’échange et de communication sur les actions, les idées et les expériences en cours dans la mise en place du calcul pour le LHC dans le cadre du projet LCG.

''' Programme Scientifique version 2 (9/2/07)'''

 14 mars matin (3h30) 9h-10h45 11H15-13h pause 10h45-11h15

==== 9h-9h05 Welcome ====

==== Etat des lieux pour le calcul au LHC en France====

''Coordination : Ghita Rahal,CC-IN2P3; Dominique Pallin, LPC-Clermont ''

* 09:05-09:15 -Infrastructure globale de grille en France et ressources associées F Malek
* 09:20-09:50 -mise en place de La grille francaise : T1 F Hernandez
* 09:55-10:20 -mise en place de La grille francaise: T2 etT3 F Chollet

* 10:25-10:45 & 11h15-13:00 -Présentation de l'état du calcul dans les expériences:
*** Les modèles de calcul des expériences (overview)
*** Quelle participation dans la mise en place du calcul (en france)?
*** Adéquation entre les infrastructures/ressources et les besoins.
*** Etat de la production des données de simulation
*** Etat d'avancement par rapport à l'objectif de la prise de données de fin 2007.
*** Difficultés, les points à améliorer…
*
* 10:25-11:45 -ALICE Y schutz
* 10:45-11h15 ----------------- Pause ---------------------------
* 11:15-11:35 -ATLAS E Lancon
* 11:40-12:00 -CMS C Charlot
* 12:05-12:25 -LHCb A Tsaregorodtsev
* 12:30-13:00 -discussion/tour de table sur l'ensemble de la session
*** la grille francaise, sa mise en place et son utilisation, Du point de vue des sites, des collaborations LHC et des utilisateurs

*

 14 mars après-midi (3h) 14h45-16h15 16H45-18h15 pause 16h15-16h45

==== Gestion et exploitation des grilles de calcul ====
Couvrir 2 aspects complémentaires :

-les actions des sites -> les conséquences au niveau des utilisateurs

-les actions des utilisateurs -> les conséquences au niveau des sites

Coordination : Christine Leroy, Dapnia-Saclay; Pierre Girard, Ingénieur, CC-IN2P3

* le fonctionnement d'un site de la grille :
du déploiement du middleware à la gestion de sa production, en passant par les procédures qu'il doit suivre, comme la déclaration de "scheduled downtime", l'utilisation des outils officiels de monitoring (SAM, GSTAT, etc) et leurs conséquences (disparition partielle ou complète de la production, etc), sécurité,etc.

* la gestion de jobs grilles :
de la façon dont ils sont soumis par les utilisateurs à la façon dont ils sont traités par les sites (dont la mise au point des formules de rank pour l'élection d'un site de soumission, le manque d'attractivité d'un site pour les jobs ou l'inverse, la gestion des priorités sur les jobs, des jobs pilotes, exécuteurs, etc.)

A- Sous-session "Gestion des jobs grille"

Dans cette première sous-session, il est demandé à chaque VO d'apporter des clarifications concernant les points suivants :

<OL>
<LI>Méthode(s) de distribution des jobs sur les sites :
<UL>
<LI>utilisation ou non d'un RB ?</LI>
<LI>utilisation ou non des informations publiées ?</LI>
<LI>Critère d'élection d'un site ? etc.</LI>
</UL>
</LI>
<LI>Organisation de la production
<UL>
<LI>qui fait quoi, qui soumet quoi, les rôles, les histoires de priorité...</LI>
<LI>une production française ou pas</LI>
<LI>Système de monitoring pour les jobs ? Si oui, utilisable ou pas par les sites ? Quel est son principe de fonctionnement, etc.</LI>
<LI>gestion des proxy</LI>
<LI>Méthode d'installation des softs (+ desinstallation)</LI>
<LI>comment un nouvel OS est validé et l'information transmise</LI>

</UL>
</LI>
<LI>Amélioration attendue et perspectives pour la gestion des jobs</LI>
</OL>


14:45 Introduction (5', Christine/Pierre)
14:50 Spécificités d'Alice (10', Artem ?)
15:00 Spécificités d'Atlas (10', Jérôme Schwi? Stéphane ? Karim ?)
15:10 Spécificités de Cms (10', Claude ? Artem ?)
15:20 Spécificités de Lhcb (10', Andrei ou Sabine?)
15:30 Discussions (45')

B- Sous-Session "Fonctionnement des sites" 


16:45 "Exploitation globale de la grille" (20' + 10', Hélène C.)
<UL>
<LI>Interaction entre outils de gestion de l'exploitation et la production</LI>
<LI>Comment les utilisateurs peuvent accéder aux informations</LI>
<LI>les outils d'exploitation (GOC DB, SAM, GSTAT, MonALISA et le CIC Portal)</LI>
<LI>L'accounting</LI>
<LI>Comment mesurer l’efficacite d’un site (utilisationCPU/CPU; resource disponible/resource indisponible ;jobs plantes/ jobs/reussis)</LI>
</UL>



17:15 "Fonctionnement d’un site"? (45', 3 intervenants ?)
<OL>
<LI>Suivi de jobs(15', David Bouvet)
<UL>
<LI>Est-ce qu'on peut retracer un job qui a planté pour savoir ce qu'il a utilisé comme ressources et pourquoi il a planté?</LI>
<LI>Est-ce qu'on peut s'assurer qu'un job qui a bien tourné, a tourné avec les bonnes librairies (Y'a-t-il des vérifications par les sites?)</LI>
<LI>Detection de jobs qui se plantent instantanement car probleme sur un WN ?</LI>
</UL>
</LI>

<LI>Gestion des pannes(15',?)
<UL>
<LI>Monitoring local, avez-vous un moyen de verifier « l’integrite » des WN ? Place disque disponible sur chaque WN</LI>
</UL>
</LI>

<LI>Le scheduling et le tuning (15', Michel Jouvin)
<UL>
<LI>Peut on mixer job d’analyse et job de simulation sur les WNs (pour optimiser IO et CPU) ?</LI>
<LI>Le manque d'attractivité d'un site pour les jobs ou l'inverse => état des lieux et amélioration en vue côté mw if any</LI>
<LI>la gestion des priorités sur les jobs</LI>
</UL>
</LI>
</OL>



17:45 "Gestion de l'infrastructure d'un site" (30',Pierre-Louis, Clermont)


==== Mise en place d’un site ====
L’exemple du T2 du LPC Clermont-Ferrand. Visite du site possible durant les 2 jours par petits groupes

* Salle machine (réseau électrique, climatisation,…)
* Choix matériel
* Sécurité
* Les difficultés rencontrées

 15 mars matin (3h30) 9h-10h45 11H15-13h pause 10h45-11h15

==== Gestion des données grilles ====
Du point de vue des sites, des collaborations LHC et des utilisateurs

''Coordination : Lionel Schwarz (CC), Stéphane Jézequel(LAPP, Atlas) ''

* Transferts massifs de données
Dans cette partie, l'objectif est de comprendre l'utilisation de FTS et
les outils de mouvement de fichiers (Phedex, DDM...) ce qui fonctionne,
ce qui ne fonctionne pas. Il serait bon de rappeler le trajet des différentes
donnees et lesquelles sont sous la responsabilite de quel site.
Egalement, l'organisation en T2-T3, nuages... des donnees des
expériences. Il faudrait obtenir des chiffres au niveau des debits
prevus entre T1-T2.
** Point sur l'infrastructure réseau et logicielle (FTS, SRM) des sites (5') - L. Schwarz
** Transferts massifs Alice (10')
** Transferts massifs Atlas (10')
** Transferts massifs CMS (10')
** Transferts massifs LHCb (10')
** Discussion (15')

* Accès aux données
Cette partie est consacrée à la problématique de l'accès aux données par
les jobs. Quel protocole est envisagé? Accès local/à distance?
Debit prévu, nombre de jobs? Problème des données utilisateur? Cohabitation
transfert des données/accès pour l'analyse. Téléchargement de données...
** Modèle d'accès aux données de LHCb (10')
** Modèle d'accès aux données de CMS (10')
** Modèle d'accès aux données de Atlas (10')
** Modèle d'accès aux données de Alice (10')
** Discussion (30')

 15 mars après-midi (2h40) 14h15-15h45 16H05-17h15 pause 15h45-16h05

==== Les centres d’analyses ====
Du point de vue des sites, des collaborations LHC et des utilisateurs

''Coordination : Eric Lancon,Dapnia-Saclay ; Claude Charlot LLR; Frédéric Derue LPNHE ''

* mise en place
* les contours
* les logiciels d’analyses (Ganga,..)
* Coordination avec les T3s ? mise en commun de ressources ?

==== Conclusions F Malek ====

*

Draft of the scientific programm

2007-01-29T14:12:46Z

Grahal: /* Etat des lieux pour le calcul au LHC en France */

D.P. ,F.M. 7/12/2006
==== Objectifs ====
LCG-France organise son 2ème colloque à Clermont-Ferrand les 14 et 15 mars 2007. Ces journées sont destinées à tous les acteurs de la grille de calcul au LHC (gestionnaires de site et utilisateurs) de l'IN2P3 et du Dapnia. Elles ont pour objectifs d’offrir un lieu d’échange et de communication sur les actions, les idées et les expériences en cours dans la mise en place du calcul pour le LHC dans le cadre du projet LCG.

''' Programme Scientifique version 1 (7/12/06)'''

 14 mars matin (3h) 9h30-11h 11H30-13h pause 11h-11h30

==== Etat des lieux pour le calcul au LHC en France====

''Coordination : Ghita Rahal,CC-IN2P3; Dominique Pallin, LPC-Clermont ''

* 9:30-10:00 -Infrastructure globale de grille en France et ressources associées
**20min+10min de discussion:Fayrouz Malek?
* 10:00-10:30 -Présentation des sites (T1 et sites associés,T2 etT3) + T2 étrangers associés
**20 min+10min de discussion: Dominique Boutigny, Frédérique Chollet?
* 10:30-11:00 -La grille:
**20min+10min discussion: Fabio Hernandez?
***Son évolution en vue des données LHC 2009-2010
***Les difficultés rencontrées;
* ---------------------------- Pause ---------------------------
* 11:30-13:00 -Présentation de l'état du calcul dans les expériences:
**20 min par expérience+10 min de discussion:Eric Lançon, Schultz, Tzagarodiev, Claude Charlot ?
*** Les modèles de calcul des expériences
*** Qui est impliqué dans la mise en place du calcul?
*** Adéquation entre les infrastructure/ressources et les besoins.
*** Etat de la production des données de simulation
*** Etat d'avancement par rapport à l'objectif de la prise de données de fin 2007.
*** Difficultés, les points à améliorer…
*

 14 mars après-midi (3h) 14h45-16h15 16H45-18h15 pause 16h15-16h45

==== Gestion et exploitation des grilles de calcul ====
Couvrir 2 aspects complémentaires :

-les actions des sites -> les conséquences au niveau des utilisateurs

-les actions des utilisateurs -> les conséquences au niveau des sites

''Coordination : Christine Leroy, Dapnia-Saclay; Pierre Girard, Ingénieur, CC-IN2P3''

* le fonctionnement d'un site de la grille :
du déploiement du middleware à la gestion de sa production, en passant par les procédures qu'il doit suivre, comme la déclaration de "scheduled downtime", l'utilisation des outils officiels de monitoring (SAM, GSTAT, etc) et leurs conséquences (disparition partielle ou complète de la production, etc), sécurité,etc.

* la gestion de jobs grilles :
de la façon dont ils sont soumis par les utilisateurs à la façon dont ils sont traités par les sites (dont la mise au point des formules de rank pour l'élection d'un site de soumission, le manque d'attractivité d'un site pour les jobs ou l'inverse, la gestion des priorités sur les jobs, des jobs pilotes, exécuteurs, etc.)

==== Mise en place d’un site ====
L’exemple du T2 du LPC Clermont-Ferrand. Visite du site possible durant les 2 jours par petits groupes

* Salle machine (réseau électrique, climatisation,…)
* Choix matériel
* Sécurité
* Les difficultés rencontrées

 15 mars matin (3h30) 9h-10h45 11H15-13h pause 10h45-11h15

==== Gestion des données grilles ====
Du point de vue des sites, des collaborations LHC et des utilisateurs

''Coordination : Lionel Schwarz, CC-IN2P3 ? ; Representant ALICE, LHCb? ''

* Réseaux, trafic
* Transfert des données SRM, FTS,…
* Stockage ?

 15 mars après-midi (2h40) 14h15-15h45 16H05-17h15 pause 15h45-16h05

==== Les centres d’analyses ====
Du point de vue des sites, des collaborations LHC et des utilisateurs

''Coordination : Eric Lancon,Dapnia-Saclay ; Claude Charlot ? ''

* mise en place
* les contours
* les logiciels d’analyses (Ganga,..)
* Coordination avec les T3s ? mise en commun de ressources ?

==== Grille de Recherche : Grid5000 ? ====

*

Draft of the scientific programm

2007-01-29T14:11:49Z

Grahal: /* Etat des lieux pour le calcul au LHC en France */

D.P. ,F.M. 7/12/2006
==== Objectifs ====
LCG-France organise son 2ème colloque à Clermont-Ferrand les 14 et 15 mars 2007. Ces journées sont destinées à tous les acteurs de la grille de calcul au LHC (gestionnaires de site et utilisateurs) de l'IN2P3 et du Dapnia. Elles ont pour objectifs d’offrir un lieu d’échange et de communication sur les actions, les idées et les expériences en cours dans la mise en place du calcul pour le LHC dans le cadre du projet LCG.

''' Programme Scientifique version 1 (7/12/06)'''

 14 mars matin (3h) 9h30-11h 11H30-13h pause 11h-11h30

==== Etat des lieux pour le calcul au LHC en France====

''Coordination : Ghita Rahal,CC-IN2P3; Dominique Pallin, LPC-Clermont ''

* 9:30-10:00 -Infrastructure globale de grille en France et ressources associées
**20min+10min de discussion:Fayrouz Malek?
* 10:00-10:30 -Présentation des sites (T1 et sites associés,T2 etT3) + T2 étrangers associés
**20 min+10min de discussion: Dominique Boutigny, Frédérique Chollet?
* 10:30-11:00 -La grille:
**20min+10min discussion: Fabio Hernandez?
***Son évolution en vue des données LHC 2009-2010
***Les difficultés rencontrées;
* ---------------------------- Pause ---------------------------
* 11:30-12:50 -Présentation de l'état du calcul dans les expériences:
**20 min par expérience+10 min de discussion:Eric Lançon, Schultz, Tzagarodiev, Claude Charlot ?
*** Les modèles de calcul des expériences
*** Qui est impliqué dans la mise en place du calcul?
*** Adéquation entre les infrastructure/ressources et les besoins.
*** Etat de la production des données de simulation
*** Etat d'avancement par rapport à l'objectif de la prise de données de fin 2007.
*** Difficultés, les points à améliorer…
*

 14 mars après-midi (3h) 14h45-16h15 16H45-18h15 pause 16h15-16h45

==== Gestion et exploitation des grilles de calcul ====
Couvrir 2 aspects complémentaires :

-les actions des sites -> les conséquences au niveau des utilisateurs

-les actions des utilisateurs -> les conséquences au niveau des sites

''Coordination : Christine Leroy, Dapnia-Saclay; Pierre Girard, Ingénieur, CC-IN2P3''

* le fonctionnement d'un site de la grille :
du déploiement du middleware à la gestion de sa production, en passant par les procédures qu'il doit suivre, comme la déclaration de "scheduled downtime", l'utilisation des outils officiels de monitoring (SAM, GSTAT, etc) et leurs conséquences (disparition partielle ou complète de la production, etc), sécurité,etc.

* la gestion de jobs grilles :
de la façon dont ils sont soumis par les utilisateurs à la façon dont ils sont traités par les sites (dont la mise au point des formules de rank pour l'élection d'un site de soumission, le manque d'attractivité d'un site pour les jobs ou l'inverse, la gestion des priorités sur les jobs, des jobs pilotes, exécuteurs, etc.)

==== Mise en place d’un site ====
L’exemple du T2 du LPC Clermont-Ferrand. Visite du site possible durant les 2 jours par petits groupes

* Salle machine (réseau électrique, climatisation,…)
* Choix matériel
* Sécurité
* Les difficultés rencontrées

 15 mars matin (3h30) 9h-10h45 11H15-13h pause 10h45-11h15

==== Gestion des données grilles ====
Du point de vue des sites, des collaborations LHC et des utilisateurs

''Coordination : Lionel Schwarz, CC-IN2P3 ? ; Representant ALICE, LHCb? ''

* Réseaux, trafic
* Transfert des données SRM, FTS,…
* Stockage ?

 15 mars après-midi (2h40) 14h15-15h45 16H05-17h15 pause 15h45-16h05

==== Les centres d’analyses ====
Du point de vue des sites, des collaborations LHC et des utilisateurs

''Coordination : Eric Lancon,Dapnia-Saclay ; Claude Charlot ? ''

* mise en place
* les contours
* les logiciels d’analyses (Ganga,..)
* Coordination avec les T3s ? mise en commun de ressources ?

==== Grille de Recherche : Grid5000 ? ====

*

Draft of the scientific programm

2007-01-29T14:10:53Z

Grahal: /* Etat des lieux pour le calcul au LHC en France */

D.P. ,F.M. 7/12/2006
==== Objectifs ====
LCG-France organise son 2ème colloque à Clermont-Ferrand les 14 et 15 mars 2007. Ces journées sont destinées à tous les acteurs de la grille de calcul au LHC (gestionnaires de site et utilisateurs) de l'IN2P3 et du Dapnia. Elles ont pour objectifs d’offrir un lieu d’échange et de communication sur les actions, les idées et les expériences en cours dans la mise en place du calcul pour le LHC dans le cadre du projet LCG.

''' Programme Scientifique version 1 (7/12/06)'''

 14 mars matin (3h) 9h30-11h 11H30-13h pause 11h-11h30

==== Etat des lieux pour le calcul au LHC en France====

''Coordination : Ghita Rahal,CC-IN2P3; Dominique Pallin, LPC-Clermont ''

* 9:30-10:00 -Infrastructure globale de grille en France et ressources associées
**20min+10min de discussion:Fayrouz Malek?
* 10:00-10:30 -Présentation des sites (T1 et sites associés,T2 etT3) + T2 étrangers associés
**20 min+10min de discussion: Dominique Boutigny, Frédérique Chollet?
* 10:30-11:00 -La grille:
**20min+10min discussion: Fabio Hernandez?
**Son évolution en vue des données LHC 2009-2010
**Les difficultés rencontrées;
* ---------------------------- Pause ---------------------------
* 11:30-12:50 -Présentation de l'état du calcul dans les expériences:
**20 min par expérience+10 min de discussion:Eric Lançon, Schultz, Tzagarodiev, Claude Charlot ?
** Les modèles de calcul des expériences
** Qui est impliqué dans la mise en place du calcul?
** Adéquation entre les infrastructure/ressources et les besoins.
** Etat de la production des données de simulation
** Etat d'avancement par rapport à l'objectif de la prise de données de fin 2007.
** Difficultés, les points à améliorer…
*

 14 mars après-midi (3h) 14h45-16h15 16H45-18h15 pause 16h15-16h45

==== Gestion et exploitation des grilles de calcul ====
Couvrir 2 aspects complémentaires :

-les actions des sites -> les conséquences au niveau des utilisateurs

-les actions des utilisateurs -> les conséquences au niveau des sites

''Coordination : Christine Leroy, Dapnia-Saclay; Pierre Girard, Ingénieur, CC-IN2P3''

* le fonctionnement d'un site de la grille :
du déploiement du middleware à la gestion de sa production, en passant par les procédures qu'il doit suivre, comme la déclaration de "scheduled downtime", l'utilisation des outils officiels de monitoring (SAM, GSTAT, etc) et leurs conséquences (disparition partielle ou complète de la production, etc), sécurité,etc.

* la gestion de jobs grilles :
de la façon dont ils sont soumis par les utilisateurs à la façon dont ils sont traités par les sites (dont la mise au point des formules de rank pour l'élection d'un site de soumission, le manque d'attractivité d'un site pour les jobs ou l'inverse, la gestion des priorités sur les jobs, des jobs pilotes, exécuteurs, etc.)

==== Mise en place d’un site ====
L’exemple du T2 du LPC Clermont-Ferrand. Visite du site possible durant les 2 jours par petits groupes

* Salle machine (réseau électrique, climatisation,…)
* Choix matériel
* Sécurité
* Les difficultés rencontrées

 15 mars matin (3h30) 9h-10h45 11H15-13h pause 10h45-11h15

==== Gestion des données grilles ====
Du point de vue des sites, des collaborations LHC et des utilisateurs

''Coordination : Lionel Schwarz, CC-IN2P3 ? ; Representant ALICE, LHCb? ''

* Réseaux, trafic
* Transfert des données SRM, FTS,…
* Stockage ?

 15 mars après-midi (2h40) 14h15-15h45 16H05-17h15 pause 15h45-16h05

==== Les centres d’analyses ====
Du point de vue des sites, des collaborations LHC et des utilisateurs

''Coordination : Eric Lancon,Dapnia-Saclay ; Claude Charlot ? ''

* mise en place
* les contours
* les logiciels d’analyses (Ganga,..)
* Coordination avec les T3s ? mise en commun de ressources ?

==== Grille de Recherche : Grid5000 ? ====

*

Draft of the scientific programm

2007-01-29T14:07:23Z

Grahal: /* Etat des lieux pour le calcul au LHC en France */

D.P. ,F.M. 7/12/2006
==== Objectifs ====
LCG-France organise son 2ème colloque à Clermont-Ferrand les 14 et 15 mars 2007. Ces journées sont destinées à tous les acteurs de la grille de calcul au LHC (gestionnaires de site et utilisateurs) de l'IN2P3 et du Dapnia. Elles ont pour objectifs d’offrir un lieu d’échange et de communication sur les actions, les idées et les expériences en cours dans la mise en place du calcul pour le LHC dans le cadre du projet LCG.

''' Programme Scientifique version 1 (7/12/06)'''

 14 mars matin (3h) 9h30-11h 11H30-13h pause 11h-11h30

==== Etat des lieux pour le calcul au LHC en France====

''Coordination : Ghita Rahal,CC-IN2P3; Dominique Pallin, LPC-Clermont ''

* 9:30-10:00 (20min+10min de discussion)Fayrouz Malek? Infrastructure globale de grille en France et ressources associées
* 10:00-10:30 (20 min+10min de discussion) Dominique Boutigny, Frédérique Chollet? Présentation des sites (T1 et sites associés,T2 etT3) + T2 étrangers associés
* 10:30-11:00 (20min+10min) Fabio Hernandez? La grille
**Son évolution en vue des données LHC 2009-2010
**Les difficultés rencontrées;
* ---------------------------- Pause ---------------------------
* 11:30-12:50 : (20 min par expérience+10 min de discussion): (Eric Lançon, Schultz, Tzagarodiev, Claude Charlot ?)
* Présentation de l'état du calcul dans les expériences:
** Les modèles de calcul des expériences
** Qui est impliqué dans la mise en place du calcul?
** Adéquation entre les infrastructure/ressources et les besoins.
** Etat de la production des données de simulation
** Etat d'avancement par rapport à l'objectif de la prise de données de fin 2007.
** Difficultés, les points à améliorer…
*

 14 mars après-midi (3h) 14h45-16h15 16H45-18h15 pause 16h15-16h45

==== Gestion et exploitation des grilles de calcul ====
Couvrir 2 aspects complémentaires :

-les actions des sites -> les conséquences au niveau des utilisateurs

-les actions des utilisateurs -> les conséquences au niveau des sites

''Coordination : Christine Leroy, Dapnia-Saclay; Pierre Girard, Ingénieur, CC-IN2P3''

* le fonctionnement d'un site de la grille :
du déploiement du middleware à la gestion de sa production, en passant par les procédures qu'il doit suivre, comme la déclaration de "scheduled downtime", l'utilisation des outils officiels de monitoring (SAM, GSTAT, etc) et leurs conséquences (disparition partielle ou complète de la production, etc), sécurité,etc.

* la gestion de jobs grilles :
de la façon dont ils sont soumis par les utilisateurs à la façon dont ils sont traités par les sites (dont la mise au point des formules de rank pour l'élection d'un site de soumission, le manque d'attractivité d'un site pour les jobs ou l'inverse, la gestion des priorités sur les jobs, des jobs pilotes, exécuteurs, etc.)

==== Mise en place d’un site ====
L’exemple du T2 du LPC Clermont-Ferrand. Visite du site possible durant les 2 jours par petits groupes

* Salle machine (réseau électrique, climatisation,…)
* Choix matériel
* Sécurité
* Les difficultés rencontrées

 15 mars matin (3h30) 9h-10h45 11H15-13h pause 10h45-11h15

==== Gestion des données grilles ====
Du point de vue des sites, des collaborations LHC et des utilisateurs

''Coordination : Lionel Schwarz, CC-IN2P3 ? ; Representant ALICE, LHCb? ''

* Réseaux, trafic
* Transfert des données SRM, FTS,…
* Stockage ?

 15 mars après-midi (2h40) 14h15-15h45 16H05-17h15 pause 15h45-16h05

==== Les centres d’analyses ====
Du point de vue des sites, des collaborations LHC et des utilisateurs

''Coordination : Eric Lancon,Dapnia-Saclay ; Claude Charlot ? ''

* mise en place
* les contours
* les logiciels d’analyses (Ganga,..)
* Coordination avec les T3s ? mise en commun de ressources ?

==== Grille de Recherche : Grid5000 ? ====

*

Draft of the scientific programm

2007-01-29T14:05:39Z

Grahal: /* Etat des lieux pour le calcul au LHC en France */

D.P. ,F.M. 7/12/2006
==== Objectifs ====
LCG-France organise son 2ème colloque à Clermont-Ferrand les 14 et 15 mars 2007. Ces journées sont destinées à tous les acteurs de la grille de calcul au LHC (gestionnaires de site et utilisateurs) de l'IN2P3 et du Dapnia. Elles ont pour objectifs d’offrir un lieu d’échange et de communication sur les actions, les idées et les expériences en cours dans la mise en place du calcul pour le LHC dans le cadre du projet LCG.

''' Programme Scientifique version 1 (7/12/06)'''

 14 mars matin (3h) 9h30-11h 11H30-13h pause 11h-11h30

==== Etat des lieux pour le calcul au LHC en France====

''Coordination : Ghita Rahal,CC-IN2P3; Dominique Pallin, LPC-Clermont ''

* 9:30-10:00 (20min+10min de discussion)Fayrouz Malek? Infrastructure globale de grille en France et ressources associées
* 10:00-10:30 (20 min+10min de discussion) Dominique Boutigny, Frédérique Chollet? Présentation des sites (T1 et sites associés,T2 etT3) + T2 étrangers associés
* 10:30-11:00 (20min+10min) Fabio Hernandez? La grille et son évolution en vue des données LHC 2009-2010 ?
* ---------------------------- Pause ---------------------------
* 11:30-12:50 : (20 min par expérience+10 min de discussion): (Eric Lançon, Schultz, Tzagarodiev, Claude Charlot ?)
* Présentation de l'état du calcul dans les expériences:
** Les modèles de calcul des expériences
** Qui est impliqué dans la mise en place du calcul?
** Adéquation entre les infrastructure/ressources et les besoins.
** Etat de la production des données de simulation
** Etat d'avancement par rapport à l'objectif de la prise de données de fin 2007.
** Difficultés, les points à améliorer…
*

 14 mars après-midi (3h) 14h45-16h15 16H45-18h15 pause 16h15-16h45

==== Gestion et exploitation des grilles de calcul ====
Couvrir 2 aspects complémentaires :

-les actions des sites -> les conséquences au niveau des utilisateurs

-les actions des utilisateurs -> les conséquences au niveau des sites

''Coordination : Christine Leroy, Dapnia-Saclay; Pierre Girard, Ingénieur, CC-IN2P3''

* le fonctionnement d'un site de la grille :
du déploiement du middleware à la gestion de sa production, en passant par les procédures qu'il doit suivre, comme la déclaration de "scheduled downtime", l'utilisation des outils officiels de monitoring (SAM, GSTAT, etc) et leurs conséquences (disparition partielle ou complète de la production, etc), sécurité,etc.

* la gestion de jobs grilles :
de la façon dont ils sont soumis par les utilisateurs à la façon dont ils sont traités par les sites (dont la mise au point des formules de rank pour l'élection d'un site de soumission, le manque d'attractivité d'un site pour les jobs ou l'inverse, la gestion des priorités sur les jobs, des jobs pilotes, exécuteurs, etc.)

==== Mise en place d’un site ====
L’exemple du T2 du LPC Clermont-Ferrand. Visite du site possible durant les 2 jours par petits groupes

* Salle machine (réseau électrique, climatisation,…)
* Choix matériel
* Sécurité
* Les difficultés rencontrées

 15 mars matin (3h30) 9h-10h45 11H15-13h pause 10h45-11h15

==== Gestion des données grilles ====
Du point de vue des sites, des collaborations LHC et des utilisateurs

''Coordination : Lionel Schwarz, CC-IN2P3 ? ; Representant ALICE, LHCb? ''

* Réseaux, trafic
* Transfert des données SRM, FTS,…
* Stockage ?

 15 mars après-midi (2h40) 14h15-15h45 16H05-17h15 pause 15h45-16h05

==== Les centres d’analyses ====
Du point de vue des sites, des collaborations LHC et des utilisateurs

''Coordination : Eric Lancon,Dapnia-Saclay ; Claude Charlot ? ''

* mise en place
* les contours
* les logiciels d’analyses (Ganga,..)
* Coordination avec les T3s ? mise en commun de ressources ?

==== Grille de Recherche : Grid5000 ? ====

*

Draft of the scientific programm

2007-01-29T14:00:21Z

Grahal: /* Etat des lieux pour le calcul au LHC en France */

D.P. ,F.M. 7/12/2006
==== Objectifs ====
LCG-France organise son 2ème colloque à Clermont-Ferrand les 14 et 15 mars 2007. Ces journées sont destinées à tous les acteurs de la grille de calcul au LHC (gestionnaires de site et utilisateurs) de l'IN2P3 et du Dapnia. Elles ont pour objectifs d’offrir un lieu d’échange et de communication sur les actions, les idées et les expériences en cours dans la mise en place du calcul pour le LHC dans le cadre du projet LCG.

''' Programme Scientifique version 1 (7/12/06)'''

 14 mars matin (3h) 9h30-11h 11H30-13h pause 11h-11h30

==== Etat des lieux pour le calcul au LHC en France====

''Coordination : Ghita Rahal,CC-IN2P3; Dominique Pallin, LPC-Clermont ''

* 9:30-10:00 Fayrouz Malek? Infrastructure globale de grille en France et ressources associées
* 10:00-10:30 Dominique Boutigny, Frédérique Chollet ? Présentation des sites (T1 et sites associés,T2 etT3) + T2 étrangers associés
* 10:30-11:00 Fabio Hernandez? La grille et son évolution en vue des données LHC 2009-2010 ?
* ---------------------------- Pause ---------------------------
* 11:30-12:50 : 20 min par expérience: (Eric Lançon, Schultz, Tz., Claude Ch. ?)
* Présentation de l'état du calcul dans les expériences:
** Les modèles de calcul des expériences
** Qui est impliqué dans la mise en place du calcul?
** Adéquation entre les infrastructure/ressources et les besoins.
** Etat de la production des données de simulation
** Etat d'avancement par rapport à l'objectif de la prise de données de fin 2007.
** Difficultés, les points à améliorer…
*

 14 mars après-midi (3h) 14h45-16h15 16H45-18h15 pause 16h15-16h45

==== Gestion et exploitation des grilles de calcul ====
Couvrir 2 aspects complémentaires :

-les actions des sites -> les conséquences au niveau des utilisateurs

-les actions des utilisateurs -> les conséquences au niveau des sites

''Coordination : Christine Leroy, Dapnia-Saclay; Pierre Girard, Ingénieur, CC-IN2P3''

* le fonctionnement d'un site de la grille :
du déploiement du middleware à la gestion de sa production, en passant par les procédures qu'il doit suivre, comme la déclaration de "scheduled downtime", l'utilisation des outils officiels de monitoring (SAM, GSTAT, etc) et leurs conséquences (disparition partielle ou complète de la production, etc), sécurité,etc.

* la gestion de jobs grilles :
de la façon dont ils sont soumis par les utilisateurs à la façon dont ils sont traités par les sites (dont la mise au point des formules de rank pour l'élection d'un site de soumission, le manque d'attractivité d'un site pour les jobs ou l'inverse, la gestion des priorités sur les jobs, des jobs pilotes, exécuteurs, etc.)

==== Mise en place d’un site ====
L’exemple du T2 du LPC Clermont-Ferrand. Visite du site possible durant les 2 jours par petits groupes

* Salle machine (réseau électrique, climatisation,…)
* Choix matériel
* Sécurité
* Les difficultés rencontrées

 15 mars matin (3h30) 9h-10h45 11H15-13h pause 10h45-11h15

==== Gestion des données grilles ====
Du point de vue des sites, des collaborations LHC et des utilisateurs

''Coordination : Lionel Schwarz, CC-IN2P3 ? ; Representant ALICE, LHCb? ''

* Réseaux, trafic
* Transfert des données SRM, FTS,…
* Stockage ?

 15 mars après-midi (2h40) 14h15-15h45 16H05-17h15 pause 15h45-16h05

==== Les centres d’analyses ====
Du point de vue des sites, des collaborations LHC et des utilisateurs

''Coordination : Eric Lancon,Dapnia-Saclay ; Claude Charlot ? ''

* mise en place
* les contours
* les logiciels d’analyses (Ganga,..)
* Coordination avec les T3s ? mise en commun de ressources ?

==== Grille de Recherche : Grid5000 ? ====

*

Draft of the scientific programm

2007-01-29T13:57:14Z

Grahal: /* Etat des lieux pour le calcul au LHC en France */

D.P. ,F.M. 7/12/2006
==== Objectifs ====
LCG-France organise son 2ème colloque à Clermont-Ferrand les 14 et 15 mars 2007. Ces journées sont destinées à tous les acteurs de la grille de calcul au LHC (gestionnaires de site et utilisateurs) de l'IN2P3 et du Dapnia. Elles ont pour objectifs d’offrir un lieu d’échange et de communication sur les actions, les idées et les expériences en cours dans la mise en place du calcul pour le LHC dans le cadre du projet LCG.

''' Programme Scientifique version 1 (7/12/06)'''

 14 mars matin (3h) 9h30-11h 11H30-13h pause 11h-11h30

==== Etat des lieux pour le calcul au LHC en France====

''Coordination : Ghita Rahal,CC-IN2P3; Dominique Pallin, LPC-Clermont ''

* 9:30-10:00 Fayrouz? Infrastructure globale de grille en France et ressources associées
* 10:00-10:30 Dominique B, Frederique C ?Présentation des sites (T1 et sites associés,T2 etT3) + T2 étrangers associés
* 10:30-11:00 La grille et son évolution en vue des données LHC 2009-2010 ?
* ---------------------------- Pause ---------------------------
* 11:30-12:50 : 20 min par expérience: (Eric L., Sch., Tz., Claude Ch. ?)
* Présentation de l'état du calcul dans les expériences:
** Les modèles de calcul des expériences
** Qui est impliqué dans la mise en place du calcul?
** Adéquation entre les infrastructure/ressources et les besoins.
** Etat de la production des données de simulation
** Etat d'avancement par rapport à l'objectif de la prise de données de fin 2007.
** Difficultés, les points à améliorer…
*

 14 mars après-midi (3h) 14h45-16h15 16H45-18h15 pause 16h15-16h45

==== Gestion et exploitation des grilles de calcul ====
Couvrir 2 aspects complémentaires :

-les actions des sites -> les conséquences au niveau des utilisateurs

-les actions des utilisateurs -> les conséquences au niveau des sites

''Coordination : Christine Leroy, Dapnia-Saclay; Pierre Girard, Ingénieur, CC-IN2P3''

* le fonctionnement d'un site de la grille :
du déploiement du middleware à la gestion de sa production, en passant par les procédures qu'il doit suivre, comme la déclaration de "scheduled downtime", l'utilisation des outils officiels de monitoring (SAM, GSTAT, etc) et leurs conséquences (disparition partielle ou complète de la production, etc), sécurité,etc.

* la gestion de jobs grilles :
de la façon dont ils sont soumis par les utilisateurs à la façon dont ils sont traités par les sites (dont la mise au point des formules de rank pour l'élection d'un site de soumission, le manque d'attractivité d'un site pour les jobs ou l'inverse, la gestion des priorités sur les jobs, des jobs pilotes, exécuteurs, etc.)

==== Mise en place d’un site ====
L’exemple du T2 du LPC Clermont-Ferrand. Visite du site possible durant les 2 jours par petits groupes

* Salle machine (réseau électrique, climatisation,…)
* Choix matériel
* Sécurité
* Les difficultés rencontrées

 15 mars matin (3h30) 9h-10h45 11H15-13h pause 10h45-11h15

==== Gestion des données grilles ====
Du point de vue des sites, des collaborations LHC et des utilisateurs

''Coordination : Lionel Schwarz, CC-IN2P3 ? ; Representant ALICE, LHCb? ''

* Réseaux, trafic
* Transfert des données SRM, FTS,…
* Stockage ?

 15 mars après-midi (2h40) 14h15-15h45 16H05-17h15 pause 15h45-16h05

==== Les centres d’analyses ====
Du point de vue des sites, des collaborations LHC et des utilisateurs

''Coordination : Eric Lancon,Dapnia-Saclay ; Claude Charlot ? ''

* mise en place
* les contours
* les logiciels d’analyses (Ganga,..)
* Coordination avec les T3s ? mise en commun de ressources ?

==== Grille de Recherche : Grid5000 ? ====

*

Atlas:SC4-Sept06

2006-10-05T10:54:38Z

Grahal: /* Logbook */

== DDM monitoring ==
* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackday.png
* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackdayLYON.png
* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackdayt2.png
* [[ Atlas:DDMmonitoring| DDM monitoring ]]
* [http://lcg2.in2p3.fr/wiki/index.php/Atlas#Resources_monitoring Other monitorings]

== Logbook ==
* In LYONDISK, files older than 24 hours are deleted (not LFC entries). Since datasets are destroyed at CERN 24 hours after its creation, subscription to T2s are done only if datasets are younger than 0.8 days.
* 5 October:
** Transfer problems LYON->GRIF; investigating
* 4 October:
** Many transfers to Lyon finish with '''State from FTS: Failed; Retries: 4; Reason: Transfer failed. ERROR an end-of-file was reached''' (Problem solved by CERN in the afternoon)
** Good efficiency for transfers CERN-LYON
** Transfer T1-> T2 to all sites except CPPM and SACLAY (SE full)
** 15:51 Update the VOBOX to glite 3.0.4
* 3 October
** dcache for SC4 tests back in operation
** Start transfer from LYONDISK to T2s (try to follow online)
** Since dataset are destroyed at CERN after 24 hours, only datasets younger than 12 hours are transfered to T2s.
** Bad transfer rate to GRIF (FTS never finish for the 3 ATLAS sites)
** SE in CPPM is full
** 20-30 MB/s rate for 4 sites
* 2 October :
** Problems with dcache in Lyon
* 30 September-1 October :
** T0-T1 transfer chaotic due to problems for DDM to get FTS messages (use CERN FTS server) (then transfers are killed).
* Status after one week :
** Transfer ran smoothly with the usual problem of LFC access speed
** No T1-T2 transfer
[[Image:LYONregion-20060925-SC4.png]]
* 24 September: Upgrade of DDM software. VOBOX activity much lower.

[[Atlas | Page principale du Twiki ATLAS]]

Atlas:SC4

2006-09-25T12:58:34Z

Grahal: /* Daily news */

== ''Bienvenue sur la page Atlas SC4 LCG-France Welcome to the LCG-France Atlas SC4 page'' ==
[https://uimon.cern.ch/twiki/bin/view/Atlas/ATLASServiceChallenges Twiki page : SC4 ATLAS]

[http://lcg2.in2p3.fr/wiki/images/Sc4-juin06.txt Compte rendu de la réunion SC4 ATLAS au CERN du 9 Juin (S.Jézéquel, G. Rahal) (written in french) ]

* T0 Role(CERN)
** Produce dummy files with 1 to 2 GB size(RAW, ESD et AOD) (see [https://uimon.cern.ch/twiki/bin/view/Atlas/AtlasTierZero T0 Twiki])
** Initiate T0->T1 transfers
** FTS server sents files to Lyon choosing between 'TAPE' (RAW 43,2 Mo/s) or 'DISK' (ESD,AOD 23+20 Mo/s) areas
* T1 Role (CCIN2P3)
** Get files from T0 (dedicated dcache area: L. Schwarz)
** Provides LFC (lfc-atlas.in2p3.fr) and FTS service (cclcgftsli01.in2p3.fr) (D. Bouvet)
** Send all AODs to each T2 (20 Mo/s) using Lyon FTS server
** Regurlarly cleanup files
* T2 Role (BEIJING, LAL, LAPP, LPC, LPNHE, SACLAY, TOKYO)
** Get files from T1 (Lyon). Files on the T2 are written in /home/atlas/sc4tier0/...
** Clean-up the files (?)
* Other roles
** ATLAS (S. Jézéquel, G. Rahal) : Initiate T1->T2 transfers

== Information from DDM monitoring ==
* [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/ Main DDM monitoring page]

* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stack4h.png http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stack4ht2.png

----

* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackday.png
* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackdayLYON.png
* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackdayt2.png

----

* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackweek.png
* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackweekLYON.png
* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackweekt2.png

--

* Transfer rates for LYON and associated T2s (validated files by DDM):
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplots.php?site=LYON LYON]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=BEIJING BEIJING]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=LAL LAL]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=LAPP LAPP]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=LPC LPC]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=LPNHE LPNHE]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=SACLAY SACLAY]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=TOKYO TOKYO]

* [http://atldq02.cern.ch:8000/dq2/site_monitor/sites Detailed information on each site ]

* [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/sitestates.php?site=LYON File transfer state in LYON ]

== Information from FTS monitoring ==

*[http://gridview.cern.ch/GRIDVIEW/graphs.php?GraphName=atlas&ThruputDataOption=&SrcSite=&DestSite=&DurationOption=&StartDay=&StartMonth=&StartYear=&EndDay=&EndMonth=&EndYear=&HostType=&GraphFor=VO Atlas FTS transfer rate]

* [http://gridview.cern.ch/GRIDVIEW/graphs.php?GraphName=IN2PCC&ThruputDataOption=&SrcSite=&DestSite=&DurationOption=&StartDay=&StartMonth=&StartYear=&EndDay=&EndMonth=&EndYear=&HostType=&GraphFor= CERN->Lyon FTS transfer rate]

*T1->T2 :
** 15 concurrent files and 10 streams for LYON-TOKYO
** 5 concurrent files and 5 streams for LYON-BEIJING (SE not enough powerful for 15/15 )
** 10 concurrent files and 10 streams for LYON-French T2s (LAL, LPNHE, LPC, SACLAY) except for LAPP (5 concurrent files and 1 stream)

== Information from dCache monitoring (provided by Lyon) ==

*[http://cctools.in2p3.fr/dcache/transfers/atlas-sc4.html Monitoring of dcache for SC4 areas]
* LYONDISK : 25 gridftp concurrent access maximum
* LYONTAPE : 10 gridft concurrent access maximum

== VOBOX Configuration ==

* 4 processors 3 GHz
* 4 GB of memory ( 2 GB dedicated to SWAP)
* The monitoring of the Vobox daily, weekly and monthly can be found [http://atlas-france.in2p3.fr/Activites/Informatique/OutilsCC/VO-cclcgatlas Here]

== Disk space availability ==

* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=BEIJING-LCG2&visibility=SE BEIJING]
* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=CPPM-LCG2&visibility=SE CPPM]
* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=GRIF&visibility=SE GRIF]
* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=IN2P3-LPC&visibility=SE LPC]
* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=IN2P3-LAPP&visibility=SE LAPP]
* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=TOKYO-LCG2&visibility=SE TOKYO]
* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=IN2P3-CC&visibility=SE LYON]

== Daily news ==

* [https://uimon.cern.ch/twiki/bin/view/Atlas/DDMSc4#Daily_log SC4 Data Managment Daily log]

* SC4 transfers from LYON to T2s:
** Simultaneous transfers to the 7 T2 sites for more than 24 hours; it reached more than 25MB/s
**[[Image:StackdayLYON-27-7.png]]

== Post-mortem DDM meeting ==
* [http://indico.cern.ch/conferenceDisplay.py?confId=4959 Presentation at CERN (M. Branco) showing the results of the SC4 tests.] (1 August 2006)

Atlas:SC4

2006-09-25T12:57:16Z

Grahal: /* Post-mortem DDM meeting */

== ''Bienvenue sur la page Atlas SC4 LCG-France Welcome to the LCG-France Atlas SC4 page'' ==
[https://uimon.cern.ch/twiki/bin/view/Atlas/ATLASServiceChallenges Twiki page : SC4 ATLAS]

[http://lcg2.in2p3.fr/wiki/images/Sc4-juin06.txt Compte rendu de la réunion SC4 ATLAS au CERN du 9 Juin (S.Jézéquel, G. Rahal) (written in french) ]

* T0 Role(CERN)
** Produce dummy files with 1 to 2 GB size(RAW, ESD et AOD) (see [https://uimon.cern.ch/twiki/bin/view/Atlas/AtlasTierZero T0 Twiki])
** Initiate T0->T1 transfers
** FTS server sents files to Lyon choosing between 'TAPE' (RAW 43,2 Mo/s) or 'DISK' (ESD,AOD 23+20 Mo/s) areas
* T1 Role (CCIN2P3)
** Get files from T0 (dedicated dcache area: L. Schwarz)
** Provides LFC (lfc-atlas.in2p3.fr) and FTS service (cclcgftsli01.in2p3.fr) (D. Bouvet)
** Send all AODs to each T2 (20 Mo/s) using Lyon FTS server
** Regurlarly cleanup files
* T2 Role (BEIJING, LAL, LAPP, LPC, LPNHE, SACLAY, TOKYO)
** Get files from T1 (Lyon). Files on the T2 are written in /home/atlas/sc4tier0/...
** Clean-up the files (?)
* Other roles
** ATLAS (S. Jézéquel, G. Rahal) : Initiate T1->T2 transfers

== Information from DDM monitoring ==
* [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/ Main DDM monitoring page]

* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stack4h.png http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stack4ht2.png

----

* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackday.png
* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackdayLYON.png
* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackdayt2.png

----

* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackweek.png
* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackweekLYON.png
* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackweekt2.png

--

* Transfer rates for LYON and associated T2s (validated files by DDM):
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplots.php?site=LYON LYON]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=BEIJING BEIJING]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=LAL LAL]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=LAPP LAPP]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=LPC LPC]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=LPNHE LPNHE]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=SACLAY SACLAY]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=TOKYO TOKYO]

* [http://atldq02.cern.ch:8000/dq2/site_monitor/sites Detailed information on each site ]

* [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/sitestates.php?site=LYON File transfer state in LYON ]

== Information from FTS monitoring ==

*[http://gridview.cern.ch/GRIDVIEW/graphs.php?GraphName=atlas&ThruputDataOption=&SrcSite=&DestSite=&DurationOption=&StartDay=&StartMonth=&StartYear=&EndDay=&EndMonth=&EndYear=&HostType=&GraphFor=VO Atlas FTS transfer rate]

* [http://gridview.cern.ch/GRIDVIEW/graphs.php?GraphName=IN2PCC&ThruputDataOption=&SrcSite=&DestSite=&DurationOption=&StartDay=&StartMonth=&StartYear=&EndDay=&EndMonth=&EndYear=&HostType=&GraphFor= CERN->Lyon FTS transfer rate]

*T1->T2 :
** 15 concurrent files and 10 streams for LYON-TOKYO
** 5 concurrent files and 5 streams for LYON-BEIJING (SE not enough powerful for 15/15 )
** 10 concurrent files and 10 streams for LYON-French T2s (LAL, LPNHE, LPC, SACLAY) except for LAPP (5 concurrent files and 1 stream)

== Information from dCache monitoring (provided by Lyon) ==

*[http://cctools.in2p3.fr/dcache/transfers/atlas-sc4.html Monitoring of dcache for SC4 areas]
* LYONDISK : 25 gridftp concurrent access maximum
* LYONTAPE : 10 gridft concurrent access maximum

== VOBOX Configuration ==

* 4 processors 3 GHz
* 4 GB of memory ( 2 GB dedicated to SWAP)
* The monitoring of the Vobox daily, weekly and monthly can be found [http://atlas-france.in2p3.fr/Activites/Informatique/OutilsCC/VO-cclcgatlas Here]

== Disk space availability ==

* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=BEIJING-LCG2&visibility=SE BEIJING]
* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=CPPM-LCG2&visibility=SE CPPM]
* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=GRIF&visibility=SE GRIF]
* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=IN2P3-LPC&visibility=SE LPC]
* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=IN2P3-LAPP&visibility=SE LAPP]
* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=TOKYO-LCG2&visibility=SE TOKYO]
* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=IN2P3-CC&visibility=SE LYON]

== Daily news ==

* [https://uimon.cern.ch/twiki/bin/view/Atlas/DDMSc4#Daily_log SC4 Data Managment Daily log]

* 20 June 2006: Mail from Miguel Branco (DDM responsible)

Today we started deploying DQ2 on the remaining T1 sites (not all
sites still available). 
Attached is the result of a (nice) ramp up, easily beating SC3's
record (on the 1st day of export of SC4) peaking at ~ 270 MB/s. Each
'step' in the graph is an additional T1 being added to the export. 
Dataset subscriptions are now slowing down and will resume tomorrow.
Our DQ2 monitoring has been turned off and we expect to have it back
tomorrow! Still a long way to go until we have a reasonable
understanding of the limiting factors..


[[Image:Atlas day-jpeg.jpg]]

* SC4 transfers from LYON to T2s:
** Simultaneous transfers to the 7 T2 sites for more than 24 hours; it reached more than 25MB/s
**[[Image:StackdayLYON-27-7.png]]

== Post-mortem DDM meeting ==
* [http://indico.cern.ch/conferenceDisplay.py?confId=4959 Presentation at CERN (M. Branco) showing the results of the SC4 tests.] (1 August 2006)

Atlas:SC4

2006-09-25T10:28:38Z

Grahal: /* ''Bienvenue sur la page Atlas SC4 LCG-France Welcome to the LCG-France Atlas SC4 page'' */

== ''Bienvenue sur la page Atlas SC4 LCG-France Welcome to the LCG-France Atlas SC4 page'' ==
[https://uimon.cern.ch/twiki/bin/view/Atlas/ATLASServiceChallenges Twiki page : SC4 ATLAS]

[http://lcg2.in2p3.fr/wiki/images/Sc4-juin06.txt Compte rendu de la réunion SC4 ATLAS au CERN du 9 Juin (S.Jézéquel, G. Rahal) (written in french) ]

* T0 Role(CERN)
** Produce dummy files with 1 to 2 GB size(RAW, ESD et AOD) (see [https://uimon.cern.ch/twiki/bin/view/Atlas/AtlasTierZero T0 Twiki])
** Initiate T0->T1 transfers
** FTS server sents files to Lyon choosing between 'TAPE' (RAW 43,2 Mo/s) or 'DISK' (ESD,AOD 23+20 Mo/s) areas
* T1 Role (CCIN2P3)
** Get files from T0 (dedicated dcache area: L. Schwarz)
** Provides LFC (lfc-atlas.in2p3.fr) and FTS service (cclcgftsli01.in2p3.fr) (D. Bouvet)
** Send all AODs to each T2 (20 Mo/s) using Lyon FTS server
** Regurlarly cleanup files
* T2 Role (BEIJING, LAL, LAPP, LPC, LPNHE, SACLAY, TOKYO)
** Get files from T1 (Lyon). Files on the T2 are written in /home/atlas/sc4tier0/...
** Clean-up the files (?)
* Other roles
** ATLAS (S. Jézéquel, G. Rahal) : Initiate T1->T2 transfers

== Information from DDM monitoring ==
* [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/ Main DDM monitoring page]

* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stack4h.png http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stack4ht2.png

----

* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackday.png
* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackdayLYON.png
* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackdayt2.png

----

* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackweek.png
* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackweekLYON.png
* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackweekt2.png

--

* Transfer rates for LYON and associated T2s (validated files by DDM):
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplots.php?site=LYON LYON]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=BEIJING BEIJING]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=LAL LAL]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=LAPP LAPP]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=LPC LPC]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=LPNHE LPNHE]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=SACLAY SACLAY]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=TOKYO TOKYO]

* [http://atldq02.cern.ch:8000/dq2/site_monitor/sites Detailed information on each site ]

* [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/sitestates.php?site=LYON File transfer state in LYON ]

== Information from FTS monitoring ==

*[http://gridview.cern.ch/GRIDVIEW/graphs.php?GraphName=atlas&ThruputDataOption=&SrcSite=&DestSite=&DurationOption=&StartDay=&StartMonth=&StartYear=&EndDay=&EndMonth=&EndYear=&HostType=&GraphFor=VO Atlas FTS transfer rate]

* [http://gridview.cern.ch/GRIDVIEW/graphs.php?GraphName=IN2PCC&ThruputDataOption=&SrcSite=&DestSite=&DurationOption=&StartDay=&StartMonth=&StartYear=&EndDay=&EndMonth=&EndYear=&HostType=&GraphFor= CERN->Lyon FTS transfer rate]

*T1->T2 :
** 15 concurrent files and 10 streams for LYON-TOKYO
** 5 concurrent files and 5 streams for LYON-BEIJING (SE not enough powerful for 15/15 )
** 10 concurrent files and 10 streams for LYON-French T2s (LAL, LPNHE, LPC, SACLAY) except for LAPP (5 concurrent files and 1 stream)

== Information from dCache monitoring (provided by Lyon) ==

*[http://cctools.in2p3.fr/dcache/transfers/atlas-sc4.html Monitoring of dcache for SC4 areas]
* LYONDISK : 25 gridftp concurrent access maximum
* LYONTAPE : 10 gridft concurrent access maximum

== VOBOX Configuration ==

* 4 processors 3 GHz
* 4 GB of memory ( 2 GB dedicated to SWAP)
* The monitoring of the Vobox daily, weekly and monthly can be found [http://atlas-france.in2p3.fr/Activites/Informatique/OutilsCC/VO-cclcgatlas Here]

== Disk space availability ==

* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=BEIJING-LCG2&visibility=SE BEIJING]
* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=CPPM-LCG2&visibility=SE CPPM]
* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=GRIF&visibility=SE GRIF]
* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=IN2P3-LPC&visibility=SE LPC]
* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=IN2P3-LAPP&visibility=SE LAPP]
* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=TOKYO-LCG2&visibility=SE TOKYO]
* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=IN2P3-CC&visibility=SE LYON]

== Daily news ==

* [https://uimon.cern.ch/twiki/bin/view/Atlas/DDMSc4#Daily_log SC4 Data Managment Daily log]

* 20 June 2006: Mail from Miguel Branco (DDM responsible)

Today we started deploying DQ2 on the remaining T1 sites (not all
sites still available). 
Attached is the result of a (nice) ramp up, easily beating SC3's
record (on the 1st day of export of SC4) peaking at ~ 270 MB/s. Each
'step' in the graph is an additional T1 being added to the export. 
Dataset subscriptions are now slowing down and will resume tomorrow.
Our DQ2 monitoring has been turned off and we expect to have it back
tomorrow! Still a long way to go until we have a reasonable
understanding of the limiting factors..


[[Image:Atlas day-jpeg.jpg]]

* SC4 transfers from LYON to T2s:
** Simultaneous transfers to the 7 T2 sites for more than 24 hours; it reached more than 25MB/s
**[[Image:StackdayLYON-27-7.png]]

== Post-mortem DDM meeting ==
* [http://indico.cern.ch/conferenceDisplay.py?confId=4959 Presentation at CERN] (1 August 2006)

Atlas:SC4

2006-09-25T10:25:33Z

Grahal: /* Daily news */

== ''Bienvenue sur la page Atlas SC4 LCG-France Welcome to the LCG-France Atlas SC4 page'' ==
[https://uimon.cern.ch/twiki/bin/view/Atlas/ATLASServiceChallenges Twiki page : SC4 ATLAS]

[http://lcg2.in2p3.fr/wiki/images/Sc4-juin06.txt Compte rendu de la réunion SC4 ATLAS au CERN du 9 Juin (S.Jézéquel, G. Rahal) (written in french) ]

* T0 Role(CERN)
** Produce dummy files with 1 to 2 GB size(RAW, ESD et AOD) (see [https://uimon.cern.ch/twiki/bin/view/Atlas/AtlasTierZero T0 Twiki])
** Initiate T0->T1 transfers
** FTS server sents files to Lyon choosing between 'TAPE' (RAW 43,2 Mo/s) or 'DISK' (ESD,AOD 23+20 Mo/s) areas
* T1 Role (CCIN2P3)
** Get files from T0 (dedicated dcache area: L. Schwarz)
** Provides LFC (lfc-atlas.in2p3.fr) and FTS service (cclcgftsli01.in2p3.fr) (D. Bouvet)
** Send all AODs to each T2 (20 Mo/s) using Lyon FTS server
** Regurlarly cleanup files
* T2 Role (BEIJING, LAL, LAPP, LPC, LPNHE, SACLAY, TOKYO)
** Get files from T1 (Lyon). Files on the T2 are written in /home/atlas/sc4tier0/...
** Clean-up the files (?)
* Other roles
** ATLAS (S. Jézéquel) : Initiate T1->T2 transfers

== Information from DDM monitoring ==
* [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/ Main DDM monitoring page]

* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stack4h.png http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stack4ht2.png

----

* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackday.png
* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackdayLYON.png
* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackdayt2.png

----

* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackweek.png
* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackweekLYON.png
* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackweekt2.png

--

* Transfer rates for LYON and associated T2s (validated files by DDM):
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplots.php?site=LYON LYON]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=BEIJING BEIJING]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=LAL LAL]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=LAPP LAPP]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=LPC LPC]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=LPNHE LPNHE]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=SACLAY SACLAY]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=TOKYO TOKYO]

* [http://atldq02.cern.ch:8000/dq2/site_monitor/sites Detailed information on each site ]

* [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/sitestates.php?site=LYON File transfer state in LYON ]

== Information from FTS monitoring ==

*[http://gridview.cern.ch/GRIDVIEW/graphs.php?GraphName=atlas&ThruputDataOption=&SrcSite=&DestSite=&DurationOption=&StartDay=&StartMonth=&StartYear=&EndDay=&EndMonth=&EndYear=&HostType=&GraphFor=VO Atlas FTS transfer rate]

* [http://gridview.cern.ch/GRIDVIEW/graphs.php?GraphName=IN2PCC&ThruputDataOption=&SrcSite=&DestSite=&DurationOption=&StartDay=&StartMonth=&StartYear=&EndDay=&EndMonth=&EndYear=&HostType=&GraphFor= CERN->Lyon FTS transfer rate]

*T1->T2 :
** 15 concurrent files and 10 streams for LYON-TOKYO
** 5 concurrent files and 5 streams for LYON-BEIJING (SE not enough powerful for 15/15 )
** 10 concurrent files and 10 streams for LYON-French T2s (LAL, LPNHE, LPC, SACLAY) except for LAPP (5 concurrent files and 1 stream)

== Information from dCache monitoring (provided by Lyon) ==

*[http://cctools.in2p3.fr/dcache/transfers/atlas-sc4.html Monitoring of dcache for SC4 areas]
* LYONDISK : 25 gridftp concurrent access maximum
* LYONTAPE : 10 gridft concurrent access maximum

== VOBOX Configuration ==

* 4 processors 3 GHz
* 4 GB of memory ( 2 GB dedicated to SWAP)
* The monitoring of the Vobox daily, weekly and monthly can be found [http://atlas-france.in2p3.fr/Activites/Informatique/OutilsCC/VO-cclcgatlas Here]

== Disk space availability ==

* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=BEIJING-LCG2&visibility=SE BEIJING]
* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=CPPM-LCG2&visibility=SE CPPM]
* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=GRIF&visibility=SE GRIF]
* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=IN2P3-LPC&visibility=SE LPC]
* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=IN2P3-LAPP&visibility=SE LAPP]
* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=TOKYO-LCG2&visibility=SE TOKYO]
* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=IN2P3-CC&visibility=SE LYON]

== Daily news ==

* [https://uimon.cern.ch/twiki/bin/view/Atlas/DDMSc4#Daily_log SC4 Data Managment Daily log]

* 20 June 2006: Mail from Miguel Branco (DDM responsible)

Today we started deploying DQ2 on the remaining T1 sites (not all
sites still available). 
Attached is the result of a (nice) ramp up, easily beating SC3's
record (on the 1st day of export of SC4) peaking at ~ 270 MB/s. Each
'step' in the graph is an additional T1 being added to the export. 
Dataset subscriptions are now slowing down and will resume tomorrow.
Our DQ2 monitoring has been turned off and we expect to have it back
tomorrow! Still a long way to go until we have a reasonable
understanding of the limiting factors..


[[Image:Atlas day-jpeg.jpg]]

* SC4 transfers from LYON to T2s:
** Simultaneous transfers to the 7 T2 sites for more than 24 hours; it reached more than 25MB/s
**[[Image:StackdayLYON-27-7.png]]

== Post-mortem DDM meeting ==
* [http://indico.cern.ch/conferenceDisplay.py?confId=4959 Presentation at CERN] (1 August 2006)

Atlas:SC4

2006-09-15T13:48:20Z

Grahal: /* Information from DDM monitoring */

== ''Bienvenue sur la page Atlas SC4 LCG-France Welcome to the LCG-France Atlas SC4 page'' ==
[https://uimon.cern.ch/twiki/bin/view/Atlas/ATLASServiceChallenges Twiki page : SC4 ATLAS]

[http://lcg2.in2p3.fr/wiki/images/Sc4-juin06.txt Compte rendu de la réunion SC4 ATLAS au CERN du 9 Juin (S.Jézéquel, G. Rahal) (written in french) ]

* T0 Role(CERN)
** Produce dummy files with 1 to 2 GB size(RAW, ESD et AOD) (see [https://uimon.cern.ch/twiki/bin/view/Atlas/AtlasTierZero T0 Twiki])
** Initiate T0->T1 transfers
** FTS server sents files to Lyon choosing between 'TAPE' (RAW 43,2 Mo/s) or 'DISK' (ESD,AOD 23+20 Mo/s) areas
* T1 Role (CCIN2P3)
** Get files from T0 (dedicated dcache area: L. Schwarz)
** Provides LFC (lfc-atlas.in2p3.fr) and FTS service (cclcgftsli01.in2p3.fr) (D. Bouvet)
** Send all AODs to each T2 (20 Mo/s) using Lyon FTS server
** Regurlarly cleanup files
* T2 Role (BEIJING, LAL, LAPP, LPC, LPNHE, SACLAY, TOKYO)
** Get files from T1 (Lyon). Files on the T2 are written in /home/atlas/sc4tier0/...
** Clean-up the files (?)
* Other roles
** ATLAS (S. Jézéquel) : Initiate T1->T2 transfers

== Information from DDM monitoring ==
* [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/ Main DDM monitoring page]

* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stack4h.png http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stack4ht2.png

----

* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackday.png
* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackdayLYON.png
* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackdayt2.png

----

* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackweek.png
* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackweekLYON.png
* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackweekt2.png

--

* Transfer rates for LYON and associated T2s (validated files by DDM):
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplots.php?site=LYON LYON]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=BEIJING BEIJING]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=LAL LAL]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=LAPP LAPP]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=LPC LPC]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=LPNHE LPNHE]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=SACLAY SACLAY]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=TOKYO TOKYO]

* [http://atldq02.cern.ch:8000/dq2/site_monitor/sites Detailed information on each site ]

* [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/sitestates.php?site=LYON File transfer state in LYON ]

== Information from FTS monitoring ==

*[http://gridview.cern.ch/GRIDVIEW/graphs.php?GraphName=atlas&ThruputDataOption=&SrcSite=&DestSite=&DurationOption=&StartDay=&StartMonth=&StartYear=&EndDay=&EndMonth=&EndYear=&HostType=&GraphFor=VO Atlas FTS transfer rate]

* [http://gridview.cern.ch/GRIDVIEW/graphs.php?GraphName=IN2PCC&ThruputDataOption=&SrcSite=&DestSite=&DurationOption=&StartDay=&StartMonth=&StartYear=&EndDay=&EndMonth=&EndYear=&HostType=&GraphFor= CERN->Lyon FTS transfer rate]

*T1->T2 :
** 15 concurrent files and 10 streams for LYON-TOKYO
** 5 concurrent files and 5 streams for LYON-BEIJING (SE not enough powerful for 15/15 )
** 10 concurrent files and 10 streams for LYON-French T2s (LAL, LPNHE, LPC, SACLAY) except for LAPP (5 concurrent files and 1 stream)

== Information from dCache monitoring (provided by Lyon) ==

*[http://cctools.in2p3.fr/dcache/transfers/atlas-sc4.html Monitoring of dcache for SC4 areas]
* LYONDISK : 25 gridftp concurrent access maximum
* LYONTAPE : 10 gridft concurrent access maximum

== VOBOX Configuration ==

* 4 processors 3 GHz
* 4 GB of memory ( 2 GB dedicated to SWAP)
* The monitoring of the Vobox daily, weekly and monthly can be found [http://atlas-france.in2p3.fr/Activites/Informatique/OutilsCC/VO-cclcgatlas Here]

== Disk space availability ==

* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=BEIJING-LCG2&visibility=SE BEIJING]
* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=CPPM-LCG2&visibility=SE CPPM]
* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=GRIF&visibility=SE GRIF]
* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=IN2P3-LPC&visibility=SE LPC]
* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=IN2P3-LAPP&visibility=SE LAPP]
* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=TOKYO-LCG2&visibility=SE TOKYO]
* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=IN2P3-CC&visibility=SE LYON]

== Daily news ==

* [https://uimon.cern.ch/twiki/bin/view/Atlas/DDMSc4#Daily_log SC4 Data Managment Daily log]

* 20 June 2006: Mail from Miguel Branco (DDM responsible)

Today we started deploying DQ2 on the remaining T1 sites (not all
sites still available). 
Attached is the result of a (nice) ramp up, easily beating SC3's
record (on the 1st day of export of SC4) peaking at ~ 270 MB/s. Each
'step' in the graph is an additional T1 being added to the export. 
Dataset subscriptions are now slowing down and will resume tomorrow.
Our DQ2 monitoring has been turned off and we expect to have it back
tomorrow! Still a long way to go until we have a reasonable
understanding of the limiting factors..


[[Image:Atlas day-jpeg.jpg]]

* 22 June: General power cut at CERN at 2:pm.

* 24 June : Dataset T0.D.run000949.ESD transfered from Lyon to LAL and TOKYO. Tranfering the same dataset to LAPP and LPC failed because these sites have same domain name (*.in2p3.fr) as Lyon.

* 25 June : Almost no transfer from CERN to T1s during the week-end.

* 26 June : SC4 transfers restarted with working DDM monitoring. Successfull transfers to LAL, SACLAY and TOKYO. Technical problem (domain name) for LAPP, LPNHE and LPC : under investigation. Contact BEIJING.
.
* 28 June :
** Problem of domain name solved for LAPP, LPC and LPNHE. First transfers to these sites have been done.
** Increase the number of LFC connection to 40 (advice from CERN-IT and DDM).
 AODs were transfered to all T2s associated to Lyon except BEIJING (looks like a FTS problem) 

**Transfer all AODs to LAL. Problems to transfer AODs to LAPP (one dcache server crashed)

* 29 June :
** Transfer of AODs to TOKYO

* 1 July
** Test transfers from LYONDISK to T2s
[[Image:T1-T2-0107-3.jpg]]

* 5 July :
** First DDM transfer to BEIJING

* 6 july
** [[Image:StackdayLYON.png]]

* 17 july
** Simultaneous transfers to T2 sites including BEIJING
**[[Image:StackdayLYON-17-7.png]]

* 27 july
** Simultaneous transfers to the 7 T2 sites for more than 24 hours; it reached more than 25MB/s
**[[Image:StackdayLYON-27-7.png]]

Atlas:SC4

2006-09-15T13:47:28Z

Grahal:

== ''Bienvenue sur la page Atlas SC4 LCG-France Welcome to the LCG-France Atlas SC4 page'' ==
[https://uimon.cern.ch/twiki/bin/view/Atlas/ATLASServiceChallenges Twiki page : SC4 ATLAS]

[http://lcg2.in2p3.fr/wiki/images/Sc4-juin06.txt Compte rendu de la réunion SC4 ATLAS au CERN du 9 Juin (S.Jézéquel, G. Rahal) (written in french) ]

* T0 Role(CERN)
** Produce dummy files with 1 to 2 GB size(RAW, ESD et AOD) (see [https://uimon.cern.ch/twiki/bin/view/Atlas/AtlasTierZero T0 Twiki])
** Initiate T0->T1 transfers
** FTS server sents files to Lyon choosing between 'TAPE' (RAW 43,2 Mo/s) or 'DISK' (ESD,AOD 23+20 Mo/s) areas
* T1 Role (CCIN2P3)
** Get files from T0 (dedicated dcache area: L. Schwarz)
** Provides LFC (lfc-atlas.in2p3.fr) and FTS service (cclcgftsli01.in2p3.fr) (D. Bouvet)
** Send all AODs to each T2 (20 Mo/s) using Lyon FTS server
** Regurlarly cleanup files
* T2 Role (BEIJING, LAL, LAPP, LPC, LPNHE, SACLAY, TOKYO)
** Get files from T1 (Lyon). Files on the T2 are written in /home/atlas/sc4tier0/...
** Clean-up the files (?)
* Other roles
** ATLAS (S. Jézéquel) : Initiate T1->T2 transfers

== Information from DDM monitoring ==
* [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/ Main DDM monitoring page]

* [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stack4h.png] [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stack4ht2.png]

----

* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackday.png
* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackdayLYON.png
* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackdayt2.png

----

* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackweek.png
* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackweekLYON.png
* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackweekt2.png

--

* Transfer rates for LYON and associated T2s (validated files by DDM):
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplots.php?site=LYON LYON]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=BEIJING BEIJING]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=LAL LAL]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=LAPP LAPP]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=LPC LPC]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=LPNHE LPNHE]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=SACLAY SACLAY]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=TOKYO TOKYO]

* [http://atldq02.cern.ch:8000/dq2/site_monitor/sites Detailed information on each site ]

* [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/sitestates.php?site=LYON File transfer state in LYON ]

== Information from FTS monitoring ==

*[http://gridview.cern.ch/GRIDVIEW/graphs.php?GraphName=atlas&ThruputDataOption=&SrcSite=&DestSite=&DurationOption=&StartDay=&StartMonth=&StartYear=&EndDay=&EndMonth=&EndYear=&HostType=&GraphFor=VO Atlas FTS transfer rate]

* [http://gridview.cern.ch/GRIDVIEW/graphs.php?GraphName=IN2PCC&ThruputDataOption=&SrcSite=&DestSite=&DurationOption=&StartDay=&StartMonth=&StartYear=&EndDay=&EndMonth=&EndYear=&HostType=&GraphFor= CERN->Lyon FTS transfer rate]

*T1->T2 :
** 15 concurrent files and 10 streams for LYON-TOKYO
** 5 concurrent files and 5 streams for LYON-BEIJING (SE not enough powerful for 15/15 )
** 10 concurrent files and 10 streams for LYON-French T2s (LAL, LPNHE, LPC, SACLAY) except for LAPP (5 concurrent files and 1 stream)

== Information from dCache monitoring (provided by Lyon) ==

*[http://cctools.in2p3.fr/dcache/transfers/atlas-sc4.html Monitoring of dcache for SC4 areas]
* LYONDISK : 25 gridftp concurrent access maximum
* LYONTAPE : 10 gridft concurrent access maximum

== VOBOX Configuration ==

* 4 processors 3 GHz
* 4 GB of memory ( 2 GB dedicated to SWAP)
* The monitoring of the Vobox daily, weekly and monthly can be found [http://atlas-france.in2p3.fr/Activites/Informatique/OutilsCC/VO-cclcgatlas Here]

== Disk space availability ==

* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=BEIJING-LCG2&visibility=SE BEIJING]
* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=CPPM-LCG2&visibility=SE CPPM]
* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=GRIF&visibility=SE GRIF]
* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=IN2P3-LPC&visibility=SE LPC]
* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=IN2P3-LAPP&visibility=SE LAPP]
* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=TOKYO-LCG2&visibility=SE TOKYO]
* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=IN2P3-CC&visibility=SE LYON]

== Daily news ==

* [https://uimon.cern.ch/twiki/bin/view/Atlas/DDMSc4#Daily_log SC4 Data Managment Daily log]

* 20 June 2006: Mail from Miguel Branco (DDM responsible)

Today we started deploying DQ2 on the remaining T1 sites (not all
sites still available). 
Attached is the result of a (nice) ramp up, easily beating SC3's
record (on the 1st day of export of SC4) peaking at ~ 270 MB/s. Each
'step' in the graph is an additional T1 being added to the export. 
Dataset subscriptions are now slowing down and will resume tomorrow.
Our DQ2 monitoring has been turned off and we expect to have it back
tomorrow! Still a long way to go until we have a reasonable
understanding of the limiting factors..


[[Image:Atlas day-jpeg.jpg]]

* 22 June: General power cut at CERN at 2:pm.

* 24 June : Dataset T0.D.run000949.ESD transfered from Lyon to LAL and TOKYO. Tranfering the same dataset to LAPP and LPC failed because these sites have same domain name (*.in2p3.fr) as Lyon.

* 25 June : Almost no transfer from CERN to T1s during the week-end.

* 26 June : SC4 transfers restarted with working DDM monitoring. Successfull transfers to LAL, SACLAY and TOKYO. Technical problem (domain name) for LAPP, LPNHE and LPC : under investigation. Contact BEIJING.
.
* 28 June :
** Problem of domain name solved for LAPP, LPC and LPNHE. First transfers to these sites have been done.
** Increase the number of LFC connection to 40 (advice from CERN-IT and DDM).
 AODs were transfered to all T2s associated to Lyon except BEIJING (looks like a FTS problem) 

**Transfer all AODs to LAL. Problems to transfer AODs to LAPP (one dcache server crashed)

* 29 June :
** Transfer of AODs to TOKYO

* 1 July
** Test transfers from LYONDISK to T2s
[[Image:T1-T2-0107-3.jpg]]

* 5 July :
** First DDM transfer to BEIJING

* 6 july
** [[Image:StackdayLYON.png]]

* 17 july
** Simultaneous transfers to T2 sites including BEIJING
**[[Image:StackdayLYON-17-7.png]]

* 27 july
** Simultaneous transfers to the 7 T2 sites for more than 24 hours; it reached more than 25MB/s
**[[Image:StackdayLYON-27-7.png]]

Atlas:SC4

2006-08-04T08:23:35Z

Grahal: /* VOBOX Configuration */

== ''Bienvenue sur la page Atlas SC4 LCG-France Welcome to the LCG-France Atlas SC4 page'' ==
[https://uimon.cern.ch/twiki/bin/view/Atlas/ATLASServiceChallenges Twiki page : SC4 ATLAS]

[http://lcg2.in2p3.fr/wiki/images/Sc4-juin06.txt Compte rendu de la réunion SC4 ATLAS au CERN du 9 Juin (S.Jézéquel, G. Rahal) (written in french) ]

* T0 Role(CERN)
** Produce dummy files with 1 to 2 GB size(RAW, ESD et AOD) (see [https://uimon.cern.ch/twiki/bin/view/Atlas/AtlasTierZero T0 Twiki])
** Initiate T0->T1 transfers
** FTS server sents files to Lyon choosing between 'TAPE' (RAW 43,2 Mo/s) or 'DISK' (ESD,AOD 23+20 Mo/s) areas
* T1 Role (CCIN2P3)
** Get files from T0 (dedicated dcache area: L. Schwarz)
** Provides LFC (lfc-atlas.in2p3.fr) and FTS service (cclcgftsli01.in2p3.fr) (D. Bouvet)
** Send all AODs to each T2 (20 Mo/s) using Lyon FTS server
** Regurlarly cleanup files
* T2 Role (BEIJING, LAL, LAPP, LPC, LPNHE, SACLAY, TOKYO)
** Get files from T1 (Lyon). Files on the T2 are written in /home/atlas/sc4tier0/...
** Clean-up the files (?)
* Other roles
** ATLAS (S. Jézéquel) : Initiate T1->T2 transfers

== Information from DDM monitoring ==
* [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/ Main DDM monitoring page]

* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stack4h.png
* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stack4ht2.png

----

* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackday.png
* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackdayLYON.png
* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackdayt2.png

----

* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackweek.png
* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackweekLYON.png
* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackweekt2.png

--

* Transfer rates for LYON and associated T2s (validated files by DDM):
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplots.php?site=LYON LYON]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=BEIJING BEIJING]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=LAL LAL]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=LAPP LAPP]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=LPC LPC]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=LPNHE LPNHE]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=SACLAY SACLAY]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=TOKYO TOKYO]

* [http://atldq02.cern.ch:8000/dq2/site_monitor/sites Detailed information on each site ]

* [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/sitestates.php?site=LYON File transfer state in LYON ]

== Information from FTS monitoring ==

*[http://gridview.cern.ch/GRIDVIEW/graphs.php?GraphName=atlas&ThruputDataOption=&SrcSite=&DestSite=&DurationOption=&StartDay=&StartMonth=&StartYear=&EndDay=&EndMonth=&EndYear=&HostType=&GraphFor=VO Atlas FTS transfer rate]

* [http://gridview.cern.ch/GRIDVIEW/graphs.php?GraphName=IN2PCC&ThruputDataOption=&SrcSite=&DestSite=&DurationOption=&StartDay=&StartMonth=&StartYear=&EndDay=&EndMonth=&EndYear=&HostType=&GraphFor= CERN->Lyon FTS transfer rate]

*T1->T2 :
** 15 concurrent files and 10 streams for LYON-TOKYO
** 5 concurrent files and 5 streams for LYON-BEIJING (SE not enough powerful for 15/15 )
** 10 concurrent files and 10 streams for LYON-French T2s (LAL, LPNHE, LPC, SACLAY) except for LAPP (5 concurrent files and 1 stream)

== Information from dCache monitoring (provided by Lyon) ==

*[http://cctools.in2p3.fr/dcache/transfers/atlas-sc4.html Monitoring of dcache for SC4 areas]
* LYONDISK : 25 gridftp concurrent access maximum
* LYONTAPE : 10 gridft concurrent access maximum

== VOBOX Configuration ==

* 4 processors 3 GHz
* 4 GB of memory ( 2 GB dedicated to SWAP)
* The monitoring of the Vobox daily, weekly and monthly can be found [http://atlas-france.in2p3.fr/Activites/Informatique/OutilsCC/VO-cclcgatlas Here]

== Disk space availability ==

* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=GRIF&visibility=SE GRIF]
* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=IN2P3-LPC&visibility=SE LPC]
* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=IN2P3-LAPP&visibility=SE LAPP]
* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=TOKYO-LCG2&visibility=SE TOKYO]
* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=IN2P3-CC&visibility=SE LYON]

== Daily news ==

* [https://uimon.cern.ch/twiki/bin/view/Atlas/DDMSc4#Daily_log SC4 Data Managment Daily log]

* 20 June 2006: Mail from Miguel Branco (DDM responsible)

Today we started deploying DQ2 on the remaining T1 sites (not all
sites still available). 
Attached is the result of a (nice) ramp up, easily beating SC3's
record (on the 1st day of export of SC4) peaking at ~ 270 MB/s. Each
'step' in the graph is an additional T1 being added to the export. 
Dataset subscriptions are now slowing down and will resume tomorrow.
Our DQ2 monitoring has been turned off and we expect to have it back
tomorrow! Still a long way to go until we have a reasonable
understanding of the limiting factors..


[[Image:Atlas day-jpeg.jpg]]

* 22 June: General power cut at CERN at 2:pm.

* 24 June : Dataset T0.D.run000949.ESD transfered from Lyon to LAL and TOKYO. Tranfering the same dataset to LAPP and LPC failed because these sites have same domain name (*.in2p3.fr) as Lyon.

* 25 June : Almost no transfer from CERN to T1s during the week-end.

* 26 June : SC4 transfers restarted with working DDM monitoring. Successfull transfers to LAL, SACLAY and TOKYO. Technical problem (domain name) for LAPP, LPNHE and LPC : under investigation. Contact BEIJING.
.
* 28 June :
** Problem of domain name solved for LAPP, LPC and LPNHE. First transfers to these sites have been done.
** Increase the number of LFC connection to 40 (advice from CERN-IT and DDM).
 AODs were transfered to all T2s associated to Lyon except BEIJING (looks like a FTS problem) 

**Transfer all AODs to LAL. Problems to transfer AODs to LAPP (one dcache server crashed)

* 29 June :
** Transfer of AODs to TOKYO

* 1 July
** Test transfers from LYONDISK to T2s
[[Image:T1-T2-0107-3.jpg]]

* 5 July :
** First DDM transfer to BEIJING

* 6 july
** [[Image:StackdayLYON.png]]

* 17 july
** Simultaneous transfers to T2 sites including BEIJING
**[[Image:StackdayLYON-17-7.png]]

* 27 july
** Simultaneous transfers to the 7 T2 sites for more than 24 hours; it reached more than 25MB/s
**[[Image:StackdayLYON-27-7.png]]

Atlas:SC4

2006-08-04T08:22:55Z

Grahal: /* VOBOX Configuration */

== ''Bienvenue sur la page Atlas SC4 LCG-France Welcome to the LCG-France Atlas SC4 page'' ==
[https://uimon.cern.ch/twiki/bin/view/Atlas/ATLASServiceChallenges Twiki page : SC4 ATLAS]

[http://lcg2.in2p3.fr/wiki/images/Sc4-juin06.txt Compte rendu de la réunion SC4 ATLAS au CERN du 9 Juin (S.Jézéquel, G. Rahal) (written in french) ]

* T0 Role(CERN)
** Produce dummy files with 1 to 2 GB size(RAW, ESD et AOD) (see [https://uimon.cern.ch/twiki/bin/view/Atlas/AtlasTierZero T0 Twiki])
** Initiate T0->T1 transfers
** FTS server sents files to Lyon choosing between 'TAPE' (RAW 43,2 Mo/s) or 'DISK' (ESD,AOD 23+20 Mo/s) areas
* T1 Role (CCIN2P3)
** Get files from T0 (dedicated dcache area: L. Schwarz)
** Provides LFC (lfc-atlas.in2p3.fr) and FTS service (cclcgftsli01.in2p3.fr) (D. Bouvet)
** Send all AODs to each T2 (20 Mo/s) using Lyon FTS server
** Regurlarly cleanup files
* T2 Role (BEIJING, LAL, LAPP, LPC, LPNHE, SACLAY, TOKYO)
** Get files from T1 (Lyon). Files on the T2 are written in /home/atlas/sc4tier0/...
** Clean-up the files (?)
* Other roles
** ATLAS (S. Jézéquel) : Initiate T1->T2 transfers

== Information from DDM monitoring ==
* [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/ Main DDM monitoring page]

* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stack4h.png
* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stack4ht2.png

----

* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackday.png
* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackdayLYON.png
* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackdayt2.png

----

* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackweek.png
* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackweekLYON.png
* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackweekt2.png

--

* Transfer rates for LYON and associated T2s (validated files by DDM):
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplots.php?site=LYON LYON]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=BEIJING BEIJING]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=LAL LAL]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=LAPP LAPP]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=LPC LPC]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=LPNHE LPNHE]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=SACLAY SACLAY]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=TOKYO TOKYO]

* [http://atldq02.cern.ch:8000/dq2/site_monitor/sites Detailed information on each site ]

* [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/sitestates.php?site=LYON File transfer state in LYON ]

== Information from FTS monitoring ==

*[http://gridview.cern.ch/GRIDVIEW/graphs.php?GraphName=atlas&ThruputDataOption=&SrcSite=&DestSite=&DurationOption=&StartDay=&StartMonth=&StartYear=&EndDay=&EndMonth=&EndYear=&HostType=&GraphFor=VO Atlas FTS transfer rate]

* [http://gridview.cern.ch/GRIDVIEW/graphs.php?GraphName=IN2PCC&ThruputDataOption=&SrcSite=&DestSite=&DurationOption=&StartDay=&StartMonth=&StartYear=&EndDay=&EndMonth=&EndYear=&HostType=&GraphFor= CERN->Lyon FTS transfer rate]

*T1->T2 :
** 15 concurrent files and 10 streams for LYON-TOKYO
** 5 concurrent files and 5 streams for LYON-BEIJING (SE not enough powerful for 15/15 )
** 10 concurrent files and 10 streams for LYON-French T2s (LAL, LPNHE, LPC, SACLAY) except for LAPP (5 concurrent files and 1 stream)

== Information from dCache monitoring (provided by Lyon) ==

*[http://cctools.in2p3.fr/dcache/transfers/atlas-sc4.html Monitoring of dcache for SC4 areas]
* LYONDISK : 25 gridftp concurrent access maximum
* LYONTAPE : 10 gridft concurrent access maximum

== VOBOX Configuration ==

* 4 processors 3 GHz
* 4 GB of memory ( 2 GB dedicated to SWAP)
* The monitoring of the Vobox dayly, weekly and monthly can be found [http://atlas-france.in2p3.fr/Activites/Informatique/OutilsCC/VO-cclcgatlas Here]

== Disk space availability ==

* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=GRIF&visibility=SE GRIF]
* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=IN2P3-LPC&visibility=SE LPC]
* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=IN2P3-LAPP&visibility=SE LAPP]
* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=TOKYO-LCG2&visibility=SE TOKYO]
* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=IN2P3-CC&visibility=SE LYON]

== Daily news ==

* [https://uimon.cern.ch/twiki/bin/view/Atlas/DDMSc4#Daily_log SC4 Data Managment Daily log]

* 20 June 2006: Mail from Miguel Branco (DDM responsible)

Today we started deploying DQ2 on the remaining T1 sites (not all
sites still available). 
Attached is the result of a (nice) ramp up, easily beating SC3's
record (on the 1st day of export of SC4) peaking at ~ 270 MB/s. Each
'step' in the graph is an additional T1 being added to the export. 
Dataset subscriptions are now slowing down and will resume tomorrow.
Our DQ2 monitoring has been turned off and we expect to have it back
tomorrow! Still a long way to go until we have a reasonable
understanding of the limiting factors..


[[Image:Atlas day-jpeg.jpg]]

* 22 June: General power cut at CERN at 2:pm.

* 24 June : Dataset T0.D.run000949.ESD transfered from Lyon to LAL and TOKYO. Tranfering the same dataset to LAPP and LPC failed because these sites have same domain name (*.in2p3.fr) as Lyon.

* 25 June : Almost no transfer from CERN to T1s during the week-end.

* 26 June : SC4 transfers restarted with working DDM monitoring. Successfull transfers to LAL, SACLAY and TOKYO. Technical problem (domain name) for LAPP, LPNHE and LPC : under investigation. Contact BEIJING.
.
* 28 June :
** Problem of domain name solved for LAPP, LPC and LPNHE. First transfers to these sites have been done.
** Increase the number of LFC connection to 40 (advice from CERN-IT and DDM).
 AODs were transfered to all T2s associated to Lyon except BEIJING (looks like a FTS problem) 

**Transfer all AODs to LAL. Problems to transfer AODs to LAPP (one dcache server crashed)

* 29 June :
** Transfer of AODs to TOKYO

* 1 July
** Test transfers from LYONDISK to T2s
[[Image:T1-T2-0107-3.jpg]]

* 5 July :
** First DDM transfer to BEIJING

* 6 july
** [[Image:StackdayLYON.png]]

* 17 july
** Simultaneous transfers to T2 sites including BEIJING
**[[Image:StackdayLYON-17-7.png]]

* 27 july
** Simultaneous transfers to the 7 T2 sites for more than 24 hours; it reached more than 25MB/s
**[[Image:StackdayLYON-27-7.png]]

Atlas:SC4

2006-08-04T08:20:21Z

Grahal: /* VOBOX Configuration */

== ''Bienvenue sur la page Atlas SC4 LCG-France Welcome to the LCG-France Atlas SC4 page'' ==
[https://uimon.cern.ch/twiki/bin/view/Atlas/ATLASServiceChallenges Twiki page : SC4 ATLAS]

[http://lcg2.in2p3.fr/wiki/images/Sc4-juin06.txt Compte rendu de la réunion SC4 ATLAS au CERN du 9 Juin (S.Jézéquel, G. Rahal) (written in french) ]

* T0 Role(CERN)
** Produce dummy files with 1 to 2 GB size(RAW, ESD et AOD) (see [https://uimon.cern.ch/twiki/bin/view/Atlas/AtlasTierZero T0 Twiki])
** Initiate T0->T1 transfers
** FTS server sents files to Lyon choosing between 'TAPE' (RAW 43,2 Mo/s) or 'DISK' (ESD,AOD 23+20 Mo/s) areas
* T1 Role (CCIN2P3)
** Get files from T0 (dedicated dcache area: L. Schwarz)
** Provides LFC (lfc-atlas.in2p3.fr) and FTS service (cclcgftsli01.in2p3.fr) (D. Bouvet)
** Send all AODs to each T2 (20 Mo/s) using Lyon FTS server
** Regurlarly cleanup files
* T2 Role (BEIJING, LAL, LAPP, LPC, LPNHE, SACLAY, TOKYO)
** Get files from T1 (Lyon). Files on the T2 are written in /home/atlas/sc4tier0/...
** Clean-up the files (?)
* Other roles
** ATLAS (S. Jézéquel) : Initiate T1->T2 transfers

== Information from DDM monitoring ==
* [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/ Main DDM monitoring page]

* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stack4h.png
* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stack4ht2.png

----

* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackday.png
* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackdayLYON.png
* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackdayt2.png

----

* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackweek.png
* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackweekLYON.png
* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackweekt2.png

--

* Transfer rates for LYON and associated T2s (validated files by DDM):
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplots.php?site=LYON LYON]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=BEIJING BEIJING]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=LAL LAL]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=LAPP LAPP]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=LPC LPC]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=LPNHE LPNHE]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=SACLAY SACLAY]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=TOKYO TOKYO]

* [http://atldq02.cern.ch:8000/dq2/site_monitor/sites Detailed information on each site ]

* [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/sitestates.php?site=LYON File transfer state in LYON ]

== Information from FTS monitoring ==

*[http://gridview.cern.ch/GRIDVIEW/graphs.php?GraphName=atlas&ThruputDataOption=&SrcSite=&DestSite=&DurationOption=&StartDay=&StartMonth=&StartYear=&EndDay=&EndMonth=&EndYear=&HostType=&GraphFor=VO Atlas FTS transfer rate]

* [http://gridview.cern.ch/GRIDVIEW/graphs.php?GraphName=IN2PCC&ThruputDataOption=&SrcSite=&DestSite=&DurationOption=&StartDay=&StartMonth=&StartYear=&EndDay=&EndMonth=&EndYear=&HostType=&GraphFor= CERN->Lyon FTS transfer rate]

*T1->T2 :
** 15 concurrent files and 10 streams for LYON-TOKYO
** 5 concurrent files and 5 streams for LYON-BEIJING (SE not enough powerful for 15/15 )
** 10 concurrent files and 10 streams for LYON-French T2s (LAL, LPNHE, LPC, SACLAY) except for LAPP (5 concurrent files and 1 stream)

== Information from dCache monitoring (provided by Lyon) ==

*[http://cctools.in2p3.fr/dcache/transfers/atlas-sc4.html Monitoring of dcache for SC4 areas]
* LYONDISK : 25 gridftp concurrent access maximum
* LYONTAPE : 10 gridft concurrent access maximum

== VOBOX Configuration ==

* 4 processors 3 GHz
* 4 GB of memory ( 2 GB dedicated to SWAP)
* The monitoring of the Vobox dayly, weekly and monthly can be found here

== Disk space availability ==

* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=GRIF&visibility=SE GRIF]
* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=IN2P3-LPC&visibility=SE LPC]
* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=IN2P3-LAPP&visibility=SE LAPP]
* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=TOKYO-LCG2&visibility=SE TOKYO]
* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=IN2P3-CC&visibility=SE LYON]

== Daily news ==

* [https://uimon.cern.ch/twiki/bin/view/Atlas/DDMSc4#Daily_log SC4 Data Managment Daily log]

* 20 June 2006: Mail from Miguel Branco (DDM responsible)

Today we started deploying DQ2 on the remaining T1 sites (not all
sites still available). 
Attached is the result of a (nice) ramp up, easily beating SC3's
record (on the 1st day of export of SC4) peaking at ~ 270 MB/s. Each
'step' in the graph is an additional T1 being added to the export. 
Dataset subscriptions are now slowing down and will resume tomorrow.
Our DQ2 monitoring has been turned off and we expect to have it back
tomorrow! Still a long way to go until we have a reasonable
understanding of the limiting factors..


[[Image:Atlas day-jpeg.jpg]]

* 22 June: General power cut at CERN at 2:pm.

* 24 June : Dataset T0.D.run000949.ESD transfered from Lyon to LAL and TOKYO. Tranfering the same dataset to LAPP and LPC failed because these sites have same domain name (*.in2p3.fr) as Lyon.

* 25 June : Almost no transfer from CERN to T1s during the week-end.

* 26 June : SC4 transfers restarted with working DDM monitoring. Successfull transfers to LAL, SACLAY and TOKYO. Technical problem (domain name) for LAPP, LPNHE and LPC : under investigation. Contact BEIJING.
.
* 28 June :
** Problem of domain name solved for LAPP, LPC and LPNHE. First transfers to these sites have been done.
** Increase the number of LFC connection to 40 (advice from CERN-IT and DDM).
 AODs were transfered to all T2s associated to Lyon except BEIJING (looks like a FTS problem) 

**Transfer all AODs to LAL. Problems to transfer AODs to LAPP (one dcache server crashed)

* 29 June :
** Transfer of AODs to TOKYO

* 1 July
** Test transfers from LYONDISK to T2s
[[Image:T1-T2-0107-3.jpg]]

* 5 July :
** First DDM transfer to BEIJING

* 6 july
** [[Image:StackdayLYON.png]]

* 17 july
** Simultaneous transfers to T2 sites including BEIJING
**[[Image:StackdayLYON-17-7.png]]

* 27 july
** Simultaneous transfers to the 7 T2 sites for more than 24 hours; it reached more than 25MB/s
**[[Image:StackdayLYON-27-7.png]]

File:StackdayLYON-27-7.png

2006-07-27T09:24:22Z

Grahal:

Atlas:SC4

2006-07-27T09:23:54Z

Grahal: /* Daily news */

== ''Bienvenue sur la page Atlas SC4 LCG-France Welcome to the LCG-France Atlas SC4 page'' ==
[https://uimon.cern.ch/twiki/bin/view/Atlas/ATLASServiceChallenges Twiki page : SC4 ATLAS]

[http://lcg2.in2p3.fr/wiki/images/Sc4-juin06.txt Compte rendu de la réunion SC4 ATLAS au CERN du 9 Juin (S.Jézéquel, G. Rahal) (written in french) ]

* T0 Role(CERN)
** Produce dummy files with 1 to 2 GB size(RAW, ESD et AOD) (see [https://uimon.cern.ch/twiki/bin/view/Atlas/AtlasTierZero T0 Twiki])
** Initiate T0->T1 transfers
** FTS server sents files to Lyon choosing between 'TAPE' (RAW 43,2 Mo/s) or 'DISK' (ESD,AOD 23+20 Mo/s) areas
* T1 Role (CCIN2P3)
** Get files from T0 (dedicated dcache area: L. Schwarz)
** Provides LFC (lfc-atlas.in2p3.fr) and FTS service (cclcgftsli01.in2p3.fr) (D. Bouvet)
** Send all AODs to each T2 (20 Mo/s) using Lyon FTS server
** Regurlarly cleanup files
* T2 Role (BEIJING, LAL, LAPP, LPC, LPNHE, SACLAY, TOKYO)
** Get files from T1 (Lyon). Files on the T2 are written in /home/atlas/sc4tier0/...
** Clean-up the files (?)
* Other roles
** ATLAS (S. Jézéquel) : Initiate T1->T2 transfers

== Information from DDM monitoring ==
* [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/ Main DDM monitoring page]

* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stack4h.png
* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stack4ht2.png

----

* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackday.png
* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackdayLYON.png
* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackdayt2.png

----

* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackweek.png
* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackweekLYON.png
* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackweekt2.png

--

* Transfer rates for LYON and associated T2s (validated files by DDM):
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplots.php?site=LYON LYON]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=BEIJING BEIJING]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=LAL LAL]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=LAPP LAPP]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=LPC LPC]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=LPNHE LPNHE]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=SACLAY SACLAY]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=TOKYO TOKYO]

* [http://atldq02.cern.ch:8000/dq2/site_monitor/sites Detailed information on each site ]

* [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/sitestates.php?site=LYON File transfer state in LYON ]

== Information from FTS monitoring ==

*[http://gridview.cern.ch/GRIDVIEW/graphs.php?GraphName=atlas&ThruputDataOption=&SrcSite=&DestSite=&DurationOption=&StartDay=&StartMonth=&StartYear=&EndDay=&EndMonth=&EndYear=&HostType=&GraphFor=VO Atlas FTS transfer rate]

* [http://gridview.cern.ch/GRIDVIEW/graphs.php?GraphName=IN2PCC&ThruputDataOption=&SrcSite=&DestSite=&DurationOption=&StartDay=&StartMonth=&StartYear=&EndDay=&EndMonth=&EndYear=&HostType=&GraphFor= CERN->Lyon FTS transfer rate]

*T1->T2 :
** 15 concurrent files and 10 streams for LYON-TOKYO
** 5 concurrent files and 5 streams for LYON-BEIJING (SE not enough powerful for 15/15 )
** 10 concurrent files and 10 streams for LYON-French T2s (LAL, LPNHE, LPC, SACLAY) except for LAPP (5 concurrent files and 1 stream)

== Information from dCache monitoring (provided by Lyon) ==

*[http://cctools.in2p3.fr/dcache/transfers/atlas-sc4.html Monitoring of dcache for SC4 areas]
* LYONDISK : 25 gridftp concurrent access maximum
* LYONTAPE : 10 gridft concurrent access maximum

== VOBOX Configuration ==

* 4 processors 3 GHz
* 4 GB of memory ( 2 GB dedicated to SWAP)

== Disk space availability ==

* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=GRIF&visibility=SE GRIF]
* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=IN2P3-LPC&visibility=SE LPC]
* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=IN2P3-LAPP&visibility=SE LAPP]
* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=TOKYO-LCG2&visibility=SE TOKYO]
* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=IN2P3-CC&visibility=SE LYON]

== Daily news ==

* [https://uimon.cern.ch/twiki/bin/view/Atlas/DDMSc4#Daily_log SC4 Data Managment Daily log]

* 20 June 2006: Mail from Miguel Branco (DDM responsible)

Today we started deploying DQ2 on the remaining T1 sites (not all
sites still available). 
Attached is the result of a (nice) ramp up, easily beating SC3's
record (on the 1st day of export of SC4) peaking at ~ 270 MB/s. Each
'step' in the graph is an additional T1 being added to the export. 
Dataset subscriptions are now slowing down and will resume tomorrow.
Our DQ2 monitoring has been turned off and we expect to have it back
tomorrow! Still a long way to go until we have a reasonable
understanding of the limiting factors..


[[Image:Atlas day-jpeg.jpg]]

* 22 June: General power cut at CERN at 2:pm.

* 24 June : Dataset T0.D.run000949.ESD transfered from Lyon to LAL and TOKYO. Tranfering the same dataset to LAPP and LPC failed because these sites have same domain name (*.in2p3.fr) as Lyon.

* 25 June : Almost no transfer from CERN to T1s during the week-end.

* 26 June : SC4 transfers restarted with working DDM monitoring. Successfull transfers to LAL, SACLAY and TOKYO. Technical problem (domain name) for LAPP, LPNHE and LPC : under investigation. Contact BEIJING.
.
* 28 June :
** Problem of domain name solved for LAPP, LPC and LPNHE. First transfers to these sites have been done.
** Increase the number of LFC connection to 40 (advice from CERN-IT and DDM).
 AODs were transfered to all T2s associated to Lyon except BEIJING (looks like a FTS problem) 

**Transfer all AODs to LAL. Problems to transfer AODs to LAPP (one dcache server crashed)

* 29 June :
** Transfer of AODs to TOKYO

* 1 July
** Test transfers from LYONDISK to T2s
[[Image:T1-T2-0107-3.jpg]]

* 5 July :
** First DDM transfer to BEIJING

* 6 july
** [[Image:StackdayLYON.png]]

* 17 july
** Simultaneous transfers to T2 sites including BEIJING
**[[Image:StackdayLYON-17-7.png]]

* 27 july
** Simultaneous transfers to the 7 T2 sites for more than 24 hours; it reached more than 25MB/s
**[[Image:StackdayLYON-27-7.png]]

File:StackdayLYON-27-07-06.png

2006-07-27T09:22:46Z

Grahal: SC4 transfers to 7 T2s

SC4 transfers to 7 T2s

Atlas:SC4

2006-07-18T10:31:18Z

Grahal: /* Daily news */

== ''Bienvenue sur la page Atlas SC4 LCG-France Welcome to the LCG-France Atlas SC4 page'' ==
[https://uimon.cern.ch/twiki/bin/view/Atlas/ATLASServiceChallenges Twiki page : SC4 ATLAS]

[http://lcg2.in2p3.fr/wiki/images/Sc4-juin06.txt Compte rendu de la réunion SC4 ATLAS au CERN du 9 Juin (S.Jézéquel, G. Rahal) (written in french) ]

* T0 Role(CERN)
** Produce dummy files with 1 to 2 GB size(RAW, ESD et AOD) (see [https://uimon.cern.ch/twiki/bin/view/Atlas/AtlasTierZero T0 Twiki])
** Initiate T0->T1 transfers
** FTS server sents files to Lyon choosing between 'TAPE' (RAW 43,2 Mo/s) or 'DISK' (ESD,AOD 23+20 Mo/s) areas
* T1 Role (CCIN2P3)
** Get files from T0 (dedicated dcache area: L. Schwarz)
** Provides LFC (lfc-atlas.in2p3.fr) and FTS service (cclcgftsli01.in2p3.fr) (D. Bouvet)
** Send all AODs to each T2 (20 Mo/s) using Lyon FTS server
** Regurlarly cleanup files
* T2 Role (BEIJING, LAL, LAPP, LPC, LPNHE, SACLAY, TOKYO)
** Get files from T1 (Lyon). Files on the T2 are written in /home/atlas/sc4tier0/...
** Clean-up the files (?)
* Other roles
** ATLAS (S. Jézéquel) : Initiate T1->T2 transfers

== Information from DDM monitoring ==
* [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/ Main DDM monitoring page]

* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stack4h.png
* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stack4ht2.png

----

* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackday.png
* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackdayLYON.png
* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackdayt2.png

----

* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackweek.png
* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackweekLYON.png
* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackweekt2.png

--

* Transfer rates for LYON and associated T2s (validated files by DDM):
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplots.php?site=LYON LYON]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=BEIJING BEIJING]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=LAL LAL]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=LAPP LAPP]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=LPC LPC]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=LPNHE LPNHE]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=SACLAY SACLAY]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=TOKYO TOKYO]

* [http://atldq02.cern.ch:8000/dq2/site_monitor/sites Detailed information on each site ]

* [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/sitestates.php?site=LYON File transfer state in LYON ]

== Information from FTS monitoring ==

*[http://gridview.cern.ch/GRIDVIEW/graphs.php?GraphName=atlas&ThruputDataOption=&SrcSite=&DestSite=&DurationOption=&StartDay=&StartMonth=&StartYear=&EndDay=&EndMonth=&EndYear=&HostType=&GraphFor=VO Atlas FTS transfer rate]

* [http://gridview.cern.ch/GRIDVIEW/graphs.php?GraphName=IN2PCC&ThruputDataOption=&SrcSite=&DestSite=&DurationOption=&StartDay=&StartMonth=&StartYear=&EndDay=&EndMonth=&EndYear=&HostType=&GraphFor= CERN->Lyon FTS transfer rate]

*T1->T2 :
** 15 concurrent files and 10 streams for LYON-TOKYO
** 5 concurrent files and 5 streams for LYON-BEIJING (SE not enough powerful for 15/15 )
** 10 concurrent files and 10 streams for LYON-French T2s (LAL, LPNHE, LPC, SACLAY) except for LAPP (5 concurrent files and 1 stream)

== Information from dCache monitoring (provided by Lyon) ==

*[http://cctools.in2p3.fr/dcache/transfers/atlas-sc4.html Monitoring of dcache for SC4 areas]
* LYONDISK : 25 concurrent access maximum
* LYONTAPE : 10 concurrent access maximum

== VOBOX Configuration ==

* 4 processors 3 GHz
* 4 GB of memory ( 2 GB dedicated to SWAP)

== Disk space availability ==

* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=GRIF&visibility=SE GRIF]
* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=IN2P3-LPC&visibility=SE LPC]
* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=IN2P3-LAPP&visibility=SE LAPP]
* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=TOKYO-LCG2&visibility=SE TOKYO]
* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=IN2P3-CC&visibility=SE LYON]

== Daily news ==

* [https://uimon.cern.ch/twiki/bin/view/Atlas/DDMSc4#Daily_log SC4 Data Managment Daily log]

* 20 June 2006: Mail from Miguel Branco (DDM responsible)

Today we started deploying DQ2 on the remaining T1 sites (not all
sites still available). 
Attached is the result of a (nice) ramp up, easily beating SC3's
record (on the 1st day of export of SC4) peaking at ~ 270 MB/s. Each
'step' in the graph is an additional T1 being added to the export. 
Dataset subscriptions are now slowing down and will resume tomorrow.
Our DQ2 monitoring has been turned off and we expect to have it back
tomorrow! Still a long way to go until we have a reasonable
understanding of the limiting factors..


[[Image:Atlas day-jpeg.jpg]]

* 22 June: General power cut at CERN at 2:pm.

* 24 June : Dataset T0.D.run000949.ESD transfered from Lyon to LAL and TOKYO. Tranfering the same dataset to LAPP and LPC failed because these sites have same domain name (*.in2p3.fr) as Lyon.

* 25 June : Almost no transfer from CERN to T1s during the week-end.

* 26 June : SC4 transfers restarted with working DDM monitoring. Successfull transfers to LAL, SACLAY and TOKYO. Technical problem (domain name) for LAPP, LPNHE and LPC : under investigation. Contact BEIJING.
.
* 28 June :
** Problem of domain name solved for LAPP, LPC and LPNHE. First transfers to these sites have been done.
** Increase the number of LFC connection to 40 (advice from CERN-IT and DDM).
 AODs were transfered to all T2s associated to Lyon except BEIJING (looks like a FTS problem) 

**Transfer all AODs to LAL. Problems to transfer AODs to LAPP (one dcache server crashed)

* 29 June :
** Transfer of AODs to TOKYO

* 1 July
** Test transfers from LYONDISK to T2s
[[Image:T1-T2-0107-3.jpg]]

* 5 July :
** First DDM transfer to BEIJING

* 6 july
** [[Image:StackdayLYON.png]]

* 17 july
** Simultaneous transfers to T2 sites including BEIJING
**[[Image:StackdayLYON-17-7.png]]

Atlas:SC4

2006-07-18T10:29:47Z

Grahal: /* Daily news */

== ''Bienvenue sur la page Atlas SC4 LCG-France Welcome to the LCG-France Atlas SC4 page'' ==
[https://uimon.cern.ch/twiki/bin/view/Atlas/ATLASServiceChallenges Twiki page : SC4 ATLAS]

[http://lcg2.in2p3.fr/wiki/images/Sc4-juin06.txt Compte rendu de la réunion SC4 ATLAS au CERN du 9 Juin (S.Jézéquel, G. Rahal) (written in french) ]

* T0 Role(CERN)
** Produce dummy files with 1 to 2 GB size(RAW, ESD et AOD) (see [https://uimon.cern.ch/twiki/bin/view/Atlas/AtlasTierZero T0 Twiki])
** Initiate T0->T1 transfers
** FTS server sents files to Lyon choosing between 'TAPE' (RAW 43,2 Mo/s) or 'DISK' (ESD,AOD 23+20 Mo/s) areas
* T1 Role (CCIN2P3)
** Get files from T0 (dedicated dcache area: L. Schwarz)
** Provides LFC (lfc-atlas.in2p3.fr) and FTS service (cclcgftsli01.in2p3.fr) (D. Bouvet)
** Send all AODs to each T2 (20 Mo/s) using Lyon FTS server
** Regurlarly cleanup files
* T2 Role (BEIJING, LAL, LAPP, LPC, LPNHE, SACLAY, TOKYO)
** Get files from T1 (Lyon). Files on the T2 are written in /home/atlas/sc4tier0/...
** Clean-up the files (?)
* Other roles
** ATLAS (S. Jézéquel) : Initiate T1->T2 transfers

== Information from DDM monitoring ==
* [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/ Main DDM monitoring page]

* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stack4h.png
* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stack4ht2.png

----

* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackday.png
* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackdayLYON.png
* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackdayt2.png

----

* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackweek.png
* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackweekLYON.png
* http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/rrd/plots/stackweekt2.png

--

* Transfer rates for LYON and associated T2s (validated files by DDM):
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplots.php?site=LYON LYON]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=BEIJING BEIJING]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=LAL LAL]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=LAPP LAPP]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=LPC LPC]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=LPNHE LPNHE]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=SACLAY SACLAY]
** [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/siteplotst2.php?site=TOKYO TOKYO]

* [http://atldq02.cern.ch:8000/dq2/site_monitor/sites Detailed information on each site ]

* [http://atlas-ddm-monitoring.web.cern.ch/atlas-ddm-monitoring/sitestates.php?site=LYON File transfer state in LYON ]

== Information from FTS monitoring ==

*[http://gridview.cern.ch/GRIDVIEW/graphs.php?GraphName=atlas&ThruputDataOption=&SrcSite=&DestSite=&DurationOption=&StartDay=&StartMonth=&StartYear=&EndDay=&EndMonth=&EndYear=&HostType=&GraphFor=VO Atlas FTS transfer rate]

* [http://gridview.cern.ch/GRIDVIEW/graphs.php?GraphName=IN2PCC&ThruputDataOption=&SrcSite=&DestSite=&DurationOption=&StartDay=&StartMonth=&StartYear=&EndDay=&EndMonth=&EndYear=&HostType=&GraphFor= CERN->Lyon FTS transfer rate]

*T1->T2 :
** 15 concurrent files and 10 streams for LYON-TOKYO
** 5 concurrent files and 5 streams for LYON-BEIJING (SE not enough powerful for 15/15 )
** 10 concurrent files and 10 streams for LYON-French T2s (LAL, LPNHE, LPC, SACLAY) except for LAPP (5 concurrent files and 1 stream)

== Information from dCache monitoring (provided by Lyon) ==

*[http://cctools.in2p3.fr/dcache/transfers/atlas-sc4.html Monitoring of dcache for SC4 areas]
* LYONDISK : 25 concurrent access maximum
* LYONTAPE : 10 concurrent access maximum

== VOBOX Configuration ==

* 4 processors 3 GHz
* 4 GB of memory ( 2 GB dedicated to SWAP)

== Disk space availability ==

* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=GRIF&visibility=SE GRIF]
* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=IN2P3-LPC&visibility=SE LPC]
* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=IN2P3-LAPP&visibility=SE LAPP]
* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=TOKYO-LCG2&visibility=SE TOKYO]
* [http://gridice2.cnaf.infn.it:50080/gridice/site/site_details.php?siteName=IN2P3-CC&visibility=SE LYON]

== Daily news ==

* [https://uimon.cern.ch/twiki/bin/view/Atlas/DDMSc4#Daily_log SC4 Data Managment Daily log]

* 20 June 2006: Mail from Miguel Branco (DDM responsible)

Today we started deploying DQ2 on the remaining T1 sites (not all
sites still available). 
Attached is the result of a (nice) ramp up, easily beating SC3's
record (on the 1st day of export of SC4) peaking at ~ 270 MB/s. Each
'step' in the graph is an additional T1 being added to the export. 
Dataset subscriptions are now slowing down and will resume tomorrow.
Our DQ2 monitoring has been turned off and we expect to have it back
tomorrow! Still a long way to go until we have a reasonable
understanding of the limiting factors..


[[Image:Atlas day-jpeg.jpg]]

* 22 June: General power cut at CERN at 2:pm.

* 24 June : Dataset T0.D.run000949.ESD transfered from Lyon to LAL and TOKYO. Tranfering the same dataset to LAPP and LPC failed because these sites have same domain name (*.in2p3.fr) as Lyon.

* 25 June : Almost no transfer from CERN to T1s during the week-end.

* 26 June : SC4 transfers restarted with working DDM monitoring. Successfull transfers to LAL, SACLAY and TOKYO. Technical problem (domain name) for LAPP, LPNHE and LPC : under investigation. Contact BEIJING.
.
* 28 June :
** Problem of domain name solved for LAPP, LPC and LPNHE. First transfers to these sites have been done.
** Increase the number of LFC connection to 40 (advice from CERN-IT and DDM).
 AODs were transfered to all T2s associated to Lyon except BEIJING (looks like a FTS problem) 

**Transfer all AODs to LAL. Problems to transfer AODs to LAPP (one dcache server crashed)

* 29 June :
** Transfer of AODs to TOKYO

* 1 July
** Test transfers from LYONDISK to T2s
[[Image:T1-T2-0107-3.jpg]]

* 5 July :
** First DDM transfer to BEIJING

* 6 july
** [[Image:StackdayLYON.png]]

* 17 july
**[[Image:StackdayLYON-17-7.png]]

File:StackdayLYON-17-7.png

2006-07-18T10:27:49Z

Grahal: T1 - T2 transfers

T1 - T2 transfers