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?

Thanks in advance
-N

Yes, you can safely delete the old app.

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

Takashi -

I have a similar question but with a slight twist.  I migrated an app
tonight to HRD and everything went great.  I would like the delete old app,
but beforehand I was assuming I would need to point my Google Apps account
to the new app.

Unfortunately I can't seem to point my Google Apps account to the new app -
I see "You do not have the permissions necessary to uninstall this
application." when I try to disable the old app in Google Apps (under
"Dashboard" then "Settings" then my app).  This is confusing for me because
I only have one account signed up on this domain and so I don't really
think there is a different user with higher credentials than me.

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?

On a related note, is there any page where we can see the active aliases?
 The only way to see the alias is to view the old app - but if I delete the
old app, how can I see that an alias exists?

Jim

     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

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

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.

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.