Hi Jeff, >From what i can see managed VMs behave much like app engine modules that use backend instance class and manual scaling - which means they stay live when you deploy a new version, and even after setting default.
I'm still using the "old" app engine console, and when i delete an old managed VM instance (or even click the stop link) it will shut down. It does take longer then for an app engine instance - sometimes 10-15mins, but i think that has to do with the managed VM health-check timing and shutdown process (or perhaps i just have mis-implemented my shutdown handlers on my managed VMs). I hope that helps. Christian On Tuesday, September 15, 2015 at 4:15:10 PM UTC-7, Jeff Schnitzer wrote: > > I have a python app on a Managed VM which I deploy with: > > gcloud preview app deploy app.yaml --remote --set-default > > It's set to manual scaling, instances 1. > > It appears that every time I deploy it, the old instance stick around (and > get billed for). Even deleting the old versions from the appengine console > didn't shut down the compute engine instances. I had to figure out which > compute engine instance was my "live" one and delete all the others from > the Compute Engine part of the console. > > Is this supposed to work this way or is there a better workflow? I just > want to deploy the new version and have the old version go away... like > regular App Engine. > > Jeff > -- 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/9d38ef2a-2b47-455c-aea4-23b423c06d42%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
