Senin, 20 April 2015

Important notice for Master/Slave Datastore app owners on Google App Engine

Dear App Engine Developer,

You are receiving this email because you are listed as an owner of a Google App Engine application that is configured to use the deprecated service Master/Slave Datastore, which will soon be shut down. Don’t worry though, this email gives clear instructions for what you need to do. Even if your application does not store data in Master/Slave Datastore, it is still configured to use Master/Slave Datastore, so please keep reading.

When we launched App Engine, Master/Slave Datastore was the only database service that applications could use to store data. Master/Slave Datastore had issues scaling with the size and complexity of applications running on App Engine, so we launched its successor, High Replication Datastore (HRD), in 2011. Since that launch HRD has proven to scale without issues.

One of our core goals with Google Cloud Platform is to provide customers with the best technologies to build their business, so when we saw that HRD was a more robust technology, we decided to make HRD the default database service. On April 4 2012 we announced the deprecation of Master/Slave Datastore -- our signal that three years from that date we would formally shut down the service.

That three years is upon us and, as mentioned above, one or more applications that you own (listed below) are running on Master/Slave Datastore. If you don’t take any action these applications will be shutdown on July 6, 2015 and will no longer serve traffic (users will see HTTP 404 responses).

To ensure that these applications continue to operate, you’ll need to follow these few steps for each application:
  • Log into the App Engine Admin Console
  • Create a new HRD application
  • Use the HRD Migration Utility (linked below) to migrate any Master/Slave data to the new HRD application

Step (3) is covered in greater detail in the Migrating to High Replication Datastore documentation.

An important note: You need to follow the above steps even if your application does not store any data because your application is configured to use the Master/Slave Datastore. For example, even if it’s a static HTML website. When we shut down the Master/Slave Datastore these applications will be also shut down if they are not migrated.

For applications on the Java 6 runtime: Java 6 apps must be upgraded to Java 7 prior to the migration to HRD.
To determine whether your app is a Java 6 app:
  • Visit the App Engine Admin console, and select your application.
  • In the left navigation pane, click Versions to display the versions page.
  • At the top of this form, click Try the new Versions page.
  • The Java runtime used by your app will be listed under RUNTIME.

To upgrade:
  • Update your development environment to use the latest App Engine Java SDK.
  • Redeploy your app to production App Engine.
  • Test it for correct behavior. There are a small number of potential compatibility issues between Java 6 and Java 7.

Below is the list of applications that you are an owner of that are running on Master/Slave Datastore:
ajixcoy21

After the decommission, we will be providing a grace period of one month during which users can re-enable their applications in order to migrate to HRD. Throughout that month, re-enabled applications will be periodically disabled according to the following schedule:

On July 6, 2015, Master/Slave applications will be disabled at 12:00pm Pacific time. You will be able to re-enable these applications and you will be able to migrate to HRD.

On July 13, 2015, Master/Slave applications that were re-enabled will be disabled at 12:00pm Pacific time. You will be able to re-enable these applications and you will be able to migrate to HRD.

On July 20, 2015, Master/Slave applications that were re-enabled will be disabled at 12:00pm Pacific time. You will be able to re-enable these applications and you will be able to migrate to HRD.

Starting July 27, 2015, Master/Slave applications that were re-enabled will be disabled daily at 12:00pm Pacific time. You will be able to re-enable these applications and you will be able to migrate to HRD, however they’ll be disabled every business day at this time.

On August 3, 2015, you will no longer be able to re-enable your application, however you will still be able to migrate to HRD.

On August 10, 2015, your Master/Slave application will be permanently shut down and will no longer be accessible.

This means that after August 10, 2015 these applications will stop servicing requests and you will no longer have programmatic access to your data. If you no longer need your Master/Slave applications and associated data, no action is required. However, if you do need any of these applications we encourage you to migrate them to HRD immediately.

For more information please visit: Master-Slave Datastore Service Turndown.
If you have any questions about the Master/Slave Datastore decommission, you can reach us via the Master/Slave Datastore deprecation support form.

Regards,

The Google Cloud Platform Team

---- © 2015 Google Inc. 1600 Amphitheatre Parkway, Mountain View, CA 94043

You have received this mandatory email service announcement to update you about important changes to Google Cloud Platform or your account.