Re: [google-appengine] HRD migration tool now available!
On Mon, Nov 14, 2011 at 8:13 AM, Joshua Smith joshuaesm...@charter.net wrote:
Cool. And that will be OK to use in Python 2.7 (I recall reading something
about not using environment variables there)?
Environment variables are thread-local in Python 2.7 so this pattern
will work there as well.
Cheers,
Brian
On Nov 13, 2011, at 2:54 PM, Alfred Fuller wrote:
full_app_id = os.getenv('APPLICATION_ID')
On Fri, Nov 11, 2011 at 12:24 PM, Joshua Smith joshuaesm...@charter.net
wrote:
Another question. I have this code in my app, so that when someone comes
in with an old key, my code will quietly convert it to the new app-id:
from google.appengine.api.app_identity import get_application_id
appname = get_application_id()
@monkeypatch_method(webapp.Request)
def get_db(self, key_attr):
k = self.get(key_attr)
if not k:
return None
key = db.Key(k)
if key.app() == appname:
return db.get(key)
logging.info(Fixing up key from old app %s (%s=%s) % ( key.app() ,
key_attr , k ))
fixed_key = db.Key.from_path(*key.to_path())
return db.get(fixed_key)
So what's happening is it is fixing up every key, because
get_application_id() doesn't have s~ on the front.
What should I call to get the app id used in Keys? (The one with the s~ in
front?)
(BTW: This approach turned out to be a real time-saver for migrating my
blobs. I could pass the old version keys from the new HR version, and it
fixed them up into its own namespace without my having to even think about
it.)
-Joshua
On Nov 11, 2011, at 1:16 PM, Joshua Smith wrote:
OK, so the migration from MS to HR was really fast, and I ran into no
problems. Woo hoo!
I didn't do the alias step, because I now need to figure out how to move
my old blobs into the new app, and I suspect that if I did the alias that
would get really, really hard. Right?
So instead, I changed the mapping of my www.myapp.com to point to the HR
version using google apps domain management. Seems to have worked. Woo hoo
again!
How do I get my post-migration email budget back up to 2000? App ID of
the new app is towngovernment-hr
Now to move the blobs...
On Nov 10, 2011, at 9:49 AM, Joshua Smith wrote:
Guess I know what I'll be doing on my day off tomorrow.
In case anyone didn't notice this in the docs:
Currently, the HRD Migration Tool does not support copying data from
Blobstore. If you use Blobstore, you need to manually copy that data over.
Ugh. That's a pretty huge hole in the tool.
Perhaps I know what I'll be doing all weekend…
-Joshua
On Nov 9, 2011, at 4:33 PM, Stacy (Google) wrote:
We’ve just released a new self service HRD migration tool. This tool
copies all of your data to HRD minimizing read-only times by using a
multi-phase approach. Please see the documentation for details on how to
use this. This tool is still considered experimental, please report
problems you experience here in the forum or to the external issue
tracker.We are still working on solutions for users of blobstore.
Using HRD makes your app eligible for our SLA, and will lead to much
better availability and more consistent performance. We think every app
will benefit from the switch to HRD.
Stacy
--
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/-/RzmZ--blDgIJ.
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.
--
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.
--
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.
--
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
Re: [google-appengine] HRD migration tool now available!
full_app_idhttps://cs.corp.google.com/#google3/apphosting/api/app_identity/app_identity.pyct=xref_usagesgs=py:google3.apphosting.api.app_identity.app_identity.get_application_idamp;full_app_id:google3/apphosting/api/app_identity/app_identity.pyl=336gsn=full_app_id=
oshttp://www.google.com/url?sa=Dq=http%3A%2F%2Fdocs.python.org%2Flibrary%2Fos.html
.getenvhttp://www.google.com/url?sa=Dq=http%3A%2F%2Fdocs.python.org%2Flibrary%2Fos.html%23process-parameters
('APPLICATION_ID')
On Fri, Nov 11, 2011 at 12:24 PM, Joshua Smith joshuaesm...@charter.netwrote:
Another question. I have this code in my app, so that when someone comes
in with an old key, my code will quietly convert it to the new app-id:
from google.appengine.api.app_identity import get_application_id
appname = get_application_id()
@monkeypatch_method(webapp.Request)
def get_db(self, key_attr):
k = self.get(key_attr)
if not k:
return None
key = db.Key(k)
if key.app() == appname:
return db.get(key)
logging.info(Fixing up key from old app %s (%s=%s) % ( key.app() ,
key_attr , k ))
fixed_key = db.Key.from_path(*key.to_path())
return db.get(fixed_key)
So what's happening is it is fixing up every key, because
get_application_id() doesn't have s~ on the front.
*What should I call to get the app id used in Keys?* (The one with the s~
in front?)
(BTW: This approach turned out to be a real time-saver for migrating my
blobs. I could pass the old version keys from the new HR version, and it
fixed them up into its own namespace without my having to even think about
it.)
-Joshua
On Nov 11, 2011, at 1:16 PM, Joshua Smith wrote:
OK, so the migration from MS to HR was really fast, and I ran into no
problems. Woo hoo!
I didn't do the alias step, because I now need to figure out how to move
my old blobs into the new app, and I suspect that if I did the alias that
would get really, really hard. Right?
So instead, I changed the mapping of my www.myapp.com to point to the HR
version using google apps domain management. Seems to have worked. Woo
hoo again!
How do I get my post-migration email budget back up to 2000? App ID of
the new app is towngovernment-hr
Now to move the blobs...
On Nov 10, 2011, at 9:49 AM, Joshua Smith wrote:
Guess I know what I'll be doing on my day off tomorrow.
In case anyone didn't notice this in the docs:
Currently, the HRD Migration Tool does not support copying data from
Blobstore. If you use Blobstore, you need to manually copy that data over.
Ugh. That's a pretty huge hole in the tool.
Perhaps I know what I'll be doing all weekend…
-Joshua
On Nov 9, 2011, at 4:33 PM, Stacy (Google) wrote:
We’ve just released a new self service HRD migration tool. This tool
copies all of your data to HRD minimizing read-only times by using a
multi-phase approach. Please see the
documentationhttp://code.google.com/appengine/docs/adminconsole/applicationsettings.html#Migrate_from_Master/Slave_to_High_Replication_Datastorefor
details on how to use this. This tool is still considered
experimental, please report problems you experience here in the forum or to
the external issue tracker.We are still working on solutions for users of
blobstore.
Using HRD makes your app eligible for our SLA, and will lead to much
better availability and more consistent performance. We think every app
will benefit from the switch to HRD.
Stacy
--
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/-/RzmZ--blDgIJ.
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.
--
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.
--
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
Re: [google-appengine] HRD migration tool now available!
Cool. And that will be OK to use in Python 2.7 (I recall reading something
about not using environment variables there)?
On Nov 13, 2011, at 2:54 PM, Alfred Fuller wrote:
full_app_id = os.getenv('APPLICATION_ID')
On Fri, Nov 11, 2011 at 12:24 PM, Joshua Smith joshuaesm...@charter.net
wrote:
Another question. I have this code in my app, so that when someone comes in
with an old key, my code will quietly convert it to the new app-id:
from google.appengine.api.app_identity import get_application_id
appname = get_application_id()
@monkeypatch_method(webapp.Request)
def get_db(self, key_attr):
k = self.get(key_attr)
if not k:
return None
key = db.Key(k)
if key.app() == appname:
return db.get(key)
logging.info(Fixing up key from old app %s (%s=%s) % ( key.app() ,
key_attr , k ))
fixed_key = db.Key.from_path(*key.to_path())
return db.get(fixed_key)
So what's happening is it is fixing up every key, because
get_application_id() doesn't have s~ on the front.
What should I call to get the app id used in Keys? (The one with the s~ in
front?)
(BTW: This approach turned out to be a real time-saver for migrating my
blobs. I could pass the old version keys from the new HR version, and it
fixed them up into its own namespace without my having to even think about
it.)
-Joshua
On Nov 11, 2011, at 1:16 PM, Joshua Smith wrote:
OK, so the migration from MS to HR was really fast, and I ran into no
problems. Woo hoo!
I didn't do the alias step, because I now need to figure out how to move my
old blobs into the new app, and I suspect that if I did the alias that would
get really, really hard. Right?
So instead, I changed the mapping of my www.myapp.com to point to the HR
version using google apps domain management. Seems to have worked. Woo hoo
again!
How do I get my post-migration email budget back up to 2000? App ID of the
new app is towngovernment-hr
Now to move the blobs...
On Nov 10, 2011, at 9:49 AM, Joshua Smith wrote:
Guess I know what I'll be doing on my day off tomorrow.
In case anyone didn't notice this in the docs:
Currently, the HRD Migration Tool does not support copying data from
Blobstore. If you use Blobstore, you need to manually copy that data over.
Ugh. That's a pretty huge hole in the tool.
Perhaps I know what I'll be doing all weekend…
-Joshua
On Nov 9, 2011, at 4:33 PM, Stacy (Google) wrote:
We’ve just released a new self service HRD migration tool. This tool
copies all of your data to HRD minimizing read-only times by using a
multi-phase approach. Please see the documentation for details on how to
use this. This tool is still considered experimental, please report
problems you experience here in the forum or to the external issue
tracker.We are still working on solutions for users of blobstore.
Using HRD makes your app eligible for our SLA, and will lead to much
better availability and more consistent performance. We think every app
will benefit from the switch to HRD.
Stacy
--
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/-/RzmZ--blDgIJ.
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.
--
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.
--
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.
--
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,
Re: [google-appengine] HRD migration tool now available!
I believe it should work. Tou should probably file a feature request to add
a function for this purpose to that app_identity api.
On Sun, Nov 13, 2011 at 1:13 PM, Joshua Smith joshuaesm...@charter.netwrote:
Cool. And that will be OK to use in Python 2.7 (I recall reading something
about not using environment variables there)?
On Nov 13, 2011, at 2:54 PM, Alfred Fuller wrote:
full_app_idhttps://cs.corp.google.com/#google3/apphosting/api/app_identity/app_identity.pyct=xref_usagesgs=py:google3.apphosting.api.app_identity.app_identity.get_application_idfull_app_id:google3/apphosting/api/app_identity/app_identity.pyl=336gsn=full_app_id=
oshttp://www.google.com/url?sa=Dq=http%3A%2F%2Fdocs.python.org%2Flibrary%2Fos.html
.getenvhttp://www.google.com/url?sa=Dq=http%3A%2F%2Fdocs.python.org%2Flibrary%2Fos.html%23process-parameters
('APPLICATION_ID')
On Fri, Nov 11, 2011 at 12:24 PM, Joshua Smith
joshuaesm...@charter.netwrote:
Another question. I have this code in my app, so that when someone comes
in with an old key, my code will quietly convert it to the new app-id:
from google.appengine.api.app_identity import get_application_id
appname = get_application_id()
@monkeypatch_method(webapp.Request)
def get_db(self, key_attr):
k = self.get(key_attr)
if not k:
return None
key = db.Key(k)
if key.app() == appname:
return db.get(key)
logging.info(Fixing up key from old app %s (%s=%s) % ( key.app() ,
key_attr , k ))
fixed_key = db.Key.from_path(*key.to_path())
return db.get(fixed_key)
So what's happening is it is fixing up every key, because
get_application_id() doesn't have s~ on the front.
*What should I call to get the app id used in Keys?* (The one with the
s~ in front?)
(BTW: This approach turned out to be a real time-saver for migrating my
blobs. I could pass the old version keys from the new HR version, and it
fixed them up into its own namespace without my having to even think about
it.)
-Joshua
On Nov 11, 2011, at 1:16 PM, Joshua Smith wrote:
OK, so the migration from MS to HR was really fast, and I ran into no
problems. Woo hoo!
I didn't do the alias step, because I now need to figure out how to move
my old blobs into the new app, and I suspect that if I did the alias that
would get really, really hard. Right?
So instead, I changed the mapping of my www.myapp.com to point to the HR
version using google apps domain management. Seems to have worked. Woo
hoo again!
How do I get my post-migration email budget back up to 2000? App ID of
the new app is towngovernment-hr
Now to move the blobs...
On Nov 10, 2011, at 9:49 AM, Joshua Smith wrote:
Guess I know what I'll be doing on my day off tomorrow.
In case anyone didn't notice this in the docs:
Currently, the HRD Migration Tool does not support copying data from
Blobstore. If you use Blobstore, you need to manually copy that data over.
Ugh. That's a pretty huge hole in the tool.
Perhaps I know what I'll be doing all weekend…
-Joshua
On Nov 9, 2011, at 4:33 PM, Stacy (Google) wrote:
We’ve just released a new self service HRD migration tool. This tool
copies all of your data to HRD minimizing read-only times by using a
multi-phase approach. Please see the
documentationhttp://code.google.com/appengine/docs/adminconsole/applicationsettings.html#Migrate_from_Master/Slave_to_High_Replication_Datastorefor
details on how to use this. This tool is still considered
experimental, please report problems you experience here in the forum or to
the external issue tracker.We are still working on solutions for users of
blobstore.
Using HRD makes your app eligible for our SLA, and will lead to much
better availability and more consistent performance. We think every app
will benefit from the switch to HRD.
Stacy
--
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/-/RzmZ--blDgIJ.
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.
--
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
Re: [google-appengine] HRD migration tool now available!
Done. Issue 6327
On Nov 13, 2011, at 4:17 PM, Alfred Fuller wrote:
I believe it should work. Tou should probably file a feature request to add a
function for this purpose to that app_identity api.
On Sun, Nov 13, 2011 at 1:13 PM, Joshua Smith joshuaesm...@charter.net
wrote:
Cool. And that will be OK to use in Python 2.7 (I recall reading something
about not using environment variables there)?
On Nov 13, 2011, at 2:54 PM, Alfred Fuller wrote:
full_app_id = os.getenv('APPLICATION_ID')
On Fri, Nov 11, 2011 at 12:24 PM, Joshua Smith joshuaesm...@charter.net
wrote:
Another question. I have this code in my app, so that when someone comes in
with an old key, my code will quietly convert it to the new app-id:
from google.appengine.api.app_identity import get_application_id
appname = get_application_id()
@monkeypatch_method(webapp.Request)
def get_db(self, key_attr):
k = self.get(key_attr)
if not k:
return None
key = db.Key(k)
if key.app() == appname:
return db.get(key)
logging.info(Fixing up key from old app %s (%s=%s) % ( key.app() ,
key_attr , k ))
fixed_key = db.Key.from_path(*key.to_path())
return db.get(fixed_key)
So what's happening is it is fixing up every key, because
get_application_id() doesn't have s~ on the front.
What should I call to get the app id used in Keys? (The one with the s~ in
front?)
(BTW: This approach turned out to be a real time-saver for migrating my
blobs. I could pass the old version keys from the new HR version, and it
fixed them up into its own namespace without my having to even think about
it.)
-Joshua
On Nov 11, 2011, at 1:16 PM, Joshua Smith wrote:
OK, so the migration from MS to HR was really fast, and I ran into no
problems. Woo hoo!
I didn't do the alias step, because I now need to figure out how to move my
old blobs into the new app, and I suspect that if I did the alias that
would get really, really hard. Right?
So instead, I changed the mapping of my www.myapp.com to point to the HR
version using google apps domain management. Seems to have worked. Woo
hoo again!
How do I get my post-migration email budget back up to 2000? App ID of the
new app is towngovernment-hr
Now to move the blobs...
On Nov 10, 2011, at 9:49 AM, Joshua Smith wrote:
Guess I know what I'll be doing on my day off tomorrow.
In case anyone didn't notice this in the docs:
Currently, the HRD Migration Tool does not support copying data from
Blobstore. If you use Blobstore, you need to manually copy that data over.
Ugh. That's a pretty huge hole in the tool.
Perhaps I know what I'll be doing all weekend…
-Joshua
On Nov 9, 2011, at 4:33 PM, Stacy (Google) wrote:
We’ve just released a new self service HRD migration tool. This tool
copies all of your data to HRD minimizing read-only times by using a
multi-phase approach. Please see the documentation for details on how to
use this. This tool is still considered experimental, please report
problems you experience here in the forum or to the external issue
tracker.We are still working on solutions for users of blobstore.
Using HRD makes your app eligible for our SLA, and will lead to much
better availability and more consistent performance. We think every app
will benefit from the switch to HRD.
Stacy
--
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/-/RzmZ--blDgIJ.
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.
--
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.
--
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] HRD migration tool now available!
OK, so the migration from MS to HR was really fast, and I ran into no problems. Woo hoo! I didn't do the alias step, because I now need to figure out how to move my old blobs into the new app, and I suspect that if I did the alias that would get really, really hard. Right? So instead, I changed the mapping of my www.myapp.com to point to the HR version using google apps domain management. Seems to have worked. Woo hoo again! How do I get my post-migration email budget back up to 2000? App ID of the new app is towngovernment-hr Now to move the blobs... On Nov 10, 2011, at 9:49 AM, Joshua Smith wrote: Guess I know what I'll be doing on my day off tomorrow. In case anyone didn't notice this in the docs: Currently, the HRD Migration Tool does not support copying data from Blobstore. If you use Blobstore, you need to manually copy that data over. Ugh. That's a pretty huge hole in the tool. Perhaps I know what I'll be doing all weekend… -Joshua On Nov 9, 2011, at 4:33 PM, Stacy (Google) wrote: We’ve just released a new self service HRD migration tool. This tool copies all of your data to HRD minimizing read-only times by using a multi-phase approach. Please see the documentation for details on how to use this. This tool is still considered experimental, please report problems you experience here in the forum or to the external issue tracker.We are still working on solutions for users of blobstore. Using HRD makes your app eligible for our SLA, and will lead to much better availability and more consistent performance. We think every app will benefit from the switch to HRD. Stacy -- 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/-/RzmZ--blDgIJ. 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. -- 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] HRD migration tool now available!
Another question. I have this code in my app, so that when someone comes in with an old key, my code will quietly convert it to the new app-id: from google.appengine.api.app_identity import get_application_id appname = get_application_id() @monkeypatch_method(webapp.Request) def get_db(self, key_attr): k = self.get(key_attr) if not k: return None key = db.Key(k) if key.app() == appname: return db.get(key) logging.info(Fixing up key from old app %s (%s=%s) % ( key.app() , key_attr , k )) fixed_key = db.Key.from_path(*key.to_path()) return db.get(fixed_key) So what's happening is it is fixing up every key, because get_application_id() doesn't have s~ on the front. What should I call to get the app id used in Keys? (The one with the s~ in front?) (BTW: This approach turned out to be a real time-saver for migrating my blobs. I could pass the old version keys from the new HR version, and it fixed them up into its own namespace without my having to even think about it.) -Joshua On Nov 11, 2011, at 1:16 PM, Joshua Smith wrote: OK, so the migration from MS to HR was really fast, and I ran into no problems. Woo hoo! I didn't do the alias step, because I now need to figure out how to move my old blobs into the new app, and I suspect that if I did the alias that would get really, really hard. Right? So instead, I changed the mapping of my www.myapp.com to point to the HR version using google apps domain management. Seems to have worked. Woo hoo again! How do I get my post-migration email budget back up to 2000? App ID of the new app is towngovernment-hr Now to move the blobs... On Nov 10, 2011, at 9:49 AM, Joshua Smith wrote: Guess I know what I'll be doing on my day off tomorrow. In case anyone didn't notice this in the docs: Currently, the HRD Migration Tool does not support copying data from Blobstore. If you use Blobstore, you need to manually copy that data over. Ugh. That's a pretty huge hole in the tool. Perhaps I know what I'll be doing all weekend… -Joshua On Nov 9, 2011, at 4:33 PM, Stacy (Google) wrote: We’ve just released a new self service HRD migration tool. This tool copies all of your data to HRD minimizing read-only times by using a multi-phase approach. Please see the documentation for details on how to use this. This tool is still considered experimental, please report problems you experience here in the forum or to the external issue tracker.We are still working on solutions for users of blobstore. Using HRD makes your app eligible for our SLA, and will lead to much better availability and more consistent performance. We think every app will benefit from the switch to HRD. Stacy -- 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/-/RzmZ--blDgIJ. 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. -- 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. -- 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] HRD migration tool now available!
Guess I know what I'll be doing on my day off tomorrow. In case anyone didn't notice this in the docs: Currently, the HRD Migration Tool does not support copying data from Blobstore. If you use Blobstore, you need to manually copy that data over. Ugh. That's a pretty huge hole in the tool. Perhaps I know what I'll be doing all weekend… -Joshua On Nov 9, 2011, at 4:33 PM, Stacy (Google) wrote: We’ve just released a new self service HRD migration tool. This tool copies all of your data to HRD minimizing read-only times by using a multi-phase approach. Please see the documentation for details on how to use this. This tool is still considered experimental, please report problems you experience here in the forum or to the external issue tracker.We are still working on solutions for users of blobstore. Using HRD makes your app eligible for our SLA, and will lead to much better availability and more consistent performance. We think every app will benefit from the switch to HRD. Stacy -- 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/-/RzmZ--blDgIJ. 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.
[google-appengine] HRD migration tool now available!
We’ve just released a new self service HRD migration tool. This tool copies all of your data to HRD minimizing read-only times by using a multi-phase approach. Please see the documentationhttp://code.google.com/appengine/docs/adminconsole/applicationsettings.html#Migrate_from_Master/Slave_to_High_Replication_Datastorefor details on how to use this. This tool is still considered experimental, please report problems you experience here in the forum or to the external issue tracker.We are still working on solutions for users of blobstore. Using HRD makes your app eligible for our SLA, and will lead to much better availability and more consistent performance. We think every app will benefit from the switch to HRD. Stacy -- 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/-/RzmZ--blDgIJ. 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.
