<div dir="ltr">There is an expectation here. Is it explicitly optioned in the API? Should it be?<br><br>Should a suspended instance be immediately resumable?<div><br></div><div>If the expectation is that a suspended instance is resumable, then the claim against quota should be preserved, and the current behavior is correct.</div>
<div><br></div><div>If the expectation is that resources are released, the instance may *not* be immediately resumable, if quotas are exceeded.</div><div><br></div><div>Should this be an option, or unclaim-resources a distinct operation? Or is the present semantics all that is allowable?</div>
<div><br></div><div>(I am new to OpenStack, so I may have missed something.)</div><div><br></div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Jun 23, 2014 at 10:05 AM, Ricky Saltzer <span dir="ltr"><<a href="mailto:ricky@cloudera.com" target="_blank">ricky@cloudera.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>That seems to be the case, and I can see where you're coming from, but if the resources aren't released at the quota level, then they're effectively being used from a user's point of view. It would be nice if <i>suspend</i> released resources after the instance is shutdown, and a <i>resume</i> would reclaim the resources (provided enough are available). For instance, if I had 210/210 vCPUs used, and I suspend <i>instance_a</i> with 1 vCPU, and then launch <i>instance_b </i>with 1 vCPU...<i>instance_b </i>should successfully deploy, but resuming <i>instance_a</i> should fail with a quota exceeded exception.<br>
<br></div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Jun 23, 2014 at 12:54 PM, John Griffith <span dir="ltr"><<a href="mailto:john.griffith@solidfire.com" target="_blank">john.griffith@solidfire.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_default" style="font-family:courier new,monospace"><br></div><div class="gmail_extra">
<div><div><br><br><div class="gmail_quote">On Mon, Jun 23, 2014 at 10:49 AM, Ricky Saltzer <span dir="ltr"><<a href="mailto:ricky@cloudera.com" target="_blank">ricky@cloudera.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Right, the quotas don't seem to be released. If I have 210/210 vCPUs used, and I suspend an instance with 4 vCPUs, I still have 210/210 vCPUs used. <br>
</div><div class="gmail_extra"><div><div><br><br><div class="gmail_quote">
On Mon, Jun 23, 2014 at 11:38 AM, John Griffith <span dir="ltr"><<a href="mailto:john.griffith@solidfire.com" target="_blank">john.griffith@solidfire.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jun 23, 2014 at 7:45 AM, Ricky Saltzer <span dir="ltr"><<a href="mailto:ricky@cloudera.com" target="_blank">ricky@cloudera.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><a href="https://ask.openstack.org/en/question/32826/why-doesnt-suspend-release-vcpusmemory/" target="_blank">https://ask.openstack.org/en/question/32826/why-doesnt-suspend-release-vcpusmemory/</a></blockquote>
</div><br><div style="font-family:'courier new',monospace">My understanding was always that the instance is no longer consuming any resources via the virt layer, so in essence the resources are in fact freed up on the Compute Node. Quotas and such however aren't modified (which seems correct to me). Are you saying you want to see quota's adjusted here? </div>
<br></div></div>
</blockquote></div><br><br clear="all"><br></div></div><div>-- <br><div dir="ltr"><div>Ricky Saltzer</div><div><a href="http://www.cloudera.com" target="_blank">http://www.cloudera.com</a><br></div><div><br></div>
</div>
</div></div>
</blockquote></div></div></div><div class="gmail_default" style="font-family:'courier new',monospace">Yeah, I think that makes sense and is expected, as a user you're still consuming those "items" even if they're not active. The alternative would be (which I think is what you're getting at) to actually deduct items that are suspended from the tenants quota count. I guess when I think of it though those resources are still "reserved" even if they're not in use. I suppose you could do this and then if on resume the quota isn't there we don't actually resume... but I think this could be argued either way.</div>
<div class="gmail_default" style="font-family:'courier new',monospace"><br></div><div class="gmail_default" style="font-family:'courier new',monospace">Maybe seperate quotas for active vs suspended? </div>
<br></div></div>
</blockquote></div><br><br clear="all"><br>-- <br><div dir="ltr"><div>Ricky Saltzer</div><div><a href="http://www.cloudera.com" target="_blank">http://www.cloudera.com</a><br></div><div><br></div></div>
</div>
</div></div><br>_______________________________________________<br>
Mailing list: <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
Post to : <a href="mailto:openstack@lists.openstack.org">openstack@lists.openstack.org</a><br>
Unsubscribe : <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
<br></blockquote></div><br></div>