search

devopsgroup-io / vagrant-digitalocean

:droplet: A Vagrant provider plugin that manages DigitalOcean droplets.
Mozilla Public License 2.0
1.71k stars 182 forks source link

Support suspend/resume #6

Open johnbender opened 11 years ago

johnbender commented 11 years ago

This appears to be possible as long as the snapshot id is available from the API. Then it's simply a call to the restore endpoint.

ianheggie commented 10 years ago

I would like this as well -

ianheggie commented 10 years ago

What are your thoughts on how this would be used - I can think of various scenarios:

  1. A combined snapshot/destroy and related create from snapshot - mainly to reduce costs of having lots of suspended machines lying around (at a rough calc, it appears you will be able to have 50 snapshots for the price of one running droplet, once they start charging for snapshots that is)
  2. Snapshots that are used for backup, allowing resumption at various stages to rewind/replay experiments.
  3. Cloning to possibly multiple droplets from the one snapshot
bradisbell commented 10 years ago

Beware that restoring from a snapshot offers no guarantee that you will get the same IP address, or even CPU type specifications. I don't think the snapshot feature of Digital Ocean is a good analog for suspended local VMs in VirtualBox or VMWare.

ianheggie commented 10 years ago

what variations are there on CPU type?

bradisbell commented 10 years ago

I worded that poorly... CPU type will stay the same, but the specs may not as there is no guarantee your new droplet will be on the same KVM host. On their FAQ page, they talk about the differences (not specifically to restoring from images):

We use server-grade Intel Hexcore processors between 2.0 GHz and 3.0 GHz. To view the clock speed and other details of the CPU on the hypervisor you are assigned, run this command on the command line: cat /proc/cpuinfo