<div dir="ltr">Hi,<div><br></div><div><div class="gmail_extra"><div class="gmail_quote">On Wed, Dec 4, 2013 at 2:40 AM, Rajendar K <span dir="ltr"><<a href="mailto:k.rajendar@gmail.com" target="_blank">k.rajendar@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">Hi Carlos,<div> Thanks for the mail. Here are my queries,</div>
<div class="gmail_extra"><br clear="all"><div><br></div><div class="gmail_quote"><div class="im">On Tue, Dec 3, 2013 at 7:52 PM, Carlos Martín Sánchez <span dir="ltr"><<a href="mailto:cmartin@opennebula.org" target="_blank">cmartin@opennebula.org</a>></span> wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">Hi,<div><br></div><div class="im"><div>
<div class="gmail_quote">
On Mon, Dec 2, 2013 at 4:51 AM, Rajendar K <span dir="ltr"><<a href="mailto:k.rajendar@gmail.com" target="_blank">k.rajendar@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div><div><div><div>Hi Carlos,<br>
</div> I have updated the files [oneflow-templates and service] as per your instructions. Hereby specify the output of oneflow<br>
<br></div></div><div>=> Elasticty conditions<br><br> "min_vms": 1,<br> "max_vms": 3,<br><b><i> "cooldown": 60, => At what period , this parameter is being employed? </i></b><br>
"elasticity_policies": [<br> {<br> "type": "CHANGE",<br> "adjust": 1,<br> "expression": "CPU < 60",<br> "period": 3,<br>
"period_number": 30,<br> "cooldown": 30 <br> }<br> ],<br> "scheduled_policies": [<br><br> ]<br> }<br><br><br></div></div><div>
kindly provide detail on how auto-scaling is happened in the above sample, with relates to "period_number" , "period" and "cooldown"<br>
</div></div></blockquote><div><br></div><div>The period_number, period and cooldown attributes are explained in detail in the documentation [1].</div><div>In your example, the expression CPU < 60 must be true 30 times, each 3 seconds.</div>
</div></div></div></div></blockquote><div><br></div><div><b><i>So the scaling should be triggered after 1.30 minutes (30 * 3 seconds) (90 seconds) is it right?<br></i></b></div><div><b><i><br></i></b></div><div><b><i>The log shows that scaling is triggered after 16 minutes,</i></b></div>
<div class="im">
<div> </div><div><span style="color:rgb(80,0,80)">LOG MESSAGES </span><span style="color:rgb(80,0,80)"> </span><span style="color:rgb(80,0,80)"> </span><br style="color:rgb(80,0,80)">
<span style="color:rgb(80,0,80)">12/02/13 10:06 [I] New state: DEPLOYING</span><br style="color:rgb(80,0,80)"><span style="color:rgb(80,0,80)"><b>12/02/13 10:07 [I] New state: RUNNING</b></span><br style="color:rgb(80,0,80)">
<span style="color:rgb(80,0,80)"><b>12/02/13 10:22 [I] Role role1 scaling up from 1 to 2 nodes</b></span><br style="color:rgb(80,0,80)"><span style="color:rgb(80,0,80)">12/02/13 10:22 [I] New state: SCALING</span><br style="color:rgb(80,0,80)">
<span style="color:rgb(80,0,80)">12/02/13 10:23 [I] New state: COOLDOWN</span><br style="color:rgb(80,0,80)"><span style="color:rgb(80,0,80)">12/02/13 10:23 [I] New state: RUNNING</span><br style="color:rgb(80,0,80)"><span style="color:rgb(80,0,80)"><b>12/02/13 10:38 [I] Role role1 scaling up from 2 to 3 nodes</b></span><br style="color:rgb(80,0,80)">
<span style="color:rgb(80,0,80)">12/02/13 10:38 [I] New state: SCALING</span><br style="color:rgb(80,0,80)"><span style="color:rgb(80,0,80)">12/02/13 10:39 [I] New state: COOLDOWN</span><br style="color:rgb(80,0,80)"><span style="color:rgb(80,0,80)">12/02/13 10:39 [I] New state: RUNNING</span></div>
</div></div></div></div></blockquote><div><br></div><div>The role will scale up <b>if the expression is true</b> those 90 seconds. When the expression is false, the counter is reset.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr"><div><div class="gmail_quote">
<div><br></div><div class="im"><div>After the scaling, your service will be in the cooldown period for 30 seconds before returning to running. The only defined policy is overriding the default cooldown of 60 that you set.</div>
<div><br>
</div></div></div></div></div></blockquote><div><br></div><div>if my understanding is correct, if we didn't specify any cooldown for each role , it takes the default policy as "60" using that parameter?</div>
</div></div></div></blockquote><div><br></div><div>That's right, if you set a default cooldown for the service you can leave it unset for the roles.</div><div><br></div><div><br></div><div>Regards</div><div><br></div>
<div>--<br><div>Carlos Martín, MSc<br>Project Engineer</div><div>OpenNebula - Flexible Enterprise Cloud Made Simple<br><div><span style="border-collapse:collapse;color:rgb(136,136,136);font-family:arial,sans-serif;font-size:13px"><a href="http://www.opennebula.org/" target="_blank">www.OpenNebula.org</a> | <a href="mailto:cmartin@opennebula.org" target="_blank">cmartin@opennebula.org</a> | <a href="http://twitter.com/opennebula" target="_blank">@OpenNebula</a></span></div>
</div></div></div></div></div></div>