[Puppet Users] Re: Dashboard can't find classes

[Stefan Heijmans]

Hi,
 
>>However those classes on my puppet master are not being parsed into the 
dashboard. There is no classed shown in dashboard, even I am sure I 
downloaded a few modules.
You mean, you have not added classes manually to the Dashboard?
If so, you do need to do this. Modules available on your Puppet Master are 
*not* automatically detected by the Dashboard.
Use the "Add Class" option to add all needed classes from the Puppet Master 
to the Dashboard, after that use Group/Class option to assign them to a 
Node.
 
Stefan

On Thursday, July 31, 2014 2:58:10 AM UTC+2, Stella wrote:

> I followed this document to install and configure Puppet 3.6.2 and 
> Dashboard 1.2.23 on Red Hat Linux 6.5, both using Apache as web server.
>
> http://docs.puppetlabs.com/guides/install_puppet/pre_install.html
> http://docs.puppetlabs.com/guides/install_puppet/install_el.html
> http://docs.puppetlabs.com/guides/install_puppet/post_install.html
> http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html
>
> My puppet master and agent are working: master can push class to agent. 
> Also I can access the dashboard console and can see my nodes are listed: 
> http://localhost:3000
>
> However those classes on my puppet master are not being parsed into the 
> dashboard. There is no classed shown in dashboard, even I am sure I 
> downloaded a few modules.
> Do I missing any configuration (module path, or other parameters) ?
>
> NOTE:
> 1. I have added the following to the masters puppet configuration file and 
> the path is correct with the dashboard running on the master.
>  node_terminus  = exec
>  external_nodes = /usr/bin/env PUPPET_DASHBOARD_URL=http://localhost:3000 
> /usr/share/puppet-dashboard/bin/external_node
>
> 2. I googled and someone mentioned that he changed the ruby path in the 
> dashboard external node script to use the ruby that was installed (original 
> /usr/bin/ruby doesn't work for ruby installs from source). I am using Ruby 
> 1.8.7. How to find out where is the new ruby installed? 
>
>
> I am stuck on this.  Please help.
>
> 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/e1b83e17-5c9e-4e04-b127-cb8ea637384c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Dashboard can't find classes

[Stella]

I followed this document to install and configure Puppet 3.6.2 and 
Dashboard 1.2.23 on Red Hat Linux 6.5, both using Apache as web server.

http://docs.puppetlabs.com/guides/install_puppet/pre_install.html
http://docs.puppetlabs.com/guides/install_puppet/install_el.html
http://docs.puppetlabs.com/guides/install_puppet/post_install.html
http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html

My puppet master and agent are working: master can push class to agent. 
Also I can access the dashboard console and can see my nodes are listed: 
http://localhost:3000

However those classes on my puppet master are not being parsed into the 
dashboard. There is no classed shown in dashboard, even I am sure I 
downloaded a few modules.
Do I missing any configuration (module path, or other parameters) ?

NOTE:
1. I have added the following to the masters puppet configuration file and 
the path is correct with the dashboard running on the master.
 node_terminus  = exec
 external_nodes = /usr/bin/env PUPPET_DASHBOARD_URL=http://localhost:3000 
/usr/share/puppet-dashboard/bin/external_node

2. I googled and someone mentioned that he changed the ruby path in the 
dashboard external node script to use the ruby that was installed (original 
/usr/bin/ruby doesn't work for ruby installs from source). I am using Ruby 
1.8.7. How to find out where is the new ruby installed? 


I am stuck on this.  Please help.

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/cbeb64fb-a9e4-4596-856c-799cabf6fa45%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Wrap class around define and use it as Require

[yamakasi . 014]

Hi Guys,

I'm using an ENC to define all my nodes including some modules I want to 
load, I have the following class/define for this:

class mymodule::modules::enable (

$enable_modules = undef
) {

 $modules_split = split($enable_modules, ',')
 enableModules { $modules_split: }
  
}

define enableModules () {
 exec { "mycommand  $name" :
  command   => "/usr/sbin/mycommand $name",
  notify => Service[myservice]
 }
}

mymodule::modules::enable{'modX': enable_modules => 'module'}


Now I'm using this per node using mod1,mod2,mod3 which works OK, I don't 
want to use create_resources here as I want to have one filed for enable, 
and one field for disable in my ENC

For some fool-proof solution that when the module is not set in my ENC I 
want to require the define enableModules in a different class and set a 
static parameter:

some::class ( )

{

Class['modulename'] -> MyModule::Modules::Enable['modX:']

file { "/my/path/to/directory" :
ensure  => directory,
mode=> '0644',
owner   => 'root',
group   => 'root',
require => Class['modulename'],
  }

}

Well, I need to wrap a class around my define to get this all working as 
you can see above but this is not working as my some::class says:

Could not find dependency Class[Enable_mymodule] for 
File[/my/path/to/directory] at...

I have tried includes, different ways of defining or wrapping the class but 
no clue at all, I also get other errors that are not related as I was 
messing things more up.

When I use:

Class['modulename] -> class { 'mymodule::modules::enable': enable_modules 
=> 'mymodule' }

I get the message that it cannot redeclare 'mymodule::modules::enable' as 
my ENC already did.


I have used some Foo parameters and Vars here as I want to use this in more 
modules if this is possible. It's just for a fallback when modules are 
needed for sofware to be loaded and the user didn't enable it in it's ENC 
yaml.

I hope someone can help me out.

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/da5f31e8-b9a0-433b-9ae9-8bf9192e85a1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] puppet enterprise install error

[Luis Lopez]

I'm do this steps:
- install puppetmaster in host puppetmaster.domain
- configure /etc/puppet/puppet.conf
  [agent]
certname=puppetmaster.domain
  [master]
   server=puppetmaster.domain ## FQDN del servidor puppetmaster
- restart puppetmaster service
- download puppet-enterprise-3.3.0-ubuntu-14.04-amd64
- execute ./puppet-enterprise-installer
- answer all quetions (use smtp server and postgres in same host)

and when press the DEPLOY button show this error

 Installing Puppet Enterprise on puppetmaster.domain.
  [172.*.*.*] An error occured while performing
install_pe_puppetmaster.domain: "\xE2" from ASCII-8BIT to UTF-8.

   This error has me to the point of losing my head.

   please help me!

  regards

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAOTSdRuLBOiZdR_mGKFSN7X13nb7df_e%3DCA%3DskZ5%2BDqoVx3ZDg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] http://yum.puppetlabs.com/el/7Server ?

[Louis Coilliot]

Nice thanks !

Louis Coilliot


2014-07-30 19:05 GMT+02:00 Melissa Stone :

