[Puppet Users] 30 days left before Puppet 2.7 end-of-life

2014-09-02 Thread Sam Kottler 
Greetings puppet-users,

Just wanted to send out a note to everyone to remind you all that Puppet
2.7 will reach end of life status on the 30th of September. This means
there will be no new releases on {yum,apt}.puppetlabs.com, via tarballs, or
on RubyGems.org. Although OS distributions will likely continue to support
2.7, it's highly recommended to upgrade to 3.x as soon as possible.

Let me know if you have any questions or concerns.

-s

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAPO4y0RBhiRm0MEYwajVY45W8ZKODkJNA3wSD3a-2%3DuFTL6PcQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Puppet 2.7.26 (security release for CVE-2014-3248) is now available

2014-06-10 Thread Sam Kottler 
Announce: Puppet 2.7.26 Available [ Security Release ]

Puppet 2.7.26 is a security fix release in the Puppet 2.7 series. This
release addresses CVE-2014-3248. It has no other bug fixes or new
features.

** CVE-2014-3248 **
Arbitrary Code Execution with Required Social Engineering
An attacker could convince an administrator to unknowingly create and
execute malicious code on platforms with Ruby 1.9.1 and earlier.
CVSSv2 Score: 5.9
Vector: AV:L/AC:M/Au:S/C:C/I:C/A:C/E:POC/RL:U/RC:C

Affected Puppet versions (ruby 1.9.1 and earlier only):
All

Fixed Puppet versions:
3.6.2
2.7.26

For more information on this vulnerability, please visit
https://puppetlabs.com/security/cve/cve-2014-3248

To report issues with the release, file a ticket in the "PUP" project
on http://tickets.puppetlabs.com/ and set the "Affects version/s"
field to "2.7.26"

Puppet 2.7.26 Downloads
--
Source: https://downloads.puppetlabs.com/puppet/puppet-2.7.26.tar.gz

Available in native package format in the Puppet Labs yum and apt
repositories:
http://yum.puppetlabs.com and http://apt.puppetlabs.com

Gems are available via rubygems at
https://rubygems.org/downloads/puppet-2.7.26.gem
  or by using `gem install puppet`

Please note that there are no longer DMG's or MSI's available for the
2.7 series. Users still on 2.7 using Puppet on OSX or Windows with the
aforementioned native packaging formats should upgrade to the 3.x
series as soon as possible.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAPO4y0T5vPiGLjtgJsfLw4No4qSTSnMrwhaZd0vr1cCyBBKaSA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Announce: Puppet 2.7.25 is available

2014-01-07 Thread Sam Kottler 
Released January 7, 2014.

2.7.25 is a bugfix release in the Puppet 2 series. Please note that this
release is supported by the community; Puppet Labs is not responsible for
maintaining the release. This release fixes:

Andrew Parker (1):
   233e80 (Maint) Add rake task for running specs on win

Dominic Cleal (1):
   3ea78c (PUP-1255) Fix assumed default file mode to 0644

Kylo Ginsberg (1):
   4e10a0 (PUP-1255) Don't use POSIX defaults on Windows

Sam Kottler (2):
   c2acac (PUP-1351) Load ext/packaging/packaging.rake instead of
