Age | Commit message (Collapse) | Author | Files | Lines |
|
Sync upstream project of tosca-parser
Change-Id: Ic707844203ea05007b3c02e9dcadb52389eb3149
JIRA:PARSER-118
Signed-off-by: shangxdy <shang.xiaodong@zte.com.cn>
|
|
Add attributes in rnc.nodes.VNF definition.
JIRA:PARSER-114
Change-Id: I8578cc89dc58202893370d367dc9923ddc1c111a
Signed-off-by: shangxdy <shang.xiaodong@zte.com.cn>
|
|
Delete not used property from vRNC,such as activestatus
and id.
Change-Id: I14b4563663d220c241440dff0244ccbadff7912b
Signed-off-by: shangxdy <shang.xiaodong@zte.com.cn>
|
|
release 0.6/0.5
Currently the parser is based on dev branch of upstream projects,
include tosco-parser and heat-translator, for the colorado release of
parser, it should be based on a stable version, so it's necessary to
update the upstream version to 0.6/tosca-parser and 0.5/heat-translator.
JIRA:PARSER-106
Change-Id: I8fb043068d25188c47e5648e1b66184446ac82d6
Signed-off-by: shangxdy <shang.xiaodong@zte.com.cn>
|
|
Create translation test code from tosca to hot about vRNC definition.
JIRA:PARSER-50
Change-Id: I04d5e776b40a856f95548f5d751aeb51220856eb
Signed-off-by: shangxdy <shang.xiaodong@zte.com.cn>
|
|
Current the high_availability definition in vRNC about active MM/CM VDUs
and passive MM/CM VDUs is cyclic dependencies, and the consequence is
deployment of vRNC may fall into a infinite loop.
The correct definition is passive VDU depend on the active VDU, but the
active VDU doesn't depend on the passive VDU.
JIRA:PARSER-95
Change-Id: I3f2fb8c0ce959878b12d7da49e2dc81596b4b528
Signed-off-by: shangxdy <shang.xiaodong@zte.com.cn>
|
|
Add input validation in class of substitution_mapping according to
specification of
http://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.0/
TOSCA-Simple-Profile-YAML-v1.0.html:
1) The properties of substituted node template which be mapped must be
in the inputs of nested service template which defines substutition
mappings;
2) The inputs of nested service template which are not in properties of
the substituted node template must have default values.
3) If the properties of node_type is required and no default value,
must provide inputs for them;
4) Property names and the input names must be the same.
JIRA:PARSER-79
Change-Id: Ie4664fe17c8279ad531ac9acec057f98d4e9281a
Signed-off-by: shangxdy <shang.xiaodong@zte.com.cn>
|
|
According to the simple tosca specification, substitution mapping only
supports key words of node_type, capabilities and requirements, but in
the definition of vRNC, add keywords of properties, so it will be
deleted
Change-Id: I45ca5f6d44410e5a6b8cdb448f3f148d63cc1376
JIRA: PARSER-67
Signed-off-by: shangxdy <shang.xiaodong@zte.com.cn>
|
|
1. Currently DM_Port_Ctrl requirement definition
requirements:
virtualBinding: DM
virtualLink: CTRL_Net_Host
shall be below:
requirements:
virtualBinding: DM_Host
virtualLink: CTRL_Net
2. In function of _load_import_template when import vRNC definition, it will
return "None, None" instead of return Null in case of no value return.
Change-Id: I81d2d471eafff8ebd77eef356e6178e1f7701a22
JIRA: PARSER-65
Signed-off-by: shangxdy <shang.xiaodong@zte.com.cn>
|
|
When run unittests through tox, some test cases are always error,
the errors are already done in openstack community, so it's
necessary to synchronise the fixes.
Change-Id: Ib29078e6cc138a474e89c6a2cc90ad7a1db1bb46
JIRA: PARSER-63
Signed-off-by: shangxdy <shang.xiaodong@zte.com.cn>
|
|
Currently the heat-translator can't translate the VDU with interface,
so VDU shall be divided into SoftComponent and VDU, and the interface
will be expressed in SoftComponent node.
Change-Id: I1f0e0c6bef88ed66edd39e21e4e6221eb15e3188
JIRA: PARSER-57
Signed-off-by: shangxdy <shang.xiaodong@zte.com.cn>
|
|
|
|
Unit test code for vRNC case.
JIRA: PARSER-34
Change-Id: Ie4a0431e3cdfd56d2ef42760da30a8f2bb6fdb5d
Signed-off-by: shangxdy <shang.xiaodong@zte.com.cn>
|
|
As a developer;
I want to known the availability of current nfv tosca
definitions about node types, capabilities types and
relationship types.
So i create some test cases to validate it.
JIRA: PARSER-34
Change-Id: Id57e38c066eea1d2090a816f5129aa95de464d32
Signed-off-by: shangxdy <shang.xiaodong@zte.com.cn>
|
|
According to the openstack comments, it's necessary to add the attribute
of address, which was deleted because the IP_address was duplication to
CP's parent's attributes.
The related modifications are refer to:
1. https://gerrit.opnfv.org/gerrit/#/c/12567.
2. https://bugs.launchpad.net/tosca-parser/+bug/1574715.
JIRA: PARSER-36
Change-Id: I6bf894cbba440013175df478cce00fa08906dc19
Signed-off-by: shangxdy <shang.xiaodong@zte.com.cn>
|
|
1、The virtualLink requirement of tosca.nodes.nfv.CP defined below:
- virtualLink:
capability: tosca.capabilities.VirtualLinkable
But the tosca.capabilities.VirtualLinkable does not exsit in simple
tosca(which is tosca.capabilities.Linkable), it should be
tosca.capabilities.nfv.VirtualLinkable in nfv tosca.
Additonally, the attribute definition of IP_address in CP is not
needed because the parent node type tosca.nodes.network.Port
also includes the same attributes ip_address.
2、The bug will be submitted to openstack community.
JIRA:PARSER-32
Change-Id: I8f70747675dd6623380493d0436d9516c545d705
Signed-off-by: shangxdy <shang.xiaodong@zte.com.cn>
|
|
Use tosca-parser and heat-translator to analyze to the basic
nfv-tosca type definitions, and use simple tosca new feature
such as policy, group and trigger, which are now supported by
the latest version of tosca-parser and heat-translator.
JIRA:PARSER-18
Change-Id: I797bcacbb5b32005d0aeb0f3f32851ac96e30f01
Signed--off-by: shangxdy <shang.xiaodong@zte.com.cn>
Signed-off-by: shangxdy <shang.xiaodong@zte.com.cn>
|