Hi, CloudStack automatically auto scales your SSVMs as necessary, there are two global settings that control that, namely:
secstorage.capacity.standby The minimal number of command execution sessions that system is able to serve immediately(standby capacity) secstorage.session.max The max number of command execution sessions that a SSVM can handle If your number of sessions is > ( secstorage.session.max - secstorage.capacity.standby) then ACS will deploy new SSVMs until you have enough standby capacity. This could happen if ACS suddenly has to deal with many more session than it typically does. You can safely delete the extra SSVMs. Regards Alex -----Original Message----- From: Mevludin Blazevic <mblaze...@uni-koblenz.de> Sent: 06 December 2022 14:14 To: users@cloudstack.apache.org Subject: Multiple secondary storage VMs are created out of nowhere Hi all, after I added another secondary storage NFS server to my zone to deleted the old secondary storage, it seems like Cloudstack started another 5 secondary storage VMs along the "old" one. On my test environment I did not see this behavior. Moreover, in the docs, I cannot see what's triggering the management server to start multiple system vms. Any ideas? Thanks, Mevludin
