summaryrefslogtreecommitdiffstats
path: root/docs/Chapter5/Heat/ONAP Heat Post Orchestration & VNF Configuration.rst
blob: f36dcfae0521c2df682850a8c6e10f09c72f3248 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
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.