Google Compute Engine Release Announcement

240 views

Skip to first unread message

Google Compute Engine Team

unread,

Oct 3, 2013, 7:31:48 PM10/3/13

Greetings Google Cloud Platform users,

Today, we have a couple of updates for Google Compute Engine: we've added two new features to the Load Balancing product and are also releasing a new version of our API.

Load Balancing Update

Load balancing now provides client session affinity, allowing clients communicating with your load balanced websites or applications to be consistently routed to the same healthy Instances. To enable session affinity, first decide whether to hash by client IP address only or client IP and protocol. Then use the new session_affinity parameter when creating your target pool. An example command to create a new target pool is below and more information can be found in the Target Pool documentation.

gcutil --project=${PROJECT_ID} addtargetpool www-pool --region=${REGION} \

--instances=${ZONE}/www1,${ZONE}/www2 --session_affinity=CLIENT_IP_PROTO

Target Pool resources now also allow for a backup target pool to be defined and then used when the percentage of healthy Instances drop to the threshold you configure. To make use of this feature, you can add a backup target pool to an existing primary target pool, or specify a backup target pool when creating a new primary target pool. In the API, we've added the setBackup operation to allow you to add a backup target pool to an existing target pool. You can also use the new gcutil command called settargetpoolbackup for the same result. For more information on how to specify backup target pools, see the Target Pool documentation.

gcutil --project=${PROJECT_ID} settargetpoolbackup www-pool \

--backup_pool=www-pool-backup --failover_ratio=.1

v1beta16 API Release

Today we're releasing an updated Compute Engine API, v1beta16. This API version adds new commands and parameters for the Load Balancing update mentioned above, as well as a few small changes listed below.

Note: If you have applications that parse the output of gcutil commands please read the transition guide carefully regarding the removal of some quota fields.

We simplified resource quotas by removing the separate limits for VM instances and number of persistent disks. We also renamed the Ephemeral Addresses quota to In Use Addresses and re-purposed it as a limit on the combined total of both ephemeral and reserved external IP addresses currently in use.
Zone resources no longer have quota information reported or enforced.
Region resources now have quota information and take the place of the old Zone quotas. Some Global quotas have moved to the Region resource as well.
Global quota default values have been increased across the board, so new projects should have more room to experiment and grow before having to ask for additional quota.
It is now possible to add and remove multiple instances in a single command for a target pool using the API or gcutil. See the Load Balancing documentation for more information.
Address resources have a new "users" field to replace the "user" field. Now multiple forwarding rules can be assigned to a single Address resource.

To summarize some of the region and zone quota changes to the API you can reference this gcutil output:

getregion output:

+--------------------+-------------------------------------------------+

| name | us-central1 |

| description | us-central1 |

| creation-time | 2013-09-03T00:00:00.482-07:00 |

| status | UP |

| zones | zones/us-central1-a,zones/us-central1-b |

| deprecation | |

| replacement | |

| usage | |

| cpus | 0.0/24.0 |

| disks-total-gb | 0.0/5120.0 |

| static-addresses | 1.0/7.0 |

| in-use-addresses | 0.0/23.0 |

+--------------------+-------------------------------------------------+

getzone output:

+---------------+-------------------------------+

| name | us-central1-a |

| description | us-central1-a |

| creation-time | 2013-09-03T00:00:00.482-07:00 |

| status | UP |

| deprecation | |

| replacement | |

+---------------+-------------------------------+

Thanks, and happy computing! As always, please send us any feedback via the normal channels.