ansible in Fedora 23+ (python3)

[Stephen Gallagher]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 11/18/2015 07:00 PM, Adam Williamson wrote:
> On Wed, 2015-11-18 at 17:19 -0500, Bill Nottingham wrote:
>> Adam Williamson (adamwill at fedoraproject.org) said:
>>>> You really really want libselinux-python(2) for that as well
>>>> - it's needed for any file/copy/templating you'd do on the
>>>> node to ensure proper SELinux contexts. (In fact, Ansible
>>>> will abort on the node without it if it detects SELinux in
>>>> use, as it doesn't want to misconfigure the node.)
>>> 
>>> Well, I explicitly addressed that above: I think as soon as you
>>> get into adding packages that are needed for some particular
>>> module, you're on a slippery slope which winds up with
>>> including docker...how do we decide which modules are
>>> 'essential' and which aren't?
>> 
>> I think that the slipperly slope argument is taking the easy way
>> out here. Ensuring that modules like 'file', 'template', and
>> 'copy' work is not the same as including docker in the minimal
>> image.
> 
> OK - so what's the clear and non-controversial definition of
> "modules like 'file', 'template' and 'copy'"? What do those modules
> share in common that we can define clearly and concisely and in a
> way there won't be any serious dispute over?
> 

I was going to suggest "whatever is needed to support
ansible-modules-core", but looking at the code for
ansible-modules-core, it covers a LOT of stuff (including
source-control tools).

So... I dunno.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAlZNxqIACgkQeiVVYja6o6ObcgCfQp6tm9brOHvAjCBFkL4sIltT
baQAn0YzBBhj71mgQFh0ta2bCUioKzfN
=6qRU
-----END PGP SIGNATURE-----