My company have been on appengine over 4-5 years now. We use namespaces a lot, for organising the users data. Better namespaces support in all tools and utilities After the backup, able to selectively restore the namespace data, to another appid Easy Export of namespace data to Google spreadsheet Datastore viewer (both new and old) needs lot of improvement. It is difficult to navigate the data and correct the data. For example, the list property data cannot be edited in the datastore viewer
Currently, mapreduce is only the framework for processing/migrating the data. This opensource project should have more documentation and examples. Again, there is lack of namespaces examples and lack of documentation on the namespaces. Rajesh www.AccountingGuru.net Accounting/Inventory/Billing on Google Cloud Platform. On Friday, April 24, 2015 at 3:39:29 AM UTC+5:30, Aleem Mawani wrote: > > @chris, thanks for asking, > > 1) Sorry I might have had some confusion here, I thought traffic > splitting/traffic migration didn't work for managed VM's but it in fact it > doesn't work for any non-default module. We haven't yet tried to put our > default module on managed vms because of stability concerns (may be > outdated) and the api's listed below) > > 2) Re: APIs, we can't yet do the following in Managed VM's: > > - channel api: we use this to send realtime notifications to web/mobile > clients > - logging api: we use this to export our logs to BQ > > 3) The other things preventing us from moving default module over to > managed vms: > > - cloud console dashboard doesn't show a lot of the aggregate metrics for > a managed vm module, most importantly instance count over time. > - cloud monitoring can't monitor managed vm instance count > - seemed that instances would go into unhealthy state and not recover or > get killed (this could be outdated) > > > At the current moment there seems to be no major concerns with managed > VM's (except for the things you're working on like startup time and deploy > time and dev experience) but there are dozens of tiny gotchas which > individually don't seem like much but together are a big enough deal that > we don't serve front end traffic over it. > > For background processing the value is so high that we've moved all of our > backend modules to managed vms (unless they need any of the above API's). > > On Thursday, April 23, 2015 at 2:24:59 PM UTC-7, Chris Ramsdale wrote: >> >> yes, the goal is to get App Engine Managed VMs (v2) to a state where they >> are ideal for frontend serving. couple of questions for you: >> >> (1) is traffic splitting and deploy-to-a-default-module not working for >> you? >> (2) re: APIs, which ones would you like to see enabled? you mentioned >> logging (and the goal is to move App Engine Logging API over to Google >> Cloud Logging all-up), but what else are you looking for? >> >> -- Chris >> >> On Thu, Apr 23, 2015 at 11:47 AM, Aleem Mawani <al...@streak.com> wrote: >> >>> Chris - with the improvements you're suggesting to Managed VMs (20 sec >>> deploys, <1 sec instance startup time) - will it be recommended to use >>> Managed VMs to serve frontend traffic? Right now they seem to be more >>> targetted to backend processing because of the slow scaling. >>> >>> If this is true, and you are targeting it to serve front end traffic, >>> does that mean we'll be able to deploy Managed VMs to our default modules, >>> perform traffic splitting, access the logging api's and realtime api's, >>> etc? These are the things that have been traditionally missing from managed >>> vms. >>> >>> On Wednesday, April 22, 2015 at 10:33:46 AM UTC-7, Chris Ramsdale wrote: >>>> >>>> >>>> >>>> On Wed, Apr 22, 2015 at 2:21 AM, troberti <tij...@firigames.com> wrote: >>>> >>>>> What a flurry of activity. :) Great to see. >>>>> >>>>> I have been using GCP( App Engine + BigQuery) in total for over 5 >>>>> years, so not new, but I have seen plenty of new users make mistakes so >>>>> let >>>>> me chime in a bit: >>>>> >>>>> On App Engine (and GCP) there are a lot of ways to approach a problem, >>>>> with the consequence that is very easy to choose the wrong solution. >>>>> There >>>>> is actually a rather steep learning curve to just know what is available. >>>>> >>>>> This is a problem, because the differences between various solutions >>>>> can result in an order of magnitude difference in >>>>> costs/latency/complexity >>>>> etc. I stopped counting the amount of times I have seen models with every >>>>> property indexed, resulting in huge datastore costs. Or where someone >>>>> tries >>>>> to put tons of data in the Datastore while BigQuery would be a much >>>>> better >>>>> fit for the problem. Every time this happens, the new user ends up >>>>> disappointed. So guiding new users in the right direction when starting >>>>> out >>>>> on GCP seems very important. >>>>> >>>>> I agree with a lot in Karl's post, and especially the Roadmap. It >>>>> doesn't need to be about features, but big ticket items like Python 3, >>>>> Java >>>>> 8, SSL etc should be communicated. It doesn't have to be an explicit list >>>>> somewhere, just a PM chiming in regularly should be good enough. >>>>> >>>>> Now back to App Engine: >>>>> >>>>> Like I said in my post on the other thread >>>>> <https://cloud.google.com/appengine/forum/?place=msg%2Fgoogle-appengine%2FqTyc2E-0IXc%2FPxUzFMXhzjQJ>, >>>>> >>>>> the trend towards managed VMs worries me a bit. For us, >>>>> zero-configuration/no-maintenance is not just another feature of App >>>>> Engine, it is one of the most important ones! We want to write our >>>>> programs >>>>> and then keep them running for years (5+) without having to do >>>>> *anything*. >>>>> Some of our apps are running like this for years now, and I want to >>>>> ensure >>>>> that this stays possible in the future. >>>>> >>>> >>>> Managed VMs represent a new hosting environment that brings with it a >>>> set of feature benefits -- open source compatible runtimes, more CPU / >>>> memory configurations, access to native resources such as a file system >>>> and >>>> network stack. we'll be investing in this environment more and more over >>>> the coming months (we're ripping docker out of the getting started flow, >>>> getting deployment times to <20 secs, getting instance activation time to >>>> <1 sec, adding scale to/from zero instances, etc.) that said, don't >>>> worry, >>>> we'll absolutely keep your existing v1 apps running just as they have for >>>> years. >>>> >>>> >>>>> >>>>> Glad to see the Docker fad go, but please don't replace it with >>>>> something where I need to choose my "technology stack" in some way. Just >>>>> provide a set of stable APIs instead so we can consider everything else >>>>> an >>>>> implementation detail for App Engine to worry about :) >>>>> >>>> >>>> exactly. if anything, we're going to make those same APIs available >>>> from other compute environments (e.g. Compute Engine and Container Engine). >>>> >>>> >>>>> >>>>> On Wednesday, April 22, 2015 at 8:31:47 AM UTC+2, Chris Ramsdale wrote: >>>>>> >>>>>> >>>>>> >>>>>> On Tue, Apr 21, 2015 at 11:22 PM, Vinny P <vinn...@gmail.com> wrote: >>>>>> >>>>>>> Hi Katie, >>>>>>> >>>>>>> I think Karl's post hit a home run and I'm happy to see the positive >>>>>>> response to his post. Let me just tack on a few items: >>>>>>> >>>>>>> >>>>>>> *Managed VMs:* The development toolchain for Managed VMs can be a >>>>>>> bit finicky. To be quite honest I have no idea how I got Managed VMs >>>>>>> working on my laptop. Streamlining this would be a huge benefit to me, >>>>>>> and >>>>>>> probably a lot of first-timers. If you can convince one of the online >>>>>>> IDE >>>>>>> services to simplify creating Managed VM GAE apps, that would be super. >>>>>>> >>>>>>> For smaller or toy apps within Managed VMs: I shouldn't need to care >>>>>>> about the Docker container running the application; I should be able to >>>>>>> create an application using just Eclipse + Google Plugin, then be able >>>>>>> to >>>>>>> deploy straight to a Managed VM runtime *without* the intermediate >>>>>>> step of having gcloud create and store a dockerfile >>>>>>> <https://cloud.google.com/appengine/docs/managed-vms/tutorial/step2#dockerfile> >>>>>>> . >>>>>>> >>>>>> >>>>>> We're removing the Docker toolchain from the mix and will be >>>>>> surfacing a hosted build service that handles this on your behalf. >>>>>> Their >>>>>> toolchain is simply unstable. >>>>>> >>>>>> >>>>>>> >>>>>>> *Firebase:* I'm glad that Google bought up Firebase - they have a >>>>>>> lot of great ideas and a well-designed API. I'd like to see Firebase >>>>>>> with >>>>>>> the ability to use the Datastore and Cloud SQL directly, not just the >>>>>>> regular Firebase DB. This would help with syncing information with >>>>>>> server >>>>>>> side systems. >>>>>>> >>>>>> >>>>>> They have a great Dev UX and we're working to further integrate them >>>>>> with Google Cloud Platform. >>>>>> >>>>>> >>>>>>> >>>>>>> *Stack Overflow:* IMO, the moderators at SO go overboard when >>>>>>> locking questions. I often find interesting SO pages when I'm searching >>>>>>> around, only to visit the page and find that the question is locked or >>>>>>> that >>>>>>> someone has deleted the page outright. At least with the mailing list I >>>>>>> have an archive of all past questions and answers in my email account. >>>>>>> I >>>>>>> don't know how you plan on using SO going forward, but I would >>>>>>> appreciate >>>>>>> minimizing any occurrences of locked/deleted questions. >>>>>>> >>>>>> >>>>>> Excellent feedback, and we'll discuss this internally. >>>>>> >>>>>> >>>>>>> >>>>>>> Thanks >>>>>>> >>>>>>> P.S. When you're giving out the support vouchers, please skip me. >>>>>>> There are a number of far more deserving people in this thread. >>>>>>> >>>>>>> ----------------- >>>>>>> -Vinny P >>>>>>> Technology & Media Consultant >>>>>>> Chicago, IL >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Wed, Apr 15, 2015 at 12:35 PM, Katie Ball (Google Cloud Support) >>>>>>> <kmrich...@google.com> wrote: >>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> My name is Katie, and I am on the Google Cloud Platform technical >>>>>>>> support <http://cloud.google.com/support> team. >>>>>>>> >>>>>>>> This message is to Google Cloud Platform community members, >>>>>>>> especially if you are newer to GCP. I would like to know what our team >>>>>>>> can >>>>>>>> do to help you have a better and more enjoyable experience during the >>>>>>>> first >>>>>>>> days on GCP. >>>>>>>> >>>>>>>> Did you need technical support? If so, I’d like to hear all about >>>>>>>> it. >>>>>>>> >>>>>>>> I’d also like to know: >>>>>>>> >>>>>>>> - >>>>>>>> >>>>>>>> What did you find most difficult about the first-time user >>>>>>>> experience? >>>>>>>> - >>>>>>>> >>>>>>>> Where did you get stuck? >>>>>>>> >>>>>>>> >>>>>>>> Please reply to the group with your answers or any ideas you have >>>>>>>> on how the technical support team can help new customers get familiar >>>>>>>> with >>>>>>>> GCP. >>>>>>>> >>>>>>>> And as a thank you for the great ideas, we will be giving away >>>>>>>> support coupons worth $450 (equivalent to 3 months of silver support) >>>>>>>> to 5 >>>>>>>> lucky community members who post a response. Please make sure to reply >>>>>>>> before April 22nd. >>>>>>>> >>>>>>>> Thanks for your insights, and cloud on! >>>>>>>> >>>>>>>> Katie >>>>>>>> >>>>>>>> -- >>>>>>>> You received this message because you are subscribed to the Google >>>>>>>> Groups "Google App Engine" group. >>>>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>>>> send an email to google-appengi...@googlegroups.com. >>>>>>>> To post to this group, send email to google-a...@googlegroups.com. >>>>>>>> Visit this group at http://groups.google.com/group/google-appengine >>>>>>>> . >>>>>>>> To view this discussion on the web visit >>>>>>>> https://groups.google.com/d/msgid/google-appengine/4f59c819-731f-422c-b33d-a68ea4d525fd%40googlegroups.com >>>>>>>> >>>>>>>> <https://groups.google.com/d/msgid/google-appengine/4f59c819-731f-422c-b33d-a68ea4d525fd%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>>>>> . >>>>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>>>> >>>>>>> >>>>>>> -- >>>>>>> You received this message because you are subscribed to the Google >>>>>>> Groups "Google App Engine" group. >>>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>>> send an email to google-appengi...@googlegroups.com. >>>>>>> To post to this group, send email to google-a...@googlegroups.com. >>>>>>> Visit this group at http://groups.google.com/group/google-appengine. >>>>>>> To view this discussion on the web visit >>>>>>> https://groups.google.com/d/msgid/google-appengine/CALSvALCyL0SC6mdVkZjmZEuoOWTc0EaAx0aJJtbowGguqyNRXw%40mail.gmail.com >>>>>>> >>>>>>> <https://groups.google.com/d/msgid/google-appengine/CALSvALCyL0SC6mdVkZjmZEuoOWTc0EaAx0aJJtbowGguqyNRXw%40mail.gmail.com?utm_medium=email&utm_source=footer> >>>>>>> . >>>>>>> >>>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>>> >>>>>> >>>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "Google App Engine" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to google-appengi...@googlegroups.com. >>>>> To post to this group, send email to google-a...@googlegroups.com. >>>>> Visit this group at http://groups.google.com/group/google-appengine. >>>>> To view this discussion on the web visit >>>>> https://groups.google.com/d/msgid/google-appengine/2281cf70-b81b-46ce-ab78-b6cbe0c1f813%40googlegroups.com >>>>> >>>>> <https://groups.google.com/d/msgid/google-appengine/2281cf70-b81b-46ce-ab78-b6cbe0c1f813%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>> . >>>>> >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> >>>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Google App Engine" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to google-appengi...@googlegroups.com. >>> To post to this group, send email to google-a...@googlegroups.com. >>> Visit this group at http://groups.google.com/group/google-appengine. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/google-appengine/fcb86987-5dc0-4c98-b29d-56268f041ae6%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/google-appengine/fcb86987-5dc0-4c98-b29d-56268f041ae6%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/ec54a339-951b-48ce-ab0a-b7fcad535e56%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
