Skip to content

generate contents for ovf-env.xml when provisioning through IMDS#959

Merged
TheRealFalcon merged 3 commits into
canonical:mainfrom
anhvoms:anhvo/noOVFProvisioning
Aug 5, 2021
Merged

generate contents for ovf-env.xml when provisioning through IMDS#959
TheRealFalcon merged 3 commits into
canonical:mainfrom
anhvoms:anhvo/noOVFProvisioning

Conversation

@anhvoms
Copy link
Copy Markdown
Contributor

@anhvoms anhvoms commented Aug 3, 2021

Proposed Commit Message

generate ovf-env.xml contents when provisioning source is IMDS

Azure Linux Agent (WaLinuxAgent) waits for the ovf-env.xml file 
to be written by cloud-init when cloud-init provisions the VM. This 
file is written whenever cloud-init reads its contents from the 
provisioning ISO. 
With this change, when there is no provisioning ISO, 
DataSourceAzure will generate the ovf-env.xml file based on the 
metadata obtained from Azure IMDS.

Checklist:

  • My code follows the process laid out in the documentation
  • I have updated or added any unit tests accordingly
  • I have updated or added any documentation accordingly

@TheRealFalcon TheRealFalcon merged commit 8f42eb5 into canonical:main Aug 5, 2021
TheRealFalcon pushed a commit to TheRealFalcon/cloud-init that referenced this pull request Aug 10, 2021
…al#959)

Azure Linux Agent (WaLinuxAgent) waits for the ovf-env.xml file 
to be written by cloud-init when cloud-init provisions the VM. This 
file is written whenever cloud-init reads its contents from the 
provisioning ISO. 
With this change, when there is no provisioning ISO, 
DataSourceAzure will generate the ovf-env.xml file based on the 
metadata obtained from Azure IMDS.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants