Re: [google-appengine] Google Cloud Platform wants to hear from you

[Aleem Mawani]

On Tue, Apr 28, 2015 at 10:03 PM 'Chris Ramsdale' via Google App Engine <
google-appengine@googlegroups.com> wrote:

> excellent feedback.  some comments inline below.
>
> On Thu, Apr 23, 2015 at 3:09 PM, 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)
>>
>
> a fix for this is in the works.  i'll come back with a date.
>
thanks!

>
>
>>
>> 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
>>
>
> have you looked into the Firebase API set?  would that work for you or is
> there some deficiency?
>
Looked into it briefly, but two things concern me:
1) Firebase is designed to synchronize state across several clients and
does a great job of this. But you kind of have to shoehorn in message
passing. So if your app is already built using the channel api which is
more message based, moving to firebase is a little awkward. For a new app
this might be less of a problem. I've heard rumblings about firebase +
datastore but I'm suspicious that could work well (if every client needs to
provide a list of entities it would like to subscribe to, this is non
trivial) for us at least.

2) Its far more expensive than channel API since its based on number of
"connections". We'd blow through their highest tiered plan and likely
increase our monthly bills by double digit percentages.

If channel API is going away, the natural replacement seems to be GCM if it
supported web clients.

>
>
>> - logging api: we use this to export our logs to BQ
>>
>
> slightly related to my point above, our goal is to enable this via Google
> Cloud Logging.  have you taken a look at their integration with BQ?
>

Its good, but we need to process logs before sending to bigquery. We'd like
to implement a Cloud Logginng -> PubSub -> Dataflow -> Bigquery  workflow
which would remove the need for us to even use GAE insances to get logs to
BQ but the Cloud Logging -> PubSub is the missing piece that isn't
available yet. Neither is the Logging API on Managed VMs so we're left with
using vanilla GAE instances to do background log processing.

>
>
>>
>> 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
>>
>
> good feedback, and i've passed this on to the Cloud monitoring folks.
>
is the plan for cloud monitoring to replace GAE dashboard. Or for the
dashboard to show instance counts of managed vms? I.e. where should we get
this data?

>
>
>> - seemed that instances would go into unhealthy state and not recover or
>> get killed (this could be outdated)
>>
>
> there have been several changes submitted to address this issue.  please
> do let me know if you are still seeing this issue.
>
will do.

>
>
Thanks for all the responses!

>
>>
>> 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  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 

[google-appengine] pdf in iframes

[p_niemann]

I am having trouble with GAE and report generation.
Is there a way to put a pdf file in an html iframe?
If this is not possible is there a way to convert a pdf to an image so the 
image can be put in an html iframe?



-- 
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/877ab14e-0caa-483c-8c41-630b4be26034%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Google Cloud Platform wants to hear from you

['Chris Ramsdale' via Google App Engine]

excellent feedback.  some comments inline below.

On Thu, Apr 23, 2015 at 3:09 PM, 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)
>

a fix for this is in the works.  i'll come back with a date.


>
> 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
>

have you looked into the Firebase API set?  would that work for you or is
there some deficiency?


> - logging api: we use this to export our logs to BQ
>

slightly related to my point above, our goal is to enable this via Google
Cloud Logging.  have you taken a look at their integration with 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
>

good feedback, and i've passed this on to the Cloud monitoring folks.


> - seemed that instances would go into unhealthy state and not recover or
> get killed (this could be outdated)
>

there have been several changes submitted to address this issue.  please do
let me know if you are still seeing this issue.


>
>
> 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  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  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
> 

Re: [google-appengine] Unable to connect application

[Madan Nirmalraj]

To be honest, I have no idea. I'm not a "computer" guy. But I did just
create a support ticket on my cloud service account.

How can I find what you are asking for?

On Tuesday, April 28, 2015, Chad Vincent  wrote:

> What is in the AppEngine logs for the blank page requests?  Anything?
>
> On Monday, April 27, 2015 at 3:43:04 PM UTC-5, Madan Nirmalraj wrote:
>>
>>
>> My team of developers has run into an issue after trying to push the app
>> code to Google. Below are details from one engineer regarding the problem:
>>
>> Initially, we have created a web application build using *Google App
>> Engine* in our local environment and application worked fine. When
>> deployed to "Production", we are faced issues in retrieving methods.
>>
>> Here are the steps which we followed to move web application into cloud.
>>
>>1. We have created "APP ID" for cloud SQL
>>2. Installed Google App Engine.
>>3. Connected to to Google Cloud from Google App engine.
>>4. New Project is created using Google App Engine.
>>5. All connections are given in "app.yaml" file (Suggested format
>>file by Google which works with app engine).
>>6. Worked fine in our local environment(Development) and we could run
>>the application successfully.
>>
>> When we deployed the files to "Production" server we were unable to
>> connect application. Showing an empty page. We observed that page
>> redirection is not working in live environment.
>>
>> In this regard, I wanted to check with you if there are any permissions
>> set on the server that is restricting us for page redirection. I also
>> wanted you to check with third party service provider (Google cloud) if
>> they can help us resolve the issue.
>>
>> What do you recommend?
>>
>> Thank you,
>>
>  --
> You received this message because you are subscribed to a topic in the
> Google Groups "Google App Engine" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/google-appengine/ti1QJxsJ3vc/unsubscribe
> .
> To unsubscribe from this group and all its topics, 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/5202a275-ec41-4bb6-883f-d7630c23850a%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thank you,

Madan Nirmalraj
Managing Member

3M Realty
8045 L Street
Omaha, NE 68127
402.630.1800

-- 
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/CAKUd7wPPrOGuTO%3DO7Ae0xqSE4go8S42Pn1e4q-CSJxFSDtDL%3Dg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Unable to connect application

[Chad Vincent]

What is in the AppEngine logs for the blank page requests?  Anything?

On Monday, April 27, 2015 at 3:43:04 PM UTC-5, Madan Nirmalraj wrote:
>
>
> My team of developers has run into an issue after trying to push the app 
> code to Google. Below are details from one engineer regarding the problem:
>
> Initially, we have created a web application build using *Google App 
> Engine* in our local environment and application worked fine. When 
> deployed to "Production", we are faced issues in retrieving methods. 
>
> Here are the steps which we followed to move web application into cloud. 
>
>1. We have created "APP ID" for cloud SQL
>2. Installed Google App Engine.
>3. Connected to to Google Cloud from Google App engine.
>4. New Project is created using Google App Engine.
>5. All connections are given in "app.yaml" file (Suggested format file 
>by Google which works with app engine).
>6. Worked fine in our local environment(Development) and we could run 
>the application successfully.
>
> When we deployed the files to "Production" server we were unable to 
> connect application. Showing an empty page. We observed that page 
> redirection is not working in live environment.
>
> In this regard, I wanted to check with you if there are any permissions 
> set on the server that is restricting us for page redirection. I also 
> wanted you to check with third party service provider (Google cloud) if 
> they can help us resolve the issue.
>
> What do you recommend?
>
> Thank you,
>

-- 
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/5202a275-ec41-4bb6-883f-d7630c23850a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] App Engine + Maven + Hot swap of war

[Carl Emmoth]

Hello,

so is it possible to run maven devserver (mvn appengine:devserver) and have 
live hot swap for any changes in war dir?

Like, if I change index.html with new text and refresh in browser, can it 
update?

It seems like fullScanSeconds only updates Java classes.

Thanks,
Carl

-- 
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/4ed768ed-a3a3-469c-96df-34fa6566b826%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.