[google-appengine] Re: Old versions of Managed VMs

[Michael Sander]

Just ran into this issue today, and noticed that as of 3/9/2016 it was 
fixed. Time to do a "gcloud components update"

On Monday, October 5, 2015 at 12:39:29 PM UTC-4, Michael Spainhower wrote:
>
> Ah, found the answer myself in the gcloud release notes at 
> https://dl.google.com/dl/cloudsdk/release/RELEASE_NOTES
>
> In a future Cloud SDK release, deployments that promote the new version
>>   to receive all traffic will stop the previous version by default.
>>
>>
> Great to hear.  Thanks! 
>
> On Sunday, October 4, 2015 at 4:02:29 PM UTC-4, Michael Spainhower wrote:
>>
>> Could anyone from Google comment on whether there is a plan to fix this 
>> issue?  Versions that are not getting traffic really shouldn't have 
>> instances constantly running.  Only using (and paying for) the resources 
>> that you really need and use is one of the key value props of Google Cloud 
>> and GAE.
>>
>> On Tuesday, September 15, 2015 at 7:15:10 PM UTC-4, 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 https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/2be9a93c-4762-415b-833e-d690053d2ee5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Old versions of Managed VMs

[Christian F. Howes]

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.

[google-appengine] Re: Old versions of Managed VMs

[Michael Spainhower]

I am using managed vms and also have the issue of non-default versions 
running residual instances.  However, I do not experience the issue you 
have described where the instances remain even after deleting the 
non-default versions.

