Re: [Puppet Users] Parameterized classes override of parameter
This is actually filed in Bug #5517 (Accepted) and a few others and has 10 votes. http://projects.puppetlabs.com/issues/5517 -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/T-tcPreqc10J. To post to this group, send email to puppet-users@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] Re: ssh authorized key problem in AIX
Haris,
On Jul 6, 7:19 am, "M.F.Haris" wrote:
> $sourcepath = $operatingsystem ? {
> AIX => "/etc/puppet/modules/userkeys/files/$pub_key.$username",
> default => "puppet:///SLES/$pub_key.${username}",
> }
Here, on the AIX path you tell it to copy the id_dsa.pub /from a local
file on the client/. You need to probably change that to 'puppet:///
modules/userkeys/$pub_key.$username' or 'puppet:///SLES/$pub_key.$
{username}' or similar and it should copy from the server.
There's a built in ssh_authorized_key type that would probably save
you a bunch of work.
http://docs.puppetlabs.com/references/stable/type.html#ssh_authorized_key
-Andrew
> ...
> ...
>
> file { "${home}/${username}/$sshDir/authorized_keys":
> ensure => "present",
> owner => $username,
> group => $group,
> mode => 600,
> require => File["${home}/${username}/${sshDir}"],
> #source => "puppet:///userkeys/files/${pub_key}.${username}",
> source => $sourcepath,
> }
>
> when i run this script on Linux nodes, it executes successfully and all
> users created with the their keys but on AIX the users are created but keys
> are not deployed there and i am getting this errr:
> *File[/home/xyz/.ssh/authorized_keys]/ensure:
> No specified sources exist*
>
> PS: Though I found a hack to copy the keys from server and deploy them on
> client nodes but i am still wondering why my AIX client is not able to
> retreive the sourcepath from server when my SLES clients are able to
> retrieve it.
>
> one more thing i am not creating any ssh key but actually copying it from
> hosted server to the clients.
>
> what am i doing wrong here? waiting for your response
>
> --
> haris
--
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] Re: Struggling with syntax
On Jul 26, 12:20 am, David Schmitt wrote:
>
> Write instead:
>
> file {
> "audit.rules":
> owner => "root",
> group => "root",
> mode => "600",
> path => $operatingsystem ? {
> default => "/etc/audit.rules",
> },
>
> }
>
> case $hardwaremodel {
> "x86_64": { File["audit.rules"] { source =>
> "puppet:///modules/audit/audit.rules.64" } },
> default: { File["audit.rules"] { source =>
> "puppet:///modules/audit/audit.rules.32" } },
>
> }
>
I have to say I don't like this at all. I think a far more clearer
definition would be like this:
file {
"audit.rules":
owner => "root",
group => "root",
mode => "600",
path => "/etc/audit.rules,
source => [
"puppet:///modules/audit/audit.rules.
$hardwaremodel",
"puppet:///modules/audit/audit.rules"
]
}
Then you just create a audit/files/audit.rules.x86_64 and anything
else will fall through to audit.rules.
> Best Regards, David
> --
> dasz.at OG Tel: +43 (0)664 2602670 Web:http://dasz.at
> Klosterneuburg UID: ATU64260999
>
> FB-Nr.: FN 309285 g FB-Gericht: LG Korneuburg
--
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] Re: Passenger Problems
On Oct 26, 1:00 pm, Taylor Leese wrote: > Patrick, > > Any idea if people are using versions > 2.2.5 in the wild > successfully? I tried to revert back to 2.2.2 previously, but I > received a number of compilation errors when running passenger-install- > apache2-module so it seems like moving up may be my only option. I am using 2.2.15 without issue on around 1000 nodes. -Andrew -- 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] Re: puppet dashboard performance issue
I also tried to look at this; since it was causing me issues as well. I had 800,000 rows or so in the reports table but I accidentally corrupted it (kill -9) so I won't have that many for a few more days. I created the separate indexex for kind and status but MySQL didn't use them. It uses indexes for everything except the report.status != failed and then it switches to a full table scan, even if the query is a simple select with only the where and no join. The documentation for MySQL indexes says that if MySQL thinks not using an index will be better it will not use indexes. mysql> explain select * from reports WHERE reports.status = 'failed'; *** 1. row *** id: 1 select_type: SIMPLE table: reports type: ref possible_keys: index_reports_on_status key: index_reports_on_status key_len: 258 ref: const rows: 274 Extra: Using where 1 row in set (0.00 sec) mysql> explain select * from reports WHERE reports.status != 'failed'; *** 1. row *** id: 1 select_type: SIMPLE table: reports type: ALL possible_keys: index_reports_on_status key: NULL key_len: NULL ref: NULL rows: 108828 Extra: Using where 1 row in set (0.00 sec) Presumably it's doing this because the number of rows that are != failed are the vast majority so a full table scan is actually faster. It looks like it's selecting all the reports, and then grouping so we get the latest one. Doing a cartesian join and then grouping seems extremely slow. I re-wrote the query to use a sub-select: select reports.*,nodes.* from nodes, (select node_id,max(time) from reports where reports.kind = 'apply' and reports.status != 'failed' GROUP by node_id) as reports WHERE reports.node_id = nodes.id; 1424 rows in set (0.12 sec). So you're only getting the latest report and then the nodes for each. How fast does that query run? -Andrew -- 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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: "Open Source Team" planning meeting summary
Writing this is groups.google.com's interface, pardon the formatting. Some bugs that have been causing us a bit of pain that I would really be happy if they actually got fixed: #3910 - Server is not authoritative over client environment when specified in an ENC This particular bug has been open for a year, and it's potentially dangerous bug (data disclosure, and indadvertantly deleting files). We'd like to see this one fixed since we can have about 20 environments going at a time and getting files from other environments is really quite annoying. At least it's gotten some attention in the past month or so. #5517 - behavior change within 2.6 makes it impossible to override class parameters of "included" parametrized classes This bug is almost singlehandedly preventing us from using parameterized classes. We honestly can't move to 2.7 (and the changes in scope) without this being fixed. Reason being, we cannot include a global class on all nodes that has settings for all nodes and then override the class with updated parameters to the class for a specific set of nodes. Parameterized classes, in theory are such a good idea, but the implementation and attention after the fact seems to be severely lacking. It seems to get pushed back every minor revision for some reason, but it would be great if it got fixed. Would be happy to provide use-cases or clarification if necessary. -Andrew -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/M0JJYjRLS2dnY2NK. To post to this group, send email to puppet-users@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] Re: Want to add AIX lpars as Puppet targets (clients)
I compiled my own Ruby (1.8.7p72), Facter (1.5.7), and my own Puppet in BFF format with GCC on AIX 5.3 TL 9 (won't work on earlier AIX). I can make these files available if you want, or I can supply you with the templates used in mkinstallp. Take a look at http://reductivelabs.com/trac/puppet/wiki/Puppet%20AIX. Out of the box, service management via SRC does not work, and package management does not work. Crontab doesn't work either (but is fixed in the unreleased 0.25.2). Check the puppet bug tracker or my github (http://github.com/ajf/puppet.git) for package and service plugins you can distribute with your recipes. -Andrew On Dec 1, 3:37 pm, JoeZ_aix wrote: > Can anyone point out some AIX specific downloads for Puppet AIX - > rpms, source, etc - also any docs??? > Thanks -- 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.
