[Puppet Users] Recommend a good tutorial on using Hiera as an ENC?
Can anyone recommend a good tutorial on using Hiera as an ENC? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Extending Puppet for network device management
Thanks a lot for the pointer :) Means a lot to me thanks :) On Sat, Jun 8, 2013 at 9:10 AM, wrote: > > Is there any developer guide or something similar which I can follow to >> know internal working of puppet in detail? so that I can go to right places >> and test/add modules. >> Any material in this direction will be very helpful to me. >> > > Vatsa, > > There are a couple of puppetlabs documents on creating custom types: > http://docs.puppetlabs.com/guides/custom_types.html > http://docs.puppetlabs.com/guides/complete_resource_example.html > > as well as books (haven't read these, so can't vouch personally): > - Puppet Types and Providers > - Pro Puppet (this covers lots of puppet topics) > > Though arguably most helpful will be looking at existing puppet types and > providers: > https://github.com/puppetlabs/puppet/tree/master/lib/puppet/type > https://github.com/puppetlabs/puppet/tree/master/lib/puppet/provider > and various modules on forge.puppetlabs.com > > Eric > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-users+unsubscr...@googlegroups.com. > To post to this group, send email to puppet-users@googlegroups.com. > Visit this group at http://groups.google.com/group/puppet-users?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] ruby issue
Dear Stuart, Kind of my first steps into puppet on RHEL 6 and I wonder how you manage to solve the rubygems issue. Since I'm using RHEL 6.4 (.x86_64) in my test env. *with only puppetlabs repo* I can't see from where I can get the rubygems missing package. As you after wiki'd it :) can you give me a piece of advise in here or attached your docs to help me through ? Thanks, --Yizhar On Saturday, June 1, 2013 8:49:16 AM UTC+3, Stuart Cracraft wrote: > Hey, good news. > > All is well. > > Ruby & related are good. Puppet too. And Red Hat. > > Also, I've documented/wiki'd the Puppet Master + Client install with > respect > to bare metal to delivered system for all related aspects and transmitted, > fully, > disclosed entirely, to staff. > > Next week, I will be tuning the configuration file on master and agents > and > writing many more puppet patterns plus training staff. > > As it is their only hope! > > --Stuart > > P.S. The firm's personnel have had heart attacks, strokes and other major > maladies amongst > staff in the past year due to the LACK OF AUTOMATION!!! > > Puppet is the Cure > > Kick Chef and CF Engine's non-collective butts! > > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] puppet 3.x, rubygem pkg can't be found on a RHEL 6.4
Dear T.J./Keith Kind of getting the same issue T.J. got regards rubygems. Tried to run # yum-config-manager --enable rhel-6-server-optional-rpms BUT since I'm using RHEL 6.4 (.x86_64) in my test env. *with only puppetlabs repo* it's not working for me. Is it a repo issue ? What should I add since I don't want to activate my RHN subscrition as I'm only at the testing phase right now. Can I installed it seperatly for .rpm ? what version do I need than ? Thanks, Yizhar A. On Thursday, April 11, 2013 11:13:46 PM UTC+3, T.J. Yang wrote: > Keith, > > Thanks for the following command, I can install puppet on RHEL 6.4 now. > > > tj > On Thu, Apr 11, 2013 at 5:12 AM, Keith Burdis > > wrote: > >> Try running: >> >> # yum-config-manager --enable rhel-6-server-optional-rpms >> > >> - Keith >> >> >> On 10 April 2013 10:04, Yusup Ashrap >wrote: >> >>> I have having the same problem with install puppet on redhat 6.2. >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Puppet Users" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to puppet-users...@googlegroups.com . >>> >>> To post to this group, send email to puppet...@googlegroups.com >>> . >>> Visit this group at http://groups.google.com/group/puppet-users?hl=en. >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >>> >>> >> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "Puppet Users" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/puppet-users/ZIx9U3Ai1ww/unsubscribe?hl=en >> . >> To unsubscribe from this group and all its topics, send an email to >> puppet-users...@googlegroups.com . >> To post to this group, send email to puppet...@googlegroups.com >> . >> Visit this group at http://groups.google.com/group/puppet-users?hl=en. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > > > > -- > T.J. Yang > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Issue installing on RHEL 6 (2.6.32-358.2.1.el6.x86_64)
On Fri, Jun 7, 2013 at 4:45 PM, Kenneth Edgar wrote: >Protected multilib versions: libselinux-2.0.94-5.3.el6.i686 != > libselinux-2.0.94-5.3.el6_4.1.x86_64 > You could try using --skip-broken to work around the problem > You could try running: rpm -Va --nofiles --nodigest Basically this indicates a problem with your yum configuration or repos. What it's refusing to do is to install differing versions of the same package for different architectures (i686 and x86_64) Particularly, the libselinux package has an issue. What this error means is that you attempted to install libselinux-2.0.94-5.3.el6.i686 but you have 2.0.94-5.3.el6_4.1.x86_64 already installed (or the other way around, I forget) If you're using the install media as a repo on an updated system, that would explain this. The el6_4 dist tag indicates an async errata (i.e. released between major RHEL releases) for RHEL6.4, while the .el6 is what gets shipped on install media (overly simplifying things here, you could have prior releases async errata, for example el6_3 in a minor release if there were no other changes) for a minor release. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Announce: puppetdbquery 1.2.0
I've written a event query tool which is in master branch in git at the moment. It requires the gem chronic and supports stuff like: puppet query events --since='2 days ago' --status=success 'class[apache]' There's unfortunately no way to omit the node query yet and just show all events. Will try to add that. Also, you can't filter for events matching stuff like resource name, property name, old value, new value etc. But hope it proves useful for you anyway. On 7 June 2013 21:15, Erik Dalén wrote: > I have worked a bit on a event query tool, it is not ready for release > yet. But hopefully it will be soon :) > > It is tricky to combine it into a single query though as the report and > event API don't support subqueries yet. > > > On 7 June 2013 19:10, hai wu wrote: > >> Erik, >> >> I am wondering when you are going to add some support for current >> puppetdb report API .. >> >> Thanks, >> Hai >> >> On Fri, Jun 7, 2013 at 11:13 AM, Erik Dalén >> wrote: >> >>> I've released version 1.2.0 of puppetdbquery. >>> >>> New for this release is auto capitalization of resource type names and >>> class names. So now the queries 'class[apache]' and 'Class[Apache]' will be >>> equivalent. Should make it a bit more forgiving and easy to use. The >>> capitalization on the resource title only happens if the resource type is >>> class, so not on stuff like 'File["/etc/passwd"]'. >>> >>> It also includes a fix to make it run better under certain ruby 1.8.7 >>> versions. >>> >>> http://forge.puppetlabs.com/dalen/puppetdbquery/1.2.0 >>> >>> -- >>> Erik Dalén >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Puppet Users" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to puppet-users+unsubscr...@googlegroups.com. >>> To post to this group, send email to puppet-users@googlegroups.com. >>> Visit this group at http://groups.google.com/group/puppet-users?hl=en. >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >>> >>> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Puppet Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to puppet-users+unsubscr...@googlegroups.com. >> To post to this group, send email to puppet-users@googlegroups.com. >> Visit this group at http://groups.google.com/group/puppet-users?hl=en. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > > > > -- > Erik Dalén > -- Erik Dalén -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Issue installing on RHEL 6 (2.6.32-358.2.1.el6.x86_64)
It seems that there is a possible problem with your repo configuration. That is, it is attempting to install a 32 bit version of the binary package, even you are probably running a 64 bit version of RHEL. I suspect you probably will encounter this problem as well with other packages. If you are not using Satellite, you probably need to review you repo configuration and ensure that it is pointing to a ISO, CD or repo with the correct 64 bit binary packages. In other words, the issue is not specifically puppet, but with RHEL. On Jun 7, 2013, at 3:45 PM, Kenneth Edgar wrote: > After installing the puppet labs repo, I try running 'yum install -y > puppet-server and recieve: > > Error: Multilib version problems found. This often means that the root >cause is something else and multilib version checking is just >pointing out that there is a problem. Eg.: > > 1. You have an upgrade for libselinux which is missing some > dependency that another package requires. Yum is trying to > solve this by installing an older version of libselinux of the > different architecture. If you exclude the bad architecture > yum will tell you what the root cause is (which package > requires what). You can try redoing the upgrade with > --exclude libselinux.otherarch ... this should give you an error > message showing the root cause of the problem. > > 2. You have multiple architectures of libselinux installed, but > yum can only see an upgrade for one of those arcitectures. > If you don't want/need both architectures anymore then you > can remove the one with the missing update and everything > will work. > > 3. You have duplicate versions of libselinux installed already. > You can use "yum check" to get yum show these errors. > >...you can also use --setopt=protected_multilib=false to remove >this checking, however this is almost never the correct thing to >do as something else is very likely to go wrong (often causing >much more problems). > >Protected multilib versions: libselinux-2.0.94-5.3.el6.i686 != > libselinux-2.0.94-5.3.el6_4.1.x86_64 > You could try using --skip-broken to work around the problem > You could try running: rpm -Va --nofiles --nodigest > > Have any of you run into this, and do you have any suggestions? I'd prefer > this method of install if possible. > > Thank you, > Ken Edgar > Unix Sysadmin, School Specialty, Inc. > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-users+unsubscr...@googlegroups.com. > To post to this group, send email to puppet-users@googlegroups.com. > Visit this group at http://groups.google.com/group/puppet-users?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Hiera YAML False bug
This but only applied to the hiera data bindings afaik, not to hiera
function calls.
On 6 June 2013 03:41, Ti Leggett wrote:
> Hm, that bug says it was a duplicate of 17474 and 17474 was revolved in
> 3.2.0-rc1. Do I have a variant of the bug that's still residual?
>
>
> On Jun 5, 2013, at 7:12 PM, Dan White wrote:
>
> > http://projects.puppetlabs.com/issues/17105
> > Hiera booleans are broken -- explicit false value registers as lookup
> failure
> >
> > On Jun 5, 2013, at 4:52 PM, Ti Leggett wrote:
> >
> >> It seems puppet thinks that variables evaluate to true even when they
> are explicitly set to false in hiera YAML.
> >>
> >> In my searching it seems like this should be fixed but with hiera 1.2.1
> and puppet 3.2.1 I'm still seeing this.
> >>
> >> In my YAML I have:
> >>
> >> # Java directives
> >> java :
> >> enable_jdk : false # Install the JDK as well as the JRE
> >> enable_v6 : true # Install Java 6
> >> enable_v7 : false # Install Java 7
> >> openjdk: true # Install OpenJDK
> >> sun: false # Install Sun
> >>
> >>
> >> And in one of my manifests I do something like:
> >>
> >> class java::install (
> >> $parameters = hiera('java', []),
> >> ) {
> >> if $parameters['openjdk'] == true {
> >> if $parameters['enable_v6'] == true and
> $java::params::openjdk_6_jre {
> >> package { $java::params::openjdk_6_jre:
> >> ensure => latest,
> >> }
> >> if $parameters['enable_jdk'] == true and
> $java::params::openjdk_6_jdk {
> >> package { $java::params::openjdk_6_jdk:
> >> ensure => latest,
> >> }
> >> }
> >> }
> >> …
> >>
> >> No matter what it thinks it should install the JDK package even though
> the parameter is set to false. I've tried setting it 0, False, n, and N and
> it always evaluates to true. Is this a known bug and if so is there a
> workaround?
> >>
> >> --
> >> You received this message because you are subscribed to the Google
> Groups "Puppet Users" group.
> >> To unsubscribe from this group and stop receiving emails from it, send
> an email to puppet-users+unsubscr...@googlegroups.com.
> >> To post to this group, send email to puppet-users@googlegroups.com.
> >> Visit this group at http://groups.google.com/group/puppet-users?hl=en.
> >> For more options, visit https://groups.google.com/groups/opt_out.
> >>
> >>
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups "Puppet Users" group.
> > To unsubscribe from this group and stop receiving emails from it, send
> an email to puppet-users+unsubscr...@googlegroups.com.
> > To post to this group, send email to puppet-users@googlegroups.com.
> > Visit this group at http://groups.google.com/group/puppet-users?hl=en.
> > For more options, visit https://groups.google.com/groups/opt_out.
> >
> >
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-users+unsubscr...@googlegroups.com.
> To post to this group, send email to puppet-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/puppet-users?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>
--
Erik Dalén
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
