There is another way that we’ve just tried on the auto project. Prior to running the vFW heat template we create a private network and create an openstack gateway router connected to the ext net. Then we connect the private network’s subnet to the router. Then feed the name or Id of the private network to the vFW template as the public network in the .env file. When the heat template connects the VM to this private network it is fine and the vim can reach the internet to retrieve things like install scripts.
The idea is a user modification to the openstack environment that doesn’t require a change to the vFW heat template. This might be enough for you. > On May 5, 2018, at 8:29 PM, Badr Eddine Aouled Yahia > <[email protected]> wrote: > > Thank you for your response. > I fully agree that openstack bad configurations are the cause of this > problem. > In fact, i dont have full control on openstack infra, so i think that adding > floating ip resources to heat templates will solve the problem but i am not > sure that onap will allow it according to onap heat specifications. > Do u think it could work this way? > >> Le dim. 6 mai 2018 à 02:02, PLATANIA, MARCO (MARCO) >> <[email protected]> a écrit : >> 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]> 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
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
