Any news on when will vm backends be available for all users?
--
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.
On Wednesday, March 26, 2014 8:04:41 AM UTC+8, Wesley C (Google) wrote:
@pdknsk: Correct, this feature has been announced publicly now so thanks
for sending a link to the developer docs. To see a summary of all the
exciting announcements we made today (2014 Mar 25), we suggest you check
https://developers.google.com/cloud/managed-vms
--
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
@pdknsk: Correct, this feature has been announced publicly now so thanks
for sending a link to the developer docs. To see a summary of all the
exciting announcements we made today (2014 Mar 25), we suggest you check
the
Could you provide datastore APIs for using on GCE without a GAE instance?
It would be great if it is possible.
On Friday, June 21, 2013 3:21:06 AM UTC+8, Takashi Matsuo (Google) wrote:
Fellow App Engine Gurus,
We're happy to announce the next generation of App Engine Managed
Backends.
Your narrative on VM-based Backends is* half-baked* without you commenting
on the short-comings of current Backends, and how those are solved by this
move.
On Thursday, June 20, 2013 9:21:06 PM UTC+2, Takashi Matsuo (Google) wrote:
Fellow App Engine Gurus,
We're happy to announce the next
Any news on general availability? I can't shake the impression of the App
Engine team being dormant.
--
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
On 4 February 2014 06:25, pdknsk pdk...@gmail.com wrote:
Any news on general availability? I can't shake the impression of the App
Engine team being dormant.
As usual, we don't specifically announce timelines ahead of time, but there
is an active group of early testers for the VM Runtime--
Thanks for the link it is really helpful for linux user
On Tuesday, December 3, 2013 11:13:48 AM UTC+5:30, pdknsk wrote:
Google Compute Engine is now Generally Available
http://googlecloudplatform.blogspot.de/2013/12/google-compute-engine-is-now-generally-available.html
Hurry! :)
--
You
Google Compute Engine is now Generally Available
http://googlecloudplatform.blogspot.de/2013/12/google-compute-engine-is-now-generally-available.html
Hurry! :)
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To unsubscribe from this group
dart vm's 2 ?
On Thursday, June 20, 2013 12:21:06 PM UTC-7, Takashi Matsuo (Google) wrote:
Fellow App Engine Gurus,
We're happy to announce the next generation of App Engine Managed
Backends. These Backends utilize the App Engine VM Runtime, allowing
developers to run Backends on Compute
Hi, I read that there is Java servlet 3.0 support? Could you give some more
hints on this? In which container (Jetty 8?) is it actually based? What EL
version is supported? Is CDI (weld) possible? Thanks!
Am Donnerstag, 20. Juni 2013 21:21:06 UTC+2 schrieb Takashi Matsuo (Google):
Fellow App
This allows us to run websockets however without auto-scaling is
worthless .
Thanks,
Mihai.
On Thursday, 20 June 2013 20:21:06 UTC+1, Takashi Matsuo (Google) wrote:
Fellow App Engine Gurus,
We're happy to announce the next generation of App Engine Managed
Backends. These Backends
Thanks Brian for letting us know.
On Tue, Sep 17, 2013 at 6:13 AM, Brian Tosch brian.to...@gmail.com wrote:
Sorry, missed it in my search but there was already an open issue 9950. I
indicated mine is a dupe but I don't think I can retract it.
On Monday, September 16, 2013 1:52:17 PM
Sorry, missed it in my search but there was already an open issue 9950. I
indicated mine is a dupe but I don't think I can retract it.
On Monday, September 16, 2013 1:52:17 PM UTC-7, Brian Tosch wrote:
I opened an issue for adding Go support.
I opened an issue for adding Go support.
https://code.google.com/p/googleappengine/issues/detail?id=9964
On Wednesday, August 28, 2013 10:44:03 PM UTC-7, Takashi Matsuo (Google)
wrote:
Hi Marcel,
Currently VM-based backends support Java and Python2.7.
I'd appreciate it if you could file
All PHP project owners, please star
https://code.google.com/p/googleappengine/issues/detail?id=9953 for
introducing support for PHP VMRuntime. Thanks
On Thursday, 29 August 2013 15:44:03 UTC+10, Takashi Matsuo (Google) wrote:
Hi Marcel,
Currently VM-based backends support Java and
What other options can you specify? This post points to the documentation,
the documentation just mentions other options can be set but doesn't say
what they are, unless I'm missing something.
Thank you,
Josh
On Thursday, June 20, 2013 2:21:06 PM UTC-5, Takashi Matsuo (Google) wrote:
Fellow
Hi Jeffery,
For restrictions, you are right. VM-based backends have only fewer
restrictions than the traditional App Engine backends.
Currently there's no public documentation. I hope these bullet points help
you understanding the difference.
- take advantage of higher CPU and memory
-
Hi Takashi,
Could you explain the differences between appengine backends and VM
backends? I am assuming VM backends don't have many restrictions as what
appengine does? Could you point me to some documentation or comparison
list? Thanks
On Thu, Aug 29, 2013 at 3:44 PM, Takashi Matsuo
Hi Marcel,
Currently VM-based backends support Java and Python2.7.
I'd appreciate it if you could file issues for supporting PHP and Go at:
https://code.google.com/p/googleappengine/issues/list?can=2q=Component%3DVMRuntime
I'd like to know how many people have interests in it.
Thanks for
Will those VM-based backends support all runtimes? So Java, Python and PHP?
-- Marcel
--
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
Manual scaling for a V1 launch, but we're looking into auto-scaling.
-- Chris
On Thu, Aug 8, 2013 at 1:47 AM, Andrew First and...@leanplum.com wrote:
This is great! Any plans to support autoscaling as well?
Andrew
On Thursday, June 20, 2013 12:21:06 PM UTC-7, Takashi Matsuo (Google)
This is great! Any plans to support autoscaling as well?
Andrew
On Thursday, June 20, 2013 12:21:06 PM UTC-7, Takashi Matsuo (Google) wrote:
Fellow App Engine Gurus,
We're happy to announce the next generation of App Engine Managed
Backends. These Backends utilize the App Engine VM
On Tue, Jun 25, 2013 at 10:50 AM, Kristopher Giesing kris.gies...@gmail.com
wrote:
PS : Now that we've got these great new backends and all the goodness of
BigQuery, CloudSQL, Datastore, ..., the only remaining evil problem in
the AppEngine world is the behavior of the dispatcher which sends
PS : Now that we've got these great new backends and all the goodness of
BigQuery, CloudSQL, Datastore, ..., the only remaining evil problem in
the AppEngine world is the behavior of the dispatcher which sends
user-facing requests to starting instances.
we have engineers dedicated to
This is a really exciting feature.
Will the durability of these backends look and feel more like GCE
(long-term / stable) or will the be more like GAE's current backends (flaky
and unstable)?
Robert
On Thursday, June 20, 2013 2:21:06 PM UTC-5, Takashi Matsuo (Google) wrote:
Fellow App
Hi Robert,
The VMs won't live forever, but definitely live long enough for the most
use-case. Generally there will be one periodic restart per weak.
-- Takashi
On Tue, Jun 25, 2013 at 9:33 PM, Robert Kluin robert.kl...@gmail.comwrote:
This is a really exciting feature.
Will the durability
That really is a great news !
And it is something that makes AppEngine so much simpler to use in
situation where we have to mix between PaaS and IaaS !
I've got one question regarding the billing :
- I assume this service will be billed as part of the AppEngine bill,
right ?
- Can
some comments inline below.
-- Chris
On Mon, Jun 24, 2013 at 7:59 AM, Nicolas Fonrose (Teevity)
nicolas.fonr...@teevity.com wrote:
That really is a great news !
And it is something that makes AppEngine so much simpler to use in
situation where we have to mix between PaaS and IaaS!
great
That is an absolutely positively excellent piece of news, Chris.
--
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
Thats pretty cool.
Just looked at the SQlite example for backend VM on python. It raises an
obvious question, what app server runtime are you running on the vm backend
to support a deployed python app.
Is it the new dev_appserver or something else ? What sort of concurrency
does it support ?
Hi Ray,
Re: cost
We're still discussing the cost, but the final shape of tariff won't be
very different from what you expect I think.
Re: memory
You can choose from a subset list of compute engine instance types.
-- Takashi
On Thu, Jun 20, 2013 at 5:54 PM, Ray windz...@gmail.com wrote:
Will
I just want to say WOW, this is amazing. I have long grumbled here that
backends, in their current form, are pretty useless. But this could change
that completely.
I also want to say that ever since Google announced Compute Engine and
started focusing on it at I/O, I've had the lingering fear
Hi Tim,
Yes it's cool, really. The reason I segment the sqlite guestbook into a
single instance is that there is no easy way to share the sqlite table on
the local disks between the instances. We run a multi-threaded server on
each instance. If you set threadsafe:true in the app.yaml file, the
How does this work on multi-core VMs I wonder. As far as I understand,
multi-threading here doesn't mean multi-processing, so each backend still
only runs on a single core.
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To unsubscribe
PS. It seems like for every great news, Google has sad news in store. It
appears that today Google has removed the option to revert to the old
Google Groups format. Oh well. Totally unrelated, I know.
--
You received this message because you are subscribed to the Google Groups
Google App
On Thursday, June 20, 2013 2:21:06 PM UTC-5, Takashi Matsuo (Google) wrote:
Fellow App Engine Gurus,
We're happy to announce the next generation of App Engine Managed
Backends. These Backends utilize the App Engine VM Runtime, allowing
developers to run Backends on Compute Engine VMs. By
re: multi-core, you can os.fork() in Python and
ForkJoinPoolshttp://docs.oracle.com/javase/7/docs/api/java/util/concurrent/ForkJoinPool.htmlin
Java.
re: Google Groups, we can only do so much :)
-- Chris
On Fri, Jun 21, 2013 at 12:58 PM, pdknsk pdk...@gmail.com wrote:
How does this work on
On Fri, Jun 21, 2013 at 2:58 PM, pdknsk pdk...@gmail.com wrote:
How does this work on multi-core VMs I wonder. As far as I understand,
multi-threading here doesn't mean multi-processing, so each backend still
only runs on a single core.
Be careful when using multiple cores within Java
Wow, this sounds quite fantastic if it works how I imagine it does.
Hopefully pricing is oriented more towards current GCE prices.
--
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
Will it cost like Compute Engine or it will cost like App Engine? (e.g. how
much are the memory?)
On Friday, June 21, 2013 3:21:06 AM UTC+8, Takashi Matsuo (Google) wrote:
Fellow App Engine Gurus,
We're happy to announce the next generation of App Engine Managed
Backends. These Backends
42 matches
Mail list logo
