[Puppet Users] Can we lookup hiera data object providing the file name

[Malintha Adikari]

I am using hiera lookup as follows in my puppet template

<%- nodeinfo = scope.function_hiera(['nodes']) -%>

I have provided the .yaml file which includes above 'nodes' object in my 
hiera.yaml file ( that is inside nodesfile.yaml file which is dynamically 
loaded as follows)

---
:backends:
  - yaml
:yaml:
  :datadir: /etc/puppet/hieradata
:hierarchy:
  - "%{::nodes_file}
  

I have want to load another data object into my puppet template but the 
problem is that data object is in a .yaml file which is not registered in 
my hiera.yaml file. I cannot register that file in my hiera.yaml. 

Is there anyway to load data object providing the file along with the 
lookup method. I do know the .yaml file name that object is in ?

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/7ef14a02-bf2a-465c-9410-2429e59b6f3c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Puppet 3.8.3 available

[Hailee Kenney]

Puppet 3.8.3 is a bug fix release in the Puppet 3.8 series. It fixes one
significant regression and several miscellaneous bugs.

Check out the release notes for more information:
https://docs.puppetlabs.com/puppet/3.8/reference/release_notes.html#puppet-383

You can see a full list of JIRA tickets for the release here:
https://tickets.puppetlabs.com/browse/PUP-5218?filter=15509

If you're installing Puppet for the first time, follow the Installation
Guide:
https://docs.puppetlabs.com/guides/install_puppet/pre_install.html

-- 
Hailee Kenney
hai...@puppetlabs.com
Software Developer, Puppet Labs

*PuppetConf 2015  is right around the corner!
Join us October 5-9 in Portland, OR. Register now
.*

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CALdYGa8U%3DBN06scdt834ri3HFtwFqLrepX-2QuLSPMcDq6HzVQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Anyone successfully use mcollective shell plugin with RHEL 5 & 6?

[Christopher Wood]

I needed slightly different behaviour from some of the puppetca plugin actions 
and opted to rewrite those portions. In your situation I would probably do the 
same thing given the irritation value of managing multiple rubies.

I found the initial learning curve for mcollective plugins steep in comparison 
to things like SOAP and REST, but it flattened very quickly thereafter. (Usual 
disclaimer: I am not a programmer. YMMV.)

On Tue, Sep 22, 2015 at 09:54:24AM -0500, Kenton Brede wrote:
>The title pretty much says it all.  I mostly manage RHEL 5 & 6 boxes that
>come with ruby 1.8.7.  The mcollective shell plugin requires ruby 1.9.
> 
>SCL might work for the RHEL 6 systems but not 5.  Building everything from
>source would work but certainly not ideal.  I took a stab at managing ruby
>with rbenv yesterday and didn't manage to get the shell plugin to work.
> 
>Any thoughts appreciated.
> 
>Thanks,
>--
>Kent Brede
> 
>--
>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 [1]puppet-users+unsubscr...@googlegroups.com.
>To view this discussion on the web visit
>
> [2]https://groups.google.com/d/msgid/puppet-users/CA%2BnSE3_W2Ma8X-mNWTaZcmoOY0aJT8JrJ_DXKhCy2bdJGvCAYg%40mail.gmail.com.
>For more options, visit [3]https://groups.google.com/d/optout.
> 
> References
> 
>Visible links
>1. mailto:puppet-users+unsubscr...@googlegroups.com
>2. 
> https://groups.google.com/d/msgid/puppet-users/CA%2BnSE3_W2Ma8X-mNWTaZcmoOY0aJT8JrJ_DXKhCy2bdJGvCAYg%40mail.gmail.com?utm_medium=email&utm_source=footer
>3. https://groups.google.com/d/optout

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/20150922194203.GA12715%40iniquitous.heresiarch.ca.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Status of activemq

[Kenton Brede]

I'm wondering the same thing here.

Kent

On Wed, Jul 22, 2015 at 6:28 PM, Ellison Marks  wrote:

