Skip to content

instance: note on metadata #402

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jan 16, 2025
Merged

instance: note on metadata #402

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
19a2415
instance: note on metadata
shwstppr Jun 3, 2024
188f893
Update source/adminguide/virtual_machines.rst
shwstppr Jun 5, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions source/adminguide/virtual_machines.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -205,6 +205,19 @@ following techniques:
updateVirtualMachine API. After installing the tools and updating the
Instance, stop and start the Instance.

Instance Metdata
~~~~~~~~~~~~~~~~

CloudStack provides different means for controlling an instance's metadata.

- 'extraconfig' parameter of 'deployVirtualMachine' or 'updateVirtualMachine' API methods
can be used for setting different metadata parameters for an instance.
- Zone-level configurations - 'vm.metadata.manufacturer' and 'vm.metadata.product' can be used
to set the manufacturer and product respectively in the instance metadata. However, a
custom value for these parameters may affect cloud-init functionality for the instance
when used with CloudStack datasource. One of the requirement for cloud-init functionality
to work with CloudStack datasource is that product value should contain 'CloudStack'.


Accessing Instances
-------------------
Expand Down