Re: [Puppet-dev] Re: Puppet RFC 23 - XPP Files

[Peter Huene]

Hi Jeremiah,

On Wed, Mar 30, 2016 at 11:56 AM,  wrote:

> I write a lot of native types for our internal use at work.  (I tell
> people that if you are just using Exec in Puppet that ansible is one search
> away in Google. ) Some of the Puppet code used with these types would be
> very challenging to "pre-compile" in any way.
>
> I think a lot of my questions are just because I don't consider a .pp file
> to usually be the unit of function in Puppet.  I only consider the
> resource, which is usually implemented in Ruby, and everything else is
> dressing.
>
> Reading over this proposal raises questions about how it will fit into
> Puppet, a language and environment very different from Python, Java or
> other languages (Puppet 4 long leaving the domain-specific title by the
> wayside.)
>
> Since you have to build an AST on a node-by-node basis I am having a hard
> time telling the value of this verses something like a marker that
> indicates the code has been parser validated.   If your code doesn't need
> node-by-node rebuild then perhaps the compiler could cache the results
> instead?  I know the adage about about three hard problems in Computer
> Science still applies but what this is doing is creating and managing a
> cache.
>

ASTs don't need to be built on a node-by-node basis (unless you meant
manifest-by-manifest basis); an AST is just a representation of the
manifest's source code. The XPP file format is simply an attempt to define
a serialization format for the AST itself so that, say, all the manifest
files in an environment could be parsed, validated, and the resulting ASTs
saved in a format that is faster to read when a catalog for a node is being
compiled all in one go and "upfront" (i.e. not during the catalog
compilation for any one node).

In compiler terminology, there's a "frontend" and a "backend".  The
frontend is responsible for producing an AST that the backend can evaluate
or generate code from (in the case of Puppet, the backend directly
evaluates ASTs to generate a catalog).  Having a well-defined AST
serialization format means we could potentially swap out another
implementation for the compiler's frontend, which is one of the goals of
this project and a first step towards a new compiler implementation.


> Pre-compiling is translating one language into another because compiling
> is changing one programing language, usually higher level, into another,
> usually lower level.   Puppet does something very different in my
> understanding given above.  It sounds as if the goat of the C++ parser is
> not to produce a catalog of resources but instead a ruby program for the
> agent to run.
>

The goal of this particular initiative is to enable the C++ parser (i.e.
the frontend) to interop with the Ruby evaluation implementation (i.e. the
backend).  The Puppet code is not being pre-compiled, but
pre-parsed/pre-validated; the C++ implementation will not (yet) evaluate
any Puppet code or load custom types or functions defined in Ruby.

The ultimate goal of the C++ implementation is to replace both the frontend
and the backend for catalog compilation, but that's a ways off still as
there needs to be design and implementation around loading custom types and
functions from Ruby source to maintain backwards compatibility.


>  From the statements about a C++ Puppet parser is the target still just a
> collection of resources?  Or is the goal to eventually spit out something
> other than what the Puppet server should send to a node?
>

The target is still the same thing we send to agents now: a resource
catalog.  That won't change when the C++ compiler implements the backend
too.


> Is the scope just 'closed' .pp files?  That is classes where all variables
> can be resolved without inquiry to facts?  The behavior of languages that
> support things like pre-compiled files is specific to how they do binding
> of missing data.  While this proposal punts on the 'serialization' format
> the handling of binding is pretty central. That raises questions like:
>
> How can a compiled format deal with Puppet features that call APIs?  Is
> this for the defined types?  How will it deal with the fact that the code
> could radically change based on node data not even present at the time the
> pre-compile is done?
>
> What happens if a precompiled module that depends on PuppetDB information
> is moved to an environment without it?  For that matter, is the format
> intended to move between Puppet installations or just very similar ones?
>
> My model of Puppet is that the compiled catalog is just an ordered list of
> resources which do not have any placeholders like variables or
> sub-dividable parts.  Classes in this model are just names that help you
> find the resources.
>
> This format is relevant to recent discussions among people on IRC and in
> the mailing lists and groups about getting and storing the catalog for a
> node.  This is historically something hard as an end user.

Re: [Puppet-dev] PR Triage starting at 10AM PDT (about five minutes)

[Peter Huene]

The notes from today's triage are available here:

