You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 14, 2021. It is now read-only.
It appears that the Azure API does not expose functionality to start up an arbitrary number of VMs simultaneously, like OpenStack and AWS do. The result of this is that if you want a fleet of n VMs, you must wait for the Deployer to create n VMs serially* before Ansible begins the provisioning process.
It would be nice if the Deployer could run batchSize threads to create the VMs at the same time to speed up the fleet creation process.
The text was updated successfully, but these errors were encountered:
I think Reaping in Azure suffers the same problem (It's done one machine at a time, rather slow if there's a large number that need to be reaped all at once), so maybe have threads, each thread reaping one machine. Should speed things up a little bit.
It appears that the Azure API does not expose functionality to start up an arbitrary number of VMs simultaneously, like OpenStack and AWS do. The result of this is that if you want a fleet of n VMs, you must wait for the Deployer to create n VMs serially* before Ansible begins the provisioning process.
It would be nice if the Deployer could run batchSize threads to create the VMs at the same time to speed up the fleet creation process.
The text was updated successfully, but these errors were encountered: