svc/monitoring: use of `become` at the playbook level
The become
is declared at the playbook level and thus enforced on remote machines coming from any provider.
But, for example, on G5k we're already root on the machine and thus we don't need to call sudo
before issuing any ansible code.
Since that looks like a provider specific requirement (IOTlab ? ) I propose to set the ansible_become
variable at the host level (Host.extra
can be used for that).
any idea @demourad why become
is needed ?
Edited by SIMONIN Matthieu