Awesome! Many thanks! From: Kyle Mestery <mestery@...> Date: Wednesday, April 15, 2015 at 7:23 PM To: alagalah <alagalah@...> Cc: "Mohnish_Anumala@..." <Mohnish_Anumala@...>, "neutron-dev@..."

Hi, all: I just install ovsdb in karaf and start in , then i ran the mininet as followed this post: https://wiki.opendaylight.org/view/OVSDB_Integration:Mininet_OVSDB_Tutorial The ovs-vsctl

Hi all, I am trying to install Openstack controller with devstack in order to communicate with my Opendaylight server that is running and works fine with mininet network. The attached files are my

Kyle, Many thanks :) As long as the messages are coming in, we'll fix any bugs on the receiving end. The code is there to catch them, lets see if it works :) Ed

After digging in a bit, this *looks* like it may be because our L3 Openstack plugin (on the Openstack side) neglected to implement the router_interface CRUD... Ed

This [1] should add the calls. Note I'm unsure if they will be handled on the Neutron NB side, Ryan can answer that. Thanks, Kyle [1] https://review.openstack.org/#/c/174184/

Hi folks, When it comes to real world deployments of OpenStack, I see (a least) 2 ways by which tenants get to access subnets that are outside their networks [1]. In odl-OVSDB, we currently disallow

FWIW we see: RouterCreated messages PortCreated/Updated messages (for the interface) We DO NOT get RouterInterfaceCreated messages. From: alagalah <alagalah@...> Date: Wednesday, April 15, 2015 at

A single instance of the following meeting has been cancelled: Subject:OpenDaylight - OPNFV community sync meeting Organizer:"Dave Neary" <dneary@...> Location:Intercall (numbers below) Bridge: 915

Mohnish, I owe you your weight in beer! Hope you are at the hackfest! This works! From: <Mohnish_Anumala@...> Date: Tuesday, April 14, 2015 at 7:41 PM To: <neutron-dev@...>,

Thanks mate! Yes, we do care about the routerID and saw it in the port create message too, so thanks for confirming. We are leveraging our existing virtual router code from helium with some

Is there any wiki or document that captures: 1. Existing OVS Table pipeline 2. Guidelines for any feature looking to introduce new flows or tables I'm familiar with the pipeline created when using

Hello folks, Just wanted to give a follow up on the topic of creation of OVS port/interface for router interfaces: It is _not_ created at all. In other words, while Neutron ports are created to

Hi, We would like to know any sample examples available, for MDSAL application with DataStore Also please provide us any information how datastore can be communicated with OVSDB server? Regards, LNT

Ed and myself spent sometime debugging lack of invocation of neutron router API. Here is the mechanism to enable it: 1. Get the base local.conf from here - thanks to Flavio:

https://wiki.opendaylight.org/view/GettingStarted:Development_Environment_Setup#Edit_your_.7E.2F.m2.2Fsettings.xml

Hi, I git pull latest change to my local repo and start maven build. But I got following error: $ mvn clean install -DskipTests [INFO] Scanning for projects... [ERROR] The build could not read 1

Ok – not quite.

Doh... before was: { "network-topology:node": [ { "node-id": "ovsdb://10.10.10.10:16640", "ovsdb:port": 16640, "ovsdb:ip": "127.0.0.1" } ] }

Before and After looks the sameJ