date:20131121

Yep, write it out as such :)  Either if/then in the manifest, or write a custom 
function that iterates through all ipaddress facts.

On Nov 21, 2013, at 4:32 AM, cko  wrote:
> I'm currently trying to solve the following problem:
> 
> I wrote a module that matches the "$ipaddress" fact for certain IP subnets 
> (like 20.20.2... or 30.30.2..). Depending on the subnet, the variable 
> $proxy-server changes.
> 
> The problem is, that some of our physical machines have a random number of 
> interfaces connected to many different subnets. In some cases the $ipadddress 
> fact returns the correct subnet, lets call it "production server lan" and 
> some don't.
> 
> Is there any way to make puppet check every available NIC for a specific 
> subnet/ regex? Something like this:
> 
> if $ipaddress_eth* =~ /^20\.20\.\..*$/ {
>$proxy-server = foo 
> }
> . 
> 
> -- 
> 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/9e5f1c49-cf71-4eab-a11b-18a9d31b5b0a%40googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.

-- 
Jo Rhett
Net Consonance : net philanthropy to improve open source and internet projects.

Author of Instant Puppet 3 Starter: 
http://www.netconsonance.com/instant-puppet-3-starter-book/



-- 
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/7B5FCEB5-C6F4-46D2-A928-12D717276683%40netconsonance.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Problem with Passenger

On Nov 18, 2013, at 12:52 PM, Marcelo Frota  wrote:
> I having problem with passenger module, i create the config file 
> /usr/share/puppet/rack/puppetmasterd/config.ru  but 
> the process master the puppet is not running . 
> For what seems apache is not recognizing the file config.ru

I don't believe that this directory is an expected path for apache, is it?  
That's an example file you copy to the apache config directory...

-- 
Jo Rhett
Net Consonance : net philanthropy to improve open source and internet projects.

Author of Instant Puppet 3 Starter: 
http://www.netconsonance.com/instant-puppet-3-starter-book/



-- 
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/764E3267-879C-41DE-8F75-5C7E32C8BE36%40netconsonance.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Announce: Hiera 1.3.0 Available

2013-11-21 Thread Melissa Stone

Hiera 1.3.0
---
Released November 21, 2013

RC2: November 8, 2013 -- Reverted #18577
RC1: October 29, 2013 -- Problems came up functional-testing on ticket
#18577, which caused us to revert it, so this build never got pushed.

For the full list of closed issues specific to Hiera 1.3.0 see
http://projects.puppetlabs.com/versions/427.


Hiera 1.3.0 Downloads
--
Source: https://downloads.puppetlabs.com/hiera/hiera-1.3.0.tar.gz

Available in native package format in the pre-release repositories at:
http://yum.puppetlabs.com and http://apt.puppetlabs.com

For information on how to enable the Puppet Labs repos, see:
http://docs.puppetlabs.com/guides/puppetlabs_package_repositories.html#open-source-repositories

Gems are available via rubygems at
https://rubygems.org/downloads/hiera-1.3.0.gem
  or by using `gem install hiera`

Mac packages are available at
https://downloads.puppetlabs.com/mac/hiera-1.3.0.dmg

Please report feedback via the Puppet Labs Redmine site, using an
affected hiera version of 1.3.0:
https://projects.puppetlabs.com/projects/hiera/



Hiera 1.3.0 release notes
---

New features


Most of the features contributed to Hiera 1.3 are intended to provide more
power by allowing new kinds of variable interpolation.

