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

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

GitHub user nickwallen reopened a pull request:

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

    METRON-1785 Automate deployment of packet capture for development 
environment

    While trying to test #1201 , I fixed some issues with the Ansible install 
of the components required for testing packet capture.  I added instructions 
for how to do this in the README.
    
    ## Testing
    
    1. Spin-up the development environment and validate that alerts are visible 
in the Alerts UI and run the Metron Service Check in Ambari.
    
    1. Follow the instruction in the README, to install and start all of the 
components for capturing packets.  Ensure that you can search and find these 
packets using the Alerts UI > PCAP tab.
    
    ## Pull Request Checklist
    
    - [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)?
    - [x] 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:
    - [x] Have you written or updated unit tests and or integration tests to 
verify your changes?
    - [x] 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)?
    - [x] Have you verified the basic functionality of the build by building 
and running locally with Vagrant full-dev environment or the equivalent?


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

    $ git pull https://github.com/nickwallen/metron METRON-1785

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

    https://github.com/apache/metron/pull/1205.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 #1205
    
----
commit 5e7afa0d61766c5bcd45e19143a4568a9da3779e
Author: nickallen <nickallen@...>
Date:   2018-09-19T18:44:29Z

    Add ability to easily deploy components for testing pcap capture

commit f6b82d0199927df0c81d84390f3987171a0321c4
Author: Nick Allen <nick@...>
Date:   2018-09-19T19:58:49Z

    Added instructions in README

commit c15c2d902f028e84f1959c06377cb68a3c7b8111
Author: Nick Allen <nick@...>
Date:   2018-09-19T20:12:13Z

    Fixing README formatting

commit 33de7740235a17f9cf35b060c6d75ee4395c6786
Author: Nick Allen <nick@...>
Date:   2018-09-19T20:13:53Z

    Fixing README formatting

commit 1a561f013ce0cdb0b48a73a6e374cb7dc6acf6ba
Author: Nick Allen <nick@...>
Date:   2018-09-19T20:19:34Z

    By default, we do not want the pcap stuff deployed

----


> Automate deployment of packet capture for development environment
> -----------------------------------------------------------------
>
>                 Key: METRON-1785
>                 URL: https://issues.apache.org/jira/browse/METRON-1785
>             Project: Metron
>          Issue Type: Improvement
>            Reporter: Nick Allen
>            Assignee: Nick Allen
>            Priority: Major
>
> I added instructions for deploying all of the components required to generate 
> and capture network packets in the development environment.  I also fixed 
> some issues I ran into along the way.



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

Reply via email to