Age | Commit message (Collapse) | Author | Files | Lines |
|
When import nested template, validate type error, in the
validate list lack the type of "topology_template"
Change-Id: Ic16e02f460dc59936dfc5a361a21b9533f0e5e83
JIRA: PARSER-58
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>
|
|
topology template
As a tosca-parser developer;
I want to implement the function of substitution_mapping;
So that must support the import topology template firstly
Change-Id: Ie26aab712e7870e1ec345ad654460bb84014f207
JIRA: PARSER-48
Signed-off-by: shangxdy <shang.xiaodong@zte.com.cn>
|
|
1. The input parameter my_cpus in definition of subsystem.yaml
lack the default value, so when the file subsystem.yaml is error
when used as a node template implementation.
2. The bug will be submitted to openstack community.
Change-Id: I1f912dab47fe3751d0a992b02dd2a2253af6f158
JIRA: PARSER-45
Signed-off-by: shangxdy <shang.xiaodong@zte.com.cn>
|
|
When node is selected by abstract description and the node capability
is customed, None will be return.
JIRA:PARSER-41
Change-Id: I4b3e7233f766aac61a4ffc363c000bb3ebea19ad
Signed-off-by: shangxdy <shang.xiaodong@zte.com.cn>
|
|
|
|
|
|
|
|
1、The virtualLink requirement of tosca.nodes.nfv.CP defined below:
In nodetype.py, the most code in functon of get_all_requirements is not
needed,becuase the property of requirements has realized the main logical
in current get_all_requirements. So the duplicated code will be deleted.
2、The bug will be submitted to openstack community.
JIRA: PARSER-37
Change-Id: I1a346ffc388546dd9c65a1b8d32e32859150d077
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>
|
|
Add two definition in parser:
tosca.policy.Placement.Colocate
tosca.policy.Placement.Antilocate
JIRA:PARSER-33
Change-Id: I0259bbc1ce2616dcbc28a912c34a7513e9432ff5
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>
|