summaryrefslogtreecommitdiffstats
path: root/docs/Chapter5/Heat/ONAP Heat Post Orchestration & VNF Configuration.rst
diff options
context:
space:
mode:
Diffstat (limited to 'docs/Chapter5/Heat/ONAP Heat Post Orchestration & VNF Configuration.rst')
-rw-r--r--docs/Chapter5/Heat/ONAP Heat Post Orchestration & VNF Configuration.rst21
1 files changed, 21 insertions, 0 deletions
diff --git a/docs/Chapter5/Heat/ONAP Heat Post Orchestration & VNF Configuration.rst b/docs/Chapter5/Heat/ONAP Heat Post Orchestration & VNF Configuration.rst
new file mode 100644
index 0000000..f36dcfa
--- /dev/null
+++ b/docs/Chapter5/Heat/ONAP Heat Post Orchestration & VNF Configuration.rst
@@ -0,0 +1,21 @@
+.. Licensed under a Creative Commons Attribution 4.0 International License.
+.. http://creativecommons.org/licenses/by/4.0
+.. Copyright 2017 AT&T Intellectual Property. All rights reserved.
+
+.. _ONAP Heat Post Orchestration & VNF Configuration:
+
+ONAP Heat Post Orchestration & VNF Configuration
+--------------------------------------------------
+
+Heat templates should contain a minimum amount of post-orchestration
+configuration data. For instance, *do not* embed complex user-data
+scripts in the template with large numbers of configuration parameters
+to the Heat template.
+
+- VNFs may provide configuration APIs for use after VNF creation. Such
+ APIs will be invoked via application and/or SDN controllers.
+
+*Note:* It is important to follow this convention to the extent possible
+even in the short-term as of the long-term direction.
+
+