> Hi Louis,
>
> el/7Server is now a link to el/7, see
> https://yum.puppetlabs.com/el/7Server/
>
>
> On Tue, Jul 29, 2014 at 3:11 AM, Louis Coilliot 
> wrote:
>
>> Hello, could you please add a link or copy from el/7 to el/7Server ?
>>
>> Like you have for el5 and el6 :
>>
>> http://yum.puppetlabs.com/el/6/
>> http://yum.puppetlabs.com/el/6Server/
>>
>> http://yum.puppetlabs.com/el/5/
>> http://yum.puppetlabs.com/el/5Server/
>>
>> This would ease deployment on official RHEL7 :
>>
>> $repo_puppetlabs_products =
>>   'http://yum.puppetlabs.com/el/$releasever/products/$basearch',
>> $repo_puppetlabs_deps =
>>   'http://yum.puppetlabs.com/el/$releasever/dependencies/$basearch',
>>
>> $releasever is 7 on Centos 7 but 7Server on RHEL 7
>>
>> Thanks in advance.
>>
>> Louis Coilliot
>>
>> --
>> 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/CAE9jN30KrkyMX6BmMbTaff%3D0TMqbB9oyLAp713UGYvErAy1OzA%40mail.gmail.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Melissa Stone
> Release Engineer, Puppet Labs
>
> *Join us at PuppetConf 2014 , September
> 20-24 in San Francisco*
> *Register by July 31st to take advantage of the Early Bird discount
>  **—**save
> $249!*
>
> --
> 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/CAHEe_koo%2Boej3hKo0bpixLikVCtuEitV7MCHdRCcsHMba23Ztg%40mail.gmail.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/CAE9jN32Eg3HJs0Jh_Skf-G_A4TZER8dyT09dkv_wLkg6dCV6Qw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Hiera not expanding $operatingsystem variable

[Christopher Wood]

On Wed, Jul 30, 2014 at 08:47:23PM +0100, Karolis Pabijanskas wrote:
>Thanks! I knew it was something simple! I just did not restart the puppet
>master that was all.. hiera works fine with or without the quotes
>though and they are not required.

I've had some troubles using all-numeric strings ("1234") unquoted in 
templates, where they are interpreted as integers. Not that I'm the expert, but 
it's worth considering that ruby variables in templates are typed, but puppet 
variables in manifests aren't, and will need more care when writing yaml for 
templates.

Consider how you'll need to use to_s or to_i in a template:

---
integer: 1234
string: "1234"

$ readyaml /tmp/yaml1 
{"integer"=>1234, "string"=>"1234"}

Obviously I'm not the expert, it's just a bit of a pain.


$ cat bin/readyaml
#!/usr/bin/env ruby

require 'pp'
require 'yaml'

data = File.read(ARGV[0])
yaml = YAML.load(data)
pp yaml


>Thanks again for the tip!
> 
>Karolis
> 
>On 30 July 2014 19:03, Garrett Honeycutt <[1]g...@garretthoneycutt.com>
>wrote:
> 
>  On 7/30/14 1:23 PM, Johan De Wit wrote:
>  > Hi,
>  >
>  > always use quotes when using facts etc in hiera :
>  >
>  > :hierarchy:
>  >   - "%{operatingsystem}"
>  >   - default
>  >
>  > hth
>  >
>  > Johan
>  >
>  > On 30/07/14 18:21, Karolis Pabijanskas wrote:
>  >> Hi All,
>  >>
>  >> I am sure this is going to be something completely stupid, but I just
>  >> can't find the issue :)
>  >>
>  >> I have a very simple module that that needs a different filepath
>  >> depending on the operating system, so I'm trying to call:
>  >>
>  >> $global_bashrc_file = hiera("global_bashrc_file")
>  >>
>  >> from my module.
>  >>
>  >> The hierarchy at the moment is very simple:
>  >>
>  >> :hierarchy:
>  >>   - %{operatingsystem}
>  >>   - default
>  >>
>  >> Calling notify from the module works just fine and brings back CentOS
>  >> as my operating system. CentOS.yaml does exist in the  datadir and
>  >> does contain the variable. Running hiera in through the shell does
>  >> indeed show it working and returns the correct variable:
>  >>
>  >> # hiera global_bashrc_file operatingsystem=CentOS
>  >> /etc/bashrc
>  >>
>  >> But when trying to get this value via puppet, I just get an error:
>  >> Error: Could not retrieve catalog from remote server: Error 400 on
>  >> SERVER: Could not find data item global_bashrc_file in any Hiera data
>  >> file and no default supplied at blah
>  >>
>  >> It does work perfectly fine if I place the variable in default.yaml,
>  >> but if I move it to the os-specific yaml it just shouts at me that I
>  >> have not declared it... Just seems like $operatingsystem does not get
>  >> passed on from puppet, even though:
>  >> # facter operatingsystem
>  >> CentOS
>  >>
>  >> and notify '{ "${operatingsystem": }' in puppet works.
>  >>
>  >> As mentioned, I am sure I am missing something very trivial, but
>  maybe
>  >> one of you enlightened ones can point me in the right direction!
>  >>
>  >> puppet version is 3.6.2
>  >> hiera version i 1.3.4
>  >>
>  >> Thanks in advance!
>  >>
>  >> Karolis
>  >>
> 
>  Hi,
> 
>  Good eye on the quotes, Johan. Whenever you change hiera.yaml, be sure
>  to restart the puppet master.
> 
>  Best regards,
>  -g
> 
>  --
>  Garrett Honeycutt
>  @learnpuppet
>  Puppet Training with LearnPuppet.com
>  Mobile: [2]+1.206.414.8658
>  --
>  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 [3]puppet-users+unsubscr...@googlegroups.com.
>  To view this discussion on the web visit
>  
> [4]https://groups.google.com/d/msgid/puppet-users/53D93388.9060604%40garretthoneycutt.com.
>  For more options, visit [5]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 [6]puppet-users+unsubscr...@googlegroups.com.
>To view this discussion on the web visit
>
> [7]https://groups.google.com/d/msgid/puppet-users/CANYNSSJAz1YOn6cnm0oSiG7KNehqu60TEyHq_hum2T5O97xycQ%40mail.gmail.com.
>For more options, visit [8]https://groups.google.com/d/optout.
> 
> References
> 
>Visible links
>1. mailto:g...@garretthoneycutt.com
>2. file:///tmp/tel:%2B1.206.414.8658
>3. mailto:puppet-users%2bunsubscr...@googlegroups.com
>4. 
> https://groups.google.com/d/msgid/puppet-users/53D93388.9060604%40garretthoneycutt.com
>5. https://groups.google.com/d/optout
>6. mail

Re: [Puppet Users] Hiera not expanding $operatingsystem variable

[Karolis Pabijanskas]

Thanks! I knew it was something simple! I just did not restart the puppet
master that was all.. hiera works fine with or without the quotes
though and they are not required.

Thanks again for the tip!

Karolis


On 30 July 2014 19:03, Garrett Honeycutt  wrote:

> On 7/30/14 1:23 PM, Johan De Wit wrote:
> > Hi,
> >
> > always use quotes when using facts etc in hiera :
> >
> > :hierarchy:
> >   - "%{operatingsystem}"
> >   - default
> >
> > hth
> >
> > Johan
> >
> > On 30/07/14 18:21, Karolis Pabijanskas wrote:
> >> Hi All,
> >>
> >> I am sure this is going to be something completely stupid, but I just
> >> can't find the issue :)
> >>
> >> I have a very simple module that that needs a different filepath
> >> depending on the operating system, so I'm trying to call:
> >>
> >> $global_bashrc_file = hiera("global_bashrc_file")
> >>
> >> from my module.
> >>
> >> The hierarchy at the moment is very simple:
> >>
> >> :hierarchy:
> >>   - %{operatingsystem}
> >>   - default
> >>
> >> Calling notify from the module works just fine and brings back CentOS
> >> as my operating system. CentOS.yaml does exist in the  datadir and
> >> does contain the variable. Running hiera in through the shell does
> >> indeed show it working and returns the correct variable:
> >>
> >> # hiera global_bashrc_file operatingsystem=CentOS
> >> /etc/bashrc
> >>
> >> But when trying to get this value via puppet, I just get an error:
> >> Error: Could not retrieve catalog from remote server: Error 400 on
> >> SERVER: Could not find data item global_bashrc_file in any Hiera data
> >> file and no default supplied at blah
> >>
> >> It does work perfectly fine if I place the variable in default.yaml,
> >> but if I move it to the os-specific yaml it just shouts at me that I
> >> have not declared it... Just seems like $operatingsystem does not get
> >> passed on from puppet, even though:
> >> # facter operatingsystem
> >> CentOS
> >>
> >> and notify '{ "${operatingsystem": }' in puppet works.
> >>
> >> As mentioned, I am sure I am missing something very trivial, but maybe
> >> one of you enlightened ones can point me in the right direction!
> >>
> >> puppet version is 3.6.2
> >> hiera version i 1.3.4
> >>
> >> Thanks in advance!
> >>
> >> Karolis
> >>
>
> Hi,
>
> Good eye on the quotes, Johan. Whenever you change hiera.yaml, be sure
> to restart the puppet master.
>
> Best regards,
> -g
>
>
>
>
> --
> Garrett Honeycutt
> @learnpuppet
> Puppet Training with LearnPuppet.com
> Mobile: +1.206.414.8658
>
> --
> 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/53D93388.9060604%40garretthoneycutt.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/CANYNSSJAz1YOn6cnm0oSiG7KNehqu60TEyHq_hum2T5O97xycQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Websphere profile creation with Puppet

[randal cobb]

Hello all,

I can't seem to find any sort of solution while googling, so here goes:

I'm fairly new to Puppet and understand the concepts and solutions I've 
researched so far.  I'm even successfully building servers with all needed 
software packages.  But I'm struggling a bit with one install:  WebSphere 
app server (NOT Liberty profile, the old WAS 7.0.0.x monster - liberty 
would be a nice blessing).  I can get it installed successfully, but I 
can't find a module or suitable solution to creating an augmented profile 
via puppet.  It kinda defeats the purpose of using automated provisioning 
just to have to SSH in to each box just to create a WAS profile.  I'm also 
sure I'm not the first person who has this need, so I turn to you 
experts...  is there a module I'm missing, or perhaps googling for the 
wrong information?  Is there a way to solve this?  If so, ANY insight, even 
if its:  "dude, go goole XXX and YYY" would be helpful.  I just can't seem 
to find anything, so ANY suggestion is a good one.

Thanks in advance!
Randy

-- 
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/0877b273-5901-4bb6-9e56-52b7b43485ce%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Hiera not expanding $operatingsystem variable

[Garrett Honeycutt]

On 7/30/14 1:23 PM, Johan De Wit wrote:
> Hi,
> 
> always use quotes when using facts etc in hiera :
> 
> :hierarchy:
>   - "%{operatingsystem}"
>   - default
> 
> hth
> 
> Johan
> 
> On 30/07/14 18:21, Karolis Pabijanskas wrote:
>> Hi All,
>>
>> I am sure this is going to be something completely stupid, but I just
>> can't find the issue :)
>>
>> I have a very simple module that that needs a different filepath
>> depending on the operating system, so I'm trying to call:
>>
>> $global_bashrc_file = hiera("global_bashrc_file")
>>
>> from my module.
>>
>> The hierarchy at the moment is very simple:
>>
>> :hierarchy:
>>   - %{operatingsystem}
>>   - default
>>
>> Calling notify from the module works just fine and brings back CentOS
>> as my operating system. CentOS.yaml does exist in the  datadir and
>> does contain the variable. Running hiera in through the shell does
>> indeed show it working and returns the correct variable:
>>
>> # hiera global_bashrc_file operatingsystem=CentOS
>> /etc/bashrc
>>
>> But when trying to get this value via puppet, I just get an error:
>> Error: Could not retrieve catalog from remote server: Error 400 on
>> SERVER: Could not find data item global_bashrc_file in any Hiera data
>> file and no default supplied at blah
>>
>> It does work perfectly fine if I place the variable in default.yaml,
>> but if I move it to the os-specific yaml it just shouts at me that I
>> have not declared it... Just seems like $operatingsystem does not get
>> passed on from puppet, even though:
>> # facter operatingsystem
>> CentOS
>>
>> and notify '{ "${operatingsystem": }' in puppet works.
>>
>> As mentioned, I am sure I am missing something very trivial, but maybe
>> one of you enlightened ones can point me in the right direction!
>>
>> puppet version is 3.6.2
>> hiera version i 1.3.4
>>
>> Thanks in advance!
>>
>> Karolis
>>

Hi,

Good eye on the quotes, Johan. Whenever you change hiera.yaml, be sure
to restart the puppet master.

Best regards,
-g




-- 
Garrett Honeycutt
@learnpuppet
Puppet Training with LearnPuppet.com
Mobile: +1.206.414.8658

-- 
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/53D93388.9060604%40garretthoneycutt.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Hiera not expanding $operatingsystem variable

[Johan De Wit]

Hi,

always use quotes when using facts etc in hiera :

:hierarchy:
  - "%{operatingsystem}"
  - default

hth

Johan

On 30/07/14 18:21, Karolis Pabijanskas wrote:

Hi All,

I am sure this is going to be something completely stupid, but I just 
can't find the issue :)


I have a very simple module that that needs a different filepath 
depending on the operating system, so I'm trying to call:


$global_bashrc_file = hiera("global_bashrc_file")

from my module.

The hierarchy at the moment is very simple:

:hierarchy:
  - %{operatingsystem}
  - default

Calling notify from the module works just fine and brings back CentOS 
as my operating system. CentOS.yaml does exist in the  datadir and 
does contain the variable. Running hiera in through the shell does 
indeed show it working and returns the correct variable:


# hiera global_bashrc_file operatingsystem=CentOS
/etc/bashrc

But when trying to get this value via puppet, I just get an error:
Error: Could not retrieve catalog from remote server: Error 400 on 
SERVER: Could not find data item global_bashrc_file in any Hiera data 
file and no default supplied at blah


It does work perfectly fine if I place the variable in default.yaml, 
but if I move it to the os-specific yaml it just shouts at me that I 
have not declared it... Just seems like $operatingsystem does not get 
passed on from puppet, even though:

# facter operatingsystem
CentOS

and notify '{ "${operatingsystem": }' in puppet works.

As mentioned, I am sure I am missing something very trivial, but maybe 
one of you enlightened ones can point me in the right direction!


puppet version is 3.6.2
hiera version i 1.3.4

Thanks in advance!

Karolis

--
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/CANYNSSKRx_p2ZpG2JjJLYhRKtwwgtB-AReVozpUsovAF7dPG_g%40mail.gmail.com 
.

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



