[Puppet Users] Re: checking puppet run status of node A during puppet run of node B

[walterheck]

Look into exported resources to see if it can do what you need. Works a tad 
better then qeurying puppetdb or contacting B directly, much more scalable 
too :)

On Monday, April 29, 2013 3:18:20 PM UTC+2, Schofield wrote:
>
> I have some middleware where the successful configuration of node B is 
> dependent on the successful configuration of node A.  Node B must pull 
> additional information from node A during its configuration.  Is there any 
> built in functionality in puppet for checking the completion status of 
> other nodes?  Right now my intent is to write a custom function to query 
> the puppetdb which is storing reports.  I want to make sure I am not 
> missing some other elegant solution in puppet that already does this.
>

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Retrieve scoped resource defaults from class method in custom type

[Ryan Uber]

[accidently sent this to puppet-dev, re-posting to puppet-users]

Hello puppet-users,

I am working on a module that provides a custom type. The type when
called will create new resources in the catalog using syntax like:

Puppet::Type.type(:file).new(:title => 'blah')

This works fine and the resources are added as expected. However, I am
unable to apply any scoped defaults to the generated resources. So
something like:

File {
  mode => 0750
}

would not be applied to the generated resources. I understand that this
is most likely because I am altering the catalog directly.

The only thing I can think of doing would be to retrieve the scoped
attributes first, and then apply them to the generated resource. I have
been trying to do this with code like:

f = Puppet::Type.type(:file)
f.allattrs.each do |attrname|
  attrvalue = f.value(attrname)
  puts "#{attrname} = #{attrvalue}"
end

I know this doesn't work, but wanted to throw this out there to see if I
am taking the wrong approach at fetching resource defaults from the
scope in which my custom type is called.

Thanks for any help or insight.

- Ryan

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Re: New Module - NetApp Storage support

[fatmcgav]

Brett

Which version are you trying to use?

Did have an issue with some earlier versions when exporting the module from
Gepetto... It would remove an empty dependencies list... However have been
using a different method for latest versions.

But to confirm, there are no dependencies for this module.

Regards
Gavin
On 30 Apr 2013 23:12, "Brett Edelen"  wrote:

> having some trouble getting this module installed. do you know the
> dependency list?
> ---
> Preparing to install into /etc/puppetlabs/puppet/modules ...
> Error: No dependencies module metadata provided for netapp
> Error: Try 'puppet help module install' for usage
> ---
>
> On Tuesday, January 29, 2013 4:00:08 AM UTC-8, Gavin Williams wrote:
>>
>> Afternoon all
>>
>> Thought I'd drop a quick message through to highlight a new module that
>> I've just released to the Forge...
>>
>> The module is 
>> fatmcgav/netapp,
>> and its purpose is to allow Puppet to manage NetApp storage devices using
>> Puppet's Network Device functionality...
>>
>> As some of you may be aware, I've been working on this module on and off
>> for a couple of months now, and a lot of assistance has been given from
>> members of the Puppet-users and Puppet-dev lists, so many thanks again for
>> that assistance.
>>
>> Please feel free to ask any questions, raise any issues etc, either in
>> response to this post, though twitter (@fatmcgav), email (fatmcgav[at]
>> gmail.com) or can raise issues directly on 
>> Git
>> .
>>
>> And lastly, I hope that people find this module useful.
>>
>> Regards
>> Gavin W
>>
>  --
> You received this message because you are subscribed to a topic in the
> Google Groups "Puppet Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/puppet-users/WIlC3dzpY4E/unsubscribe?hl=en
> .
> To unsubscribe from this group and all its topics, send an email to
> puppet-users+unsubscr...@googlegroups.com.
> To post to this group, send email to puppet-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/puppet-users?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Puppet Mail notification configuration

[Jithin Xavier]

Hi All-

How we can configure mail notification in Puppet enterprise server, like if 
any changes happened in agent it should notify through mail. I have seen 
some of the documentation regarding that in Puppet docs - 
http://docs.puppetlabs.com/references/0.25.5/report.html#tagmail. Anyone 
here has any prior experience about the mail notification, Please help me 
to configure this.

Thanks,
Jithin

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] puppet 3 and hiera debugging

[Denmat]

Hi,

Run the master in no-daemonize and debug. You will see how it searches through 
your hierarchy that way.

Also you can use the command line on the master to query hiera. See puppet docs 
for details.

Cheers,
Den

On 01/05/2013, at 2:46, lth  wrote:

> I'm using puppet 3.1 and I want to figure out why hiera seems to be looking 
> in the wrong place and getting the wrong value.
> 
> I found a post from this group saying to run puppet -d on the master and look 
> in the log.  Having done that I still don't see anything hiera related except 
> for where puppet reads  hiera_config from puppet.conf, nor do I see anything 
> about the automatic parameter lookup or where I use the heira() function to 
> assign another variable.  
> 
> I tried both:
> puppet agent -t --environment=devel --logdest=/tmp/puppet_agent.log --debug
> puppet master --debug --no-daemonize --logdest=/tmp/puppet.log 
> --compile=vb271-puppet.vm --environment=devel
> 
> neither of which gave me anything useful.  What am I doing wrong?
> 
> Thanks in advance.
> -- 
> 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 post to this group, send email to puppet-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/puppet-users?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>  
>  

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: manifest digest mismatch error

[Mark Hahn]

I found the problem.  I had incorrectly tried to mount that file as a disk. 
 That must have corrupted the file.  I downloaded the file again and it 
worked when installing that as an appliance.

Now I just have to get the stupid networking and ssh working.

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] manifest digest mismatch error

[Mark Hahn]

I'm getting this error when trying to install the puppet tutorial appliance 
into virtualbox ...

Failed to import appliance *
C:\Users\Administrator\Desktop\learn_puppet_centos_pe2.7.0_ovf.2013.01.07\learn_puppet_centos_pe2.7.0_ovf.2013.01.07.ovf
*.

The SHA1 digest of 
*'learn_puppet_centos_pe2.7.0_ovf.2013.01.07-disk1.vmdk'*does not match the one 
in 
*'learn_puppet_centos_pe2.7.0_ovf.2013.01.07.mf'*(VERR_MANIFEST_DIGEST_MISMATCH).
Result Code: VBOX_E_FILE_ERROR (0x80BB0004)Component: ApplianceInterface: 
IAppliance 
{3059cf9e-25c7-4f0b-9fa5-3c42e441670b}

I'm in virtualbox 4.2.12 and you can see the vmdk version above.

Can someone please give me a hand?  I'm anxious to learn puppet.

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: New Module - NetApp Storage support

[Brett Edelen]

having some trouble getting this module installed. do you know the 
dependency list?
---
Preparing to install into /etc/puppetlabs/puppet/modules ...
Error: No dependencies module metadata provided for netapp
Error: Try 'puppet help module install' for usage
---

On Tuesday, January 29, 2013 4:00:08 AM UTC-8, Gavin Williams wrote:
>
> Afternoon all
>
> Thought I'd drop a quick message through to highlight a new module that 
> I've just released to the Forge... 
>
> The module is 
> fatmcgav/netapp, 
> and its purpose is to allow Puppet to manage NetApp storage devices using 
> Puppet's Network Device functionality... 
>
> As some of you may be aware, I've been working on this module on and off 
> for a couple of months now, and a lot of assistance has been given from 
> members of the Puppet-users and Puppet-dev lists, so many thanks again for 
> that assistance. 
>
> Please feel free to ask any questions, raise any issues etc, either in 
> response to this post, though twitter (@fatmcgav), email (fatmcgav[at]
> gmail.com) or can raise issues directly on 
> Git
> .
>
> And lastly, I hope that people find this module useful. 
>
> Regards
> Gavin W
>

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Class definitions under node default do not propagate in puppet-agents

[Dimitris]

In site.pp when i declare a class under  changes are 
propagated correctly.
When the same class is declared under  i have no effect on 
changes.


node default {
  # This is where you can declare classes for all nodes.
  # Example:
  #   class { 'my_class': }
 class { 'hosts': }
}

node 'puppetagent1.example.com' {

  # Note the quotes around the name! Node names can have characters that
  # aren't legal for class names, so you can't always use bare, unquoted
  # strings like we do with classes.

  # Any resource or class declaration can go inside here. For 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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] rspec-puppet testing with puppet $::settings

[Wolf Noble]

Hi Simon,



On Apr 29, 2013, at 23:35, "Simon Piette"  wrote:

> Hi all,
> 
> Any solution for testing variables that depends on settings will be welcome


What I've done elsewhere is to make a parameter for, in your case, vardir:


(untested, but close)

Class foo($vardir = $::settings::vardir){
file { "${vardir}/files":
  ensure => directory
}
}


Then in 
spec/classes/foo_main_spec.rb:
require 'spec_helper'
require 'puppetlabs_spec_helper/module_spec_helper'
vartest = Puppet.settings[:vardir]
describe 'foo', :type => :class do
  #...
  #Then you can assign vartest as a class parameter to your tests.
end

W


=MobileMail=
Please excuse brevity or spelling errors


-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Puppet 2.6.x is now EOL

[Michael Stahnke]

The time has come for us to say good-bye to Puppet 2.6.x. Puppet 2.6.x is
now end of Life, as originally announced Jan 17, 2013.

Puppet 2.6.0 first launched July 20, 2010. Since that time, we've had two
major versions of Puppet, 2.7.x and the semantically versioned Puppet 3
series.

Puppet 2.7.x is on security-fix only already, but no end of life for it has
been announced. Puppet 3 is being actively developed with Puppet 3.2
currently in a release candidate phase.

We do have an upgrading guide available:
http://docs.puppetlabs.com/guides/upgrading.html and as always, help is
available in IRC, on mailing lists, and ask.puppetlabs.com


Mike Stahnke
Engineering
Puppet Labs

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: how do you test and release puppet changes?

[Felipe Salum]

I'm basically doing the same.

I have replicated my production environment in Vagrant, that means the 
puppetmaster/puppetdb setup as well as the app,db,cache,api layers are 
identical to production in the vagrant setup.

After all tests are done in Vagrant, destroying and re-creating the VMs 
from scratch to make sure any new change or manifests do not break when 
installing a new machine from scratch we submit a pull request of the 
change to a specific branch, somebody else in the team reviews and merges 
it. The requester pull the changes in the production puppetmaster in a 
specific environment, connect to a few nodes in production and run puppet 
agent --environment to validate it. 

Once we are satisfied, we merge that branch into master and pull it into 
the puppetmaster production environment which all nodes use by default.

Any tips to improve this process is welcome :)

Felipe

On Friday, April 26, 2013 10:03:47 AM UTC-7, Derek Olsen wrote:
>
>
> We are in the process of evaluating our puppet related test and 
> release process and interested in knowing what other folks are doing. 
>
> We are in a position that is not ideal but is not unique from what I 
> can tell.   Our current testing process is basically the 
> responsibility of each person making a change.   Small changes are 
> committed and pushed to dev/qa/prod in one swoop with the committer 
> spot checking the results manually.Larger changes are tested by 
> running a node against a puppet environment which is pointed to the 
> change branch and the desired behavior is manually verified. 
>
> What we would like to do is start with implementing some basic control 
> points which require passing tests before the changes move along. 
> With the goal of being able to increase the test coverage over time to 
> protect ourselves from ourselves. 
>
> One thought we had as an initial step is to just verify catalog 
> compilation for some number of nodes against the proposed changes and 
> block the changes if catalog compilation fails.   This raises the next 
> question around tooling.   We could script up a catalog compiler test 
> calling the the puppet binaries but should we use this as an 
> opportunity to get familiar with rspec-puppet? 
>
> Are people using catalog diffs at all in their release process?   It 
> would seem nice to provide an automated catalog diff for people making 
> 'small' changes so they can make sure their change didn't accidentally 
> drop or change a large number of resources. 
>
> So please share what you find works or doesn't work at your shop. 
>
> TIA> 
>

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] [ANN] puppet-cleaner 0.2.0

[Nikola Petrov]

Looks good to me. I will try to integrate this with the vim puppet support.
Nice work

-- 
Nikolavp


On Tue, Apr 30, 2013 at 5:51 PM, Gerardo Santana Gómez Garrido <
gerardo.sant...@gmail.com> wrote:

> Hi Chris,
>
> you're right. I've fixed the README.md. Thanks!
>
> El lunes, 29 de abril de 2013 22:58:50 UTC-5, Chris Hirsch escribió:
>
>> On 4/29/13 7:43 PM, Gerardo Santana G�mez Garrido wrote:
>> > This release was tested successfully with puppet 3.
>> If I understand correctly this should be compatible with puppet 3 so you
>> may want to update your Requirements as it says it's 2.7.11 only. Thank
>> for the work I'll be checking this out tomorrow!
>>
>  --
> 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 post to this group, send email to puppet-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/puppet-users?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] rspec-puppet testing with puppet $::settings

