CERN Accelerating science

LHC Experiment Application

HammerCloud

Name of Supplier and/or Developer: 
CERN IT-SDC
Contact details for Supplier and/or Developer: 
Ramon Medrano Llamas
Does developer claim IPv6 compliance?: 
Don't know
Did you try running on dual stack system?: 
No
Used by Experiment: 
ATLAS
CMS
LHCb
IPv6 Compliance: 

WMAgent

Does developer claim IPv6 compliance?: 
Don't know
Used by Experiment: 
CMS
IPv6 Compliance: 

CMSSW

Does developer claim IPv6 compliance?: 
Don't know
Used by Experiment: 
CMS
IPv6 Compliance: 

cmsweb

Name of Supplier and/or Developer: 
CMS
Contact details for Supplier and/or Developer: 
Diego da Silva Gomes
Does developer claim IPv6 compliance?: 
Yes
Did you try running on dual stack system?: 
Yes
If so, did it break the application?: 
No
Does it bind to both stacks?: 
Yes
Can it be configured to prefer IPv6 or IPv4?: 
Don't know/not tested
Used by Experiment: 
CMS
IPv6 Compliance: 

AliEN

Name of Supplier and/or Developer: 
ALICE
Does developer claim IPv6 compliance?: 
Don't know
Used by Experiment: 
ALICE

DIRAC

Name of Supplier and/or Developer: 
LHCb
Does developer claim IPv6 compliance?: 
Yes
Did you try running on dual stack system?: 
Yes
If so, did it break the application?: 
No
Does it bind to both stacks?: 
Yes
Can it be configured to prefer IPv6 or IPv4?: 
No
Name of Tester: 
Raja Nandakumar
Used by Experiment: 
LHCb
IPv6 Compliance: 
Are the logs IPv6 compliant?: 
Yes

PanDA

Does developer claim IPv6 compliance?: 
Yes
Did you try running on dual stack system?: 
Yes
Used by Experiment: 
ATLAS
IPv6 Compliance: 

PhEDEx agents

Name of Supplier and/or Developer: 
CMS
Contact details for Supplier and/or Developer: 
Tony Wildish
Does developer claim IPv6 compliance?: 
Don't know
Used by Experiment: 
CMS
IPv6 Compliance: 

various D web tools

Name of Supplier and/or Developer: 
CMS Database team
Contact details for Supplier and/or Developer: 
andreas.pfeiffer@cern.ch
Does developer claim IPv6 compliance?: 
Don't know
Does it bind to both stacks?: 
Don't know/not tested
Is IPv6 preferred by default?: 
Don't know/not tested
Can it be configured to prefer IPv6 or IPv4?: 
Don't know/not tested
Used by Experiment: 
CMS
IPv6 Compliance: 

Frontier

Name of Supplier and/or Developer: 
Dave Dykstra
Version: 
client 2.8.15
Release date: 
Tuesday, February 2, 2016
Does developer claim IPv6 compliance?: 
Yes
From which version of the application does the developer claim IPv6 compliance?: 
client 2.8.15
Did you try running on dual stack system?: 
Yes
If so, did it break the application?: 
No
Does it bind to both stacks?: 
Yes
Is IPv6 preferred by default?: 
No
Can it be configured to prefer IPv6 or IPv4?: 
Yes
Used by Experiment: 
ATLAS
CMS
How does it behave with a private IPv4 and a public IPv6?: 
It makes no distinction between private and public
IPv6 Compliance: 
Subscribe to RSS - LHC Experiment Application