--
Johan De Wit

Open Source Consultant

Red Hat Certified Engineer  (805008667232363)
Puppet Certified Professional 2013/2014 (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:
Linux Training | https://www.open-future.be/linux-training-8-till-12th-september
Puppet Introduction Course | 
https://www.open-future.be/puppet-introduction-course-15th-september
Puppet Fundamentals Training | https://www.open-future.be/puppet-fundamentals-training-16-till-18th-september 
Zabbix Certified Specialist | https://www.open-future.be/zabbix-certified-specialisttraining-22-till-24th-september

Zabbix Certified Professional | 
https://www.open-future.be/zabbix-certified-professional-training-25-till-26th-september
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/53D92A23.4020201%40open-future.be.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] http://yum.puppetlabs.com/el/7Server ?

[Melissa Stone]

Hi Louis,

el/7Server is now a link to el/7, see https://yum.puppetlabs.com/el/7Server/


On Tue, Jul 29, 2014 at 3:11 AM, Louis Coilliot 
wrote:

> Hello, could you please add a link or copy from el/7 to el/7Server ?
>
> Like you have for el5 and el6 :
>
> http://yum.puppetlabs.com/el/6/
> http://yum.puppetlabs.com/el/6Server/
>
> http://yum.puppetlabs.com/el/5/
> http://yum.puppetlabs.com/el/5Server/
>
> This would ease deployment on official RHEL7 :
>
> $repo_puppetlabs_products =
>   'http://yum.puppetlabs.com/el/$releasever/products/$basearch',
> $repo_puppetlabs_deps =
>   'http://yum.puppetlabs.com/el/$releasever/dependencies/$basearch',
>
> $releasever is 7 on Centos 7 but 7Server on RHEL 7
>
> Thanks in advance.
>
> Louis Coilliot
>
> --
> 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/CAE9jN30KrkyMX6BmMbTaff%3D0TMqbB9oyLAp713UGYvErAy1OzA%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Melissa Stone
Release Engineer, Puppet Labs

*Join us at PuppetConf 2014 , September
20-24 in San Francisco*
*Register by July 31st to take advantage of the Early Bird discount
 **—**save $249!*

-- 
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/CAHEe_koo%2Boej3hKo0bpixLikVCtuEitV7MCHdRCcsHMba23Ztg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Hiera not expanding $operatingsystem variable

[Karolis Pabijanskas]

Hi All,

I am sure this is going to be something completely stupid, but I just can't
find the issue :)

I have a very simple module that that needs a different filepath depending
on the operating system, so I'm trying to call:

$global_bashrc_file = hiera("global_bashrc_file")

from my module.

The hierarchy at the moment is very simple:

:hierarchy:
  - %{operatingsystem}
  - default

Calling notify from the module works just fine and brings back CentOS as my
operating system. CentOS.yaml does exist in the  datadir and does contain
the variable. Running hiera in through the shell does indeed show it
working and returns the correct variable:

# hiera global_bashrc_file operatingsystem=CentOS
/etc/bashrc

But when trying to get this value via puppet, I just get an error:
Error: Could not retrieve catalog from remote server: Error 400 on SERVER:
Could not find data item global_bashrc_file in any Hiera data file and no
default supplied at blah

It does work perfectly fine if I place the variable in default.yaml, but if
I move it to the os-specific yaml it just shouts at me that I have not
declared it... Just seems like $operatingsystem does not get passed on from
puppet, even though:
# facter operatingsystem
CentOS

and notify '{ "${operatingsystem": }' in puppet works.

As mentioned, I am sure I am missing something very trivial, but maybe one
of you enlightened ones can point me in the right direction!

puppet version is 3.6.2
hiera version i 1.3.4

Thanks in advance!

Karolis

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

Re: [Puppet Users] use client_data/catalog/.json for nagios check?

[Brian Wilkins]

We use this one : 
https://github.com/liquidat/nagios-icinga-checks/blob/master/check_puppetagent

But you have to modify it if you are using an earlier version of Python for 
the date time code to get the difference. 

It's also good if you check the report file for errors. Rather than just 
the summary. We check both.


On Wednesday, July 30, 2014 9:01:48 AM UTC-4, Jason Antman wrote:
>
> I've used two different ways of doing this, depending on whether or not 
> you have this stuff installed/running:
> (1) if you have PuppetDB, just use that. I probably have a (Python) check 
> plugin for this somewhere if you need it.
> (2) use `mco puppet status` and parse the output of that
>
> These also have the advantage that they can be run as cron'ed passive 
> checks, and submit the results very efficiently.
>
>
> On Tue, Jul 22, 2014 at 6:20 PM, Denmat > 
> wrote:
>
>> This one from RIP works ok for me:
>>
>> https://github.com/ripienaar/monitoring-scripts/blob/master/puppet/check_puppet.rb
>>
>>
>> On 23 Jul 2014, at 5:47, Atom Powers > 
>> wrote:
>>
>> I use a script that checks if the puppet client is running and parses the 
>> lastrunreport for last run time and if any errors were reported applying 
>> the catalog.
>>
>>
>> On Tue, Jul 22, 2014 at 12:36 PM, Bernard Clark > > wrote:
>>
>>> We need to be alerted whenever a puppet report from any puppet client is 
>>> late. We were thinking of having Nagios monitor the last modification time 
>>> of a client's /var/lib/puppet/client_data/catalog/.json and alert us 
>>> when that file ages too much. Anyone have a better 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...@googlegroups.com .
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/puppet-users/5d8181b7-6911-4af1-95dd-24331425d80e%40googlegroups.com
>>>  
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> -- 
>> Perfection is just a word I use occasionally with mustard.
>> --Atom Powers-- 
>>
>> -- 
>> 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/CAF-H%3DOkfzUo9JD9Jt_s8z3zr-w5f5M%3DGrZACWc_s%2B52E0DrE4g%40mail.gmail.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...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/puppet-users/FF386C74-4A77-4EE4-BE09-62D0ACB129A1%40gmail.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/de6ac3cc-e46e-4b9e-aa1b-962b6382dc3c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: custom function to read inifile

[Ritesh Nanda]

Thanks Jason , i had that thing in mind , i made it part of the function
itself to download the file and then read it .

Thanks for the concern.

Regards,
Ritesh


On Wed, Jul 30, 2014 at 5:37 AM, Jason Antman  wrote:

