Apologies for the late summary, this summarizes last week's activity.

This is my first time posting, so I apologize if someone else has posted this before, I didn't see anything.

I installed puppet-server-3.2.1-1.el6.noarch from the x86_64 puppetlabs-release-6-7.noarch repo.  I had issues stopping and restarting via the init script and did a little digging.  I found that the master's pid file is now in /var/lib/puppet/run/ rather than /var/run/puppet/, however this change was not updated for the stop procedures in the init script.

The pidfile variable should look like: "pidfile=/var/lib/puppet/run/master.pid"

This also appears to be an issue with the puppet agent init script.

Thank you,

Ken Edgar

Hi has anyone heard of anybody with experience of deploying alfresco using puppet? We need a developer with this experience.

 

Thanks

Puppet Labs Devs,

It's super effective!

Thanks,

Trevor

Puppet manifests today don't specify the version of DSL they are writing to, afaik. This will likely lead to the classic versioning problem. Imagine a new language construct gets added and not all Puppet versions can support this language construct. Without having a way to know the DSL version of a Puppet manifest, this mismatch can only be detected at runtime in an adhoc manner.

Thoughts? I'm mainly interested in someone validating the existence of this problem to help me assure I'm not missing anything.

Thanks Rags

Puppet Dev Community Summary

• Finished Card Total: 31 vs 27 last week
• Merged: 20 vs 16 last week
• Not Merged: 6 vs 6 last week
• Other: 5 vs 5 last week

Please see the team's current work in progress, outstanding pull requests, and backlog on the Puppet Dev Community board.

Merged

(PR facter/454) (maint) Extract heredoc fixtures from memory spec [Adrien Thebo]

Merged into master in 99e494d

(PR puppet/1695) clean up docs for new parser functions [Dustin J. Mitchell]

No comment found with summary:

