metron-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From nickwallen <>
Subject [GitHub] incubator-metron pull request #410: METRON-645 Unable to Start Fastcapa Test...
Date Tue, 03 Jan 2017 20:00:06 GMT
GitHub user nickwallen opened a pull request:

    METRON-645 Unable to Start Fastcapa Test Environment

    The Fastcapa Test Environment could not be started.  There were three problems that needed
    1. The version of DPDK being used (2.2.0) does not work with newer versions of the Linux
kernel.  See [this thread]( for more
information. Updating to the latest DPDK release, 16.11 which is N+3 from 2.2.0, resolved
this problem.
    2. The `install_pcap_replay` variable was not defined.  This variable is required and
was added sometime after the creation of the Fastcapa test environment.
    3. In the Fastcapa Ansible deployment scripts, I moved all tasks into a separate `tasks`
block.  Previously, Ansible was more forgiving and allowed tasks to be embedded in the `roles`
    The Ansible deployment includes a complete validation process at the tail end of deployment.
 If the process completes successfully, then you know that it is working.  Look for the message
"Successfully received a Kafka message from fastcapa!"  The message, or absence thereof, is
hard to miss.
    cd incubator-metron/metron-deployment/vagrant/fastcapa-test-platform
    vagrant up

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

    $ git pull METRON-645

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 #410
commit 88e378e7332f711b54982190d67b647210fcdabf
Author: Nick Allen <>
Date:   2017-01-03T19:29:45Z

    METRON-645 Unable to Start Fastcapa Test Environment


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