- Keys to YAML hashes can now contain interpolation syntax (#20220)

- You can now use `%{scope('variable_name')}` as a synonym for
  `%{variable_name}` and `%{hiera('variable_name')}` to trigger a Hiera
lookup
  from inside Hiera data.  (We call this Hiera-ception) (#21367)

Feature #20220: Interpolate hash keys
Feature #20755: Add Pretty Print to command line hiera output
Feature #21367: Add support for a hiera variable syntax which interpolates
data by performing a hiera lookup

Better error handling and correctness fixes
---

There are also quite a few error handling changes, most of which had
previously
caused silent or unattributable error messages.

Bug #17094: hiera can end up in and endless loop with malformed lookup
variables
Bug #20519: small fix in hiera/filecache.rb
Bug #20645: syntax error cause nil
Bug #21669: Hiera.yaml will not interpolate variables if datadir is
specified as an array
Bug #22777: YAML and JSON backends swallow errors
Feature #21211: Hiera crashes with an unfriendly error if it doesn't have
permission to read a yaml file

Build/Packaging fixes and improvements
--

We are now building Hiera packages for Ubuntu Saucy, which previously was
unable to use Puppet because a matching Hiera package couldn't be built.
Older
Fedora 17 is no longer supported and hardcoded hostnames in
build_defaults.yaml
were removed.

Bug #22166: Remove hardcoded hostname dependencies
Bug #22239: Remove Fedora 17 from build_defaults.yaml
Bug #22905: Quilt not needed in debian packaging
Bug #22924: Update packaging workflow to use install.rb
Feature #14520: Hiera should have an install.rb


Hiera 1.3.0 Contributors
--
Adrien Thebo, Andrew Parker, Bruno Léon, Eric Sorenson, Erik Dalén, Florian
Anderiasch, Gerardo Santana, Jeff McCune, Jesse Hathaway, Josh Partlow,
Matthaus Owens, Melissa Stone, Moses Mendoza, Scott Schneider, Stef T,
Thomas Hallgren, bob, nhuisman

Hiera 1.3.0 Changelog

Adrien Thebo (1):
  41181fb Revert "Merge pull request #137 from
lollipopman/add_hiera_lookup"

Andrew Parker (5):
  a1810b7 (#17094) Ensure that a leading $ resolves
  6314cbb (Maint) Add heira to Gemfile so that you can run it
  dbfedb4 (Maint) Clean up specs
  8113855 (#22142) Ensure that :datadir is a String
  d81a600 (#22777) Propagate errors from cached files

Bruno Léon (1):
  e109ce8 Interpolate hash keys like already done for strings.

Eric Sorenson (1):
  a749895 (#20519) Fix formatting typo in debug output

Erik Dalén (2):
  3165eeb (#21211) Fix format string
  6946bef (#21211) Raise a error on failed reading of cache

Florian Anderiasch (2):
  d516dda Fixed configuration example consistency problem
  c40ae07 And one more line inconsistent

Gerardo Santana (2):
  dffb48d Fix for issue#20645
  1ecd621 spec fix for for issue#20645

Jeff McCune (2):
  8dd0a55 (maint) Fix gemspec version
  e70c1c7 (maint) Fix gemspec version

Jesse Hathaway (11):
  f62f660 Add support for a hiera variable syntax which interpolates
data by performing a hiera lookup
  b39db81 Change hiera and scope lookup syntax to use a single sigil
for interpolation
  6cd4845 Remove trailing whitespace in deep merge comment
  981de92 Set backends to nil before loading a backend
  1461832 Add support for a hiera variable syntax which interpolates
data by performing a hiera lookup:
  4f683c4 Collapse SCOPE_INTERPOLATION & HIERA_INTERPOLATION into a
single regex

Re: [Puppet Users] package conflict resolution method:

On Tuesday, November 19, 2013 1:48:26 PM UTC-6, Matt Simmons wrote:
>
> Hi John, 
>
> I'm new around here, but I'm also in the same situation as Tom, who 
> started this thread. 
>
> I was wondering if you could expound a little bit on the better solution 
> that you mention. I write what I could refer to as "third grade puppet", 
> but I'd like to get better. 
>
> When you suggest factoring out these resources into separate classes and 
> modules, do you mean that, in essence, all possibly-shared resources should 
> be in discrete modules or classes? How does that jive with modules included 
> from Puppet Forge? Doesn't that mean refactoring everything you include 
> there, as well? 
>

I do not mean that possibly-shared resources must necessarily go into their 
own tiny classes, though that would be one way to go about it.  I mean that 
any given resource must belong to exactly one module, in such a way that 
using the module via its public-facing classes and types cannot by itself 
cause multiple declaration.

The module owning any particular resource might reasonably be one obtained 
from the Forge, or it might be a home-grown one.  That multiple modules 
might attempt to own the same resource is a thorny and longstanding module 
compatibility issue -- two modules that both attempt to own the same 
resource are not compatible.  Such a pair can be rendered compatible either 
by making one module depend on the other for the resource, or by making 
both depend on some third module for it.  Needless to say, that involves 
modifying one or both of the modules.

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/15b590a6-0fb1-4ffe-8ce0-222fc4beb49c%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Purging of ssh_authorized_keys

I agree with much of what Felix said here. Most importantly, John's "every 
possible file everywhere" is more than a bit extreme. (sorry, John :D ) I 
actually think that something even more limited than what Felix suggested would 
solve most desires. I believe that purging unlisted SSH keys for all users 
puppet is explicitly set to manage would solve 90% if not much more of the 
problem.

In essence, manage SSH keys for users which Puppet has defined. This fits 
cleanly within the Puppet model and doesn't cause unexpected behavior. This is 
a perfectly reasonable target and would solve most complaints. People who want 
all users to have their SSH keys purged would put all users in their manifests 
:D

On Nov 21, 2013, at 12:39 PM, Felix Frank  
wrote:
> I'm forking this thread from a cron discussion on the development list.
> I feel that the exchange of design ideas regarding the much requested
> cleaning of authorized ssh public keys is of interest to the base of
> (potential) users and is not (yet) closely related to implementation
> details.
> 
> On 11/21/2013 09:10 PM, John Bollinger wrote:
>> 
>>There is a similar request for ssh_authorized_keys, which is
>>just about
>>at the top of the highly voted issues (see [2]).
>> 
>> 
>> 
>> There are indeed similarities here with Ssh_authorized_key, but also
>> some important differences.  Consider that Ssh_authorized_key can
>> manage any file as a keystore (see the 'target' parameter).  As such,
>> it is flatly impossible for Puppet to reliably determine from which
>> files it must purge keys to zap them all without collateral damage. 
>> Puppet could be conservative by only purging from files having the
>> standard name, but if Ssh_authorized_key.target has any use in the
>> first place then a conservative purge would miss some keys in some
>> environments.  I think it would be worse to provide a key purging
>> feature that doesn't do the full job than to omit key purging altogether.
> 
> I think we can agree that "clearing all public keys from all files" is
> out of the question. It cannot and should not be the goal in my opinion.
> 
> For the vast majority of users, it will be important that the "active"
> keys are accounted for, i.e. such keys that are installed in
> authorized_keys files which will be read by an sshd to find trusted
> public keys.
> 
> Taking this perspective, using the default location would be a fair
> start indeed. I can think of two ways of extending that approach.
> 
> 1. Try to locate and interpret the system-wide sshd configuration. Find
> the actual location(s) used for authorized keys files.
> 
> 2. Add a parameter (to the resources type?) that allows to override the
> default location of a user's authorized keys file. Think resources {
> "ssh_authorized_key": purge => true, location => "%h/.ssh_hidden/keys" }.
> 
> Both approaches could also be combined, of course.
> 
> There will always be limitations, e.g. we cannot protect the admin from
> users (or other admins) running additional sshd instances with different
> configurations. But doing so would be well beyond the scope of what I,
> as a user, would expect from puppet.
> 
>> I think a more feasible reference model for key purging is the one
>> provided by recursively-managed Files.  Essentially, there is a
>> container (a File resource) that establishes the scope of the purge. 
>> There is not currently a suitable container type for authorized keys,
>> but one could certainly be created, say Ssh_authorized_keyfile or
>> Ssh_authorized_keys.
> 
> I can see how this would be more in the spirit of puppet design than
> what I sketched above. But wouldn't this require the manifest designer
> to enumerate all key files after all?
> 
> That's quite a limitation, because usually (see user, group) purging
> resources is expected to act specifically upon resources that are not
> covered by the manifest at all.
> 
> I can see scenarios where such a feature would be useful, e.g. in a
> defined type that manages all aspect of a user account, their authorized
> keys file could be added to the list. However, if the manifest design
> allows for such convenience, it will also easily allow workarounds such
> as handling the key files via the concat module or just adding a dummy
> for each user in order to allow the current purging mechanism to apply.
> This makes me question the value of such a container type.
> 
> Best regards,
> 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/528E6F92.6050601%40Alumni.TU-Berlin.de.
> For more options, visit https://groups.google.com/groups/opt_out.

-- 
Jo Rhett
Net Consonance : net philanthropy to improve open source and internet projects.

Re: [Puppet Users] cannot find puppet_node_classifier

2013-11-21 Thread Martin Alfke

Hi,

ENC description from puppetlabs can be found here:
http://docs.puppetlabs.com/guides/external_nodes.html

Or search/google for "puppet enc examples"
you will find sites like this:
https://github.com/rmt/puppetenc-ruby
http://wiki.unixh4cks.com/index.php/Simple_External_Node_Classifier%28ENC%29_for_puppet_in_python
http://seriousbirder.com/blogs/puppet-master-external-node-classifier/

hth,

Martin

On 21 Nov 2013, at 15:49, shlo.af...@gmail.com wrote:

> Is there good website i can read about it more?
> 
> On Thursday, November 21, 2013 4:20:34 PM UTC+2, jcbollinger wrote:
> 
> 
> On Thursday, November 21, 2013 7:00:24 AM UTC-6, shlo@gmail.com wrote:
> Do I need to install something special for that or it came with Puppet?
> 
> 
> 
> It is essentially a Puppet extension point.  There are programs that provide 
> a suitable node classifier (Foreman, Dashboard), but a lot of people write 
> their own.  The whole point is that the program to which you point must 
> output appropriate details specific to the nodes of your site.  If you don't 
> know what this is about then you really should shelve the idea for now.
> 
> 
> 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/4dce398c-1f23-4d81-98b4-86667fd7b283%40googlegroups.com.
> 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/C92F580E-3089-4831-BA76-3DE52BA39AE8%40gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Could not find parent resource type



On Thursday, November 21, 2013 6:07:26 AM UTC-6, Johan De Wit wrote:
>
> And to make autoloading work : 
>
> ...modules/myclass/init.pp 
>   /params.pp 
>
>

Make that
  modules/myclass/*manifests*/init.pp
and
  modules/myclass/*manifests*/params.pp
 

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/43c0cc9f-06b5-4cc5-ad29-e744f611bf0b%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Problem with Passenger

Marcelo,

well, have you made sure that apache is configured correctly according
to the documentation?

I.e. http://docs.puppetlabs.com/guides/passenger.html

I advise to restart apache and keep an eye on its log files.

HTH,
Felix

On 11/21/2013 02:07 PM, Marcelo Frota wrote:
> Hi Felix, 
> 
> My archive config.ru is equal to the file that you spoke. 
> 
> Do you have other sugestion, for the my problem ? 
> 
> Regards
> Marcelo Frota

-- 
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/528E06B2.80401%40alumni.tu-berlin.de.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Re: Could not find parent resource type

Just a quick remark: If anonymisation is an issue for you, you should
definitely go back to pastebin and anynonymise the code there as well.

I notice some anti-patterns, but nothing stands out to me that should
make the agent fail like that...

Cheers,
Felix

On 11/21/2013 01:26 PM, Raj kumar V wrote:
> Warning: Scope(Class[<>]): Could not look up qualified variable
> '<>::params::<>_APIkey'; class <>::params could not be found
> 
> Warning: Scope(Class[<>]): Could not look up qualified variable
> '<>::params::<>_APIkey'; class <>::params could not be found
> Error: Could not find class site24x7::params for 

-- 
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/528DFEF3.8010706%40alumni.tu-berlin.de.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] cannot find puppet_node_classifier

On Thursday, November 21, 2013 7:00:24 AM UTC-6, shlo@gmail.com wrote:
>
> Do I need to install something special for that or it came with Puppet?
>
>

It is essentially a Puppet extension point.  There are programs that 
provide a suitable node classifier (Foreman, Dashboard), but a lot of 
people write their own.  The whole point is that the program to which you 
point must output appropriate details specific to the nodes of your site.  
If you don't know what this is about then you really should shelve the idea 
for now.

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/5422693a-7f83-4365-8dd1-4ea9976530b3%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Purging of ssh_authorized_keys

Hi,

I'm forking this thread from a cron discussion on the development list.
I feel that the exchange of design ideas regarding the much requested
cleaning of authorized ssh public keys is of interest to the base of
(potential) users and is not (yet) closely related to implementation
details.

On 11/21/2013 09:10 PM, John Bollinger wrote:
>
> There is a similar request for ssh_authorized_keys, which is
> just about
> at the top of the highly voted issues (see [2]).
>
>
>
> There are indeed similarities here with Ssh_authorized_key, but also
> some important differences.  Consider that Ssh_authorized_key can
> manage any file as a keystore (see the 'target' parameter).  As such,
> it is flatly impossible for Puppet to reliably determine from which
> files it must purge keys to zap them all without collateral damage. 
> Puppet could be conservative by only purging from files having the
> standard name, but if Ssh_authorized_key.target has any use in the
> first place then a conservative purge would miss some keys in some
> environments.  I think it would be worse to provide a key purging
> feature that doesn't do the full job than to omit key purging altogether.

I think we can agree that "clearing all public keys from all files" is
out of the question. It cannot and should not be the goal in my opinion.

For the vast majority of users, it will be important that the "active"
keys are accounted for, i.e. such keys that are installed in
authorized_keys files which will be read by an sshd to find trusted
public keys.

Taking this perspective, using the default location would be a fair
start indeed. I can think of two ways of extending that approach.

1. Try to locate and interpret the system-wide sshd configuration. Find
the actual location(s) used for authorized keys files.

2. Add a parameter (to the resources type?) that allows to override the
default location of a user's authorized keys file. Think resources {
"ssh_authorized_key": purge => true, location => "%h/.ssh_hidden/keys" }.

Both approaches could also be combined, of course.

There will always be limitations, e.g. we cannot protect the admin from
users (or other admins) running additional sshd instances with different
configurations. But doing so would be well beyond the scope of what I,
as a user, would expect from puppet.

> I think a more feasible reference model for key purging is the one
> provided by recursively-managed Files.  Essentially, there is a
> container (a File resource) that establishes the scope of the purge. 
> There is not currently a suitable container type for authorized keys,
> but one could certainly be created, say Ssh_authorized_keyfile or
> Ssh_authorized_keys.

I can see how this would be more in the spirit of puppet design than
what I sketched above. But wouldn't this require the manifest designer
to enumerate all key files after all?

That's quite a limitation, because usually (see user, group) purging
resources is expected to act specifically upon resources that are not
covered by the manifest at all.

I can see scenarios where such a feature would be useful, e.g. in a
defined type that manages all aspect of a user account, their authorized
keys file could be added to the list. However, if the manifest design
allows for such convenience, it will also easily allow workarounds such
as handling the key files via the concat module or just adding a dummy
for each user in order to allow the current purging mechanism to apply.
This makes me question the value of such a container type.

Best regards,
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/528E6F92.6050601%40Alumni.TU-Berlin.de.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Puppet Masterless on Windows

2013-11-21 Thread Rob Reynolds

I would be explicit about telling vagrant where your modules folder is.
e.g.
https://github.com/ferventcoder/vagrant-windows-puppet/blob/master/boxes/win2008r2x64-vagrant/Vagrantfile#L34


On Thu, Nov 21, 2013 at 12:16 AM, Roger Yu  wrote:

> yes i installed vagrant windows version and use vagrant provision command
> to trigger puppet provisioner
> and as I mentioned above, manifest file base-hadoop.pp works fine, just
> init.pp under modules folder was not called
>
>
> Rob Reynolds於 2013年11月19日星期二UTC-8上午9時08分24秒寫道：
>>
>> For vagrant, are you kicking off the commands with the vagrant puppet
>> provisioner? And are you using vagrant-windows plugin?
>>
>>
>> On Tue, Nov 19, 2013 at 8:28 AM, Felix Frank > de> wrote:
>>
>>> Hi,
>>>
>>> I haven't played with Vagrant, but your wording makes me ask:
>>>
>>> Is there indeed an agent (as in `puppet agent` as opposed to `puppet
>>> apply`) at work? Because that will never use a manifest from your local
>>> machine. Puppet agent has the sole purpose of connecting to a master.
>>>
>>> Cheers,
>>> Felix
>>>
>>> On 11/18/2013 09:28 PM, Spencer Thomason wrote:
>>> > Hi all,
>>> >
>>> > I have been working on a configuration of a Masterless configuration on
>>> > Windows.  I am able to get individual jobs to run like:
>>> >
>>> > puppet apply 
>>> >
>>> > However, I would like to spin up the Vagrant box off a base VM, and
>>> have
>>> > a puppet manifest file in a location where puppet knows to look and
>>> > provision based off that file.  The obvious place seems to be
>>> > C:\ProgramData\PuppetLabs\puppet\etc on Windows.  However, I can't
>>> seem
>>> > to get the agent configured right to look at a manifest file in that
>>> > directory or another directory.
>>> >
>>> > Can someone provide some steps that I am missing for a "hello world"
>>> > type puppet configuration for what I am talking about above?
>>> >
>>> > Thanks!
>>> >
>>> > Spencer
>>>
>>> --
>>> 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...@googlegroups.com.
>>> To view this discussion on the web visit https://groups.google.com/d/
>>> msgid/puppet-users/528B7570.9070503%40alumni.tu-berlin.de.
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>
>>
>>
>>
>> --
>> Rob Reynolds
>> Developer, Puppet Labs
>>
>> Join us at PuppetConf 2014, September 23-24 in San Francisco
>>
>  --
> 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/6d7a58d1-b1c3-4e06-bcc8-9fc0bfacb68b%40googlegroups.com
> .
>
> For more options, visit https://groups.google.com/groups/opt_out.
>



-- 
Rob Reynolds
Developer, Puppet Labs

Join us at PuppetConf 2014, September 23-24 in San Francisco

-- 
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/CAMJiBK6G6fSLbM4%2B8e-E7OS7YZcWo8aiEF4bye%2BANtMT_Q-esA%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Exported resource resolving oddly

2013-11-21 Thread Ken Barber

> I'm trying my hand at my first exported resource. In fact, this comes from
> converting an older resource to an exported one, which might explain the
> problem
>
> Currently, I have two classes:
>
> class yum {
>File <<| tag == 'repofile' |>> ~> Exec['yum clean all']
>:
> }
>
> class yum::foo {
>include yum
>@@file { 'foo-yum':
>   tag => 'repofile',
>   path => '/etc/yum.repos.d/foo.repo',
>   ensure => file,
>   source => 'puppet:///modules/yum/foo.repo',
>}
> }
>
> When I try to run this by including yum::foo in a class, I get this error:
>
> Error: Could not retrieve catalog from remote server: Error 400 on SERVER:
> Another local or imported resource exists with the type and title
> File[foo-repofile] on node osem2.foo.net
> Warning: Not using cache on failed catalog
> Error: Could not retrieve catalog; skipping run
> #
>
> So I go looking for anything containing foo-repofile:
>
> # cd /etc/puppet/modules && find . -type f | xargs grep foo-repofile
> #
>
> ORIGINALLY, this resource was called foo-repofile, but at that time, it was
> in a different module and wasn't exported. How can I purge that from
> PuppetDB so it gets over it and lets me use this new one? Or is the the
> problem somewhere or something else?

So this is a duplicate exported resource. Something in your content
has created this scenario at some time, and its usually either a)
genuine, you really have exported the same type/title combination
twice from two nodes, and are now collecting it onto one, a constraint
violation or b) an old node has exported this in the past, and that
node has not been deactivated.

The trick is to figure out how to debug these issues, since they are
often quite solveable.

Zach Smith has created a tool for analyzing what has been exported to
PuppetDB: http://forge.puppetlabs.com/zack/exports and this is a great
start.

You can also query this manually yourself:

$ curl 'http://localhost:8080/v3/resources?query=\["=","exported",true\]'

In general, the trick to avoid this error is to make sure the types
you export can never collide. In your code:

@@file { 'foo-yum':
  path => '/etc/yum.repos.d/foo.repo',
}

... you are exporting something with a very fixed title and namevar
(foo-yum and path respectively) ... basically if two nodes export
this, you will always get a collision on the collecting host, so the
pattern you have will only work if there is 1 export, or if you pin
the collection query to the node that exported it.

To be honest though - exported resources might not be appropriate for
this yum repo use case anyway, although perhaps I don't see it :-).
Can you explain why you are trying to use exported resources for this
purpose?

ken.

-- 
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/CAE4bNTmXwwyYwBG6aR9cNc%2BjS_MzLvoaeBaOSPT5XhCkwSQxFw%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Puppet Dashboard with Passenger - 500 Internal Server Error (Mysql::Error: Can't create/write to file Errcode: 13)

2013-11-21 Thread Jason Friedrich


Distribution: Ubuntu 12.04.3
Ruby version: ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux]
Gem version: 1.8.15
Puppet version: 3.3.2-1puppetlabs1 (Puppetlabs apt repo)
Puppet Dashboard: 1.2.23-1puppetlabs1 (Puppetlabs apt repo)


I have successfully set up a puppet master, with two agents and the 
Puppet Dashboard following the instructions from the puppetlabs web 
site. When I use the internal, built-in web server, everything seems to 
work fine. Even though the init scripts in the Ubuntu packages seem to 
have a bug or two, it worked fine for me.


Now I wanted to move everything to the apache web server, as a test for 
a bigger environment later. The puppetmaster was easily set up, the 
puppetmaster-passenger deb works really great, like a charm.


With the install/config of the Puppet Dashboard in Apache2 I have more 
problems. I have edited the settings.yml file 
(http://pastebin.com/UUDKaJTi) and the database.yml 
(http://pastebin.com/mpznUhdQ) to configure the Dashboard and the MySQL 
database I use. I have copied the config.ru 
(http://pastebin.com/myZzrA9p) file to the /usr/share/puppet-dashboard 
directory and created the Apache configuration 
(http://pastebin.com/XDpSkvbk).


When I try to hit the site though, I am getting the message "Puppet 
Dashboard encountered an error. Something went wrong, and Puppet 
Dashboard was unable to render the requested page [...]" and a strange 
errror output in the production.log file (http://pastebin.com/aYYBRkEX).


I do not understand why Puppet Dashboard tries to create a MYI file in 
/tmp. It should not create anything locally at all. It should use the 
configured MySQL server.


When I execute

rake RAILS_ENV=production db:migration

in the Puppet Dashboard Directory, I get the same the same error. All 
these settings worked fine when I used the built-in Webrick, so I do not 
quite understand why this happens right now.


Hope that someone can help and put me on the right track.

Thanks,
-Jason

--
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/528E378A.9040700%40probytes.eu.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Exported resource resolving oddly

I think you're right. Thanks, John and Ken for helping get me straightened
out.



*Bret Wortman*
http://about.me/wortmanbret



On Thu, Nov 21, 2013 at 1:52 PM, jcbollinger wrote:

>
>
> On Thursday, November 21, 2013 10:29:37 AM UTC-6, Bret Wortman wrote:
>>
>> Wait -- so this collects every occurrence thoughout the database, not
>> just for the system being processed?
>>
>
>
> Yes, that's the point of exported resources.  They allow resources the
> catalog compilation process for one node's catalog to emit resource
> declarations that are available for incorporation into ANY node's catalog.
> It only makes sense to do this with resources that are in some way specific
> to the exporting node.  The canonical example is Host resources -- if each
> node exports a Host resource describing itself and collects all the
> exported Hosts, then all managed nodes will end up with /etc/hosts files
> listing (at least) all managed nodes.
>
>
>
>> I think the word "node" was tripping me up in the online documentation --
>> I was reading "node" and thinking "resource". Okay, I get it now, and
>> you're absolutely right -- this is a terrible use of exported resources. I
>> think what I was looking for was virtual, not exported, resources.
>>
>>
>
> No, I think you were just looking for collections.  You can use them with
> ordinary (non-virtual) resources.  If you are not already using virtual
> resources to manage the Yum repos then I don't see what advantage you would
> obtain by converting your ordinary resources to virtual ones.
>
>
> John
>
>  --
> 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/zNFaLT3tf3Q/unsubscribe.
> To unsubscribe from this group and all its topics, 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/8f851721-c4f2-44e8-97ad-5e68afd8581d%40googlegroups.com
> .
>
> 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAN9oxgS-JRyOCr%2BLFQmvEMQxgbh6LkHr0mT4UFo9Wbm5tsCy-w%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Weird Error From Running Puppet

2013-11-21 Thread MM

So I had this confuse error message when running puppet via Vagrant puppet 
provisioner with Puppet 3.3.2 and Data in Module














*Error: Could not run: Could not find file trueThe following SSH command 
responded with a non-zero exit status.Vagrant assumes that this means the 
command failed!puppet apply --binder true --ordering manifest --modulepath 
'/etc/puppet/modules:/tmp/vagrant-puppet/modules-0' --manifestdir 
/tmp/vagrant-puppet/manifests --detailed-exitcodes 
/tmp/vagrant-puppet/manifests/default.pp || [ $? -eq 2 ]Stdout from the 
command:Stderr from the command:Error: Could not run: Could not find file 
true*

Here my file layout,

.
├── Gemfile
├── Gemfile.lock
├── Rakefile
├── Vagrantfile
├── data
│   ├── environment
│   └── node
├── hiera.yaml
├── puppet
│   ├── Puppetfile
│   ├── manifests
│   └── modules
└── r10k.yaml

Vagrant is configured to run puppet as following,

  config.vm.define 'mysql_server' do | mysql |
mysql.vm.hostname = 'mysql-server.local'
mysql.vm.provision :puppet do | puppet |
  puppet.options = [
'--binder true',
'--ordering manifest',
  ]
  puppet.manifests_path = 'puppet/manifests'
  puppet.manifest_file  = 'default.pp'
  puppet.module_path= 'puppet/modules'
end

So my question is what does error message mean?  Do I need to tell puppet 
where to look hiera.yaml anywhere in host or guest?

Thanks,
-wd

-- 
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/5a33e4a4-b341-4250-bbfb-5fb7a98674b5%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Puppet and scripts.

2013-11-21 Thread Daniel Lyons

So I knew the script took a while but I thought to myself: "No way does it 
take 5 minutes." Sure enough I dropped the timeout and it finishes. 312 
seconds...
 
Also I understand now that the log is posted in full AFTER the script runs, 
so that's why I wasn't seeing any of the echo outputs at all after the 
timeout fail.
 
I needed that second brain to see a goof like that, highly appriciate 
it Andreas.

On Thursday, November 21, 2013 10:33:41 AM UTC-8, Andreas Ntaflos wrote:

> On 2013-11-21 19:08, Daniel Lyons wrote: 
> > We've got a decently complicated .sh script used to set up oracle 
> > database, inlcuding partioning and the like. If I attempt to run it 
> > through puppet the script will end after 300 seconds as timed out. To 
> > test a simpler case I just made a little script as such: 
>
> Exec has a timeout parameter: 
>
> http://docs.puppetlabs.com/references/latest/type.html#exec-attribute-timeout
>  
>
> HTH 
>
> 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/aef74b71-7690-4bf2-b2ff-6b63b633d34a%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Exported resource resolving oddly

Wait -- so this collects every occurrence thoughout the database, not just
for the system being processed? I think the word "node" was tripping me up
in the online documentation -- I was reading "node" and thinking
"resource". Okay, I get it now, and you're absolutely right -- this is a
terrible use of exported resources. I think what I was looking for was
virtual, not exported, resources.



*Bret Wortman*
http://about.me/wortmanbret



On Thu, Nov 21, 2013 at 11:15 AM, Bret Wortman  wrote:

> The curl command, incidentally, returned nothing on the server, and
> errored on the client when typed in verbatim. And from the client, when I
> changed "localhost" to the name of the puppet master, I got a "curl (7):
> couldn't connect to host" error. I'll try Zach's tool next.
>
>
>
> *Bret Wortman*
> http://about.me/wortmanbret
>
>
>
> On Thu, Nov 21, 2013 at 10:53 AM, Ken Barber  wrote:
>
>> > I'm trying my hand at my first exported resource. In fact, this comes
>> from
>> > converting an older resource to an exported one, which might explain the
>> > problem
>> >
>> > Currently, I have two classes:
>> >
>> > class yum {
>> >File <<| tag == 'repofile' |>> ~> Exec['yum clean all']
>> >:
>> > }
>> >
>> > class yum::foo {
>> >include yum
>> >@@file { 'foo-yum':
>> >   tag => 'repofile',
>> >   path => '/etc/yum.repos.d/foo.repo',
>> >   ensure => file,
>> >   source => 'puppet:///modules/yum/foo.repo',
>> >}
>> > }
>> >
>> > When I try to run this by including yum::foo in a class, I get this
>> error:
>> >
>> > Error: Could not retrieve catalog from remote server: Error 400 on
>> SERVER:
>> > Another local or imported resource exists with the type and title
>> > File[foo-repofile] on node osem2.foo.net
>> > Warning: Not using cache on failed catalog
>> > Error: Could not retrieve catalog; skipping run
>> > #
>> >
>> > So I go looking for anything containing foo-repofile:
>> >
>> > # cd /etc/puppet/modules && find . -type f | xargs grep foo-repofile
>> > #
>> >
>> > ORIGINALLY, this resource was called foo-repofile, but at that time, it
>> was
>> > in a different module and wasn't exported. How can I purge that from
>> > PuppetDB so it gets over it and lets me use this new one? Or is the the
>> > problem somewhere or something else?
>>
>> So this is a duplicate exported resource. Something in your content
>> has created this scenario at some time, and its usually either a)
>> genuine, you really have exported the same type/title combination
>> twice from two nodes, and are now collecting it onto one, a constraint
>> violation or b) an old node has exported this in the past, and that
>> node has not been deactivated.
>>
>> The trick is to figure out how to debug these issues, since they are
>> often quite solveable.
>>
>> Zach Smith has created a tool for analyzing what has been exported to
>> PuppetDB: http://forge.puppetlabs.com/zack/exports and this is a great
>> start.
>>
>> You can also query this manually yourself:
>>
>> $ curl 'http://localhost:8080/v3/resources?query=\["=","exported",true\]'
>>
>> In general, the trick to avoid this error is to make sure the types
>> you export can never collide. In your code:
>>
>> @@file { 'foo-yum':
>>   path => '/etc/yum.repos.d/foo.repo',
>> }
>>
>> ... you are exporting something with a very fixed title and namevar
>> (foo-yum and path respectively) ... basically if two nodes export
>> this, you will always get a collision on the collecting host, so the
>> pattern you have will only work if there is 1 export, or if you pin
>> the collection query to the node that exported it.
>>
>> To be honest though - exported resources might not be appropriate for
>> this yum repo use case anyway, although perhaps I don't see it :-).
>> Can you explain why you are trying to use exported resources for this
>> purpose?
>>
>> ken.
>>
>> --
>> 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/zNFaLT3tf3Q/unsubscribe.
>> To unsubscribe from this group and all its topics, 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/CAE4bNTmXwwyYwBG6aR9cNc%2BjS_MzLvoaeBaOSPT5XhCkwSQxFw%40mail.gmail.com
>> .
>> 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAN9oxgRFQYL5eOs8XE%2BMBmjje0mv7%3DJgJJBACipwarA%3Dk4y2%3Dg%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Exported resource resolving oddly

I'm trying my hand at my first exported resource. In fact, this comes from 
converting an older resource to an exported one, which might explain the 
problem

Currently, I have two classes:

class yum {
   File <<| tag == 'repofile' |>> ~> Exec['yum clean all']
   :
}

class yum::foo {
   include yum
   @@file { 'foo-yum':
  tag => 'repofile',
  path => '/etc/yum.repos.d/foo.repo',
  ensure => file,
  source => 'puppet:///modules/yum/foo.repo',
   }
}

When I try to run this by including yum::foo in a class, I get this error:

Error: Could not retrieve catalog from remote server: Error 400 on SERVER: 
Another local or imported resource exists with the type and title 
File[foo-repofile] on node osem2.foo.net
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run
#

So I go looking for anything containing foo-repofile:

# cd /etc/puppet/modules && find . -type f | xargs grep foo-repofile
# 

ORIGINALLY, this resource was called foo-repofile, but at that time, it was 
in a different module and wasn't exported. How can I purge that from 
PuppetDB so it gets over it and lets me use this new one? Or is the the 
problem somewhere or something else?

Thanks!


Bret

-- 
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/997d02b2-82bd-42af-8a3d-01522a4ee72f%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Exported resource resolving oddly

On Thursday, November 21, 2013 10:29:37 AM UTC-6, Bret Wortman wrote:
>
> Wait -- so this collects every occurrence thoughout the database, not just 
> for the system being processed?
>

Yes, that's the point of exported resources.  They allow resources the 
catalog compilation process for one node's catalog to emit resource 
declarations that are available for incorporation into ANY node's catalog.  
It only makes sense to do this with resources that are in some way specific 
to the exporting node.  The canonical example is Host resources -- if each 
node exports a Host resource describing itself and collects all the 
exported Hosts, then all managed nodes will end up with /etc/hosts files 
listing (at least) all managed nodes.

> I think the word "node" was tripping me up in the online documentation -- 
> I was reading "node" and thinking "resource". Okay, I get it now, and 
> you're absolutely right -- this is a terrible use of exported resources. I 
> think what I was looking for was virtual, not exported, resources.
>
>

No, I think you were just looking for collections.  You can use them with 
ordinary (non-virtual) resources.  If you are not already using virtual 
resources to manage the Yum repos then I don't see what advantage you would 
obtain by converting your ordinary resources to virtual ones.

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/8f851721-c4f2-44e8-97ad-5e68afd8581d%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Exported resource resolving oddly

It's partly to experiment with something I just learned, in all honesty.
But it's also because this is a resource that I only want on certain
systems, and after installing it (or any yum file for that matter), I want
to trigger a "yum clean all" so that puppet doesn't spin for a while before
yum finally discovers the new yumfile. So collecting it in the yum module
permits me to only have the "yum clean all" exec defined in one place,
triggered by the collection. And it permits me to add other,
system-specific and application-specific repos from time to time as needed
as well. These are usually put together by our developers, not repos that
we're trying to pull from the internet.

I'll readily admit it may not be the best use, but it's proving a good
learning experience.

I tried altering the title by embedding $hostname, but that didn't help.
What if I embed $title within the namevar instead, and changed title to be
the actual filename? I'll try that next



*Bret Wortman*
http://about.me/wortmanbret



On Thu, Nov 21, 2013 at 10:53 AM, Ken Barber  wrote:

> > I'm trying my hand at my first exported resource. In fact, this comes
> from
> > converting an older resource to an exported one, which might explain the
> > problem
> >
> > Currently, I have two classes:
> >
> > class yum {
> >File <<| tag == 'repofile' |>> ~> Exec['yum clean all']
> >:
> > }
> >
> > class yum::foo {
> >include yum
> >@@file { 'foo-yum':
> >   tag => 'repofile',
> >   path => '/etc/yum.repos.d/foo.repo',
> >   ensure => file,
> >   source => 'puppet:///modules/yum/foo.repo',
> >}
> > }
> >
> > When I try to run this by including yum::foo in a class, I get this
> error:
> >
> > Error: Could not retrieve catalog from remote server: Error 400 on
> SERVER:
> > Another local or imported resource exists with the type and title
> > File[foo-repofile] on node osem2.foo.net
> > Warning: Not using cache on failed catalog
> > Error: Could not retrieve catalog; skipping run
> > #
> >
> > So I go looking for anything containing foo-repofile:
> >
> > # cd /etc/puppet/modules && find . -type f | xargs grep foo-repofile
> > #
> >
> > ORIGINALLY, this resource was called foo-repofile, but at that time, it
> was
> > in a different module and wasn't exported. How can I purge that from
> > PuppetDB so it gets over it and lets me use this new one? Or is the the
> > problem somewhere or something else?
>
> So this is a duplicate exported resource. Something in your content
> has created this scenario at some time, and its usually either a)
> genuine, you really have exported the same type/title combination
> twice from two nodes, and are now collecting it onto one, a constraint
> violation or b) an old node has exported this in the past, and that
> node has not been deactivated.
>
> The trick is to figure out how to debug these issues, since they are
> often quite solveable.
>
> Zach Smith has created a tool for analyzing what has been exported to
> PuppetDB: http://forge.puppetlabs.com/zack/exports and this is a great
> start.
>
> You can also query this manually yourself:
>
> $ curl 'http://localhost:8080/v3/resources?query=\["=","exported",true\]'
>
> In general, the trick to avoid this error is to make sure the types
> you export can never collide. In your code:
>
> @@file { 'foo-yum':
>   path => '/etc/yum.repos.d/foo.repo',
> }
>
> ... you are exporting something with a very fixed title and namevar
> (foo-yum and path respectively) ... basically if two nodes export
> this, you will always get a collision on the collecting host, so the
> pattern you have will only work if there is 1 export, or if you pin
> the collection query to the node that exported it.
>
> To be honest though - exported resources might not be appropriate for
> this yum repo use case anyway, although perhaps I don't see it :-).
> Can you explain why you are trying to use exported resources for this
> purpose?
>
> ken.
>
> --
> 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/zNFaLT3tf3Q/unsubscribe.
> To unsubscribe from this group and all its topics, 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/CAE4bNTmXwwyYwBG6aR9cNc%2BjS_MzLvoaeBaOSPT5XhCkwSQxFw%40mail.gmail.com
> .
> 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAN9oxgRT_1amgPh63yqSNDbBQ1fGrGUP2QHxG7nfMK8sx34zgw%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] cannot find puppet_node_classifier

2013-11-21 Thread Jason Antman

As far as I know, "/usr/bin/puppet_node_classifier" is supposed to be
the path to your ENC script.

What ENC are you trying to use? Either your ENC documentation should
tell you how to configure this (Puppet Dashboard/Console, Foreman, etc.)
or if you're writing your own ENC, this should be the path to your node
terminus script.

On 11/21/2013 05:36 AM, shlo.af...@gmail.com wrote:

Hi,
I'm trying to learn configure puppet nodes using ENC. The instruction
tell to add to puppet.conf the line:

external_nodes = /usr/bin/puppet_node_classifier

I cannot find puppet_node_classifier anywhere in my system. I have
puppet 3.3.1 installed.

What I need to install in order to have it?
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/a66813f4-f0d6-4b8d-b792-d4910993c892%40googlegroups.com.

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 view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/528DFDB8.7000802%40jasonantman.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] cannot find puppet_node_classifier

2013-11-21 Thread shlo . afgin

Is there good website i can read about it more?

On Thursday, November 21, 2013 4:20:34 PM UTC+2, jcbollinger wrote:
>
>
>
> On Thursday, November 21, 2013 7:00:24 AM UTC-6, shlo@gmail.com wrote:
>>
>> Do I need to install something special for that or it came with Puppet?
>>
>>
>
> It is essentially a Puppet extension point.  There are programs that 
> provide a suitable node classifier (Foreman, Dashboard), but a lot of 
> people write their own.  The whole point is that the program to which you 
> point must output appropriate details specific to the nodes of your site.  
> If you don't know what this is about then you really should shelve the idea 
> for now.
>
>
> 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/4dce398c-1f23-4d81-98b4-86667fd7b283%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] cannot find puppet_node_classifier

2013-11-21 Thread shlo . afgin

Do I need to install something special for that or it came with Puppet?

On Thursday, November 21, 2013 2:34:00 PM UTC+2, Jason Antman wrote:
>
> As far as I know, "/usr/bin/puppet_node_classifier" is supposed to be 
> the path to your ENC script. 
>
> What ENC are you trying to use? Either your ENC documentation should 
> tell you how to configure this (Puppet Dashboard/Console, Foreman, etc.) 
> or if you're writing your own ENC, this should be the path to your node 
> terminus script. 
>
> On 11/21/2013 05:36 AM, shlo@gmail.com  wrote: 
> > 
> > 
> > Hi, 
> > I'm trying to learn configure puppet nodes using ENC. The instruction 
> > tell to add to puppet.conf the line: 
> > external_nodes = /usr/bin/puppet_node_classifier 
> > 
> > I cannot find  puppet_node_classifier anywhere in my system. I have 
> > puppet 3.3.1 installed. 
> > What I need to install in order to have it? 
> > 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...@googlegroups.com . 
> > To view this discussion on the web visit 
> > 
> https://groups.google.com/d/msgid/puppet-users/a66813f4-f0d6-4b8d-b792-d4910993c892%40googlegroups.com.
>  
>
> > 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/4b3404ef-70a1-4f0b-8a35-eb040801881d%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Exported resource resolving oddly

The curl command, incidentally, returned nothing on the server, and errored
on the client when typed in verbatim. And from the client, when I changed
"localhost" to the name of the puppet master, I got a "curl (7): couldn't
connect to host" error. I'll try Zach's tool next.



*Bret Wortman*
http://about.me/wortmanbret



On Thu, Nov 21, 2013 at 10:53 AM, Ken Barber  wrote:

> > I'm trying my hand at my first exported resource. In fact, this comes
> from
> > converting an older resource to an exported one, which might explain the
> > problem
> >
> > Currently, I have two classes:
> >
> > class yum {
> >File <<| tag == 'repofile' |>> ~> Exec['yum clean all']
> >:
> > }
> >
> > class yum::foo {
> >include yum
> >@@file { 'foo-yum':
> >   tag => 'repofile',
> >   path => '/etc/yum.repos.d/foo.repo',
> >   ensure => file,
> >   source => 'puppet:///modules/yum/foo.repo',
> >}
> > }
> >
> > When I try to run this by including yum::foo in a class, I get this
> error:
> >
> > Error: Could not retrieve catalog from remote server: Error 400 on
> SERVER:
> > Another local or imported resource exists with the type and title
> > File[foo-repofile] on node osem2.foo.net
> > Warning: Not using cache on failed catalog
> > Error: Could not retrieve catalog; skipping run
> > #
> >
> > So I go looking for anything containing foo-repofile:
> >
> > # cd /etc/puppet/modules && find . -type f | xargs grep foo-repofile
> > #
> >
> > ORIGINALLY, this resource was called foo-repofile, but at that time, it
> was
> > in a different module and wasn't exported. How can I purge that from
> > PuppetDB so it gets over it and lets me use this new one? Or is the the
> > problem somewhere or something else?
>
> So this is a duplicate exported resource. Something in your content
> has created this scenario at some time, and its usually either a)
> genuine, you really have exported the same type/title combination
> twice from two nodes, and are now collecting it onto one, a constraint
> violation or b) an old node has exported this in the past, and that
> node has not been deactivated.
>
> The trick is to figure out how to debug these issues, since they are
> often quite solveable.
>
> Zach Smith has created a tool for analyzing what has been exported to
> PuppetDB: http://forge.puppetlabs.com/zack/exports and this is a great
> start.
>
> You can also query this manually yourself:
>
> $ curl 'http://localhost:8080/v3/resources?query=\["=","exported",true\]'
>
> In general, the trick to avoid this error is to make sure the types
> you export can never collide. In your code:
>
> @@file { 'foo-yum':
>   path => '/etc/yum.repos.d/foo.repo',
> }
>
> ... you are exporting something with a very fixed title and namevar
> (foo-yum and path respectively) ... basically if two nodes export
> this, you will always get a collision on the collecting host, so the
> pattern you have will only work if there is 1 export, or if you pin
> the collection query to the node that exported it.
>
> To be honest though - exported resources might not be appropriate for
> this yum repo use case anyway, although perhaps I don't see it :-).
> Can you explain why you are trying to use exported resources for this
> purpose?
>
> ken.
>
> --
> 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/zNFaLT3tf3Q/unsubscribe.
> To unsubscribe from this group and all its topics, 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/CAE4bNTmXwwyYwBG6aR9cNc%2BjS_MzLvoaeBaOSPT5XhCkwSQxFw%40mail.gmail.com
> .
> 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAN9oxgStxTjcA6ef7cq%2BCwouXFpso5hCgKkOWDq44qiHRnZK2A%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] saving copy of template on puppetmaster

