Bill,
So I would detailed it like this:
- freeze VPS
when the VM stops providing services it's down as far as I'm concerned
please, note, that connections are not dropped, new connections are not
responded with RESET and when VM is migrated all the clients are
serviced as if nothing has happened. From client point of view there is
only a small delay in servicing, but not a real downtime (when clients
are rejected). Maybe due to these some of people call it zero down-time.
Though from technical POV this is not the best term for sure. It is
better to call it checkpointing/restore or live migration.
- freeze networking
- copy VPS data to destination
- dump VPS
- copy dump to the destination
- restore VPS
- unfreeze VPS
and here is where my service is available again. The server may not know
it's been down, but the clients will.
- kill original VPS on source
Moreover, in OpenVZ live migration allows to migrate 32bit VPSs
between i686 and x86-64 Linux machines.
I guess you're using "zero downtime" as a marketing term rather than a
technical term.
Thanks,
Kirill
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
