Re: [google-appengine] Re: need to connect App Engine Std to GCE via internal IP address

2017-04-24 Thread 'Lorne Kligerman' via Google App Engine
Understood, thanks for the write up! On Mon, Apr 24, 2017 at 4:45 PM, Robert Dyas wrote: > Yes, but in addition to that consider it a feature request that the > incoming IP address from GAE std to GCE will be easily identifiable (or a > range). The reason for this is

Re: [google-appengine] Re: need to connect App Engine Std to GCE via internal IP address

2017-04-24 Thread Robert Dyas
Yes, but in addition to that consider it a feature request that the incoming IP address from GAE std to GCE will be easily identifiable (or a range). The reason for this is we have some servers that will still be accepting requests over their external IP that will be required to be encrypted,

Re: [google-appengine] Re: need to connect App Engine Std to GCE via internal IP address

2017-04-24 Thread 'Lorne Kligerman' via Google App Engine
More details to come, however we will provide a mechanism to be sure that only your App Engine app can connect to your own GCE VMs. On Mon, Apr 24, 2017 at 1:41 PM, Robert Dyas wrote: > Question: will the IP address from App Engine Std appear as though its on > the

[google-appengine] Re: need to connect App Engine Std to GCE via internal IP address

2017-04-24 Thread Robert Dyas
Question: will the IP address from App Engine Std appear as though its on the internal GCE network? Hopefully yes so that its easy to filter incoming requests as coming from a trusted source or not. On Sunday, April 23, 2017 at 5:27:25 PM UTC-4, Lorne Kligerman wrote: > > Hey folks, > > I'm

[google-appengine] Re: need to connect App Engine Std to GCE via internal IP address

2017-04-23 Thread Robert Dyas
That's great news! It can't come too soon! On Sunday, April 23, 2017 at 5:27:25 PM UTC-4, Lorne Kligerman wrote: > > Hey folks, > > I'm glad to report that this is something that we're actively working on! > Nothing to report at the moment on timing but when ready for some testing > I'll be sure

[google-appengine] Re: need to connect App Engine Std to GCE via internal IP address

2017-04-23 Thread 'Lorne Kligerman' via Google App Engine
Hey folks, I'm glad to report that this is something that we're actively working on! Nothing to report at the moment on timing but when ready for some testing I'll be sure to send a note here. Stay tuned! Cheers, Lorne. Product Manager - App Engine On Saturday, April 22, 2017 at 7:15:31 AM

[google-appengine] Re: need to connect App Engine Std to GCE via internal IP address

2017-04-22 Thread Robert Dyas
Yep, that helps. Thank you. I also bet that if you ran a test connecting over a 7 day period you would see lots of times where that ~200-400ms becomes ~1,000 to ~2,000+ms. When I run this same test machine-2-machine using the internal IP addresses on GCE, the time is close enough to zero that

[google-appengine] Re: need to connect App Engine Std to GCE via internal IP address

2017-04-22 Thread Evan Jones
I just took a quick look at the trace viewer for ~5 requests. It looks like sending/receiving data on an existing connection takes around 1-5 ms for the Send and Receive calls. For creating a new connection: I see times like: CreateSocket: 3-5 ms Resolve: 1 ms Connect: 2-12 ms ... a whole

[google-appengine] Re: need to connect App Engine Std to GCE via internal IP address

2017-04-21 Thread Robert Dyas
Do you have any idea how much slower creating a new connection is? This is probably our issue. We don't use connection pooling currently as each user is logged in to the db with their own credentials (ERP type app), but it might be worth exploring if the pooling and driver can handle that. It

[google-appengine] Re: need to connect App Engine Std to GCE via internal IP address

2017-04-19 Thread Evan Jones
My understanding is that App Engine Standard can only talk to things that are accessible via a "public" Internet IP address, so I'm not sure I'm going to be able to provide any magic suggestions. However, I will mention that in our experience we can get "reasonable" latency. In particular, we