> Before you get any further, you do understand that the inifile has to be
> on the *master*, right? Just checking, because I've seen a lot of people
> trying to write functions, and only later realizing that the data they want
> is on the node, not the master.
>
> When I've come up with issues like this (mainly JSON not ini, but
> whatever, same difference for our purposes) I put the data somewhere that
> Puppet can access natively (like in my ENC) and have puppet *write* files
> not read them.
>
>
> On Wed, Jul 23, 2014 at 6:11 PM, Ritesh Nanda 
> wrote:
>
>> Craig , i looked at that module puppetlabs-inifile, it  allows to change
>> the settings in  ini file , i want to read/parse a ini file , assign a
>> value to a variable.
>>
>> @henrik you were correct problem was with iniFile.load class . Now the
>> functions looks like
>>
>> require_relative 'inifile'
>>
>> *This allows me to keep inifile.rb file inside the function directory. Is
>> this correct ?*
>>
>> Puppet::Parser::Functions.newfunction(
>>   :inireadvalue, :type => :rvalue,
>>   :arity => 3,
>>   :doc => "Reads an .ini file and...") do |args|
>> filename   = args[0]
>> section= args[1]
>> key = args[2]
>>
>>  if !File.exist?(filename)
>>
>> raise(Puppet::ParseError, 'inireadvalue(): Path and file provided does
>> not  exists ' +
>>   'Provide the correct path')
>> end
>>
>> fileload = IniFile.load(filename)
>> data = fileload[section]
>> value = data[key]
>> return value
>>
>>
>>   end
>>
>>
>> Thanks for your help.
>>
>> Regards,
>> Ritesh Nanda
>>
>>
>> On Wed, Jul 23, 2014 at 2:31 PM, Craig Barr 
>> wrote:
>>
>>> Does this  meet your
>>> use case?
>>>
>>>
>>> On Wednesday, 23 July 2014 07:36:45 UTC+10, Ritesh Nanda wrote:

 Hello ,

 I was trying to write a custom function which would run on puppet
 master take input a ini file , parse a section of that ini file and assign
 its value to a variable .
 Something like

 $test = iniread('example.ini', 'Program', 'path')

 This would assign the value to test variable when the functions runs on
 the puppet master.

 iniread.rb file looks like

 require 'rubygems'
 require 'inifile'
 module Puppet::Parser::Functions
   newfunction(:iniread, :type => :rvalue) do |args|
 raise(Puppet::ParseError, 'inifile read(): Wrong number of arguments ' +
   "given (#{args.size} for 3)") if args.size != 3

 filename = args[0]
  section = args[1]
 key = args[2]

 file = IniFile.load(filename)
 data = file[section]
 value = data[key]
 return value

   end
 end

 It gives an error while running

 Error 400 on SERVER: undefined method `[]' for nil:NilClass at
 /etc/puppetlabs/puppet/modules/example/manifests/init.pp:45

 init.pp has

 $test =iniread("example.ini", "Program", "path")


 Doing that in ruby works

 require 'inifile'
 filename = ARGV[0]
 section = ARGV[1]
 key = ARGV[2]
 file = IniFile.load(filename)
 data = file[section]
 InstPath = data[key]
 puts InstPath

 Help to this would be really appreciated.

 Regards,
 Ritesh



   --
>>> 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/mNzxsAqTZ7I/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/705ed63d-1ae5-4fb5-afbc-6dfa7b579154%40googlegroups.com
>>> 
>>> .
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>>
>>
>> * With Regards  *
>>
>> * Ritesh Nanda*
>>
>>   --
>> 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/CAO5CbpBOAynKgnZFOr_QVe80Dxo5ccRwrYOsy6GhGg4_rvrbjA%40mail.gmail.com
>> 

[Puppet Users] Re: how to use conditional statements

[jcbollinger]

On Tuesday, July 29, 2014 7:58:32 AM UTC-5, Satish Katuru wrote:
>
> Hi 
>
> Here is my flow:
>
> Stop service-->copy required files from Master server-->Start service 
>
> Once this is done,I am taking a copy of files on Master Server and 
> removing the files from original location.
>


Why?  It would be easier and better to leave the master copy where it is on 
the master.

 

>
> I wanted to add this condition (if files are not there at that location no 
> need stop and restart the service )
>
>
> The reason behind this question is for every 30 minutes deployment will be 
> done on agent machine automatically.I just wanted to make sure that if 
> files are there then only I have to stop and start the service.
>
>

To begin, if you (may) need to stop and start the service at different 
points in the run, then you will need to use an Exec for one of those 
points.  The stop would be a better one to do that way.  The result would 
be something like this:

exec { 'Stop myservice to deploy new files':
  command => 'service myservice stop',
  path => '/usr/bin:/bin:/usr/sbin:/sbin'
  # ... see below ...
}
->
file { '/var/myservice/deployed_file':
  source => 'puppet:///modules/mymodule/deployed_file'
}
->
service { 'myservice':
  ensure => 'running'
}

Having set up something along those lines, your question boils down to how 
to avoid executing the Exec's command if file deployment is not going to 
happen.  Well, the Exec resource type has parameters 'onlyif' and 'unless' 
that it can use to determine whether the command needs to be run.  The case 
you describe is a simple one: you can simply test for the existence of your 
deployed file:

...
  unless => 'test -e /var/myservice/deployed_file'
...

Note that this general strategy doesn't work well if you remove the 
deployment file from the master.  If you do, then the File resource will 
fail on every run, and the Service will not be ensured running (though it 
may be running anyway).


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/392b1b58-8527-4614-a5e2-ec332205f79b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Manifest does work

[jcbollinger]

On Tuesday, July 29, 2014 3:28:27 PM UTC-5, Juliano Resende wrote:
>
> Hi,
>
> I'm beginner in puppet and i have a problem in implementation using puppet 
> version 3.4.2, i setup the master and the agent, but the manifests does not 
> apply on agent.
>
>

[...]

 

> Debug: Using cached certificate_revocation_list for ca
> Info: Retrieving pluginfacts
>
 

> Debug: Failed to load library 'msgpack' for feature 'msgpack'
> Debug: Puppet::Network::Format[msgpack]: feature msgpack is missing
> Debug: file_metadata supports formats: pson yaml b64_zlib_yaml raw
> Debug: Finishing transaction 70123282612320
> Info: Retrieving plugin
> Debug: Failed to load library 'msgpack' for feature 'msgpack'
> Debug: Puppet::Network::Format[msgpack]: feature msgpack is missing
> Debug: file_metadata supports formats: pson yaml b64_zlib_yaml raw
> Debug: Finishing transaction 70123282471520
> Debug: Failed to load library 'msgpack' for feature 'msgpack'
> Debug: Puppet::Network::Format[msgpack]: feature msgpack is missing
> Debug: catalog supports formats: pson dot yaml b64_zlib_yaml raw
> Info: Caching catalog for parc-puppetclient-tna-mia.tpn.terra.com
> Debug: Creating default schedules
> Debug: Loaded state in 0.00 seconds
> Info: Applying configuration version '1406664522'
> Debug: Finishing transaction 70123282264000
> Debug: Storing state
> Debug: Stored state in 0.01 seconds
>
>

Looks like the agent is receiving an empty catalog.

 

>
> Configuração do puppet.conf (master)
>
> [main]
> certname = parc-puppet01-tna-mia.exemplo.com
> dns_alt_names = parc-puppet01-tna-mia,
> parc-puppet01-tna-mia.exemplo.com
> logdir = /var/log/puppet
>
> rundir = /var/run/puppet
>
> ssldir = $vardir/ssl
> environmentpath = $confdir/environments
>
>

The environmentpath variable is associated with the "directory 
environments" feature.  This was new in Puppet 3.5, but you say you are 
running Puppet 3.4.2.  Latest is 3.6.2.

 

> [agent]
> classfile = $vardir/classes.txt
>
> localconfig = $vardir/localconfig
> [master]
> autosign = true
>
>
>

IF you were using a version of the Puppet master that supports directory 
environments, then with the puppet config you present, the site.pp file and 
any other starting-point manifests for the default ("production") 
environment would be expected to appear in $confdir/environments/production 
on the master.  On Puppet 3.4.2, with the config you present, the master 
will look for site.pp specifically, in $confdir/manifests/.

If you wish, your Puppet 3.4 clients should be able to run against a Puppet 
3.5 or 3.6 master.


John

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

Re: [Puppet Users] use client_data/catalog/.json for nagios check?

[Jason Antman]

I've used two different ways of doing this, depending on whether or not you
have this stuff installed/running:
(1) if you have PuppetDB, just use that. I probably have a (Python) check
plugin for this somewhere if you need it.
(2) use `mco puppet status` and parse the output of that

These also have the advantage that they can be run as cron'ed passive
checks, and submit the results very efficiently.


On Tue, Jul 22, 2014 at 6:20 PM, Denmat  wrote:

> This one from RIP works ok for me:
>
> https://github.com/ripienaar/monitoring-scripts/blob/master/puppet/check_puppet.rb
>
>
> On 23 Jul 2014, at 5:47, Atom Powers  wrote:
>
> I use a script that checks if the puppet client is running and parses the
> lastrunreport for last run time and if any errors were reported applying
> the catalog.
>
>
> On Tue, Jul 22, 2014 at 12:36 PM, Bernard Clark 
> wrote:
>
>> We need to be alerted whenever a puppet report from any puppet client is
>> late. We were thinking of having Nagios monitor the last modification time
>> of a client's /var/lib/puppet/client_data/catalog/.json and alert us
>> when that file ages too much. Anyone have a better 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/5d8181b7-6911-4af1-95dd-24331425d80e%40googlegroups.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Perfection is just a word I use occasionally with mustard.
> --Atom Powers--
>
> --
> 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/CAF-H%3DOkfzUo9JD9Jt_s8z3zr-w5f5M%3DGrZACWc_s%2B52E0DrE4g%40mail.gmail.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/FF386C74-4A77-4EE4-BE09-62D0ACB129A1%40gmail.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/CAFt4V4%3DdCQQbG0iVE08nNV5nuEtQGyuqm8hq7qptxmHkTjFvfQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Wrap Package in a define

[Jason Antman]

For future reference...
(1) if at all possible (I assume you did this) hacking up upstream modules
is bad
(2) I'd use pip2pi (https://github.com/wolever/pip2pi) to create a mirror
of the modules you want, and then have puppet manage /root/.pip/pip.conf
(assuming puppet is running as root) and set:

[global]
index-url = /path/to/mirror




On Mon, Jul 21, 2014 at 2:25 PM, Brian Wilkins  wrote:

> Thanks David. We have taken the route of downloading the necessary
> dependencies and then explicitly setting the source for each package
> statement. We have an FTP server for our yum repo so we just added a pip
> directory and provide the ftp:// URL to pip. That seems to work.
>
>
> On Monday, July 21, 2014 5:53:01 AM UTC-4, David Schmitt wrote:
>>
>>
>> Hi Brian,
>>
>> On 2014-07-18 14:32, Brian Wilkins wrote:
>> > Hello,
>> >
>> > We are trying to use the puppet-forge graphite module located here:
>> > https://github.com/echocat/puppet-graphite/blob/master/
>> manifests/install.pp
>> > and our servers will not have access to the Internet. So we are
>> > downloading all the pip packages to a local repository and will point
>> > pip to each package. I would like to wrap the Package type so I can
>> > provide the source. How would I do this so that the package name is
>> > passed to the defined type? My intent is to not change much of the code
>> > here:
>> > https://github.com/echocat/puppet-graphite/blob/master/
>> manifests/install.pp
>> >
>> > Otherwise, I will have to comment out alot of the manifest and replace
>> > with exec statements pointing to each individual package.
>>
>> As far as I understand the current pip provider code, it won't work
>> anyways without access to the pypi repository.
>>
>> Since pip provides a way to globally configure a different index, I
>> think that would be a much better way to achieve your goal:
>>
>> > http://pip.readthedocs.org/en/latest/user_guide.html#configuration
>>
>>  From a cursory glance over the possibilities, setting an environment
>> variable to override your index location might be another way to avoid
>> poisoning the global pip config.
>>
>>
>> Regards, David
>> --
>> * Always looking for people I can help with awesome projects *
>> G+: https://plus.google.com/+DavidSchmitt
>> Blog: http://club.black.co.at/log/
>> LinkedIn: http://at.linkedin.com/in/davidschmitt
>>
>  --
> 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/f24ebad4-f27d-41aa-978a-33ca56a9b541%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/CAFt4V4k1FV6RHaomJpOVz3ReQXyYu4Bj%2BZh0-gEGwawG%3DHW%2Beg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Use MCollective to execute test automation (long running job) on lab machines

[Jason Antman]

Agreed with everything Schmitt said. This isn't what mcollective is for,
that's not how it works, there are tools made especially for this, etc. I'm
not saying it isn't possible if you jump through enough hoops. I'm just
saying it's an incredibly bad idea.


On Mon, Jul 14, 2014 at 2:41 PM, Andrii Kalytiuk 
wrote:

> Hi,
>
> I look into ways to use MCollective to *run test automation* on lab
> machines.
>
> After couple of days of research I still have a question *is MCollective
> is right tool* to perform all required routines.
>
> *So my question is:*
> *Will it be proper* to use MCollective for following operations on
> Windows nodes - using own custom agents:
>
>1. Wait for server node (virtual machine) to become responsive after
>revert
>2. Copy file with (test automation data) from network location
>3. Unzip test automation files
>4. Update content of config files on machine
>
> Have you looked into Puppet? It does exactly what you want in steps 2-4
(maybe step 1 as well, with some additional tools).

>
>1. Run command line utility to execute test automation.
>   - Takes from couple of minutes to hour or more
>   - Console output to be returned to MCollective client
>   - Output returns to client gradually (more or less shortly after it
>   is produced on server)
>   - *Is it possible to send responses to prompts of interactive
>   command line application?*
>
> No, mcollective doesn't do this. Mcollective tasks shouldn't (can't?) work
that way. AFAIK, you tell an mco server to do something, and eventually it
tells you *that the server received the request to do something* (reply).
Also, why is your testing prompting you interactively? How do you get
reproducable tests? Or examine the output later?

>
>-
>1. Archive certain files on server
>2. Copy zip file with output files to network location
>
> As I get from documentations all points except 5th can be implemented as a
> single or several command line calls.
>
> *So main questions are:*
> Is it possible to use MCollective to execute long-running command line
> utility on server and gradually return to client output of the utility as
> it is produced?
> Is it possible to implement interaction with a command line application
> which prompts for additional user inputs on server (e. g. non-silent
> installation)?
>
> Thank you.
>
> Andrii
>
> --
> 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/6a928f6f-2381-4bcc-826f-70c58a0ce579%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/CAFt4V4km4dDLL%3DGkRLLt-JhOc0EdfULbYP4uSQpU7Y4d%3Dfwd5A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: duplicated resource with an exported resource

[Jason Antman]

Just in case anyone comes by this in the future, maybe I'm missing
something, but why not keep this really simple (did you read the type
reference docs for host?):

@@host { "${::hostname}_exported" :

  name=> $::hostname,

  ensure  => present,

  ip => $secondary_ip,

}



host { $::hostname :

  ensure  => present,

  ip  => $primary_ip
}


On Tue, Jul 15, 2014 at 3:22 PM, José Luis Ledesma <
joseluis.lede...@gmail.com> wrote:

> It worked as you thought.
>
> Many thanks, perhaps the code is not so nice, but the config applied is,
> by far, better.
>
> Regards,
> El 15/07/2014 15:24, "jcbollinger"  escribió:
>
>
>>
>> On Monday, July 14, 2014 8:55:38 AM UTC-5, Kristof Willaert wrote:
>>>
>>> [snip]
>>>
>>> You will not be able to collect that resource on the node that exports
 it (you would again -- and rightfully -- get a duplicate resource
 complaint), but I think otherwise you should be ok.

>>>
>>> The documentation for exported resources suggests otherwise:
>>>
>>> Any node (including the node that exported it) can then *collect* the
>>> exported resource and manage its own copy of it. [1]
>>>
>>> I must say I haven't tried it myself, but unless I misinterpret the
>>> sentence above, it should be possible.
>>>
>>
>>
>> You're not misinterpreting the docs, but you *are* misinterpreting my
>> statement.  Although *generally* the node exporting a resource can
>> collect that resource, if the OP used the approach I described then his
>> nodes would not be able to collect the Site::Secondary_host resources they
>> declare themselves.  If they tried to collect their own, then it would
>> yield a duplicate Host resource (from the defined type body; because he
>> already, separately, declares a Host for the node itself).  The key there
>> is that -- I think -- the type's body will not be evaluated by the
>> declaring node for instances that it does not collect, even those that it
>> declares itself.
>>
>>
>> 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/e05c726c-b0ca-40be-8f5a-a38df765a9cf%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/CAF_B3ddtHrbANnKirUdvic9wgC7DxWmgtLy%3D4_TErgEmn5vMWQ%40mail.gmail.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/CAFt4V4n3EW8oWAXTf6xgTF%3DG0%2B_KnU6SHL8CJ-pE02jEXJabZw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Work around for dynamic environments and modules with custom types

[Chris Gibbs]

Just wondering if anyone has a work around for this bug

https://tickets.puppetlabs.com/browse/PUP-1515 

Im trying to use the puppetlabs-mysql module, specifically with the 
mysql::db custom type. Keep gettng a 400 error. Using r10k to populate 
environments and pull modules.

cheers,


-- 
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/fc6d7bbd-4767-45b8-9683-d924ff38a035%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: custom function to read inifile

[Jason Antman]

Before you get any further, you do understand that the inifile has to be on
the *master*, right? Just checking, because I've seen a lot of people
trying to write functions, and only later realizing that the data they want
is on the node, not the master.

When I've come up with issues like this (mainly JSON not ini, but whatever,
same difference for our purposes) I put the data somewhere that Puppet can
access natively (like in my ENC) and have puppet *write* files not read
them.


On Wed, Jul 23, 2014 at 6:11 PM, Ritesh Nanda 
wrote:

> Craig , i looked at that module puppetlabs-inifile, it  allows to change
> the settings in  ini file , i want to read/parse a ini file , assign a
> value to a variable.
>
> @henrik you were correct problem was with iniFile.load class . Now the
> functions looks like
>
> require_relative 'inifile'
>
> *This allows me to keep inifile.rb file inside the function directory. Is
> this correct ?*
>
> Puppet::Parser::Functions.newfunction(
>   :inireadvalue, :type => :rvalue,
>   :arity => 3,
>   :doc => "Reads an .ini file and...") do |args|
> filename   = args[0]
> section= args[1]
> key = args[2]
>
>  if !File.exist?(filename)
>
> raise(Puppet::ParseError, 'inireadvalue(): Path and file provided does not
>  exists ' +
>   'Provide the correct path')
> end
>
> fileload = IniFile.load(filename)
> data = fileload[section]
> value = data[key]
> return value
>
>
>   end
>
>
> Thanks for your help.
>
> Regards,
> Ritesh Nanda
>
>
> On Wed, Jul 23, 2014 at 2:31 PM, Craig Barr 
> wrote:
>
>> Does this  meet your
>> use case?
>>
>>
>> On Wednesday, 23 July 2014 07:36:45 UTC+10, Ritesh Nanda wrote:
>>>
>>> Hello ,
>>>
>>> I was trying to write a custom function which would run on puppet master
>>> take input a ini file , parse a section of that ini file and assign
>>> its value to a variable .
>>> Something like
>>>
>>> $test = iniread('example.ini', 'Program', 'path')
>>>
>>> This would assign the value to test variable when the functions runs on
>>> the puppet master.
>>>
>>> iniread.rb file looks like
>>>
>>> require 'rubygems'
>>> require 'inifile'
>>> module Puppet::Parser::Functions
>>>   newfunction(:iniread, :type => :rvalue) do |args|
>>> raise(Puppet::ParseError, 'inifile read(): Wrong number of arguments ' +
>>>   "given (#{args.size} for 3)") if args.size != 3
>>>
>>> filename = args[0]
>>> section = args[1]
>>> key = args[2]
>>>
>>> file = IniFile.load(filename)
>>> data = file[section]
>>> value = data[key]
>>> return value
>>>
>>>   end
>>> end
>>>
>>> It gives an error while running
>>>
>>> Error 400 on SERVER: undefined method `[]' for nil:NilClass at
>>> /etc/puppetlabs/puppet/modules/example/manifests/init.pp:45
>>>
>>> init.pp has
>>>
>>> $test =iniread("example.ini", "Program", "path")
>>>
>>>
>>> Doing that in ruby works
>>>
>>> require 'inifile'
>>> filename = ARGV[0]
>>> section = ARGV[1]
>>> key = ARGV[2]
>>> file = IniFile.load(filename)
>>> data = file[section]
>>> InstPath = data[key]
>>> puts InstPath
>>>
>>> Help to this would be really appreciated.
>>>
>>> Regards,
>>> Ritesh
>>>
>>>
>>>
>>>  --
>> 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/mNzxsAqTZ7I/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/705ed63d-1ae5-4fb5-afbc-6dfa7b579154%40googlegroups.com
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
>
>
> * With Regards  *
>
> * Ritesh Nanda*
>
>   --
> 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/CAO5CbpBOAynKgnZFOr_QVe80Dxo5ccRwrYOsy6GhGg4_rvrbjA%40mail.gmail.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-