> So, I'm going through the dance of upgrading to puppet 4.2 from 3.8 on
> CentOS 6, and I've run into a few things that brought up some questions.
> During the install, I ran into a number of collisions and incompatibilities
> between pc1 and the existing packages, but pertinent to this issue, I had
> to uninstall the old puppetlabs-release package in favor of the pc1 release
> package, as they were both claiming ownership of the signing key. It's
> mostly worked out, however, now I'm at the point where I'm working on
> migrating mcollective. Aside from some hiccups with involving
> incompatibilities with the new facter, I've got things talking to each
> other. Now though, I'm wondering about activemq. I've still got the version
> I had installed from the puppetlabs-deps repo, and it's working, I'm just
> not sure where I'm supposed to get updates at this point.
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/16492e87-eb64-45a1-9dc5-6d861560fafd%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Kent Brede

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CA%2BnSE39RGuhWuUzcwdbq%2BNTYSZ7PdcVvURY2jzGqBC%3DJ_vmf%3Dw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Anyone successfully use mcollective shell plugin with RHEL 5 & 6?

[Ellison Marks]

I'm in a similar situation. I haven't tried it yet, but it might work with 
the new AIO packages, since they vendor a newer ruby version, 
2.1.something, IIRC.

On Tuesday, September 22, 2015 at 7:54:39 AM UTC-7, kbrede wrote:
>
>
> The title pretty much says it all.  I mostly manage RHEL 5 & 6 boxes that 
> come with ruby 1.8.7.  The mcollective shell plugin requires ruby 1.9.
>
> SCL might work for the RHEL 6 systems but not 5.  Building everything from 
> source would work but certainly not ideal.  I took a stab at managing ruby 
> with rbenv yesterday and didn't manage to get the shell plugin to work.
>
> Any thoughts appreciated.
>
> Thanks,
>
> -- 
> Kent Brede
>
>
>
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/5d6cbdf2-e1a8-43fa-a942-afc9c49c3fbc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] could not add registry class after installed registry module

[Yingbo Li]

I am new to puppet. I am trying the quick start with version 2015.2. The 
puppet master is on CentOS7. I have setup a windows 7 agent. Connection has 
no problem. I am following the instructions bellows:

Add the registry Class to the Example Group 

 
*To add the* registry *class to the example group*:

   1. From the console, click *Nodes* > *Classification*.
   2. Select the *windows_example* group.
   3. Click the *Classes* tab.
   4. In the *Class name* field, begin typing registry, and select it from 
   the autocomplete list.
   5. Click *Add class*.
   6. Click *Commit 1 change*.
   Note that the registry class now appears in the list of classes for your 
   agent node.
   7. Puppet runs, which configures the *windows_ example* group using the 
   newly-assigned class. Wait one or two minutes. 


   
   After create group "windows_example". I am trying to add registry class 
   to the example group. But  at the step 4, after typing "registry", I cannot 
   see the autocomplete list and I could not click "+Add class" (it does not 
   work, after click it did not show "Commit 1 change". Can you give me some 
   instruction or suggestion? Thank you!
   
Yingbo

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/19d6bdf2-68ca-4735-86db-fdea42094cae%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Anyone successfully use mcollective shell plugin with RHEL 5 & 6?

[Kenton Brede]

The title pretty much says it all.  I mostly manage RHEL 5 & 6 boxes that
come with ruby 1.8.7.  The mcollective shell plugin requires ruby 1.9.

SCL might work for the RHEL 6 systems but not 5.  Building everything from
source would work but certainly not ideal.  I took a stab at managing ruby
with rbenv yesterday and didn't manage to get the shell plugin to work.

Any thoughts appreciated.

Thanks,

-- 
Kent Brede

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CA%2BnSE3_W2Ma8X-mNWTaZcmoOY0aJT8JrJ_DXKhCy2bdJGvCAYg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] puppet local environment doesn't match server specified node environment switching agent to

[Andreas Dvorak]

Hi,

now I found out that I need to create the new windows environment in The 
Foreman. Than I change the server in The Foreman from production to windows.

