<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0cm;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
        {mso-style-name:msonormal;
        mso-margin-top-alt:auto;
        margin-right:0cm;
        mso-margin-bottom-alt:auto;
        margin-left:0cm;
        font-size:11.0pt;
        font-family:"Calibri",sans-serif;}
span.im
        {mso-style-name:im;}
span.EmailStyle19
        {mso-style-type:personal-reply;
        font-family:"Calibri",sans-serif;
        color:windowtext;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}
@page WordSection1
        {size:612.0pt 792.0pt;
        margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
        {page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-GB">I think nested quotas would give the same thing, i.e. you have a parent project for the group and child projects for the users. This would not need user/group quotas but continue with the ‘project owns resources’ approach.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">It can be generalised to other use cases like the value add partner or the research experiment working groups (<a href="http://openstack-in-production.blogspot.fr/2017/07/nested-quota-models.html">http://openstack-in-production.blogspot.fr/2017/07/nested-quota-models.html</a>)<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">Tim<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal" style="margin-left:36.0pt"><b><span style="font-size:12.0pt;color:black">From:
</span></b><span style="font-size:12.0pt;color:black">Zhipeng Huang <zhipengh512@gmail.com><br>
<b>Reply-To: </b>"openstack-sigs@lists.openstack.org" <openstack-sigs@lists.openstack.org><br>
<b>Date: </b>Wednesday, 7 March 2018 at 17:37<br>
<b>To: </b>"OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org>, openstack-operators <openstack-operators@lists.openstack.org>, "openstack-sigs@lists.openstack.org" <openstack-sigs@lists.openstack.org><br>
<b>Subject: </b>Re: [Openstack-sigs] [openstack-dev] [keystone] [oslo] new unified limit library<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><a name="_MailOriginalBody">This is certainly a feature will make Public Cloud providers very happy :)<o:p></o:p></a></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="mso-bookmark:_MailOriginalBody"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="mso-bookmark:_MailOriginalBody">On Thu, Mar 8, 2018 at 12:33 AM, Tim Bell <</span><a href="mailto:Tim.Bell@cern.ch" target="_blank"><span style="mso-bookmark:_MailOriginalBody">Tim.Bell@cern.ch</span><span style="mso-bookmark:_MailOriginalBody"></span></a><span style="mso-bookmark:_MailOriginalBody">>
 wrote:<o:p></o:p></span></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<p class="MsoNormal" style="margin-left:36.0pt"><span style="mso-bookmark:_MailOriginalBody">Sorry, I remember more detail now... it was using the 'owner' of the VM as part of the policy rather than quota.<br>
<br>
Is there a per-user/per-group quota in Nova?<br>
<br>
Tim<br>
<br>
-----Original Message-----<br>
From: Tim Bell <</span><a href="mailto:Tim.Bell@cern.ch"><span style="mso-bookmark:_MailOriginalBody">Tim.Bell@cern.ch</span><span style="mso-bookmark:_MailOriginalBody"></span></a><span style="mso-bookmark:_MailOriginalBody">><br>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" <</span><a href="mailto:openstack-dev@lists.openstack.org"><span style="mso-bookmark:_MailOriginalBody">openstack-dev@lists.openstack.org</span><span style="mso-bookmark:_MailOriginalBody"></span></a><span style="mso-bookmark:_MailOriginalBody">><br>
Date: Wednesday, 7 March 2018 at 17:29<br>
<span class="im">To: "OpenStack Development Mailing List (not for usage questions)" <</span></span><a href="mailto:openstack-dev@lists.openstack.org"><span style="mso-bookmark:_MailOriginalBody">openstack-dev@lists.openstack.org</span><span style="mso-bookmark:_MailOriginalBody"></span></a><span style="mso-bookmark:_MailOriginalBody"><span class="im">></span></span><span style="mso-bookmark:_MailOriginalBody"><o:p></o:p></span></p>
<div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="mso-bookmark:_MailOriginalBody">Subject: Re: [openstack-dev] [keystone] [oslo] new unified limit library<br>
<br>
<br>
    There was discussion that Nova would deprecate the user quota feature since it really didn't fit well with the 'projects own resources' approach and was little used. At one point, some of the functionality stopped working and was repaired. The use case
 we had identified goes away if you have 2 level deep nested quotas (and we have now worked around it).<br>
<br>
    Tim<br>
    -----Original Message-----<br>
    From: Lance Bragstad <</span><a href="mailto:lbragstad@gmail.com"><span style="mso-bookmark:_MailOriginalBody">lbragstad@gmail.com</span><span style="mso-bookmark:_MailOriginalBody"></span></a><span style="mso-bookmark:_MailOriginalBody">><br>
    Reply-To: "OpenStack Development Mailing List (not for usage questions)" <</span><a href="mailto:openstack-dev@lists.openstack.org"><span style="mso-bookmark:_MailOriginalBody">openstack-dev@lists.openstack.org</span><span style="mso-bookmark:_MailOriginalBody"></span></a><span style="mso-bookmark:_MailOriginalBody">><br>
    Date: Wednesday, 7 March 2018 at 16:51<br>
    To: "</span><a href="mailto:openstack-dev@lists.openstack.org"><span style="mso-bookmark:_MailOriginalBody">openstack-dev@lists.openstack.org</span><span style="mso-bookmark:_MailOriginalBody"></span></a><span style="mso-bookmark:_MailOriginalBody">" <</span><a href="mailto:openstack-dev@lists.openstack.org"><span style="mso-bookmark:_MailOriginalBody">openstack-dev@lists.openstack.org</span><span style="mso-bookmark:_MailOriginalBody"></span></a><span style="mso-bookmark:_MailOriginalBody">><br>
    Subject: Re: [openstack-dev] [keystone] [oslo] new unified limit library<br>
<br>
<br>
<br>
        On 03/07/2018 09:31 AM, Chris Friesen wrote:<br>
        > On 03/07/2018 08:58 AM, Lance Bragstad wrote:<br>
        >> Hi all,<br>
        >><br>
        ]<br>
        ><br>
        > 1) Nova currently supports quotas for a user/group tuple that can be<br>
        > stricter than the overall quotas for that group.  As far as I know no<br>
        > other project supports this.<br>
    ...<br>
        I think the initial implementation of a unified limit pattern is<br>
        targeting limits and quotas for things associated to projects. In the<br>
        future, we can probably expand on the limit information in keystone to<br>
        include user-specific limits, which would be great if nova wants to move<br>
        away from handling that kind of stuff.<br>
        ><br>
        > Chris<br>
        ><br>
        > __________________________________________________________________________<br>
        ><br>
        > OpenStack Development Mailing List (not for usage questions)<br>
        > Unsubscribe:<br>
        > </span><a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank"><span style="mso-bookmark:_MailOriginalBody">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</span><span style="mso-bookmark:_MailOriginalBody"></span></a><span style="mso-bookmark:_MailOriginalBody"><br>
        > </span><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank"><span style="mso-bookmark:_MailOriginalBody">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</span><span style="mso-bookmark:_MailOriginalBody"></span></a><span style="mso-bookmark:_MailOriginalBody"><br>