https://github.com/voxpupuli/community-triage/blob/master/core/notes
/2016-03-15.md

On Tue, Mar 15, 2016 at 9:55 AM, Branan Riley  wrote:

> http://links.puppetlabs.com/pr-triage
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-dev/CADWDnrku0mMpOO5ES0zoqn1eOYuq5PSJwXa3_3ZFaQtMc-fsug%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-dev/CACZQQfNQtm47gU2TB%3Diq3CXtZZnyjiq4P2spsypZcyWpY8jVTg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet-dev] rspec and facter 2 vs facter 3

[Peter Huene]

Hi Miguel,

On Wed, Sep 9, 2015 at 5:23 AM, Miguel Di Ciurcio Filho <
mig...@instruct.com.br> wrote:

> Hi there,
>
> I was playing with rspec and run `rake spec` on puppetlabs-apache module.
>
> I'm have puppet-agent 1.2.2 installed and this error happens:
>
> Failure/Error: Unable to find matching line from backtrace
>  NameError:
>uninitialized constant Facter::Util::Loader
>
> After some investigation, I've found that the problem comes down to
> theses lines:
>
>
> https://github.com/puppetlabs/puppetlabs-apache/blob/master/spec/spec_helper.rb#L9
>
> Facter::Util::Loader.any_instance.stubs(:load_all)
>

Facter 3 doesn't have a Facter::Util::Loader defined, which is why this
code is unable to stub it.  Removing this line should be fine.


> Facter.clear
>

This call to `Facter.clear` should remain as it is attempting to ensure
that the facts collection is cleared between test runs.


> Facter.clear_messages
>

This method was removed in Facter 2, so I'm unsure as to how this was
working without testing against Facter 1.x.  Regardless, it should also be
removed.


> Looking further into the problem, I looked into the logs produced by
> Travis-CI and finally understood that the tests are depending on
> Facter 2.
>
> I commented out those 3 lines and the tests passed fine locally.
>
> Since I'm not that familiar with Facter's API changes from 2 to 3, are
> these 3 lines still relevant? I've read the comment above them (Ensure
> that we don't accidentally cache facts and environment between test
> cases) but I still don't understand what is the issue being handled.
>
> Is this in any way related to
> https://tickets.puppetlabs.com/browse/FACT-981 ?
>
> Regards,
>
> Miguel
>
>
> --
> http://www.instruct.com.br - 19 2511-6506
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-dev/CAK6Ystn5GJNNQyaoqEwCVj3VbVYgQ3tDOGkzx5c1REgPyJnkgA%40mail.gmail.com
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
--
Peter Huene
Software Engineer, Puppet Labs
Puppet Open Source Team
---

PuppetConf 2015 is coming to Portland, Oregon! Join us October 5-9!

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-dev/CACZQQfNZt4UhePqNekpJ9MEdAFg8iK0jebAE1hfhbbDDA6ZBBw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet-dev] rspec and facter 2 vs facter 3

[Peter Huene]

On Wed, Sep 9, 2015 at 8:53 AM, Peter Huene <peter.hu...@puppetlabs.com>
wrote:

> Hi Miguel,
>
> On Wed, Sep 9, 2015 at 5:23 AM, Miguel Di Ciurcio Filho <
> mig...@instruct.com.br> wrote:
>
>> Hi there,
>>
>> I was playing with rspec and run `rake spec` on puppetlabs-apache module.
>>
>> I'm have puppet-agent 1.2.2 installed and this error happens:
>>
>> Failure/Error: Unable to find matching line from backtrace
>>  NameError:
>>uninitialized constant Facter::Util::Loader
>>
>> After some investigation, I've found that the problem comes down to
>> theses lines:
>>
>>
>> https://github.com/puppetlabs/puppetlabs-apache/blob/master/spec/spec_helper.rb#L9
>>
>> Facter::Util::Loader.any_instance.stubs(:load_all)
>>
>
> Facter 3 doesn't have a Facter::Util::Loader defined, which is why this
> code is unable to stub it.  Removing this line should be fine.
>
>
>> Facter.clear
>>
>
> This call to `Facter.clear` should remain as it is attempting to ensure
> that the facts collection is cleared between test runs.
>
>
>> Facter.clear_messages
>>
>
> This method was removed in Facter 2, so I'm unsure as to how this was
> working without testing against Facter 1.x.  Regardless, it should also be
> removed.
>

