{"action":"closed","issue":{"url":"https://api.github.com/repos/ansible/ansible/issues/11729","labels_url":"https://api.github.com/repos/ansible/ansible/issues/11729/labels{/name}","comments_url":"https://api.github.com/repos/ansible/ansible/issues/11729/comments","events_url":"https://api.github.com/repos/ansible/ansible/issues/11729/events","html_url":"https://github.com/ansible/ansible/issues/11729","id":97171789,"number":11729,"title":"Exclude paramiko module from ansible build?","user":{"login":"Andrew415","id":6968468,"avatar_url":"https://avatars.githubusercontent.com/u/6968468?v=3","gravatar_id":"","url":"https://api.github.com/users/Andrew415","html_url":"https://github.com/Andrew415","followers_url":"https://api.github.com/users/Andrew415/followers","following_url":"https://api.github.com/users/Andrew415/following{/other_user}","gists_url":"https://api.github.com/users/Andrew415/gists{/gist_id}","starred_url":"https://api.github.com/users/Andrew415/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Andrew415/subscriptions","organizations_url":"https://api.github.com/users/Andrew415/orgs","repos_url":"https://api.github.com/users/Andrew415/repos","events_url":"https://api.github.com/users/Andrew415/events{/privacy}","received_events_url":"https://api.github.com/users/Andrew415/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-07-25T00:04:20Z","updated_at":"2015-07-25T00:23:40Z","closed_at":"2015-07-25T00:23:40Z","body":"Hi,\r\n\r\nI was wondering if there could be any potential problems of excluding paramiko from Ansible? According to http://www.ansible.com/blog/2014/01/15/ssh-connection-upgrades-coming-in-ansible-1-5 you used it in the past for ControlPersist which is a feature available in OpenSSH 5.6 (released maybe a year ago) and as such appears redundant. You also list some rationales for having it in \"How do I get ansible to reuse connections, enable Kerberized SSH, or have Ansible pay attention to my local SSH config file?\"\r\nhttps://docs.ansible.com/ansible/faq.html which seems to me to be a legacy issue only. Furthermore these explanations:\r\n\r\n\"Paramiko is great for starting out, but the OpenSSH type offers many advanced options.\" \r\n\r\nThis line doesn't make any sense. Great for starting what out?\r\n\r\n\"You will want to run Ansible from a machine new enough to support ControlPersist, if you are using this connection type.\" \r\n\r\n\"A machine\" or openssh version? \r\n\r\n\"You can still manage older clients. If you are using RHEL 6, CentOS 6, SLES 10 or SLES 11 the version of OpenSSH is still a bit old, so consider managing from a Fedora or openSUSE client even though you are managing older nodes, or just use paramiko.\"\r\n\r\nHow about you avoid all this confusing nonsense and just recommend using the latest openssh?\r\n\r\nCaveat emptor: I don't know anything about https://github.com/paramiko/paramiko but it has not been updated since April (stable?) and it has a large number of bug and pull requests that seems like a lot of work for one guy to be working part time let alone full time. \r\n\r\nBasically I want to make sure I can exclude this from my ansible builds because adding unnecessary code to my environment adds unnecessary risk. \r\n\r\nIf this is the case then you should also remove it from the list of required modules on https://docs.ansible.com/ansible/intro_installation.html and list it as optional.\r\n\r\nThanks!"}}