Skip to content
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

Staging Migration to new Azure Subscription #194

Closed
4 tasks done
Tracked by #179
VinceHillier opened this issue Apr 14, 2023 · 4 comments
Closed
4 tasks done
Tracked by #179

Staging Migration to new Azure Subscription #194

VinceHillier opened this issue Apr 14, 2023 · 4 comments
Assignees

Comments

@VinceHillier
Copy link
Contributor

VinceHillier commented Apr 14, 2023

Expanding on #179

Staging Migration Plan

Staging has ~550GB of data, previous transfers took 16m per 500G. It should be less than 20 minutes to transfer staging.

Pre window tasks:

  • Create new public IP for staging on new subscription
    20.106.209.98
  • Reduce TTL for staging.kernelci.org from 3600 to 600.
  • Schedule DNS update with LF determining T:0
  • Prepare NSG ruleset for post migration

T: 0m

  1. Shutdown staging vm
  2. Snapshot osDisk and data disk
  3. Update IP address for (api.)staging.kernelci.org in DNS
    T:+20m
  4. Transfer snapshots to new subscription
    T:+50m
  5. Create disks based off snapshots (staging disk should be 1TB)
  6. Create VM with osDisk and data disk, assign new public IP
    T:+70m
  7. Update NSG to match previous rules
  8. Update Zabbix monitoring to use new IP
    T:+80m
@VinceHillier VinceHillier self-assigned this Apr 14, 2023
@gctucker
Copy link
Contributor

I guess this is specifically about the staging.kernelci.org VM?

@VinceHillier
Copy link
Contributor Author

I guess this is specifically about the staging.kernelci.org VM?

Correct

@VinceHillier
Copy link
Contributor Author

This has been completed.

@gctucker
Copy link
Contributor

I believe we still need to update the DNS records with the longer TTLs and do some clean-up with the old subdomains. But that's a separate task, I don't think there's a GitHub issue for it yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants