Skip to content

Latest commit

 

History

History
 
 

metron-deployment

README.md

This project contains tools for building, packaging, and deploying Apache Metron. Please refer to the following sections for more information on how to get Apache Metron running in your environment.

How do I deploy Metron with Ambari?

This provides a Management Pack (MPack) extension for Apache Ambari that simplifies the provisioning, management and monitoring of Metron on clusters of any size.

This allows you to easily install Metron using a simple, guided process. This also allows you to monitor cluster health and even secure your cluster with kerberos.

What is this good for?

  • If you want to see how Metron can really scale by deploying it on your own hardware, or even in the cloud, this is the best option for you.

  • If you want to run a proof-of-concept to see how Apache Metron can benefit your organization, then this is the way to do it.

How?

To deploy Apache Metron using Ambari, follow the instructions at packaging/ambari/metron-mpack.

How do I deploy Metron on a single VM?

This will deploy Metron and all of its dependencies on a virtual machine running on your computer.

What is this good for?

  • If you are new to Metron and want to explore the functionality that it offers, this is good place to start.

  • If you are a developer contributing to the Apache Metron project, this is also a great way to test your changes.

What is this not good for?

  • This VM is not intended for processing anything beyond the most basic, low volume work loads.

  • Additional services should not be installed along side Metron in this VM.

  • This VM should not be used to run a proof-of-concept for Apache Metron within your organization.

Running Metron within the resource constraints of a single VM is incredibly challenging. Failing to respect this warning, will cause various services to fail mysteriously as the system runs into memory and processing limits.

How?

To deploy Metron in a VM running on your computer, follow the instructions at development/centos6.

How do I address services crashing when running Metron on a single VM?

We recommend looking at Ambari and shutting down any services you may not be using. For example, we recommend turning off Metron Profiler, as this commonly causes REST services to crash when running on a single VM.

Parser Aggregation Feature

The Parser Aggregation feature does not currently exist in the management UI. In order to address resource limitations in the full dev development environments, bro, yaf, and snort have been aggregated into a single parser topology. However, the Management UI is not currently able to display its status until the feature is added. Aggregated parsers can still be created via Ambari and the command line scripts.

Here are some tips for working with parser aggregation while the UI feature is being developed.

  • How are parsers picked up by the UI?: This is based entirely on what is currently stored in the Zookeeper configs. See Management Utility "DUMP" option with "-c PARSER" to see all of what is currently loaded. The management UI does not update the configurations stored locally on disk, so Zookeeper is the source of truth.

  • Removing an existing aggregation: In the Ambari UI click on the Metron serice and select "Metron Parsers." Select "stop" from the dropdown for the parser component. Click "back," "configs," and then navigate to "Parsers." In the text field option labeled "parsers". Remove the double quotes from around the listed parsers. Save and choose "Restart" when prompted. This will deploy three individual parsers rather than a single aggregated parser: bro, snort, and yaf. Be aware, you may need to shut down other topologies to free up resources so that you can run the parsers without aggregation. Stopping the profiler, pcap, or batch_indexing are a few options that will still allow data to pass through the system end-to-end.

  • Managing parser lifecycle: Starting and stopping parsers in the management UI will in no way affect a parser running as aggregated. The exception to this is if you create a parser via the management UI that has the same name as the aggregation, e.g. "bro__snort__yaf." We recommend against this. It will appear as thought you now have the ability to manage the aggregated parser now, but you will only be able to start/stop it.

  • Editing parser configuration: In order to modify the aggregated parsers' configurations, you will need to first pull all of the configuration from Zookeeper to the local configuration directory by executing the following commands

    source /etc/default/metron
$METRON_HOME/bin/zk_load_configs.sh -m PULL -o ${METRON_HOME}/config/zookeeper -z $ZOOKEEPER -f

    Make your changes to an individual parser's configuration json, e.g. ${METRON_HOME}/config/zookeeper/parsers/bro.json, save locally, and then push them back up to Zookeeper

    $METRON_HOME/bin/zk_load_configs.sh -m PUSH -i $METRON_HOME/config/zookeeper/ -z $ZOOKEEPER

    See Management Utility for more detail.

  • Other gotchas: Stop the aggregated parsers in Ambari before removing or adding grouping quotes. Otherwise, you will end up with both the individual parsers and the aggregated topology running concurrently. Ambari only manages the parser topology lifecycle via the current parser name list provided, so changing that list removes Ambari's ability to reference the old topology names.

How do I build RPM packages?

This provides RPM packages that allow you to install Metron on an RPM-based operating system like CentOS.

What is this good for?

  • If you want to manually install Apache Metron on an RPM-based system like CentOS, installation can be simplified by using these packages.

  • If you want a guided installation process using Ambari on an RPM-based system, then these RPMs are a necessary prerequisite.

What is this not good for?

  • If you want a complete, guided installation process, use Ambari rather than just these packages. Installing Metron using only these RPMs still leaves a considerable amount of configuration necessary to get Metron running. Installing with Ambari automates these additional steps.

How?

To build the RPM packages, follow the instructions at packaging/docker/rpm-docker.

How do I build DEB packages?

This builds installable DEB packages that allow you to install Metron on an APT-based operating system like Ubuntu.

What is this good for?

  • If you want to manually install Metron on a APT-based system like Ubuntu, installation can be simplified by using these packages.

  • If you want a guided installation process using Ambari on an APT-based system, then these DEBs are a necessary prerequisite.

What is this not good for?

  • If you want a complete, guided installation process, use Ambari rather than just these packages. Installing Metron using only these RPMs still leaves a considerable amount of configuration necessary to get Metron running. Installing with Ambari automates these additional steps.

How?

To build the DEB packages, follow the instructions at packaging/docker/deb-docker.

How do I build Metron with Docker?

This provides a Docker containing all of the prerequisites required to build Metron. This allows you to easily build Metron without installing all of the build dependencies manually.

What is this good for?

  • If you want to build Metron, but do not want to manually install all of the build dependencies, then this is a good option.

How?

Follow the instructions available at packaging/docker/ansible-docker.