#puppet

/

      • mcarpenter has quit
      • shrug has quit
      • denbeiren has quit
      • shrug joined the channel
      • shrug has quit
      • shrug joined the channel
      • denbeiren joined the channel
      • camlow32_ joined the channel
      • camlow325 has quit
      • camlow32_ has quit
      • denbeiren has quit
      • Dakota-choad has quit
      • newtMcKerr joined the channel
      • denbeiren joined the channel
      • newtMcKerr has quit
      • bva has quit
      • _joes_ has quit
      • vijaycs85 has quit
      • vijaycs85 joined the channel
      • _joes_ joined the channel
      • EZtheOG joined the channel
      • ericsysmin has quit
      • joufflu joined the channel
      • sgtpepper joined the channel
      • Norith joined the channel
      • camlow325 joined the channel
      • benighted has quit
      • turbodog joined the channel
      • cyborg-one has quit
      • sgtpepper has quit
      • rimma_ joined the channel
      • EZtheOG has quit
      • Torreto joined the channel
      • EZtheOG joined the channel
      • nigelk has quit
      • EZtheOG has quit
      • KevinCorcoran has quit
      • benighted joined the channel
      • cryptoduck has quit
      • azerus joined the channel
      • nigelk joined the channel
      • EZtheOG joined the channel
      • scotts has quit
      • Hydrar has quit
      • desaila joined the channel
      • kam270 joined the channel
      • cyrus_mc has quit
      • felipe1982 joined the channel
      • felipe1982
        hi all - I have a question about stankevich/puppet-python module
      • turbodog has quit
      • I have RHEL 6, which ships with python 2.6. I have enabled IUS repo, and can "yum list python27" successfully. To install PIP packages for python2.7, I need to install python27-pip, which provides /usr/bin/pip2.7. How do I get the PYTHON module to use pip2.7 as a provider to install packages?
      • EZtheOG has quit
      • cosman joined the channel
      • scotje has quit
      • cosman has quit
      • EZtheOG joined the channel
      • Guina2e690e1Guin joined the channel
      • githogori joined the channel
      • JoWie has quit
      • EZtheOG has quit
      • cosman joined the channel
      • Miguelzinho joined the channel
      • viq has quit
      • bburt has quit
      • Norith has quit
      • Norith joined the channel
      • Guina2e690e1Guin has left the channel
      • MIMILUKA joined the channel
      • MIMILUKA
        oi
      • camlow325 joined the channel
      • camlow325 joined the channel
      • nigelk has quit
      • `Calvin has quit
      • suziebaunsgard has quit
      • seanh-corona joined the channel
      • sgtpepper joined the channel
      • felipe1982
        can anyone help with using python module from forge?
      • waveclaw
        possibly the person who wrote the module. What does the webpage on forge.puppetlabs.com say for your module in question?
      • EZtheOG joined the channel
      • L3top joined the channel
      • winem_ has quit
      • binford2k
        felipe1982: it will probably use the binary that resolves first in the path
      • felipe1982
        pip2.7 is on the path, but it always calls "pip" instead, which I do not want. How do I make it call pip2.7 instead.
      • binford2k
        ...
      • you cannot without rewriting the module
      • EZtheOG has quit
      • but like I said, you can make "pip" point to whatever you want
      • felipe1982
        then the module does not support different versions, only "system" version - which is contrary to the documentation
      • binford2k
        rename binaries. Use symlinks. etc
      • sgtpepper has quit
      • waveclaw
        do you use pip to install anything for the OS? RHEL 6 uses python for core components. Forcing the system to use the wrong pip would impact packed installs.
      • binford2k
        felipe1982: I don't know that module. If the docs say it can use other versions, then follow what the docs say.
      • waveclaw
        packaged*
      • felipe1982
        our software uses libraries from python2.7, so we install it along with base OS python2.6
      • EZtheOG joined the channel
      • waveclaw
        but the OS has direct support for multiple versions of python installed side-by-side. What binford2k offered would violate that design.
      • binford2k
        waveclaw: correct
      • felipe1982
        @waveclaw I tend to agree
      • waveclaw
        and if you get the python defaults on RHEL to an unworkbale state, well, that is the risk you take. Keep install media handy.
      • unworkable*
      • cosman has quit
      • EZtheOG has quit
      • binford2k
        felipe1982: did you read the docs?
      • viq joined the channel
      • cosman joined the channel
      • waveclaw
        puppet-python looks to just use the OS defaults. The facts at least only look for pip on the default search path.
      • felipe1982
        binford2k: I'm reading - but don't see where to specify binary path pip2.7
      • EZtheOG joined the channel
      • kpease has quit
      • binford2k: can python2.6 do virtualenv? Never used that feature.
      • binford2k
        "version - Python version to use. Default: system default"
      • felipe1982
        binford2k: sorry RHEL6 and python2.7
      • binford2k: i meant
      • waveclaw
        looks like there is support in the module for using a specific python version.
      • felipe1982
        waveclaw: binford2k yes - but that still tries to install package name "python-pip" which does not exist in my repos (using IUS repo). But python27-pip does exist.
      • chadothompson joined the channel
      • waveclaw
        the pkgname is an option for the python::pip define. If you trace the puppet code at the Project URL provided in the module documentation on the forge you can see where the module gets it.
      • felipe1982
        waveclaw: yes - pkgname - the name of the package to install. Required.
      • pip install <pkgname>, but not pip2.7 install <pkgname>
      • waveclaw
        well, this installs packages with a set of execs based on pip_env. So at that point I'm out. If a module author writes shells scripts in puppet I cannot support them.
      • binford2k
        haha
      • waveclaw
        as a hint, though: you'll need to fork stankevich's module and fix lines 118-121 in manifets/pip.pp to stop it using the generic pip executable.
      • felipe1982
        ah i see now
      • waveclaw
        there are probably other defeciences which need to be addressed. How this is a supported module is beyond me. I wouldn't let it be installed in our work environment.
      • binford2k
        or you can do as the author intended and make a virtualenv with python2.7 and use that.
      • I don't know if python2.6 does virtualenv, to answer your question above
      • felipe1982
        so this module has incomplete implementation of using non-system python install on RHEL.
      • binford2k
        but that would be the first avenue to explore, as that's what the module supports.
      • thanks for putting words in my mouth :)
      • waveclaw
        binford2k: virtualenv's have defeciencies for support of this sort. The guy who wrote the module is a very big pro-VE guy.
      • binford2k
        yeah. But if he's going to use this module, that's what he's got to work with.
      • felipe1982
        I"m going to guess that VE won'g help me, because it won't execute python2.7 version of PIP that I need/want.
      • is there a better module for what I need/want?
      • waveclaw
        if you are a dev working on your own dev stuff in Python, virtualenv's are the way to go.
      • felipe1982
        not dev - this is production.
      • waveclaw
        if you are an ops wennie trying to get a system working virtualenv's are the devil's toys.
      • binford2k
        "because it won't execute python2.7 version of PIP", you realize that's the whole point of a virtualenv, right?
      • felipe1982
        i'm trying to integrate puppet into employers systems, and automate what I can.
      • binford2k: didn't know that.
      • waveclaw
        so, felipe1982, how well have you documented what you did to get to python2.7? Because to use this module you are going to have to deploy a virtualenv copy of that work to do it.
      • binford2k
      • felipe1982: note that I'm not saying that virtualenvs are a great solution, I'm just saying that's all this module supports
      • felipe1982
        binford2k: ok - that's interesting, I'll have a look
      • waveclaw
        just be aware that this kind of 'packaging' is not ITIL or controlled. You are going to have to manage your depenencies yourself, enforce version locking manually and patch very very carefully.
      • binford2k
        ^^
      • felipe1982: sorry for sounding like a jerk. I didn't realize you weren't familiar with virtualenvs
      • waveclaw
        fortunately these are all things Puppet is very good at which is probably why the module was written. It seems to be just a wrapper around the pyenv process.