Re: [google-appengine] Re: App Engine to Compute Engine communication via internal IP

Agreed, this would be very helpful. This would serve as a poor mans cloud functions until they get python and internal access. Looking for this on the Flexible environment. Den fredag 9 mars 2018 kl. 12:48:56 UTC+1 skrev Daniel Florey: > > Any news? I've spend a lot of time to find information

Re: [google-appengine] Re: App Engine to Compute Engine communication via internal IP

Any news? I've spend a lot of time to find information on how to access Compute Engine vial URLFetch from App Engine standard using internal IP. Is this simply not possible (yet)? On Thursday, June 29, 2017 at 2:19:49 AM UTC+2, Lorne Kligerman wrote: > > Not just yet. We'll let you know when

[google-appengine] Re: App Engine to Compute Engine communication via internal IP

Hi, Adam. I have tried using flexible instance to connect to a container engine which I created an internal load balancer. But this unfortunately does not work. (External load balancer does work.) Is there anyone could suggest? A detailed description of my troubleshooting process is posted here

Re: [google-appengine] Re: App Engine to Compute Engine communication via internal IP

Not just yet. We'll let you know when we're ready for early tests. Thanks! On Wed, Jun 28, 2017 at 3:07 PM, Robert Dyas wrote: > Now that GAE Std Java 8 is in beta, is there any update on when this might > become available for testing? > > On Wednesday, January 4, 2017

[google-appengine] Re: App Engine to Compute Engine communication via internal IP

Now that GAE Std Java 8 is in beta, is there any update on when this might become available for testing? On Wednesday, January 4, 2017 at 1:25:40 PM UTC-5, Lorne Kligerman wrote: > > As Adam mentioned, this is only possible right now with the flex. However > we do know this is a problem and

[google-appengine] Re: App Engine to Compute Engine communication via internal IP

Hey Lorne, thanks for the information. I have a "standard" instance and I'm migrating to "flex" in order to be able to open direct connections to a Kubernetes cluster. Good to know that this should work! On Wednesday, January 4, 2017 at 10:25:40 AM UTC-8, Lorne Kligerman wrote: > > As Adam

[google-appengine] Re: App Engine to Compute Engine communication via internal IP

Being able to have App Engine standard access my GCE instances via their internal IP addresses would help us greatly. Hopefully this will also solve some of the speed/latency issues between App Engine standard and GCE resources. On Wednesday, January 4, 2017 at 1:25:40 PM UTC-5, Lorne

[google-appengine] Re: App Engine to Compute Engine communication via internal IP

As Adam mentioned, this is only possible right now with the flex. However we do know this is a problem and are working towards a solution for standard, nothing more to report at this time. On Friday, December 30, 2016 at 1:53:53 PM UTC-8, Nick (Cloud Platform Support) wrote: > > Hey Jitenda,

[google-appengine] Re: App Engine to Compute Engine communication via internal IP

Hey Jitenda, The Flexible Environment can be used by any user, although of course being a beta product, it isn't covered by the same SLA's as other products. You should check our documentation including the terms of service , service level agreements

[google-appengine] Re: App Engine to Compute Engine communication via internal IP

Thanks Adam for your answer , But as per this documentation App Engine flexible environment is still in beta release , can it be used in production ? On Saturday, June 25, 2016 at 2:38:46 AM UTC+5:30, Adam (Cloud Platform Support) wrote: > >

[google-appengine] Re: App Engine to Compute Engine communication via internal IP

You should be able to do this if you use a Flexible Environment instance, and specify the same network name in the app.yaml that your Compute Engine instance running MySQL is on. It