<div dir="ltr"><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><br>root@aaaa:/srv/cloud/one# oneflow show 179<br>
SERVICE 179 INFORMATION <br>ID : 179 <br>NAME : Sampletest <br>USER : root <br>GROUP : oneadmin <br>
STRATEGY : straight <br>SERVICE STATE : RUNNING <br>SHUTDOWN : shutdown <br><br>PERMISSIONS <br>
OWNER : um- <br>GROUP : --- <br>OTHER : --- <br><br>ROLE role1<br>ROLE STATE : RUNNING <br>VM TEMPLATE : 590 <br>
CARNIDALITY : 3 <br>MIN VMS : 1 <br>MAX VMS : 3 <br>COOLDOWN : 60s <br>SHUTDOWN : shutdown <br>
NODES INFORMATION<br> VM_ID NAME STAT UCPU UMEM HOST TIME<br> 568 role1_0_(service_179) runn 0 1024M 10.1.26.32 0d 01h24<br> 569 role1_1_(service_179) runn 0 1024M 10.1.26.31 0d 01h07<br>
570 role1_2_(service_179) runn 0 1024M 10.1.26.32 0d 00h51<br><br>ELASTICITY RULES<br><br>ADJUST EXPRESSION EVALS PERIOD COOL<br>+ 1 CPU[0.0] < 60 30 / 3s 30s<br>
<br><br>LOG MESSAGES <br>12/02/13 10:06 [I] New state: DEPLOYING<br>12/02/13 10:07 [I] New state: RUNNING<br>12/02/13 10:22 [I] Role role1 scaling up from 1 to 2 nodes<br>
12/02/13 10:22 [I] New state: SCALING<br>12/02/13 10:23 [I] New state: COOLDOWN<br>12/02/13 10:23 [I] New state: RUNNING<br>12/02/13 10:38 [I] Role role1 scaling up from 2 to 3 nodes<br>12/02/13 10:38 [I] New state: SCALING<br>
12/02/13 10:39 [I] New state: COOLDOWN<br>12/02/13 10:39 [I] New state: RUNNING<br><br></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>kindly provide detail on how auto-scaling is happened in the above sample, with relates to "period_number" , "period" and "cooldown"<br>
<br>with regards<br>Raj<br><div><div><br></div></div></div><div class="gmail_extra"><br clear="all"><div>Raj,<div><span></span><br><span></span><div>Believe Yourself...</div></div></div>
<br><br><div class="gmail_quote">On Sat, Nov 30, 2013 at 2:19 AM, Carlos Martín Sánchez <span dir="ltr"><<a href="mailto:cmartin@opennebula.org" target="_blank">cmartin@opennebula.org</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">Hi,<div><br></div><div class="gmail_extra"><div class="gmail_quote"><div class="im">On Fri, Nov 29, 2013 at 5:19 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 All,<div> I am using opennebula 4.2, i have the following queries related to auto scaling features</div>
<div><br></div><div>(i) Even when conditions met, scaling up takes long time to trigger.</div>
<div> For my trial, I have used #periods 5 #period 30 cooldown 30</div><div> <br> -> i can able to c the values 5/5 in the log, and then it crosses 16/5 in course of time</div><div> -> Unable to trace down when it trigger actually.</div>
<div> hope it should trigger when it reaches 5/5 ?</div><div><br></div></div></blockquote><div><br></div></div><div>This is a known bug, the period and period number inputs in sunstone are inverted [1].</div><div>
To solve it, execute:</div>
<div><br></div><div><div>$ sudo wget <a href="http://dev.opennebula.org/projects/opennebula/repository/revisions/5c7b370f6be5f4f9167d508bdd31b580f05dafd4/raw/src/sunstone/public/js/plugins/oneflow-templates.js" target="_blank">http://dev.opennebula.org/projects/opennebula/repository/revisions/5c7b370f6be5f4f9167d508bdd31b580f05dafd4/raw/src/sunstone/public/js/plugins/oneflow-templates.js</a> -O /usr/lib/one/sunstone/public/js/plugins/oneflow-templates.js</div>
<div><br></div><div>$ sudo wget <a href="http://dev.opennebula.org/projects/opennebula/repository/revisions/970c34464a1d5a71f3a9dfdd3d77d62883400857/raw/src/sunstone/public/js/plugins/oneflow-services.js" target="_blank">http://dev.opennebula.org/projects/opennebula/repository/revisions/970c34464a1d5a71f3a9dfdd3d77d62883400857/raw/src/sunstone/public/js/plugins/oneflow-services.js</a> -O /usr/lib/one/sunstone/public/js/plugins/oneflow-services.js</div>
</div><div><br></div><div>Or wait a few days and upgrade to OpenNebula 4.4 :)</div><div class="im"><div><br></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></div><div>(ii) Scheduled policies</div><div> -> For my trial i have specified </div><div> start time -> 2013-11-29 10:30:30</div>
<div> is my time format is correct? unable to scale up/down using this time format.</div><div><br></div></div></blockquote><div><br></div></div><div>Could you paste the output of oneflow show -j ?</div><div class="im">
<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></div><div>(ii) is it like "AND" conditions, if i specify both (i) and (ii)?. I have tried separately (i) and (ii) but still in-vain.</div>
</div></blockquote><div><br></div></div><div>No, they do not interfere with each other. Each condition (time, metrics expression) is evaluated independently.</div><div><br></div><div>Regards</div><div><br></div><div>[1] <a href="http://opennebula.org/documentation:rel4.2:known_issues" target="_blank">http://opennebula.org/documentation:rel4.2:known_issues</a><br>
</div><div class="im">--<br><div>Carlos Martín, MSc<br>Project Engineer</div><div>OpenNebula - Flexible Enterprise Cloud Made Simple<br></div><div><a href="http://www.opennebula.org/" style="font-family:arial,sans-serif;font-size:13px" target="_blank">www.OpenNebula.org</a><span style="color:rgb(136,136,136);font-family:arial,sans-serif;font-size:13px"> </span><span style="color:rgb(136,136,136);font-family:arial,sans-serif;font-size:13px">|</span><span style="color:rgb(136,136,136);font-family:arial,sans-serif;font-size:13px"> </span><a href="mailto:cmartin@opennebula.org" style="font-family:arial,sans-serif;font-size:13px" target="_blank">cmartin@opennebula.org</a><span style="color:rgb(136,136,136);font-family:arial,sans-serif;font-size:13px"> </span><span style="color:rgb(136,136,136);font-family:arial,sans-serif;font-size:13px">|</span><span style="color:rgb(136,136,136);font-family:arial,sans-serif;font-size:13px"> </span><a href="http://twitter.com/opennebula" style="font-family:arial,sans-serif;font-size:13px" target="_blank">@OpenNebula</a> </div>
</div></div></div></div>
</blockquote></div><br></div>