Ask Your Question

plugins.ini and quantum.conf: can we merge them?

asked 2011-06-28 16:55:57 -0600

salvatore-orlando gravatar image


I was wondering why do we have two distinct file for Quantum API service configuration (default: /etc/quantum.conf) and for specifying the plugin (default ./plugins.ini). Plugins.ini at the moment only specifies the class of the quantum plugin.

It seems this information can be easily moved into quantum.conf. Is there a particular reason for keeping these two bits of configuration separated?

edit retag flag offensive close merge delete

3 answers

Sort by ยป oldest newest most voted

answered 2011-06-28 17:49:45 -0600

danwent gravatar image

+1, barring technical issues.

edit flag offensive delete link more

answered 2011-06-28 17:55:33 -0600

somikbehera gravatar image

When I created the plugins.ini there wasn't general quantum.conf and the first pieces of code we wanted to get consensus around where the plugin interfaces.

Now that we have got things working better, I think collapsing the configuration file seems like a good idea. I'll create a bug for this issue.

edit flag offensive delete link more

answered 2011-06-28 18:03:46 -0600

salvatore-orlando gravatar image

Thanks Somik Behera, that solved my question.

edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2011-06-28 16:55:57 -0600

Seen: 42 times

Last updated: Jun 28 '11