Are you using a standard runtime or custom runtime 
(https://cloud.google.com/appengine/docs/managed-vms/#runtimes)?  The 
lifecycle (shutdown) request handling seems like a potential culprit, so 
that may be worth examining if you are using a custom runtime.  I am using 
a node custom Dockerfile and my app just returns a 200 on requests to `
/_ah/stop` 
(https://github.com/home-buddy/express-appengine-handlers/blob/master/index.js#L18).
 
 You can probably check your logs for requests to that URL to see if there 
are non-200 responses.

What version of the gcloud cli tool are you running?  While potentially 
unrelated to this issue, you may want to update it because I do not think 
`--remote` is an option anymore (implying you may need an update).

As an aside, I would love guidance on fixing the issue where every 
non-default version has instances running.  Perhaps this is the expected 
behavior since managed VMs is labeled as beta?

On Tuesday, September 15, 2015 at 7:15:10 PM UTC-4, 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/7779690b-5a1a-41df-8bdc-2c179daab1e1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Old versions of Managed VMs

[Jeff Schnitzer]

Interesting. Maybe I just didn't wait long enough after deleting the
nondefault versions.

Still, it's a small surprise that I have to prune old versions. With normal
GAE, I leave those versions around so I can go back through the logs when
necessary.

Jeff

On Wed, Sep 16, 2015 at 1:03 PM, Michael Spainhower 
wrote:

> I am using managed vms and also have the issue of non-default versions
> running residual instances.  However, I do not experience the issue you
> have described where the instances remain even after deleting the
> non-default versions.
>
> Are you using a standard runtime or custom runtime (
> https://cloud.google.com/appengine/docs/managed-vms/#runtimes)?  The
> lifecycle (shutdown) request handling seems like a potential culprit, so
> that may be worth examining if you are using a custom runtime.  I am using
> a node custom Dockerfile and my app just returns a 200 on requests to `
> /_ah/stop` (
> https://github.com/home-buddy/express-appengine-handlers/blob/master/index.js#L18).
> You can probably check your logs for requests to that URL to see if there
> are non-200 responses.
>
> What version of the gcloud cli tool are you running?  While potentially
> unrelated to this issue, you may want to update it because I do not think
> `--remote` is an option anymore (implying you may need an update).
>
> As an aside, I would love guidance on fixing the issue where every
> non-default version has instances running.  Perhaps this is the expected
> behavior since managed VMs is labeled as beta?
>
>
> On Tuesday, September 15, 2015 at 7:15:10 PM UTC-4, 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/CADK-0uhr%2BW9yrN14nv%2BUWLgcFPzft4x7x0xxSoSd9ns6BVJuhQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Old versions of Managed VMs

[Jason Collins]

Jeff, there is a tiny switch in the legacy console Versions tab that allows 
you to "stop" a managed VM. I believe this will delete the underlying VMs 
while still keeping your version and logs around. Big gotcha: you need to 
manually re-"start" the version to serve any traffic (regardless of your 
scaling configuration) - this has tripped me up a number of times.





I have not found the equivalent button in the new console, so I don't know 
how you'd achieve same there.

Also, this is still a rapidly evolving feature, so this advice is seriously 
time-limited! ;)

j


On Wednesday, 16 September 2015 14:05:58 UTC-7, Jeff Schnitzer wrote:
>
> Interesting. Maybe I just didn't wait long enough after deleting the 
> nondefault versions.
>
> Still, it's a small surprise that I have to prune old versions. With 
> normal GAE, I leave those versions around so I can go back through the logs 
> when necessary.
>
> Jeff
>
> On Wed, Sep 16, 2015 at 1:03 PM, Michael Spainhower  > wrote:
>
>> I am using managed vms and also have the issue of non-default versions 
>> running residual instances.  However, I do not experience the issue you 
>> have described where the instances remain even after deleting the 
>> non-default versions.
>>
>> Are you using a standard runtime or custom runtime (
>> https://cloud.google.com/appengine/docs/managed-vms/#runtimes)?  The 
>> lifecycle (shutdown) request handling seems like a potential culprit, so 
>> that may be worth examining if you are using a custom runtime.  I am using 
>> a node custom Dockerfile and my app just returns a 200 on requests to `
>> /_ah/stop` (
>> https://github.com/home-buddy/express-appengine-handlers/blob/master/index.js#L18).
>>   
>> You can probably check your logs for requests to that URL to see if there 
>> are non-200 responses.
>>
>> What version of the gcloud cli tool are you running?  While potentially 
>> unrelated to this issue, you may want to update it because I do not think 
>> `--remote` is an option anymore (implying you may need an update).
>>
>> As an aside, I would love guidance on fixing the issue where every 
>> non-default version has instances running.  Perhaps this is the expected 
>> behavior since managed VMs is labeled as beta?
>>
>>
>> On Tuesday, September 15, 2015 at 7:15:10 PM UTC-4, 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/e69f4b39-b1f2-495f-9aa2-6b862b2a8faa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Old versions of Managed VMs

[Michael Spainhower]

Could anyone from Google comment on whether there is a plan to fix this 
issue?  Versions that are not getting traffic really shouldn't have 
instances constantly running.  Only using (and paying for) the resources 
that you really need and use is one of the key value props of Google Cloud 
and GAE.

On Tuesday, September 15, 2015 at 7:15:10 PM UTC-4, 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/853b7998-fa21-4a65-a6a7-4a19dc778c5a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Old versions of Managed VMs

[Michael Spainhower]

Ah, found the answer myself in the gcloud release notes 
at https://dl.google.com/dl/cloudsdk/release/RELEASE_NOTES

In a future Cloud SDK release, deployments that promote the new version
>   to receive all traffic will stop the previous version by default.
>
>
Great to hear.  Thanks! 

On Sunday, October 4, 2015 at 4:02:29 PM UTC-4, Michael Spainhower wrote:
>
> Could anyone from Google comment on whether there is a plan to fix this 
> issue?  Versions that are not getting traffic really shouldn't have 
> instances constantly running.  Only using (and paying for) the resources 
> that you really need and use is one of the key value props of Google Cloud 
> and GAE.
>
> On Tuesday, September 15, 2015 at 7:15:10 PM UTC-4, 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/4bcd8f06-9c00-45b4-b831-d0fb7ae67a89%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.