IPv6 Compliance
Are the logs IPv6 compliant?
Yes
Tests on lxplus+ipv6 (dual-stack machine)
- Log in to post comments
Test with pure-ipv6 machine : first results
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.
- Log in to post comments
Formal ipv6 compliance
Latest version of DIRAC now is ipv6 compliant. Large-scale tests (from LHCb) are still pending, due to issues with python socket library used by LHCb from CERN-PH.
- Log in to post comments
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
- Log in to post comments
Can it be configured to prefer IPv6 or IPv4?
No
Name of Tester
Raja Nandakumar
Used by Experiment
LHCb
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