Matthaus Litteken | 2 Jun 00:44 2012

[Puppet Users] Announce: Puppet 2.7.15rc4 Available

Puppet 2.7.15rc4 is a maintenance release candidate for Puppet in the
2.7.x series.

Downloads are available at:
 * Source https://downloads.puppetlabs.com/puppet/puppet-2.7.15rc4.tar.gz

Windows package is available at
https://downloads.puppetlabs.com/windows/puppet-2.7.15rc4.msi

RPMs are available at https://yum.puppetlabs.com/el or /fedora

Debs are available at  https://apt.puppetlabs.com

Mac package is available at
https://downloads.puppetlabs.com/mac/puppet-2.7.15rc4.dmg

See the Verifying Puppet Download section at:
https://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet

Please report feedback via the Puppet Labs Redmine site, using an
affected puppet version of 2.7.15rc4:
http://projects.puppetlabs.com/projects/puppet/

## Puppet 2.7.15rc4 Release Notes ##

(#14761) Add boot, reboot to excludes list for redhat provider

    On sles, the reboot init script would be triggered during a `puppet resource
    service` call, which would ignore the status argument and proceed
to reboot the
(Continue reading)

Michael Stanhke | 2 Jun 01:13 2012

Re: Unable to Install puppet Master


On May 16, 3:23 am, Jeeva <kissan... <at> gmail.com> wrote:
> Hi,
>
>  I was trying to instal puppet-enterprise-2.5.1-el-5-x86_64 in centos6
> machine. But got below error.
>
> ## Installing packages from files...
> error: Failed dependencies:
>         java >= 1.5.0 is needed by pe-
> tanukiwrapper-3.5.9-5.pe.el5.x86_64

How do you have java installed?  The PE installer normally tries to
pull it in via yum (java-1.6.0-openjdk).  If you have java installed
from another method (sun/oracle java, or even something else) you may
need to do something differently.  Which java do you actually have?
>
> =========================================================================== =====
>
> !! ERROR: Could not install packages from files; see messages above
> for cause.
>
> 1. Then I checked my java version which is > what is required.
>     java -version
> java version "1.6.0_29"
> Java(TM) SE Runtime Environment (build 1.6.0_29-b11)
> Java HotSpot(TM) 64-Bit Server VM (build 20.4-b02, mixed mode)
>
> 2. I'm trying to install puppet master, console and puppet agent in
> same machine as i want to test it before I move it to prod.
(Continue reading)

Matthaus Litteken | 2 Jun 01:25 2012

[Puppet Users] Announce: Puppet 3.0.0rc3 Available

Puppet 3.0.0rc3 is a feature release candidate for the 3.x series of Puppet.

Puppet 3.0.0 has breaking changes from the Puppet 2.7 series and has new
dependencies of Facter version 2.0.0 or greater, and Hiera (and the
hiera puppet functions) version 1.0.0 or greater.

Downloads are available at:
 * Source http://downloads.puppetlabs.com/puppet/puppet-3.0.0rc3.tar.gz

RPMs are available at http://yum.puppetlabs.com

Debs are available at http://apt.puppetlabs.com

Mac packages are available at
http://downloads.puppetlabs.com/mac/puppet-3.0.0rc3.dmg

Windows packages are available at
http://downloads.puppetlabs.com/windows/puppet-3.0.0rc3.msi

See the Verifying Puppet Download section at:
http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet

Please report feedback via the Puppet Labs Redmine site, using an
affected puppet version of 3.0.0rc3:
http://projects.puppetlabs.com/projects/puppet/

## Puppet 3.0.0rc3 Release Notes ##
(#14761) Add boot, reboot to excludes list for redhat provider

    On sles, the reboot init script would be triggered during a `puppet resource
(Continue reading)

Jos Houtman | 4 Jun 16:50 2012
Picon

[Puppet Users] Re: Announce: Hiera-Puppet 1.0.0rc1 Available

Hello,


I am trying to install the hiera(-puppet) 1.0 rc's but I am having trouble installing from source. 
The goal is a 3.0 puppet installation with hiera. 

The rake file seems to be broken because it fails on the require on the 3rd line. 
What am i missing?

Jos

On Wednesday, May 23, 2012 1:39:17 AM UTC+2, Matthaus Litteken wrote:
Hiera-Puppet 1.0.0rc1 is a feature release candidate designed to
accompany Puppet 3.0 and Hiera 1.0.

It includes Puppet functions for hiera and also the puppet backend for
hiera lookups.

Downloads are available:
 * Source http://downloads.puppetlabs.com/hiera/hiera-puppet-1.0.0rc1.tar.gz
 * Apt and yum development repositories
 * Apple package http://puppetlabs.com/downloads/mac/hiera-puppet-1.0.0rc1.dmg

It includes contributions from the following people:
Gary Larizza, Hunter Haugen, Kelsey Hightower, Ken Barber, Matthaus
Litteken, and Nan Liu

See the Verifying Puppet Download section at:
 http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet#Verifying+Puppet+Downloads

Please report feedback via the Puppet Labs Redmine site, using an
affected version of 1.0.0rc1:
 http://projects.puppetlabs.com/projects/hiera-puppet

Hiera-Puppet 1.0.0rc1 Changelog
===
Gary Larizza (2):
      894a7a4 Fail if a lookup key isn't passed
      927de1f Add test coverage for hiera_hash()

Hunter Haugen (1):
      632457e Rubygems is not required to use hiera

Kelsey Hightower (2):
      48bfccb (#14461) Remove Puppet parser functions
      a042de4 Revert "(#14461) Remove Puppet parser functions"

Ken Barber (1):
      2df319a (#14124) Load rake tasks directly to fix tests for Ruby 1.9.x

Matthaus Litteken (6):
      cb721c5 Add mac packaging to hiera-puppet
      64b7375 Move conf to ext directory
      4101d02 Add debian packaging for hiera-puppet
      470c5c8 Add Redhat packaging to hiera-puppet
      5adc454 Add package task to tasks
      1138e65 Updating CHANGELOG for hiera-puppet 1.0.0rc1

Nan Liu (1):
      eb800e4 (#12037) hiera-puppet should support hash values.

--
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/-/DDBTSk12aE0J.
To post to this group, send email to puppet-users <at> googlegroups.com.
To unsubscribe from this group, send email to puppet-users+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Matthaus Litteken | 4 Jun 19:25 2012

Re: [Puppet Users] Re: Announce: Hiera-Puppet 1.0.0rc1 Available

Line 3 of hiera's rakefile is require 'rspec/core/rake_task'. Rspec
can be installed via packages or gems, but you shouldn't need to use
the rake tasks to install from source.

To use hiera or hiera-puppet from source, just add hiera/lib and/or
hiera-puppet/lib to your RUBYLIB. So, for example, if you have hiera
in /usr/local/hiera you could call `export
RUBYLIB=/usr/local/hiera/lib:${RUBYLIB}` to add hiera's libdir to your
rubylib.

HTH,
-matthaus

On Mon, Jun 4, 2012 at 7:50 AM, Jos Houtman <jos <at> hyves.nl> wrote:
> Hello,
>
> I am trying to install the hiera(-puppet) 1.0 rc's but I am having trouble
> installing from source.
> The goal is a 3.0 puppet installation with hiera.
>
> The rake file seems to be broken because it fails on the require on the 3rd
> line.
> What am i missing?
>
> Jos
>
>
> On Wednesday, May 23, 2012 1:39:17 AM UTC+2, Matthaus Litteken wrote:
>>
>> Hiera-Puppet 1.0.0rc1 is a feature release candidate designed to
>> accompany Puppet 3.0 and Hiera 1.0.
>>
>> It includes Puppet functions for hiera and also the puppet backend for
>> hiera lookups.
>>
>> Downloads are available:
>>  * Source
>> http://downloads.puppetlabs.com/hiera/hiera-puppet-1.0.0rc1.tar.gz
>>  * Apt and yum development repositories
>>  * Apple package
>> http://puppetlabs.com/downloads/mac/hiera-puppet-1.0.0rc1.dmg
>>
>> It includes contributions from the following people:
>> Gary Larizza, Hunter Haugen, Kelsey Hightower, Ken Barber, Matthaus
>> Litteken, and Nan Liu
>>
>> See the Verifying Puppet Download section at:
>>
>>  http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet#Verifying+Puppet+Downloads
>>
>> Please report feedback via the Puppet Labs Redmine site, using an
>> affected version of 1.0.0rc1:
>>  http://projects.puppetlabs.com/projects/hiera-puppet
>>
>> Hiera-Puppet 1.0.0rc1 Changelog
>> ===
>> Gary Larizza (2):
>>       894a7a4 Fail if a lookup key isn't passed
>>       927de1f Add test coverage for hiera_hash()
>>
>> Hunter Haugen (1):
>>       632457e Rubygems is not required to use hiera
>>
>> Kelsey Hightower (2):
>>       48bfccb (#14461) Remove Puppet parser functions
>>       a042de4 Revert "(#14461) Remove Puppet parser functions"
>>
>> Ken Barber (1):
>>       2df319a (#14124) Load rake tasks directly to fix tests for Ruby
>> 1.9.x
>>
>> Matthaus Litteken (6):
>>       cb721c5 Add mac packaging to hiera-puppet
>>       64b7375 Move conf to ext directory
>>       4101d02 Add debian packaging for hiera-puppet
>>       470c5c8 Add Redhat packaging to hiera-puppet
>>       5adc454 Add package task to tasks
>>       1138e65 Updating CHANGELOG for hiera-puppet 1.0.0rc1
>>
>> Nan Liu (1):
>>       eb800e4 (#12037) hiera-puppet should support hash values.
>
> --
> 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/-/DDBTSk12aE0J.
> To post to this group, send email to puppet-users <at> googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscribe <at> googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.

-- 
Matthaus Litteken
Release Manager, Puppet Labs

--

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

Matthaus Litteken | 4 Jun 20:31 2012

June RCs will be cut this Wednesday

We'll be cutting RCs for Puppet, Dashboard and Facter this Wednesday.
If you have tickets you've been working on, please try to get pull
requests in and merged as soon as reasonably possible for this
release.

-Matthaus

--

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

Picon

Re: [PATCH/puppet 1/1] (#4655) Allow stage to be set using a default class parameter

I really like this feature, is this patch already integrated into any Puppet release?

--
You received this message because you are subscribed to the Google Groups "Puppet Developers" group.
To view this discussion on the web visit https://groups.google.com/d/msg/puppet-dev/-/mJE49Q95s4IJ.
To post to this group, send email to puppet-dev <at> googlegroups.com.
To unsubscribe from this group, send email to puppet-dev+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
Nan Liu | 5 Jun 18:20 2012

Re: Re: [PATCH/puppet 1/1] (#4655) Allow stage to be set using a default class parameter

On Tue, Jun 5, 2012 at 8:38 AM, Cristian Măgherușan-Stanciu
<cristi.magherusan <at> gmail.com> wrote:
> I really like this feature, is this patch already integrated into any Puppet
> release?

It's available in 2.7.3. The changelog file in puppet usually contains
important patches and it's release version.

Thanks,

Nan

--

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

Moses Mendoza | 6 Jun 21:31 2012

Announce: Facter 1.6.10rc1 Available

Facter 1.6.10rc1 is a maintenance release candidate in the 1.6.x branch with bug fixes.

It includes contributions from Hailee Kenney, Josh Cooper, Jeff Weiss, Stefan Shulte, and Moses Mendoza.

This release is available for download at:
 https://downloads.puppetlabs.com/facter/facter-1.6.10rc1.tar.gz
 https://yum.puppetlabs.com

See the Verifying Puppet Download section at:
 http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet#Verifying+Puppet+Downloads

Please report feedback via the Puppet Labs Redmine site, using an
affected version of 1.6.10rc1:
 http://projects.puppetlabs.com/projects/facter/

Release Notes at: https://projects.puppetlabs.com/projects/facter/wiki/Wiki

Facter 1.6.10rc1 Highlights
======================
(#10261) Detect x64 architecture on Windows
    
    Previously, the hardwaremodel fact was using
    
        RbConfig::CONFIG['host_cpu']
    
    for Windows, but this returns i686 on a 64-bit OS, which is incorrect. And
    this caused the architecture fact to be reported as i386, which is also
    wrong.
    
    This commit updates the hardwaremodel fact on Windows to return the
    appropriate cpu model, e.g. x64, i686, etc. Based on that, the
    architecture fact will either be x86 or x64, and can be used to install
    architecture-specific packages, e.g. splunk-4.2.4-110225-x64-release.msi.

(#13678) Allow passing shell built-ins to exec method on windows
    
    The former exec method tried to run the command on windows no matter
    wether it could be found on the filesystem or not. This allowed end
    users to run shell-builtins with the exec method.
    
    The new exec method always tried to expand the binary first and returned
    nil if the binary was not found. This commit now restores the old
    behaviour on windows: Even if we fail to expand the command, we will try
    to run the command in the exact same way as it was passed to the exec
    method in case it is indeed a shell built-in. But we will now raise a
    deprecation warning.
    
    Reason for deprecating this "even if we cannot find it, just run it"
    behaviour: We may want to predetermine the paths where facter tries to find
    binaries in the future. A fall back behaviour may then lead to strange
    results. Most built-ins can be expressed in pure ruby anyways.

(#13678) Join PATHs correctly on windows
    
    On windows File.join joins with the File::SEPARATOR which is '/' on
    windows. While a lot of the windows API and the ruby filetests allow
    / as a separator we should use File::ALT_SEPARATOR ('\' on windows) to
    create pathnames on windows

Facter 1.6.10rc1 Changelog
===================
Josh Cooper (4)
    f42896d (#14764) Stub architecture fact when Windows facts run on Linux
    964d1f0 (#12864) Close registry key
    ab025bb Revert "Revert "(#12864) Windows: get primary DNS from registry""
    478386d (#10261) Detect x64 architecture on Windows

Hailee Kenney (1)
    b050eb1 (#14582) Fix noise in LSB facts

Jeff Weiss (1)
    f44ca52 (maint) Fix hardware model fact for ruby 1.9

Stefan Shulte (12)
    2043244 (#13678) Remove deprecation msg triggerd by the ipaddress6 fact
    d118d81 (#13678) Add filename extension on absolute paths on windows
    85654b0 (#13678) Allow passing shell built-ins to exec method on windows
    8f4c016 (#13678) Single quote paths on unix with spaces
    2d164e8 (#13678) Join PATHs correctly on windows
    e7e7e8f (#13678) Extend spec tests for expand_command
    0fea7b0 maint: Add shared context for specs to imitate windows or posix
    60d0cd2 (#13678) Fix spec failures on windows
    121a2ab (#13678) Fix quoting in expand_command
    55b1125 (#13678) Add more unit tests for new methods
    9086c0a (#13678) Add RDoc documentation for new methods
    165ace4 (#13678) Convert command to absolute paths before executing

Moses Mendoza(2)
    d6a3e91 Make package task depend on tar in Rakfile
    6cc881d Use git describe in Rakefile to determine pkg ver

--
You received this message because you are subscribed to the Google Groups "Puppet Developers" group.
To post to this group, send email to puppet-dev <at> googlegroups.com.
To unsubscribe from this group, send email to puppet-dev+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
Jeff McCune | 6 Jun 21:44 2012

What's the story about modules that need utility code?

Hi,

We're struggling a bit to come up with a good story around the
following scenario.

Imagine you're a relatively new-to-puppet and new-to-ruby person who
is writing a Puppet Module that contains ruby code.  A type and
provider, custom Facter fact, or new puppet subcommand using faces are
all good examples.

When you're in this situation and you find yourself in need of a place
to put some code you've written that will be used by multiple things,
what story should we tell about where to put it?  A concrete example
is a class you've written to display progress bars.  More than one
Puppet face action may need this class and you don't want to duplicate
code by copying the class into each action.

The proposal in #11419 [1] is to put utility code inside of the
Puppet::Modules namespace.  The reasoning is that when you're in this
situation your first intuition is probably to put it somewhere inside
of Puppet.  We don't have a place today, so if you look you might
decide to put your utility code in Puppet::Util.  Puppet already uses
this namespace quite a bit though, so the potential for conflicts and
monkey patching is high.

Daniel points out Puppet::Modules doesn't actually fix the problem,
two puppet modules may still declare Puppet::Modules::ProgressBar and
fight with each other.  The idea he has is to follow the Ruby
convention of putting it somewhere else in the global namespace.  My
concern here is that the story isn't very opinionated and it may not
be clear to a new person that a file path of lib/puppet shouldn't
really be declaring a namespace of ProgressBar at the top level.  By
ruby conventions this constant should live in lib/progress_bar.rb.

If you've read this far, could you provide any concrete examples of
utility code you've written, where you put it, and how you came to
decide to put it there?

No matter what we decide about #14149 we're going to clearly document
the story at http://docs.puppetlabs.com/  This email is mainly aimed
at trying to figure out what the story should be.

Any thoughts or comments would be greatly welcomed.

[1] http://projects.puppetlabs.com/issues/14149

Thanks,
-Jeff

--

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


Gmane