tosca-parser error with nfv yaml file
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
TOSCA Parser |
New
|
Undecided
|
Unassigned |
Bug Description
Dears,
I have started using tosca-parser module but I got the following error.
Kindly find bellow my .yaml file.
tosca = ToscaTemplate(path, parsed_params, a_file)
File "/usr/local/
self.
File "/usr/local/
None)
File "/usr/local/
self.groups = self._groups()
File "/usr/local/
self.
File "/usr/local/
custom_defs)
File "/usr/local/
if type is not None else None
File "/usr/local/
if self.DESCRIPTION in self.defs:
TypeError: argument of type 'NoneType' is not iterable
127.0.0.1 - - [31/Oct/2017 12:33:35] "POST /deploy_template HTTP/1.1" 500 2641
For more information, the input parameters for the following source code line are:
tosca = ToscaTemplate(path, parsed_params, a_file)
#path= the path to the yaml file
#parsed_params={}
#a_file=True
I appriciate your support to fix this issue.
Thanks in advance.
Best regards.
#######
tosca_definitio
description: This is a basic example for test
topology_template:
inputs:
network_name:
type: string
default: admin_internal_net
odl:
type: string
default: 192.168.111.28:8181
node_templates:
VM1:
type: tosca.nodes.Compute
capabilities:
# Host container properties
host:
# Guest Operating System properties
os:
# host Operating System image properties
type: sfc_client
VM2:
type: tosca.nodes.Compute
capabilities:
# Host container properties
host:
# Guest Operating System properties
os:
# host Operating System image properties
type: sfc_client
VM3:
type: tosca.nodes.Compute
capabilities:
# Host container properties
host:
# Guest Operating System properties
os:
# host Operating System image properties
type: sfc_client
my_network:
type: tosca.nodes.
properties:
my_port1:
type: tosca.nodes.
requirements:
- binding:
node: VM1
- link:
node: my_network
my_port2:
type: tosca.nodes.
requirements:
- binding:
node: VM2
- link:
node: my_network
my_port3:
type: tosca.nodes.
requirements:
- binding:
node: VM3
- link:
node: my_network
VNF1:
type: tosca.nodes.nfv.VNF
properties:
attributes:
type: dpi
address: 10.100.0.105
port: 40000
nsh_aware: true
requirements:
- host: VM1
CP11: #endpoints of VNF1 linked to VL1
type: tosca.nodes.nfv.CP
properties:
attributes:
IP_address: 10.100.0.105
interface: ens3
port: 30000
requirements:
- virtualBinding: VNF1
- virtualLink: VL1
VNF2:
type: tosca.nodes.nfv.VNF
properties:
attributes:
type: firewall
address: 10.100.0.106
port: 40000
nsh_aware: true
requirements:
- host: VM2
CP21: #endpoints of VNF2 linked to VL1
type: tosca.nodes.nfv.CP
properties:
attributes:
IP_address: 10.100.0.106
interface: ens3
port: 30000
requirements:
- virtualBinding: VNF2
- virtualLink: VL1
VNF3:
type: tosca.nodes.nfv.VNF
properties:
attributes:
type: napt44
address: 10.100.0.107
port: 40000
nsh_aware: true
requirements:
- host: VM3
CP31: #endpoints of VNF3 linked to VL2
type: tosca.nodes.nfv.CP
properties:
attributes:
IP_address: 10.100.0.107
port: 30000
interface: ens3
requirements:
- virtualBinding: VNF3
- virtualLink: VL1
VL1:
type: tosca.nodes.nfv.VL
properties:
vendor: HP
attributes:
type: ip
Forwarding_
type: tosca.nodes.nfv.FP
description: the path (CP11->CP21->CP31)
properties:
policy:
requirements:
- forwarder: CP11
- forwarder: CP21
- forwarder: CP31
#####
# VNF Forwarding Graph nodes and the associated
# Network Forwarding Paths
#####
groups:
VNF_FG1:
type: tosca.groups.
description: VNF forwarding graph
properties:
vendor:
version:
members: [ Forwarding_path1 ]
outputs:
vnf1_ip:
description: The private IP address of the VNF container1.
value: { get_attribute: [VM1, private_address] }
vnf2_ip:
description: The private IP address of the VNF container2.
value: { get_attribute: [VM2, private_address] }
vnf3_ip:
description: The private IP address of the VNF container3.
value: { get_attribute: [VM3, private_address] }
Hi David, are you using any specific release of tosca-parser? or master version? Also subscribing Bob to this bug. Thanks!