Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Autoscaling triggered by schedule and alarm and exceeds maxsize

Hi, In my OpenStack environment I'm seeing Autoscaling create more VMs than specified in maxsize when both scheduled autoscaling and alarm autoscaling (i.e. CPU usage metering) are triggered at the same time.

I'm currently using Kilo, but does anyone know if this has been implemented in recent Openstack releases or if there is a workaround?

Thanks in advance!