Re: [Puppet Users] apt repository appears to have dependency issue with latest release (3.2.1)
Why are there two separate repos, especially when you are unable to install a package from main without the other? On May 25, 2013 11:52 AM, "Arnaud Gomes-do-Vale" wrote: > Eric Sorenson writes: > > > We'll do a better job in the future of > > (a) pointing out the necessity of the dependencies repo in the release > > notes > > (b) featuring the Upgrading guide ( > > http://docs.puppetlabs.com/guides/upgrading.html ) more prominently, > > as it has best practice for safe upgrading > > Maybe adding a line to the release announcement, something like > "WARNING, Debian users, you now need an additional dependencies repo to > install the puppet package" would have helped? > > I know "use the release package" is the proper way to set up apt, but it > is not available during install -- I was hit by the issue when doing a > fresh install on a new VM, with a preseed file that used to work. > > -- > Arnaud > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-users+unsubscr...@googlegroups.com. > To post to this group, send email to puppet-users@googlegroups.com. > Visit this group at http://groups.google.com/group/puppet-users?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] apt repository appears to have dependency issue with latest release (3.2.1)
Eric Sorenson writes: > We'll do a better job in the future of > (a) pointing out the necessity of the dependencies repo in the release > notes > (b) featuring the Upgrading guide ( > http://docs.puppetlabs.com/guides/upgrading.html ) more prominently, > as it has best practice for safe upgrading Maybe adding a line to the release announcement, something like "WARNING, Debian users, you now need an additional dependencies repo to install the puppet package" would have helped? I know "use the release package" is the proper way to set up apt, but it is not available during install -- I was hit by the issue when doing a fresh install on a new VM, with a preseed file that used to work. -- Arnaud -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] PuppetDB 1.3/ HSQLDB vs Postgres
Hi everyone; I was just wondering if anyone has any opinion/information on the pros and cons of using the built-in HSQLDB vs Postgres. Thanks! Bee -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Puppet/Nagios/PuppetDB slow performance
On 2013-05-25 10:11, Alexander Bien wrote: On 24.05.2013 16:58, Ken Barber wrote: Its probably the nagios resource, its well known for not scaling when the files contain a lot of entries. That would explain why your PuppetDB is showing low load - as its probably not the bottleneck. I second that. We have mysql storeconfigs, about 5000 Services, 2,5 MB nagios_* files and >50k lines of config. The puppet run takes aprox 45 minutes. I have heard people on irc say that its not uncommon. You can cut quite a bit off that time by using templates and files (one per service/host) and purging on the base directory. Regards, David -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Puppet/Nagios/PuppetDB slow performance
On 24.05.2013 16:58, Ken Barber wrote: Its probably the nagios resource, its well known for not scaling when the files contain a lot of entries. That would explain why your PuppetDB is showing low load - as its probably not the bottleneck. I second that. We have mysql storeconfigs, about 5000 Services, 2,5 MB nagios_* files and >50k lines of config. The puppet run takes aprox 45 minutes. I have heard people on irc say that its not uncommon. - alex -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: "Future" parser and "return value" of resource definition
Also, this is accepted :
collect([1,2,3]) |$x| {
file { "/tmp/b$x":
content => collect([1,2,3]) |$y| { $y };
}
}
and this isn't :
collect([1,2,3]) |$x| {
file { "/tmp/b$x":
content => collect([1,2,3]) |$y| { $y + 0 };
}
}
Error: Failed to apply catalog: Parameter content failed on File[/tmp/b2]:
Munging failed for value 1 in class content: can't convert Fixnum into
String at /etc/puppet/manifests/site.pp:4
but this is :
each([1,2,3]) |$x| {
file { "/tmp/ab$x":
content => each([1,2,3]) |$y| { $y + 1 };
}
}
It also seems that "collect" isn't too useful compared to "each" :
* you can use collect everywhere you would use collect
* "each" seems to return the original collection unchanged
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
