[jira] [Commented] (METRON-1424) Kerberos: Solr

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/METRON-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16393479#comment-16393479 ] 

ASF GitHub Bot commented on METRON-1424:
----------------------------------------

GitHub user merrimanr opened a pull request:

    https://github.com/apache/metron/pull/960

    METRON-1424: Kerberos: Solr

    ## Contributor Comments
    This PR adds Kerberos support for Solr in Metron.  This has been verified in full dev using the following steps:
    
    1. Spin up full dev
    2. Stop and remove Elasticsearch and Kibana
    3. Install HDP Search (https://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.6.0/bk_solr-search-installation/content/ch_hdp-search-install-ambari.html)
    4. Create collections for bro, snort and error using the `$METRON_HOME/bin/create_collection.sh` script.
    5. Kerberize full dev using the instructions in https://github.com/apache/metron/blob/master/metron-deployment/Kerberos-manual-setup.md
    6. In Ambari, change the "Solr Zookeeper Urls" setting in the Metron > Index Settings tab to "node1:2181/solr" and the "Random Access Search Engine" setting in the Metron > Indexing tab to "Solr" (it also helps to change "Random Access Indexing Offset" in the Metron > Indexing tab to "LATEST")
    7. Verify data is showing up in Solr
    8. Restart Metron REST and you should be able to query data in Solr without issue
    
    This PR assumes HDP Search is being used.  The benefit of using HDP Search is that Ambari handles Kerberos configuration for Solr.  If using a separate Solr install, Kerberos configuration would need to be done manually there.
    
    Side note:  I had a lot of trouble getting everything to work all at once due to resource constraints in full dev.  I would suggest shutting down as many services as possible, getting data into Solr first, then shutting down topologies, then starting REST and querying data.
    
    
    ## Pull Request Checklist
    
    Thank you for submitting a contribution to Apache Metron.  
    Please refer to our [Development Guidelines](https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=61332235) for the complete guide to follow for contributions.  
    Please refer also to our [Build Verification Guidelines](https://cwiki.apache.org/confluence/display/METRON/Verifying+Builds?show-miniview) for complete smoke testing guides.  
    
    
    In order to streamline the review of the contribution we ask you follow these guidelines and ask you to double check the following:
    
    ### For all changes:
    - [ ] 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)?
    
    
    ### For code changes:
    - [ ] 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:
      ```
      mvn -q clean integration-test install && dev-utilities/build-utils/verify_licenses.sh 
      ```
    
    - [ ] 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?
    
    ### For documentation related changes:
    - [ ] Have you ensured that format looks appropriate for the output in which it is rendered by building and verifying the site-book? If not then run the following commands and the verify changes via `site-book/target/site/index.html`:
    
      ```
      cd site-book
      mvn site
      ```
    
    #### Note:
    Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.
    It is also recommended that [travis-ci](https://travis-ci.org) is set up for your personal repository such that your branches are built there before submitting a pull request.


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/merrimanr/incubator-metron solr-kerberos

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/metron/pull/960.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 #960
    
----
commit ac1de170af8fa769683f72783f6258cf12663f94
Author: merrimanr <me...@...>
Date:   2018-02-28T22:49:37Z

    initial commit

commit 870a2ea15ab08082402bb649c6bceca22e12709b
Author: merrimanr <me...@...>
Date:   2018-03-05T14:33:17Z

    renamed schema files in rpm spec

commit 7724e14c833292bce3f3328905df3ec160898008
Author: merrimanr <me...@...>
Date:   2018-03-06T17:49:22Z

    initial commit

commit c71f692369ecfd9e273f807a8a7e4340128d0255
Author: merrimanr <me...@...>
Date:   2018-03-08T20:10:18Z

    Merge remote-tracking branch 'mirror/feature/METRON-1416-upgrade-solr' into solr-kerberos

commit 7aad27eb2f5b09778a7f985b78fa09df8190ee4b
Author: merrimanr <me...@...>
Date:   2018-03-09T19:58:45Z

    cleaned up debug statements

----


> Kerberos: Solr
> --------------
>
>                 Key: METRON-1424
>                 URL: https://issues.apache.org/jira/browse/METRON-1424
>             Project: Metron
>          Issue Type: Sub-task
>            Reporter: Justin Leet
>            Priority: Major
>
> Verify that our Mpack passes the right credentials to Solr. Verify that Solr kerberizes out of the box. This'll need to be spun up so we can find any issues.
> This should also be spun up for at least the ticket expiration time (over 24 hours by default).  We'd seen some issues with lowering the ticket expiration time not seeming to be reflected in configs, so we should be careful to make sure ticket expiration works as expected.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)