<br>
<br>
<br>
<br>
    __________________________________________________________________________<br>
    OpenStack Development Mailing List (not for usage questions)<br>
    Unsubscribe: </span><a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank"><span style="mso-bookmark:_MailOriginalBody">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</span><span style="mso-bookmark:_MailOriginalBody"></span></a><span style="mso-bookmark:_MailOriginalBody"><br>
    </span><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank"><span style="mso-bookmark:_MailOriginalBody">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</span><span style="mso-bookmark:_MailOriginalBody"></span></a><span style="mso-bookmark:_MailOriginalBody"><br>
<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: </span><a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank"><span style="mso-bookmark:_MailOriginalBody">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</span><span style="mso-bookmark:_MailOriginalBody"></span></a><span style="mso-bookmark:_MailOriginalBody"><br>
</span><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank"><span style="mso-bookmark:_MailOriginalBody">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</span><span style="mso-bookmark:_MailOriginalBody"></span></a><span style="mso-bookmark:_MailOriginalBody"><o:p></o:p></span></p>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="mso-bookmark:_MailOriginalBody"><br>
<br clear="all">
<o:p></o:p></span></p>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="mso-bookmark:_MailOriginalBody"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="mso-bookmark:_MailOriginalBody">--
<o:p></o:p></span></p>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="mso-bookmark:_MailOriginalBody">Zhipeng (Howard) Huang<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="mso-bookmark:_MailOriginalBody"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="mso-bookmark:_MailOriginalBody">Standard Engineer<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="mso-bookmark:_MailOriginalBody">IT Standard & Patent/IT Product Line<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="mso-bookmark:_MailOriginalBody">Huawei Technologies Co,. Ltd<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="mso-bookmark:_MailOriginalBody">Email:
</span><a href="mailto:huangzhipeng@huawei.com" target="_blank"><span style="mso-bookmark:_MailOriginalBody">huangzhipeng@huawei.com</span><span style="mso-bookmark:_MailOriginalBody"></span></a><span style="mso-bookmark:_MailOriginalBody"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="mso-bookmark:_MailOriginalBody">Office: Huawei Industrial Base, Longgang, Shenzhen<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="mso-bookmark:_MailOriginalBody"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="mso-bookmark:_MailOriginalBody">(Previous)<o:p></o:p></span></p>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="mso-bookmark:_MailOriginalBody">Research Assistant<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="mso-bookmark:_MailOriginalBody">Mobile Ad-Hoc Network Lab, Calit2<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="mso-bookmark:_MailOriginalBody">University of California, Irvine<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="mso-bookmark:_MailOriginalBody">Email:
</span><a href="mailto:zhipengh@uci.edu" target="_blank"><span style="mso-bookmark:_MailOriginalBody">zhipengh@uci.edu</span><span style="mso-bookmark:_MailOriginalBody"></span></a><span style="mso-bookmark:_MailOriginalBody"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="mso-bookmark:_MailOriginalBody">Office: Calit2 Building Room 2402<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="mso-bookmark:_MailOriginalBody"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="mso-bookmark:_MailOriginalBody">OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>