METRON-1091 Package STELLAR shell as stand alone

~~This PR adds metron-deployment/packaging/archive, and the metron-stellar-shell module.~~ This PR adds a second archive product ( ${}-stand-alone.tar.gz ) to stellar-common.

This module packages a stellar shell environment that allows running stellar on a workstation that is not a dev/build machine, nor is a cluster node.

The idea is that a metron 'admin' may want to run stellar commands on his local machine.

Remote management ( config_get etc ) and profile would be useful, but have not been included. I do not believe it is realistic for the expected user to open firewall ports or have the 'confs' setup to have these functions work as they would on a metron cluster node.

This use case would seem to require REST support of some kind. Maybe a /metron-interface/metron-rest-stellar module. Or maybe when extensions come to stellar we can just do it as an extension.

Also a problem, is that there are management functions that bring in hadoop dependencies mixed in with other functions like SHELL_EDIT() that may be useful on their own.


  • package ~~- take /metron-deployment/packaging/archive/metron-stellar-shell/target/metron-stellar-shell-0.4.1-archive.tar.gz and unpack it in some directory~~ take metron-stellar/stellar-common/target/stellar-common-0.4.1-stand-alone.tar.gz and unpack it in some directory
  • run it
  • `stellar it up

Questions for reviewers

  • Where should the doc for this go?
  • What NOTICE or other Files should be in the deployed env?
  • Do we want to post this as a separate download?
  • Above questions wrt port opening and configuration

Pull Request Checklist

Thank you for submitting a contribution to Apache Metron.
Please refer to our Development Guidelines for the complete guide to follow for contributions.
Please refer also to our Build Verification Guidelines for complete smoke testing guides.

In order to streamline the review of the contribution we ask you follow these guidelines and ask you to double check the following:

For all changes:

  • [x] Is there a JIRA ticket associated with this PR? If not one needs to be created at Metron Jira.
  • [x] Does your PR title start with METRON-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
  • [x] Has your PR been rebased against the latest commit within the target branch (typically master)?

For code changes:

  • [ ] Have you included steps to reproduce the behavior or problem that is being changed or addressed?
  • [x] Have you included steps or a guide to how the change may be verified and tested manually?
  • [x] Have you ensured that the full suite of tests and checks have been executed in the root metron folder via:

      mvn -q clean integration-test install && build_utils/ 
  • [ ] Have you written or updated unit tests and or integration tests to verify your changes?

  • [ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
  • [ ] Have you verified the basic functionality of the build by building and running locally with Vagrant full-dev environment or the equivalent?

For documentation related changes:

  • [ ] Have you ensured that format looks appropriate for the output in which it is rendered by building and verifying the site-book? If not then run the following commands and the verify changes via site-book/target/site/index.html:

  cd site-book
  mvn site


Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible. It is also recommended that travis-ci is set up for your personal repository such that your branches are built there before submitting a pull request.


2020/11/22 01:47
  • 点赞
  • 收藏
  • 回答