(PR puppet/1663) (#20787) Do not generate NetBIOS name service requests [Josh Cooper]

merged into stable in 25303fa; this should be released in 3.2.2.

(PR facter/443) (maint) Remove duplication from selinux facts [Brian Cain]

merged into master in 9d8d201. This should be released in Facter 2.0.0. Thanks for the contribution!

(PR facter/445) (#20938) Ignore stderr from domain commands [Andrew Parker]

merged into stable in fc6a207; this should be released in 1.7.2.

(PR facter/444) (maint) Remove duplication from virtual fact [Andrew Roetker]

merged into master in fda0bdd; this should be released in 2.0.0. Thanks for the contribution!

(PR puppetlabs-stdlib/56) add a "step" argument to range()

merged into master in 928c131; this should be released in the next major or minor release of puppetlabs-stdlib. Thanks again for the contribution!

(PR puppet/1671) (Maint) Remove unused variables [Erik Dalén]

merged this awesome into master in fd4f17e. This should be released in 3.3.0. Thanks!

(PR puppet/1668) Feature #20916: This patch extends the zypper package provider with the install_options ... [Michele Catalano]

merged into master in 7c7e9a5; this should be released in 3.3.0. For the record I modified the commit message to conform to the git commit message standard with a 50 character first line and detailed body. Thanks again for the contribution!

(PR puppet/1351) (#17827) Properly format SMTP HELO when sending tagmail

merged into master in 8dbe436; this should be released in 3.3.0. There was a syntax incompatibility with ruby 1.8.7, so I rebased this on master and made the syntax amendment. Thanks for the contribution!

(PR puppet/1672) (Maint) Simplify search for init scripts [Erik Dalén]

merged into master in ccf626f; this should be released in 3.3.0. Thanks for the contribution!

(PR puppet/1673) Set HOME environment for eix/portage provider [Alexey Lapitsky]

merged into master in 7f3add7; this should be released in 3.3.0. Thanks for the contribution!

(PR puppet/1674) Docs: Improve documentation of "duration" settings [nfagerlund]

merged into stable in 54845c5 and merged up to master in a6d1be3. This should be released in 3.2.2 and 3.3.0. Thanks!

(PR puppet/1675) Docs: Fix a persistent formatting glitch in the file type's ensure parameter docs [nfagerlund]

merged into stable in 7ecb4b8 and merged up into master in ad85de4. This should be released in 3.2.2 and 3.3.0. Thanks!

(PR puppet/1677) Update specs for Windows on Ruby 1.9 [Josh Cooper]

merged into stable in a2217a9 and merged up into master in 4c84d8e. This should be released in 3.2.2 and 3.3.0. Thanks!

(PR puppet/1669) (#20920) Include file and line number on invalid resource relationship [Erik Dalén]

merged into master as 9f51185; this should be released in 3.3.0. I refactored the specs in 492b833 to make sure that the exception being raised had the actual file and line context if it was available. Thanks again for the contribution!

(PR puppet/1679) (maint) Pidlock#file_path uses correct instance var [Josh Partlow]

merged into master in 4cce551; this should be released in 3.3.0. Thanks for chasing this down, I ran into this myself and couldn't figure this out for the life of me.

(PR puppet/1682) (#20967) Apply Redhat carried patch for rundir permissions [Andrew Parker]

merged into master in a6e746d; this should be released in 3.3.0. Thanks!

(PR puppet/1687) (maint) remove fact stringifying deprecation warning [Adrien Thebo]

merged into master as 605003f, the deprecation warning when facts are munged into strings is no longer issued.

(PR facter/448) (#20994) Fix memorysize and memoryfree facts on AIX [Aran]

merged into master in 0b488c2; this should be released in 2.0.0. Thanks for the contribution!

Not Merged

(PR puppetlabs-stdlib/151) Add dirname_rec function [Raphaël Pinson]

closed without merge. This change has a lot of value but there are a lot of really good questions about how this should behave, what the default behaviors should be, how many precautions should be put in place, et cetera. It seems that as it is, this PR is a bit too controversial to be merged in.

(PR puppet/1684) 20997 pmt handle forge warnings [Adrien Thebo]

this fix was an incomplete fix for a bigger problem, closed without merge.

(PR facter/442) [#20860] Add a fact for the current Puppet parser [Will Farrington]

closed without merge; this will only work as expected with puppet apply. A more complete implementation would probably have to add this information at aroundhttps://github.com/puppetlabs/puppet/blob/master/lib/puppet/indirector/catalog/compiler.rb#L145 , which should work correctly for all use cases.

(PR puppet/1666) (#20897) Added lines to handle UTF_8 systems at startup [Bob Maerten]

closed without merge; this change could have unintended side effects, and uses a very big hammer to solve this problem.

(PR facter/447) (maint) Remove memory fact duplication [Nate Wolfe]

I'm not convinced that this adds much value to the code base. It gains compactness at the expense of clarity, and since we can fit the entire source of Facter on a floppy disk I don't think it's worth the trade off.

(PR puppet/1686) (#12361) Remove masterlog option [Charlie Sharpsteen]

merged and then reverted; removing this option would introduce a backward incompatible change.

Other

Reproduce puppetlabs-razor provider => git 3.2.1 bug

An issue was reported in #puppet on Freenode about a possible regression in Puppet 3.2.1 with declaring a specific provider for a resource. I wasn't able to duplicate with puppet 3.2.1 and the version of puppetlabs/razor from the Forge.

Release puppetlabs/java_ks 1.1.0

released puppetlabs/java_ks (http://forge.puppetlabs.com/puppetlabs/java_ks/1.1.0)

Publish snippets

I've stolen Jeff's snippets and stuffed everything in https://github.com/adrienthebo/community-dev-snippets for use with Autokey.

Windows acceptance tests for Facter

We don't have the bandwidth for this, nor is there much demand. Considering this rejected.

Windows acceptance tests for Hiera

We don't have the bandwidth for this, nor is there much demand. Considering this rejected.

Last updated: 2013-06-11 13:56:20 -0700

--

curl -H "Accept: application/json"  http://puppetdb.domain/v2/nodes

I suppose it's too late to implement this so the client would do:

curl -H "Accept: application/json;version=2.0"  http://puppetdb.domain/api/nodes

I don't want to have to update puppetdb endpoints registered across various systems every time the API is versioned.

Mike Hancock

Last week was consumed by trying to dig into, understand, and fix a failure that we got in our Jenkins environment from a fix that had been put in (https://projects.puppetlabs.com/issues/20967), which uncovered a large number of things that made testing that issue difficult. So we unfortunately didn't get to everything that we wanted to (notably merging in heredoc support for the future parser and a better regression test for puppet properly closing pipes when daemonizing). We also didn't get to #14652 nor making progress on fixing up our testing systems to test against our packages.

Hi

Henrik has a draft in place for work he's been doing specifying a new injection mechanism which would subsume hiera 1.  The draft is here:

https://github.com/puppetlabs/armatures/blob/master/arm-8.hiera_2/index.md

He's called out a number of discussion point areas, which I've provided links to below with some initial responses in order to establish the arm-8 discussion thread.  (although I may have munged some of them incorrectly)

---

https://github.com/puppetlabs/armatures/blob/master/arm-8.hiera_2/index.md#use-hardcoded-environments

site.pp appears to be configurable in puppet-conf, so I think environments.pp should be as well.

https://github.com/puppetlabs/armatures/blob/master/arm-8.hiera_2/index.md#use-magical-return

-1 on magical returns for site {} to $environment; I don't think you want $environment set by accident.

https://github.com/puppetlabs/armatures/blob/master/arm-8.hiera_2/index.md#provide-access-to-classes-and-parameters-in-environmentspp

Agreed, classes and parameters from ENC seem superfluous in this step.

https://github.com/puppetlabs/armatures/blob/master/arm-8.hiera_2/index.md#conditional-categories-or-not

-1 on conditionals in site { categories {} } unless we are positive the complexity is required and can't be dealt with in another way.

https://github.com/puppetlabs/armatures/blob/master/arm-8.hiera_2/index.md#explicit-when-common-or-not

Allowing `when common {}` seems clearer, but I wouldn't require it.

https://github.com/puppetlabs/armatures/blob/master/arm-8.hiera_2/index.md#precedence-score---how

It doesn't seem clear to me that a nested binding necessarily should have precedence over an unnested one.  I think this is a case where we need to let people know about the conflict and let them resolve it in a higher layer.

I would not try the alt scoring method yet.  Though deterministic, I think it's too open to surprising the user rather than just letting them know what is in conflict.

https://github.com/puppetlabs/armatures/blob/master/arm-8.hiera_2/index.md#support-when-with-or-semantics

I'm the fence here; but leaning towards simplicity without 'when a or b' to begin with.

https://github.com/puppetlabs/armatures/blob/master/arm-8.hiera_2/index.md#is-abstract-too-abstract

I'm showing my own bias--abstract seems right to me.

bind stub "foo"

bind empty "foo" # but this might make people think they were 'unbinding'

bind placeholder "foo"

stub "foo"

declare "foo"

name "foo"

bind no body "foo"

or just accept

bind "foo" # but that seems too likely to hide mistakes.

bind abstract "foo" # still seems best

https://github.com/puppetlabs/armatures/blob/master/arm-8.hiera_2/index.md#is-override-too-overloaded

Do you mean as a word or is it used in two different areas in the proposed language?

override "foo" to 42

or 

bind overridding "foo" to 42

https://github.com/puppetlabs/armatures/blob/master/arm-8.hiera_2/index.md#lambda-or-type-reference-to-get-an-instance-or-support-both

I'm already concerned that lambda's are mind-blowing (albeit powerful). But given that complex multibind merges need something to sort them out, having lambdas available for that seems best.  Plugging in a runtime class seems like something that could be added later.

https://github.com/puppetlabs/armatures/blob/master/arm-8.hiera_2/index.md#use-keywords-include-and-exclude-for-class-inclusion-and-erasure

Having a shortcut syntax for this seems like a good idea.

https://github.com/puppetlabs/armatures/blob/master/arm-8.hiera_2/index.md#are-includeexclude-as-keywords-overloaded---use-something-else

I think the overloading is fine.  Right now I'm thinking that adding layers with intricate include/exclude parameters is going to be much rarer thatn including and excluding clases.

https://github.com/puppetlabs/armatures/blob/master/arm-8.hiera_2/index.md#is-it-of-value-to-pick-parts-from-an-enc-to-hiera2-transformation

Given that it's a small addition to an already complex area, it might be useful for migration as noted.