[Simon Piette]

Hi Wolfe,

On Tue, Apr 30, 2013 at 12:05 PM, Wolf Noble  wrote:

> Hi Simon,
> On Apr 29, 2013, at 7:45 PM, Simon Piette 
>  wrote:
>
> What I've done elsewhere is to make a parameter for, in your case, vardir:
>
>
> (untested, but close)
>
> Class foo($vardir = $::settings::vardir){
> file { "${vardir}/files":
>   ensure => directory
> }
> }
>
>
> Then in
> spec/classes/foo_main_spec.rb:
> require 'spec_helper'
> require 'puppetlabs_spec_helper/module_spec_helper'
> vartest = Puppet.settings[:vardir]
> describe 'foo', :type => :class do
>   #...
>   #Then you can assign vartest as a class parameter to your tests.
> end
>
>
>
>
That's what I did for this module:

https://github.com/spiette/puppet-selinux/blob/master/manifests/params.pp

But under other circumstances, (a puppet module) I can't do this, I have to
use the $::settings variable.

Thanks,

Simon

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] puppet 3 and hiera debugging

[lth]

I'm using puppet 3.1 and I want to figure out why hiera seems to be looking 
in the wrong place and getting the wrong value.

I found a post from this group saying to run puppet -d on the master and 
look in the log.  Having done that I still don't see anything hiera related 
except for where puppet reads  hiera_config from puppet.conf, nor do I see 
anything about the automatic parameter lookup or where I use the heira() 
function to assign another variable.  

I tried both:
puppet agent -t --environment=devel --logdest=/tmp/puppet_agent.log --debug
puppet master --debug --no-daemonize --logdest=/tmp/puppet.log 
--compile=vb271-puppet.vm --environment=devel

neither of which gave me anything useful.  What am I doing wrong?

Thanks in advance.

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] rspec-puppet testing with puppet $::settings

[Wolf Noble]

Hi Simon,
On Apr 29, 2013, at 7:45 PM, Simon Piette 
 wrote:

> Hi all,
> 
> Any solution for testing variables that depends on settings will be welcome.
>
> Thanks,

I sent this last night from another account, but it didn't seem to go through:




What I've done elsewhere is to make a parameter for, in your case, vardir:


(untested, but close)

Class foo($vardir = $::settings::vardir){
file { "${vardir}/files":
  ensure => directory
}
}


Then in
spec/classes/foo_main_spec.rb:
require 'spec_helper'
require 'puppetlabs_spec_helper/module_spec_helper'
vartest = Puppet.settings[:vardir]
describe 'foo', :type => :class do
  #...
  #Then you can assign vartest as a class parameter to your tests.
end





Hope that helps.

W



This message may contain confidential or privileged information. If you are not 
the intended recipient, please advise us immediately and delete this message. 
See http://www.datapipe.com/legal/email_disclaimer/ for further information on 
confidentiality and the risks of non-secure electronic communication. If you 
cannot access these links, please notify us by reply message and we will send 
the contents to you.

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: augeas

[Stan]

thanks a lot for webmin, it's good!!!

Le lundi 29 avril 2013 14:52:42 UTC+2, Stan a écrit :
>
> Hello
>
> I use augeas to replace a value in a config file:
>
> example (this example is good) :
>
> /etc/ssh/sshd_config file
>
> LogLevel INFO
>
>
> class ssh::redhat {
> augeas { "sshd_config":
>   context => "/files/etc/ssh/sshd_config",
>   changes => [
> "set LogLevel VERBOSE",
>   ],
>   notify => Service["sshd"],
> }
>
> This configuration is good
>
> but how do when the file is written like this:
>
> parameter = value (with =)
>
>
> /etc/webmin/config file
>
> lang = us
>
>
> class webmin::redhat {
> augeas { "config":
>   context => "/files/etc/webmin/config",
>   changes => [
> "set "lang =" fr]",
>   ],
> }
> }
>
> this configuration is not good, did you have an idea?
> regards
>

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] [ANN] puppet-cleaner 0.2.0

[Gerardo Santana Gómez Garrido]

