You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@metron.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/04/04 20:47:00 UTC

[jira] [Commented] (METRON-1509) Docs - metron-deployment/other-examples - Adding 0.4.1 AWS EC2 Single Node/Vagrant Method

    [ https://issues.apache.org/jira/browse/METRON-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16426147#comment-16426147 ] 

ASF GitHub Bot commented on METRON-1509:
----------------------------------------

GitHub user as22323 opened a pull request:

    https://github.com/apache/metron/pull/980

    METRON-1509  Docs - metron-deployment/other-examples - Adding 0.4.1 AWS EC2 Single Node/Vagrant Method

    ## Contributor Comments
    [Please place any comments here.  A description of the problem/enhancement, how to reproduce the issue, your testing methodology, etc.]
    
    
    ## 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?
    - [ ] Have you included steps or a guide to how the change may be verified and tested manually?
    - [ ] 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 && dev-utilities/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/LTW-GCR-CSOC/metron master

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

    https://github.com/apache/metron/pull/980.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 #980
    
----
commit 5e9777686b8fd25c53eec9505428ed50e69b122c
Author: as22323 <a....@...>
Date:   2018-04-04T20:26:52Z

    Added Metron 0.4.1 - AWS EC2 Single Node Deployment

commit 224d2afe75a6dc4189aed3d54077b9468fdd7e27
Author: as22323 <a....@...>
Date:   2018-04-04T20:27:12Z

    Update README.md

commit e3e2d8bd207393a0c4a8578cb2f8db598fd27f26
Author: as22323 <a....@...>
Date:   2018-04-04T20:28:36Z

    Update README.md

commit 814cc7a3a71c7deede011179126bb6e333fb6f3f
Author: as22323 <a....@...>
Date:   2018-04-04T20:29:42Z

    Update README.md

----


> Docs - metron-deployment/other-examples - Adding 0.4.1 AWS EC2 Single Node/Vagrant Method
> -----------------------------------------------------------------------------------------
>
>                 Key: METRON-1509
>                 URL: https://issues.apache.org/jira/browse/METRON-1509
>             Project: Metron
>          Issue Type: Improvement
>    Affects Versions: Next + 1
>            Reporter: ashah
>            Priority: Minor
>             Fix For: Next + 1
>
>
> Otto and Nickwallen in Jira:METRON-1434 & PR [916|https://github.com/apache/metron/pull/916] suggested that a proposed AWS/Vagrant method be put into a doc and/or be referred to in a doc. This request updates a Metron doc to include an external community deployment method as a reference in a doc. 
> This updates /metron-deployment/other-examples/README.md to include an external reference to the following deployment method ""Metron 0.4.1 - AWS EC2 Single Node Deployment with Vagrant"" 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)