Thanks @amrith
I found out the problem. Our code base is different and these files should be
generated by function "_prepare_file_and_userdata". It explains why we should
not set "datastore_manager" in guestagent.conf and why it works for you.
It makes it less like a configuration file. Becuase we can configure it, but we
should not set it manually which is a little confusing. Anyway, I know the
issue and thanks for the replies.
------------------ Original ------------------
From: "Amrith Kumar"<[email protected]>;
Date: Mon, Jun 15, 2015 10:14 PM
To: "openstack-dev@lists."<[email protected]>;
Subject: Re: [openstack-dev] [trove]Put all alternativeconfigurationsin
default trove.conf
Hi,
The value is sent down from Task Manager based on a value that is setup as part
of the datastore.
It is actually a bad thing if you set a value of the datastore_manager in the
taskmanager.conf file on the Trove controller, and attempt to launch some other
datastore.
The way this works is that the Task Manager reads the information from the
datastore configuration and generates a configuration file (two files actually)
and renders them dynamically and sends them down to the newly spawned instance.
Thanks,
-amrith
From: 陈迪豪 [mailto:[email protected]]
Sent: Monday, June 15, 2015 8:57 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [trove]Put all alternative configurationsin
default trove.conf
Thanks for your reply @amrith.
The datastore_manager refer to the manager you gonna use, mysql or others. If
you don't set it, the default value is None. And if it's None, guest agent will
fail to start up.
That's why I think it's the necessary configuration we need to focus on. I
don't know why you can setup without setting it. So what's your datastore if
you don't configure it? MySQL?
------------------ Original ------------------
From: "Amrith Kumar"<[email protected]>;
Date: Mon, Jun 15, 2015 07:27 PM
To: "openstack-dev@lists."<[email protected]>;
Subject: Re: [openstack-dev] [trove]Put all alternative configurationsin
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]
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
