metron-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From justinleet <>
Subject [GitHub] incubator-metron pull request #423: METRON-270: Add Zeppelin to the platform
Date Wed, 25 Jan 2017 15:20:13 GMT
GitHub user justinleet opened a pull request:

    METRON-270: Add Zeppelin to the platform

    Adds Zeppelin to the Ambari Management Pack portion.  Adding to the Ansible / quick dev
portion is happening a bit in parallel with Nick's work on METRON-346.
    This ticket existed before the mpack, so if we're not comfortable having this just cover
the mpack I'd prefer to split this ticket rather than force them together.  This isn't packaging
up any notebooks, so there's not deviation in functionality until notebooks are added.
    Essentially, this ties into metron-indexing (because we rely on data generated there).
 I'm open to adjusting this if anybody feels strongly about it, but I think it's currently
the best place.  Zeppelin notebook JSON files are loaded from metron-platform/metron-indexing/src/main/config/zeppelin/.
 These files can be placed into subdirs for organization if desired. (e.g. zeppelin/bro/bro.json)
and must end with .json.
    A custom action is added to the mpack to import these notebooks.  This action is available
regardless of whether or not Metron itself is running. Zeppelin configuration is autopopulated
by the management pack.
    Zeppelin allows for duplicate notebook names (they'll be given differing IDs). I didn't
implement a way to track installed notebooks, but this is potentially a good future feature
(to allow us to delete all installed notebooks, etc.).  Once the management pack installs
the notebooks, they're treated as belonging to Zeppelin entirely and can be managed there.
    For testing, I created a few notebooks (valid, invalid, misnamed and in subdirs), updated
the spec files, recreated the RPMs, and ran this up on a pretty constrained local cluster.
I was able to see them and run sections of them as appropriate.

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

    $ git pull zeppelin_dashboard

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

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #423
commit e5b392cc73d49fa4d9a3420df556e480c8f918af
Author: justinjleet <>
Date:   2017-01-23T13:36:24Z

    Working initially

commit 1cafd1d7c03d9fc25d7d100ddb369bc43bec4aad
Author: justinjleet <>
Date:   2017-01-24T20:46:24Z

    Building directory for loading notebook files

commit 58f2ed354c86d66d75a850d97a3af38ad6fc4a53
Author: justinjleet <>
Date:   2017-01-25T14:57:11Z

    Updating READMEs

commit c7e3958d6c99d723d9010d804a10a38ffbd053e9
Author: justinjleet <>
Date:   2017-01-25T15:11:10Z

    Removing extraneous spec change from testing, and updating README


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 or file a JIRA ticket
with INFRA.

View raw message