Hi folks, Just started writing system test plan for OVSDB and I found one issue, one possible improvement and one general question. 1) Lets starts with the issue: with a controller with 2 IP interface

Resending with a link instead of an attachment ---- Anees, I have to disagree with you on the need for the Affinity Service to touch the network. Yes, we do not need yet another virtualization impleme

Hi Luis, Exactly. The correct solution is to identify the appropriate Controller-ip-address to set based on the reachability information towards the switch via OVSDB. And as Brent suggested, this is w

Anees, I have to disagree with you on the need for the Affinity Service to touch the network. Yes, we do not need yet another virtualization implementation, but this is not about virtualization is abo

Hi kyle, Thank you for sharing this information! I checked out the devstack tree from here. git clone https://github.com/CiscoSystems/devstack.git And, setup my local.conf and run stack.sh. However, I

Hi Thomas, Thank you very much for sharing this information! I’ll try the patch. Regards, Hideyuki Tai

Team, As most of you know already, we made significant progress on the Neutron integration and we will have the OF1.0 based GRE overlay support completed anytime now. All the corresponding code has be

Hey guys, Do we have a document describing the call flow between Neutron and ODL? Would like to use that as a basis to put the same functionality in CloudStack. I’ve already got some of the skeleton w

Hi Kyle, OpenDove, VTN & OVSDB devs, Since we all have integrations completed with the Neutron nb-apis and these southbound drivers (ovsdb, open-dove, vtn) cannot co-exist in the same virtualization e

Team, After couple of weeks of integration effort, we finally have a working Multi-node DevStack setup running Fedora 19 with Neutron ML2 opendaylight plugin integrated and working nicely using the OV

In addition to the basic metadata setting/getting, the affinity engine has a way to set forwarding rules for traffic redirection. This is the feature required for Radware. We have a couple of options

Hi Suchi, Good questions. I will not pretend to be an expert in this area as I have had little time to dig into these projects unfortunately. My reaction/response is therefore one of practicality. We

So from what I understand from this and other previous conversations, it looks like there are 2 trends for the Virtualization edition: 1) Run all apps together but try to use only one virtualization a

As we've discussed at some length, Affinity is not in the same category of function as the virtualization implementations, and also doesn't implement the Neutron APIs, so I don't think the issue of mu

Hi Madhu, I completely agree with your opinion. Regards, Hideyuki Tai

Madhu, I don't think this is the right way to handle this -- IMO Neutron shouldn't need to be aware of details of the virtualization implementation. In keeping with the notion of Neutron being focused

IMHO VTN,Dove,Affinity are the virtualization solution on top of ODL platform and openstack should be agnostic of these virtualization solution. ODL should be a southbound for openstack rather then sp

Ok, I'll schedule a meeting to decide resolution for next release.

Just a final note, if the intention for next release is to have a better harmonization among virtualization apps, I think option 1) goes more on the right direction.

Hi all Today, i follow https://wiki.opendaylight.org/view/OVSDB_Integration:Mininet_OVSDB_Tutorial section Clone the OVSDB Repo and Insert into Controller, to compile ovsdb neutron, but i get the foll