Thank you.

Andreas



-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/dcc28dce-9744-4045-80ba-e7f5205f9467%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: multi-line content= construct for puppet resource file command

[Massimiliano Adamo]

Il giorno mercoledì 6 marzo 2013 07:49:44 UTC+1, Robert Citek ha scritto:
>
> Hello all, 
>
> How does one enter multi-line content using 'puppet resource file ...' 
> at the command line? 
>
> For example, I am trying to create a file called /tmp/hw.txt with two 
> lines of content: 
>
> $ cat /tmp/hw.txt 
> hello 
> world 
>
> This does not work: 
>
> $ puppet resource file hello_world \ 
>   path=/tmp/hw.txt \ 
>   ensure=file \ 
>   content="hello\nworld\n" 
>

one of the following will work (or either both):
content => inline_template('<%= "hello" + "\n" + "world" %>'),
content => inline_template('<%= "hello\nworld" %>'),
 

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/e27dd8a1-0442-4c47-af8b-8d00c0295979%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] java_ks certificate chaining

[Pradeep kumar]

Im trying to include certificate chaining in my puppet module using the 
java_ks as given below.  But the chain is not getting added to the keystore 
and in the debug logs I dont see chain getting imported.  Am I missing 
something here?

Puppet install.pp
java_ks { 'cmhs:/tmp/cmhs.jks':
ensure => latest,
certificate => '/tmp/cmhs.cer',
chain => '/tmp/cmhs_ca_root.cer',
private_key => '/tmp/cmhs.key',
password => 'changeme',
   }

[root@puppet-agent tmp]# keytool -list -keystore cmhs.jks -storepass 
changeme

Keystore type: JKS
Keystore provider: SUN

Your keystore contains 1 entry

cmhs, Sep 22, 2015, PrivateKeyEntry,
Certificate fingerprint (SHA1): 
26:EE:96:A6:24:AD:62:6D:71:46:7B:F4:0E:7A:68:9A:FE:D8:C2:B0


Debug log:
Info: Applying configuration version '1442903710'
Debug: Executing 'keytool -list -keystore /tmp/cmhs.jks -alias cmhs'
Debug: Executing 'keytool -list -keystore /tmp/cmhs.jks -alias cmhs'
Debug: Executing 'keytool -importkeystore -srcstoretype PKCS12 
-destkeystore /tmp/cmhs.jks -srckeystore /tmp/cmhs.20150922-16212-o8clvu-0 
-alias cmhs'
Notice: /Stage[main]/Cmhs::Install/Java_ks[cmhs:/tmp/cmhs.jks]/ensure: 
created
Debug: /Stage[main]/Cmhs::Install/Java_ks[cmhs:/tmp/cmhs.jks]: The 
container Class[Cmhs::Install] will propagate my refresh event
Debug: Class[Cmhs::Install]: The container Stage[main] will propagate my 
refresh event
Debug: Finishing transaction 69944070871020



-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/1a372370-6c3a-4f0b-ad74-a01a91815bde%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] puppet local environment doesn't match server specified node environment switching agent to

[jcbollinger]

On Tuesday, September 22, 2015 at 3:51:17 AM UTC-5, Andreas Dvorak wrote:
>
> Hi,
>>
>
> I am using Puppet 3.6.2 free version. The node classification is done by 
> the node.pp file.
> I do not understand the group. Where does the Puppet Master do the 
> overwritting of the environment?
>
>

A non-default environment for a given node can be specified either on the 
master (via an ENC or other node terminus) or by the agent, according to 
its configuration.  If it is specified in both places than the master wins, 
and a warning is reported on the agent.  This is what you are seeing.

You do have an ENC configured on your master, so presumably it is indeed 
setting nodes' environments.


John

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/d48e9e79-940e-4050-be5b-a9a9eb83babd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Inside a custom function, how do you if noop is enabled ?

[Henrik Lindberg]

On 2015-21-09 22:34, Frédéric Lespez wrote:


In the 3.x function API use:

lookupvar('varname')

In the 4.x function API use:

closure_scope.lookupvar('varname')

Here is the specification for the 4.x API.

https://github.com/puppetlabs/puppet-specifications/blob/master/language/func-api.md




Thank Henrik. It works like a charm.

Also consider looking up the $facts hash instead of directly looking up
individual facts like $clientnoop. This to be future proof. (See the
link you posted regarding details).

In fact, using the $fact hash was my first choice. But I didn't find a
clientnoop  fact, nor a noop fact.
Did I miss something ?



The docs are vague regarding $clientnoop - have to dig deeper to find 
out what is going on wrt. that variable.


If you expected (as I did, but I did not really try things out) that it 
is a fact and should have been in the $facts hash, then I suggest that a 
ticket is logged. It is either a problem in code, or something that 
should be mentioned in documentation.


- henrik


--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/557e90f2-d9e2-4d1b-a9c5-96dcf3f6bfd4%40googlegroups.com
.
For more options, visit https://groups.google.com/d/optout.



--

Visit my Blog "Puppet on the Edge"
http://puppet-on-the-edge.blogspot.se/

--
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/mtrgeh%24e9o%241%40ger.gmane.org.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] puppet local environment doesn't match server specified node environment switching agent to

[Andreas Dvorak]

>
> Hi,
>

I am using Puppet 3.6.2 free version. The node classification is done by 
the node.pp file.
I do not understand the group. Where does the Puppet Master do the 
overwritting of the environment?

Andreas

>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/3c8e7d1b-1044-47bf-823e-ac06a8e23e7e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] puppet local environment doesn't match server specified node environment switching agent to

[Rich Burroughs]

Are you using Puppet Enterprise? If so, have a look at this:

https://docs.puppetlabs.com/pe/latest/console_classes_groups_preconfigured_groups.html#the-agent-specified-environment-node-group

If you are using the console for node classification you need to have a
group that allows the agent to specify the environment, to use something
other than production. Or you can create a group that points to a specific
environment.


Rich
On Tue, Sep 22, 2015 at 12:55 AM Andreas Dvorak 
wrote:

> Hi,
>
> I have created a new environment for windows server, but the agent does
> not use it. Can somebody please help me?
>
> message on agent run:
> puppet local environment windows doesn't match server specified node
> environment switching agent to production
>
> puppet.conf of windows agent
>
> [main]
> server=puppet-simu.baag
> ca_server=puppet1-simu.baag
> autoflush=true
>
> [agent]
> environment=windows
> pluginsync=true
>
> puppet.conf of master
> [main]
> autosign= $confdir/autosign.conf { mode = 664 }
> environmentpath = $confdir/environments
> logdir  = /var/log/puppet
> rundir  = /var/run/puppet
> ssldir  = $vardir/ssl
> privatekeydir   = $ssldir/private_keys { group = service }
> hostprivkey = $privatekeydir/$certname.pem { mode = 640 }
> pluginsync  = true
>
> [agent]
> classfile = $vardir/classes.txt
> localconfig   = $vardir/localconfig
> default_schedules = false
> report= true
> pluginsync= true
> masterport= 8140
> environment   = production
> certname  = sv2655.muc.baag
> dns_alt_names = puppet-simu.baag, puppet1-simu.baag
> server= sv2655.muc.baag
> listen= false
> splay = false
> runinterval   = 1800
> noop  = false
> show_diff = false
>
> [master]
> autosign   = $confdir/autosign.conf { mode = 664 }
> reports= foreman
> external_nodes = /etc/puppet/node.rb
> node_terminus  = exec
> ca = true
> ssldir = /var/lib/puppet/ssl
>
> cat environment.conf
> config_version = /usr/bin/git --git-dir /data/git/windows/.git show --stat
> | head -1| cut -d" " -f2
> manifest   = /data/git/windows/manifests
> modulepath = /data/git/windows/modules
>
> # pwd
> /etc/puppet/environments
> # ls -l
> total 20
> drwxr-xr-x 2 root root 4096 Oct 18  2013 common
> drwxr-xr-x 3 root root 4096 Oct 18  2013 development
> drwxr-xr-x 4 root root 4096 Sep 21 09:48 example_env
> drwxr-xr-x 3 root root 4096 Sep 21 10:09 production
> drwxr-xr-x 2 root root 4096 Sep 22 08:48 windows
>
> # pwd
> /data/git/windows/manifests
>
> # ls -l
> total 4
> -rw-rw-r-- 1 gitwin gitwin  23 Sep 22 08:41 nodes.pp
> -rw-rw-r-- 1 gitwin gitwin 195 Sep 22 08:41 site.pp
> # cat site.pp
> node default {
>   notify { 'Server ist noch nicht in Puppet definiert': }
> }
> if versioncmp($::puppetversion, '3.6.0') >= 0 {
>   Package {
> allow_virtual => true,
>   }
> }
> hiera_include('classes')
>
> # cat nodes.pp
> node 'vm7523.baag' {
> }
>
> Best regards,
> Andreas
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/3b134331-5c38-47b4-bef5-9dd467318b4a%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAPGcbtAOrR3%3DFc%3DoU%2BrxPVewvpB6nE%3DqKmkTwYj1VUmPq1_S-w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] puppet local environment doesn't match server specified node environment switching agent to

