-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add network dict with ipv6 #26
base: main
Are you sure you want to change the base?
Conversation
This change should be tested on both IPv6-only and IPv4 hosts. I did not have time to complete the tests yet. |
@italovalcy @gretelliz -- IPv6 site (TACC) worked well for completion of the tests. IPv4 site (FIU) worked well for completion of the tests. Although tests are completed on both of the VMs, they showed different results. |
Hi Mert, thanks for submitting the PR for adding support for IPv6. Just for us to understand: is there anything that is being impacted by the lack of IPv6 support at this point? The reason I'm asking this, and also the reason why we didnt apply this PR at this point, is that the integration with OESS and Juniper vMX presented some challenges for this new ipv6 setup that I'm still trying to figure it out. Understanding how critical IPv6 support is would help us prioritize this. |
No, there is nothing being impacted by the lack of IPv6 support. |
Hi Mert! thank you for clarifying this point! My suggestion them is that we keep this PR open for now while we figure this integration with OESS Juniper vMX first. I will try to handle this until the end of the week and I will let you know, okay? |
Sure. And I really don't have any kind of dependency to these changes. |
network dictionary added to the docker-compose.yml with IPv6 subnet enabled.
services are attached to the (docker) network.
This addition will make the containers be connected to an IPv6 subnet, so that on IPv6-only hosts (eg. FABRIC sites STAR, HAWI) can be used to run the tests.