Hello! I’ve never had to set datastore_manager in trove.conf and I can launch Trove just fine with either one of three setup methods, devstack, redstack, or following the detailed installation steps provided in the documentation. My suspicion is that the steps you are using to register your guest image are not correct (i.e. the invocation of the trove-manage command or any wrappers for it). I would like to understand the problem you are facing because this solution appears baffling. -amrith -- Amrith Kumar, CTO Tesora (www.tesora.com) Twitter: @amrithkumar IRC: amrith @freenode From: 陈迪豪 [mailto:chendihao at unitedstack.com] Sent: Monday, June 15, 2015 7:15 AM To: openstack-dev at lists.openstack.org Subject: [openstack-dev] [trove]Put all alternative configurations in default trove.conf Hi all, I have created the blueprint about the default configuration file. I think we should add the essential configuration like "datastore_manager" in default trove.conf. The blueprint is here https://blueprints.launchpad.net/trove/+spec/default-configuration-items Any suggestion about this? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150615/28a4a4ef/attachment.html>