[Puppet Users] Re: facter variables empty
I found it : http://projects.puppetlabs.com/issues/8342 I switch to passenger and it works now. Thanks you On 5 oct, 23:41, Denmat tu2bg...@gmail.com wrote: Hi, sounds like it could be a similar issue of puppet with mongrel. This was raised recently on the list. Have a look at those. Also paste the code you are trying to apply so we can see what you're attempting to do. Here is a link that you can use to see some tips on debugging issues.http://www.devco.net/archives/2009/08/19/tips_and_tricks_for_puppet_d... Cheers, Den -- 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: Hostname fact doesn't handle hostnames with periods
I've had issues like this in a previous life (I was a founder of Tideway Systems and we put a lot of effort into finding info from the runtime environment and reasoning about what the returned info meant). IMO, you've got to be clear what the underlying information model that puppet / facter supports is. In particular, if you simply say that the facts are the data reported by the underlying tools, then you've got zero abstraction of the model and it's 'an exercise for the user to handle the differences between platforms. Alternatively, you can define a canonical ontology and how the different tools map onto that ontology. Even with such an ontology, you probably need to include platform specific types in the data model. It is usually useful to separate out the data returned from interrogation from how facter has interpreted it. Not least for debugging and provenance purposes. fwiw, I'm also a big fan of encouraging best practice in the use of the tools, so in this instance, the teaching/documentation would show how to avoid naming pitfalls introduced by differences in standards and how to remediate an environment that's fallen into such a trap. Otherwise, the tools get bogged down in handling nasty inconsistencies, which are impossible to cope with cleanly in code as they depend on implicit or explicit customer organisational policies - and the tool gets blamed for any shortfalls, while the organisation keeps digging itself deeper into the trap. -- 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.
Re: [Puppet Users] Re: Hostname fact doesn't handle hostnames with periods
I've had issues like this in a previous life (I was a founder of Tideway Systems and we put a lot of effort into finding info from the runtime environment and reasoning about what the returned info meant). IMO, you've got to be clear what the underlying information model that puppet / facter supports is. In particular, if you simply say that the facts are the data reported by the underlying tools, then you've got zero abstraction of the model and it's 'an exercise for the user to handle the differences between platforms. Alternatively, you can define a canonical ontology and how the different tools map onto that ontology. Even with such an ontology, you probably need to include platform specific types in the data model. So in this proposal we have 'hostname' which is defined as the shortname, and 'uname_nodename' which is the data derived from the system. One is cross-platform, the other is specific to POSIX systems with the uname data available. So if we created 'uname_nodename' this could be used internally be the 'hostname' fact if on a POSIX system that supports it. In OWL ontological terms this is not a 'owl:sameAs' but a derived relationship of some kind (?). It is usually useful to separate out the data returned from interrogation from how facter has interpreted it. Not least for debugging and provenance purposes. Indeed. At the moment all facts are equal. I hope in the future name spacing can logically separate facts out - but I'm not sure enough metadata can be gleaned from namespaces - something to think about. I agree though - there is value in the separation. not only to solve the problem users are having here - but from a reporting/debugging perspective you can see more clearly what the system is really set to - not just how facter interprets it. In fact there is a similar discussion for proper reporting for the operatingsystem fact for windows: http://projects.puppetlabs.com/issues/7643 http://projects.puppetlabs.com/issues/7621 In #7643 we talk about exposing all the Win32_OperatingSystem WMI/CIM class vars ... and in #7621 we would simply use those for the operatingsystem fact on windows. Real value/contrived value layers has its value. fwiw, I'm also a big fan of encouraging best practice in the use of the tools, so in this instance, the teaching/documentation would show how to avoid naming pitfalls introduced by differences in standards and how to remediate an environment that's fallen into such a trap. Otherwise, the tools get bogged down in handling nasty inconsistencies, which are impossible to cope with cleanly in code as they depend on implicit or explicit customer organisational policies - and the tool gets blamed for any shortfalls, while the organisation keeps digging itself deeper into the trap. It seems to me that most people have set the hostname to be the fqdn. And in a way (for right or wrong) this has become a pseudo-expectation. Not just for Puppet but for other things. I have worked with Doug and Dexter in places where they have done this - and have found myself working around issues in other places at times. Thanks for your informed input :-). ken. -- 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] perltidy workalike to tidy up Puppet manifests
There's a wonderful tool called perltidy that can clean up Perl
scripts, enforcing certain style guidelines by default but allowing
lots of customization.
Does Puppet have a tool like perltidy to enforce a certain style in
Puppet manifests? I don't see any mention of such a tool at
http://docs.puppetlabs.com/guides/style_guide
Thanks,
Phil
p.s. Below is an example of perltidy in action, but there are more at
http://perltidy.sourceforge.net . Various configuration options such
as Cuddled Else, Define Horizontal Tightness, etc. are explained
at http://perltidy.sourceforge.net/stylekey.html
[pdurbin@beamish bin]$ cat print_binary_numbers.pl
#!/usr/bin/perl
use strict; use warnings;
use Time::HiRes qw( sleep ) ;
for (my $i = 0; $i 10; $i++ )
{
sleep .1 ;
printf (%10b %3d\n, $i,
$i);
}
[pdurbin@beamish bin]$ perltidy print_binary_numbers.pl
[pdurbin@beamish bin]$ cat print_binary_numbers.pl.tdy
#!/usr/bin/perl
use strict;
use warnings;
use Time::HiRes qw( sleep );
for ( my $i = 0 ; $i 10 ; $i++ ) {
sleep .1;
printf( %10b %3d\n, $i, $i );
}
[pdurbin@beamish bin]$
--
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: Problem: Puppet under Passenger.
Thanks for your suggestion, Devon. I tried uncommenting that line in
config.ru and restarting httpd, but continue to get the same error. I
did verify that the libs are in the proper location.
[root@server ~]# stat /opt/puppet/lib/puppet.rb
File: `/opt/puppet/lib/puppet.rb'
Size: 3773Blocks: 8 IO Block: 4096 regular
file
Device: 805h/2053d Inode: 42600516Links: 1
Access: (0664/-rw-rw-r--) Uid: ( 501/ puppet) Gid: ( 502/
puppet)
Access: 2011-09-21 15:56:12.0 -0400
Modify: 2011-08-06 15:27:03.0 -0400
Change: 2011-10-06 10:28:53.0 -0400
Any other ideas?
On Oct 5, 1:24 pm, devon devon.pet...@gmail.com wrote:
- Installed Puppet and Facter from the latest tarballs.
- Installed Ruby 1.9.2 and rack/passenger gems from RVM.
If you installed puppet via tarball, and ruby/rack/passenger via RVM
it could be that puppet isn't in the RUBYLIB. You may need to edit
the config.ru to specify where puppet is - the config.ru has a
commented section with the following, which you may need to uncomment:
# if puppet is not in your RUBYLIB:
# $:.unshift('/opt/puppet/lib')
--
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.
Re: [Puppet Users] perltidy workalike to tidy up Puppet manifests
On Oct 6, 2011, at 7:19 AM, Philip Durbin wrote: There's a wonderful tool called perltidy that can clean up Perl scripts, enforcing certain style guidelines by default but allowing lots of customization. Does Puppet have a tool like perltidy to enforce a certain style in Puppet manifests? I don't see any mention of such a tool at http://docs.puppetlabs.com/guides/style_guide not the same but certainly in the neighborhood... https://github.com/rodjek/puppet-lint/ Craig -- 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.
Re: [Puppet Users] perltidy workalike to tidy up Puppet manifests
On Thu, Oct 6, 2011 at 11:00 AM, Craig White craig.wh...@ttiltd.com wrote: On Oct 6, 2011, at 7:19 AM, Philip Durbin wrote: There's a wonderful tool called perltidy that can clean up Perl scripts, enforcing certain style guidelines by default but allowing lots of customization. Does Puppet have a tool like perltidy to enforce a certain style in Puppet manifests? I don't see any mention of such a tool at http://docs.puppetlabs.com/guides/style_guide not the same but certainly in the neighborhood... https://github.com/rodjek/puppet-lint/ Ah, unlike perltidy, puppet-lint doesn't re-write your code. It's a reporting tool, so you are left to go and make the recommended changes yourself. That said, puppet-lint is *very* useful and I could see it being a great help in detecting ugly Puppet code. It's a huge step up from simply using `puppet --parseonly` to check the syntax. Also, within minutes of me opening an issue, the developer (Tim Sharpe) replied, which is a great sign. Thanks! Phil -- 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] Feature 4815: Allow Mount to create a mount point and set the under lying permission?
Having this feature would be very useful to me... Other than doing the work myself, is there any hope of getting this any time soon? -- Jeff Ollie -- 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.
Re: [Puppet Users] Feature 4815: Allow Mount to create a mount point and set the under lying permission?
On 6 October 2011 18:15, Jeffrey Ollie j...@ocjtech.us wrote: Having this feature would be very useful to me... Other than doing the work myself, is there any hope of getting this any time soon? -- Jeff Ollie This doesn't really seem the work of a provider, but rather a define. Could you not just wrap a file block and a mount inside a define? -- 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] More changes on yum.puppetlabs.com
Greetings, I'd like to remove the cruft (no longer maintained) areas of yum.puppetlabs.com. I fear they only cause confusion and offer less-than-desirable experience for our users. I'd like to remove /base /prosvc /porsvc.unsigned /SRMS /sources I'd like to do this some time next week. The stuff mostly found in base is available elsewhere and signed properly. The prosvc stuff has been largely unmaintained. The /SRPMS folder is now broken out into each distribution area, so this high-level directory isn't needed. The /sources directory contains a very incomplete listing of source. We have that available either via SRPMS or at downloads.puppetlabs.com This will basically keep: /el (stuff for RHEL, CentOS, Scientific, Oracle Linux etc) /fedora For specific feedback on this change, you can update http://projects.puppetlabs.com/issues/8473 or you can reply to this thread. NOTE: There's been some discussion about other package platforms, Debian/Ubuntu, Solaris, etc. There are plans to begin working on making those packages readily available (working with the community), however it's time permitting still. Mike -- 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: Puppet 2.7 allows dash in variable names: bug or feature?
perhaps you should enclose the variables in quotes to something like
this:
http://${yumserver}/repos/vmware-${esxversion-rhel6-64};
On Oct 5, 8:46 pm, Steve Snodgrass phe...@gmail.com wrote:
While testing puppet 2.7, I found that one of my manifests broke
because of the following quoted string:
http://$yumserver/repos/vmware-$esxversion-rhel6-64;
Everything in the resulting string after vmware- was blank. After
some experiments I found that puppet 2.7 allows dashes in variable
names, and was interpreting $esxversion-rhel6-64 as one big
variable. Of course adding curly braces fixes the problem, but that
seems like a significant change. Was it intended?
Results of applying a simple test manifest:
notice(Dashtest: $fqdn-is-my-hostname)
Puppet 2.6.11:
notice: Scope(Class[main]): Dashtest: foobar.example.com-is-my-
hostname
Puppet 2.7.5:
notice: Scope(Class[main]): Dashtest:
-Steve
--
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] Applying policy based on network address
Hi all, I'm trying to wrap my brain around this one and could use a little help/guidance. I have need to deploy software based on the network a system is in. Has anyone had need or been able to do the following?: (Pseudo code) If 123.123.123.123 is in 123.123.123.0/24 or 234.234.234.234.0/24 (list/array of networks it could belong to) then ensure package is present. -or- If 123.123.123.123 is in 123.123.123.0/255.255.255.0 then ensure package is present. Yes I suppose a case statement would work better. Now I know from Facter I have the following _easily_ at my disposal: ipaddress and netmask. As easy as it would be to use the network_eth0 to get what network the host is in I'm a little hesitant to go down that route since I can't rely on the eth0 part network_eth0 being consistent. Fedora 15, for example, is using a new naming convention for their Ethernet interfaces. Mine is em1. I suppose I could figure out the eth0/em1 part by using the ipaddress and interfaces fact and use it to figure out the network_eth0/em1 and that would give me the network address. But this just seems like really too much freakin' work. Anyone have anything simple and elegant? Is there some glaring feature of puppet/facter that I've overlooked that says ...Duh! As always any help in advance is appreciated, Kris -- 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.
Re: [Puppet Users] Re: I can't seem to create mountpoint and change permissions after mounting in 2.7.3
I haven't used them yet, but isn't this what stages are meant to facilitate? http://docs.puppetlabs.com/references/stable/metaparameter.html#stage -- 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] Puppet installation
Hi Folks, I am trying a non-standard installation of puppet. I have root privileges during installation how ever I will not have root privileges during run time. I wish to exercise more control over puppet master / slave during run time. For the default yum based installation, the various important configuration points to locations which require sudo privilege for changes. 1. /etc/puppet/puppet.conf 2. /etc/puppet/manifests/site.pp etc Is it possible to move / relocate these configurations to a folder where I could give a normal user privilege to edit them? Is there documentation for how to install in such non-standard way? Thanks, Ashish -- 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: Problem: Puppet under Passenger.
Correction. I'm not sure what config.ru I changed but it obviously
wasn't the right one. Now I'm getting errors about not being able to
load Facter but I'm pretty sure I can sort it out from here. Thanks
for your help Devon.
On Oct 6, 10:40 am, William wsti...@gmail.com wrote:
Thanks for your suggestion, Devon. I tried uncommenting that line in
config.ru and restarting httpd, but continue to get the same error. I
did verify that the libs are in the proper location.
[root@server ~]# stat /opt/puppet/lib/puppet.rb
File: `/opt/puppet/lib/puppet.rb'
Size: 3773 Blocks: 8 IO Block: 4096 regular
file
Device: 805h/2053d Inode: 42600516 Links: 1
Access: (0664/-rw-rw-r--) Uid: ( 501/ puppet) Gid: ( 502/
puppet)
Access: 2011-09-21 15:56:12.0 -0400
Modify: 2011-08-06 15:27:03.0 -0400
Change: 2011-10-06 10:28:53.0 -0400
Any other ideas?
On Oct 5, 1:24 pm, devon devon.pet...@gmail.com wrote:
- Installed Puppet and Facter from the latest tarballs.
- Installed Ruby 1.9.2 and rack/passenger gems from RVM.
If you installed puppet via tarball, and ruby/rack/passenger via RVM
it could be that puppet isn't in the RUBYLIB. You may need to edit
the config.ru to specify where puppet is - the config.ru has a
commented section with the following, which you may need to uncomment:
# if puppet is not in your RUBYLIB:
# $:.unshift('/opt/puppet/lib')
--
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.
Re: [Puppet Users] Applying policy based on network address
On Oct 5, 2011, at 7:38 PM, CZACHOR, KRISTOPHER wrote:
Hi all,
I’m trying to wrap my brain around this one and could use a little
help/guidance. I have need to deploy software based on the network a system
is in.
Has anyone had need or been able to do the following?:
(Pseudo code)
If 123.123.123.123 is in 123.123.123.0/24 or 234.234.234.234.0/24
(list/array of networks it could belong to) then ensure package is present.
-or-
If 123.123.123.123 is in 123.123.123.0/255.255.255.0 then ensure package is
present.
Yes I suppose a case statement would work better.
Now I know from Facter I have the following _easily_ at my disposal:
ipaddress and netmask. As easy as it would be to use the network_eth0 to get
what network the host is in I’m a little hesitant to go down that route since
I can’t rely on the eth0 part network_eth0 being consistent. Fedora 15, for
example, is using a new naming convention for their Ethernet interfaces. Mine
is em1. I suppose I could figure out the eth0/em1 part by using the ipaddress
and interfaces fact and use it to figure out the network_eth0/em1 and that
would give me the network address. But this just seems like really too much
freakin’ work.
Anyone have anything simple and elegant? Is there some glaring feature of
puppet/facter that I’ve overlooked that says …”Duh!”
As always any help in advance is appreciated,
create a custom fact...
Facter.add(datacenter) do
setcode do
datacenter = unknown
# Get current ip address from Facter's own database
ipaddr = Facter.value(:ipaddress)
# A data center
if ipaddr.match(^10\.3\.)
datacenter = A
# C data center
elsif ipaddr.match(^10\.1\.)
datacenter = C
# D data center
elsif ipaddr.match(^10\.0\.)
datacenter = D
# E data center
elsif ipaddr.match(^10\.2\.)
datacenter = E
# F data center
elsif ipaddr.match(^10\.10\.)
datacenter = F
end
datacenter
end
end
deploy based on custom fact...
case $datacenter {
default: {
$ldap_servers = ldap://ldap2.example.com ldap://ldap1.example.com;
}
A: {
$ldap_servers = ldap://ldap1.example.com ldap://ldap2.example.com;
}
B: {
$ldap_servers = ldap://ldap1.example.com ldap://ldap2.example.com;
}
Craig
--
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: Problem: Puppet under Passenger.
IIRC there are issues with Puppet and Ruby 1.9.2 specifically with
ssl. You could be running into something like this,
http://groups.google.com/group/puppet-users/browse_thread/thread/fa49f1b9b36ceac6/72bf694d4e2f3012
However if you're planning to run this instance in production I'd use
Ruby 1.8.7.
Ramin
On Oct 6, 10:44 am, William wsti...@gmail.com wrote:
Correction. I'm not sure what config.ru I changed but it obviously
wasn't the right one. Now I'm getting errors about not being able to
load Facter but I'm pretty sure I can sort it out from here. Thanks
for your help Devon.
On Oct 6, 10:40 am, William wsti...@gmail.com wrote:
Thanks for your suggestion, Devon. I tried uncommenting that line in
config.ru and restarting httpd, but continue to get the same error. I
did verify that the libs are in the proper location.
[root@server ~]# stat /opt/puppet/lib/puppet.rb
File: `/opt/puppet/lib/puppet.rb'
Size: 3773 Blocks: 8 IO Block: 4096 regular
file
Device: 805h/2053d Inode: 42600516 Links: 1
Access: (0664/-rw-rw-r--) Uid: ( 501/ puppet) Gid: ( 502/
puppet)
Access: 2011-09-21 15:56:12.0 -0400
Modify: 2011-08-06 15:27:03.0 -0400
Change: 2011-10-06 10:28:53.0 -0400
Any other ideas?
On Oct 5, 1:24 pm, devon devon.pet...@gmail.com wrote:
- Installed Puppet and Facter from the latest tarballs.
- Installed Ruby 1.9.2 and rack/passenger gems from RVM.
If you installed puppet via tarball, and ruby/rack/passenger via RVM
it could be that puppet isn't in the RUBYLIB. You may need to edit
the config.ru to specify where puppet is - the config.ru has a
commented section with the following, which you may need to uncomment:
# if puppet is not in your RUBYLIB:
# $:.unshift('/opt/puppet/lib')
--
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: Problems with exported resources after upgrade to 2.7.5
This is definitely busted for me too. I think it's just broken when
custom defines are exported, as exported classes seem to be working OK
(witness nagios::service for example).
Any word on a fix?
Thanks,
Robin
On Oct 3, 7:51 am, Greg Sutcliffe greg.sutcli...@gmail.com wrote:
Hi all,
I use a number of exported resources, some of which are exported custom
definitions.Since
upgrading to 2.7.5, I've seen an issue which is driving me up the wall
trying to debug it. Hopefully
someone can help :)
Consider the following three snippets of code:
*$modulepath/ntp/manifests/ntp_register.pp:*
define basics::ntp_register ($content=, $order=10) {
concat::fragment{ntp_conf_$name:
target = /etc/ntp.conf,
content = $content,
order = $order
}
}
$modulepath/servers/manifests/ntp_server.pp
class servers::ntp_server {
@@basics::ntp_register { Server Ntp $domain: content = stuff here\n }
}
*$modulepath/servers/manifests/ntp_client.pp*
class servers::ntp {
Basics::Ntp_register | title == Server Ntp $domain |
}
So we have a defined resource, an export of that resource, and a collection
of it. In 2.7.3, this worked fine,
however, in 2.7.4 and 2.7.5 I get
err: Could not retrieve catalog from remote server: Error 400 on SERVER:
Could not find type
Basics::Ntp_register on node client.foo.bar
I'm not sure what's changed that's causing this. I've read some stuff about
loading order, but they seem
to be old bugs that were fixed ages ago. I can see that rewriting this as a
local definition containing an
exported resource might work, but I'd rather understand what's wrong with my
approach first.
Thanks in advance,
Greg
--
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.
Re: [Puppet Users] Feature 4815: Allow Mount to create a mount point and set the under lying permission?
On Thu, Oct 6, 2011 at 12:17 PM, Adam Gibbins a...@adamgibbins.com wrote: On 6 October 2011 18:15, Jeffrey Ollie j...@ocjtech.us wrote: Having this feature would be very useful to me... Other than doing the work myself, is there any hope of getting this any time soon? This doesn't really seem the work of a provider, but rather a define. Could you not just wrap a file block and a mount inside a define? I think that the problem with that is that you are dealing with two different directories that have the same name. There's the original directory that is used as a mount point and then there's the directory that is mounted on top of that. AFAIK puppet can't deal with that situation using only a define. -- Jeff Ollie -- 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.
Re: [Puppet Users] Re: Problems with exported resources after upgrade to 2.7.5
On Thu, Oct 6, 2011 at 11:50 AM, Rob Walsh rob.wa...@gmail.com wrote: This is definitely busted for me too. I think it's just broken when custom defines are exported, as exported classes seem to be working OK (witness nagios::service for example). Any word on a fix? Anecdotes have piled up to become data, and we're looking at it now. -- Nigel Kersten Product Manager, Puppet Labs -- 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.
Re: [Puppet Users] Re: Problems with exported resources after upgrade to 2.7.5
On Thu, Oct 6, 2011 at 16:01, Nigel Kersten ni...@puppetlabs.com wrote: On Thu, Oct 6, 2011 at 11:50 AM, Rob Walsh rob.wa...@gmail.com wrote: This is definitely busted for me too. I think it's just broken when custom defines are exported, as exported classes seem to be working OK (witness nagios::service for example). Any word on a fix? Anecdotes have piled up to become data, and we're looking at it now. It would be helpful if folks hit by this could let me know: * what DBMS are you using? * what version of ActiveRecord is in use? Also, if possible, a query that tries to collect something that is being missed would be useful. That should be selecting from resources where type = 'File' and a few other criteria. Daniel -- ⎋ Puppet Labs Developer – http://puppetlabs.com ♲ Made with 100 percent post-consumer electrons -- 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.
Re: [Puppet Users] Puppet installation
You may want to have a look at the output of puppet --genconfig to see what paths are being used by default. At least with 2.7.3, if you run puppet --genconfig as a non-root user, puppet generates a configuration to put itself in $HOME/.puppet instead of the system defaults. If you're running puppet without root privileges, unless you're planning on multiple users doing ad hoc management you might as well install to a homedir. Installing through yum won't buy you much, IMHO. On Thu, Oct 6, 2011 at 10:36 AM, Ashish ashishrv@gmail.com wrote: Hi Folks, I am trying a non-standard installation of puppet. I have root privileges during installation how ever I will not have root privileges during run time. I wish to exercise more control over puppet master / slave during run time. For the default yum based installation, the various important configuration points to locations which require sudo privilege for changes. 1. /etc/puppet/puppet.conf 2. /etc/puppet/manifests/site.pp etc Is it possible to move / relocate these configurations to a folder where I could give a normal user privilege to edit them? Is there documentation for how to install in such non-standard way? Thanks, Ashish -- 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. -- 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.
Re: [Puppet Users] Trigger when on any package change
Run once after everything is the desirable result if any packages have been added, removed, or updated. -- 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/-/fQBe3hsJ648J. 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.
Re: [Puppet Users] Feature 4815: Allow Mount to create a mount point and set the under lying permission?
On Thu, Oct 06, 2011 at 03:00:29PM -0500, Jeffrey Ollie wrote:
On Thu, Oct 6, 2011 at 12:17 PM, Adam Gibbins a...@adamgibbins.com wrote:
On 6 October 2011 18:15, Jeffrey Ollie j...@ocjtech.us wrote:
Having this feature would be very useful to me... Other than doing
the work myself, is there any hope of getting this any time soon?
This doesn't really seem the work of a provider, but rather a define.
Could you not just wrap a file block and a mount inside a define?
I think that the problem with that is that you are dealing with two
different directories that have the same name. There's the original
directory that is used as a mount point and then there's the directory
that is mounted on top of that. AFAIK puppet can't deal with that
situation using only a define.
You could create the mountpoint with an exec resource. Like
define mymount (.) {
exec { create_${name}:
command = /bin/mkdir -m 0755 ${name},
creates = $name,
}
mount { $name:
...
require = Exec[create_${name}],
}
}
You can now use a file resource to set e.g. owner and group on the
mounted path.
-Stefan
pgptbHE4L8lh6.pgp
Description: PGP signature
Re: [Puppet Users] Re: I can't seem to create mountpoint and change permissions after mounting in 2.7.3
Not really On Wed, Oct 5, 2011 at 8:54 PM, Chris McDermott csmcderm...@gmail.comwrote: I haven't used them yet, but isn't this what stages are meant to facilitate? http://docs.puppetlabs.com/references/stable/metaparameter.html#stage -- 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. -- 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.
