This is an automated email from the ASF dual-hosted git repository.

paul_a pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/cloudstack-documentation.git


The following commit(s) were added to refs/heads/master by this push:
     new a97d13d  Add OVF properties documentation for VMware templates (#68)
a97d13d is described below

commit a97d13d27d9dd0ddbb7c1770c5bf4a391a73bfab
Author: Nicolas Vazquez <nicovazque...@gmail.com>
AuthorDate: Sun Sep 1 15:03:45 2019 -0300

    Add OVF properties documentation for VMware templates (#68)
    
    * Add OVF properties documentation for VMware templates
---
 source/adminguide/templates.rst        | 5 +++++
 source/adminguide/virtual_machines.rst | 5 +++++
 2 files changed, 10 insertions(+)

diff --git a/source/adminguide/templates.rst b/source/adminguide/templates.rst
index 353db9f..6c43dba 100644
--- a/source/adminguide/templates.rst
+++ b/source/adminguide/templates.rst
@@ -275,6 +275,11 @@ To upload a template:
       
 Note that uploading multi-disk templates is also supported.
 
+.. note:: 
+            Templates corresponding to appliances with 'static properties' in 
the OVF (such as virtual appliances) are also supported. CloudStack stores any 
template properties in the OVF in the database after successful template 
installation. Once the template is ready, these properties are viewed by 
selecting the template and clicking on the 'OVF Properties' tab.
+
+
+
 .. include:: templates/_bypass-secondary-storage-kvm.rst
 
 
diff --git a/source/adminguide/virtual_machines.rst 
b/source/adminguide/virtual_machines.rst
index 598e4ab..4a29fc8 100644
--- a/source/adminguide/virtual_machines.rst
+++ b/source/adminguide/virtual_machines.rst
@@ -194,6 +194,11 @@ To create a VM from a template:
 #. Be sure that the hardware you have allows starting the selected
    service offering.
 
+   .. note:: 
+      VMware only: If the selected template OVF contains static properties, 
the wizard will display these properties. Static 
+      properties do not have the concept of required and optional fields . 
Therefore CloudStack is not able
+      to enforce the population of 'important fields'.
+
 #. Click Submit and your VM will be created and started.
 
    .. note:: 

Reply via email to