-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Combine Kafka client configuration for external server and ManageIQ server #135
Comments
Other follow-up items:
|
Will be tracked by: #136 |
Outstanding Issues:
Tracked by Issue: #139
Tracked by Issue: #140
See: https://github.com/ManageIQ/manageiq/blob/2f8ae2345eb25b16ad87f7dc124b4fe68a610bdb/config/settings.yml#L936 to Tracked by Issue: #136 Pull Requests: #137
Tracked by: #135
Tracked by: #142
Tracked by: #141
Tracked by: ManageIQ/manageiq-appliance-build#454 Outstanding PRs:Should be ready to merge: ManageIQ/manageiq-rpm_build#122 |
Similar to "Investigate if logs directory should be moved to /var/log #130 (comment)" where are we storing the persistent queue messages, should we have another volume dedicated to it? Also we should look at message retention settings |
PR 130 introduced the ability to configure a ManageIQ appliance as a Kafka message server and to configure a ManageIQ appliance as a Kafka message client to an existing ManageIQ appliance previously configured as a Kafka message server.
Prior to PR 130 there already existed the ability to configure a ManageIQ appliance as a Kafka message client to an external, non-ManageIQ, Kafka server.
With PR 130 the
Configure Messaging
menu will look like this:This issue will track combining options 2 and 3 above:
into a single option for configuring the current appliance connected to either an appliance configured as a messaging server or an external messaging system
The text was updated successfully, but these errors were encountered: