Create agent in parametric app using ipv6 address.

[mhlidd]

I'm looking to write a parametric test for the following ticket where we want to see whether setting an agent to an IPv6 address will lead to issues in the tracer. Could you point me towards how to customize an agent in the system-tests repo to use IPv6 and how to have a tracer point to it?

[cbeauchesne]

Hi,

From the docker doc :

IPv6 is only supported on Docker daemons running on Linux hosts.

We need to keep the parametric scenario working fine on all our laptops. It means there are two solutions :

• skip the parametric test if the host is not a Linux
• Or use and end-to-end scenario (it won't be runnable on non-linux hosts)

Form a technical point of view, I'm fine for both
Form a QA point of view, I'm strongly in favor of end-to-end, because IPv6 is something that will probably causes other issues in our tracers under the variety of condition encountered in real life. And parametric scenario can't catch those, where end-to-end scenario are far better to achieve that.

Do you have any opinion/argument in favor of parametric for this use case ?

[mhlidd]

Weblog makes sense to me here then. I believe it will cover all scenarios that I am concerned with. Just to double check, there are no prerequisite steps to using a weblog scenario with IPv6 right? I just start with setting a DD_AGENT_HOST and shouldn't encounter any issues?

[cbeauchesne]

By default, the docker network use IPv4. You could use a IPv4 translated to IPv6, and it should works. But you need to get the agent IP address, so it'll requires a few extra bit.

Though, I think we should go the ambitious way, and use a real IPv6, because I strongly suspect that a translated IPv4 address will be converted back by some network layer. So having a real IPv6 address is better IMO