similar to: using wildcards on node

Hello, I''m having difficulties to find documentation about the parameters that are used in the guests configuration files. For example, I don''t know what means the "extra", the "on_reboot", "on_crash", etc. Any help? Thanks. Pedro Simões _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com

Forgive me if this has been discussed already (and please point me i the correct direction) But I have been trying to find a way to classify nodes in site.pp via webserver*.domain.com. Any hints? -Jason

Ok, the file definition was missing. Now i''ve put that: ## services/ssh.pp class ssh { file { sshd_config: name => "/etc/ssh/sshd_config" } service { ssh: name => $operatingsystem ? { Debian => ssh, default => sshd }, ensure =>

Hello, I have two Vmware images, with 256MB of RAM memory each one, running puppetmasterd for the server and puppetd for the client. It''s normal that my puppetmasterd and puppetd occupies almost 10% of RAM memory each one? They aren''t doing anything especial, just listening on the ports. Thanks.

I''ve spent the last week or two poring over the documentation and setting up my first puppet environment, and while I''ve figured out how to do most of what I want to do with it, I have some questions that I haven''t been able to find answers for... * Can I match parts of a facter fact? In particular I have hostnames that include the environment as part of the

Hello, I want a simple operation in a puppet node like restarting the ssh service if it was stopped. My site.pp is simple as this: import "services/*" node default { include ssh } The services directory as a ssh.pp : class ssh { service { ssh: ensure => running, subscribe => File["/etc/ssh/sshd_config"] } } I''ve stopped the ssh service in the

Can you wildcard a domain for a node name like the following? node ''*.sub.example.com'' { .... } Thanks, Kent

Hello, How can I eliminate pending signing requests with puppetca?

Hi, When I run puppet agent --test --environment 42A, I have the following warning : Warning: Local environment: "42A" doesn''t match server specified node environment "production", switching agent to "production". ... The puppet manifest for the environment "42A" isn''t applied. The puppet version is 3.3.1-1puppetlabs1 on agent and

Hello, I'm trying to setup a PDC with Samba, but I have the known problem of the roaming profiles: big files. I think it's difficult to guarantee that a inexperienced user will copy is downloaded files, documents, or whatever, to a H:\ share instead of is handy desktop. Other problem is the files of Outlook or Thunderbird that can get big. The goal is to avoid email configuration each

Is it possible to define variable at this level. I need to pass the monit config file name ( sometimes its monitrc sometimes in not ). Here is what I have. # /etc/puppet/manifests/nodes.pp node basenode { include postgresql include monit include wiki include apace } node ''freebeerontuesdays.com'' inherits basenode { } -- You received this message because you are

Hello, Is it possible to configure an ENC to provide class definition to a number of nodes at the same time where a few other nodes are controlled in the site.pp by node ''FQDN'' {blah} for the same puppetmaster ? I am wondering once parameters are set for the master to look for an ENC based definitions, will it conflict with the site.pp node definitions ? For example these

Hello All, So I finally got around to start to cut over node definitions from standard flat files to external nodes (foreman), and getting error message: "Error 400 on SERVER: Could not find node ''nodename''; cannot compile" - So basically it can''t pick up the node from the external node config. When I test the fetching of the yaml file it seems to work

All, I am sure this is just something I am doing wrong, but I am trying to implement a node classifier (shell script) to have my nodes inherit the proper classes. However, when I run it I am not getting any classes except those that are defined in default. Rather than going into detail showing all of my configurations right off the bat, I have a question: I just stood up a

Hello folks, Im trying to migrate from static nodes-definition to external nodes definition. My script looks like this stolen from http://reductivelabs.com/trac/puppet/wiki/ExternalNodes: {{{ #!/usr/bin/perl -w use warnings; use YAML qw( Dump ); use Switch; #initialize vars our @classes; our %parameters; Function to fill @classes and %parameters with correct values .... print Dump( {

Hi, I have read this on the sourceforge site: Windows wildcards support for FLAC and Metaflac *Private: (?)<javascript:help_window('/help/tracker.php?helpname=private')> * No The Linux shell support wildcards but not the Windows shell. Would it be possible to add wildcard support for Windows? Example with Windows: metaflac --add-replay-gain *.flac Gives the following error:

I''m having some trouble with getting an ENC to work alongside site.pp: Even with a ''default'' node definition, and an ENC that only returns 0, regardless of input, consistently results in a ''cannot find node'' error. I''m wondering what I''ve missed here. I''ve tried to reduce everything to a ''base case'': and

I am working on a project that involves host names with now sequence to them. I would like my "node" hostnames in nodes.pp to point to a file with a list of these hostnames. Example: node {path/filename} { instead of the usual: node ''www1.example.com'' { or node /^www\d+$/ { Can this be done? Can anyone show my an example of how this was achieved? Thanks

Please can you send me some orientation? Many thanks in advance. Only if posible one book o similar example to understand why it is not what I try. El 8 jun. 2017 7:50 PM, "Pedro p?ramo" <percentil101 at gmail.com> escribi?: > Many thanks Jim. > > What I,m trying to show with the fhist plot is the empirical distribution > of the values of the left plot simulation.

I''m using the external_nodes functionality to read in a flat file of a node''s configuration. Currently said file is a straight yaml file (just to keep things simple). The place I''m currently stuck is in doing some more advance node configurations and placing that data in the yaml file. For example: node ''foo'' { $var1 =