| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
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>
|
shangxdy