Excellent. Thanks Luis. Thanks, Madhu On 11/25/13, 1:02 PM, Luis Gomez wrote:

OK, thanks to the Postman examples I have the system test nailed down with the steps below: - Configure mininet in passive mode (sudo ovs-vsctl set-manager ptcp:6640) - Start mininet with

Anees, In that case I remove my disagreement, however from our point of view it is the affinity service that is providing the abstraction and the enforcement, whether affinity touches the network

Benny, your last sentence is what I am getting at -- so I don't think there is any disagreement. I'm not arguing that we don't need network abstractions separate from network virtualization. And I

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

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

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

Hi Brent, Thanks for your quick answer. I will try the examples from Postman and let you know. For the question about which controller IP should be configured in the OVS bridge, I still think

Hi Luis, Thanks so much for the feedback, this is really awesome! I threw in some thoughts, Im sure the others have additional input due to their better knowledge of the core controller but here are

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

Unfortunately, I couldn't attend the last TSC call where the issue of conflicting services in the virtualization edition was discussed further. But in reading Dave's notes, it seems there was some

Hi Hideyuki: Is this a fresh Ubuntu/Fedora box? Do you have a firewall enabled? Looks like your credentials are wrong. Make sure you have updated the IP addresses in the localrc file before running

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

FYI: For all those who tried this, I should have mentioned this is currently work in progress. The intent below is to show all the Neutron APIs being handled by the ODL NeutronAPIService. There is

Hi all, we are working on getting more videos out there to assist folks getting started. Here was one we recorded today with OVSDBs resident controller all-star Madhu. The resolution is up to 720p so

All: After returning from the OpenStack Summit in Hong Kong last week, I've spent some time working on the Neutron ML2 MechanismDriver for ODL. The good news is that after plenty of help from Ryan

If you dont have it handy or not bookmarked : https://trello.com/b/SbPFDkvW/hydrogen-ovsdb -Madhu

Hi OVSDB-Devs, I updated the Trello page with some important info : - Hydrogen release date (our first release deadline) - Code Freeze date - Member's and Timezone they work on (as discussed in IRC) -

Awesome, thanks guys. We probably should have been more specific other then filling out the ConfigurationService methods. Hugo, really appreciated your review, I submitted the patch. Thanks

Thank You Luis.