Actually, I misspoke.  This method was moved into a different module and
mixed back into the Facter module, so it still exists in 2.x.  The Facter 3
API is missing this method as it was marked private and was not considered
to be part of the public API.  We may need to add this back in as there is
currently no way for tests to clear the warnonce/debugonce messages if they
are testing those methods.


>
>
>> Looking further into the problem, I looked into the logs produced by
>> Travis-CI and finally understood that the tests are depending on
>> Facter 2.
>>
>> I commented out those 3 lines and the tests passed fine locally.
>>
>> Since I'm not that familiar with Facter's API changes from 2 to 3, are
>> these 3 lines still relevant? I've read the comment above them (Ensure
>> that we don't accidentally cache facts and environment between test
>> cases) but I still don't understand what is the issue being handled.
>>
>> Is this in any way related to
>> https://tickets.puppetlabs.com/browse/FACT-981 ?
>>
>> Regards,
>>
>> Miguel
>>
>>
>> --
>> http://www.instruct.com.br - 19 2511-6506
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Puppet Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to puppet-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/puppet-dev/CAK6Ystn5GJNNQyaoqEwCVj3VbVYgQ3tDOGkzx5c1REgPyJnkgA%40mail.gmail.com
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> --
> Peter Huene
> Software Engineer, Puppet Labs
> Puppet Open Source Team
> ---
>
> PuppetConf 2015 is coming to Portland, Oregon! Join us October 5-9!
>
>


-- 
--
Peter Huene
Software Engineer, Puppet Labs
Puppet Open Source Team
---

PuppetConf 2015 is coming to Portland, Oregon! Join us October 5-9!

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-dev/CACZQQfO2JcEWO9-P461iGg1u4WdS68Lo9r5GvrzYiNXYCWMAdw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet-dev] How do you know what variables are frozen?

[Peter Huene]

On Wed, Jul 15, 2015 at 12:18 PM, Trevor Vaughan tvaug...@onyxpoint.com
wrote:

 Indeed, I did change it to that but it would still be nice to know what's
 going on so that I can stuff it into rspec and check for it.


Puppet's compiler intentionally freezes $trusted and its values.  If you
intend to support operating on arguments like this, you should be creating
a copy and not modifying the argument (probably a good rule to follow
anyway, especially for a function named parse).


 Thanks,

 Trevor

 On Wed, Jul 15, 2015 at 2:59 PM, R.I.Pienaar r...@devco.net wrote:



 - Original Message -
  From: Trevor Vaughan tvaug...@onyxpoint.com
  To: puppet-dev puppet-dev@googlegroups.com
  Sent: Wednesday, July 15, 2015 7:50:36 PM
  Subject: Re: [Puppet-dev] How do you know what variables are frozen?

  In this case, it was a custom function that was tripping things up.
 
  Looking through the code, I *think* this was the scenario:
 
  1) Fact = trusted['certname']
  2) Function call to parse_host($trusted['certname'])
  3) Parse host:
 
  host = args.first
  host.strip! # Here's the offender
 
  I also tried seeing if dup'ing the args would work, but it copies the
  frozen attribute with the String object (which makes sense).
 
  So, I don't know if I was trying to modify something from a Fact or if
 the
  object just happened to be carrying the 'frozen' status as it went
 along.

 so do not use strip! use x = something.strip? this way you dont try to
 modify anything in scope.

 --
 You received this message because you are subscribed to the Google Groups
 Puppet Developers group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to puppet-dev+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/puppet-dev/1753817636.200946.1436986745705.JavaMail.zimbra%40devco.net
 .
 For more options, visit https://groups.google.com/d/optout.




 --
 Trevor Vaughan
 Vice President, Onyx Point, Inc
 (410) 541-6699

 -- This account not approved for unencrypted proprietary information --

 --
 You received this message because you are subscribed to the Google Groups
 Puppet Developers group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to puppet-dev+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/puppet-dev/CANs%2BFoWKrP%2Btj%2BJsiENkam9q7ohLGQd5-Z5Gfa%3DoE%2BsSX2D%2Bvw%40mail.gmail.com
 https://groups.google.com/d/msgid/puppet-dev/CANs%2BFoWKrP%2Btj%2BJsiENkam9q7ohLGQd5-Z5Gfa%3DoE%2BsSX2D%2Bvw%40mail.gmail.com?utm_medium=emailutm_source=footer
 .

 For more options, visit https://groups.google.com/d/optout.




