<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=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:\5B8B\4F53;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@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;}
@font-face
{font-family:"\@\5B8B\4F53";
panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
text-align:justify;
text-justify:inter-ideograph;
font-size:10.5pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"\7EAF\6587\672C Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.5pt;
font-family:"Calibri","sans-serif";}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.Char
{mso-style-name:"\7EAF\6587\672C Char";
mso-style-priority:99;
mso-style-link:\7EAF\6587\672C;
font-family:"Calibri","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
/* Page Definitions */
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 90.0pt 72.0pt 90.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="ZH-CN" link="#0563C1" vlink="#954F72" style="text-justify-trim:punctuation">
<div class="WordSection1">
<p class="MsoPlainText"><span lang="EN-US">Excerpts from Sylvernass Arthas's message of 2016-05-08 05:33:13 -0700:<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">> Hi, guys<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">> <o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">> Now, all tenant share the public config "max_stacks_per_tenant" which decides maximum number of stacks any one tenant may have active at one time, the default value is 1000.<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">> Should heat provides ability to set this config by different tenant? For example, in a enterprise, maybe tenant A needs 10000 stack quota, tenant B needs 100 stack quota, but now heat can't manage with it, at least
in Liberity.<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">> So in future, will heat provides this ability or other policy to solve this?<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">I think enough people have stated that they want it that it will happen some day. There may even be a spec now, I haven't been tracking all of the specs. However, I don't actually think there's any point to Heat quotas,
as the resources used to run a Heat stack are so much cheaper compared to the resources it enables the user to consume -- servers, networks, volumes, etc. One might as well let users run as many heat stacks as they want within reason, as their quotas on those
items will fill up far before they cost you any actual money.<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">In fact, the only reason the max setting exists now is to protect the code that does stack listing from eating up all of the memory on the servers.<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">It has a second unintended use case which is to prevent anyone from using Heat as free object storage. :)<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">It's important to take my words with a grain of salt. I'm not directly involved with Heat anymore.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
</body>
</html>