Re: [Puppet Users] ANNOUNCE: Puppet 2.6.0 - Final release!
Douglas Garstang wrote: >> >> After poking around looking at the bugs people filed, it just seems >> like it wasn't tested fully enough. It passes simple test cases. > > For release candidates though, not the final release. If it doesn't > work with the final release, it should be noted in the documentation > that it doesn't work. It doesn't seem to work for autoloaded classes, > which, at least in my world, makes it useless. So we had an extensive release candidate process - during which a fairly small number of people tested a number of features including PL people internally. The examples of parametrized classes we tested were not sufficiently extensive to identify the problem. Interestingly tracking the history of this - you did call out a problem with 2.6.0rc1 on the mailing list but didn't log a ticket until well after the release was marked final 7/19 versus 7/30. That ticket (http://projects.puppetlabs.com/issues/4405) appears to be have been a moot issue - it's not clear to me that there was a problem in the first place. Later, a ticket was logged (http://projects.puppetlabs.com/issues/4423) again after 2.6.0 was released by Jeff McCune based on his further testing and exposition of your emails. Overall, from this I'd mention that it is critical to us that people log tickets - we can't always follow every thread on the mailing list. If you find a bug then log a ticket as quickly as possible - include the version, your platform, an accurate and simple as possible manifest example of your issue, etc, etc. If we don't act on your ticket then bug us until we do. Best of all - submit bug fixes or patches. Regards James Turnbull -- Puppet Labs - http://www.puppetlabs.com C: 503-734-8571 -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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] ANNOUNCE: Puppet 2.6.0 - Final release!
On Mon, Aug 9, 2010 at 9:30 AM, Nigel Kersten wrote:
> On Mon, Aug 9, 2010 at 8:27 AM, Douglas Garstang
> wrote:
>> On Sun, Aug 8, 2010 at 2:54 PM, Peter Meier wrote:
>>> -BEGIN PGP SIGNED MESSAGE-
>>> Hash: SHA1
>>>
>>> On 08/07/2010 12:29 AM, Douglas Garstang wrote:
On Mon, Jul 19, 2010 at 10:23 PM, James Turnbull
wrote:
> The journey was long and arduous and many fell along the way but Puppet
> Labs is proud to announce the 2.6.0 release!
>
> The 2.6.0 release is a major feature release and includes a huge variety
> of new features, fixes, updates and enhancements. These include the
> complete cut-over from XMLRPC to the REST API, numerous language
> enhancements, a complete rewrite of the events and reporting system, an
> internal Ruby DSL, a single binary, Windows support, a new HTTP report
> processor, and a myriad of other enhancements.
>
> We've included release notes below that you can also see at:
>
> http://projects.puppetlabs.com/projects/puppet/wiki/Release_Notes
Cool. Did autoloaded module names in parameterized classes get fixed?
Ie, in the 2.6 rc I tried using, you couldn't go:
class { syslog::server: version => "1.3.13" }
Also, seems like a lot of people where having trouble getting
parameterized classes to work at all. Curious to see if that works
now.
>>>
>>> have a look at the bugreport to track that issue.
>>
>> Seems a bit weird to me that one of the new features would not working
>> in the final release...
>
> New features seem like a perfectly reasonable place for new bugs to
> appear to me actually :)
>
> After poking around looking at the bugs people filed, it just seems
> like it wasn't tested fully enough. It passes simple test cases.
For release candidates though, not the final release. If it doesn't
work with the final release, it should be noted in the documentation
that it doesn't work. It doesn't seem to work for autoloaded classes,
which, at least in my world, makes it useless.
Doug.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@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] ANNOUNCE: Puppet 2.6.0 - Final release!
On Mon, Aug 9, 2010 at 8:27 AM, Douglas Garstang
wrote:
> On Sun, Aug 8, 2010 at 2:54 PM, Peter Meier wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On 08/07/2010 12:29 AM, Douglas Garstang wrote:
>>> On Mon, Jul 19, 2010 at 10:23 PM, James Turnbull
>>> wrote:
The journey was long and arduous and many fell along the way but Puppet
Labs is proud to announce the 2.6.0 release!
The 2.6.0 release is a major feature release and includes a huge variety
of new features, fixes, updates and enhancements. These include the
complete cut-over from XMLRPC to the REST API, numerous language
enhancements, a complete rewrite of the events and reporting system, an
internal Ruby DSL, a single binary, Windows support, a new HTTP report
processor, and a myriad of other enhancements.
We've included release notes below that you can also see at:
http://projects.puppetlabs.com/projects/puppet/wiki/Release_Notes
>>>
>>> Cool. Did autoloaded module names in parameterized classes get fixed?
>>> Ie, in the 2.6 rc I tried using, you couldn't go:
>>>
>>> class { syslog::server: version => "1.3.13" }
>>>
>>> Also, seems like a lot of people where having trouble getting
>>> parameterized classes to work at all. Curious to see if that works
>>> now.
>>
>> have a look at the bugreport to track that issue.
>
> Seems a bit weird to me that one of the new features would not working
> in the final release...
New features seem like a perfectly reasonable place for new bugs to
appear to me actually :)
After poking around looking at the bugs people filed, it just seems
like it wasn't tested fully enough. It passes simple test cases.
>
> Doug.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-us...@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.
>
>
--
nigel
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@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] ANNOUNCE: Puppet 2.6.0 - Final release!
On Sun, Aug 8, 2010 at 2:54 PM, Peter Meier wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 08/07/2010 12:29 AM, Douglas Garstang wrote:
>> On Mon, Jul 19, 2010 at 10:23 PM, James Turnbull
>> wrote:
>>> The journey was long and arduous and many fell along the way but Puppet
>>> Labs is proud to announce the 2.6.0 release!
>>>
>>> The 2.6.0 release is a major feature release and includes a huge variety
>>> of new features, fixes, updates and enhancements. These include the
>>> complete cut-over from XMLRPC to the REST API, numerous language
>>> enhancements, a complete rewrite of the events and reporting system, an
>>> internal Ruby DSL, a single binary, Windows support, a new HTTP report
>>> processor, and a myriad of other enhancements.
>>>
>>> We've included release notes below that you can also see at:
>>>
>>> http://projects.puppetlabs.com/projects/puppet/wiki/Release_Notes
>>
>> Cool. Did autoloaded module names in parameterized classes get fixed?
>> Ie, in the 2.6 rc I tried using, you couldn't go:
>>
>> class { syslog::server: version => "1.3.13" }
>>
>> Also, seems like a lot of people where having trouble getting
>> parameterized classes to work at all. Curious to see if that works
>> now.
>
> have a look at the bugreport to track that issue.
Seems a bit weird to me that one of the new features would not working
in the final release...
Doug.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@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] ANNOUNCE: Puppet 2.6.0 - Final release!
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/07/2010 12:29 AM, Douglas Garstang wrote:
> On Mon, Jul 19, 2010 at 10:23 PM, James Turnbull wrote:
>> The journey was long and arduous and many fell along the way but Puppet
>> Labs is proud to announce the 2.6.0 release!
>>
>> The 2.6.0 release is a major feature release and includes a huge variety
>> of new features, fixes, updates and enhancements. These include the
>> complete cut-over from XMLRPC to the REST API, numerous language
>> enhancements, a complete rewrite of the events and reporting system, an
>> internal Ruby DSL, a single binary, Windows support, a new HTTP report
>> processor, and a myriad of other enhancements.
>>
>> We've included release notes below that you can also see at:
>>
>> http://projects.puppetlabs.com/projects/puppet/wiki/Release_Notes
>
> Cool. Did autoloaded module names in parameterized classes get fixed?
> Ie, in the 2.6 rc I tried using, you couldn't go:
>
> class { syslog::server: version => "1.3.13" }
>
> Also, seems like a lot of people where having trouble getting
> parameterized classes to work at all. Curious to see if that works
> now.
have a look at the bugreport to track that issue.
cheers pete
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkxfJ1gACgkQbwltcAfKi38EPACffQ3dpZGWg187UlLP+jPqByfU
hqkAnR8aiytcejnPoD5RdE2+fwEuWlLl
=5gST
-END PGP SIGNATURE-
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@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] ANNOUNCE: Puppet 2.6.0 - Final release!
On Mon, Jul 19, 2010 at 10:23 PM, James Turnbull wrote:
> The journey was long and arduous and many fell along the way but Puppet
> Labs is proud to announce the 2.6.0 release!
>
> The 2.6.0 release is a major feature release and includes a huge variety
> of new features, fixes, updates and enhancements. These include the
> complete cut-over from XMLRPC to the REST API, numerous language
> enhancements, a complete rewrite of the events and reporting system, an
> internal Ruby DSL, a single binary, Windows support, a new HTTP report
> processor, and a myriad of other enhancements.
>
> We've included release notes below that you can also see at:
>
> http://projects.puppetlabs.com/projects/puppet/wiki/Release_Notes
Cool. Did autoloaded module names in parameterized classes get fixed?
Ie, in the 2.6 rc I tried using, you couldn't go:
class { syslog::server: version => "1.3.13" }
Also, seems like a lot of people where having trouble getting
parameterized classes to work at all. Curious to see if that works
now.
Doug.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@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 on Windows (was Re: [Puppet Users] ANNOUNCE: Puppet 2.6.0 - Final release!)
I (unfortunately) have some experience in throwing together NSIS and WISE installers and would be willing to contribute towards such a packaging effort ... *if only I could get it to work in the first place!* On Tue, Jul 20, 2010 at 12:47 AM, James Turnbull wrote: > Rohan McGovern wrote: >> James Turnbull said: >>> The journey was long and arduous and many fell along the way but Puppet >>> Labs is proud to announce the 2.6.0 release! >>> >> >> Is anyone aware of an attempt to package up a complete (puppet + all >> prereqs) installer for Windows? Either official, or by someone in the >> community? >> >> And, asking from the other direction: would anyone else be interested in >> such a thing? >> >> I would be, because setting up puppet on Windows seems pretty tough >> right now. I also have no need for Ruby on my Windows boxes except >> for the usage of puppet. > > Rohan > > There isn't such an attempt so far - we've got it on the cards to do - > but any progress in that direction would be awesome. > > We've got some basic notes at: > > http://projects.puppetlabs.com/projects/puppet/wiki/Puppet_Windows > > Regards > > James Turnbull > > -- > Puppet Labs - http://www.puppetlabs.com > C: 503-734-8571 > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-us...@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-us...@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 on Windows (was Re: [Puppet Users] ANNOUNCE: Puppet 2.6.0 - Final release!)
On 2010-07-20 01:47, James Turnbull wrote: > Rohan McGovern wrote: >> James Turnbull said: >>> The journey was long and arduous and many fell along the way but Puppet >>> Labs is proud to announce the 2.6.0 release! >>> >> >> Is anyone aware of an attempt to package up a complete (puppet + all >> prereqs) installer for Windows? Either official, or by someone in the >> community? >> >> And, asking from the other direction: would anyone else be interested in >> such a thing? >> >> I would be, because setting up puppet on Windows seems pretty tough >> right now. I also have no need for Ruby on my Windows boxes except >> for the usage of puppet. > > Rohan > > There isn't such an attempt so far - we've got it on the cards to do - > but any progress in that direction would be awesome. > > We've got some basic notes at: > > http://projects.puppetlabs.com/projects/puppet/wiki/Puppet_Windows > Oh, I didn't see your reply before I sent my last message. thanks for the link. -- Gabriel Filion -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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] ANNOUNCE: Puppet 2.6.0 - Final release!
On 2010-07-20 01:40, Rohan McGovern wrote: > And, asking from the other direction: would anyone else be interested in > such a thing? > I know the company I work for would be very interested in having it packaged for Windows. The last time I asked on IRC, the Windows support was coming along but was not quite there yet. What features are currently working properly and what are the ones that are lacking? -- Gabriel Filion -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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 on Windows (was Re: [Puppet Users] ANNOUNCE: Puppet 2.6.0 - Final release!)
James- Will you be updating your book with info on Windows management? Our Windows side likes books, and after the success I have had with Puppet they are wanting to look at it now that it supports Windows. Evan On Tue, Jul 20, 2010 at 12:47 AM, James Turnbull wrote: > Rohan McGovern wrote: >> James Turnbull said: >>> The journey was long and arduous and many fell along the way but Puppet >>> Labs is proud to announce the 2.6.0 release! >>> >> >> Is anyone aware of an attempt to package up a complete (puppet + all >> prereqs) installer for Windows? Either official, or by someone in the >> community? >> >> And, asking from the other direction: would anyone else be interested in >> such a thing? >> >> I would be, because setting up puppet on Windows seems pretty tough >> right now. I also have no need for Ruby on my Windows boxes except >> for the usage of puppet. > > Rohan > > There isn't such an attempt so far - we've got it on the cards to do - > but any progress in that direction would be awesome. > > We've got some basic notes at: > > http://projects.puppetlabs.com/projects/puppet/wiki/Puppet_Windows > > Regards > > James Turnbull > > -- > Puppet Labs - http://www.puppetlabs.com > C: 503-734-8571 > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-us...@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-us...@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 on Windows (was Re: [Puppet Users] ANNOUNCE: Puppet 2.6.0 - Final release!)
Rohan McGovern wrote: > James Turnbull said: >> The journey was long and arduous and many fell along the way but Puppet >> Labs is proud to announce the 2.6.0 release! >> > > Is anyone aware of an attempt to package up a complete (puppet + all > prereqs) installer for Windows? Either official, or by someone in the > community? > > And, asking from the other direction: would anyone else be interested in > such a thing? > > I would be, because setting up puppet on Windows seems pretty tough > right now. I also have no need for Ruby on my Windows boxes except > for the usage of puppet. Rohan There isn't such an attempt so far - we've got it on the cards to do - but any progress in that direction would be awesome. We've got some basic notes at: http://projects.puppetlabs.com/projects/puppet/wiki/Puppet_Windows Regards James Turnbull -- Puppet Labs - http://www.puppetlabs.com C: 503-734-8571 -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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] ANNOUNCE: Puppet 2.6.0 - Final release!
James Turnbull said: > The journey was long and arduous and many fell along the way but Puppet > Labs is proud to announce the 2.6.0 release! > Is anyone aware of an attempt to package up a complete (puppet + all prereqs) installer for Windows? Either official, or by someone in the community? And, asking from the other direction: would anyone else be interested in such a thing? I would be, because setting up puppet on Windows seems pretty tough right now. I also have no need for Ruby on my Windows boxes except for the usage of puppet. -- Rohan McGovern QA Engineer Qt Development Frameworks, Nokia -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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] ANNOUNCE: Puppet 2.6.0 - Final release!
The journey was long and arduous and many fell along the way but Puppet
Labs is proud to announce the 2.6.0 release!
The 2.6.0 release is a major feature release and includes a huge variety
of new features, fixes, updates and enhancements. These include the
complete cut-over from XMLRPC to the REST API, numerous language
enhancements, a complete rewrite of the events and reporting system, an
internal Ruby DSL, a single binary, Windows support, a new HTTP report
processor, and a myriad of other enhancements.
We've included release notes below that you can also see at:
http://projects.puppetlabs.com/projects/puppet/wiki/Release_Notes
The release is available for download at:
http://puppetlabs.com/downloads/puppet/puppet-2.6.0.tar.gz
Please note that the release is signed with the new Puppet Labs key and
the signature is available at:
http://puppetlabs.com/downloads/puppet/puppet-2.6.0.tar.gz.sign
See the Verifying Puppet Downloads section at
http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet
Please report any feedback via the Puppet Labs Redmine site:
http://projects.puppetlabs.com
Please select an affected version of 2.6.0.
RELEASE NOTES
Language
Support for parameterised classes
The 2.6.0 release provides an extension to the existing class syntax to
allow parameters to be passed to classes. This brings classes more in
line with definitions, with the significant difference that definitions
have multiple instances whilst classes remain singletons.
To create a class with parameters you can now specify:
class apache($version) {
... class contents ...
}
Classes with parameters are NOT added using the include function but
rather the resulting class can then be included more like a definition:
node webserver {
class { apache: version => "1.3.13" }
}
Like definitions, you can also specify default parameter values in your
class like so:
class apache($version="1.3.13",$home="/var/www") {
... class contents ...
}
New relationship syntax
You can now specify relationships directly in the language:
File[/foo] -> Service[bar]
Specifies a normal dependency while:
File[/foo] ~> Service[bar]
Specifies a subscription.
You can also do relationship chaining, specifying multiple relationships
on a single line:
File[/foo] -> Package[baz] -> Service[bar]
Note that while it’s confusing, you don’t have to have all of the arrows
be the same direction:
File[/foo] -> Service[bar] <~ Package[baz]
This can provide some succinctness at the cost of readability.
You can also specify full resources, rather than just resource references:
file { "/foo": ensure => present } -> package { bar: ensure => installed }
But wait! There’s more! You can also specify a subscription on either
side of the relationship marker:
yumrepo { foo: }
package { bar: provider => yum, ... }
Yumrepo <| |> -> Package <| provider == yum |>
This, finally, provides easy many to many relationships in Puppet, but
it also opens the door to massive dependency cycles. This last feature
is a very powerful stick, and you can considerably hurt yourself with it.
Run Stages
Run Stages are a way for you to provide coarse-grained ordering in your
manifests without having to specify relationships to every resource you
want in a given order. It’s most useful for setup work that needs to be
done before the vast majority of your catalog even works – things like
configuring yum repositories so your package installs work.
Run Stages are currently (intentionally) a bit limited – you can only
put entire classes into a run stage, you can’t put individual resources
there.
There’s a main stage that resources all exist in by default; if you
don’t use run stages, everything’s in this, but it doesn’t matter to
you. You can define new stages via the new stage resource type:
stage { pre: before => Stage[main] }
Here we’ve used the before metaparameter but you could also use after,
require, etc to establish the necessary relationships between stages.
Now you just specify that your class belongs in your new run stage:
class yum { ... }
class redhat {
...
class { yum: stage => pre }
}
This will make sure that all of the resources in the yum are applied
before the main stage is applied.
Note that we’re using the new parameterized classes here – this is
necessary because of the class-level limitations of Run Stages. These
limitations are present because of the complication of trying to
untangle resource dependencies across stage boundaries if we allowed
arbitrary resources to specify stages.
On a related note, if you specify a stage for a given class, you should
specify as few as possible explicit relationships to or from that class.
Otherwise you risk a greater chance of dependency cycles.
This can all be visualized relatively easily using the —graph option to
puppetd and opening the graphs in OmniGraffle or GraphViz.
Specifying the ordering of Run Stages also works much better when
specified using the new relationship
