yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #65227
[Bug 1696830] Re: nova-placement-api default config files is too strict
Reviewed: https://review.openstack.org/473615
Committed: https://git.openstack.org/cgit/openstack/snap-nova/commit/?id=f011198f5bd93d20fd37a124140d9addbf1a4c29
Submitter: Jenkins
Branch: master
commit f011198f5bd93d20fd37a124140d9addbf1a4c29
Author: Corey Bryant <corey.bryant@xxxxxxxxxxxxx>
Date: Tue Jun 13 13:14:00 2017 +0000
Enable nova-placement-api config and logging
nova-placement-api is a bit tricky. The wsgi application doesn't accept
CLI arguments, so we can't pass --config-file, --config-dir, or
--log-file via uwsgi's pyargv. Additionally, nova-placement-api doesn't
pass the [keystone_authtoken] from the config file found in
OS_PLACEMENT_CONFIG_DIR to keystonemiddleware.
We continue to use the OS_PLACEMENT_CONFIG_DIR environment variable to
point at the default nova.conf in $SNAP/etc/nova.conf. This default
nova.conf includes logdir=$SNAP_COMMON/log/, enabling nova-placement-api.log
to be written to the correct directory.
Passing [keystone_authtoken] to keystonemiddleware is fixed in oslo.config.
The prior commit titled "Patch (_COMMON) dirs into oslo.config defaults"
includes a patch for this. keystonemiddleware gets the [keystone_authtoken]
config via oslo.config's find_config_files() and find_config_dirs(), which
are patched to include the $SNAP and $SNAP_COMMON config directories.
Change-Id: I02e2a5d9df91eb8cbf36beb474809bc1e80fe80b
Closes-Bug: 1696830
** Changed in: snap-nova
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1696830
Title:
nova-placement-api default config files is too strict
Status in OpenStack Compute (nova):
Confirmed
Status in oslo.config:
Fix Released
Status in Glance Snap:
New
Status in Keystone Snap:
New
Status in Neutron Snap:
New
Status in Nova Snap:
Fix Released
Status in Nova Hypervisor Snap:
New
Bug description:
If nova.conf doesn't exist in the typical location of
/etc/nova/nova.conf and OS_PLACEMENT_CONFIG_DIR isn't set, nova-
placement-api's wsgi application will fail. In our case with the
OpenStack snap, we have two possible paths we may pick nova.conf up
from, based on what --config-file specifies. I think the right answer
here is to be a bit more flexible and not set the default config file
if it's path doesn't exist.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1696830/+subscriptions
References