Excerpts from Walter A. Boring IV's message of 2015-03-23 13:49:48 -0700:
> Maybe we can leverage Cinder's use of the abc in the drivers.py now.
> We could create an OptionsVD that drivers would add and implement. The
> config generator could inspect objects looking for OptionsVD and then
> c
Maybe we can leverage Cinder's use of the abc in the drivers.py now.
We could create an OptionsVD that drivers would add and implement. The
config generator could inspect objects looking for OptionsVD and then
call list_opts() on it. That way, driver maintainers don't also have
to patch th
Excerpts from Gary Kotton's message of 2015-03-21 16:36:07 +:
> Hi,
> One of the issues that we had in Nova was that when we moved to oslo
> libraries configuration options support by the libraries were no longer
> present in the generated configuration file. Is this something that is
> already
for usage questions)
Subject: [openstack-dev] [oslo][cinder][nova][neutron] going forward to
oslo-config-generator ...
All,
Let me start with the TLDR;
Cinder, Nova and Neutron have lots of configuration options that need to be
processed by oslo-config-generator to create the .conf.sample file
Hi,
One of the issues that we had in Nova was that when we moved to oslo
libraries configuration options support by the libraries were no longer
present in the generated configuration file. Is this something that is
already supported or planned (sorry for being a little ignorant here).
In neutron t
All,
Let me start with the TLDR;
Cinder, Nova and Neutron have lots of configuration options that need to
be processed by oslo-config-generator to create the
.conf.sample file. There are a couple of different ways this
could be done. I have one proposal out, which has raised concerns,
ther
