The issue is that your openstack platform is not configured to allow VMs to be directly attached to the external or provider network. I don’t know how to change this configuration in openstack but I’m pretty positive that that is the issue.
Marco On Sat, May 5, 2018 at 11:21 AM -0400, "Badr Eddine Aouled Yahia" <[email protected]<mailto:[email protected]>> wrote: Hello, I am playing the vFWCL use-case on Amsterdam release and i am now on the step of the creation of the VF modules, i have done all the previous steps successfully and now i am facing this problem: when creating the vf modules, i get number of attemps exceeded, but thes problems is exactly the creation of an external interface for the VMs to access the public net. I watched the VMs on openstack created successefully but when it comes to attribute ips, it rolls back on the mso container in var/log/ecomp/MSO/VnfAdapter/ logs, i fount this exception "It is not allowed to create an interface on external network" I doubt that there is a problem in the heat templates because i have deployed a simple service with a single vnf (freeRadius) with well configured resources and parameters (router interface, floating ip ...) in the heat templates. In the vFW heat templates, this kid of parameters and resources is not specified but all the tutorials in ONAP does not add any resources or parameters to the vFWCL heat so i am a little bit confused. Does anyone have an idea how to solve this problem without the need to modify the heats for the vFWCL with hardcoded things? or even to what this problem could be related? Thanks community :)
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
