Added warning about ConfigDrive

The ConfigDrive data files will be added only if the user also provides
a CloudInit file although this is not enforced by checks.
The new text mentions that without providing a CloudInit file
no Cloud Init Data Source will be generated and no warning
will be given.

Change-Id: Icfa0247d1e97cd2e902caeb1ef55314ea9071311
Signed-off-by: Dan Andresan <Dan.Andresan@enea.com>

1 files changed, 4 insertions, 1 deletions

diff --git a/doc/book-enea-nfv-access-getting-started/doc/getting_started_ucpe_manager.xml b/doc/book-enea-nfv-access-getting-started/doc/getting_started_ucpe_manager.xml
index ed1876e..609da64 100644
--- a/doc/book-enea-nfv-access-getting-started/doc/getting_started_ucpe_manager.xml
+++ b/doc/book-enea-nfv-access-getting-started/doc/getting_started_ucpe_manager.xml
@@ -1745,7 +1745,10 @@ export CLASSPATH=.:$JAVA_HOME/jre/lib:$JAVA_HOME/lib:$JAVA_HOME/lib/tools.jar
             create an instance for multiple VNFs, they will be prompted to
             provide a data file for each entry in this table. Each type of VNF
             will require different cloud-init files, e.g.: a license
-            file.</para>
+            file. The data files will be added to the cloud-init image that the user 
+            provides at the instantiation of the VNF. If the cloud-init image is not 
+              provided, no Cloud-Init Data Source will be created for that VNF
+            and there will be no warning.</para>
           </listitem>
         </orderedlist>