Re: [google-appengine] App Engine HRD migration and easier process for people with no data
Google's messaging about migration is getting stronger, so I assume the why bother is so Google doesn't one day shut down my instance. - Kris On Thursday, September 20, 2012 4:30:07 PM UTC-7, Joshua Smith wrote: I have one such app, and I can tell you that it has had exactly 0 downtime for years. If you don't use the datastore, then whether you are on HR or M/S completely doesn't matter. Even during periodic maintenance, the app will just keep on serving. So… why bother? On Sep 20, 2012, at 5:09 PM, Greg Linden gli...@gmail.com javascript: wrote: Perhaps I'm wrong, but I'd assume there are a large number of appengine applications that have stored nothing in the datastore. It would be fantastic if there was a quick, easy tool to do the migration to HRD for those applications without the hassle of changing the application name and other goodies people with a more serious migrations have to do. Again, I may be wrong, but I'd assume that, if you have no data in your master/slave datastore, if you are not using your master/slave datastore, the migration to HRD could be done in place. Perhaps someone at Google could think about that, whether it would be easy to do, and how many people fall into this category. I'm sure you'd have much higher compliance if you made it easier, and this probably is one easy way to make it easier for a large number of people. -- You received this message because you are subscribed to the Google Groups Google App Engine group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/VpNv04_Nr1YJ. To post to this group, send email to google-a...@googlegroups.comjavascript: . To unsubscribe from this group, send email to google-appengi...@googlegroups.com javascript:. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en. -- You received this message because you are subscribed to the Google Groups Google App Engine group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/4TM_AH3o8JkJ. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Re: [google-appengine] App Engine HRD migration and easier process for people with no data
Oh, well.. yeah. Good point. I think google is stuck supporting M/S for 3 years after their deprecation warning, though. So I'm in no hurry. On Sep 21, 2012, at 3:49 PM, Kristopher Giesing kris.gies...@gmail.com wrote: Google's messaging about migration is getting stronger, so I assume the why bother is so Google doesn't one day shut down my instance. - Kris On Thursday, September 20, 2012 4:30:07 PM UTC-7, Joshua Smith wrote: I have one such app, and I can tell you that it has had exactly 0 downtime for years. If you don't use the datastore, then whether you are on HR or M/S completely doesn't matter. Even during periodic maintenance, the app will just keep on serving. So… why bother? On Sep 20, 2012, at 5:09 PM, Greg Linden gli...@gmail.com wrote: Perhaps I'm wrong, but I'd assume there are a large number of appengine applications that have stored nothing in the datastore. It would be fantastic if there was a quick, easy tool to do the migration to HRD for those applications without the hassle of changing the application name and other goodies people with a more serious migrations have to do. Again, I may be wrong, but I'd assume that, if you have no data in your master/slave datastore, if you are not using your master/slave datastore, the migration to HRD could be done in place. Perhaps someone at Google could think about that, whether it would be easy to do, and how many people fall into this category. I'm sure you'd have much higher compliance if you made it easier, and this probably is one easy way to make it easier for a large number of people. -- You received this message because you are subscribed to the Google Groups Google App Engine group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/VpNv04_Nr1YJ. To post to this group, send email to google-a...@googlegroups.com. To unsubscribe from this group, send email to google-appengi...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en. -- You received this message because you are subscribed to the Google Groups Google App Engine group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/4TM_AH3o8JkJ. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en. -- You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Re: [google-appengine] App Engine HRD migration and easier process for people with no data
I have one such app, and I can tell you that it has had exactly 0 downtime for years. If you don't use the datastore, then whether you are on HR or M/S completely doesn't matter. Even during periodic maintenance, the app will just keep on serving. So… why bother? On Sep 20, 2012, at 5:09 PM, Greg Linden glin...@gmail.com wrote: Perhaps I'm wrong, but I'd assume there are a large number of appengine applications that have stored nothing in the datastore. It would be fantastic if there was a quick, easy tool to do the migration to HRD for those applications without the hassle of changing the application name and other goodies people with a more serious migrations have to do. Again, I may be wrong, but I'd assume that, if you have no data in your master/slave datastore, if you are not using your master/slave datastore, the migration to HRD could be done in place. Perhaps someone at Google could think about that, whether it would be easy to do, and how many people fall into this category. I'm sure you'd have much higher compliance if you made it easier, and this probably is one easy way to make it easier for a large number of people. -- You received this message because you are subscribed to the Google Groups Google App Engine group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/VpNv04_Nr1YJ. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en. -- You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.