[openstack-dev] [glance] Unifying configuration file
kuvaja at hp.com
Tue Jun 17 14:29:48 UTC 2014
I do not like this idea. As now we are on 5 different config files (+ policy and schema). One for each (API and Registry) would still be ok, but putting all together would just become messy.
If the *-paste.ini will be migrated to .conf files that would bring it down, but please do not try to mix reg and API configs together.
- Erno (jokke) Kuvaja
> -----Original Message-----
> From: Flavio Percoco [mailto:flavio at redhat.com]
> Sent: 17 June 2014 15:19
> To: openstack-dev at lists.openstack.org
> Subject: Re: [openstack-dev] [glance] Unifying configuration file
> On 17/06/14 15:59 +0200, Julien Danjou wrote:
> >Hi guys,
> >So I've started to look at the configuration file used by Glance and I
> >want to switch to one configuration file only.
> >I stumbled upon this blueprint:
> > https://blueprints.launchpad.net/glance/+spec/use-oslo-config
> w.r.t using config.generator https://review.openstack.org/#/c/83327/
> >which fits.
> >Does not look like I can assign myself to it, but if someone can do so,
> >go ahead.
> >So I've started to work on that, and I got it working. My only problem
> >right now, concerned the [paste_deploy] options that is provided by
> >Glance. I'd like to remove this section altogether, as it's not
> >possible to have it and have the same configuration file read by both
> >glance-api and glance-registry.
> >My idea is also to unify glance-api-paste.ini and
> >glance-registry-paste.ini into glance-paste.ini and then have each
> >server reads their default pipeline (pipeline:glance-api).
> >Does that sounds reasonable to everyone?
> +1, it sounds like a good idea. I don't think we need to maintain 2
> separate config files, especially now that the registry service is optional.
> Thanks for working on this.
> Flavio Percoco
More information about the OpenStack-dev