Replace hardcoded configurations by play vars

[fwiesweg]

Hi,

I pulled some of the hard-coded constants into the playbook and command line arguments. If you feel like you'd like this upstream, let me know and I'll update the README. Fixes and improvements are of course welcome.

Best,
Florian

[fwiesweg]

Oh and thanks for the good work! Really made our builds run quite a bit quicker.

[spanezz]

Thanks, I like the direction this is going!

Unless I'm mistaken, nspawn-runner with this change would change behaviour on existing deployments. I wonder if the previous hardcoded values could be used as defaults when nspawn_runner_* keys are not present in the configuration, to allow smooth upgrades?

@kapouer, since you're also having nspawn-runner deployed, what do you think?

[kapouer]

Indeed, keeping default behavior is good, unless there are better defaults which should be used.

[fwiesweg]

There you go ;-) I have not gotten around to test the latest commit with the old defaults in our installation, but the changes are quite straightforward.

[fwiesweg]

Just tested it on our ci infrastructure and of course found some ... not so intelligent bugs. I fixed them all and updated the branch. README has been updated as well.