Re: [Puppet Users] Terminolgy ... puppet policy or recipe

2015-02-15 Thread Dawn Foster
On Mon, Feb 16, 2015 at 1:28 AM, Grant Schoep  wrote:
> Ok. So my company is going full on Puppet.. yey.. I've been using puppet for
> years. They are using the term "puppet recipes" all over the place. I always
> though that was a chef thing
>
>
> So I can set the record strait? What do you think? My little svn.db is full
> of PP files, not PR files. Can I tell these new bigwigs they are wrong?

You are correct. If you want some documentation to use as proof, here
is a pretty good definition of manifest from the docs:
https://docs.puppetlabs.com/learning/manifests.html#manifests

Regards,
Dawn

-- 
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/CAPUeXZow2z5U2uiBoq-4FFO2z0qeK99Kxw-ysJQmycaFDxeLcQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: [Puppet Users] Cant remove depreciated warning message

2015-02-15 Thread David LeVene
So the problem ended up being the python module - it was not the latest 
version and it was adding custom resources which ignored what is in the 
global config.

The 3 files which were causing the problems were;
python_version.rb
pip_version.rb
virtualenv_version.rb

The newer version have a statement like this in them - which resolves my 
issues.

https://github.com/stankevich/puppet-python/blob/master/lib/facter/pip_version.rb

if Gem::Version.new(facter_puppet_version) >= Gem::Version.new('3.6')
> pkg = Puppet::Type.type(:package).new(:name => 'python', :allow_virtual => 
> 'false')
> else
> pkg = Puppet::Type.type(:package).new(:name => 'python') 
> end 


Hope if someone else is having these problems it may help them.

Cheers
David 

-- 
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/fe0e9ede-8fad-4b16-8cb0-bdb8aae2a8c0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [Puppet Users] Terminolgy ... puppet policy or recipe

2015-02-15 Thread Trevor Vaughan
Puppet Manifest is the appropriate term I believe.

On Sun, Feb 15, 2015 at 8:28 PM, Grant Schoep  wrote:

> Ok. So my company is going full on Puppet.. yey.. I've been using puppet
> for years. They are using the term "puppet recipes" all over the place. I
> always though that was a chef thing
>
>
> So I can set the record strait? What do you think? My little svn.db is
> full of PP files, not PR files. Can I tell these new bigwigs they are wrong?
>
> --
> 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/65f2f7cf-3590-4fc5-afe7-09d038254de3%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699
tvaug...@onyxpoint.com

-- This account not approved for unencrypted proprietary information --

-- 
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/CANs%2BFoX3JkV-%3DTj%3DfLB9RpFw%3DpNtyQgVN_SijGM3KsWVN_iZoQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


[Puppet Users] Terminolgy ... puppet policy or recipe

2015-02-15 Thread Grant Schoep
Ok. So my company is going full on Puppet.. yey.. I've been using puppet 
for years. They are using the term "puppet recipes" all over the place. I 
always though that was a chef thing


So I can set the record strait? What do you think? My little svn.db is full 
of PP files, not PR files. Can I tell these new bigwigs they are wrong?

-- 
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/65f2f7cf-3590-4fc5-afe7-09d038254de3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[Puppet Users] Re: puppet dashboard with \n\n\n

2015-02-15 Thread Anton Markelov
Sorry for necroposting. If you use mod_passenger, just change PassengerRuby 
parameter from '/usr/bin/ruby' to '/usr/bin/ruby1.8'.

