Puppet users - Jun 2011 - "Open Source Team" planning meeting summary 2011-06-1

Thanks to everyone that provided their feedback on what they would like
to see worked on.  We''ve gone through the suggestions, and
re-prioritized our back-log to take into account the various
suggestions, and the state of each of the tickets.

Next week, I don''t plan on directly soliciting with a "call for
tickets"
like I did this week, but I definitely wish to encourage everyone to
comment on these if they have anything they would like to bring up.

The main reason for not having a call for tickets next week is that I''d
like to encourage everyone to take advantage of the voting functionality
of the ticketing system to help us figure out what the most important
things are.  I''ve created a public saved search[1] to easily see what
the current top voted issues are, in case you''re interested in what
that
list looks like.

There are a few suggestions that aren''t listed here, but we
haven''t
forgotten about them.  We just didn''t want to end up trying to stuff a
ton of things into our backlog, when we already knew we wouldn''t be
able
to get to everything this week.

The current "Open Source Team" backlog:

 * #2128 - Allow arbitrary fact as node_name identifier

 * #7127 - prerun_command don''t stop puppet on error

 *  #650 - puppet replaces configuration directories when they are
           symlinks

 * #4416 - Resources cannot be used on the run where they are synced

 * #7742 - Package type V2 - apt

 * #7224 - Bad english: hostname was not match with the server
           certificate

 * #5517 - behavior change within 2.6 makes it impossible to override
           class parameters of "included" parametrized classes

 * #7743 - Package type V2 - dpkg

 * #7744 - Package type V2 - aptitude

[1] http://projects.puppetlabs.com/projects/puppet/issues?query_id=147

-- 
Jacob Helwig

Hi,

I just wanted to clarify something from this email. Although the best way to
get traction for a ticket in the future will be voting in the ticketing
system, people are always welcome to highlight particular tickets in order
to solicit votes.

With that in mind, a quick list of things that I have found particularly
frustrating about Puppet:

https://projects.puppetlabs.com/issues/4408

Puppet should at least warn (or better yet fail) when you try to use an
undefined variable (it should not warn/fail, however if a variable was
explicitly set to undef)

http://projects.puppetlabs.com/issues/3910

a +1 to ENCs being authoritative over environments. I have done some ugly
hacks that I am ashamed of to work around this.

http://projects.puppetlabs.com/issues/4908

listing the internal resources in the reports creates lots of unnecessary
(and useless) data in reports



