Age | Commit message (Collapse) | Author | Files | Lines |
|
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>
|
|
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>
|
|
Change-Id: I356c88886d698f4527a65696f17f946aa6d07a32
Signed-off-by: Aric Gardner <agardner@linuxfoundation.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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>
|
|
Update the vRNC definition according to the latest vRNC type.
include node_templates, groups, policies and outputs.
JIRA:PARSER-31
Change-Id: Ie69a8e4480188ffad8247d68e5c15085bbb44848
Signed-off-by: shangxdy <shang.xiaodong@zte.com.cn>
|
|
Update the vRNC type definition according to the nfv tosca definiton.
include MM, CM, DM and LB.
JIRA:PARSER-35
Change-Id: I3017c93081bc77fc2ac1e4633f4232f130f6b4de
Signed-off-by: shangxdy <shang.xiaodong@zte.com.cn>
|
|
Base types are modified:
1.tosca.nodes.nfv.VDU:
from tosca.nodes.SoftwareComponent to tosca.nodes.Compute
2.tosca.nodes.nfv.CP:
from tosca.nodes.Root to tosca.nodes.network.Port
3.tosca.nodes.nfv.VL:
from tosca.nodes.Root to tosca.nodes.network.Network
4.tosca.relationships.nfv.VirtualBindsTo:
from tosca.relationships.ConnectsTo to tosca.relationships.network.BindsTo
5. tosca.relationships.nfv.VirtualLinksTo:
from tosca.relationships.ConnectsTo to tosca.relationships.network.LinksTo
6. tosca.capabilities.nfv.VirtualBindable: i
from tosca.capabilities.Root to tosca.capabilities.network.Bindable
7. tosca.capabilities.nfv.VirtualLinkable:
from tosca.capabilities.Root to tosca.capabilities.network.Linkable.
JIRA:PARSER-30
Change-Id: If6f32cf891a979ae88c345980930451f876ad9e0
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. minor changes for better reading(heading spaces, tail dot)
and compatible with some edit tools, such as vim
2. L20: new people To new contributors
3. L33: sequence
Change-Id: I50b89310ddf176a0872c60363b69cdf979b37abc
Signed-off-by: Julien <zhang.jun3g@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>
|
|
|
|
Change-Id: I9a2963cc2bd4a77448ed7ac623582d91ff94d60d
|
|
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>
|
|
Change-Id: Ie0917b70674a7a16c89c8e6bc79aed5e436cabdd
Signed-off-by: Ryota MIBU <r-mibu@cq.jp.nec.com>
|
|
Change-Id: I7915929ab219aa392f45f4867f34ad2dcc981c4e
|
|
|
|
JIRA: PARSER-14
document format has been updated, this patch is to improve the document
in parser project to satisfy the requirement of sphinx.
Change-Id: I629fa84a1b0333e9b59c24cdf7444733f7b35582
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
|
|
Change-Id: I271ed953474d62365094be486935e592714a22c3
|
|
Signed-off-by: shiva-charan.m-s <shiva-charan.m-s@hp.com>
|
|
As a test engineer,I want to understand how to verify the output of
yang-to-tosca based specific input.so that I can define output template.
JIRA:PARSER-16
Change-Id: Id17e86db9667715e43615195570854ae1ead5e8b
Signed-off-by: shangxdy <shang.xiaodong@zte.com.cn>
|
|
Change-Id: I48a65818a652d2e221dc8450e4f52d7ae053f3b8
Signed-off-by: Ryota MIBU <r-mibu@cq.jp.nec.com>
|
|
Change-Id: I2863a76a5d5417c184283fdf97282c94359162dc
|
|
|
|
|
|
Define a general nfv Tosca template, which supports ETSI/MANO standard.
Recheck for changed documents architecture.
JIRA:PARSER-6
Change-Id: I0c6f0571c8a5dffbe0bc281d68f2b9542952bf7d
Signed-off-by: shangxdy <shang.xiaodong@zte.com.cn>
|
|
|
|
As a Parser developer,
I want to konwn the detailed description of TOSCA definition for to a vRNC,
so that I can translate it to heat-template.
Recheck for changing file format from md to rst.
JIRA:PARSER-13
Change-Id: Id666eb076e1ec3bbd428f9a1b6bad1491e3f0d7a
Signed-off-by: shangxdy <shang.xiaodong@zte.com.cn>
|
|
As a user,I need a manual and want to understand how to use all and
the new introduced keywords to define a vRNC, so that I can use it
to define myown vRNC.
Recheck for changing file format from md to rst.
JIRA:PARSER-10
Change-Id: Ie7e16ac6f9eede57462d4c83e8acad51ceecc857
Signed-off-by: shangxdy <shang.xiaodong@zte.com.cn>
|
|
Define a vRNC(an VNF of Radio Network Controller) by using TOSCA template.
Recheck for changed documents architecture.
JIRA:PARSER-7
Change-Id: I3164b262b2cf3e82f0afc6e3663331d886741c96
Signed-off-by: shangxdy <shang.xiaodong@zte.com.cn>
|
|
|
|
JIRA: PARSER-14
please see the documents under /docs directory
Change-Id: I7cae579f40b61baec2b277142689be25ba1ca75f
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|