<html><head><style>p{margin-top:0px;margin-bottom:0px;}</style></head><body><div style="font-size:13px; font-family:Arial,sans-serif;"><div>Hi All,<br><br></div><p class="p1">We were having a similar use case like *<span style="font-weight: bold;">Preemptible Instances</span>* called as *<span style="font-weight: bold;">Rich-VM’s</span>* which</p><p class="p1">are high in resources and are deployed each per hypervisor. We have a custom code in</p><p class="p1">production which tracks the quota for such instances separately and for the same reason</p><p class="p1">we have *<span style="font-weight: bold;">rich_instances</span>* custom quota class same as *<span style="font-weight: bold;">instances</span>* quota class.<span class="Apple-converted-space"> </span></p>
<p class="p2"><br></p>
<p class="p1">I discussed this thing pretty recently with sean-k-mooney I hope he remembers it.</p><div><br></div><div><br></div><div><div style="width: 36px; height: 1px; margin-bottom: 15px; background-color: rgb(160, 160, 160);"></div><div style="line-height: 16px;"><strong style="font-size: 13px; color: rgb(54, 54, 54); letter-spacing: -1px;">ボーアディネシュ</strong><span style="font-size: 11px; color: rgb(54, 54, 54);"> Bhor Dinesh</span><br><span style="font-size: 11px; color: rgb(137, 137, 137);">Verda2チーム</span><span style="font-size: 11px; color: rgb(137, 137, 137);"></span><br><br><div style="color: rgb(137, 137, 137);"><span style="font-size: 11px; line-height: 14px;">〒160-0022 東京都新宿区新宿4-1-6 JR新宿ミライナタワー 23階</span><br><span style="font-family: tahoma; font-size: 11px; line-height: 14px; color: rgb(153, 153, 153);"><strong style="font-weight: bold; color: rgb(136, 136, 136);">Mobile </strong><span style="font-size: 11px; color: rgb(153, 153, 153);">08041289520 </span><strong style="font-weight: bold; color: rgb(136, 136, 136);">Fax </strong><span style="font-size: 11px; color: rgb(153, 153, 153);">03-4316-2116</span></span><br><span style="font-family: tahoma; font-size: 11px; color: rgb(153, 153, 153);"><strong style="font-weight: bold; color: rgb(136, 136, 136);">Email </strong><span style="font-size: 11px; color: rgb(153, 153, 153);"><a href="mailto:dinesh.bhor@linecorp.com" style="color: rgb(153, 153, 153); text-decoration: none;" rel="noreferrer noopener" target="_blank">dinesh.bhor@linecorp.com </a></span><br></span><br><span style="margin-right: -3px;"><a href="http://linecorp.com" target="_blank" rel="noreferrer noopener"><img align="absmiddle" src="https://static.navercorp.com/static/site/connect2/user/connect/signature/line.png" border="0"></a></span></div></div></div><br><p style="font-size:10pt;font-family:sans-serif;padding:0 0 0 10pt"><span>-----Original Message-----</span><br><b>From:</b> "Kevin L. Mitchell"<klmitch@mit.edu> <br><b>To:</b> "OpenStack Development Mailing List (not for usage questions)"<openstack-dev@lists.openstack.org>; "openstack-operators@lists.openstack.org"<openstack-operators@lists.openstack.org>; <br><b>Cc:</b> <br><b>Sent:</b> Oct 25, 2018 (Thu) 11:35:08<br><b>Subject:</b> Re: [openstack-dev] [nova][limits] Does ANYONE at all use the quota class functionality in Nova?<br> </p>> On 10/24/18 10:10, Jay Pipes wrote:<br>> > Nova's API has the ability to create "quota classes", which are<br>> > basically limits for a set of resource types. There is something called<br>> > the "default quota class" which corresponds to the limits in the<br>> > CONF.quota section. Quota classes are basically templates of limits to<br>> > be applied if the calling project doesn't have any stored<br>> > project-specific limits.<br><br>For the record, my original concept in creating quota classes is that<br>you'd be able to set quotas per tier of user and easily be able to move<br>users from one tier to another. This was just a neat idea I had, and<br>AFAIK, Rackspace never used it, so you can call it YAGNI as far as I'm<br>concerned :)<br><br>> > Has anyone ever created a quota class that is different from "default"?<br>> > <br>> > I'd like to propose deprecating this API and getting rid of this<br>> > functionality since it conflicts with the new Keystone /limits endpoint,<br>> > is highly coupled with RAX's turnstile middleware <br><br>I didn't intend it to be highly coupled, but it's been a while since I<br>wrote it, and of course I've matured as a developer since then, so<br>*shrug*. I also don't think Rackspace has ever used turnstile.<br><br>> > and I can't seem to<br>> > find anyone who has ever used it. Deprecating this API and functionality<br>> > would make the transition to a saner quota management system much easier<br>> > and straightforward.<br><br>I'm fine with that plan, speaking as the original developer; as I say,<br>I don't think Rackspace ever utilized the functionality anyway, and if<br>no one else pipes up saying that they're using it, I'd be all over<br>deprecating the quota classes in favor of the new hotness.<br>-- <br>Kevin L. Mitchell <klmitch@mit.edu><br><br><br>__________________________________________________________________________<br>OpenStack Development Mailing List (not for usage questions)<br>Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe<br><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br><br></div></body></html><table style='display:none'><tr><td><img src="https://ack.mail.navercorp.com/readReceipt/notify/?img=gsbmFot%2FaxkoK6EYaqumpxFCKquZaA3CMxt%2FFztZMxvqM6k0aA0CMqKZFuIo%2BrkSKAK5W49vpSl51zlqDBFdp6d5MreRhoRTbzk5bX3CMrnRpzkrtzwGbX3q74emp6lq%2BzJo1ZlTb4b%3D.gif" border="0"/></td></tr></table>