On Wed, Jun 1, 2011 at 2:46 PM, Jacob Helwig <jacob@puppetlabs.com> wrote:
> Thanks to everyone that provided their feedback on what they would like
> to see worked on.  We''ve gone through the suggestions, and
> re-prioritized our back-log to take into account the various
> suggestions, and the state of each of the tickets.
>
> Next week, I don''t plan on directly soliciting with a "call
for tickets"
> like I did this week, but I definitely wish to encourage everyone to
> comment on these if they have anything they would like to bring up.
>
> The main reason for not having a call for tickets next week is that
I''d
> like to encourage everyone to take advantage of the voting functionality
> of the ticketing system to help us figure out what the most important
> things are.  I''ve created a public saved search[1] to easily see
what
> the current top voted issues are, in case you''re interested in
what that
> list looks like.
>
> There are a few suggestions that aren''t listed here, but we
haven''t
> forgotten about them.  We just didn''t want to end up trying to
stuff a
> ton of things into our backlog, when we already knew we wouldn''t
be able
> to get to everything this week.
>
> The current "Open Source Team" backlog:
>
>  * #2128 - Allow arbitrary fact as node_name identifier
>
>  * #7127 - prerun_command don''t stop puppet on error
>
>  *  #650 - puppet replaces configuration directories when they are
>           symlinks
>
>  * #4416 - Resources cannot be used on the run where they are synced
>
>  * #7742 - Package type V2 - apt
>
>  * #7224 - Bad english: hostname was not match with the server
>           certificate
>
>  * #5517 - behavior change within 2.6 makes it impossible to override
>           class parameters of "included" parametrized classes
>
>  * #7743 - Package type V2 - dpkg
>
>  * #7744 - Package type V2 - aptitude
>
> [1] http://projects.puppetlabs.com/projects/puppet/issues?query_id=147
>
> --
> Jacob Helwig
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
>
> iQGcBAEBAgAGBQJN5rMnAAoJEHJabXWGiqEB/m8MAJ0lcfe6CQPLZRDsW1MBuS+h
> 1KNZI0vTmZ72RKhvQ2JebjwacA1hQ7yalnPf/g/1rFc+HXY+4v1IZHin8vbjWBJZ
> 1kdgZf6OUxpSZo9UTs143rToLo07BzC0c+KIOkR8GOXVtgOqspRRcqdjvEayAkD8
> zrVTGbikIDYbSi8xWTCzvS+KakEZ3BTpWyMSnc8KvnTMMr1AKpDye1zHsT3DblX6
> n960LgY88oqmQty3T9nrtXnFBzoQNz5UoscwG+R+Uxl6Bg0hENNlnWKS1ZEDf/Zk
> H4aM3HgGjReTJYJg9wojV5kD8w6+aolM+wU8MrE8AjRNuD2d95aQevRduTJZmZp8
> 7IhdMKgJQ95K1uzDpTCx1XxTQPeYSEJLtMHgJ5ZLXS+JwFFxK/QVu9ngm11SmEws
> h53t54doxcbo0wjuV/n002PeGczFO+v+0A5XJ7KRaVhF3Qq20SCET5wNxGEKydjH
> M3taWRNpPHRl5lkM4Dt+ZaRaMmW8Pve1pQ/2fHLZNg=> =0cpB
> -----END PGP SIGNATURE-----
>
>
-- 
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@googlegroups.com.
To unsubscribe from this group, send email to
puppet-dev+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-dev?hl=en.

On 15 Jun 2011, at 9:56 AM, Dan Bode wrote:
> I just wanted to clarify something from this email. Although the best way
to get traction for a ticket in the future will be voting in the ticketing
system, people are always welcome to highlight particular tickets in order to
solicit votes.
In that case, I''ll make a shameless plug for #6863 -- allow array
literals to be given as function arguments in the parser. I''m pretty
sure it''s just an oversight that this isn''t currently allowed,
but it leads to ugly workarounds like this:

	$array = [''a'',''b'',''c'']
	$var = myfunction(''first arg'', $array)

	$empty_array = []
	$other_var = myfunction($empty_array)

-- 
Ian Ward Comfort <icomfort@stanford.edu>
Systems Team Lead, Academic Computing Services, Stanford University

-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On Wednesday, June 15, 2011 at 6:09 PM, Ian Ward Comfort wrote:
> On 15 Jun 2011, at 9:56 AM, Dan Bode wrote:
> > I just wanted to clarify something from this email. Although the best
way to get traction for a ticket in the future will be voting in the ticketing
system, people are always welcome to highlight particular tickets in order to
solicit votes.
> 
> In that case, I''ll make a shameless plug for #6863 -- allow array
literals to be given as function arguments in the parser. I''m pretty
sure it''s just an oversight that this isn''t currently allowed,
but it leads to ugly workarounds like this:
> 
>  $array =
[''a'',''b'',''c'']
>  $var = myfunction(''first arg'', $array)
> 
>  $empty_array = []
>  $other_var = myfunction($empty_array)
> 
Hmm, this should already be fixed for 2.7.0. I guess I just missed that ticket
when fixing up the grammar. I''ll verify that and update it if so.
> -- 
> Ian Ward Comfort <icomfort@stanford.edu
(mailto:icomfort@stanford.edu)>
> Systems Team Lead, Academic Computing Services, Stanford University
> 
> -- 
> 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@googlegroups.com
(mailto:puppet-dev@googlegroups.com).
> To unsubscribe from this group, send email to
puppet-dev+unsubscribe@googlegroups.com
(mailto:puppet-dev+unsubscribe@googlegroups.com).
> For more options, visit this group at
http://groups.google.com/group/puppet-dev?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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.