[Netstack] Aligning the API code with the specification

Hi all, There are currently several parts of the API implementation that are not aligned with the specification. This happened as the specification was updated while the API was being implemented, and therefore the API code now does not reflect the specification. These issues came out while dev

Re: [Netstack] Aligning the API code with the specification

Hi Salvatore, Your current line of thinking makes sense to me. I am doing a review of the branch, and will send out a response soon. We should try to get the unit tests merged soon and then create high priority "test stopper" bugs around API spec divergence and try to fix them as soon as possible.

Re: [Netstack] [Merge] lp:~netstack/quantum/quantum-unit-tests into lp:quantum

Inline with SB>> On Tue, Jul 19, 2011 at 4:46 PM, Salvatore Orlando < salvatore.orla...@eu.citrix.com> wrote: > Hi Somik, > > thanks for your review! > See my replies inline. > > > Great work on this changelist Salvatore! This was much needed. I do have > a few > > questions, while not directly r

[Netstack] Official Python version for Quantum

Hello Folks, I would like to know if we have defined an official version of Python to be used on all Quantum development. Is it 2.6 or 2.7? Is there any place on the Quantum blueprints where we have defined the supported versions of all the libraries that we are using for our development?

Re: [Netstack] Official Python version for Quantum

To add to Edgar's mail: we see that RHEL6 uses python 2.6.x while Ubuntu uses 2.7.x Since most of the code has /usr/bin/env python, it boils down to this: do people run OS on ubuntu only or also on RHEL/Centos VMs. There are some py modules which behave differently on RHEL6 and ubuntu. de

Re: [Netstack] Extensions and Plugins

Hi Ying, We looked at your branch at https://code.launchpad.net/~cisco-openstack/quantum/plugin-framework. The extension code in this branch can be easily incorporated in the extension framework we are proposing. Just for demo purposes, we put your portprofile extensions into our extension framew

Re: [Netstack] Official Python version for Quantum

Hi Edgar, That's a good question. I think this is a case where we would invoke the "what is the larger openstack policy?" principle. My understanding is that Nova assumes python 2.6.x ( http://wiki.openstack.org/PythonDevelopmentEnvironment), though in practice I suspect a general rule would be

Re: [Netstack] Official Python version for Quantum

Hi Dan Maybe we should talk to the Openstack list too We know OS works fine on Ubuntu 11.04 with 2.7.2 and that dev env page was written in Jan 2011 before 11.04 came out. Maybe that will get updated soon! Debo From: netstack-bounces+dedutta=cisco@lists.launchpad.net [mailto

Re: [Netstack] Official Python version for Quantum

On Wed, Jul 20, 2011 at 11:51 AM, Debo Dutta (dedutta) wrote: > Hi Dan > > ** ** > > Maybe we should talk to the Openstack list too …. We know OS works fine on > Ubuntu 11.04 with 2.7.2 and that dev env page was written in Jan 2011 before > 11.04 came out. Maybe that will get updated soon! >

Re: [Netstack] Exception in network-refactoring-l2 branch

Thanks Deepak, Ryu, and Dan, for your timely responses. As Deepak pointed out, there was a non-NULL value in the cidr_v6 column which was creating this issue. Since the default behavior is to not process ipv6, I did not think that the implementation would be looking at this value. However, it seems

Re: [Netstack] Extensions and Plugins

Hi Rajaram, Yes, I agree with you and Dan that this framework brings more flexibility and plugin-specific extensions are only loaded when the plugin is used. Thanks for clarifying this. The confusion I had earlier is that the framework does not support dynamic loading and API extension wil