TWiki>
LCG Web>WLCGCommonComputingReadinessChallenges>WLCGOperationsWeb>WLCGOpsCoordination>WlcgIpv6>WlcgIpv6SAM (2015-02-26, AndreaSciaba)
EditAttachPDF
LCG Web>WLCGCommonComputingReadinessChallenges>WLCGOperationsWeb>WLCGOpsCoordination>WlcgIpv6>WlcgIpv6SAM (2015-02-26, AndreaSciaba) EditAttachPDFUsing SAM to test IPv6
Goals
- Use SAM to submit automatic tests to IPv6-only or dual-stack service instances over the IPv6 protocol for client-server communications. This would be used to test all instances in the IPv6 testbed and it would be very important to immediately validate new software releases with respect to IPv6. It would be strongly related also to the middleware readiness validation activity.
- Test the compliance of the SAM infrastructure to IPv6. The main point is to make sure that SAM does not limit in any way the ability for sites to deploy services in dual-stack (or pure IPv6 mode, if the scenario is realistic). This is more intended for the SAM production system, which should seamlessly work on all service instances. It is not really required that all SAM components work over IPv6, whenever there are central services (located at CERN) interacting which will have an IPv4 address for the foreseeable future.
Milestones
| Step | Date | Comment |
|---|---|---|
| Use SAM to test dual-stack services | This can be done already now; no change is required | |
| Run the central Nagios on a dual-stack node | This tests the ability of Nagios to run in dual-stack and is a prerequisite to submit tests over IPv6 | |
| Understand, for the SAM tests run by Nagios, how to force them to use IPv6 (or IPv4 when applicable) on dual-stack or IPv6-only endpoints | ||
| Understand if Condor-G can handle a mixture of IPv4 and IPv6 CE endpoints | This is required for the job submission tests to work in a mixed environment; if not possible, a dedicated SAM infrastructure using only IPv6 will be needed | |
| Understand if the messaging system works with producers running on IPv6 WNs | This is required for IPv6-only worker nodes to be able to publish test results | |
| Understand if the CREAM/ARC-CE/gfal2 clients can work via IPv6 | This is needed for all the other job submission tests and the basic storage tests | |
| Deploy a dedicated SAM infrastructure for IPv6 validation | This is needed to achieve the first of the goals stated above | |
| Run tests from "representative" VOs | Currently the choice would be: ATLAS or CMS for Condor-G, LHCb for CREAM, ALICE for ARC-CE, ATLAS for gfal2 |
Edit | Attach | Topic revision: r1 - 2015-02-26 - AndreaSciaba
LCG Wikis
- ABATBEA
- ACPP
- ADCgroup
- AEGIS
- AfricaMap
- AgileInfrastructure
- ALICE
- AliceEbyE
- AliceSPD
- AliceSSD
- AliceTOF
- AliFemto
- ALPHA
- Altair
- 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-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors. or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback