Open Stack

Regarding second question, we have found the solution we were looking for.
In compute node, the* **nova.conf** *file contained the following option:

*security_group_api=quantum*

which we have changed to

*security_group_api=nova*

so nova-compute does no longer ask to quantum for security groups.


2013/6/6 Adrián Roselló Rey <adrian.rosello at i2cat.net>

> Hi all!
>
> We're trying to develop a Quantum plugin, but first of all we were
> configuring a base quantum plugin to analyze the basic workflow when
> creating an instance. Taking a look at the plugins functionalities, some
> questions came to our mind:
>
> We have seen that a plugin class can define the extensions it understands
> (router, security-groups, etc) as explained in the QuantumDevelopmen
> documentation<https://wiki.openstack.org/wiki/QuantumDevelopment#API_Extensions>.
>
>
> 1. Can we develop a plugin without extensions?
>
> 2. We have seen that, even though we declare a plugin without extensions,
> the nova-compute quantum client tries to access a method exposed by the one
> of the extensions (ex: /security_groups). Is there anyway to configure the
> client and tell him which plugin is quantum using?
>
> Thank you!
>
> Best Regards,
>
> Adrián Roselló
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130606/f8d8c76f/attachment.html>