I agree with Amrith – we should try to understand what the problem first.

The datastore_manager config setting is passed down to the guest in the 
guest_info.conf file along with a few other config settings that the guest 
uses. I believe the intention is that trove_guestagent.conf is passed down 
unmodified (I.e. All guests have the same trove_guestagent.conf).

Regards,
Doug


From: Amrith Kumar <[email protected]<mailto:[email protected]>>
Reply-To: OpenStack List 
<[email protected]<mailto:[email protected]>>
Date: Monday, June 15, 2015 at 7:27 AM
To: OpenStack List 
<[email protected]<mailto:[email protected]>>
Subject: Re: [openstack-dev] [trove]Put all alternative configurations in 
default trove.conf

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:[email protected]]
Sent: Monday, June 15, 2015 7:15 AM
To: [email protected]<mailto:[email protected]>
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?
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to