-
Notifications
You must be signed in to change notification settings - Fork 739
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sysctl reloading #18
Comments
As suggested, I would recommend to use a dict in the default variables defining all the sysctr variables and then in the tasks using the dict to install them on the systems. See also this role https://github.com/picotrading/ansible-sysctl |
You mean something like this, with all variables?
I thought about this, and yes that would make the task clearer and only one reload will happen. But then, I'd have to document all variables inline, e.g. this way:
|
I am using said role and have in my group configuration something like:
I think this is very nice … |
That actually looks good, though I'd still use a
@chris-rock what do you think? The one up there, or the way it currently is:
The first way only executes one task and is probably faster. Also only one sysctl-reload has to happen. Debugging could be harder, though I didn't test it. |
We could also use a third case where we move the items to vars in main.yml. This enables users to overwrite the array. also this may make it easier to document each parameter. We should double-check, that the output will be still useful. It is essential, that operators know what the tasks does but just looking on the output. |
This sounds like the best idea, @chris-rock. Output would be along theses lines:
The first lines and second to last line show the failed setting, the last line shows the successful setting. |
The taskname looks strange. Should be something like "set sysctl" |
Yeah, this will be changed, I just used this one to demonstrate the output. |
cool. then it looks great. |
Kitchen travis
See this discussion.
@ypid, can you please provide context on what solution you would like to see to make the sysctl-tasks clearer?
The text was updated successfully, but these errors were encountered: