VMware Aria Automation 8.16

8.18 8.17 8.16 8.14 8.13 all
Português (Brasil) 简体中文 Deutsch Español Français Italiano 日本語 한국어 Nederlands Русский 繁體中文 English

Delayed deployment in
Automation Assembler
Last Updated February 19, 2025

A virtual machine might need to be fully initialized before proceeding with
Automation Assembler
 deployment.
For example, deploying a machine that is still installing packages and starting a web server might lead to conditions where a fast user tries to reach the application before it's available.
Be aware of the following considerations when using this feature.
  • The feature makes use of the cloud-init phone_home module and is available when deploying Linux machines.
  • Phone home isn't available for Windows because of Cloudbase-init limitations.
  • Phone home can affect deployment order like an explicit dependency, but has more flexibility around timing and processing options.
  • Phone home requires a cloudConfig section in the cloud template.
  • Your creativity is a factor. Initialization commands might include embedded wait time between operations, which can be used in concert with phone home.
  • Cloud template-based phone home won't work if the machine template already contains phone_home module settings.
  • The machine must have outbound communication access back to
    Automation Assembler
    .
To introduce a deployment delay in
Automation Assembler
, add a
cloudConfigSettings
 section to the cloud template: 
cloudConfigSettings:
  phoneHomeShouldWait: true
  phoneHomeTimeoutSeconds: 600
  phoneHomeFailOnTimeout: true
Property
Description
phoneHomeShouldWait
Whether to wait for initialization, true or false.
phoneHomeTimeoutSeconds
When to decide whether to proceed with deployment even though initialization is still running. Default is 10 minutes.
phoneHomeFailOnTimeout
Whether to proceed with deployment after timing out, true or false. Note that even when proceeding, deployment might still fail for separate reasons.

Content feedback and comments