Justin Leet created METRON-427:

             Summary: Create Ambari Management Pack for Metron Installation
                 Key: METRON-427
                 URL: https://issues.apache.org/jira/browse/METRON-427
             Project: Metron
          Issue Type: New Feature
            Reporter: Justin Leet

Right now, Metron depends on Ambari blueprints, in the Ansible scripts, to 
deploy onto a cluster.

To ease installation, a full Ambari Management Pack 
(https://cwiki.apache.org/confluence/display/AMBARI/Management+Packs) can be 
used to lay down topologies, etc.

The current expectation is that the boundaries of this would cover from Kafka 
to the indexes.  The dev list has additional discussion about whether or not 
sensor install and what should exist beyond minimum viable product.  Additional 
follow-on tickets would be created based on the results of both that discussion 
and any discussion on this ticket.

A minimum viable product for this would cover
* Laying down topologies (parsers, enrichment, and indexing)
* Starting and stopping topologies
* Setting up configuration
* Setting up bits (Using RPMs currently built locally)
* Set up infra dependencies (MySql and Elasticsearch)

At this point, the MVP could take data from Kafka, run it through the 
topologies, and make it available in the output Elasticsearch Indexes.

A good deal of the ground work for this is already completed (several Service 
Definitions, along with the RPM creation).  Relevant Jira's are:
* METRON-383 (Create Ambari Service Definition for Metron Parsers)
* METRON-385 (Create Ambari Service Definition for Indexing)
* METRON-386 (Create Ambari Service Definition for Elasticsearch)
* METRON-357 (Create Ambari Service Definition for Kibana)
* METRON-214 (Build RPM Packages for Deployment)

This message was sent by Atlassian JIRA

Reply via email to