I just go pip route when it comes to ansible. Here is my vagrant repo to get you up and running for anyone interested (if nothing else but to cheat off)
https://github.com/OldCrowEW/vagrant-ansible On Fri, Sep 23, 2016 at 1:56 PM David Shrewsbury <shrewsbury.d...@gmail.com> wrote: > Oh yuck. > > Yeah, mixing distribution packages with pip packages can get really ugly, > especially > as the operating system distribution gets older and package versions get > further apart. > > -Dave > > > > On Fri, Sep 23, 2016 at 1:49 PM, Richard Eggert <richard.egg...@gmail.com> > wrote: > >> The first thing I ran into was a conflict with the installed version of >> pbr. >> >> To get around this, I set up a virtualenv, and tried installing into that. >> >> I then went down a rabbit hole of dealing with a few dozen transitive >> dependencies, at least a few of which required me to install gcc in order >> to install them. >> >> In a few cases, I found that the latest installed version of a transitive >> dependency depended on a newer version of another library than what was >> available from the corporate Pypi mirror. I got around these issues by >> manually specifying older versions of the libraries that had such >> dependencies. >> >> I managed to get pretty far like this, until pip tried to install cffi, >> which resulted in a compilation error from gcc: >> UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 75: >> ordinal not in range(128) >> >> I then tried setting the environment variable LC_ALL=C as I had seen >> suggested in various places. This resulted in another error: >> >> 'FFI_DEFAULT_ABI' undeclared >> >> Another Google search later, and I yum installed libffi-devel and tried >> again. cffi installed successfully. >> >> I then attempted to install shade again. This resulted in dozens of >> compilation errors from _openssl.c while attempting to transitively install >> the cryptography library. >> >> >> I had no idea what to do at this point and gave up. >> >> >> ~Rich >> >> On Friday, September 23, 2016 at 1:12:52 PM UTC-4, David Shrewsbury wrote: >>> >>> Ansible isn't responsible for packaging and shipping of the libraries >>> that the >>> modules may use. Shade isn't packaged on Centos or EPEL simply because >>> no one from the community has stepped up to make those packages >>> available. >>> It is available on Ubuntu and Fedora distributions, but that doesn't >>> help you >>> unfortunately. >>> >>> Installing it via pip was the right thing for you to do in your >>> circumstance, but >>> I'm curious as the "Python Dependency Hell" you mentioned. Could you >>> elaborate >>> on that a bit (if nothing else just to satisfy my curiosity)? >>> >>> -Dave >>> >>> >>> On Friday, September 23, 2016 at 11:29:55 AM UTC-4, Richard Eggert wrote: >>>> >>>> I installed Ansible using yum on CentOS 6.8 via a corporate mirror of >>>> EPEL. However, when I attempted to use the os_server module to interact >>>> with the OpenStack API, it failed saying that "shade" is required. When I >>>> went to install Shade via Yum, I discovered to my horror and dismay that >>>> Shade (python-shade) is not available from EPEL, making it impossible to >>>> install via Yum. I attempted to install it via pip but quickly fell into >>>> the ninth circle of Python Dependency Hell. >>>> >>>> How could Ansible be available via EPEL while not also making available >>>> one of the libraries that a module it ships with depends upon? Was this an >>>> oversight? >>>> >>> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "Ansible Project" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/ansible-project/4YgEuScim5E/unsubscribe >> . >> To unsubscribe from this group and all its topics, send an email to >> ansible-project+unsubscr...@googlegroups.com. > > >> To post to this group, send email to ansible-project@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/ansible-project/9f033d68-2f94-409a-ab70-fff20dae0a25%40googlegroups.com >> <https://groups.google.com/d/msgid/ansible-project/9f033d68-2f94-409a-ab70-fff20dae0a25%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > David Shrewsbury (Shrews) > > -- > You received this message because you are subscribed to the Google Groups > "Ansible Project" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to ansible-project+unsubscr...@googlegroups.com. > To post to this group, send email to ansible-project@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/ansible-project/CAB91eg4YvxqX0EcDn6iL3N3jkJHt7nCBaPWjdFL8AyhbU9P56w%40mail.gmail.com > <https://groups.google.com/d/msgid/ansible-project/CAB91eg4YvxqX0EcDn6iL3N3jkJHt7nCBaPWjdFL8AyhbU9P56w%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to ansible-project+unsubscr...@googlegroups.com. To post to this group, send email to ansible-project@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAKsMCEQf_wUbv7AWY0r3w20ONAo6RsG5gF5bh1YfDmwvFs0mRQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
