summaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)AuthorFilesLines
2016-09-30Update the tosca2heat documents for release Coloradoshangxdy1-2/+21
Update the tosca2heat documents for release Colorado: 1. add brief description for feature or function; 2. add list of tosca keywords in parser. 3. other improvement. JIRA:PARSER-107 Change-Id: I25b46ec2490885534b54cce4bcf5fa030e882785 Signed-off-by: shangxdy <shang.xiaodong@zte.com.cn>
2016-09-20Parser Release C RC1 docs final clean upzhipengh6-22/+170
Change-Id: Ib74e8cbaaa6397e9f9f1e9eba35d7d2f8e8d5108 Signed-off-by: zhipengh <huangzhipeng@huawei.com>
2016-09-19Delete not used property from vRNCshangxdy3-21/+1
Delete not used property from vRNC,such as activestatus and id. Change-Id: I14b4563663d220c241440dff0244ccbadff7912b Signed-off-by: shangxdy <shang.xiaodong@zte.com.cn>
2016-09-19Merge "Provide file list about the difference between parser and upstreams."shangxdy2-3/+113
2016-09-19Merge "Update the upstream of tosco-parser and heat-translator to stable ↵shangxdy29-1457/+1502
release 0.6/0.5"
2016-09-16Installation doc and userguide for policy2tosca and yang2toscashiva-charan4-0/+203
Change-Id: I10e5745b75e4cdeafae28767ad8233decabf3482 Signed-off-by: shiva-charan <shiva-charan.m-s@hpe.com>
2016-09-14Provide file list about the difference between parser and upstreams.shangxdy2-3/+113
Provide a list about difference between parser project and the upstream projects, include tosco-parser and heat-project in openstack community. JIRA:PARSER-108 Change-Id: I6195fe035340e5af40f7e7a30f7d7cb1fbcdb27f Signed-off-by: shangxdy <shang.xiaodong@zte.com.cn>
2016-09-14Update the upstream of tosco-parser and heat-translator to stableshangxdy29-1457/+1502
release 0.6/0.5 Currently the parser is based on dev branch of upstream projects, include tosco-parser and heat-translator, for the colorado release of parser, it should be based on a stable version, so it's necessary to update the upstream version to 0.6/tosca-parser and 0.5/heat-translator. JIRA:PARSER-106 Change-Id: I8fb043068d25188c47e5648e1b66184446ac82d6 Signed-off-by: shangxdy <shang.xiaodong@zte.com.cn>
2016-09-13Add resources and outputs informantion in scriptshangxdy1-11/+25
Add debug information when run script in functest. Change-Id: I4e86d6fb4b2285d96c131163b8f72942eafa2563 Signed-off-by: shangxdy <shang.xiaodong@zte.com.cn>
2016-09-12Merge "Add keys validation testcase in substitution_mapping class"shangxdy3-6/+54
2016-09-12Merge "Replace test file from test_tosca_nfv_sample with vRNC"shangxdy1-9/+24
2016-09-12Merge changes from topics ↵shangxdy46-15/+208
'Add_property_software_config_transport_in_compute_node', 'Add_signal_transport_property_in_softwaredeployment' * changes: Add property of software_config_transport in compute node Add signal_transport in software deployment resource
2016-09-10Merge "index and intro docs update for Rel C"zhipengh2-0/+13
2016-09-09Add keys validation testcase in substitution_mapping classshangxdy3-6/+54
Add keys validation in class of substitution_mapping according to specification of http://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.0/TOSCA-Simple-Profile-YAML-v1.0.html: 1) Substitution mapping only supports keys of node_type, capabilities and requirements; 2) The key of node_type is required, the others are optional. JIRA:PARSER-80 Change-Id: Icd3284349175429e5ba5e52814819a6790f0e831 Signed-off-by: shangxdy <shang.xiaodong@zte.com.cn>
2016-09-09Add property of software_config_transport in compute nodeshangxdy45-12/+92
According to hot syntax, when deploy software into compute, it shall include software_config_transport property in server resource, because the openstack environment configuration may not support the default value. so the software_config_transport shall be specified. JIRA:PARSER-105 Change-Id: Iefe50400ae2008214bb8cb98dde719130553b3bf Signed-off-by: shangxdy <shang.xiaodong@zte.com.cn>
2016-09-09Add signal_transport in software deployment resourceshangxdy18-3/+116
According to hot syntax, when deploy software, it shall include signal_transport property, or will use default value NO_SIGNAL, but the openstack environment configuration may not support the default value. so the signal_transport shall be specified. JIRA:PARSER-104 Change-Id: Ifd01cd55c7daf538efb32f44a8d278cf3058af05 Signed-off-by: shangxdy <shang.xiaodong@zte.com.cn>
2016-09-09Replace test file from test_tosca_nfv_sample with vRNCshangxdy1-9/+24
About parser test in funkiest, replace test case from test_tosca_nfv_sample.yaml to vRNC.yaml, which include more VDUs, VLs and CPs. JIRA:PARSER-103 Change-Id: I7a1c5937f644f7269c0263e681b8778bf98a1406 Signed-off-by: shangxdy <shang.xiaodong@zte.com.cn>
2016-09-08Emergence merged for unit test.shangxdy1-8/+0
Reversed merged caused the unit test error, i think this is the ci system's bug. Change-Id: I6d29f7f11cc0a78c695f179aa30c93545a575584 Signed-off-by: shangxdy <shang.xiaodong@zte.com.cn>
2016-09-07Merge "Create translation test code for vRNC"shangxdy8-39/+1302
2016-09-07Merge "Add deployment scripts for vRNC"shangxdy11-0/+44
2016-09-07Merge "Fix network info output about compute node"shangxdy20-102/+6
2016-09-07Create translation test code for vRNCshangxdy8-39/+1302
Create translation test code from tosca to hot about vRNC definition. JIRA:PARSER-50 Change-Id: I04d5e776b40a856f95548f5d751aeb51220856eb Signed-off-by: shangxdy <shang.xiaodong@zte.com.cn>
2016-09-07index and intro docs update for Rel Czhipengh2-0/+13
Change-Id: Ie00fe27841522a4f324e598e37bffbdadac2ec15 Signed-off-by: zhipengh <huangzhipeng@huawei.com>
2016-09-07Merge "policy2tosca doc patch set-3"Zhipeng (Howard) Huang1-0/+87
2016-09-05policy2tosca doc patch set-3shiva-charan1-0/+87
Change-Id: Icc2ad677a55bfe0f58bbfad6305674e7764422ea Signed-off-by: shiva-charan <shiva-charan.m-s@hpe.com>
2016-09-02Merge "[NFV] Reduce instance requirements"xiaodong shang2-6/+6
2016-09-01Fix parser run error when attach blockstorage.shangxdy2-4/+4
The error is below: CREATE_FAILED Error: resources.tosca.relationships.attachesto_1: Failed to attach volume dc1cd8fb-9cf3-42c2-bb3e-6a24ba354003 to server fded0b07-9da2-4d9c-aedc-fefd22ee1efb - Invalid input for field/attribute device. Value: /data. u'/data' does not match '(^/dev/x{0,1}[a-z]{0,1}d{0,1})([a-z]+)[0-9]*$' JIRA:PARSER-102 Change-Id: Ie30c669ab5eeddbcd8bc33d648b8cd33d9942333 Signed-off-by: shangxdy <shang.xiaodong@zte.com.cn>
2016-09-01[NFV] Reduce instance requirementsMichael Polenchuk2-6/+6
In order to keep requirements of cpu/ram at minimum reduce their values. Change-Id: I624f9638d6207a2dc8a6f83e47ad4e6a0f221595 Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
2016-09-01Merge "Fix BlockStorageAttachment bug when translate compute node"julien zhang3-3/+35
2016-09-01Fix network info output about compute nodeshangxdy20-102/+6
In the template version of 2013-05-23, the intrinsic function of get_attr doesn't support keys or indexes, it requires 2014-10-16 or higher, the syntax is below: get_attr: <resource name> <attribute name> <key/index 1> (optional) not support in 2013-05-23 <key/index 2> (optional) not support in 2013-05-23 So the translation about compute node's ip address only uses two parameters currently. JIRA:PARSER-101 Change-Id: I51e5d7c04c329ede69ff3be61bbee2941b56ea93 Signed-off-by: shangxdy <shang.xiaodong@zte.com.cn>
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>
2016-08-28Fix BlockStorageAttachment bug when translate compute nodeshangxdy3-3/+35
Currently, when translate compute node with local_storage and high_availability, there is not BlockStorageAttache resource created about block storage, and only BlockStorage created. If only local_storage requirement in compute node, the result is correct. The reason is the function logic of _get_attachment_node is error. and the patch will fixit. JIRA:PARSER-100 Change-Id: I36456089ae65102d4b17797d266c850d8c16b29d Signed-off-by: shangxdy <shang.xiaodong@zte.com.cn>
2016-08-25Make patch for provider network when run in functestshangxdy1-9/+52
When run parser in functest, we don't know the provider network about Openstack, if use vxlan or vlan or gre as default, it may be error. So it's necessary to path the provider network definition in yaml, and select it in runtime. JIRA:PARSER-99 Change-Id: I20ae6b213870b18cee094d43ce2ba958f53b111e Signed-off-by: shangxdy <shang.xiaodong@zte.com.cn>
2016-08-25Modify the test script for reducing the test timeshangxdy1-73/+65
Currently in functest, when deploy a template use parser, the timeout is a constant value of 3min, It can be set according to the actual running time. Additionally, its necessary to add more debug information. JIRA:PARSER-98 Change-Id: I11b667247644dbd64ecd6e8b0b1015240301279d Signed-off-by: shangxdy <shang.xiaodong@zte.com.cn>
2016-08-24Add deployment scripts for vRNCshangxdy11-0/+44
Add deployment scripts for vRNC when deploy vRNC in openstack. JIRA:PARSER-49 Change-Id: I13092f9939a3fe6710e50e2191a82b8cdc25e3e3 Signed-off-by: shangxdy <shang.xiaodong@zte.com.cn>
2016-08-23Bug: there is not segmentation_id in resource ofshangxdy3-2/+15
tosca.nodes.network.Network In current implementation of tosca.nodes.network.Network translation, the property of segmentation_id is included, but it doesn't exist in hot syntax, so it will be deleted from current code. JIRA:PARSER-96 Change-Id: I2bd32be887a07f77f7dad3fca469464f124e628f Signed-off-by: shangxdy <shang.xiaodong@zte.com.cn>
2016-08-23Replace the policie types with parent type when judging policy nodeshangxdy1-8/+10
template in HotResource In class of HotResource, because the policy node template has not interface property, so it is excepted when get all operation from node, but the policy types are enumerated, they are can expressed with parent type. JIRA:PARSER-97 Change-Id: I6393dcaefc774af3aa627ffa287b75083a173f3f Signed-off-by: shangxdy <shang.xiaodong@zte.com.cn>
2016-08-22policy2tosca patch set-6shiva-charan.m-s23-0/+946
Signed-off-by: shiva-charan <shiva-charan.m-s@hpe.com>
2016-08-22Merge "Remove the cyclic dependencies in vRNC definition"julien zhang2-6/+0
2016-08-22Merge "Add high_availability test case"julien zhang2-0/+49
2016-08-22Remove the cyclic dependencies in vRNC definitionshangxdy2-6/+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-22Add high_availability test caseshangxdy2-0/+49
As a template designer; I want to define a vdu with high availability; So i will add test case to violate high_availability requirement in VDU; JIRA:PARSER-94 Change-Id: Icd35e5a533231395a2174cdc20b747a9ab803599 Signed-off-by: shangxdy <shang.xiaodong@zte.com.cn>
2016-08-22Modify the stack name to template file name when deploy stack useshangxdy2-4/+7
heat-translator When deploy a stack online, it can specify a name as a input name（which was added by issue PARSER-91), but the parameter is optional, if no specified name, currently the default stack name is shown below: 'heat' + first part of a random uuid For readable and to be easier founded, the default name will be improved to be the follow: 'heat' + filename of template file + first part of a random uuid. JIRA:PARSER-93 Change-Id: Ib8f5fd18bf4e57d2424c2a439aa6db8feead44cd 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-08-19Merge "Provide a specific stack_name when deploy a template use heat-translator"julien zhang1-3/+12
2016-08-19Merge "Judge volume node is error when translate compute node"julien zhang1-2/+6
2016-08-19Merge "JIRA:PARSER-1 -XSLT script for YANG to TOSCA"julien zhang1-111/+217
2016-08-19Judge volume node is error when translate compute nodeshangxdy1-2/+6
Currently, when translate a compute node in heat-translator, code is below: for requires in requirements: for value in requires.values(): if isinstance(value, dict): for node_name in value.values(): for n in self.nodetemplates: if n.name == node_name: volume_name = node_name break else: # unreachable code ! for n in self.nodetemplates: if n.name == node_name: volume_name = node_name break It's error in nfv tosca because there are more than one requirements, So the unreachable code will reach. Notes: the fix will submit to Openstack community. JIRA:PARSER-92 Change-Id: Ife9c0d28ebe236c04d9d2c02f0025cf774bf6208 Signed-off-by: shangxdy <shang.xiaodong@zte.com.cn>
2016-08-19Provide a specific stack_name when deploy a template use heat-translatorshangxdy1-3/+12
Currently, the stack ame of a template is random when use heat-translator online, and there is not any other feedback information except success or failure, the result is not very convenient. So it is necessary to provide a stack name when deploy a template. Note: the improvement will submit to openstack community. JIRA:PARSER-91 Change-Id: Ia5f99c38301211dfb9c21a8b10dd31a50b82f966 Signed-off-by: shangxdy <shang.xiaodong@zte.com.cn>
2016-08-17JIRA:PARSER-1 -XSLT script for YANG to TOSCAshiva-charan1-111/+217
Change-Id: I29f80ab21354af452fc95b155c04171001f9577e Signed-off-by: shiva-charan <shiva-charan.m-s@hpe.com>