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
[Update] POST /linode/instances/{linodeId}/migrate #119
[Update] POST /linode/instances/{linodeId}/migrate #119
Conversation
leslitagordita
commented
Aug 30, 2019
•
edited
edited
- Also updates endpoint's description to add more information about pending host migration vs DC migration and info about NGN feature support.
- Updates endpoints summary name to include DC migration capability.
- Add request body example and linode cli example
|
||
|
||
**Note:** Next Generation Network (NGN) data centers do not support IPv6 `/116` pools or IP Failover. | ||
If you have these features enabled on your Linode and attempt to migrate to an NGN data center, |
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.
@alsaihn can you confirm this? I thought we just wouldn't persist the IPv6 pool and IP failover, not that we would prevent the migration from happening. I did a quick check in the code and didn't see anything that would fail the migration.
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.
@yoshizzle I found that information in this related KB post. I also checked w/ Sal, but more verification makes sense. Thanks!
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.
There's a ticket for that exact behavior in our backlog, so the comment as listed here is accurate for now. It will have to change later though.
Release 1.0.16
CT-1137 3PT Audit