Github user mmiklavc commented on a diff in the pull request:
https://github.com/apache/incubator-metron/pull/521#discussion_r113204204
--- Diff: metron-deployment/vagrant/Kerberos-setup.md ---
@@ -1,48 +1,105 @@
-# Setting Up Kerberos in Vagrant Full Dev
-**Note:** These are instructions for Kerberizing Metron Storm topologies
from Kafka to Kafka. This does not cover the sensor connections or MAAS.
-General Kerberization notes can be found in the metron-deployment
[README.md](../README.md)
+Kerberos Setup
+==============
-## Setup the KDC
+This document provides instructions for kerberizing Metron's Vagrant-based
development environments; "Quick Dev" and "Full Dev". These instructions do
not cover the Ambari MPack or sensors. General Kerberization notes can be
found in the metron-deployment [README.md](../README.md).
-1. Build full dev and ssh into the machine
- ```
- cd incubator-metron/metron-deployment/vagrant/full-dev-platform
- vagrant up
- vagrant ssh
- ```
+* [Setup](#setup)
+* [Create a KDC](#create-a-kdc)
+* [Enable Kerberos](#enable-kerberos)
+* [Kafka Authorization](#kafka-authorization)
+* [HBase Authorization](#hbase-authorization)
+* [Storm Authorization](#storm-authorization)
+* [Start Metron](#start-metron)
+
+Setup
+-----
+
+1. Deploy a Vagrant development environment; either [Full
Dev](full-dev-platform) or [Quick Dev](quick-dev-platform).
+
+1. Export the following environment variables. These need to be set for
the remainder of the instructions. Replace `node1` with the appropriate hosts,
if you are running Metron anywhere other than Vagrant.
-2. Export env vars. Replace *node1* with the appropriate hosts if running
anywhere other than full-dev Vagrant.
```
# execute as root
sudo su -
export ZOOKEEPER=node1
export BROKERLIST=node1
--- End diff --
I've been thinking about this and realized we shouldn't be declaring our
zookeeper and kafka broker lists this way because it won't work for anything
but a single node environment. The lists are really host:port comma-delimited.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
