1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
|
.. This work is licensed under a Creative Commons Attribution 4.0 International License.
.. http://creativecommons.org/licenses/by/4.0
==============================
Introduction of Parser Project
==============================
In NFV, various templates (such as descriptors, records and so on) are utilized
to describe the deployment requirements (such as basic VM requirements – vCPU,
memory, storage, as well as the NFV acceleration management requirement such as
Huge Pages support, SR-IOV, NUMA affinity, DPDK support etc.),
the post-instaniation records (such as storage usage report, CPU performance
report etc.) or other purposes. However in order to make these templates
adaptable and feasible for purpose like deployment orchestration/automation,
certain tooling mechanism that provides template translation is necessary.
Project Parser will help to provide such tooling mechanism, by parsing Telecom
operators’ descriptors/records into TOSCA/CAMP templates and then further
translate TOSCA/CAMP templates into certain common templates, which could be
used in IaaS orchestration projects like OpenStack Heat.
For Release B, Parser offers the following capabilities:
* Integration of Heat-Translator Liberty release code. (both heat in-tree code and standalone package are provided)
* Yang2Tosca module which offers the capability to translate yang based
scriptors to tosca formate templates. Users could further use Heat-translator
module to translate this tosca template to Heat Orchestration template.
Yang2Tosca module could be installed seperately after user installed
OPNFV B release platform.
* The "parser_new_keywords" document demonstrate a set of keywords concluded by
Parser team that need to be supported in tosca to heat translation. However
it should be noted that these keywords only serve as a roadmap. We will start
from Release C to indicate which specific set of keywords are supported in
Parser.
* The "vRNC_tosca_intro" document describes Parser's use case analysis on vRNC scenario.
The "example" folder contains examples of tosca-nfv standard and vRNC scenario.
See also https://wiki.opnfv.org/parser.
For Release C, Parser offers additional capabilities:
* Policy2Tosca module which enables policy related fields in tosca could be translated
into heat orchestration template correctly. Policy2Tosca module could be installed seperately
after user installed OPNFV C release platform.
* Tosca2Heat enhancements which includes a set of feature addons (such as substitution mapping)
for OpenStack tosca-parser module which is integrated in the OPNFV C release platform. And the
main details are listed below:
** support substitution mapping semantic in tosca-parser:
- support parse and validation about substitution mapping definition;
- support import nested template;
- support deployment a node which is substituted by a template;
- support deployment a template alone which has substitution mapping definition.
** afinity and anti-affinity support when deploy servers:
- tosca.policies.Placement.Colocate;
- tosca.policies.Placement.Antilocate;
** add validation about input parameters;
** add high availability and block volume in compute translation;
** add ip output in compute translation;
** add deployment a whole vRNC testcase with parser.
* Additional testing support.
|
