| 2013-05-23 23:34:17 |
Maru Newby |
description |
The L3 agent is responsible for spawning the metadata proxy (quantum-ns-metadata-proxy), and at present only supports configuration of file-based logging for the proxy (see [1] and [2]). Even file-based logging will not be configured if log_dir is not set in the L3 agent config. This is the default in devstack, and the result is that the metadata proxy doesn't log anywhere, making any errors with the proxy opaque to a developer.
Either a sane default should be provided to ensure that some kind of logging is always configured for the proxy, or the L3 agent (and the DHCP agent going forward) should error out when it tries to spawn the proxy.
[1] https://github.com/openstack/quantum/blob/master/quantum/agent/l3_agent.py#L263
[2] https://github.com/openstack/quantum/blob/master/quantum/agent/common/config.py#L40 |
The L3 agent is responsible for spawning the metadata proxy (quantum-ns-metadata-proxy), and at present only supports configuration of file-based logging for the proxy. Even file-based logging will not be configured if log_dir is not set in the L3 agent config (see [1] and [2]). This is the default in devstack, and the result is that the metadata proxy doesn't log anywhere, making any errors with the proxy opaque to a developer.
Either a sane default should be provided to ensure that some kind of logging is always configured for the proxy, or the L3 agent (and the DHCP agent going forward) should error out when it realizes that it can't configure logging for the proxy.
[1] https://github.com/openstack/quantum/blob/master/quantum/agent/l3_agent.py#L263
[2] https://github.com/openstack/quantum/blob/master/quantum/agent/common/config.py#L40 |
|