2013-11-21 Thread warden



I am using puppet to manage files on the nodes with the ERB templates. 
Plain old standard. What I need to do is to get a copy of the generated 
(parsed) template file on the puppet master server. What I want to achieve 
is that I want to see the current version of the file as it is on the 
client, but on the server...

I was going through the documentation but I didn't find anything useful. 
The closest thing was the "backup" feature of file resource what I think 
does exactly what I want, but for the previous version, not the current one.

so, by example, given the following definition:

file { "/some/file":
  source => template("sometemplate");
}

I want to have the /some/file contents on puppetmaster server too, not only 
on the client. I see in the docs that I can do something like:

$variable = template("xx");

but how to put that then in the file on the puppetmaster?

-- 
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/dc6c5930-a0b8-4c91-870f-ef24039d9648%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Belgian PUG - Something about augeas - Tuesday, November 26, 2013

2013-11-21 Thread Johan De Wit

Something about augeas 


Belgian Puppet User Group
Added by Johan De Wit
Tuesday, November 26, 2013
7:00 PM
Offices Open-Future
Zavelstraat 73
Kortenberg

This time, the meetup will be more a workshop.

The idea is to have a kind of (moderated ??) discussion about how to 
manage files in puppet with the augeas resource,  getting to know some 
tools to help write the correct resource code (eg. augtool...
Learn more 
 



Sponsored by Open-Future 
 and inuits 



--
Johan De Wit

Open Source Consultant

Red Hat Certified Engineer (805008667232363)
Puppet Certified Professional 2013 (PCP006)
_
 
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:
Puppet Advanced Training | 
https://www.open-future.be/puppet-advanced-training-12-till-14th-november
Zabbix Certified Training | 
http://www.open-future.be/zabbix-certified-training-18-till-20th-november
Zabbix Large Environments Training | 
http://www.open-future.be/zabbix-large-environments-training-21-till-22nd-november
Puppet Fundamentals Training | 
http://www.open-future.be/puppet-fundamentals-training-10-till-12th-december
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/528E0178.9050105%40open-future.be.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Problem with Passenger

2013-11-21 Thread Marcelo Frota

Hi Felix, 

My archive config.ru is equal to the file that you spoke. 

Do you have other sugestion, for the my problem ? 

Regards
Marcelo Frota

Em quinta-feira, 21 de novembro de 2013 09h09min03s UTC-2, Felix.Frank 
escreveu:
>
> Hi, 
>
> is that config.ru from the ubuntu package? 
>
> It looks odd and seems to miss the vital '$0 = "master"' line. For 
> reference: 
> https://github.com/puppetlabs/puppet/blob/master/ext/rack/config.ru 
>
> HTH, 
> Felix 
>
> On 11/18/2013 09:52 PM, Marcelo Frota wrote: 
> > I am running puppet with puppet version  3.3.2-1, apache 
> > 2.2.22-1ubuntu1.4 and passenger module 2.2.11debian-2. 
> > 
> > My config.ru : 
>
> -- 
> MPeX.net GmbH / Werner-Voï¿½-Damm 62 / D-12101 Berlin / Germany 
> MPeXnetworks / www.mpexnetworks.de 
> Tel: ++49-30-78097 180 / Fax: ++49-30-78097 181 
>
> Sitz, Registergericht: Berlin, Amtsgericht Charlottenburg, HRB 76688 
> Geschï¿½ftsfï¿½hrer: Lars Brï¿½uer, Gregor Rex-Lawatscheck 
>

-- 
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/2d2ec909-43c9-4693-97a6-5625cba8b706%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: Could not find parent resource type

Warning: Scope(Class[<>]): Could not look up qualified variable 
'<>::params::<>_APIkey'; class <>::params could not be found

Warning: Scope(Class[<>]): Could not look up qualified variable 
'<>::params::<>_APIkey'; class <>::params could not be found
Error: Could not find class site24x7::params for 



On Thursday, 21 November 2013 14:41:01 UTC+5:30, Raj kumar V wrote:
>
> I have written a module with a init class. Now I have to pass a dynamic 
> value. so I have created a params class and inherited in the init class and 
> trying to access the value. But puppet says 
>
> Could not find parent resource type ::params of type hostclass 
>
> error. Any idea? 
>

-- 
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/c53f59b2-c58e-4b0a-8540-aa2cd3d7cc20%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] matching all current "ipaddress_ethX" facts