Re: [Puppet Users] how to use conditional statements

[Jason Antman]

Puppet is idempotent. It doesn't work that way. Puppet declares intended
state. So you tell puppet "service should be running and files should be
there" and Puppet makes it so. If you have a "thing" that should be
implemented/executed in a specific way with specific ordering, that's what
custom providers (and types for them) are for.

Maybe someone else will chime in with a better solution than "write a
custom provider to do something awful", but every time I've run up against
this I've just decided that I either needed a provider for it, or the
application was broken and needed to be fixed.

-Jason


On Tue, Jul 29, 2014 at 8:58 AM, Satish Katuru 
wrote:

> Hi
>
> Here is my flow:
>
> Stop service-->copy required files from Master server-->Start service
>
> Once this is done,I am taking a copy of files on Master Server and
> removing the files from original location.
>
> I wanted to add this condition (if files are not there at that location no
> need stop and restart the service )
>
>
> The reason behind this question is for every 30 minutes deployment will be
> done on agent machine automatically.I just wanted to make sure that if
> files are there then only I have to stop and start the service.
>
>
> Thanks,
> Satish.
>
> --
> 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/e1ef43c1-fc2a-4893-9584-730d044709f3%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/CAFt4V4%3DzA0zDJdjAzuJakTPSvH05%2Bh7YxpvyXGd4echzDkU6GQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] increasing frequency of puppet agent runs during initial deployment?

[Jason Antman]

I've seen those environments. I've worked in them. A few host types in my
current environment are like that. IT IS A BUG. The only valid reason for
this is either a bug in your manifests/modules, or that things aren't
ordered properly.

That being said... don't run via cron. If you're using any sort of
provisioning system, just have that run puppet until it succeeds. If you're
not, then at host provisioning time, you could use a script that runs
puppet until it succeeds.


On Tue, Jul 29, 2014 at 11:26 AM, jcbollinger 
wrote:

>
>
> On Monday, July 28, 2014 2:20:33 PM UTC-5, Christopher Wood wrote:
>>
>> Before figuring out how to shorten the initial agent runs, I'd inquire
>> why a full configuration takes several agent runs.
>
>
> +1
>
> I have never seen or heard about an environment that *required* multiple
> Puppet runs to converge to a stable configuration.  I may have seen one or
> two where it was more *convenient* to allow two runs for convergence than
> to make the necessary arrangements for Puppet to apply a complete config to
> a new machine in just one run.  But never more than two, even for
> convenience.
>
>
> 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/e4b6cb7d-45b5-48db-95ca-0a0aca5448e5%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/CAFt4V4nJgmUoVYQ-5_Qm9UESoQmYiP0xFwn2fWvAhsG4MN6oEA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Puppet-dashboard issues

