[jira] [Commented] (METRON-385) Create Ambari Service Definition for Indexing

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

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

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

GitHub user justinleet opened a pull request:

    https://github.com/apache/incubator-metron/pull/222

    METRON-385 Create Ambari Service Definition for Indexing

    https://issues.apache.org/jira/browse/METRON-385
    
    Opening this PR for community review and feedback.
    
    Prereq:
    * Ambari 2.4
    
    Testing this PR:
    * The RPMs in metron-deployment should be built.  They should either be mounted or copied to /localrepo in the node to be used as the indexing master node.
    * Copy or mount the services and stack contents into the appropriate places on the ambari-server node.  For example:
    ** incubator-metron/metron-deployment/packaging/ambari/src/main/resources/stacks/HDP/2.4/services/INDEXING -> /var/lib/ambari-server/resources/stacks/HDP/2.4/services/INDEXING
    **incubator-metron/metron-deployment/packaging/ambari/src/main/resources/common-services/INDEXING -> /var/lib/ambari-server/resources/common-services/INDEXING
    * Install the master to a node with the Kafka Broker.
    
    Limitations / Notes
    * Service advisor for ensuring that the service is colocated appropriately doesn't appear to work. It's currently in the PR as-is.  It can easily be removed if we want to leave it out for now.
    * Because the RPMs are currently not published to a yum repo, it's necessary to do the copy / mount step. Assuming the RPMs find a more permanent home, the repolist for the used stack should be updated and preferred.
    * Elasticsearch.properties had a couple properties added to reflect what was in the Ansible scripts, because the current file was missing properties necessary to run the script outside of that context.
    * Ambari currently provides no hooks for performing actions when a service is deleted.  To ensure cleanup please run
    
    ```
    #!/bin/bash
    
    # kafka
    /usr/hdp/current/kafka-broker/bin/kafka-topics.sh \
            --zookeeper $ZK_QUORUM \
            --delete \
            --topic indexing
    done
    
    # storm kill
    storm kill indexing
    
    # yum delete
    yum -y erase metron-indexing metron-common
    
    # final file delete
    rm -rf /usr/metron
    ```


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

    $ git pull https://github.com/justinleet/incubator-metron ambari-indexing

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

    https://github.com/apache/incubator-metron/pull/222.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 #222
    
----
commit 3172d9137b05f3f4c271f2a121fa4223606c8221
Author: justinjleet <ju...@gmail.com>
Date:   2016-08-17T12:14:36Z

    WIP Indexing Service

commit d147e24097a76032b64f705456e6f3cfc335bff3
Author: justinjleet <ju...@gmail.com>
Date:   2016-08-17T12:50:06Z

    Metron Indexing Service in Ambari

----


> Create Ambari Service Definition for Indexing
> ---------------------------------------------
>
>                 Key: METRON-385
>                 URL: https://issues.apache.org/jira/browse/METRON-385
>             Project: Metron
>          Issue Type: New Feature
>            Reporter: Justin Leet
>            Assignee: Justin Leet
>
> To pull everything into an easier install through Ambari, create a service definition to automatically install and handle the indexing topology appropriately.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)