2013-11-21 Thread cko

Hi,

I'm currently trying to solve the following problem:

I wrote a module that matches the "$ipaddress" fact for certain IP subnets 
(like 20.20.2... or 30.30.2..). Depending on the subnet, the variable 
$proxy-server changes.

The problem is, that some of our physical machines have a random number of 
interfaces connected to many different subnets. In some cases the 
$ipadddress fact returns the correct subnet, lets call it "production 
server lan" and some don't.

Is there any way to make puppet check every available NIC for a specific 
subnet/ regex? Something like this:

if $ipaddress_eth*** =~ /^20\.20\.\..*$/ {
   $proxy-server = foo 
}
. 

-- 
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/9e5f1c49-cf71-4eab-a11b-18a9d31b5b0a%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Puppet dashboard config for node request

2013-11-21 Thread kaustubh chaudhari

Sorry if this is a duplicate request. Unable to see my previous post, hence 
resending!


I am trying to have a node request tab in puppet-dashboard in the open 
source version, In PE we have this tab to accept / reject node request.

Can we configure the same in open source puppet dashboard ?

Kaustubh 

-- 
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/194a18e4-68b8-4ec8-8fef-5f0a7b3b2f7c%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Puppet and scripts.

2013-11-21 Thread Andreas Ntaflos

