GitHub user weizhouapache added a comment to the discussion: Trying autoscaling on CloudStack
> 1. when I disabled the autoscale group (for maintenance scenario), it didn't > expunge the existing VMs. the monitoring, scale up/down are disabled. existing VMs will not be touched. (I believe users do not expect the VMs to be expunged) > 2. Also another one where I rebooted the whole system, the existing autoscale > VMs from previous session are turned off and the autoscale group just chooses > to create new ones instead. I heard this was a common problem on cloudstack > where instances aren't automatically turned back up after a system reboot so > it might be related to that. yes, the stopped VM is not considered as a working vm, so AS group will spin up a new vm. You can update the VM to HA enabled in multiple ways - stop vm and update it to ha-enabled, or - create service offerin with HA-enabled, or - set global configuration "force.ha" to true, and so on > 3. Just to add another one as well when I expunged all the previous autoscale > VM from machine 1-5, the autoscale group just created number 6 onwards > instead of repeating from 1. yes, the name of the autoscale vms use consequent number. IMHO, using vms with same number in the name is confusing GitHub link: https://github.com/apache/cloudstack/discussions/11111#discussioncomment-13626253 ---- This is an automatically sent email for users@cloudstack.apache.org. To unsubscribe, please send an email to: users-unsubscr...@cloudstack.apache.org