-- 
*Join us at **PuppetConf 2015, October 5-9 in Portland, OR - *www.
http://www.google.com/url?q=http%3A%2F%2Fwww.sa=Dsntz=1usg=AFQjCNEnS7itqgvQV3E4Se1fu4Um_UapSw
2015.puppetconf.com
http://www.google.com/url?q=http%3A%2F%2F2015.puppetconf.comsa=Dsntz=1usg=AFQjCNE1uQL4Sh23Vr-XkPLa4xfNcoXSog

*Register early to save 40%!*

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Developers group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-dev/CACZQQfOK4iJk7KcFT9_9n3pU-4U90Cxnhw2660FdafMCuYAggg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet-dev] How do you know what variables are frozen?

[Peter Huene]

On Wed, Jul 15, 2015 at 8:59 AM, Trevor Vaughan tvaug...@onyxpoint.com
wrote:

 I *think* I've just run into a case where I was trying to run strip! on a
 frozen Facter variable.

 1) How do we know what variables are frozen coming from Facter?


Facter shouldn't be freezing resolved fact values, so is this something
that a custom fact is explicitly doing to the returned value?

http://ruby-doc.org/core-2.2.2/Object.html#method-i-frozen-3F should work
for checking in an object is frozen, though.


 2) What is the best way to ensure that our tests check for this case?


 Thanks,

 Trevor

 --
 Trevor Vaughan
 Vice President, Onyx Point, Inc
 (410) 541-6699

 -- This account not approved for unencrypted proprietary information --

 --
 You received this message because you are subscribed to the Google Groups
 Puppet Developers group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to puppet-dev+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/puppet-dev/CANs%2BFoW0ovdB6E%3DLTFtD7Er126StgUyuaTpB89n2Bz%2BFminS7w%40mail.gmail.com
 https://groups.google.com/d/msgid/puppet-dev/CANs%2BFoW0ovdB6E%3DLTFtD7Er126StgUyuaTpB89n2Bz%2BFminS7w%40mail.gmail.com?utm_medium=emailutm_source=footer
 .
 For more options, visit https://groups.google.com/d/optout.




-- 
*Join us at **PuppetConf 2015, October 5-9 in Portland, OR - *www.
http://www.google.com/url?q=http%3A%2F%2Fwww.sa=Dsntz=1usg=AFQjCNEnS7itqgvQV3E4Se1fu4Um_UapSw
2015.puppetconf.com
http://www.google.com/url?q=http%3A%2F%2F2015.puppetconf.comsa=Dsntz=1usg=AFQjCNE1uQL4Sh23Vr-XkPLa4xfNcoXSog

*Register early to save 40%!*

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Developers group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-dev/CACZQQfMTNFjiUyQcd_hymwtEcLhX1z%2BeQA9Z8P5AyTnOfLpyzg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet-dev] Community PR Triage for 2015-06-02

[Peter Huene]

Starting the PR triage for puppet/facter/hiera/puppet-server in about 10 
minutes (10:00 AM PDT) at http://links.puppetlabs.com/pr-triage

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Developers group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-dev/f64af402-0d1e-45bb-b641-24c74ab12c69%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet-dev] Re: Community PR Triage for 2015-05-26

[Peter Huene]

On Tuesday, May 26, 2015 at 9:45:24 AM UTC-7, Peter Huene wrote:

 Starting the PR triage for puppet/facter/hiera/puppet-server in about 15 
 minutes (10:00 AM PDT) at http://links.puppetlabs.com/pr-triage


Notes available at 
https://github.com/puppet-community/community-triage/blob/master/core/notes/2015-05-26.md

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Developers group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-dev/75b80357-0825-42f7-b2aa-ec18beb846fd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet-dev] Community PR Triage for 2015-05-26

[Peter Huene]

Starting the PR triage for puppet/facter/hiera/puppet-server in about 15 
minutes (10:00 AM PDT) at http://links.puppetlabs.com/pr-triage

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Developers group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-dev/f2ad3bef-a3e5-479c-a7f1-49639a3379e4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet-dev] Community PR Triage for 2015-05-19