[Benjamin Cayzac]

Hi !

Problem fixed !

Syntax wasn't good, i found on old doc but i've search again and i've found 
another syntaxe to do the same thing : "bundle exec rake db:migrate 
RAILS_ENV=production"

And it works ! the database has been generated.

I just want to know how to use the dashboard db with puppet. And if it's 
possible to fill that db automaticaly when a puppet agent connects itself 
to the puppetmaster.
Fill the nodes table and reports table etc.

More information on my configuration :
Passenger : 4.0
Puppet-dashboard : 2.0 Beta
i've just changed puppetmaster : 3.6

thx

Le mardi 29 juillet 2014 16:20:23 UTC+2, Benjamin Cayzac a écrit :
>
> Hi ! 
>
> (sorry for my poor english) 
>
>
> My puppetmaster 3.4.3 run on Ubuntu 14.04 LTS 
>
> I've just manage to replace WEBrick, Puppet use Apache/Passenger to work 
> now. 
>
> I'm a newbie on this, so i've setup Puppet with different docs found on 
> internet. I've started with "apt-get" for the basic install. 
>
> For Passenger, I tried gems. Ruby version is 1.9.1, I saw that is the 
> source 
> of many problems but i'm a newbie on linux too... I don't know if a 
> downgrad 
> of ruby is a good idea or not, or if it is necessary. 
>
> Puppet works fine, but my problem concern dashboard. 
>
> So here is my problem : 
>
> I've configured with success the vhost for apache. 
> I've created the database on mysql. 
>
> but when i run "rake RAILS_ENV=production db:migrate" i've got an error : 
> Warning: Rails rake tasks currently unavailable because we can't find the 
> 'rails' gem 
> rake aborted! 
> Don't know how to build task 'db:migrate' 
>
> trace : 
>
> /var/lib/gems/1.9.1/gems/rake-10.3.2/lib/rake/task_manager.rb:62:in `[]' 
> /var/lib/gems/1.9.1/gems/rake-10.3.2/lib/rake/application.rb:149:in 
> `invoke_task' 
> /var/lib/gems/1.9.1/gems/rake-10.3.2/lib/rake/application.rb:106:in `block 
> (2 levels) in top_level' 
> /var/lib/gems/1.9.1/gems/rake-10.3.2/lib/rake/application.rb:106:in `each' 
> /var/lib/gems/1.9.1/gems/rake-10.3.2/lib/rake/application.rb:106:in `block 
> in top_level' 
> /var/lib/gems/1.9.1/gems/rake-10.3.2/lib/rake/application.rb:115:in 
> `run_with_threads' 
> /var/lib/gems/1.9.1/gems/rake-10.3.2/lib/rake/application.rb:100:in 
> `top_level' 
> /var/lib/gems/1.9.1/gems/rake-10.3.2/lib/rake/application.rb:78:in `block 
> in 
> run' 
> /var/lib/gems/1.9.1/gems/rake-10.3.2/lib/rake/application.rb:176:in 
> `standard_exception_handling' 
> /var/lib/gems/1.9.1/gems/rake-10.3.2/lib/rake/application.rb:75:in `run' 
> /var/lib/gems/1.9.1/gems/rake-10.3.2/bin/rake:33:in `' 
> /usr/local/bin/rake:23:in `load' 
> /usr/local/bin/rake:23:in `' 
>
>
> Any idea ? 
>
> thx 
>
>
>

-- 
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/aa4bf090-0c26-438b-9e86-1b58176b21b1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: How to group systems using Puppet and hiera?

[Pete Brown]

On 29 July 2014 17:24, Grant Street  wrote:
> I think my problem was I was trying to set the role variable under a
> "parameters:" clause in my group yaml file... e
> I'm also trying your method, Pete, but I'm hitting a snag.
>
> I have certname.yaml file that contains

Sorry I composed that email on my phone.
I meant certname to be the variable $::certname.
Which is usually the $::fqdn of your node.

So if the $::fqdn is www.example.com the file should be named
www.example.com.yaml


> ---
> role: modeler
>
> and a file modeler.yaml that contains
> ---
> classes:
>  - my_class
>
> But I am getting an error saying
> Error: Could not find class modeler for .
>
> If I set the certname.yaml to
> ---
> parameters:
>   role: modeler
>
> I get
> Error: Could not find data item role in any Hiera data file and no default
> supplied at .
>
> Am I doing something wrong?
>
>
> On Sunday, July 27, 2014 4:46:45 PM UTC+10, Pete wrote:
>>
>>
>> On 27 Jul 2014 16:42, "Pete Brown"  wrote:
>> >
>> > I have taken to using hiera as my ENC these days.
>> >
>> > My site.pp is basically
>> > hiera_Include(role)
>> > And each nide as a role variable set in my certname.yaml file.
>>
>> Dammit.
>> Each node has a role variable.
>>
>>
> --
> 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/c4f24ba9-ecdf-4707-b24e-c61e28473c99%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/CAJ8DPF5DSaktixVxS9L3RnJMvMwDJP_deVL%3DGt2Ta1d6-uo4cg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.