[RFT] MigrationQueue, for host9-host26 Linoders

March 15, 2007 9:59 pm

I would like for a few of you waiting for the upgrades on hosts 9-26 to test a self-serve migration feature in the LPM before releasing it to the masses.

Once you accept (by clicking a button) your Linode will enter a "Migration Queue". The queue limits the number of concurrent migrations of Linodes per datacenter. You leave your Linode running and when your turn in the Queue comes around your Linode will be shutdown, migrated, upgraded to the correct resources, and booted.

https://www.linode.com/members/migrate/

Thank for the help!
-Chris

12 Responses

  1. Well, it seems to be working… the data is currently being migrated from host21 to host73. Two thoughts so far.

    1) provide a list of how many are in the queue and an estimated start time. I clicked on "migrate" and then had no idea when to expect my server to be shut down. Made me feel a little out of control.

    2) while the migration is happening the dashboard status is "Brand New". Should say "Migrating" 🙂

  2. Queued mine about 10 minutes ago and it seems to be migrating OK now. It began only a minute or two after I queued it, though, so not sure how well it tested the queueing part.

    I’ll agree with Stephen that the "Brand New" status could be a little disconcerting though probably not a big deal. Another thing that would be nice is to be able to see more of the job queue history – I missed the finish of the job to migrate my first disk and now it’s dropped out of the Dashboard page so I can’t see what I hope is the reassuring "Success" status for that job.

    UPDATE: The migration has finished and my linode is back up and running. The only minor issue I’ve noticed is that the SSH key for logging into the Lish console don’t seem to have migrated to the new machine, but I expect I can just upload it again. And, of course, now I have the terrible problem of deciding how to use the new-found 50% free disk storage, doubled RAM, etc. 😉

    Thanks! 😀

  3. I had to leave to go to work while the migration was running but I got my "up!" page at 7:24, 26 minutes after the migration started.

    Everything seemed to go without a hitch.

  4. Hi,

    Migration went very smoothly – took 14 minutes (had about 3 gigs to move).

    New host much more responsive so far.

    Thanks

    Jon

  5. [quote:9816be0bd4=”zibeli”]Another thing that would be nice is to be able to see more of the job queue history[/quote]

    I’d also like to be able to see more of the history sometimes.

  6. [quote=”knehcsa”]I’d also like to be able to see more of the history sometimes.[/quote]
    Done. There’s a new link which appears at the top right of the Job Queue table — Show more Jobs (and Show fewer Jobs). It doesn’t persist across refreshes, but I think that’s good enough…

    [quote=”sweh”]2) while the migration is happening the dashboard status is "Brand New". Should say "Migrating" :-)[/quote]
    Also fixed.

    -Chris

  7. [quote:fe38356838=”caker”]Done. There’s a new link which appears at the top right of the Job Queue table — Show more Jobs (and Show fewer Jobs). It doesn’t persist across refreshes, but I think that’s good enough…[/quote]

    Cool – it’s handy to have a look if you’ve got trouble – not something you need to see every day.

  8. Just to confirm – the existing Fremont hosts will be upgraded at some point in the near future, correct? this migration is optional?

    What happens to the IP address(es) – does it/they change if a linode is migrated within the same datacenter? i.e. if I migrated, would I also have to update my DNS records and wait for them to propagate?

    Paul (on host20)

  9. [quote:a4e4747ddb=”PaulC”]Just to confirm – the existing Fremont hosts will be upgraded at some point in the near future, correct? this migration is optional?

    What happens to the IP address(es) – does it/they change if a linode is migrated within the same datacenter? i.e. if I migrated, would I also have to update my DNS records and wait for them to propagate?

    Paul (on host20)[/quote]

    If you want the upgrades now, I suggest doing the migration. Everything moves with you. You press the button, your node is shutdown, disk images migrated, and then your node is rebooted. No changes are required on your end.

    -Chris

  10. I just migrated my Linode from 12 to 73, it worked perfectly.

    I’ve also learned (again!) that I need to check the forums more often; I expect my etch upgrade this morning would have gone more quickly with the extra memory!

    Steve, with a Linode 64^H^H80^H^H128^H^H^H256!

  11. Should I be able to with li9-234 ?

  12. [quote:5117871d35=”caker”]I would like for a few of you waiting for the upgrades on hosts 9-26 to test a self-serve migration feature in the LPM before releasing it to the masses.

    Once you accept (by clicking a button) your Linode will enter a "Migration Queue". The queue limits the number of concurrent migrations of Linodes per datacenter. You leave your Linode running and when your turn in the Queue comes around your Linode will be shutdown, migrated, upgraded to the correct resources, and booted.

    https://www.linode.com/members/migrate/

    Thank for the help!
    -Chris[/quote]

    Chris,
    Just did the migration from host26 to host73.

    As I’ve come to expect with Linode, it was quick (<10 min), easy, and painless.

    Thanks for the great tools and the continual server upgrades!

    –John

Leave a Reply