[Peter Huene]

Starting the PR triage for puppet/facter/hiera/puppet-server in about 10 
minutes (10:00 AM PDT) at http://links.puppetlabs.com/pr-triage

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Developers group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-dev/afe1babf-9d72-44cc-a2cc-13a290866453%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet-dev] Re: Community PR Triage for 2015-05-19

[Peter Huene]

On Tuesday, May 19, 2015 at 9:49:02 AM UTC-7, Peter Huene wrote:

 Starting the PR triage for puppet/facter/hiera/puppet-server in about 10 
 minutes (10:00 AM PDT) at http://links.puppetlabs.com/pr-triage


Triage notes are available at: 
https://github.com/puppet-community/community-triage/blob/master/core/notes/2015-05-19.md
 

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Developers group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-dev/c616d991-5590-47cb-8c45-abb4e21dd650%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet-dev] Re: Community PR Triage for 2015-05-13

[Peter Huene]

On Wednesday, May 13, 2015 at 9:50:09 AM UTC-7, Peter Huene wrote:

 Starting the PR triage for puppet/facter/hiera/puppet-server in about 10 
 minutes (10:00 AM PDT) at http://links.puppetlabs.com/pr-triage

 
Notes available at 
https://github.com/puppet-community/community-triage/blob/master/core/notes/2015-05-13.md
 
https://github.com/puppet-community/community-triage/blob/master/core/notes/2015-04-29.md

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Developers group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-dev/5ca7fc4b-b60c-444d-97bb-12764f0e563a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet-dev] Re: Community PR Triage for 2015-05-13

[Peter Huene]

On Wednesday, May 13, 2015 at 11:44:24 AM UTC-7, Peter Huene wrote:

 On Wednesday, May 13, 2015 at 9:50:09 AM UTC-7, Peter Huene wrote:

 Starting the PR triage for puppet/facter/hiera/puppet-server in about 10 
 minutes (10:00 AM PDT) at http://links.puppetlabs.com/pr-triage

  
 Notes available at 
 https://github.com/puppet-community/community-triage/blob/master/core/notes/2015-05-13.md
  
 https://github.com/puppet-community/community-triage/blob/master/core/notes/2015-04-29.md


Correction in URL: 
https://github.com/puppet-community/community-triage/blob/master/core/notes/2015-05-13.md

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Developers group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-dev/c156dc2a-4b9c-4b70-b5de-633dc14a9b25%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet-dev] Community PR Triage for 2015-05-13

[Peter Huene]

Starting the PR triage for puppet/facter/hiera/puppet-server in about 10 
minutes (10:00 AM PDT) at http://links.puppetlabs.com/pr-triage

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Developers group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-dev/bd85fb60-9d30-456a-8e43-ceff2ce86212%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet-dev] Re: Community PR Triage for 2015-05-06

[Peter Huene]

On Wednesday, May 6, 2015 at 9:52:16 AM UTC-7, Peter Huene wrote:

 Starting the PR triage for puppet/facter/hiera/puppet-server in about 10 
 minutes (10:00 AM PDT) at http://links.puppetlabs.com/pr-triage


Notes are available at: 
https://github.com/puppet-community/community-triage/blob/master/core/notes/2015-05-06.md
 

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Developers group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-dev/0e9c7360-3546-4c31-a44f-3c2773b8dbbc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet-dev] Community PR Triage for 2015-05-06

[Peter Huene]

Starting the PR triage for puppet/facter/hiera/puppet-server in about 10 
minutes (10:00 AM PDT) at http://links.puppetlabs.com/pr-triage

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Developers group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-dev/f08d0efd-449e-45f2-887b-15c94234a726%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet-dev] Community PR Triage for 2015-04-29

[Peter Huene]

Starting the PR triage for puppet/facter/hiera/puppet-server in about 10 
minutes (10:00 AM PDT) at http://links.puppetlabs.com/pr-triage

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Developers group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-dev/8c5c9555-e1e1-4fe2-8293-fbfee0e050fe%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet-dev] Re: Community PR Triage for 2015-04-29

[Peter Huene]

On Wednesday, April 29, 2015 at 9:48:46 AM UTC-7, Peter Huene wrote:

 Starting the PR triage for puppet/facter/hiera/puppet-server in about 10 
 minutes (10:00 AM PDT) at http://links.puppetlabs.com/pr-triage