Hi Chris,

you're right. I've fixed the README.md. Thanks!

El lunes, 29 de abril de 2013 22:58:50 UTC-5, Chris Hirsch escribió:
>
> On 4/29/13 7:43 PM, Gerardo Santana G�mez Garrido wrote: 
> > This release was tested successfully with puppet 3. 
> If I understand correctly this should be compatible with puppet 3 so you 
> may want to update your Requirements as it says it's 2.7.11 only. Thank 
> for the work I'll be checking this out tomorrow! 
>

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] realizing virtual resource does not match on default properties

[Calvin Walton]

On Tue, 2013-04-30 at 06:45 -0700, Schofield wrote:
> Given a class that defines multiple virtual users with common properties 
> defined in the User class:
> 
> class users{
>   User{
> gid => 2000,
> shell => "/bin/bash",
> managehome => "true",
> password => 'XrU4ZYu0nwk7s',
> require => Group['mygroup'],
>   }
> 
>   @user{ 'user1':
> uid => 1690,
>   }
>   @user{ 'user2':
> uid => 1691,
>   }
> }
> 
> Realizing user1 and 2 fails when matching on a property defined as a 
> default.
> 
> class some_other_class{
>   include users
>   User <| gid == 2000 |>
> }
> 
> Is this expected?  Or should it be considered a bug?  Running puppet 
> version 3.0.0.

I've seen 
http://projects.puppetlabs.com/issues/9655 which looks related, but I'm
not sure if it's the same issue. It would probably be a good idea to
open a bug specifically for the issue you're seeing.

I would expect this to work :)

-- 
Calvin Walton 

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] realizing virtual resource does not match on default properties

[Schofield]

Given a class that defines multiple virtual users with common properties 
defined in the User class:

class users{
  User{
gid => 2000,
shell => "/bin/bash",
managehome => "true",
password => 'XrU4ZYu0nwk7s',
require => Group['mygroup'],
  }

  @user{ 'user1':
uid => 1690,
  }
  @user{ 'user2':
uid => 1691,
  }
}

Realizing user1 and 2 fails when matching on a property defined as a 
default.

class some_other_class{
  include users
  User <| gid == 2000 |>
}

Is this expected?  Or should it be considered a bug?  Running puppet 
version 3.0.0.


-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Re: High Availability of Puppet server for separate geographical location

[R.I.Pienaar]

- Original Message -
> From: "jcbollinger" 
> To: puppet-users@googlegroups.com
> Sent: Tuesday, April 30, 2013 2:39:52 PM
> Subject: [Puppet Users] Re: High Availability of Puppet server for separate 
> geographical location
> 
> 
> 
> On Monday, April 29, 2013 8:55:39 AM UTC-5, shyam sundar Keshari wrote:
> >
> > Hi Team,
> >
> > I have to configure puppet server in Primary-Secondary mode for 2
> > distributed location .
> >
> > Site A is already running 1 Puppet server .Now I need to configure
> > another puppet secondary server at site B ,so that
> >
> > all client at location B ,only connect to that server .And site A
> > puppet client only connect to site A .
> >
> > But mine requirement is of that suppose site A server goes down then
> > Site B server handle all client request and
> >
> > same if Site B server down then server A handles all .
> >
> > Kindly guide me to implement this scenario .
> >
> >
> For the most part, this is outside Puppet's scope.  You need to stand up
> some kind appliance or service in front of your Puppet servers to monitor
> when one goes down, so as to redirect traffic to the other when needed.
> That cannot be part of Puppet, else it would go down with Puppet if ever
> Puppet went down.
> 
> With an external failover system in place, there would still be a few
> things to arrange on the Puppet side.  In order for site B to properly
> serve site A's nodes, it must have
> 
>- site A's SSL certificate, or at least a certificate that site A's
>nodes will trust;
>- ENC and/or node declarations for site A's nodes, matching those on
>site A;
>- modules (and standalone classes, if any) matching those on site A;
>- external data (if applicable) appropriate for site A's nodes; and
>- stored configs for site A, if applicable.

SRV goes a long way towards solving some of this, it is possible to share 
a CA between masters too which solves some of that.  Gets a lot harder when
you involve PuppetDB.

http://docs.puppetlabs.com/guides/scaling_multiple_masters.html


