Open Stack

> On 19 Jan 2016, at 13:05, SHTILMAN, Tomer (Tomer) <tomer.shtilman at nokia.com> wrote:
> 
> Thanks 
> Not sure that duplicating mistral.conf three times will be the best in this case , will make things very hard to manage
> 
> 
> -----Original Message-----
> From: EXT Lingxian Kong [mailto:anlin.kong at gmail.com] 
> Sent: Tuesday, January 19, 2016 2:29 AM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [mistral] how to split mistral log files
> 
> Hi, Tomer,
> 
> If you really want Mistral services to be running on different processes or different servers, I recommend you use different config file respectively, log file path can be configured differently, which can achieve what you said.

I agree with Lingxian on that. Log file name is a part of configuration. Having any assumptions about file naming (e.g. based on a type of process that we run) would make it less transparent. In other words, I think there shouldn’t be any automatically generated names.
Another reason: some day we may want to change something else which means we’d get inconsistency around config parameters, some of them are ‘plain’ and some are ‘generated’.

> On Tue, Jan 19, 2016 at 5:19 AM, SHTILMAN, Tomer (Tomer) <tomer.shtilman at nokia.com> wrote:
>> 
>> I thought of changing
>> https://github.com/openstack/mistral/blob/master/setup.cfg
>> 
>> And creating three different console scripts
>> 
>> console_scripts =
>> 
>>    mistral-engine = mistral.cmd.launch:main
>> 
>>    mistral-api = mistral.cmd.launch:main
>> 
>>    mistral-executor = mistral.cmd.launch:main
>> 
>>    mistral-db-manage = mistral.db.sqlalchemy.migration.cli:main


I think regardless of config files this would be a nice addition slightly improving usability.
I see no reason why these specific scripts can’t be added. I’d say go ahead and send a patch.

Renat Akhmerov
@ Mirantis Inc.