GitHub user ottobackwards reopened a pull request:
https://github.com/apache/metron/pull/690
METRON-1091 Package STELLAR shell as stand alone
This PR adds metron-deployment/packaging/archive, and the
metron-stellar-shell module.
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.
## Testing
- 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
- 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](https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=61332235)
for the complete guide to follow for contributions.
Please refer also to our [Build Verification
Guidelines](https://cwiki.apache.org/confluence/display/METRON/Verifying+Builds?show-miniview)
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](https://issues.apache.org/jira/browse/METRON/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel).
- [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/verify_licenses.sh
```
- [ ] 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](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] 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
```
#### Note:
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](https://travis-ci.org) is set up
for your personal repository such that your branches are built there before
submitting a pull request.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ottobackwards/metron stellar_stand_alone
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/metron/pull/690.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #690
----
commit 81c0badc31353813e0d884c860c0c854b2026709
Author: Otto Fowler <ottobackwa...@gmail.com>
Date: 2017-08-09T19:25:33Z
Initial pass at packaging stellar shell for stand alone deployment.
New archive area under packaging for things packaged as archives
New stellar script that doesn't rely on having bigtop installed
commit a6acc137d9fb31baeb8c2e7d9d4076bde6b098ba
Author: Otto Fowler <ottobackwa...@gmail.com>
Date: 2017-08-11T18:14:58Z
Merge branch 'master' of https://github.com/apache/metron into
stellar_stand_alone
commit c315e1ce52c6dc44a6eb688b4387f7a89a1cfc97
Author: Otto Fowler <ottobackwa...@gmail.com>
Date: 2017-08-31T19:44:20Z
refactor to stellar centric deployment
commit bde23812615a3c24b034d2b48b3127a8f5b5b900
Author: Otto Fowler <ottobackwa...@gmail.com>
Date: 2017-08-31T19:44:24Z
Merge branch 'master' of https://github.com/apache/metron into
stellar_stand_alone
----
---
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.
---
