Open Stack

I +1 what Mark and Gary agreed on the IRC.
That's exactly what I meant by 'namespaces' on yesterday's meeting.

Cheers,
Salvatore

On 24 July 2012 16:30, Sumit Naiksatam (snaiksat) <snaiksat at cisco.com>wrote:

>  Hi Gary,****
>
> ** **
>
> Are you asking this just in the context of the RPC related configurations,
> or also for moving all the existing configuration from the plugin-specific
> configuration files (the ones under etc/quantum/plugins) to a single
> configuration file?****
>
> ** **
>
> Moving plugin-independent common configuration to a common file makes
> sense to me (including the agent and/or RPC related configurations as
> discussed in the IRC meeting yesterday). However, I am not in favor of
> moving all plugin-specific configurations to a single/common file.****
>
> ** **
>
> Thanks,****
>
> ~Sumit. ****
>
> ** **
>
> *From:* Gary Kotton [mailto:gkotton at redhat.com]
> *Sent:* Tuesday, July 24, 2012 6:03 AM
> *To:* openstack-dev at lists.openstack.org
> *Subject:* Re: [openstack-dev] [Quantum] Agents and configuration files***
> *
>
> ** **
>
> Hi,
> Can people please raise their concerns about moving all of the plugin.ini
> files into quantum.conf.
> This will solve us a number of problems. Please let me know if you have
> any reservations.
> Thanks
> Gary
>
> On 07/24/2012 09:17 AM, Gary Kotton wrote: ****
>
> Hi,
>
> *Background*: The quantum service makes use of the configuration file
> quantum.conf. In addition to this there is a common configuration file
> shared between the plugin and the agent (plugin.ini). The aforementioned
> files are loaded by the common configuration files.
>
> *Current developments*: A number of current developments, for example
> notifications (https://review.openstack.org/#/c/9835/) and scalable
> agents (https://review.openstack.org/#/c/9591/) require RPC
> configurations.
>
> From the discussion last night the community the consensus is to have the
> common configuration items that may be relevant to one or more agent/plugin
> in the quantum configuration file. This change will require the agents to
> also load the quantum.conf configuration files.
>
> *Open issues*:
> 1. I do not think that the common configuration supports mapping of name
> spaces to configuration files.
> 2. Configuration file loading. With the plugins the configuration files
> are loaded in two stages. If possible it would be great that the files
> could be loaded at once - this can be done by listing the plugin/agent ini
> file(s) in the quantum.conf. When this is loaded then the other files will
> be loaded.
>
> Please let me know if you have any comments or objections. I would like to
> move ahead and start to work on this.
>
> Thanks
> Gary
>
>
> ****
>
> ** **
>
> ** **
>
> _______________________________________________****
>
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20120724/cbe979f5/attachment.html>