>
> I see two reasonably good approaches here:
> 
>1. the site A and B masters are maintained as a mirrored pair.  This has
>the effect that from Puppet's perspective, physical sites A and B are
>meaningless partitions of a single large, federated site.  A shared,
>central certificate authority would be required (and that would need to be
>the site A master if you want to avoid issuing new certificates to all the
>site A nodes).
>2. A mirror of site A's master is maintained as a hot spare at site B,
>and vice versa.  Each spare could run on the same (possibly virtual)
>hardware as the local master (but on a different port), or it could run on
>different hardware and merely be geographically colocated.  This would
>maintain a logical distinction between sites A and B, and would be overall
>easier to set up and maintain.
> 
> If you consider option 2, however, you should soon realize that in that
> case you don't get any particular advantage from putting the spare masters
> on the same machine as the local site's main master.  Indeed, it might be
> easier to set them up as ordinary nodes (for the site in which they are
> actually located), and even to let the local site's masters have
> responsibility for maintaining the spares' puppet master config, each as a
> mirror of the other site's master.
> 
> 
> 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 post to this group, send email to puppet-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/puppet-users?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
> 
> 
> 

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: High Availability of Puppet server for separate geographical location

[jcbollinger]

On Monday, April 29, 2013 8:55:39 AM UTC-5, shyam sundar Keshari wrote:
>
> Hi Team, 
>
> I have to configure puppet server in Primary-Secondary mode for 2 
> distributed location . 
>
> Site A is already running 1 Puppet server .Now I need to configure 
> another puppet secondary server at site B ,so that 
>
> all client at location B ,only connect to that server .And site A 
> puppet client only connect to site A . 
>
> But mine requirement is of that suppose site A server goes down then 
> Site B server handle all client request and 
>
> same if Site B server down then server A handles all . 
>
> Kindly guide me to implement this scenario . 
>
>
For the most part, this is outside Puppet's scope.  You need to stand up 
some kind appliance or service in front of your Puppet servers to monitor 
when one goes down, so as to redirect traffic to the other when needed.  
That cannot be part of Puppet, else it would go down with Puppet if ever 
Puppet went down.

With an external failover system in place, there would still be a few 
things to arrange on the Puppet side.  In order for site B to properly 
serve site A's nodes, it must have

   - site A's SSL certificate, or at least a certificate that site A's 
   nodes will trust;
   - ENC and/or node declarations for site A's nodes, matching those on 
   site A;
   - modules (and standalone classes, if any) matching those on site A;
   - external data (if applicable) appropriate for site A's nodes; and
   - stored configs for site A, if applicable.
   
I see two reasonably good approaches here:

   1. the site A and B masters are maintained as a mirrored pair.  This has 
   the effect that from Puppet's perspective, physical sites A and B are 
   meaningless partitions of a single large, federated site.  A shared, 
   central certificate authority would be required (and that would need to be 
   the site A master if you want to avoid issuing new certificates to all the 
   site A nodes).
   2. A mirror of site A's master is maintained as a hot spare at site B, 
   and vice versa.  Each spare could run on the same (possibly virtual) 
   hardware as the local master (but on a different port), or it could run on 
   different hardware and merely be geographically colocated.  This would 
   maintain a logical distinction between sites A and B, and would be overall 
   easier to set up and maintain.

If you consider option 2, however, you should soon realize that in that 
case you don't get any particular advantage from putting the spare masters 
on the same machine as the local site's main master.  Indeed, it might be 
easier to set them up as ordinary nodes (for the site in which they are 
actually located), and even to let the local site's masters have 
responsibility for maintaining the spares' puppet master config, each as a 
mirror of the other site's master.


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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: replace a word in config file

[Stan]

a text file

example text file : 

*root*: acl adsl-client apache at backup-config bacula-backup bandwidth 
bind8 burner cfengine change-user cluster-copy cluster-cron cluster-passwd 
cluster-shell 

replace root by admin

*admin*: acl adsl-client apache at backup-config bacula-backup bandwidth 
bind8 burner cfengine change-user cluster-copy cluster-cron cluster-passwd 
cluster-shell 

Le mardi 30 avril 2013 11:25:21 UTC+2, Stan a écrit :
>
> Hi
>
> What is a solution with puppet to replace one word in a config file?
>
> for example i would like replace "root" by "admin" in /etc/files/toto
>
> regards
>

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: replace a word in config file

