Charm needed: conn-check

[Wes Mason]

conn-check [1][2] is a tool for verifying network connections between application deployments and related infrastructure, which we're using in ~onlineservices to verify our deploys for things such as related services (internal and external) being up or available due to firewall rules and/or network routing.

It can also be run as a Nagios check to regularly check the status of connections.

[1] https://launchpad.net/conn-check
[2] https://pypi.python.org/pypi/conn-check

[Wes Mason (wesmason)]

Side note: there is a precise branch in progress, but it takes some extra work as it requires a pip upgrade within a venv to support wheels under precise (as python-pip in the precise repos is too old to support wheels and the dir scraping).

[Review Queue (review-queue)]

This items has failed automated testing! Results available here http://reports.vapour.ws/charm-tests/charm-bundle-test-10357-results

[Marco Ceppi (marcoceppi)]

Hi Wes! Thanks for working on this. This seemed to fail in our testing environment, partially because of missing dependencies. If you create a tests directory with a setup bash script which installed all the components (ansible, nosetest, etc) assuming it's a clean system, this would allow the testing infrastructure to execute your charms tests and we can re-run it.

[Whit Morriss (whitmo)]

Howdy Wes!

To echo Marco, the tests are failing on the ansible syntax check since there is not a make target that installs ansible and puts the ansible-playbook command on the path. I'd suggest conditional creating a virtualenv for ansible in the makefile.

With an ansible based charm, unit-tests might not make any sense, so you could remove the test tar get and the generated unit-test directory. What would be super helpful is a few functional tests using amulet which will help us keep up with changes over time in the automated testing system.

Anyway, thanks for your work on this!

-w