TWiki>
LCG Web>WLCGCommonComputingReadinessChallenges>WLCGOperationsWeb>WLCGOpsCoordination>WLCGOpsCoordWNOPN (2013-12-23, JosepFlix)
EditAttachPDF
LCG Web>WLCGCommonComputingReadinessChallenges>WLCGOperationsWeb>WLCGOpsCoordination>WLCGOpsCoordWNOPN (2013-12-23, JosepFlix) EditAttachPDFWorker Nodes on LHCOPN at WLCG Tier-1s
Survey on the status of deployment of Worker Nodes in the LHCOPN at WLCG Tier-1.| Site | Current status | Comments |
|---|---|---|
| YES/NO | ||
| CERN | YES | We verified that worker nodes both at CERN and at Wigner are all on the OPN. |
| ASGC | YES | |
| BNL | No | |
| CNAF | YES | |
| FNAL | YES | |
| IN2P3 | NO | |
| KISTI | YES | All cluster for ALICE T1 are to be in OPN (while joining OPN is in progress). |
| KIT | YES | The WNs are behind a NAT, so access from the WNs to OPN-connected resources is possible, but all traffic goes through the NAT gateway. |
| NDGF | Only a split ALICE-T1/CMS-T2 cluster is on the OPN. | Implementing local peering at all sites with the NDGF part of the OPN (not the entire LHCOPN), which means clusters can talk to the OPN via a local shortcut. After that, all clusters will be moved away from the OPN. |
| NL-T1 | No | We don't mind if WNs of other sites approach our storage over the OPN but because of reasons related to firmware we are not able to put our WNs on the LHCOPN yet. |
| PIC | No | No. WNs have private IPs (IPv4), then we cannot move then to OPN, the WN IP range is NAT'ed and enforced by the Internet access Firewall. Router connected to the LHCOPN does not have the NAT ability. Once we move to IPv6, the IPs could be public, and situation could be better for us. However, this would imply a re-definition of some of our internal VLANs and we are still investigating the impact. |
| RAL | No | However we are in the process of reviewing this. Our concerns primarily relate to the loss of firewall/security monitoring and uncontrolled traffic flows when our SE is down |
| TRIUMF | YES | The WNs are behind a NAT box which is on the LHCOPN. Note that our NAT traffic is limited to 1 Gbps by design and according to the current ATLAS use cases. |
LCG Wikis
- ABATBEA
- ACPP
- ADCgroup
- AEGIS
- AfricaMap
- AgileInfrastructure
- ALICE
- AliceEbyE
- AliceSPD
- AliceSSD
- AliceTOF
- AliFemto
- ALPHA
- ArdaGrid
- ASACUSA
- AthenaFCalTBAna
- Atlas
- AtlasLBNL
- AXIALPET
- CAE
- CALICE
- CDS
- CENF
- CERNSearch
- CLIC
- Cloud
- CloudServices
- CMS
- Controls
- CTA
- CvmFS
- DB
- DefaultWeb
- DESgroup
- DPHEP
- DM-LHC
- DSSGroup
- EGEE
- EgeePtf
- ELFms
- EMI
- ETICS
- FIOgroup
- FlukaTeam
- Frontier
- Gaudi
- GeneratorServices
- GuidesInfo
- HardwareLabs
- HCC
- HEPIX
- ILCBDSColl
- ILCTPC
- IMWG
- Inspire
- IPv6
- IT
- ItCommTeam
- ITCoord
- ITdeptTechForum
- ITDRP
- ITGT
- ITSDC
- LAr
- LCG
- LCGAAWorkbook
- Leade
- LHCAccess
- LHCAtHome
- LHCb
- LHCgas
- LHCONE
- LHCOPN
- LinuxSupport
- Main
- Medipix
- Messaging
- MPGD
- NA49
- NA61
- NA62
- NTOF
- Openlab
- PDBService
- Persistency
- PESgroup
- Plugins
- PSAccess
- PSBUpgrade
- R2Eproject
- RCTF
- RD42
- RFCond12
- RFLowLevel
- ROXIE
- Sandbox
- SocialActivities
- SPI
- SRMDev
- SSM
- Student
- SuperComputing
- Support
- SwfCatalogue
- TMVA
- TOTEM
- TWiki
- UNOSAT
- Virtualization
- VOBox
- WITCH
- XTCA
 |
|
Copyright &© 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors. Ideas, requests, problems regarding TWiki? Send feedback