Skip to content

Conversation

@arm4b
Copy link
Member

@arm4b arm4b commented Jan 26, 2016

Currently user should generate mistral config by hand, adjusting rabbitmq and postgresql configuration.

And we do the same via our smoke tests:
u17xv8d 1

Let's place mistral config with default connection, assuming everything is local, removing one step for 80% of users to make it minimally working.

Since mistral config is managed by packaging, once user change default config - it won't be replaced automatically during package upgrade, what is perfectly nice.

Please commit changes directly to mistral-default-config shared branch if you have something to add/adjust for default mistral.conf.

@arm4b arm4b self-assigned this Jan 26, 2016
@lakshmi-kannan
Copy link
Contributor

lgtm.

@dennybaa
Copy link
Contributor

+1. awesome @armab

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Guys, keep in mind: I have no idea what I'm doing, since it's mistral.
For example we use it for testing, but how bad could be this setting for default installation?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, found it's used for OpenStack only:
https://pypi.python.org/pypi/mistral#configuring-mistral

Merging.

arm4b pushed a commit that referenced this pull request Jan 26, 2016
Default connection settings in mistral.conf
@arm4b arm4b merged commit d0a4f6a into master Jan 26, 2016
@arm4b arm4b deleted the mistral-default-config branch January 26, 2016 18:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants