Diego, The chef orchestration supports basic elasticity, i.e. scaling up and down on manual command. To scale up or down, just issue another "knife deployment resize" command specifying a different size after your deployment has already been created.
Clearwater exposes some simple Key Performance Indicators over SNMP - in particular CPU usage and latency. However, the chef orchestration doesn't currently include advanced elasticity, in which these Key Performance Indicators are polled and invoke knife to resize the deployment (although this shouldn't be hard to build). I hope that helps, although I'm not sure if that was the answer you were looking for. Matt From: [email protected] [mailto:[email protected]] On Behalf Of Diego Lugones Sent: 05 November 2013 07:08 To: [email protected] Subject: Re: [Clearwater] Clearwater Digest, Vol 7, Issue 5 Hi Matt, I am trying to understand how CW provides elasticity. I am generating calls with sipp concurrently from several nodes. I expect to see a new set of Amazon instances (say bono-2, sprout-2 ... etc) after the traffic (in calls/sec) exceeds some value. However, I cannot see this. Could you point me to some part of the code, or documentation, were elasticity is implemented. How/where elasticity is defined? i.e. is there any parameter(s) I can setup to instantiate new VMs according to the calls-load, latency or failed-calls, etc. Thanks Diego
_______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/listinfo/clearwater