On 2013-11-21 19:08, Daniel Lyons wrote:
> We've got a decently complicated .sh script used to set up oracle
> database, inlcuding partioning and the like. If I attempt to run it
> through puppet the script will end after 300 seconds as timed out. To
> test a simpler case I just made a little script as such:

Exec has a timeout parameter:
http://docs.puppetlabs.com/references/latest/type.html#exec-attribute-timeout

HTH

Andreas



signature.asc
Description: OpenPGP digital signature

Re: [Puppet Users] Could not find parent resource type

On Thursday, November 21, 2013 6:00:53 AM UTC-6, Felix.Frank wrote:
>
> On 11/21/2013 12:17 PM, Raj kumar V wrote: 
> > In my module folder,  
> > 
> > I have 2 files. 
> > 
> > init.pp 
> > params.pp 
> > 
> > My init code: 
> > 
> > class myclass($api_key=$myclass::params::myclassagent_APIkey) inherits 
> > myclass::params{ 
>
> No need to inherit the params class. I would get rid of that first. 
>

I'm afraid there *is* a reason: class myclass uses a variable from class 
myclass::params as the default value for its class parameter.  The only 
self-contained way to ensure that that variable's value is already set when 
class myclass is evaluated is to inherit from myclass::params.  I don't 
like that much, but it has become a widely-used pattern.

>
> > include myclass::params 
>
> This is likely needed, although I'm not sure wether 
> $myclass::params::myclassagent_APIkey will already be available when 
> puppet encounters the class declaration header. 
>

That's absolutely unneeded if the class inherits from myclass::params, as 
shown.  On the other hand, it would be needed and appropriate if the body 
of class myclass used any variables of class myclass::params and myclass 
did not inherit from myclass::params.

> > some code here... 
> > 
> > }include myclass 
>

