[Puppet Users] user creation in puppet nodes through PUPPET Master

[prasanthr021]

Hi

 I am a beginner in Puppet.. I want to create a user in 2 puppet nodes 
through puppet master. can anyone help in this. 
I need to know the path where I should save this code in puppet master

Thanks   

-- 
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/c449060b-9740-4539-9844-e36b96d4a053%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Upgrade

[Don Dorman]

Has anyone found documentation on upgrading Puppet 3.4.3 to Puppet 3.6.2. 
running on RHEL 6.4

I have found some documents, but nothing simple and clearly defined.


-- 
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/0a20e707-1a52-465f-8476-dc2cd07fe252%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Upgrade

[Dirk Heinrichs]

Am 20.01.2015 um 13:39 schrieb Don Dorman:

> Has anyone found documentation on upgrading Puppet 3.4.3 to Puppet
> 3.6.2. running on RHEL 6.4

First update the server, then agent nodes. You can use Puppet to update
the agents (I've written myself a small module to do that).

> I have found some documents, but nothing simple and clearly defined.

Server: yum upgrade
Agents:
Manual: yum upgrade
Automatic: Use (custom) puppet module, maybe with a version
parameter. Then to update, just increase the version number and wait for
the next automatic agent run.

Feel free to ask for my module ;).

HTH...

Dirk
-- 

*Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions
*Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach
*Tel*: +49 2226 159 (Ansage) 1149
*Email*: d...@recommind.com 
*Skype*: dirk.heinrichs.recommind
www.recommind.com 

-- 
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/54BE4E31.90307%40recommind.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Upgrade

[Don Dorman]

Thanks for the very prompt respo0nse.

So respectively on the Puppet Master I have copied Puppet 3.6.2 to 
/var/data/Puppet. I have the RHEL 6.4.iso mounted to /mnt

So I am guessing to upgrade the Master it should be as simple as yum 
upgrade puppet-server-3.6.2-1.el6.noarch.rpm

and yum upgrade puppetdb-2.0.0-1.el6.noarch.rpm

and the obvious yum upgrade puppet-3.6.2-1.el6.noarch.rpm


On Tuesday, 20 January 2015 07:46:57 UTC-5, Dirk Heinrichs wrote:
>
>  Am 20.01.2015 um 13:39 schrieb Don Dorman:
>
>  Has anyone found documentation on upgrading Puppet 3.4.3 to Puppet 
> 3.6.2. running on RHEL 6.4
>
>
> First update the server, then agent nodes. You can use Puppet to update 
> the agents (I've written myself a small module to do that).
>
> I have found some documents, but nothing simple and clearly defined.
>
>
> Server: yum upgrade
> Agents:
> Manual: yum upgrade
> Automatic: Use (custom) puppet module, maybe with a version parameter. 
> Then to update, just increase the version number and wait for the next 
> automatic agent run.
>
> Feel free to ask for my module ;).
>
> HTH...
>
> Dirk
> -- 
>
> *Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions
> *Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach
> *Tel*: +49 2226 159 (Ansage) 1149
> *Email*: d...@recommind.com 
> *Skype*: dirk.heinrichs.recommind
> www.recommind.com
>  

-- 
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/9ba58bad-16a7-4ef9-9e21-a8572a54cff5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Upgrade

[Dirk Heinrichs]

Am 20.01.2015 um 13:53 schrieb Don Dorman:

> So respectively on the Puppet Master I have copied Puppet 3.6.2 to
> /var/data/Puppet. I have the RHEL 6.4.iso mounted to /mnt
>
> So I am guessing to upgrade the Master it should be as simple as yum
> upgrade puppet-server-3.6.2-1.el6.noarch.rpm
>
> and yum upgrade puppetdb-2.0.0-1.el6.noarch.rpm
>
> and the obvious yum upgrade puppet-3.6.2-1.el6.noarch.rpm

Yes (could also be one command).

"yum upgrade", as I suggested, would update ALL packages to their LATEST
versions.

Bye...

Dirk
-- 

*Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions
*Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach
*Tel*: +49 2226 159 (Ansage) 1149
*Email*: d...@recommind.com 
*Skype*: dirk.heinrichs.recommind
www.recommind.com 

-- 
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/54BE5182.90803%40recommind.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Conditional Require For File Type

[jcbollinger]

