GitHub user nickwallen opened a pull request:
https://github.com/apache/metron/pull/647
METRON-1031: Management UI Cannot Start Topologies in Kerberized Environment
The Metron Management UI cannot start topologies in a kerberized
environment. This includes the Parser, Enrichment, and Indexing topologies.
It seems that Metron REST does not pass "-ksp" to the start topology
commands. As a result, topologies that are started with the Management UI
cannot start a producer against a kerberized Kafka.
### Changes
* Altered the `StormCLIWrapper` to add logging of the actual CLI commands
that are executed.
* The `-ksp` argument is always used (with Kerberos or not) when launching
the Parser, Enrichment, and Indexing topologies.
* Added a Spring property `kafka.security.protocol` that serves as the
`-ksp` argument when launching the topologies.
* Ambari sets this Spring property based on Kafka's own configuration in
Ambari.
### Testing
To manually test this, validate that all of the topologies can be stopped
and started using the Management UI and Swagger UI both before and after
kerberization.
1. Launch the Full Dev environment.
1. Stop then start the Parser topologies using the Management UI.
1. Stop then start the Enrichment and Indexing topologies using the Swagger
UI.
1. Kerberize the Full Dev environment.
1. Stop then start the Parser topologies using the Management UI.
1. Stop then start the Enrichment and Indexing topologies using the Swagger
UI.
### Pull Request Checklist
- [ ] Is there a JIRA ticket associated with this PR? If not one needs to
be created at [Metron
Jira](https://issues.apache.org/jira/browse/METRON/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel).
- [ ] Does your PR title start with METRON-XXXX where XXXX is the JIRA
number you are trying to resolve? Pay particular attention to the hyphen "-"
character.
- [ ] Has your PR been rebased against the latest commit within the target
branch (typically master)?
- [ ] Have you included steps to reproduce the behavior or problem that is
being changed or addressed?
- [ ] Have you included steps or a guide to how the change may be verified
and tested manually?
- [ ] Have you ensured that the full suite of tests and checks have been
executed in the root metron folder via:
- [ ] Have you written or updated unit tests and or integration tests to
verify your changes?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] Have you verified the basic functionality of the build by building
and running locally with Vagrant full-dev environment or the equivalent?
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/nickwallen/metron METRON-1031
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/metron/pull/647.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #647
----
commit 6cff444a1120ca3577776aa4e39f54981f2d43b5
Author: Nick Allen <[email protected]>
Date: 2017-07-11T23:05:26Z
METRON-1031: Management UI Cannot Start Topologies in Kerberized Environment
commit a70ad836f9a08e58dc97c0cfc4d5dcaabf5c818b
Author: Nick Allen <[email protected]>
Date: 2017-07-12T13:52:04Z
Configuration fixup
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
