summaryrefslogtreecommitdiffstats
path: root/docs
AgeCommit message (Collapse)AuthorFilesLines
2016-09-07policy2tosca doc patch set-3shiva-charan1-0/+87
Change-Id: Icc2ad677a55bfe0f58bbfad6305674e7764422ea Signed-off-by: shiva-charan <shiva-charan.m-s@hpe.com> (cherry picked from commit ea4fe71fde55d304a23bc2f67a7cb8ec4b067e29)
2016-08-30Adjusted the docs structure according to directivesSofia Wallin4-5/+13
Created a new subdirectory /installationprocedure. Moved the featureconfig.rst and installerconfig.rst to /installationprocedure Added a feature.configuration.rst that should include needed configuration instructions. Please move relevant content to this file and remove the other two (featureconfig.rst and installerconfig.rst) Index file adjusted to updates Change-Id: I54f30b358b4e0685ff98223b1c83c14745c9259b Signed-off-by: Sofia Wallin <sofia.wallin@ericsson.com> (cherry picked from commit 5298fb1f996ab547c518b085e8c39fc5e0665bd9)
2016-08-22Remove the cyclic dependencies in vRNC definitionshangxdy1-3/+0
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>
2016-08-20Update the documents in Release Cshangxdy7-60/+191
As a developer; I want anybody who cares of project of parser to know what new features in release C; So i update the distribution documents. JIRA:PRASER-87 Change-Id: I0537ba55fa12daa2975f1b794908bca457cfd9c2 Signed-off-by: shangxdy <shang.xiaodong@zte.com.cn>
2016-07-21Substitution mappings doesn't supports propertiesshangxdy1-2/+0
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>
2016-07-01Initial release documentsJulien5-0/+108
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>
2016-06-13Create test case about nfv toscashangxdy2-37/+33
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>
2016-05-19Merge "Update the vRNC definition against the latest nfv tosca definition"julien zhang1-108/+153
2016-05-19Merge "Update the vRNC types(node types/relation types) definiton"julien zhang1-175/+32
2016-04-29Update the vRNC definition against the latest nfv tosca definitionshangxdy1-108/+153
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>
2016-04-29Update the vRNC types(node types/relation types) definitonshangxdy1-175/+32
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>
2016-04-27Update the nfv tosca definietion against the latest specshangxdy1-573/+573
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>
2016-02-26docs: fix issuesRyota MIBU9-95/+128
Change-Id: Ie0917b70674a7a16c89c8e6bc79aed5e436cabdd Signed-off-by: Ryota MIBU <r-mibu@cq.jp.nec.com>
2016-01-25update parser documentMatthewLi18-274/+95
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>
2016-01-26Merge "Yang to TOSCA output template for test case."Zhipeng (Howard) Huang1-0/+151
2016-01-18JIRA:PARSER-1 -docs for yang2tosca patch set-3shiva-charan.m-s2-0/+82
Signed-off-by: shiva-charan.m-s <shiva-charan.m-s@hp.com>
2016-01-12Yang to TOSCA output template for test case.shangxdy1-0/+151
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>
2016-01-07JIRA:PARSER-17 Clean up documentation setupzhipengh15-15/+142
Change-Id: I2863a76a5d5417c184283fdf97282c94359162dc
2015-12-22Define a general nfv Tosca template(new)shangxdy6-16/+645
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>
2015-12-21Merge "Define a TOSCA template for a vRNC(new)"julien zhang4-3/+690
2015-12-21The documents for simple vRNC TOSCA template definition(new)shangxdy3-0/+37
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>
2015-12-21New Keywods documentation for parser(new).shangxdy1-0/+113
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>
2015-12-21Define a TOSCA template for a vRNC(new)shangxdy4-3/+690
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>
2015-12-13how to use docs today in OPNFVMatthewLi2-0/+100
JIRA: PARSER-14 please see the documents under /docs directory Change-Id: I7cae579f40b61baec2b277142689be25ba1ca75f Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
2015-03-24JIRA:PARSER-1 -Basic Setup For Parser Gerrit Repohannibalhuang1-0/+1
Change-Id: Iec2941e6f11416c896fedd5d3c8ec249302c40be Signed-off-by: hannibalhuang <huangzhipeng@huawei.com>