пятница, 4 октября 2013 г., 6:00:26 UTC+10 пользователь Matt Zagrabelny 
написал:
>
> Greetings, 
>
> I've setup puppet dashboard 1.2.23 along with puppetmaster 2.7.18. 
>
> I am seeing many \n strings all over the place when looking at 
> reports. Specifically the \n's are in the Metrics, Log, Events links. 
>
> My nodes are showing up okay, and it seems just to be a problem with 
> the reports. For instance, a Metrics page starts with: 
>
> \n 
> \n 
> Metrics 
> \n 
> \n 
> Events 
>
> \n\n\n\n\n\n\n\n\n 
>
> Any advice on where to dig? /usr/share/puppet-dashboard/log/* does not 
> yield any hints. 
>
> Thanks! 
>
> -mz 
>

-- 
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/c61c5608-8342-4c67-9368-3bc86aac15ac%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [Puppet Users] iteration in future parser doesn't handle hashes as documented

2015-02-15 Thread Henrik Lindberg

On 2015-15-02 23:52, Jo Rhett wrote:

Opened as https://tickets.puppetlabs.com/browse/PUP-4015



You are bit by "stringify_facts" (see ticket for explanation).

- henrik


On Feb 15, 2015, at 2:49 PM, Jo Rhett mailto:jrh...@netconsonance.com>> wrote:

From documentation at
https://docs.puppetlabs.com/puppet/latest/reference/experiments_lambdas.html


*For a hash:*

If two parameters are used, they will be set to the key and value of
each hash entry. If one parameter is used, it is set to an array
containing |[key, value]|.


With Puppet 3.7.4 this doesn’t work as documented:

$ facter | grep system_uptime
system_uptime => {"uptime"=>"1:04 hours", "days"=>0, "hours"=>1,
"seconds"=>3898}

$ cat iter.pp
each( $facts['system_uptime'] ) |$key, $value| {
  notice "$key = $value"
}

$ puppet apply iter.pp
Notice: Scope(Class[main]): 0 = s
Notice: Scope(Class[main]): 1 = e
Notice: Scope(Class[main]): 2 = c
Notice: Scope(Class[main]): 3 = o
Notice: Scope(Class[main]): 4 = n
Notice: Scope(Class[main]): 5 = d
Notice: Scope(Class[main]): 6 = s
(snip)

The hash is clearly being recast as a single long string passed into
an indexed array.

--
Jo Rhett
+1 (415) 999-1798
Skype: jorhett
Net Consonance : net philanthropy to improve open source and
internet projects.


--
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/EA1FCAEB-38D7-48F7-8832-A81C18A24001%40netconsonance.com
.
For more options, visit https://groups.google.com/d/optout.


--
Jo Rhett
+1 (415) 999-1798
Skype: jorhett
Net Consonance : net philanthropy to improve open source and
internet projects.

--
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/D5F46694-BFCA-447D-A666-582E1BB04B1D%40netconsonance.com
.
For more options, visit https://groups.google.com/d/optout.



--

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

--
You received this message because you are subscribed to the Google Groups "Puppet 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/mbrdmk%244m9%241%40ger.gmane.org.
For more options, visit https://groups.google.com/d/optout.


Re: [Puppet Users] iteration in future parser doesn't handle hashes as documented

2015-02-15 Thread Jo Rhett
Opened as https://tickets.puppetlabs.com/browse/PUP-4015

On Feb 15, 2015, at 2:49 PM, Jo Rhett  wrote:
> From documentation at 
> https://docs.puppetlabs.com/puppet/latest/reference/experiments_lambdas.html
> 
>> For a hash:
>> 
>> If two parameters are used, they will be set to the key and value of each 
>> hash entry. If one parameter is used, it is set to an array containing [key, 
>> value].
>> 
> With Puppet 3.7.4 this doesn’t work as documented:
> 
> $ facter | grep system_uptime
> system_uptime => {"uptime"=>"1:04 hours", "days"=>0, "hours"=>1, 
> "seconds"=>3898}
> 
> $ cat iter.pp 
> each( $facts['system_uptime'] ) |$key, $value| {
>   notice "$key = $value"
> }
> 
> $ puppet apply iter.pp 
> Notice: Scope(Class[main]): 0 = s
> Notice: Scope(Class[main]): 1 = e
> Notice: Scope(Class[main]): 2 = c
> Notice: Scope(Class[main]): 3 = o
> Notice: Scope(Class[main]): 4 = n
> Notice: Scope(Class[main]): 5 = d
> Notice: Scope(Class[main]): 6 = s
> (snip)
> 
> The hash is clearly being recast as a single long string passed into an 
> indexed array.
> 
> -- 
> Jo Rhett
> +1 (415) 999-1798
> Skype: jorhett
> Net Consonance : net philanthropy to improve open source and internet 
> projects.
> 
> 
> -- 
> 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/EA1FCAEB-38D7-48F7-8832-A81C18A24001%40netconsonance.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
Jo Rhett
+1 (415) 999-1798
Skype: jorhett
Net Consonance : net philanthropy to improve open source and internet projects.

-- 
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/D5F46694-BFCA-447D-A666-582E1BB04B1D%40netconsonance.com.
For more options, visit https://groups.google.com/d/optout.


[Puppet Users] iteration in future parser doesn't handle hashes as documented

2015-02-15 Thread Jo Rhett
>From documentation at 
>https://docs.puppetlabs.com/puppet/latest/reference/experiments_lambdas.html
> For a hash:
> 
> If two parameters are used, they will be set to the key and value of each 
> hash entry. If one parameter is used, it is set to an array containing [key, 
> value].
> 
With Puppet 3.7.4 this doesn’t work as documented:

$ facter | grep system_uptime
system_uptime => {"uptime"=>"1:04 hours", "days"=>0, "hours"=>1, 
"seconds"=>3898}

$ cat iter.pp 
each( $facts['system_uptime'] ) |$key, $value| {
  notice "$key = $value"
}

$ puppet apply iter.pp 
Notice: Scope(Class[main]): 0 = s
Notice: Scope(Class[main]): 1 = e
Notice: Scope(Class[main]): 2 = c
Notice: Scope(Class[main]): 3 = o
Notice: Scope(Class[main]): 4 = n
Notice: Scope(Class[main]): 5 = d
Notice: Scope(Class[main]): 6 = s
(snip)

The hash is clearly being recast as a single long string passed into an indexed 
array.

-- 
Jo Rhett
+1 (415) 999-1798
Skype: jorhett
Net Consonance : net philanthropy to improve open source and internet projects.

-- 
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/EA1FCAEB-38D7-48F7-8832-A81C18A24001%40netconsonance.com.
For more options, visit https://groups.google.com/d/optout.


Re: [Puppet Users] Puppet module

2015-02-15 Thread James A. Peltier
- Original Message - 

| Trying to install the module vcsrepo with puppet, but really unsure how it
| could be done. The commandline to install it is:
| puppet module install puppetlabs-vcsrepo

| Tried to install it this way, but that didn't work:
| package { 'vcsrepo':
| ensure => installed,
| }

| --
| 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/a834ec65-608a-42f0-842b-d10dd67d8003%40googlegroups.com
| .
| For more options, visit https://groups.google.com/d/optout .


A module is not a package.  The way to install modules is to use puppet module 
install on the command line or to manage it some other way, for example r10k or 
puppet-librarian, which can be used to manage modules that get installed on the 
server in an environment.

-- 
James A. Peltier
IT Services - Research Computing Group
Simon Fraser University - Burnaby Campus
Phone   : 778-782-6573
Fax : 778-782-3045
E-Mail  : jpelt...@sfu.ca
Website : http://www.sfu.ca/itservices
Twitter : @sfu_rcg
Powering Engagement Through Technology
"Build upon strengths and weaknesses will generally take care of themselves" - 
Joyce C. Lock

-- 
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/913558440.17246196.1424028141114.JavaMail.zimbra%40sfu.ca.
For more options, visit https://groups.google.com/d/optout.


Re: [Puppet Users] Puppet module

2015-02-15 Thread Bilal Ahmad
Yes, of course I have read it. I was trying to install the module with a 
puppet script instead of doing it in the commandline. The documentation 
said nothing about that.

lørdag 14. februar 2015 19.52.45 UTC+1 skrev Hristo Mohamed følgende:
>
> Have you considered reading the documentation?
> https://github.com/puppetlabs/puppetlabs-vcsrepo
>
> On Sat, Feb 14, 2015 at 5:37 PM, Bilal Ahmad  > wrote:
>
>> Trying to install the module vcsrepo with puppet, but really unsure how 
>> it could be done. The commandline to install it is:
>>
>> puppet module install puppetlabs-vcsrepo
>>
>> Tried to install it this way, but that didn't work:
>>
>> package { 'vcsrepo':
>> ensure => installed,
>> }
>>
>>  -- 
>> 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/a834ec65-608a-42f0-842b-d10dd67d8003%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/e324ff59-12fe-4b91-9737-8861e60a9eea%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.