This is an automated email from the ASF dual-hosted git repository.
dahn pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/cloudstack-documentation.git
The following commit(s) were added to refs/heads/main by this push:
new 4ca721b instance: note on metadata (#402)
4ca721b is described below
commit 4ca721b9ef8c3822344472db44540e5b1268ccb8
Author: Abhishek Kumar <[email protected]>
AuthorDate: Thu Jan 16 15:43:20 2025 +0530
instance: note on metadata (#402)
Signed-off-by: Abhishek Kumar <[email protected]>
---
source/adminguide/virtual_machines.rst | 13 +++++++++++++
1 file changed, 13 insertions(+)
diff --git a/source/adminguide/virtual_machines.rst
b/source/adminguide/virtual_machines.rst
index 83fa259..bb3c870 100644
--- a/source/adminguide/virtual_machines.rst
+++ b/source/adminguide/virtual_machines.rst
@@ -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
-------------------
