[UPDATE] Migrating from Tokyo 1 to Tokyo 2 #2216
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When the migrations from Tokyo 1 to Tokyo 2 are scheduled, Linode will also reserve Tokyo 2 IP addresses for users' Tokyo 1 Linodes in advance of the migrations. These reserved IPs will be communicated to users in a support ticket to help them in planning their migrations. This guide update includes an explanation of this feature and how to take advantage of it.
As an added wrinkle, the dashboard for Tokyo 1 Linodes will show an early migration button before the official migration schedule is generated and sent to users, and users will be able to use this button to migrate to Tokyo 2. If a user migrates with this button before the migration schedule is set, then they will not have a Tokyo 2 IP reserved in advance for them; the reserved IPs are only provided when the migration schedule is set. This guide update acknowledges and explains this behavior.
A new section is included that explains how to update a domain's TTL ahead of the migration.