For the record, I'm now trying to split apart the problem. Whatever integration / scheduling tool I'll use, it will just call defined previously written Ansible playbooks.
The idea behind this is: * No XML wrappers around shell commands (seriously, what are some of these people taking) * I want to be flexible to switch the scheduler, so it makes sense to have an intermediate layer (If I'm lucky and my company grows then there will be a point where it's far more efficient to go and buy some enterprise scheduler. These things are good at doing the right thing if a job aborts, meaning a more hands-off operation for me) * Ansible is very "direct steer", you write down your jobs (playbooks) while you test them and it's a lot of fun to set up jobs like "snapshot the VM, bump the VMs ram, patch it, reduce the VM" * It doesn't put anything in your way to allow reruns. That is great, meaning an interrupted job can catch up, you just have to make smart enough modules What I'll need to watch out for: * Versioning, playbook changes need to be reflected in jobs so no apples-to-oranges comparisms happen. * Abuse: Not running any config changes from there (this will be a problem once there's more people). One side is cfengine with a vertical learning curve made of stone and on the other side is the easy hipster tool you're not supposed to use. possibly i'll be able to put in enough granularity on permissions to limit ansible to the intended job * Reporting is of unknown quality so far (just dont know it) * No "big" jobs, just very small ones. Otherwise it'll be hard to have them resume. Example: A VM host has issues, I'm moving machines off it, but it crashes during such a backup. The backup should resume later on, if it's still supposed to. That only works if you do that on the scheduler side imho. The general idea of this is adding reliabilty to these tasks where you normally spend a lot of time worrying if they go right or log on during the morning hours to check a result. (And we all do know that, right?) Thoughts? Florian _______________________________________________ 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/
