diff options
author | shangxdy <shang.xiaodong@zte.com.cn> | 2016-09-07 16:22:31 +0000 |
---|---|---|
committer | Gerrit Code Review <gerrit@172.30.200.206> | 2016-09-07 16:22:31 +0000 |
commit | ab3d502d62346220a9ddb6432964fe14424267e3 (patch) | |
tree | 1d9fa537f3ef8863e63073a1265aa9f4a715886a /tosca2heat/heat-translator/translator/tests/data/vRNC/README.txt | |
parent | 3758010f2946c953670845646579c54564ff029a (diff) | |
parent | d59d5fadc2ac8989eb5577618cc93e71861c4b8a (diff) |
Merge "Create translation test code for vRNC" into stable/colorado
Diffstat (limited to 'tosca2heat/heat-translator/translator/tests/data/vRNC/README.txt')
-rw-r--r-- | tosca2heat/heat-translator/translator/tests/data/vRNC/README.txt | 22 |
1 files changed, 22 insertions, 0 deletions
diff --git a/tosca2heat/heat-translator/translator/tests/data/vRNC/README.txt b/tosca2heat/heat-translator/translator/tests/data/vRNC/README.txt new file mode 100644 index 0000000..9ea77a4 --- /dev/null +++ b/tosca2heat/heat-translator/translator/tests/data/vRNC/README.txt @@ -0,0 +1,22 @@ +README: + +This CSAR contains all definitions that are required for deploying a simple +vRNC(virtual Radio Network Controller) on a cloud. + +Entry information for processing through an orchestrator is contained in file +TOSCA-Metadata/TOSCA.meta. This file provides high-level information such as +CSAR version or creator of the CSAR. Furthermore, it provides pointers to the +various TOSCA definitions files that contain the real details. +The entry 'Entry-Definitions' points to the definitions file which holds the +service template for the workload. +'Entry-Definitions' is optional. An orchestrator can also process the contents +like this: +1) Read in and process each definitions file. +2) For each definitions file: + 2.1) Read in all * type definitions (node types, capability types, etc.) and + store them in an internal map +3) Verify and build dependencies (e.g. inheritance) between all type definitions + previously read in. Orchestrator built-in types (e.g. TOSCA base types) are + also considered in this step. +4) Process the actual service template (the file with a node_templates section). + Validate using previously obtained type information.
\ No newline at end of file |