<div dir="ltr">I also have the same concern with Lee, as Magnum depend on HEAT  and HEAT need call nova, cinder, neutron to create the Bay resources. But both Nova and Cinder has its own quota policy, if we define quota again in Magnum, then how to handle the conflict? Another point is that limiting the Bay by quota seems a bit coarse-grainded as different bays may have different configuration and resource request. Comments? Thanks.<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Dec 17, 2015 at 4:10 AM, Lee Calcote <span dir="ltr"><<a href="mailto:leecalcote@gmail.com" target="_blank">leecalcote@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">Food for thought - there is a cost to FIPs (in the case of public IP addresses), security groups (to a lesser extent, but in terms of the computation of many hundreds of them), etc. Administrators may wish to enforce quotas on a variety of resources that are direct costs or indirect costs (e.g. # of bays, where a bay consists of a number of multi-VM / multi-host pods and services, which consume CPU, mem, etc.).<div><br></div><div>If Magnum quotas are brought forward, they should govern (enforce quota) on Magnum-specific constructs only, correct? Resources created by Magnum COEs should be governed by existing quota policies governing said resources (e.g. Nova and vCPUs).</div><span class="HOEnZb"><font color="#888888"><div><br></div><div>Lee</div></font></span><div><br><div><blockquote type="cite"><div><div class="h5"><div>On Dec 16, 2015, at 1:56 PM, Tim Bell <<a href="mailto:Tim.Bell@cern.ch" target="_blank">Tim.Bell@cern.ch</a>> wrote:</div><br></div></div><div><div><div><div class="h5"><blockquote type="cite" style="font-family:Calibri;font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">-----Original Message-----<br>From: Clint Byrum [<a href="mailto:clint@fewbar.com" target="_blank">mailto:clint@fewbar.com</a>]<br>Sent: 15 December 2015 22:40<br>To: openstack-dev <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>><br>Subject: Re: [openstack-dev] [openstack][magnum] Quota for Magnum<br>Resources<br><br>Hi! Can I offer a counter point?<br><br>Quotas are for _real_ resources.<br><br></blockquote><br style="font-family:Calibri;font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="font-family:Calibri;font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">The CERN container specialist agrees with you ... it would be good to</span><br style="font-family:Calibri;font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="font-family:Calibri;font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">reflect on the needs given that ironic, neutron and nova are policing the</span><br style="font-family:Calibri;font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="font-family:Calibri;font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">resource usage. Quotas in the past have been used for things like key pairs</span><br style="font-family:Calibri;font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="font-family:Calibri;font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">which are not really real.</span><br style="font-family:Calibri;font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><br style="font-family:Calibri;font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><blockquote type="cite" style="font-family:Calibri;font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">Memory, CPU, disk, bandwidth. These are all _closely_ tied to things that<br></blockquote><span style="font-family:Calibri;font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">cost</span><br style="font-family:Calibri;font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><blockquote type="cite" style="font-family:Calibri;font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">real money and cannot be conjured from thin air. As such, the user being<br>able to allocate 1 billion or 2 containers is not limited by Magnum, but<br></blockquote><span style="font-family:Calibri;font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">by real</span><br style="font-family:Calibri;font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><blockquote type="cite" style="font-family:Calibri;font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">things that they must pay for. If they have enough Nova quota to allocate<br></blockquote><span style="font-family:Calibri;font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">1</span><br style="font-family:Calibri;font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><blockquote type="cite" style="font-family:Calibri;font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">billion tiny pods, why would Magnum stop them? Who actually benefits from<br>that limitation?<br><br>So I suggest that you not add any detailed, complicated quota system to<br>Magnum. If there are real limitations to the implementation that Magnum<br>has chosen, such as we had in Heat (the entire stack must fit in memory),<br>then make that the limit. Otherwise, let their vcpu, disk, bandwidth, and<br>memory quotas be the limit, and enjoy the profit margins that having an<br>unbound force multiplier like Magnum in your cloud gives you and your<br>users!<br><br>Excerpts from Vilobh Meshram's message of 2015-12-14 16:58:54 -0800:<br><blockquote type="cite">Hi All,<br><br>Currently, it is possible to create unlimited number of resource like<br>bay/pod/service/. In Magnum, there should be a limitation for user or<br>project to create Magnum resource, and the limitation should be<br>configurable[1].<br><br>I proposed following design :-<br><br>1. Introduce new table magnum.quotas<br>+------------+--------------+------+-----+---------+----------------+<br><br>| Field      | Type         | Null | Key | Default | Extra          |<br><br>+------------+--------------+------+-----+---------+----------------+<br><br>| id         | int(11)      | NO   | PRI | NULL    | auto_increment |<br><br>| created_at | datetime     | YES  |     | NULL    |                |<br><br>| updated_at | datetime     | YES  |     | NULL    |                |<br><br>| deleted_at | datetime     | YES  |     | NULL    |                |<br><br>| project_id | varchar(255) | YES  | MUL | NULL    |                |<br><br>| resource   | varchar(255) | NO   |     | NULL    |                |<br><br>| hard_limit | int(11)      | YES  |     | NULL    |                |<br><br>| deleted    | int(11)      | YES  |     | NULL    |                |<br><br>+------------+--------------+------+-----+---------+----------------+<br><br>resource can be Bay, Pod, Containers, etc.<br><br><br>2. API controller for quota will be created to make sure basic CLI<br>commands work.<br><br>quota-show, quota-delete, quota-create, quota-update<br><br>3. When the admin specifies a quota of X number of resources to be<br>created the code should abide by that. For example if hard limit for Bay<br></blockquote></blockquote><span style="font-family:Calibri;font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">is 5</span><br style="font-family:Calibri;font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><blockquote type="cite" style="font-family:Calibri;font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">(i.e.<br><blockquote type="cite">a project can have maximum 5 Bay's) if a user in a project tries to<br>exceed that hardlimit it won't be allowed. Similarly goes for other<br></blockquote>resources.<br><blockquote type="cite"><br>4. Please note the quota validation only works for resources created<br>via Magnum. Could not think of a way that Magnum to know if a COE<br>specific utilities created a resource in background. One way could be<br>to see the difference between whats stored in magnum.quotas and the<br>information of the actual resources created for a particular bay in<br></blockquote></blockquote><span style="font-family:Calibri;font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">k8s/COE.</span><br style="font-family:Calibri;font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><blockquote type="cite" style="font-family:Calibri;font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><blockquote type="cite"><br>5. Introduce a config variable to set quotas values.<br><br>If everyone agrees will start the changes by introducing quota<br>restrictions on Bay creation.<br><br>Thoughts ??<br><br><br>-Vilobh<br><br>[1] <a href="https://blueprints.launchpad.net/magnum/+spec/resource-quota" target="_blank">https://blueprints.launchpad.net/magnum/+spec/resource-quota</a><br></blockquote><br>________________________________________________________________<br>__________<br>OpenStack Development Mailing List (not for usage questions)<br>Unsubscribe: OpenStack-dev-<br><a href="mailto:request@lists.openstack.org" target="_blank">request@lists.openstack.org</a>?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></blockquote></div></div><span style="font-family:Calibri;font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">__________________________________________________________________________</span><span class=""><br style="font-family:Calibri;font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="font-family:Calibri;font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">OpenStack Development Mailing List (not for usage questions)</span><br style="font-family:Calibri;font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="font-family:Calibri;font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">Unsubscribe:<span> </span></span><a href="mailto:OpenStack-dev-request@lists.openstack.org" style="font-family:Calibri;font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" target="_blank">OpenStack-dev-request@lists.openstack.org</a><span style="font-family:Calibri;font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">?subject:unsubscribe</span><br style="font-family:Calibri;font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" style="font-family:Calibri;font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></span></div></div></blockquote></div><br></div></div><br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div>Thanks,<br><br></div>Jay Lau (Guangya Liu)<br></div></div></div></div>
</div>