Configurations look ok. Could you check to see if there are destroyVirtualMachine API calls in the management server logs? If not then the condition for Scale down is probably not getting hit. To find out if the condition is being hit in Netscaler, run "nsconmsg" in the shell. When scale down is triggered, you should see logs something like:
Evaluating autoscale policy.. : Triggering autoscale action SCALE_DOWN for action ... > -----Original Message----- > From: Francois Gaudreault [mailto:fgaudrea...@cloudops.com] > Sent: Friday, June 28, 2013 1:44 AM > To: dev@cloudstack.apache.org > Subject: Auto-scaling won't scale down > > Hi, > > So I tried the AutoScaling on our setup today, and while it's working fine to > scale > up, it won't scale down. We are on CS 4.1.0 nonoss with NetScaler 10.1 build > 112.15. > > I configured a Scale Up policy to trigger when servers are under 30% CPU idle > for > a duration of 60sec, and Scale Down policy to trigger when servers are over > 40% > CPU idle for a duration of 120secs. I configured the AutoScaling to have a > minimum of 1 machine, and a maximum of 3. > > I do see the SNMP calls coming from the NetScaler, and the response. > > Did I configured it wrong? Let me know what you need for troubleshooting. > > Thanks! > > -- > Francois Gaudreault > Architecte de Solution Cloud | Cloud Solutions Architect > fgaudrea...@cloudops.com > 514-629-6775 > - - - > CloudOps > 420 rue Guy > Montréal QC H3J 1S6 > www.cloudops.com > @CloudOps_
