-
Notifications
You must be signed in to change notification settings - Fork 883
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
Srv6d openstack dualstack #1805
Conversation
Thanks for the PR! Could you please insert your github username alphabetically (with matching capitalization) instead of at the bottom? |
Sure, done. |
With AWS we went ipv4 first, since many of their instances don't have a functioning ipv6 IMDS. When all new AWS deployments get an ipv6 imds we intend to switch this order to prioritize ipv6. In this current PR, the ipv6 address will be tried first with a minor delay before ipv4. Since I think new openstack deployments are expected to have an ipv6 IMDS, I think this approach makes sense. I'm mentioning this in case anyone with more depth in openstack wants to chime in. |
I think it makes more sense to keep IPv4 first as you're still likely to have tons of deployments without IPv6. |
@TheRealFalcon In my tests there weren't any noticeable delays with v4 metadata caused by this change. In my opinion this behaviour makes sense, since most users would expect a happy eyeballs like approach and ipv4 is seldomly preferred when ipv6 is available. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks for the PR!
- CLA signed
The virtual machine cannot directly access fe80::a9fe |
The following is the configuration for virtual machine IPv6
|
After application of this change to 24.1.4 cloud-init, we are failing a test which surprisingly passes when we use Ubuntu's 24.3.1 version of cloud-init under identical setup:
|
|
@ani-sinha please keep the discussion in one place and please check out my idea on the cause: #5419 (comment) |
Proposed Commit Message
Add Support for IPv6 metadata to
DataSourceOpenStack
Additional Context
Test Steps
Will successfully request metadata over IPv6 from the openstack provider, given
it is reachable over IPv6. If not, or if IPv4 is faster it will be used instead.
Checklist: