Open Stack

Miguel:

Thanks for the information below. The blueprint you are working on is indeed very useful. But I don't see anything around the ability to actually load a specific plugin and test it. Or did I miss that part? I think for the open source plugins, having the ability for the CI system to somehow detect this and use it for the tempest run would be very useful. For example, there's no way the Ryu changes I just reviewed would have passed through the CI system because they require a specific branch of the Ryu code to run. So devstack doesn't even work unless you use that branch. Yet the tempest run in the review passed ok. This sort of false-positive could be fixed if we could use more than just the OVS plugin for tempest runs.

Thanks,
Kyle

On Jan 30, 2013, at 3:31 PM, MIguel Lavalle <miguel at mlavalle.com> wrote:

> Kyle,
> 
> I think you are asking more than one question here. Let me see if I got them all and if I can address them:
> 
> 1) You can configure the plugin in the localrc file with the Q_PLUGIN option.
> 
> 2) DevStack comes "out of the box" with configuration files for several plug-in's. You can find them in
> devstack/lib/quantum_plugins. As of now, the configuration files that you can find there are: bigswitch_floodlight, linuxbridge, openvswitch, ryu
> 
> 3) In devstack/lib/quantum_plugins you can also find README.md. It explains how to set-up a configuration file for other plug-ins
> 
> 4) Back in December, the following smoke test was added to tempest: https://github.com/openstack/tempest/commit/0c38121479486781b150ce5e96c943cd5fdd24d2. It tests Quantum from the API level, and therefore tests whatever plug-in is being used.
> 
> 5) Right now I am implementing the code for this blueprint: https://blueprints.launchpad.net/tempest/+spec/quantum-basic-api. Again, it tests Quantum from the API level, and therefore tests whatever plug-in is being used.
> 
> I hope this helps
> 
> Regards
> 
> Miguel
> 
> 
> 
> On 01/30/2013 02:59 PM, Kyle Mestery (kmestery) wrote:
>> On Jan 30, 2013, at 12:51 PM, Jason Zhang <bearovercloud at gmail.com> wrote:
>>> I had tested it against Linuxbridge, it worked with namespace enabled, not sure the Ryu plugin.
>>> 
>> Are you saying you have verified tempest works with linuxbridge? Is there a way to configure it, or how does it know which plugin to use in the localrc? For example, with a change for the Ryu plugin, it would make sense to have it use the Ryu plugin in the tempest run.
>> 
>>> On 1/30/13 10:36 AM, Kyle Mestery (kmestery) wrote:
>>>> While reviewing some changes for the Ryu plugin, which I tried to run myself, it occurred to me I wasn't 100% sure the tempest/devstack integration with Quantum is testing anything other than the OVS plugin. Can anyone confirm this? Certainly for the open source plugins it would be great to enable support for this to test out OVS, linuxbridge, and Ryu.
>>>> 
>>>> Thanks,
>>>> Kyle
>>>> _______________________________________________
>>>> OpenStack-dev mailing list
>>>> OpenStack-dev at lists.openstack.org
>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>> 
>>> _______________________________________________
>>> OpenStack-dev mailing list
>>> OpenStack-dev at lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> 
>> 
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 
> 
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev