It's really cool to see someone else doing this.
> Jenkins and similar tools could integrate with Vagrant to built
> an environment and run some tests, which would probably be a valid
> way to do it; at least it could be another layer of testing.
This is how I'm doing it. I have a rake build task in Jenkins which spins
up a Vagrant VM set when something changes.
The tricky bit is figuring out what subset needs to be tested and what to
do about the network(which I'm still working on). I've been banging my
head against a wall for a while trying to puzzle out how to do this
easily, and eventually made peace with the fact I'm just going to have to
write something.
> But we already have service monitors on the infrastructure which,
> ostensibly, tells us if a host is doing what is it "programmed" to
> do. Using another suite of automated test scripts is a duplication
> of effort and ripe for problems. The monitor and Jenkins may not be
> testing the same things, leading to a situation where a
> configuration tests OK but breaks in production. On the other hand,
> a service monitor expects to be monitoring a system over a long
> period of time and none that I know of have the ability to "test
> host X for service Y right now and only once".
Yes, and this is effectively functional testing. I'm using my existing
nagios and nrpe configs(which are done via CM automagically) for testing
from within the Vagrant environment. What would be an NRPE check from
nagios becomes a "build" status health check. I can then call out to NRPE
via the rakefile, or use a virtual monitoring box within the vagrant env
which dumps to the shared folder and parse the results.
It can then be extended as necessary, but I haven't thought of a good
reason to that's not "some dev requires something specific."
--Nick
_______________________________________________
Discuss mailing list
[email protected]
https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss
This list provided by the League of Professional System Administrators
http://lopsa.org/
