<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>
<div>Why wouldn't you separate you dev/test/productiion via tenants as well? That’s what we encourage our users to do. This would let you create flavors that give dev/test less resources under exhaustion conditions and production more resources. You could
even pin dev/test to specific hypervisors/areas of the cloud and let production have the rest via those flavors. </div>
<div>
<div>____________________________________________</div>
<div> </div>
<div>Kris Lindgren</div>
<div>Senior Linux Systems Engineer</div>
<div>GoDaddy, LLC.</div>
</div>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Daniel Comnea <<a href="mailto:comnea.dani@gmail.com">comnea.dani@gmail.com</a>><br>
<span style="font-weight:bold">Date: </span>Wednesday, April 8, 2015 at 3:32 AM<br>
<span style="font-weight:bold">To: </span>Daniel Comnea <<a href="mailto:comnea.dani@gmail.com">comnea.dani@gmail.com</a>><br>
<span style="font-weight:bold">Cc: </span>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>>, "<a href="mailto:openstack-operators@lists.openstack.org">openstack-operators@lists.openstack.org</a>"
<<a href="mailto:openstack-operators@lists.openstack.org">openstack-operators@lists.openstack.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [Openstack-operators] [Openstack-dev] resource quotas limit per stacks within a project<br>
</div>
<div><br>
</div>
<div>
<div>
<div dir="ltr">
<div>
<div>
<div>+ operators <br>
<br>
</div>
Hard to believe nobody is facing this problems, even on small shops you end up with multiple stacks part of the same tenant/ project.<br>
<br>
</div>
Thanks,<br>
</div>
Dani<br>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Wed, Apr 1, 2015 at 8:10 PM, Daniel Comnea <span dir="ltr">
<<a href="mailto:comnea.dani@gmail.com" target="_blank">comnea.dani@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 dir="ltr">
<div>
<div>
<div>Any ideas/ thoughts please?<br>
<br>
</div>
In VMware world is basically the same feature provided by the resource pool.<br>
<br>
<br>
</div>
Thanks,<br>
</div>
Dani<br>
</div>
<div class="HOEnZb">
<div class="h5">
<div class="gmail_extra"><br>
<div class="gmail_quote">On Tue, Mar 31, 2015 at 10:37 PM, Daniel Comnea <span dir="ltr">
<<a href="mailto:comnea.dani@gmail.com" target="_blank">comnea.dani@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 dir="ltr">
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>Hi all,<br>
<br>
</div>
I'm trying to understand what options i have for the below use case...<br>
<br>
</div>
Having multiple stacks (various number of instances) deployed within 1 <span>Openstack</span> project (tenant), how can i guarantee that there will be no race after the project resources.<br>
<br>
</div>
E.g - say i have few stacks like<br>
<br>
</div>
stack 1 = production<br>
</div>
stack 2 = development<br>
</div>
stack 3 = integration<br>
<br>
</div>
i don't want to be in a situation where stack 3 (because of a need to run some heavy tests) will use all of the resources for a short while while production will suffer from it.<br>
<br>
</div>
Any ideas?<br>
<br>
</div>
Thanks,<br>
</div>
Dani<br>
<br>
</div>
P.S - <span>i'm</span> aware of the heavy work being put into improving the quotas or the CPU pinning however that is at the project level<br>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</span>
</body>
</html>