I'm not very comfortable with putting that 'include' statement at top level 
of the module's init.pp.  I think I understand the idea, but it could lead 
to subtle errors.  In fact, it leaves you in the realm of undocumented 
behavior if you ever try to declare class myclass elsewhere via a 
parameterized-style declaration (not that I generally account 
parameterized-style class declarations a good idea, but that seems the 
direction this is heading).

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/d70b79a6-5130-41ac-b358-c4a6ea0e3bd5%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: matching all current "ipaddress_ethX" facts



On Thursday, November 21, 2013 6:32:44 AM UTC-6, cko wrote:
>
> Hi,
>
> I'm currently trying to solve the following problem:
>
> I wrote a module that matches the "$ipaddress" fact for certain IP subnets 
> (like 20.20.2... or 30.30.2..). Depending on the subnet, the variable 
> $proxy-server changes.
>
> The problem is, that some of our physical machines have a random number of 
> interfaces connected to many different subnets. In some cases the 
> $ipadddress fact returns the correct subnet, lets call it "production 
> server lan" and some don't.
>
> Is there any way to make puppet check every available NIC for a specific 
> subnet/ regex? Something like this:
>
> if $ipaddress_eth*** =~ /^20\.20\.\..*$/ {
>$proxy-server = foo 
> }
>