Notes available at 
https://github.com/puppet-community/community-triage/blob/master/core/notes/2015-04-29.md
 

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Developers group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-dev/dbbf79dc-684c-4343-ba62-1e025c453a1a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet-dev] Community PR Triage for 2015-04-22

[Peter Huene]

Starting the PR triage for puppet/facter/hiera/puppet-server in about 15 
minutes (10:00 AM PDT) at http://links.puppetlabs.com/pr-triage

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Developers group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-dev/13d9e87c-79b2-424c-b4c6-d789fb8eff12%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet-dev] Re: Community PR Triage for 2015-04-22

[Peter Huene]

On Wednesday, April 22, 2015 at 9:43:19 AM UTC-7, Peter Huene wrote:

 Starting the PR triage for puppet/facter/hiera/puppet-server in about 15 
 minutes (10:00 AM PDT) at http://links.puppetlabs.com/pr-triage


Notes available 
at 
https://github.com/puppet-community/community-triage/blob/master/core/notes/2015-04-22.md

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Developers group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-dev/7cb5635a-3c68-4be3-bfdf-0bd71ee4e980%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet-dev] Announce: Facter 2.4.1 available

[Peter Huene]

Facter 2.4.1 is a bug fix release in the Facter 2 series.

Included in this release are fixes for the following bugs:

   - The ec2_metadata fact was not filtering out sensitive IAM security
   credentials.
   - The virtual fact's detection of KVM hypervisors when running as
   non-root on Linux was misreporting as physical.

To download Facter, follow the instructions here:
http://docs.puppetlabs.com/guides/install_puppet/pre_install.html


Release notes are available here: http://docs.puppetlabs.
com/facter/latest/release_notes.html


To see a complete list of issues fixed in this release:
*https://tickets.puppetlabs.com/issues/?filter=13550
https://tickets.puppetlabs.com/issues/?filter=13550 *

We're tracking bugs people find in this release with the Affected Version
field set to 2.4.1:
*https://tickets.puppetlabs.com/issues/?filter=13551
https://tickets.puppetlabs.com/issues/?filter=13551 *

-- 
*Join us at **PuppetConf 2015, October 5-9 in Portland, OR - *www.
http://www.google.com/url?q=http%3A%2F%2Fwww.sa=Dsntz=1usg=AFQjCNEnS7itqgvQV3E4Se1fu4Um_UapSw
2015.puppetconf.com
http://www.google.com/url?q=http%3A%2F%2F2015.puppetconf.comsa=Dsntz=1usg=AFQjCNE1uQL4Sh23Vr-XkPLa4xfNcoXSog

*Register early to save 40%!*

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Developers group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-dev/CACZQQfOihfQN5j27k7ePSVqGV63tiN%2BzSQoDOyPsL0QL4wKTrw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet-dev] Announce: Native Facter 0.3.0 is available!

[Peter Huene]

Native Facter (cfacter) 0.3.0 is a features-and-fixes release in the Native
Facter pre-1.0 series.

Included in this release is support for building Native Facter on Windows
and Solaris.  The EC2 and GCE facts were also implemented in this release.

Notable updates:

   - Windows is now a supported platform:
   - Please see https://github.com/puppetlabs/cfacter/blob/master/WINDOWS.md
   for build instructions.
  - Solaris is now a supported platform:
   - Please see https://github.com/puppetlabs/cfacter-build
   for build instructions.
   - Added a Fedora 20 package.
   - Implemented overriding facts from FACTER_* environment variables.
   - Added a new networking structured fact to organize networking data.
   - Implemented the EC2 and GCE facts.
   - Various bug fixes including a fix for a hang when exec'ing a shell
   script missing a hashbang and supporting custom facts on platforms with
   libraries in a lib64 directory.

Packages for the following platforms have been distributed on the Puppet
Labs Package Repositories:

   - Debian/Ubuntu: Lucid, Precise, Squeeze, Trusty, and Wheezy.
   - RHEL 5, 6, and 7.
   - Fedora 20

Please see
https://docs.puppetlabs.com/guides/puppetlabs_package_repositories.html
 for information about installing from the package repositories.

