Thanks, this is a good suggestion and definitely something we have in mind. We’d like to make it so that events affecting the VM can be published via something like pub/sub, and then you could imagine where perhaps Google Cloud Functions would be a good way to respond and handle them.
Thanks, we’ll consider this, but it’s probably a lot of engineering for a feature that most users rarely use.
This is something we’d love to add.
We’ve just released a feature to GA which allows you to detach and re-attach boot disks to GCE VMs.
Using this feature, you may now restore a VM from snapshot by:
1. Stopping the instance – (e.g. gcloud compute instances stop INSTANCE_NAME —zone INSTANCE_ZONE)
2. Detaching the boot disk from the VM in question ($ gcloud compute instances detach-disk INSTANCE_NAME —disk DISK_NAME —zone INSTANCE_ZONE)
2. Creating a disk from the snapshot in question
3. Attaching the disk from step 2 to the VM as the boot disk ($ gcloud compute instances attach-disk INSTANCE_NAME —disk NEW_DISK_NAME —boot —zone INSTANCE_ZONE)
After restore, the VM will keep its IP address and other properties (e.g. tags, labels, etc.).
See more info about the feature in the docs:
Down the road, we’re also planning to improve this flow to be “one-click easy.” More updates to come.Anonymous commented
Restore instance from a snapshot that create from the same instance before without kill instance and recreate it.
UPDATE: IPv6 load balancer endpoints are now GA.1 However, we continue to work on instance-level v6 addressing. Since I believe that at least some votes on this issue are for v6 all the way to the instance, I am leaving this issue open.