ansible-fprobe role (https://github.com/juju4/ansible-fprobe) + patches for fedora
Go to file
2017-07-15 12:33:48 -04:00
defaults Initial commit on github 2016-10-30 15:40:48 -04:00
handlers Initial commit on github 2016-10-30 15:40:48 -04:00
meta sync repositories - add Jenkinsfile 2017-01-07 03:55:05 -05:00
tasks fprobe starting on second time only sometimes? 2017-07-15 12:33:48 -04:00
templates sync repositories - add Jenkinsfile 2017-01-07 03:55:05 -05:00
test review kitchen test to validate in kitchen+lxd 2017-07-11 20:45:34 -04:00
vars Initial commit on github 2016-10-30 15:40:48 -04:00
.kitchen.vagrant.yml Initial commit on github 2016-10-30 15:40:48 -04:00
.kitchen.yml README update 2017-02-02 21:18:50 -05:00
.travis.yml disable travis trusty test - stalling 2017-01-07 04:19:47 -05:00
.travis.yml.docker vagrant update for travix/lxd/kitchen, travis space escape 2017-04-02 16:26:12 -04:00
.travis.yml.lxd sync repositories - add Jenkinsfile 2017-01-07 03:55:05 -05:00
.travis.yml.lxd-kitchen review kitchen test to validate in kitchen+lxd 2017-07-11 20:45:34 -04:00
.travis.yml.simple sync repositories - add Jenkinsfile 2017-01-07 03:55:05 -05:00
get-dependencies.sh sync repositories - add Jenkinsfile 2017-01-07 03:55:05 -05:00
Jenkinsfile sync repositories - add Jenkinsfile 2017-01-07 03:55:05 -05:00
LICENSE Initial commit on github 2016-10-30 15:40:48 -04:00
README.md README update 2017-02-02 21:18:50 -05:00

Build Status - Master Build Status - Devel

Fprobe ansible role

Ansible role to setup fprobe as netflow exporter http://fprobe.sourceforge.net/

Requirements & Dependencies

Ansible

It was tested on the following versions:

  • 1.9
  • 2.0
  • 2.2

Operating systems

Ubuntu 14.04, 16.04 and Centos 7

Example Playbook

Just include this role in your list. For example

- host: all
  roles:
    - juju4.fprobe

Variables

Nothing specific for now.

Continuous integration

This role has a travis basic test (for github), more advanced with kitchen and also a Vagrantfile (test/vagrant). Default kitchen config (.kitchen.yml) is lxd-based, while (.kitchen.vagrant.yml) is vagrant/virtualbox based.

Once you ensured all necessary roles are present, You can test with:

$ gem install kitchen-ansible kitchen-lxd_cli kitchen-sync kitchen-vagrant
$ cd /path/to/roles/juju4.fprobe
$ kitchen verify
$ kitchen login
$ KITCHEN_YAML=".kitchen.vagrant.yml" kitchen verify

or

$ cd /path/to/roles/juju4.fprobe/test/vagrant
$ vagrant up
$ vagrant ssh

Troubleshooting & Known issues

License

BSD 2-clause