[Raphink]

Hi,


Depending on the config format, you can use Augeas for that. What is the 
format you need to edit?


Regards,

Raphaël

On Tuesday, April 30, 2013 11:25:21 AM UTC+2, Stan wrote:
>
> Hi
>
> What is a solution with puppet to replace one word in a config file?
>
> for example i would like replace "root" by "admin" in /etc/files/toto
>
> regards
>

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: augeas

[Raphink]

Hello,



On Monday, April 29, 2013 2:52:42 PM UTC+2, Stan wrote:
>
> Hello
>
> I use augeas to replace a value in a config file:
>
> example (this example is good) :
>
> /etc/ssh/sshd_config file
>
> LogLevel INFO
>
>
> class ssh::redhat {
> augeas { "sshd_config":
>   context => "/files/etc/ssh/sshd_config",
>   changes => [
> "set LogLevel VERBOSE",
>   ],
>   notify => Service["sshd"],
> }
>
> This configuration is good
>
>
As a note, I would recommend using the `sshd_config` type from 
http://augeasproviders.com/documentation/examples.html#sshd_config_provider 
instead, 
as it manages more edge cases (and still uses Augeas in the background).

 

> but how do when the file is written like this:
>
> parameter = value (with =)
>
>
> /etc/webmin/config file
>
> lang = us
>
>
> class webmin::redhat {
> augeas { "config":
>   context => "/files/etc/webmin/config",
>   changes => [
> "set "lang =" fr]",
>   ],
> }
> }
>  
>
this configuration is not good, did you have an idea?
> regards
>


The sshd_config example worked because /etc/ssh/sshd_config is a file known 
to Augeas, as it is listed in the sshd.aug module. /etc/webmin/config 
however, is not known to Augeas.

You might want to try the Webmin lens on it:

augeas { 'webmin config':
  lens => 'Webmin.lns',
  incl => '/etc/webmin/config',
  changes => [ 'set lang fr' ],
}
 
If that doesn't work, you can try the Simplevars.lns lens instead.


Regards,

Raphaël

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] replace a word in config file

[Stanislas LEVEAU]

Hi

What is a solution with puppet to replace one word in a config file?

for example i would like replace "root" by "admin" in /etc/files/toto

regards

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Problems Running Puppet Once For Passenger Installation - Certificates Disappear

[Felix Frank]

Hi,

On 04/25/2013 04:31 PM, Philip Gardner wrote:
> notice:
> /Stage[main]/Puppet::Config::Master/Exec[run_puppet_once]/returns:
> executed successfully
> notice:
> /Stage[main]/Puppet::Config::Master/Apache::Vhost[puppetmasterd]/File[/var/log/httpd]/mode:
> mode changed '0700' to '0755'
> notice:
> /Stage[main]/Puppet::Config::Master/Apache::Vhost[puppetmasterd]/File[/etc/puppet/rack/public]/ensure:
> created
> notice:
> /Stage[main]/Puppet::Config::Master/Apache::Vhost[puppetmasterd]/File[25-puppetmasterd.conf]/ensure:
> created
> err: /Stage[main]/Apache/Service[httpd]/ensure: change from stopped to
> running failed: Could not start Service[httpd]: Execution of
> '/sbin/service httpd start' returned 1:  at
> /tmp/vagrant-puppet/modules-0/apache/manifests/init.pp:37
> notice: /Stage[main]/Apache/Service[httpd]: Triggered 'refresh' from 51
> events
> notice: /Stage[main]/Puppet::Service/Service[puppet]/ensure: ensure
> changed 'stopped' to 'running'
> notice: /Stage[main]/Puppet::Service/Service[puppet]: Triggered
> 'refresh' from 1 events
> notice: Finished catalog run in 290.04 seconds
> 
> I've tried a number of different ways of running the puppet agent by
> hand to get this to work, and all fail; the certificate request is
> signed by the ca but the /var/lib/puppet/ssl directory is never created,
> and thus we get a mismatch when the puppet agent actually does run.

Humm, so the above agent output is from a puppet agent run on
master.dev.local? Against the ca.dev.local? Or which master compiles the
catalog?

I just can't see how that agent runs without storing the certificat in
/var/lib/puppet. Any funny settings in puppet.conf on that node perchance?

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.