LHC Experiment Application

cmsweb

Submitted by sciaba on Mon, 07/15/2013 - 19:14
IPv6 Compliance
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

DIRAC

Submitted by sciaba on Mon, 07/15/2013 - 19:09
IPv6 Compliance
Are the logs IPv6 compliant?
Yes

Tested the following (all of which work) :

1. SetupProject - setting up the LHCb environment for generic LHCb projects

2. Setting up DIRAC environment and connecting to DIRAC services

2.1 Getting list and location of replicas for LFNs

2.2 Pinging DIRAC services at a CERN machine and the LHCb VO-box at GridKa to test if the services respond. This ping uses the dip protocol to connect to the services

Note: Supplier is LHCb + Dirac consortium (diracgrid.org)

Next on dual-stack machine : test generic job submission using Ganga

DIRAC not ipv6 compliant by default. The standard installation listens only on ipv4 ports.

It is not difficult to make it bind to ipv6 ports, but there are some niggling authentication issues that need to be sorted out.

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

various D web tools

Submitted by bhoeft on Mon, 05/13/2013 - 13:40
IPv6 Compliance
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

Frontier

Submitted by bhoeft on Mon, 05/13/2013 - 13:38
IPv6 Compliance
Name of Supplier and/or Developer
Dave Dykstra
Version
client 2.8.15
Release date
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