On Friday, January 16, 2015 at 12:48:19 PM UTC-6, Weeve wrote:
>
> On Thu, Jan 15, 2015 at 9:53 AM, jcbollinger  > wrote: 
> > 
> > In any case, if $foo does not resolve to a class or resource reference, 
> then 
> > why does catalog building succeed?  (Or perhaps the problem actually 
> > manifests as catalog building failure) 
>
> Feels like I've been staring at the problem too long, forgetting to 
> provide a little more detail here. 
>
> When I have requires = $foo, the catalog does compile and $foo does 
> resolve to Class['a'] or Class['b'] correctly when I look at the debug 
> output from the Puppet agent (puppet agent -tv --debug). 
>
> If I use the anchor method as well ($foo -> Class['a]), it wasn't 
> installing it in the preferred order as well, but if I use the anchor 
> method on the Service Type that Class['a'] provides in its service.pp, 
> then it worked for me. 
>


There seems to be a bit of a terminology gap here.  Class['a'] does not 
"have" a service.pp in any useful sense of the term.  I suppose you 
probably mean that *module* 'a' has a class or defined type "a::service" 
whose definition resides in modules/a/manifests/service.pp.  The 
distinction matters, as does, in particular, whether a::service is a class 
or a defined type.  (In a typical module architecture, such a thing would 
be a class.)

Moreover, it's unclear what you mean when you say you "use the anchor 
method on the Service Type [...]."  I can probably guess roughly what you 
mean, but here, too, the details matter.  We can give better answers if you 
present code that actually exhibits the problem -- preferrably *minimal* 
code that does so.

 

>
> >> This should work: 
> >> 
> >> $foo = "a" 
> >> 
> >> File["/path/to/file"] { require => Class[$foo] } 
> >> 
>
> This method allowed the catalog to compile as well, but didn't change 
> any of the ordering issues. 
>
>

My best guess at this point is that you have a class containment issue 
.
  
That is, Puppet is very likely applying the ordering you specify, but that 
doesn't have the *effect* you expect because Class['a'] and/or Class['b'] 
declares other classes that you consider as belonging to 'a' / 'b', but 
which are not properly contained by 'a' / 'b'.


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/e7828d3c-70f2-4b02-a919-1846d0b8dc42%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] user creation in puppet nodes through PUPPET Master

[Johan De Wit]

On 20/01/15 11:57, prasanthr...@gmail.com wrote:




Hi

 I am a beginner in Puppet.. I want to create a user in 2 puppet nodes 
through puppet master. can anyone help in this.

I need to know the path where I should save this code in puppet master

Thanks
--
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/c449060b-9740-4539-9844-e36b96d4a053%40googlegroups.com 
.

For more options, visit https://groups.google.com/d/optout.

http://puppetlabs.com/download-learning-vm

Enjoy the journey

Johan

--
Johan De Wit

Open Source Consultant

Red Hat Certified Engineer  (805008667232363)
Puppet Certified Professional 2013/2014 (PCP006)
blog : http://johan.koewacht.net/
_
 
Open-Future Phone +32 (0)2/255 70 70

Zavelstraat 72  Fax   +32 (0)2/255 70 71
3071 KORTENBERG Mobile+32 (0)474/42 40 73
BELGIUM http://www.open-future.be
_
 



Next Events:
Bacula Administrator 1 | 
http://www.open-future.be/bacula-administrator-i-training-13th-till-15th-january
Puppet Fundamentals | 
http://www.open-future.be/puppet-fundamentals-training-26th-till-28th-january
Puppet Architect | 
http://www.open-future.be/puppet-architect-training-29th-till-30th-january
Linux Training | http://www.open-future.be/linux-training-9th-till-13th-february
Puppet Practitioner | 
http://www.open-future.be/puppet-practitioner-training-17th-till-19th-february
Bacula Administrator 1 | 
http://www.open-future.be/bacula-administrator-i-training-24th-till-26th-february
Subscribe to our newsletter | http://eepurl.com/BUG8H

--
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/54BE6A1E.9020604%40open-future.be.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] user creation in puppet nodes through PUPPET Master

[Felix Frank]

On 01/20/2015 03:45 PM, Johan De Wit wrote:
> http://puppetlabs.com/download-learning-vm
> 
> Enjoy the journey

Beat me to the punch.

See you soon, Johan!

Best,
Felix

-- 
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/54BE6A52.9090105%40alumni.tu-berlin.de.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Behavior of exported resource collectors

[Martin Alfke]

Hi,

I have the following code:

define monitor::host (
  $target,
  $monitortag = $::domain,
) {
}
…
}

The define gets exported on all nodes:

@@monitor::host { $::fqdn: }

And I collect on the monitor server:

Monitor::Host <<| |>> {
  target => ‘/full path to config’,
}

This is working as expected

No I want to collect from a specific monitortag only:

Monitor::Host <<| monitortag == ‘foo.com’ |>> {
  target => ‘/full path to config’,
}

Now we receive an error message on the host where we collect claiming that 
target is not set.

Is this known behaviour?

Many thanks,

Martin

-- 
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/87C98E61-9294-4526-B70F-11F7EBDE15CD%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Resource ordering syntax

[jcbollinger]

On Monday, January 19, 2015 at 5:33:26 AM UTC-6, Andrew Langhorn wrote:
>
> Thanks Martin! That makes sense.
> Is it not possible to refer to the entire resource, then, when the title 
> is used as the declaration?
>
>

I don't understand the question.  It is not possible to refer to *less than* 
an entire resource.  Perhaps you haven't fully appreciated Martin's 
comment, which I usually word a bit differently: when you use an array as a 
resource title, it serves as *shorthand* for multiple resource 
declarations, one per array element.  There is no aggregate resource with 
an array title; each declared resource is separate and independent.

However, all resources declared via that syntax share all the parameters 
specified, so in particular, if one of the parameters is a 'require' or 
'before', then all resources declared by that block will have the specified 
relationship.  Example:

package { [‘foo’, ‘bar’]: ensure => present, before => Service['foobar'] } 

In that case, Package['foo'] and Package['bar'] will both be applied before 
Service['foobar'].

Also, the chaining operators can be applied directly to resource 
declaration blocks, and when used with an array-titled resource declaration 
block they apply, separately, to every resource declared by the block.  
Thus, the following example is semantically identical to the previous one:

package { [‘foo’, ‘bar’]: ensure => present } 
->
Service['foobar']

Outside the syntactic context of an (array-titled) resource declaration 
block, however, there is no inherent association between the multiple 
resources declared by that block.


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/e8cf1530-044e-46d3-bfcc-9be02dd08b54%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Upgrade

[Don Dorman]

I would love to take a look at your module.

On Tuesday, 20 January 2015 07:46:57 UTC-5, Dirk Heinrichs wrote:
>
>  Am 20.01.2015 um 13:39 schrieb Don Dorman:
>
>  Has anyone found documentation on upgrading Puppet 3.4.3 to Puppet 
> 3.6.2. running on RHEL 6.4
>
>
> First update the server, then agent nodes. You can use Puppet to update 
> the agents (I've written myself a small module to do that).
>
> I have found some documents, but nothing simple and clearly defined.
>
>
> Server: yum upgrade
> Agents:
> Manual: yum upgrade
> Automatic: Use (custom) puppet module, maybe with a version parameter. 
> Then to update, just increase the version number and wait for the next 
> automatic agent run.
>
> Feel free to ask for my module ;).
>
> HTH...
>
> Dirk
> -- 
>
> *Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions
> *Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach
> *Tel*: +49 2226 159 (Ansage) 1149
> *Email*: d...@recommind.com 
> *Skype*: dirk.heinrichs.recommind
> www.recommind.com
>  

-- 
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/685943ff-1e13-46ae-9eb9-c37950fbad65%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Conditional Require For File Type

[Jason Wever]

On Tue, Jan 20, 2015 at 9:40 AM, jcbollinger  wrote:
> There seems to be a bit of a terminology gap here.  Class['a'] does not
> "have" a service.pp in any useful sense of the term.  I suppose you probably
> mean that module 'a' has a class or defined type "a::service" whose
> definition resides in modules/a/manifests/service.pp.  The distinction
> matters, as does, in particular, whether a::service is a class or a defined
> type.  (In a typical module architecture, such a thing would be a class.)

Yes, that is correct.  Sorry for my lack of proper terminology.

> Moreover, it's unclear what you mean when you say you "use the anchor method
> on the Service Type [...]."  I can probably guess roughly what you mean, but
> here, too, the details matter.  We can give better answers if you present
> code that actually exhibits the problem -- preferrably minimal code that
> does so.

Point taken.

> My best guess at this point is that you have a class containment issue.
> That is, Puppet is very likely applying the ordering you specify, but that
> doesn't have the effect you expect because Class['a'] and/or Class['b']
> declares other classes that you consider as belonging to 'a' / 'b', but
> which are not properly contained by 'a' / 'b'.

Thanks for the link.  This does sound like what is going on.  I'll
take a look at the module and see if this will help.

Thanks,
-- 
Jason Wever

-- 
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/CAEqBX788SiCn6-9butPtn-mbXhSky8vSL5Mxf4m8778FgiYZ4w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: File 'replace => false' doesn't match my expectations...

[Marc]

Using 'replace => false' should not trigger a checksum operation but given 
the time it takes with big files I think it does.
Does it make sense to perform checksum when 'replace' is set to false?

*  exec { 'wget -O - http://repo01.demo.lan/coreos/coreos_qemu.img.bz2 | 
bzcat > /root/coreos/core01/core01.img':*
*path=> '/usr/bin',*
*creates => '/root/coreos/core01/core01.img',*
*  }*

*  file { [ '/root/coreos/core02/core02.img',*
*   '/root/coreos/core03/core03.img',*
*   '/root/coreos/core04/core04.img' ]:*
*ensure  => file,*
*replace => false,*
*source  => '/root/coreos/core01/core01.img',*
*owner   => 'root',*
*group   => 'root',*
*mode=> '0644',*
*  }*

Marc

On Thursday, February 5, 2009 at 5:59:06 AM UTC+1, Luke Kanies wrote:
>
> On Jan 30, 2009, at 9:54 AM, Jeff wrote:
>
> >
> > On Jan 28, 7:18 pm, Andrew Shafer  wrote:
> >> Jeff,
> >>
> >> What version of Puppet are you using?
> >
> > Andrew,
> >
> > Each time I used a template, it overwrote a changed file. Each time I
> > used a source, it did not.
> >
> > Version: 0.24.4
> >
> > I just tested one more time to make sure. The results were the same.
> > If I used a template AND replace => false, it still overwrote a
> > modified file. If I used source AND replace => false, it did not.
>
>
> Definitely not the right behaviour, and fixed in recent releases.
>
> -- 
> The leader of Jamestown was "John Smith" (not his real name), under
> whose direction the colony engaged in a number of activities,
> primarily related to starving. -- Dave Barry, "Dave Barry Slept Here"
> -
> Luke Kanies | http://reductivelabs.com | http://madstop.com
>
>

-- 
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/b2d3014f-b8de-4cb4-8b92-e62a7a9d9d6b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Using Ruby puppet db library - syntax question

[JonY]

I'm hoping to use this library (or something similar) to request a single 
fact from all nodes. The equiv curl request would be 'curl -X GET 
http://host:8080/v3/facts --data-urlencode 'query=["=","name","fs_space"]'.

I've been looking at the docs on 
'https://github.com/puppetlabs/puppetdb-ruby' but I can't seem to get the 
syntax correct for this type of request. Suggestions?

-- 
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/015ec9dd-338a-45bb-a39f-f09ae2162ff6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] invoke-rc.d errors - what happened to this system?

[JonY]

Debian 6 machine running 3.7.1. Attempts to run 'puppet agent --test' give 
a stream of errors like this:

invoke-rc.d: WARNING: 'invoke-rc.d dnsmasq start' called
invoke-rc.d: during shutdown sequence.
invoke-rc.d: enabling safe mode: initscript policy layer disabled.


If I do a 'service dnsmasq start' after this it works ok with no error 
messages. 

'runlevel' reports '3 6'.

The system is apparently bolluxed somehow but I'm not sure what's wrong. 
Where should I look?

-- 
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/e0406c05-1770-4ca1-88ac-ea9909fa9ab5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: invoke-rc.d errors - what happened to this system?

[JonY]

Looking at the debug log it appears that puppet is calling 
'/etc/init.d/dnsmasq status' before this message appears.. but when I enter 
the same command subsequently I'm told ''running'. and nothing else.

Similar messages appear for puppet, ifplugd, apache2.. every service that I 
monitor with puppet. 

On Tuesday, January 20, 2015 at 12:19:12 PM UTC-8, JonY wrote:
>
> Debian 6 machine running 3.7.1. Attempts to run 'puppet agent --test' give 
> a stream of errors like this:
>
> invoke-rc.d: WARNING: 'invoke-rc.d dnsmasq start' called
> invoke-rc.d: during shutdown sequence.
> invoke-rc.d: enabling safe mode: initscript policy layer disabled.
>
>
> If I do a 'service dnsmasq start' after this it works ok with no error 
> messages. 
>
> 'runlevel' reports '3 6'.
>
> The system is apparently bolluxed somehow but I'm not sure what's wrong. 
> Where should I look?
>

-- 
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/d3f34da1-0986-4f06-a392-1cf32ba3d8c9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.