Age | Commit message (Collapse) | Author | Files | Lines |
|
Submit initial release documents according to opnfvdocs project
requirement in Berlin Summit
JIRA: PARSER-60
Change-Id: I6eb650259c4da521aee1918842a6d0bfe06a6a0d
Signed-off-by: Julien <zhang.jun3g@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>
|
|
|
|
|
|
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>
|
|
Change-Id: Ie0917b70674a7a16c89c8e6bc79aed5e436cabdd
Signed-off-by: Ryota MIBU <r-mibu@cq.jp.nec.com>
|
|
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>
|
|
|
|
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: 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>
|
|
Change-Id: Iec2941e6f11416c896fedd5d3c8ec249302c40be
Signed-off-by: hannibalhuang <huangzhipeng@huawei.com>
|