ext/packaging/tasks/**
   b1b29a Bump the version to 2.7.25


Puppet 2.7.25 Downloads
--
Source: https://downloads.puppetlabs.com/puppet/puppet-2.7.25.tar.gz

Available in native package format in the Puppet Labs yum and apt
repositories:
http://yum.puppetlabs.com and http://apt.puppetlabs.com

Gems are available via rubygems at
https://rubygems.org/downloads/puppet-2.7.25.gem
  or by using `gem install puppet`

Please note that there are no longer DMG's or MSI's available for the 2.7
series. Users still on 2.7 using Puppet on OSX or Windows with the
aforementioned native packaging formats should upgrade to the 3.x series as
soon as possible.

Please report feedback via the Puppet Labs tickets site, using an
affected puppet version of 2.7.25:
https://tickets.puppetlabs.com/browse/PUP

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAPO4y0RyiAVqWHhunFiz5hLPrrJYYjD2rT24POAGOAvsVzq%3Dyw%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] dashed by dashboard

2014-01-07 Thread Sam Kottler 
On Mon, Jan 6, 2014 at 8:51 PM, Stuart Cracraft wrote:

> Okay, took care of that. Thanks.
>
> Now, when doing per page 170 in chapter 7 (chapter puppet consoles) in Pro
> Puppet
> by Krum et al, I have:
>
>  ruby /usr/share/foreman-installer/generate_answers.rb
>

We changed the installation process as part of a pretty large overhaul in
the Foreman installer that was released in 1.3.

You can see the up-to-date installation guide here:
http://theforeman.org/manuals/1.3/quickstart_guide.html


>
> but it does not have a file generate_answers.rb anywhere in the
> /usr/share/foreman-installer tree.
>
> Has anyone else encountered the above?
>
>
> On Monday, January 6, 2014 10:46:57 AM UTC-8, Jose Luis Ledesma wrote:
>
>> You hace to enable both epel and optional repositories.
>>
>> Regards,
>>
>  --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/d41f912e-2ed0-4efd-9354-a3f1d78c084c%40googlegroups.com
> .
>
> 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAPO4y0SGQBMxdGe5YwPnSy2ePcnhnqNsZx%2BvJWg3AUzutFCX2g%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Announce: Puppet 2.7.24 is available

2013-12-26 Thread Sam Kottler 
Released December 26, 2013.

2.7.24 is a security release in the Puppet 2 series. Please note that this
release is supported by the community; Puppet Labs is not responsible for
maintaining the release. This release fixes:

* CVE-2013-4969: Unsafe use of temp files in File type

See http://puppetlabs.com/security/cve/cve-2013-4969 for details.

Andrew Parker (1):
  691fbbe (#23343) Use `replace_file` to update a file's contents

Sam Kottler (1):
  22ecab2 Bump the version to 2.7.24


Puppet 2.7.24 Downloads
--
Source: https://downloads.puppetlabs.com/puppet/puppet-2.7.24.tar.gz

Available in native package format in the Puppet Labs yum and apt
repositories:
http://yum.puppetlabs.com and http://apt.puppetlabs.com

Gems are available via rubygems at
https://rubygems.org/downloads/puppet-2.7.24.gem
  or by using `gem install puppet`

Please note that there are no longer DMG's or MSI's available for the 2.7
series. Users still on 2.7 using Puppet on OSX or Windows with the
aforementioned native packaging formats should upgrade to the 3.x series as
soon as possible.

Please report feedback via the Puppet Labs tickets site, using an
affected puppet version of 2.7.24:
https://tickets.puppetlabs.com/browse/PUP

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAPO4y0Q-VF1VzQ%2BVwiVvG-OiX5LtpEkbQJE%3DM6QdRAdUsJ%2BFjA%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: End of Life Plan for Puppet 2.7.x

2013-08-21 Thread Sam Kottler 


Will Farrington, Andrew Parker, Mike Stahnke, and I just had a conversation at 
PuppetConf about the future of 2.7 and decided that Will and I will be 
maintaining and managing releases for the 2.7 branch. This means that Puppet 
Labs will be hosting 2.7 packages on the releases page and in package repos at 
least until September 30, 2014 when the Puppet Enterprise 2.x lifecycle ends.

Will and I will write the release notes for 2.7 and will likely setup a 
separate Jenkins instance to run integration and functional tests. We'd love 
some help on the QA side going forward so feel free to reach out if you're 
interested in getting involved.

One of the motivations behind this change is that the packages in EPEL and 
Debian wheezy rely (or will very soon) on a stable 2.7 branch due to the large 
number of breaking changes in 3.0+. This branch will serve as an upstream for 
those repos.


Let me know if you've got any questions.


-Sam


On Thursday, July 11, 2013 9:28:08 AM UTC-7, Michael Stanhke wrote:
>
> The time has come for us to say good-bye to the Puppet 2.7 series. 
> This means the security fixes, bug fixes, and features provided for 
> Puppet 2.7 since its release in June 2011 will cease on October 1, 
> 2013. 
>
> We strongly encourage users who have not already upgraded to move 
> forward to the Puppet 3 series, originally released on Sept 28, 2012. 
> This version is actively developed and maintained, with Puppet 3.2.2 
> released June 18 and 3.2.3 currently in a release candidate phase. To 
> support your upgrade, please make use of the following resources: 
>
> Puppet Labs Upgrade Guide: 
> http://docs.puppetlabs.com/guides/upgrading.html 
> Web: http://ask.puppetlabs.com 
> IRC:  #puppet 
> Mailing list: puppet...@googlegroups.com  
>
>
> Thanks, 
> Michael Stahnke 
> Engineering 
>

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Packages on fedora19

2013-07-05 Thread Sam Kottler 
Greetings,

I'm (along with Mike + a few others) one of the Fedora package maintainers
for Puppet & Facter. A number of people have reported good results with the
latest release of 3.1.1 in F19. Of course, PL's repos are ideal for the
latest version, but the vanilla version in Fedora proper will also work as
a stop-gap measure.

-Sam

On Thu, Jul 4, 2013 at 11:28 PM, Pete Brown  wrote:

> On 5 July 2013 02:43, Matthaus Owens  wrote:
> > Brian,
> > Yes, there have been some changes to ruby in fedora 19. We will
> > probably need to tweak the spec we build against before we will get a
> > clean build on f19. There are some details here:
> >
> http://fedoraproject.org/wiki/Features/Ruby_2.0.0#New_Packaging_Guidelines
> > and http://fedoraproject.org/wiki/Packaging:Ruby
>
> Yeah that's going to ram the proverbial spanner in the works.
>
> I am happy to run up a test vm here and help out if it's needed.
>
> >
> > On Wed, Jul 3, 2013 at 4:44 PM, Brian Pitts  wrote:
> >> I tried an installation earlier today and received this error:
> >>
> >> Resolving Dependencies
> >> --> Running transaction check
> >> ---> Package puppet.noarch 0:3.2.2-1.fc18 will be installed
> >> --> Processing Dependency: ruby(abi) >= 1.8 for package:
> >> puppet-3.2.2-1.fc18.noarch
> >> --> Processing Dependency: ruby-rgen for package:
> puppet-3.2.2-1.fc18.noarch
> >> --> Running transaction check
> >> ---> Package puppet.noarch 0:3.2.2-1.fc18 will be installed
> >> --> Processing Dependency: ruby(abi) >= 1.8 for package:
> >> puppet-3.2.2-1.fc18.noarch
> >> ---> Package ruby-rgen.noarch 0:0.6.5-1.fc18 will be installed
> >> --> Finished Dependency Resolution
> >> Error: Package: puppet-3.2.2-1.fc18.noarch (puppetlabs-products)
> >>Requires: ruby(abi) >= 1.8
> >>
> >> It looks like there's no package providing ruby(api).
> >>
> >> $ repoquery --whatprovides 'ruby(abi)'
> >> $ repoquery --provides ruby
> >> ruby = 2.0.0.247-11.fc19
> >> ruby(runtime_executable) = 2.0.0
> >> ruby(x86-32) = 2.0.0.247-11.fc19
> >> ruby = 2.0.0.247-11.fc19
> >> ruby(runtime_executable) = 2.0.0
> >> ruby(x86-64) = 2.0.0.247-11.fc19
> >> $ repoquery --provides ruby-libs
> >> libruby.so.2.0
> >> ruby(release) = 2.0.0
> >> ruby-libs = 2.0.0.247-11.fc19
> >> ruby-libs(x86-32) = 2.0.0.247-11.fc19
> >> libruby.so.2.0()(64bit)
> >> ruby(release) = 2.0.0
> >> ruby-libs = 2.0.0.247-11.fc19
> >> ruby-libs(x86-64) = 2.0.0.247-11.fc19
> >>
> >>
> >>
> >> On 07/03/2013 06:24 PM, Pete Brown wrote:
> >>>
> >>> I was just wondering the same thing.
> >>> My dev environment runs in Fedora 18 and I almost upgraded yesterday
> >>> but thought some testing was in order first.
> >>>
> >>> I am likely to do what I did last time and try installing the versions
> >>> from the previous release.
> >>> I will be running up a Fedora 19 vm and install puppet from the Fedora
> >>> 18 repo shortly and will let you know how it goes.
> >>>
> >>> If I can find srpms I may rebuild them and see how that goes. :)
> >>>
> >>> On 4 July 2013 06:04, Tony G.  wrote:
> 
>  Howdy!
> 
>  Probably this is being worked but just throwing it out there as f19 is
>  already out, I guess the package for it will be soon available on
>  http://yum.puppetlabs.com/fedora/ ?
> 
>  Thanks!
> 
>  --
>  Tony
>  http://tonyskapunk.net
> 
>  --
>  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.
>  For more options, visit https://groups.google.com/groups/opt_out.
> 
> 
> >>>
> >>
> >> --
> >> All the best,
> >> Brian Pitts
> >>
> >>
> >> --
> >> 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.
> >> For more options, visit https://groups.google.com/groups/opt_out.
> >>
> >>
> >
> >
> >
> > --
> > Matthaus Owens
> > Release Manager, Puppet Labs
> >
> > Join us at PuppetConf 2013, August 22-23 in San Francisco -
> > http://bit.ly/pupconf13
> > Register now and take advantage of the Early Bird discount - save 25%!
> >
> > --
> > 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/gro

Re: [Puppet Users] Puppet experience better in Fedora 17 or Fedora 18?

2013-02-28 Thread Sam Kottler 
Puppet 3.0.2 is in the updates-testing repository for Fedora 18.

On Thu, Feb 28, 2013 at 7:35 PM, Peter Brown  wrote:

> Actually scratch the comment about puppet having packages for Fedora 18.
> The repo exists but it seems to be empty for now.
> I guess they are still building it.
>
>
> On 1 March 2013 10:26, Peter Brown  wrote:
>
>> Fedora 18 is officially supported in the puppetlabs yum repos now.
>> Last I looked it wasn't (only a couple of days ago).
>> I have been running a couple of node on Fedora 18 for a while and there
>> is a few issues that occur but I think they still affect 17 as well.
>> Most of the issues I have seen relate to systemd especially when the
>> service still has an init script. There are bug reports relating to those
>> issues and they are still in progress.
>> I am getting tempted to offer my services to test those bugs...
>>
>> I can't comment on cobbler or the bug you are seeing.
>>
>> Good luck either way.
>>
>> Pete.
>>
>>
>> On 1 March 2013 07:38, thyrsus  wrote:
>>
>>> I've been struggling to get cobbler to bootstrap puppet in Fedora 17.
>>> Currently I'm suffering from puppet bug #9084, and I'm about to see if
>>> applying the changes from https://github.com/puppetlabs/puppet/pull/831get 
>>> me functional (I've already tried the symlink to ca.pem workaround, and
>>> it didn't get me there).  I'll find out this evening if that's already been
>>> applied to the fedora 17 package, in which case I'm stuck.
>>>
>>> Would I have a better experience if I skipped to Fedora 18, since it's
>>> using Puppet 3.0, or am I just trading in for a better class of "puzzles"?
>>>
>>> - Stephen
>>>
>>>  --
>>> 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.

Re: [Puppet Users] WebRick role

2013-01-07 Thread Sam Kottler 
Hi and welcome!

The puppet master itself is a simple rack application so webrick is the
default rack server. You can use any application server that is
Rack-compatible; Apache w/ Passenger is also a very common configuration.

There is not a web interface by default, but there are a number of tools
that provide a web UI for managing your Puppet infrastructure, like Foreman
[1] and Puppet Enterprise [2].

Hope that helps!

1. http://theforeman.org
2. http://puppetlabs.com/puppet/puppet-enterprise/

On Mon, Jan 7, 2013 at 5:45 AM, bernard.gran...@morpho.com <
bernard.gran...@morpho.com> wrote:

> Hy,
>
> I am just starting with Puppet, and install a test bed with community
> version, one master and 8 clients.
>
> I wonder if WebRick is used only of master-agents communication or
> does WebRick provides a web application usable by human with a web
> browser ?
>
> Thank's for any helps
>
> Bernard
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Re: trouble with catalog with Foreman as ENC

2012-09-04 Thread Sam Kottler 
That means that modules/connexity_apt/files/connexity.list doesn't exist.

-Sam

On Tue, Sep 4, 2012 at 2:01 PM, confused  wrote:

> Thank you, that was very helpful.
>
> Now I need to work through:
> err:
> /Stage[main]/Connexity_apt/File[/etc/apt/sources.list.d/connexity.list]:
> Could not evaluate: getaddrinfo: Name or service not known Could not
> retrieve file metadata for puppet://modules/connexity_apt/connexity.list:
> getaddrinfo: Name or service not known at
> /opt/puppet/modules/connexity_apt/manifests/init.pp:6
>
> Or this:
> err:
> /Stage[main]/Connexity_apt/File[/etc/apt/sources.list.d/connexity.list]:
> Could not evaluate: Error 400 on SERVER: Not authorized to call find on
> /file_metadata/puppet/modules/connexity_apt/etc/apt/sources.list.d/connexity.list
> Could not retrieve file metadata for
> puppet:///puppet/modules/connexity_apt/etc/apt/sources.list.d/connexity.list:
> Error 400 on SERVER: Not authorized to call find on
> /file_metadata/puppet/modules/connexity_apt/etc/apt/sources.list.d/connexity.list
> at /opt/puppet/modules/connexity_apt/manifests/init.pp:6
>
> I'm sure that I'm missing something simple here again, apparently I'm on
> the steep part of the learning curve.
>
>
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/puppet-users/-/ptkwXpwGGvYJ.
>
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Re: newish puppet on RHEL4 and/or SLES9?

2012-08-29 Thread Sam Kottler 
Thanks!

-Sam

On Wed, Aug 29, 2012 at 7:10 PM, James Turnbull wrote:

> Sam Kottler wrote:
> > Who's got the ban hammer? :P
> >
>
> The address appears to be now banned. Apologies for the spam.
>
> Regards
>
> James
>
>
> --
> James Turnbull
> Puppet Labs
> 1-503-734-8571
> To schedule a meeting with me: http://tungle.me/jamtur01
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Re: newish puppet on RHEL4 and/or SLES9?

2012-08-29 Thread Sam Kottler 
Who's got the ban hammer? :P

On Wed, Aug 29, 2012 at 3:44 PM, shell Nor  wrote:

> My puppet has been created in isolation on an island at top of scotland
> over a period of 2 weeks nonstop working on her mismatched outfit.  sure
> youve probwho hsn't .  Flattery will get u know where..no.Know
> we're he're..wh'at i'd on't knowdumf...
>dumf
> humfrey'yes  m'lady.why do I love you so'.HumPhrey...
>YesM'lady.
>
> remember w is an upside down vivisection h is r 1 leaning again
> movemenf ..espanyolrythme and movemenf...
>what ya gonna do about the below  bell .ow...!!  stay team
> ent   you wrote it its your
> scrip.crypt.whose hose hh .Mortgage coming to a show
> home near lend an ear...Job coming to a show you how Billed
>  the perfect invoice guaranteed to be presentable  F9,
>  Puppet, the honor you dont want to be without...Michele xX
>
>
> On Wednesday, August 15, 2012 3:41:32 PM UTC+1, Jason Antman wrote:
>>
>> I'm in the process of building out a new puppet master and pulling our
>> existing/legacy infrastructure into Puppet control for the basic
>> system-level stuff (mail, syslog, sudo, ssh, etc.). Unfortunately, the
>> directive from on high is that all of our hosts need to be managed by
>> the same system. That list is about 95% RHEL/Cent 5 or 6, but there's a
>> few RHEL4 and SLES9 machines on the "must have" list. As upgrades are
>> very unlikely, I'd like to be on the newest version possible - ideally,
>> 2.7.12+ on the master so I can leverage puppetDB.
>>
>> Is anyone out there running new-ish puppet (2.7, or else 2.6) on such
>> ancient beasts? If so, can anyone point me at sources for the packages,
>> and dependencies? Or perhaps have spec files to share?
>>
>> I'd like to say I can spend the time to build and test puppet and all
>> the dependencies, but alas, that is very far from the case.
>>
>> Thanks for any assistance,
>> Jason
>>
>> PS - If you happen to be a competent generalist Linux admin in the
>> Boston, MA or Atlanta, GA area, feel free pass along your resume...
>>
>  --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/puppet-users/-/0DM356VV6JYJ.
>
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Re: Attending PuppetConf?

2012-08-24 Thread Sam Kottler 
Sorry, this was supposed to go to the Foreman list. My apologies.

-Sam

On Fri, Aug 24, 2012 at 5:56 PM, Sam Kottler wrote:

> Hi all,
>
> There has been talk of a Foreman meetup at PuppetConf. I think it's a
> great idea for all of us to talk about what we're doing with Foreman and to
> meet in person.
>
> How many of you are going to PuppetConf and would like a meetup? Also,
> thoughts on a meetup vs. a BoF at the conference itself (or maybe both...)?
>
> -S
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Attending PuppetConf?

2012-08-24 Thread Sam Kottler 
Hi all,

There has been talk of a Foreman meetup at PuppetConf. I think it's a great
idea for all of us to talk about what we're doing with Foreman and to meet
in person.

How many of you are going to PuppetConf and would like a meetup? Also,
thoughts on a meetup vs. a BoF at the conference itself (or maybe both...)?

-S

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Re: Error 400 on SERVER: Could not autoload active_record: uninitialized constant ActiveRecord

2012-08-21 Thread Sam Kottler 
Storeconfigs use activerecord as an ORM.

-Sama

On Tue, Aug 21, 2012 at 7:30 AM, NewpTone  wrote:

>
> Thx,this really helps me ,but I wonder why  storeconfig setting will
> cause the error ?
> 在 2011年12月22日星期四UTC+8上午3时53分55秒，Joehillen写道：
>>
>> Ok, I solved the issue.
>>
>> It took some doing because apparently puppet doesn't work with the newest
>> version of activerecord.
>>
>> http://projects.puppetlabs.**com/issues/867
>>
>> Here are the steps that ended up working:
>>
>> apt-get install rubygems
>> gem install activerecord --version 3.0.11
>> apt-get install libmysqlclient15-dev
>> gem install mysql
>>
>> I had to disable async_storeconfig because stomp gave an error and I had
>> never used it before:
>>
>> err: Could not retrieve catalog from remote server: Error 400 on SERVER:
>> Could not write * to queue: undefined method `publish' for
>> #
>> Instance::#
>> client : #
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/puppet-users/-/zmMWfOpsodcJ.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] puppet client environment is being ignored from foreman settings

2012-08-16 Thread Sam Kottler 
Yaniv,

I was asking if you happen to have an environment defined on your agent in
puppet.conf. Anyhow, we can handle this over on foreman-users :)

-Sam

On Thu, Aug 16, 2012 at 1:01 PM, Yaniv Fine  wrote:

> Why do i have to define environment in puppet.conf on the agent . Isnt
> defining the host in a group on foreman good enugh ? .in general there
> could be a conflict . Btw when i configure env in puppet.conf it does work
> like expected but it ignored the setting related to env .in foreman
> On Aug 16, 2012 7:19 PM, "Sam Kottler"  wrote:
>
>> Hi Yaniv,
>>
>> Do you have the environment defined in puppet.conf on the agent and use
>> Foreman as an ENC? If so, you're probably seeing
>> http://projects.puppetlabs.com/issues/3910.
>>
>> Some users are getting around this bug by adding functionality to the ENC
>> script that validates the environment defined in Foreman against the one in
>> the host's puppet.conf. Someone who has done this might be able to help you
>> on the foreman-users list.
>>
>> -Sam
>>
>> On Thu, Aug 16, 2012 at 11:05 AM, Yaniv Fine  wrote:
>>
>>> Hi experts .
>>> i am runnig foreman 1
>>> puppetmaster 2.7.18
>>> i have setup a test client machine .
>>> on foreman i have configured the new client to be part of the
>>> development environment .
>>> on the client i have setup that it will run the following from site.pp
>>> to debug information .
>>> notify { "environment":
>>> message => $environment
>>>
>>>
>>> when i run on the client .
>>> puppet agent--test --debug --verbose
>>>
>>> i get "Notify[environment]/message: defined 'message' as 'production'"
>>> allthought on foreman this client is setup as "development"
>>> when i add the
>>> environment  = development on the client /etc/puppet.puppet.conf
>>> the client get "Notify[environment]/message: defined 'message' as
>>> 'development'"   which is ok .
>>>
>>> BTW in foreman => settings
>>> i have default_puppet_environment = testing
>>> which is beeing ignored via the client .
>>>
>>>
>>> is this normal that i need to override the foreman client setting . with
>>> a "environment  = development on the client /etc/puppet.puppet.conf "
>>> 
>>>
>>>
>>> thank you
>>>
>>>  --
>>> You received this message because you are subscribed to the Google
>>> Groups "Puppet Users" group.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msg/puppet-users/-/JF3PZ63IdjAJ.
>>> To post to this group, send email to puppet-users@googlegroups.com.
>>> To unsubscribe from this group, send email to
>>> puppet-users+unsubscr...@googlegroups.com.
>>> For more options, visit this group at
>>> http://groups.google.com/group/puppet-users?hl=en.
>>>
>>
>>  --
>> You received this message because you are subscribed to the Google Groups
>> "Puppet Users" group.
>> To post to this group, send email to puppet-users@googlegroups.com.
>> To unsubscribe from this group, send email to
>> puppet-users+unsubscr...@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/puppet-users?hl=en.
>>
>  --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] puppet client environment is being ignored from foreman settings

2012-08-16 Thread Sam Kottler 
Hi Yaniv,

Do you have the environment defined in puppet.conf on the agent and use
Foreman as an ENC? If so, you're probably seeing
http://projects.puppetlabs.com/issues/3910.

Some users are getting around this bug by adding functionality to the ENC
script that validates the environment defined in Foreman against the one in
the host's puppet.conf. Someone who has done this might be able to help you
on the foreman-users list.

-Sam

On Thu, Aug 16, 2012 at 11:05 AM, Yaniv Fine  wrote:

> Hi experts .
> i am runnig foreman 1
> puppetmaster 2.7.18
> i have setup a test client machine .
> on foreman i have configured the new client to be part of the development
> environment .
> on the client i have setup that it will run the following from site.pp to
> debug information .
> notify { "environment":
> message => $environment
>
>
> when i run on the client .
> puppet agent--test --debug --verbose
>
> i get "Notify[environment]/message: defined 'message' as 'production'"
> allthought on foreman this client is setup as "development"
> when i add the
> environment  = development on the client /etc/puppet.puppet.conf
> the client get "Notify[environment]/message: defined 'message' as
> 'development'"   which is ok .
>
> BTW in foreman => settings
> i have default_puppet_environment = testing
> which is beeing ignored via the client .
>
>
> is this normal that i need to override the foreman client setting . with a
> "environment  = development on the client /etc/puppet.puppet.conf "
> 
>
>
> thank you
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/puppet-users/-/JF3PZ63IdjAJ.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.