Puppet DSL does not support this directly, but it sounds like a good 
candidate for a custom function.  You could do a proof-of-concept with an 
inline template, even, but I recommend a bona fide function for your final 
implementation.


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/7f75b91e-915b-4f42-b1b9-7e7b20d4e9da%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] How to configure puppet-dashboard for Node request management

2013-11-21 Thread kaustubh chaudhari

Hi,

i am looking for configure a way to accept / reject node request using 
puppet-dashboard. 

I know this facility is available in PE, but i am trying to find a way to 
do this in opensource version. 

Is this possible?

Kausutbh

-- 
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/c0348c32-660c-4cd3-83f7-644dc7418831%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Puppet and scripts.

2013-11-21 Thread Daniel Lyons

Hello,
So I realize one of the main points of puppet is moving way from .sh
scripts but I'm at a point where I need to use one until I can get
everything figured out. The problem I'm having is that my scripts dont seem
to run properly if I have puppet call them.

We've got a decently complicated .sh script used to set up oracle database,
inlcuding partioning and the like. If I attempt to run it through puppet
the script will end after 300 seconds as timed out. To test a simpler case
I just made a little script as such:

#!/bin/sh
echo Something

Then if I try to use it with this (as a puppet agent run):

exec { "Thing":

provider => shell,
command => "sh /testscript.sh",
path => "(my path)"

}

I notice through --debug it says it executes the script but I don't see the
actual echo command comming out. I've read about logoutput => true and that
will give me the "Somthing" in the puppet information but if I run the big
script I still dont see anything. The install script opens with defining a
bunch of functions and then heading into a main, so I'm wondering if there
is something with puppet and scripts that doesn't want to just run? It
seems like it should just let the script run though. I have verified the
script works correctly when simply run straight in the shell.

Again, as I've moved some other programs and installs to puppet I realize
I'm kind of going against the puppet grain on this and eventually plan to
do away with sh scripts but for now, due to time constraints and having a
lot of this script written before I arrived here, I sort of need to put a
temporary fix on this one by running the script we've used for a while.

Thanks for the help, and double thanks if this is something out of my range
of understanding for scripts and puppet that I'm unaware of. I'm a bit of a
newbie to all this and have run through the tutorials and such but I think
there's a piece I'm blind to here. :)

-Daniel

--
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/1bc22825-abb8-4fb8-b200-b620b61742e9%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: Could not find parent resource type

Still the same error. I have the params in the same init location.

http://pastebin.com/nCmcgMi4

look at the pp scripts here

On Thursday, 21 November 2013 14:41:01 UTC+5:30, Raj kumar V wrote:
>
> I have written a module with a init class. Now I have to pass a dynamic 
> value. so I have created a params class and inherited in the init class and 
> trying to access the value. But puppet says 
>
> Could not find parent resource type ::params of type hostclass 
>
> error. Any idea? 
>

-- 
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/c6c1d05b-4e7a-46cc-9876-a726a421bb46%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Could not find parent resource type

2013-11-21 Thread Johan De Wit


And to make autoloading work :

...modules/myclass/init.pp
 /params.pp

hth

Jo

On 11/21/2013 01:00 PM, Felix Frank wrote:

Hi,

comments inline.

On 11/21/2013 12:17 PM, Raj kumar V wrote:

In my module folder, 

I have 2 files.

init.pp
params.pp

My init code:

class myclass($api_key=$myclass::params::myclassagent_APIkey) inherits
myclass::params{

No need to inherit the params class. I would get rid of that first.


include myclass::params

This is likely needed, although I'm not sure wether
$myclass::params::myclassagent_APIkey will already be available when
puppet encounters the class declaration header.


some code here...

}include myclass

params.pp got:

class myclass::params{
myclassagent_APIkey=' '
}

That looks all right, except for the missing $ on the variable name.

HTH,
Felix




--
Johan De Wit

Open Source Consultant

Red Hat Certified Engineer (805008667232363)
Puppet Certified Professional 2013 (PCP006)
_
 
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:
Puppet Advanced Training | 
https://www.open-future.be/puppet-advanced-training-12-till-14th-november
Zabbix Certified Training | 
http://www.open-future.be/zabbix-certified-training-18-till-20th-november
Zabbix Large Environments Training | 
http://www.open-future.be/zabbix-large-environments-training-21-till-22nd-november
Puppet Fundamentals Training | 
http://www.open-future.be/puppet-fundamentals-training-10-till-12th-december
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/528DF77E.7080808%40open-future.be.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Puppet: a way to secure certain files

2013-11-21 Thread Sergey Arlashin

Thank you!

On Nov 20, 2013, at 9:02 PM, jcbollinger  wrote:

