[Openstack] no force_config_drive option?
yang sheng
forsaks.30 at gmail.com
Mon Apr 4 14:45:16 UTC 2016
Hi All
I deployed openstack with 4 nodes (2 controllers and 2 compute nodes).
Based on the neutron deployment scenario documentation (
http://docs.openstack.org/liberty/networking-guide/scenario-provider-lb.html),
i used provider networks with linux bridge. It mentioned that I should use
the config drive instead of metadata service.
However, after I configure the nova.conf in compute node, adding
"force_config_drive=ture" (
http://docs.openstack.org/user-guide/cli_config_drive.html),
openstack-nova-compute service couldn't start.
I checked log file and it says:
2016-04-04 10:31:26.066 30361 ERROR nova File
"/usr/lib/python2.7/site-packages/oslo_service/service.py", line 281, in
wait
2016-04-04 10:31:26.066 30361 ERROR nova status, signo =
self._wait_for_exit_or_signal(ready_callback)
2016-04-04 10:31:26.066 30361 ERROR nova File
"/usr/lib/python2.7/site-packages/oslo_service/service.py", line 254, in
_wait_for_exit_or_signal
2016-04-04 10:31:26.066 30361 ERROR nova self.conf.log_opt_values(LOG,
logging.DEBUG)
2016-04-04 10:31:26.066 30361 ERROR nova File
"/usr/lib/python2.7/site-packages/oslo_config/cfg.py", line 2229, in
log_opt_values
2016-04-04 10:31:26.066 30361 ERROR nova _sanitize(opt, getattr(self,
opt_name)))
2016-04-04 10:31:26.066 30361 ERROR nova File
"/usr/lib/python2.7/site-packages/oslo_config/cfg.py", line 1906, in
__getattr__
2016-04-04 10:31:26.066 30361 ERROR nova raise NoSuchOptError(name)
2016-04-04 10:31:26.066 30361 ERROR nova NoSuchOptError: no such option:
force_config_drive
2016-04-04 10:31:26.066 30361 ERROR nova
so how should I enable the config drive in nova?
thanks for any advice!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20160404/5d1bf53e/attachment.html>
More information about the Openstack
mailing list