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.Tim White commented
+1 for v6 to the instance
We are currently testing a new option that may help people send mail without using a third party service. If you are interested in testing this product, please fill out the interest request form here1. Product Management for the feature may reach out to you.
We are also continuing to make improvements to our system to allow for some customers that have an established relationship with us to apply for an exception to be able to send directly on port 25. There are a number of IP reputation issues that have to be worked through for such a use case, so it should not be considered a common solution that will meet everyone’s needs.
We will have more updates on both of these items over time.
Thanks for the suggestion! Swap space is not a very common use case, so far as we know, and it might not rise to the level of something that makes sense to burden the API with for all time, but we’ll take a look.Tim White commented
Swap space is a common use case. Most cloud providers give you a small swapfile or swap partition by default. It prevents OOM issues when something suddenly balloons in memory, and swap will allow it to complete without crashing. For example, compiling something. Just adding an extra persistent disk for swap, or a swapfile would be useful. cloud-init should be able to handle this already
Thanks for the suggestion.
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.
Thx, pls see comments for further info.