> 
> 
> On Wednesday, November 20, 2013 12:06:35 AM UTC-6, Rich Burroughs wrote:
> You can use hiera gpg for ssh keys too.
> 
> See this example:
> 
> https://groups.google.com/d/msg/puppet-users/jHcuKQXT9cQ/g23Lmf4e6b8J
> 
> 
> 
> 
> But you would be unwise to do that in conjunction with Puppet 3, unless you 
> fall into one of a small number of special cases.  If you add the hiera-gpg 
> back end to your hiera configuration then the encrypted file will be 
> decrypted once for each class parameter that is neither explicitly assigned a 
> value nor resolved in a higher-priority back end.  Decrypting the file is 
> very expensive, and if you do it many times then you will see a very 
> noticeable impact on catalog compilation performance.  There have been 
> reports on this group of such decryption adding several minutes of 
> compilation time for catalogs that otherwise take a few seconds.
> 
> That decryption overhead will not affect you if you use few (or no) 
> parameterized classes (watch out for third-party modules!), if you take care 
> to assign values to all class parameters of every declared class (again, 
> beware third party modules here), or if you are using Puppet 2 rather than 
> Puppet 3.
> 
> You should consider whether it really makes sense to encrypt at all, vs. 
> simply securing the master against unauthorized users.  If you encrypt then 
> you must record the plaintext decryption key somewhere that the master can 
> read it, and if you hypothesize an assailant that is savvy enough to track 
> down sensitive information in your Puppet configs then you should assume that 
> that assailant can also find the decryption key.  In fact, such an assailant 
> must also break your access controls to reach the sensitive information, 
> meaning that they must have gained root access to your server before 
> encryption is even a factor.  If an assailant gains root then it's already 
> game over.
> 
> 
> 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/59d9ed61-8fb3-4b51-bf1d-5d96feab83d8%40googlegroups.com.
> 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/C08FC97C-6503-46A1-B204-DBE0B7243794%40gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Could not find parent resource type

Hi,

comments inline.

On 11/21/2013 12:17 PM, Raj kumar V wrote:
> In my module folder, 
> 
> I have 2 files.
> 
> init.pp
> params.pp
> 
> My init code:
> 
> class myclass($api_key=$myclass::params::myclassagent_APIkey) inherits
> myclass::params{

No need to inherit the params class. I would get rid of that first.

> include myclass::params

This is likely needed, although I'm not sure wether
$myclass::params::myclassagent_APIkey will already be available when
puppet encounters the class declaration header.

> some code here...
> 
> }include myclass
> 
> params.pp got:
> 
> class myclass::params{
> myclassagent_APIkey=' '
> }

That looks all right, except for the missing $ on the variable name.

HTH,
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/528DF5F5.8030205%40alumni.tu-berlin.de.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Could not find parent resource type

In my module folder, 

I have 2 files.

init.pp
params.pp

My init code:

class myclass($api_key=$myclass::params::myclassagent_APIkey) inherits 
myclass::params{

include myclass::params

some code here...

}include myclass
params.pp got:

class myclass::params{
myclassagent_APIkey=' '
}

What am i missing?

On Thursday, 21 November 2013 15:41:49 UTC+5:30, Felix.Frank wrote:
>
> This looks pretty bad :-) 
>
> Can you paste (excerpts of) your manifest code on pastebin or a similar 
> service? 
>
> On 11/21/2013 10:11 AM, Raj kumar V wrote: 
> > I have written a module with a init class. Now I have to pass a dynamic 
> > value. so I have created a params class and inherited in the init class 
> > and trying to access the value. But puppet says 
> > 
> > Could not find parent resource type ::params of type hostclass 
> > 
> > error. Any idea? 
>

-- 
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/f59055d3-7888-400f-9f46-3bd02fe3160a%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Problem with Passenger

Hi,

is that config.ru from the ubuntu package?

It looks odd and seems to miss the vital '$0 = "master"' line. For
reference:
https://github.com/puppetlabs/puppet/blob/master/ext/rack/config.ru

HTH,
Felix

On 11/18/2013 09:52 PM, Marcelo Frota wrote:
> I am running puppet with puppet version  3.3.2-1, apache
> 2.2.22-1ubuntu1.4 and passenger module 2.2.11debian-2.
> 
> My config.ru : 

-- 
MPeX.net GmbH / Werner-Voß-Damm 62 / D-12101 Berlin / Germany
MPeXnetworks / www.mpexnetworks.de
Tel: ++49-30-78097 180 / Fax: ++49-30-78097 181

Sitz, Registergericht: Berlin, Amtsgericht Charlottenburg, HRB 76688
Geschäftsführer: Lars Bräuer, Gregor Rex-Lawatscheck

-- 
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/528DE9CF.6010307%40alumni.tu-berlin.de.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] create_resources and file

Hi,

tough call. You may have to replicate the file type in a defined type
like so:

define my_file($owner="root",$mode="644",...,$template="") {

  if $template { File[$name] { content => template($template) } }

  file { $name: owner => $owner, ... }
}

Then you can create_resource('my_file',hiera('input')) and pass an
actual "template" parameter to your define.

Lots of work, but I feel that at some points, many if not most users
likely feel the need to wrap the file type this way.

HTH,
Felix

On 11/18/2013 03:33 PM, erkan yanar wrote:
> Doing create_resources('file',hiera_hash('input'))
> works great for some hiera like
> input:
>   /tmp/a.txt:
> owner: root
> ensure: file
> ...
> 
> Im not able to put any template() stuff in there
> input:
>   /tmp/a.txt:
> owner: root
> ensure: file
> content: template("create_re/aha.erb")
> 
> Instead of doing the template lookup. The content of the file is
> 'template("create_re/aha.erb")'
> 
> Any way to dynamically (hiera) define the templates?
> 
> 
> Regards
> Erkan

-- 
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/528DE7FA.5090408%40alumni.tu-berlin.de.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Want to restrict puppet module execute every 30mins

Hi,

this would even work, but I think the approach as a whole is not well in
line with puppet's philosophy. Application deployment is not among its
core strengths.

If you really want to do this by puppet, I suggest you keep it simple:
1. perform all your steps in one monolithic script
2. have puppet deploy the script and execute it
3. give puppet the ability to determine if the script needs running,
typically by first comparing the deployed version to the desired one, e.g.

$version = "0.2-5"
exec { "deploy-app --version=${version}":
  unless => deploy-app --check --version=${version}"
  ...
}

HTH,
Felix

On 11/20/2013 05:08 PM, Sergey Arlashin wrote:
> You can create some sort of a trigger file. Like this:
> file { "/some/folder/file_trigger"
>ensure => present,
>content => "version01",
>   … 
> }
> 
> Add "refreshonly => true" to your resources. Then subscribe your
> resources to this file. Once the file is changed, your code will be
> executed. 
> 1. stop application service
> 2. take backup of existing application
> 3. download application artifact
> 4. install the application
> 5. some configuration stuff
> 6. start the application service

-- 
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/528DE6C9.3020507%40alumni.tu-berlin.de.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] cannot find puppet_node_classifier

2013-11-21 Thread shlo . afgin



Hi,
I'm trying to learn configure puppet nodes using ENC. The instruction tell 
to add to puppet.conf the line:
external_nodes = /usr/bin/puppet_node_classifier 

I cannot find  puppet_node_classifier anywhere in my system. I have puppet 
3.3.1 installed.
What I need to install in order to have it?
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/a66813f4-f0d6-4b8d-b792-d4910993c892%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Puppetmaster generated Certificate with "old" CA domainname

Hi,

humm, the TCP handshake fails...?

Is there firewalling on master and/or agent side?

Are you using passenger by the way?

Cheers,
Felix

On 11/20/2013 01:54 AM, yamakasi@gmail.com wrote:
> Hi Mark,
> 
> Yes I removed /var/lib/puppet/ssl on the agent.
> 
> At the moment I get an: Error: Could not request certificate: Connection
> timed out - connect(2)
> 
> But what I see on the master when running the agent on a client:
> 
> tcp0  0 10.0.0.250:8140 dhcp-01.domain...:46779
> SYN_RECV  
> 
> And that takes a long time and the connection timeout happens.
> 
> Matt

-- 
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/528DDD54.8060805%40alumni.tu-berlin.de.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] undefined method `enum_lsdev' for Facter::Util::Processor:Module

Hi,

are you certain that puppet uses the facter gem you installed? Is an
older version of facter installed by other means?

Regards,
Felix

On 11/20/2013 01:19 PM, yamakasi@gmail.com wrote:
> Hi All,
> 
> I'm facing the following error on an Ubuntu 12.04 install with Puppet 3.3.2
> 
> Error: Could not retrieve local facts: undefined method `enum_lsdev' for
> Facter::Util::Processor:Module
> 
> Facter is the latest version installed using gem.
> 
> I have seen this was a bug, is it still or again ?
> 
> Thanks!
> 
> Matt

-- 
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/528DDCCD.50909%40alumni.tu-berlin.de.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Could not find parent resource type

This looks pretty bad :-)

Can you paste (excerpts of) your manifest code on pastebin or a similar
service?

On 11/21/2013 10:11 AM, Raj kumar V wrote:
> I have written a module with a init class. Now I have to pass a dynamic
> value. so I have created a params class and inherited in the init class
> and trying to access the value. But puppet says 
> 
> Could not find parent resource type ::params of type hostclass 
> 
> error. Any idea? 

-- 
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/528DDC65.2020006%40alumni.tu-berlin.de.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Could not find parent resource type

I have written a module with a init class. Now I have to pass a dynamic 
value. so I have created a params class and inherited in the init class and 
trying to access the value. But puppet says 

Could not find parent resource type ::params of type hostclass 

error. Any idea? 

-- 
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/ff29ad11-7e0f-4f9e-bfa4-2db5010923be%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] some good books