Re: [google-appengine] Need advice on what to do POST HRD migration

[Takashi Matsuo]

On Sat, Aug 25, 2012 at 1:35 AM, n3phele <n3p...@gmail.com> wrote:

I have a question about what do to *after* migration to the HRD data store.

After migration I end up with

foo.appspot.com (old master/slave)

and

foo-hrd.appspot.com (new HRD app)

I have chosen the appengine setup so that requests to foo.appspot.com are redirected to foo-hrd.appspot.com

My question is:

Can I safely delete the foo.appspot.com application using the appengine dashboard and be sure that the redirect foo.appspot.com will remain in place?

Yes, you can safely delete the old app.

 

Thanks in advance

-N

 

--
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/-/nrFOVU87HSgJ.
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.

--
Takashi Matsuo | Developers Advocate | tma...@google.com

[Mike Putnam]

On Sun, Sep 09, 2012 at 06:27:59PM -0700, Jim McCabe wrote:
Here is my question - if Google Apps is currently pointing to the old app
(foo.appspot.com), but I delete that app in the App Engine console, will
the alias continue to forward web requests to the new app
(foo-hrd.appspot.com)? In other words, since Google Apps appears to be
permanently wired to the old app, will I lose all hosting if I delete the
old app?

In my recent conversions from master/slave to high replication, the
migration tool automatically rerouted traffic to the new app id. There
was some indication near the bottom(?) of the migration area that the
old app id was disabled and forwarding external requests to the new app
id.

However, if you communicated foo.appspot.com directly to your users then
you would need to re-communicate the foo-hd.appspot.com. Or if you are
masking the appspot domain with your own CNAME, then you would need to
modify that CNAME to point to foo-hrd.appspot.com.

Mike

[Jim McCabe]

Thanks - I ended up solving the problem differently a while after posting.  To reiterate I am using Google Apps to mask the appspot.com address with my own custom domain (and also using Google Apps to manage email).

I couldn't really figure out how to delete the old App Engine service from my Google Apps account.  However, I went ahead and added the new App Engine app (with the new application ID) to the Google Apps account, and it worked fine.  In fact, by surprise, it immediately removed the domain mapping so that I had no domain mapping at all.

That is - after I added the 2nd App Engine app, Google immediately removed the mapping of my custom domain the old app.  This made it possible for me to map the domain to the new app, no problem at all!

Jim

[Barry Hunter]

>
> However, if you communicated foo.appspot.com directly to your users then
> you would need to re-communicate the foo-hd.appspot.com.

Not true.

Once the alias is in place, the application at foo-hd.appspot.com is
still accessible at foo.appspot.com

From the outside world nothing has to change.

> Or if you are
> masking the appspot domain with your own CNAME, then you would need to
> modify that CNAME to point to foo-hrd.appspot.com.

Umm, no, should not be CNAMEing to appspot.com domain.

If you are using a custom domain - via Google Apps, the CNAME should
be to ghs.google.com anyway.

If using SSL, you may also have a specific hostname you should be CNAMEing to.