Please enable JavaScript.
Coggle requires JavaScript to display documents.
5 VM scale set, az vmss create --custom-data cloud-init.yaml
custom-data…
5 VM scale set
Autoscale
-
conditions, rules, and limits
-
Metrics:
- Percentage CPU
- inbound outbound
- disk read write
- disk queue depth (coda I/O)
-
time aggregation
average, minimum, maximum, total, last, and count
-
scale action
cool down period
During this period, the scale rule isn't triggered again.
-
low-priority scale sets
-
Azure infrastructure frequently has underused compute resources available. A low-priority scale set provisions VMs through this underused compute capability
clean up
- Delete: The entire VM is removed
- Deallocate: The VM is stopped
When Azure needs the computing power again, you'll receive a notification about the VM that will be removed from your scale set.
If you need to clean up
custom script extension
-
- Install an application across a scale set
- update across a scale set
upgrade modes
- Automatic: anche tutte vm insieme
- Rolling: versioni differenti della app
- manual
-
-
-
horizontal scaling: load-balanced, identical VMs
- same configuration
- same applications
- load balancer
- health probe (pings)
-
-
-
-
az vmss create --custom-data cloud-init.yaml
custom-data flag specifies that the VM configuration should use the settings in the cloud-init.yaml file after the VM has been created.