#puppet

/

      • nahmad1 joined the channel
      • mdobrev joined the channel
      • Hypnoz joined the channel
      • scavmartin joined the channel
      • otter768 joined the channel
      • turbodog joined the channel
      • scavmartin
        I have been looking for a way to change the ruby puppet uses for instance i have a puppet agent that has ruby2.2 set as the default “ruby” command I want puppet agent to use the “ruby1.9.1” command instead. Is this possible?
      • radiocats joined the channel
      • radiocats has quit
      • radiocats joined the channel
      • rnelson0
        Helio-: even if you could just do things like configure ntp and syslog it would be a start
      • nahmad1 has quit
      • scavmartin_ joined the channel
      • kellyp joined the channel
      • scavmartin has quit
      • scavmartin_ is now known as scavmartin
      • BarnacleBob joined the channel
      • torrancew
        scavmartin: that depends on a number of things - primarily, how did you install puppet?
      • _morgan has quit
      • scavmartin
        via foreman, can and then I upgraded ruby via puppet and it broke puppet :)
      • torrancew
        scavmartin: by that do you mean that you used the "foreman installer" to install puppet?
      • scavmartin
        well the server was provisioned by foreman, the puppet is a package installed from puppetlabs apt repo
      • sorry
      • torrancew
        what distro?
      • scavmartin
        14.04 (trusty)
      • GillesM has quit
      • lindenle has quit
      • chitopunk has quit
      • Dr_Natas
        knowing that I have a site.pp file how can I push updates to all the clients inside that file without logging in to each client and telling them up "puppet apply -t" ?
      • torrancew
        you are kind of screwed. I think you can set the default ruby for the whole system via the defaults mechanism, but I don't know of a simple way to always use ruby foo with app bar on debian/ubuntu. Redhat has SCLs for this, I think.
      • chrisportman joined the channel
      • Dr_Natas: typically, folks run puppet on a schedule (via cron, or as a daemon)
      • scottyc joined the channel
      • kellyp has quit
      • lindenle joined the channel
      • edux has quit
      • scavmartin
        There is no way to override the ruby executable path\name that puppet uses? I noticed the “rubysitedir” fact, can that be overridden easily? Yes I know I can use alternatives but they want the default to be ruby2.2, so I cannot switch the default ruby to point to the older version.
      • torrancew
        scavmartin: well, you could swap to a PC1 package, which provides its own, compatible ruby
      • tessier_ has quit
      • and is resistant to changes to the system ruby
      • _morgan joined the channel
      • Rapture
        how would I set a default value in a template? eg. input_type: <%= @input_type %> (with a default type of log) ?
      • torrancew
        or you can do a bunch of nonsense with file edits or symlinks in hopes of either tricking puppet into running under the old system ruby, or into being able to run under the new one
      • but that's officially not something I volunteer to support :)
      • Rapture: you tend to set a default for the /variable/ in your manifest
      • and then use that variable in the template
      • is there some reason you need/want the default in ERBV?
      • ERB*?
      • Dr_Natas
        torrancew: Ok I just wanted to see if there was a lazy way I can push updates when I wanted at will. All at once without resorting to cron jobs or others.
      • torrancew
        Dr_Natas: if you want to trigger puppet runs across your fleet, that is a pretty strong use case for mcollective
      • Rapture
        torrancew: no reason to put it in the ERB I suppose. I'm building a config file so users can do something like: http://pastebin.com/raw.php?i=sGbGBgGh in his/her node manifest. The configfile is an erb template
      • chrisportman has left the channel
      • torrancew
        but not a thing you can do with puppet alone (agents no longer support listening on a port for such requests, though they once did)
      • Rapture: yeah, just give your parameter a default value
      • binford2k
        Dr_Natas: the 'lazy' way of doing it is just letting Puppet run on a schedule so the nodes are always up to date with your configuration model
      • tomfoolry joined the channel
      • Rapture
        so currently I have $input_type = undef -- I can just make that a string and then if a user specifies it in their manifest it will override?
      • foul_owl
        What's the easiest and quickest way to say class profiles::apache depends on class profiles::nfs?
      • jtreminio
        foul_owl: when you call profiles::apache do a requires
      • binford2k
        Rapture: yes, do it in your manifest. If for some reason you HAVE to default in the erb, it can be done with <%= @variable || 'default value' %>
      • Rapture: but that's bad practice because it's opaque
      • Dr_Natas
        I'm under the development phase where I'm testing Centos5 & Centos6 & Centos7 all at once. I just didn't want to switch tabs and execute "puppet apply -t" 3x.
      • foul_owl
        I have to do it when I call profiles::apache?
      • Rapture
        @binford2k: ok thanks
      • foul_owl
        Can I put the requirement in the class profiles::apache itself?
      • binford2k
        Dr_Natas: mco puppet runall
      • scavmartin
        torrancew: the PC1 release seems to have the same issue
      • shdwdruid joined the channel
      • mosburn joined the channel
      • torrancew
        scavmartin: I do not follow
      • Rapture: undef works fine, too, fwiw
      • rasca has quit
      • doesn't have to be quoted
      • but if you want the default to be "logs", then set it to "logs"
      • scavmartin
        torrancew: I switched to the PC1 repo, uninstall puppet and puppet-common and re-installed. I confirmed the new packages was from PC1. It still seems to use the ruby2.2 and not an embedded version.
      • Rapture
        torrancew: got it. testing now :) thanks
      • torrancew
        scavmartin: are you sure that it's /the/ ruby2.2, and not just /a/ ruby2.2?
      • mosburn has quit
      • scavmartin
        it has the same paths as the previous errors
      • so I believe that it is using the same ruby executable which is 2.2
      • rasca joined the channel
      • torrancew
        then I suspect something isn't right, as PC1 definitely brings its own rubies to the table. If you care to share some pastes of your error messages, we can maybe try to dig in further'
      • IanV0rn2341 joined the channel
      • Matriculate has quit
      • seanh-corona has quit
      • otter768 joined the channel
      • scavmartin has quit
      • CyrilPeponnet is now known as CP|AFK
      • scavmartin joined the channel
      • seanh-corona joined the channel
      • Voyd_ has quit
      • thirdkni_ has quit
      • holodnak has quit
      • lindenle has quit
      • scavmartin
        torrancew: https://gist.github.com/anonymous/33ec577530c2e... has the error output and some data on a fix I did try
      • torrancew
        scavmartin: issue a "which puppet", please
      • seanh-corona has quit
      • nahmad1 joined the channel
      • _ingo has quit
      • (have to run shortly)
      • holodnak joined the channel
      • mlan joined the channel
      • lindenle joined the channel
      • thirdknife joined the channel
      • scavmartin: sorry, waited as long as I could. The bank won't do the same for me! tl;dr I suspect you may still have some non-PC1 puppet hanging out, that is higher priority in $PATH or something
      • scavmartin_ joined the channel
      • scavmartin_
        torrancew: Sorry IRC client issues, /usr/bin/puppet
      • kpease has quit
      • turbodog has quit
      • scavmartin has quit
      • scavmartin_ is now known as scavmartin
      • Rapture
        torrancew: http://pastebin.com/raw.php?i=jqaKJJd8 -- Did I do this wrong?
      • fw_ joined the channel
      • turbodog joined the channel
      • nahmad1 has quit
      • Hypnoz joined the channel
      • torrancew
        scavmartin: PC1 does not live in /usr/bin
      • tomfoolry_ joined the channel
      • Rapture: don't see an error there, may need mroe context
      • but really, gotta go now!
      • torrancew turns into a pumpkin
      • Rapture
        kk
      • later
      • nahmad1 joined the channel
      • aqua^c has quit
      • aqua^c joined the channel
      • mdobrev joined the channel
      • oneplusi joined the channel
      • Hypnoz joined the channel
      • spredzy has quit
      • spredzy joined the channel
      • lindenle has quit
      • lindenle joined the channel
      • foul_owl
        Does puppet create parent directories yet?
      • binford2k
        yet? It never will
      • foul_owl
        I have probably 30 nested directories I need to creat
      • Hmm
      • Rather directories nested 30 levels deep :(
      • binford2k
        there is no way to manage parent directories consistently in a sane fashion
      • if you accept all the tradeoffs of that, then you can install modules to do it
      • Miguelzinho joined the channel
      • but core Puppet won't ever do that
      • vikas027 joined the channel
      • jbehrends has quit
      • ryno75 has quit
      • lindenle has quit
      • thirdknife has quit
      • jzeolla joined the channel
      • lindenle joined the channel
      • _cmd_ joined the channel