[Andreas Dvorak]

Hi,

I have created a new environment for windows server, but the agent does not 
use it. Can somebody please help me?

message on agent run:
puppet local environment windows doesn't match server specified node 
environment switching agent to production

puppet.conf of windows agent

[main]
server=puppet-simu.baag
ca_server=puppet1-simu.baag
autoflush=true

[agent]
environment=windows
pluginsync=true

puppet.conf of master
[main]
autosign= $confdir/autosign.conf { mode = 664 }
environmentpath = $confdir/environments
logdir  = /var/log/puppet
rundir  = /var/run/puppet
ssldir  = $vardir/ssl
privatekeydir   = $ssldir/private_keys { group = service }
hostprivkey = $privatekeydir/$certname.pem { mode = 640 }
pluginsync  = true

[agent]
classfile = $vardir/classes.txt
localconfig   = $vardir/localconfig
default_schedules = false
report= true
pluginsync= true
masterport= 8140
environment   = production
certname  = sv2655.muc.baag
dns_alt_names = puppet-simu.baag, puppet1-simu.baag
server= sv2655.muc.baag
listen= false
splay = false
runinterval   = 1800
noop  = false
show_diff = false

[master]
autosign   = $confdir/autosign.conf { mode = 664 }
reports= foreman
external_nodes = /etc/puppet/node.rb
node_terminus  = exec
ca = true
ssldir = /var/lib/puppet/ssl

cat environment.conf 
config_version = /usr/bin/git --git-dir /data/git/windows/.git show --stat 
| head -1| cut -d" " -f2
manifest   = /data/git/windows/manifests
modulepath = /data/git/windows/modules

# pwd
/etc/puppet/environments
# ls -l
total 20
drwxr-xr-x 2 root root 4096 Oct 18  2013 common
drwxr-xr-x 3 root root 4096 Oct 18  2013 development
drwxr-xr-x 4 root root 4096 Sep 21 09:48 example_env
drwxr-xr-x 3 root root 4096 Sep 21 10:09 production
drwxr-xr-x 2 root root 4096 Sep 22 08:48 windows

# pwd
/data/git/windows/manifests

# ls -l
total 4
-rw-rw-r-- 1 gitwin gitwin  23 Sep 22 08:41 nodes.pp
-rw-rw-r-- 1 gitwin gitwin 195 Sep 22 08:41 site.pp
# cat site.pp
node default {
  notify { 'Server ist noch nicht in Puppet definiert': }
}
if versioncmp($::puppetversion, '3.6.0') >= 0 {
  Package {
allow_virtual => true,
  }
}
hiera_include('classes')

# cat nodes.pp
node 'vm7523.baag' {
}

Best regards,
Andreas

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/3b134331-5c38-47b4-bef5-9dd467318b4a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.