Sam, Flavio Thanks for the inputs. This allinone setup creates bridge, network & tenants. We tried setting ODL_BOOT_WAIT to 300 and in one of two attempts br-int, OF port

Sam, Thanks for the quick response and clarification. Will test and confirm this, as I was seeing some inconsistent behavior, trying to use the helium feature install set in Lithium.

Adding groupbasedpolicy-dev, which also implements a provider for neutron northbound. It seems like we should try to identify all the projects the implement a provider and have them all contribute to

Fowarding to this mail to the ovsdb-dev ML. I think that page should list all ways to integrate with OpenStack.

Good point, Sam. To do that, use something like “ODL_BOOT_WAIT=123” in local.conf — flavio

Natarajan, what all does the allinone setup do besides stack and start odl? Meaning does it try to create any bridges or networks? could you modify the allinone to add a 60s or 90s sleep in between

++Venkat

Badri, all that is needed for OepnStack and ODL integration is the odl-ovsdb-openstack feature. If the list from Helium here is why they are no longer needed: odl-base-all odl-aaa-authn

Hi, For the Helium-OVSDB integration, there is a list of features to be enabled in opendaylight given as opendaylight-user@root> feature:install odl-base-all odl-aaa-authn odl-restconf

Hi Vishal, As per my understanding in SG we have to support both stateful and stateless use cases both Ingress and Egress. We can claim Openstack parity only when both are done. Currently we are

Hi Flavio, Thank you very much! I am carefully reading those references, and I will attempt to document them in the code. Best, Marcelo WARNING / LEGAL TEXT: This message is intended only for the

Hi, I have read through ovsdb / openstack (helium), but I have issues identifiying the actual ovs port creation. Following from PortHandler.neutronPortCreated the only output I found is flow

Hi Aswin, Just to be clear, by stateless use cases do you mean you're using neither TCP Flags nor Learn action and require user to explicitly configure Ingress SG Rules to allow traffic? Default SG

Hi Vishal, Yes we are working on the provider in the net-virt. Neutron part is done , but we have to port it to MD-SAL. Currently we are working with stateless use cases and trying to achieve

Hi Flavio, Sam & All, We were testing latest neutron/lithium odl / stable kilo devstack combo in all-in-one mode few days back, using modified Flavio’s vagrant setup

Hi, I was looking for some information on the SG implementation in ODL. My understanding is that the provider in net-virt is in progress while NeutronNorthbound part of it is complete. Is this

[ccing ovsdb-dev, Anil & Hideyuki] Hello Marcelo, As you probably know, it is my intention to write part 3 of the blog to talk about DNAT’s implementation in odl’s L3 obvsd netvirt. I just need

Thanks Sam for all of the help. Problem solved.

Hi Sam, We are planning to indroduce some support of queries and filtering in MD-SAL And hopefully also NETCONF and RESTCONF (this is tracked by https://bugs.opendaylight.org/show_bug.cgi?id=2300) I