similar to: Run Puppet Against Master with Local node.pp Manifest?

Hi All, I am new to Puppet and I am wondering if there is a way to just apply a manifest one-time (present on the master, not included in site.pp) on an agent node without having to edit site.pp? It''s like I want to run a command on the agent that will do this for me. Something analogous to "puppet apply <manifest>" except that the manifest is not locally present on

Hi, I am new to the job and forum. I installed puppet and puppetmaster and set up my first dependencies acording to a manual that we have here in our company. Everything works fine and I can set up new nodes with several modules to choose from. Unfortunatley the Dashboard <http://forge.puppetlabs.com/puppetlabs/dashboard>gives me errors instead of starting correctley. Here the

Hi List, Puppet Version: v2.7.13 Question - If I correctly setup multiple manifestdir''s in the puppet.conf file how can I import a node pp file located in a different directory tree to site.pp? My configuration information is below. In my puppet.conf file I have setup an environment called "stable", within this environment I have setup the manifestdir, modulepath and

I''m trying to create a function that I can call in a manifest like this: $doc = doc(''apache::service'') In the function, I want it to actually find the filename for the ''apache::service'' class... from there, I''m going to run some code that will generate the puppet-doc in text format, and then return it in a variable. Ultimately this is so

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

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

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

Hi all, I have been working on a configuration of a Masterless configuration on Windows. I am able to get individual jobs to run like: puppet apply <path to my puppet .pp file> However, I would like to spin up the Vagrant box off a base VM, and have a puppet manifest file in a location where puppet knows to look and provision based off that file. The obvious place seems to be

*FROM:* http://projects.puppetlabs.com/projects/puppet/wiki/LDAP_Nodes """* NOTE: You can use node entries in your manifests together with LDAP nodes. External or LDAP nodes will be used before node entries. You cannot however use LDAP nodes and external nodes together. You must use one of these two types.* """ But, in *PRO PUPPET* page 127: """ *Note

Hy I m a new user in world puppet I have installed a packge test on a node "screen" without problem Now i want to try to uninstall it but without success. This is the file configuration this is my file init.pp package {"screen-4.0.3-16.el6": ensure=> "absent" } #package and purge its config files package {"screen-4.0.3-16.el6": ensure =>

I have the following in vagrantfile in WIndows system. config.vm.provision :puppet do |puppet| puppet.manifests_path = "manifests" puppet.manifest_file = "base-hadoop.pp" puppet.module_path = "modules" end when i run vagrant provision, i do see manifest and module folders are mounted and ssh into vm, I can find files in the following path

Hi, I''m running into some trouble when trying to access some variables which actually are a class parameter. The following works OK: node "common" { $var=''foo'' } node "gratia-base" inherits common { class { ''gratia'': dbhost => ''server.mysite.net'', } } node "node1"

I have a node that has some bad stored configs (namely the wrong ssh host keys) that I''m trying to clear out. Looking around it seems I''m supposed to do: puppet node clean foo.example.com However, that keeps bailing out because it''s trying to open a SQLite3 db where stored configs are normally kept, but my stored configs are kept in puppetdb (http://pastie.org/7814483

Hi, is site.pp a file must to have? I have set up a puppet server, but my following manifest just cannot apply to my client, the server itself. # cat haitest.pp file { ''/etc/motd'' : source => "puppet:///files/motd" ,} Thanks. Hai T. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this

Does anyone know why i would get a module error for my ''base'' module that I''m not even including for a node? I''m explicitly NOT include the ''base'', yet puppet-client-t2 still errors when i pull it in. Snips from both are below. Any ideas why this would happen? Thanks, JJ ==== site.pp file [root@puppet-master-t1 puppet]# cat

Dear puppet wizards, http://docs.puppetlabs.com/puppet/3/reference/lang_defined_types.html does not suggest to me that nested parametrized defines would be forbidden, hence I expected the following code to work: add_to_ssh_authorized_keys.pp: -------- define a::ssh_keys::add_to_ssh_authorized_keys($homebasedir="/home", $targetuser="root", $keyowner, $keyownername,

I''m a first time user that just installed Puppet 3.1.0 over the weekend and hit a road block that I can''t seem to get across. I have a Linux master (Mageia 2) and two Windows 7 clients. I was able to get basic recipes working by putting the resources directly in the node definitions. Now I''m trying to move to the next step and start using classes. I am *not*

I''m maintaining part of a rather large puppet config and at a loss to figure out where the following errors are coming from during a puppet update: err: Removing mount all: /var/lib/puppet/files/all does not exist or is not a directory err: Removing mount pixel: /var/lib/puppet/files/pixel does not exist or is not a directory err: Removing mount compute: /var/lib/puppet/files/compute

Hi all, I think i''m forgetting something. If i do: "puppet apply manifiests/site.pp" it works perfectly, loading modules i have include in site.pp file. site.pp: cat manifiests/site.pp node default { include ntp, motd } But it does not work if i run puppet agent. puppet agent --test --server=debianita.user.arinso --environment production Info: Retrieving plugin Info:

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