-- 
*Join us at **PuppetConf 2015, October 5-9 in Portland, OR - *www.
http://www.google.com/url?q=http%3A%2F%2Fwww.sa=Dsntz=1usg=AFQjCNEnS7itqgvQV3E4Se1fu4Um_UapSw
2015.puppetconf.com
http://www.google.com/url?q=http%3A%2F%2F2015.puppetconf.comsa=Dsntz=1usg=AFQjCNE1uQL4Sh23Vr-XkPLa4xfNcoXSog

*Register early to save 40%!*

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Developers group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-dev/CACZQQfPC69-mTVBzf1fD1pnF0wBjp45OYS9NtM08ucoEaqbUjw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet-dev] Puppet PR Triage

[Peter Huene]

The Puppet PR Triage will start in about 10 minutes, at 10 AM PST.

Please join us at http://links.puppetlabs.com/pr-triage

-- 
*Join us at **PuppetConf 2015, October 5-9 in Portland, OR - *www.
http://www.google.com/url?q=http%3A%2F%2Fwww.sa=Dsntz=1usg=AFQjCNEnS7itqgvQV3E4Se1fu4Um_UapSw
2015.puppetconf.com
http://www.google.com/url?q=http%3A%2F%2F2015.puppetconf.comsa=Dsntz=1usg=AFQjCNE1uQL4Sh23Vr-XkPLa4xfNcoXSog

*Register early to save 40%!*

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Developers group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-dev/CACZQQfO%2Bh9CxXTC6R63tDN_zFvJb%2BhQGvXoTtsoRdai2ENNcQg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet-dev] Re: Puppet PR Triage

[Peter Huene]

The notes for this week's triage are now available at:

*https://github.com/puppet-community/community-triage/blob/master/core/notes/2014-12-03.md
https://github.com/puppet-community/community-triage/blob/master/core/notes/2014-12-03.md*

Thanks,

Peter

On Wed, Dec 3, 2014 at 9:50 AM, Peter Huene peter.hu...@puppetlabs.com
wrote:

 The Puppet PR Triage will start in about 10 minutes, at 10 AM PST.

 Please join us at http://links.puppetlabs.com/pr-triage

 --
 *Join us at **PuppetConf 2015, October 5-9 in Portland, OR - *www.
 http://www.google.com/url?q=http%3A%2F%2Fwww.sa=Dsntz=1usg=AFQjCNEnS7itqgvQV3E4Se1fu4Um_UapSw
 2015.puppetconf.com
 http://www.google.com/url?q=http%3A%2F%2F2015.puppetconf.comsa=Dsntz=1usg=AFQjCNE1uQL4Sh23Vr-XkPLa4xfNcoXSog

 *Register early to save 40%!*




-- 
*Join us at **PuppetConf 2015, October 5-9 in Portland, OR - *www.
http://www.google.com/url?q=http%3A%2F%2Fwww.sa=Dsntz=1usg=AFQjCNEnS7itqgvQV3E4Se1fu4Um_UapSw
2015.puppetconf.com
http://www.google.com/url?q=http%3A%2F%2F2015.puppetconf.comsa=Dsntz=1usg=AFQjCNE1uQL4Sh23Vr-XkPLa4xfNcoXSog

*Register early to save 40%!*

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Developers group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-dev/CACZQQfMEw5rY6sGmr6O%2BMnjjFTs-Pubm0oW0o34r-tN1T%2BdN%2Bg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet-dev] Puppet PR Triage starting in 10 minutes

[Peter Huene]

The Puppet/Facter/Hiera PR triage will be starting in 10 minutes at
http://links.puppetlabs.com/pr-triage

- Peter

-- 
*Join us at **PuppetConf 2015, October 5-9 in Portland, OR - *www.
http://www.google.com/url?q=http%3A%2F%2Fwww.sa=Dsntz=1usg=AFQjCNEnS7itqgvQV3E4Se1fu4Um_UapSw
2015.puppetconf.com
http://www.google.com/url?q=http%3A%2F%2F2015.puppetconf.comsa=Dsntz=1usg=AFQjCNE1uQL4Sh23Vr-XkPLa4xfNcoXSog

*Register early to save 40%!*

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Developers group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-dev/CACZQQfMrFMCc-7fp9EVnrVK9_hjPDvybaMvhKxaZVu9j88PiLA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.