[Puppet Users] Module parameter handling

[Thomas Bendler]

Hi @all,

I write a module that create local users on my boxes. Now I try to make
that module fully dynamic so that the user informations are passed to the
module as parameter like this:

class { 'local_users':
  user => [
{ 'john' => { name => 'John Doe', home => '/export/home/john' } },
{ 'jane' => { name => 'Jane Doe', home => '/export/home/jane' } }
  ]
}

So far, so good. But now I would like to iterate through the user array and
create the user resource and I have no clue how this should be done
correctly. My approach is to call a define:

local_users::config::account { $local_users::user }

Which look like this:

define local_users::config::account (
  $id   = $title,
  $name = undef,
  $home = undef
) {
  user { $id:
ensure => present,
  comment=> $name,
  home   => $home,
  managehome => true,
  password   => '!!';
  }
}

I guess the direction should be understandable, I would like to specify the
users and their attributes as a parameter. What I don't get so far is, do I
need one resource definition for each possible combination or is there a
way that only the parameter that contain values are used within the
resource type? Is the path in general the correct one that I use or is
there a better approach to get this done?

​Regards Thomas​
-- 
Linux ... enjoy the ride!

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

Re: [Puppet Users] Module parameter handling

[Hristo Mohamed]

Look up on the create_resources function on the docs.
If I undestood you correctly, you want to create all the users from your
hash, with the user type at ONCE?
If yes, this will do nicely :)

Hristo

On Wed, Mar 2, 2016 at 11:26 AM, Thomas Bendler 
wrote:

> Hi @all,
>
> I write a module that create local users on my boxes. Now I try to make
> that module fully dynamic so that the user informations are passed to the
> module as parameter like this:
>
> class { 'local_users':
>   user => [
> { 'john' => { name => 'John Doe', home => '/export/home/john' } },
> { 'jane' => { name => 'Jane Doe', home => '/export/home/jane' } }
>   ]
> }
>
> So far, so good. But now I would like to iterate through the user array
> and create the user resource and I have no clue how this should be done
> correctly. My approach is to call a define:
>
> local_users::config::account { $local_users::user }
>
> Which look like this:
>
> define local_users::config::account (
>   $id   = $title,
>   $name = undef,
>   $home = undef
> ) {
>   user { $id:
> ensure => present,
>   comment=> $name,
>   home   => $home,
>   managehome => true,
>   password   => '!!';
>   }
> }
>
> I guess the direction should be understandable, I would like to specify
> the users and their attributes as a parameter. What I don't get so far is,
> do I need one resource definition for each possible combination or is there
> a way that only the parameter that contain values are used within the
> resource type? Is the path in general the correct one that I use or is
> there a better approach to get this done?
>
> ​Regards Thomas​
> --
> Linux ... enjoy the ride!
>
> --
> 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/CAELoU1NfDYgjqgHsH%3DAGmOsM9GG1nuAfnRibc_fA9cRUe5uMug%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/CALuoJ66aL%2BoQoMGBVrY6qMfL8ffVOZJE8-8-CRcTo_QZSH76PQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Help needed : Upgrade pf weblogic 12.1.3 to 12.2.1

[bert hajee]

Hi Meenu,

I'm not sure what your exact problem is, but you can check out 
https://www.enterprisemodules.com/ and look for the WebLogic modules. You 
can also find some blog articles about extracting the configuration 
information. Checkout the blog 
to https://www.enterprisemodules.com/blog/archive/category/weblogic

Hope this gives you some pointers.

regards,

Bert Hajee



On Monday, 29 February 2016 17:32:43 UTC+1, Sumit Gupta wrote:
>
> Hi All,
>
> I am new to puppet and recently installed a weblogic domain 12.1.3. Now my 
> company's requirement is to upgrade this to 12.2.1. I just wanted to check 
> if this is possible using puppet? If yes, any pointers to the script will 
> be appreciated.
>
> Thanks
> Meenu
>

-- 
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/7603eeed-88c8-40c3-b639-17088f89ea49%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Custom type, relationship and fetch order

[Thomas Champagne]

Thanks for answering Felix,

I solve some problems with require/before parameters in the manifest. I 
create a new type (user_group) that define link between user and group. The 
provider of user_group type call the provider of user to get the 
relationship.

And I define new type in the manifest module : 
define rest::user (
  $user_name = $title,
  $ensure = present,
  $groups = [],
) {
  user { $title: ensure => $ensure, before => Group[$groups], }
 user_group { $title: ensure => $ensure, groups => $groups, require => [User
[$title], Group[$groups]], }
}

define rest::group (
  $user_name = $title,
  $ensure = present,
) {
  group { $title: ensure => $ensure, }
}

So in the manifest, I define my node like this : 

node 'host' {
rest::user { 'bob':
ensure => present,
groups => ['user','developer'],
}
rest::user { 'alex':
ensure => present,
groups => ['user'],
}
rest::group { 'developer',
ensure => present,
}
rest::group { 'user',
ensure => present,
}
}
Now, the log is 
prefetch user
flush user 'bob'
flush user 'alex'
prefetch group
flush group 'developer'
flush group 'user'
prefetch user_group
flush user_group 'bob'
flush user_group 'alex'

I have last problem. When I only configure group that ensure is absent :
node 'host' {
  rest::group { 'developer',
ensure => absent,
  }
}

There is no user defined and so, user provider doesn't fetch user data. If 
there is a real relationship between the group and a user, the deletion 
failed because group provider doesn't know the relationship. 
Is there a way to force fetch of a type ?

Thomas

-- 
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/79027b5b-552c-477b-8eab-72e315de94c0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Custom type, relationship and fetch order

[Felix Frank]

Hi,

I'm not sure about directly forcing a prefetch action.

However, it seems to me that it would make sense for you to implement a 
*generate* method for your group type. It should enumerate the users 
that are members of the group and create a Puppet resource each. (Don't 
worry about duplicates, Puppet will prune those for you.)


HTH,
Felix

On 03/02/2016 02:23 PM, Thomas Champagne wrote:

Thanks for answering Felix,

I solve some problems with require/before parameters in the manifest. 
I create a new type (user_group) that define link between user and 
group. The provider of user_group type call the provider of user to 
get the relationship.


And I define new type in the manifest module :
|
define rest::user (
  $user_name =$title,
  $ensure =present,
  $groups =[],
){
  user {$title:ensure=>$ensure,before =>Group[$groups],}
 user_group {$title:ensure=>$ensure,groups 
=>$groups,require=>[User[$title],Group[$groups]],}

}
|

|
define rest::group(
  $user_name =$title,
  $ensure =present,
){
group{$title:ensure=>$ensure,}
}
|
|
So in the manifest, I define my node like this :
|
|
node 'host'{
rest::user {'bob':
ensure=>present,
groups =>['user','developer'],
}
rest::user {'alex':
ensure=>present,
groups =>['user'],
}
rest::group{'developer',
ensure=>present,
}
rest::group{'user',
ensure=>present,
}
}
|
|Now, the log is
||prefetch user
flush user 'bob'
flush user 'alex'
||prefetch group
flush group 'developer'
flush group 'user'
||prefetch user_group
||flush user_group 'bob'
flush user_group 'alex'|

I have last problem. When I only configure group that ensure is absent :
|
|
|node 'host'{
|rest::group{'developer',
ensure=>absent,
}
}
|

There is no user defined and so, user provider doesn't fetch user 
data. If there is a real relationship between the group and a user, 
the deletion failed because group provider doesn't know the relationship.

Is there a way to force fetch of a type ?

Thomas|


--
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/56D6FA49.8060802%40Alumni.TU-Berlin.de.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Custom type, relationship and fetch order

[Thomas Champagne]

Yes, I agree with you. I have seen this solution in the "resources" type 
that generate resources to purge them. 
So, you tell : in the generate method of "group" type, it call instance 
method of the user provider to generate user. With this solution, if I 
define a user in the node, the rest endpoint will be apply twice : the 
first time with prefetch "user" provider and second time by the generate 
method of "group" type. I would like to limit calls to REST API. 

I think I must cache answer of the first call to rest endpoint user in the 
"user" provider. So, the "group" provider can get relationship without 
calling again the REST API. If there is no defined user, "user" provider 
doesn't have prefetched data but it will cache them at first call. 

Do you think it is the better implementation ?
Do you know if there is other module with this implementation ?

-- 
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/bcea1b07-b486-4c93-8b79-008a8ce0d00b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Hiera Data Binding not working on some modules

[Julio Guevara]

Hi Puppet Users,

the situation is as follow. I have been trying to use the Data binding 
feature of hiera for this module 
https://forge.puppetlabs.com/jlambert121/puppet i have the following:

dist/profiles/manifests/puppet_master.pp
class profiles::puppet_master ($hello) {
  include ::puppet
  notify { $hello : }
}

dist/roles/manifests/puppet_master.pp
class roles::puppet_master {
  include profiles::puppet_master
}


hieradata/node/example.domain.yaml
---
role:
  - '::roles::puppet_master'

profiles::puppet_master::hello: 'Hello World'
puppet::server: true
puppet::server_version: 'latest'
puppet::dns_alt_names:
  - 'puppet.domain'
puppet::puppetdb_server: 'puppet.domain'
puppet::puppetdb: true
puppet::manage_puppetdb: false
puppet::manage_hiera: false
puppet::firewall: true


puppetdb::listen_address: '0.0.0.0'


hiera::hierarchy:
  - 'node/%%{::}{networking.fqdn}'
  - 'type/%%{::}{type}'
  - 'location/%%{::}{location}/%%{::}{type}'
  - 'location/%%{::}{location}'
  - 'common'
hiera::datadir: 
'/etc/puppetlabs/code/environments/%%{::}{::environment}/hieradata'

r10k::version: '2.1.1'
r10k::sources:
  environments:
remote: 'g...@xxx.xxx.xxx.xxx:puppet-control'
basedir: '%%{::}{settings.environmentpath}'
prefix: false
r10k::manage_modulepath: false

The thing is that i can mange to data bind with hiera the value 
profiles::puppet_master::hello, but i'm unable to do the same thing for all 
the other values.
Because of this they go to their defaults values and actually uninstall my 
puppet server on the master :/

Can you guys help me out figuring why this is working for the puppet_master 
class but not for the puppet module?

Thanks
Julio

-- 
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/7831831a-014d-4b75-81c7-09c9a14ba77f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Force Fact within manifest

[Kylo Ginsberg]

On Tue, Mar 1, 2016 at 9:09 AM, JS  wrote:

> Which guy?  The OP?
>
> Yep, OP, per the rest of the post.
>
> That's not what anyone else in this necro'd thread said back in its
>> previous life, so exactly what and who are you agreeing with?
>
> Yes, it was actually this necro'd threads main point of emphasis,
> including subject, introduction, middle and final answer from OP.  Even the
> word "requirement" was used.
>
> Yes, they can, but normally they are zilch (nada, bumpkus, zero).
>> Moreover, even when massive changes are applied, they rarely change the
>> values of any of the standard facts.  Of course, all bets are off with
>> custom facts.
>
> "Normally" and Puppet dont really go hand in hand with the vast
> customizable use of it, especially when custom facts come into the equation.
>
> Well that's not what Puppet is, or ever was intended to be.
>
> Many products start out not intending to be what they become.
> It may not be the purpose of Puppet, but Puppet uses Facter, which does
> report facts, so they are basically bonded to each other.  If something
> becomes what it wasn't intended to be, should the designer and creator
> continue to tell users they are using it wrong?  Seems to me a lot of
> things have failed that way.
>
> it would be a potentially dangerous mistake to rely on PuppetDB to hold an
>> accurate representation of node state between Puppet runs.  Furthermore, it
>> is difficult to determine at the time you query PuppetDB whether the node
>> in question actually is between runs, as for each node there will be from
>> seconds to minutes out of each catalog run interval in which a catalog run
>> is in progress.
>
> Querying isn't an issue with mcollective. Nor is puppet going to run with
> a statelock.  I even have a custom fact that says when the facts were
> gathered, so I have exact time stamps.
>
> I'm not so sure that yours is a commonly requested feature.
>
> The word "common" means something different to each individual.  However,
> I have had 3 customers request this feature, which have led to searches,
> which have led to quite a few requests from others, over the years.  Just
> as the OP has requested here.
> I wouldnt say its common to "hope" puppet recognizes fact values during a
> run, I would almost say that is expected.
>
> I think the best debate I read against our wishes or hopes, was that facts
> should only be viewed as what they were prior to a catalog run.  I guess
> that makes sense.  However, since they CAN and ARE used as a reporting
> method or "inventory", there should be some form of seeing what they have
> changed to.
> The other side of this debate though too, is users that want to see what
> the facts are BEFORE a puppet run.  Current reported facts would only show
> what they were before the previous run, which is also not an "accurate
> representation".
>
> Puppet is a configuration management system, not an inventory system.  To
>> the extent that it can also serve incidentally as a poor man's inventory
>> system, that's great, but not of much import to me.  As far as I am
>> concerned, Puppet is better suited to working alongside or even under an
>> inventory system than it is to working as an inventory system
>
> I suppose most of what I said could use subbing of the word "Puppet" with
> "Facter".   I do agree that Puppet doesn't need to, and probably even
> shouldn't always grab the changed facts at the end of the run.  However,
> Facter itself is widely used as a reporting or inventory system (and even
> marketed by puppetlabs as so).  Thus, I do agree what you say, in regards
> to Puppet.  However, they are two separate systems that work together.  I
> think most people just want to see Facter expand on the whole gathering of
> inventory.  No need to pull in another inventory management system, when
> Facter can do it.   Facter and Puppet allow you to get new facts at the
> end, but don't provide any native way of doing so.  I think that is the
> main point people that request this are trying to say.
>
> You are in luck, however: Puppet's source is open
>
> Yep, and thats what makes it such an amazing tool and great community.  As
> well as allows users like myself, OP, and others, that want this kind of
> reporting feature, to be able to actually do so.
>
> All in all, I truly understand what you're saying, and even agree when it
> comes to Puppet.  Although, I also believe all things can be made better.
> Giving users the ability to query changed or custom facts, after a puppet
> run (or heck even without Puppet at all, just via Facter), seems like
> something that could be made better.
>
> Right now, (especially since postrun_command is broke in windows) I run a
> quick powershell script in its own new session that calls puppet upload
> facts, or a nohup in the background (if nix), after every puppet run.  This
> keeps it in its own environment and outside of puppets ruby process and env
> vars.  I then use a ENC script to pull in the lat

[Puppet Users] Re: Hiera Data Binding not working on some modules

[Julio Guevara]

Running the puppetserver on debug mode i got the following:

puppet::server
2016-03-02 13:25:27,995 DEBUG [puppet-server] Puppet Performing a hiera 
indirector lookup of puppet::server with options {:variables=>Scope(Class[
Puppet]), :merge=>#>, 
@value_type=#]>>>]>, @options={}>}
2016-03-02 13:25:27,995 DEBUG [puppet-server] Puppet hiera(): Looking up 
puppet::server in YAML backend
2016-03-02 13:25:27,996 DEBUG [puppet-server] Puppet hiera(): Looking for 
data source node/kcinf-puppetdb01p.infrastructure.us.loc
2016-03-02 13:25:27,996 DEBUG [puppet-server] Puppet hiera(): Cannot find 
datafile /etc/puppetlabs/code/environments//hieradata/node/example.domain, 
skipping
2016-03-02 13:25:27,997 DEBUG [puppet-server] Puppet hiera(): Looking for 
data source type/PUPPETDB
2016-03-02 13:25:27,997 DEBUG [puppet-server] Puppet hiera(): Cannot find 
datafile /etc/puppetlabs/code/environments//hieradata/type/PUPPETDB.yaml, 
skipping
2016-03-02 13:25:27,997 DEBUG [puppet-server] Puppet hiera(): Looking for 
data source location/KC/PUPPETDB
2016-03-02 13:25:27,998 DEBUG [puppet-server] Puppet hiera(): Cannot find 
datafile 
/etc/puppetlabs/code/environments//hieradata/location/KC/PUPPETDB.yaml, 
skipping
2016-03-02 13:25:27,998 DEBUG [puppet-server] Puppet hiera(): Looking for 
data source location/KC
2016-03-02 13:25:27,998 DEBUG [puppet-server] Puppet hiera(): Cannot find 
datafile /etc/puppetlabs/code/environments//hieradata/location/KC.yaml, 
skipping
2016-03-02 13:25:27,998 DEBUG [puppet-server] Puppet hiera(): Looking for 
data source common
2016-03-02 13:25:27,999 DEBUG [puppet-server] Puppet hiera(): Cannot find 
datafile /etc/puppetlabs/code/environments//hieradata/common.yaml, skipping

profiles::puppet_master::hello
2016-03-02 13:25:27,951 DEBUG [puppet-server] Puppet Performing a hiera 
indirector lookup of profiles::puppet_master::hello with options {:variables
=>Scope(Class[Profiles::Puppet_master]), 
:merge=>#>, 
@value_type=#]>>>]>, @options={}>}
2016-03-02 13:25:27,951 DEBUG [puppet-server] Puppet hiera(): Looking up 
profiles::puppet_master::hello in YAML backend
2016-03-02 13:25:27,952 DEBUG [puppet-server] Puppet hiera(): Looking for 
data source node/example.domain
2016-03-02 13:25:27,952 DEBUG [puppet-server] Puppet hiera(): Found profiles
::puppet_master::hello in node/example.domain

it seems to be that the environment is nil when trying to look for the 
puppet::server key but it is there for the profiles::puppet_master::hello 
search.
Any idea?

On Wednesday, March 2, 2016 at 10:41:05 AM UTC-6, Julio Guevara wrote:
>
> Hi Puppet Users,
>
> the situation is as follow. I have been trying to use the Data binding 
> feature of hiera for this module 
> https://forge.puppetlabs.com/jlambert121/puppet i have the following:
>
> dist/profiles/manifests/puppet_master.pp
> class profiles::puppet_master ($hello) {
>   include ::puppet
>   notify { $hello : }
> }
>
> dist/roles/manifests/puppet_master.pp
> class roles::puppet_master {
>   include profiles::puppet_master
> }
>
>
> hieradata/node/example.domain.yaml
> ---
> role:
>   - '::roles::puppet_master'
>
> profiles::puppet_master::hello: 'Hello World'
> puppet::server: true
> puppet::server_version: 'latest'
> puppet::dns_alt_names:
>   - 'puppet.domain'
> puppet::puppetdb_server: 'puppet.domain'
> puppet::puppetdb: true
> puppet::manage_puppetdb: false
> puppet::manage_hiera: false
> puppet::firewall: true
>
>
> puppetdb::listen_address: '0.0.0.0'
>
>
> hiera::hierarchy:
>   - 'node/%%{::}{networking.fqdn}'
>   - 'type/%%{::}{type}'
>   - 'location/%%{::}{location}/%%{::}{type}'
>   - 'location/%%{::}{location}'
>   - 'common'
> hiera::datadir: 
> '/etc/puppetlabs/code/environments/%%{::}{::environment}/hieradata'
>
> r10k::version: '2.1.1'
> r10k::sources:
>   environments:
> remote: 'g...@xxx.xxx.xxx.xxx:puppet-control'
> basedir: '%%{::}{settings.environmentpath}'
> prefix: false
> r10k::manage_modulepath: false
>
> The thing is that i can mange to data bind with hiera the value 
> profiles::puppet_master::hello, but i'm unable to do the same thing for all 
> the other values.
> Because of this they go to their defaults values and actually uninstall my 
> puppet server on the master :/
>
> Can you guys help me out figuring why this is working for the 
> puppet_master class but not for the puppet module?
>
> Thanks
> Julio
>

-- 
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/a9dd192d-86aa-4c3e-a995-d63c94255e54%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] IS it possible to generate dynamically the configuration of a node ?

[Martin Rodriguez]

Hi,

I'm new to puppet and a java developer.

I'm looking for a way to force the puppet server to connect to my java app 
to get the configuration of a node ?

If it is possible, could you please give an example of the code like a 
hello world.

I just simply want to generate file type configs dynamically (configuration 
inside database) without to write directly the sites.pp file.

Thanks a lot for your help.


-- 
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/47676c1a-6302-4936-8d26-938e9177d4fb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] IS it possible to generate dynamically the configuration of a node ?

[Peter Kristolaitis]

This is exactly what an ENC is for: 
https://docs.puppetlabs.com/guides/external_nodes.html



On 3/2/2016 4:56 PM, Martin Rodriguez wrote:

Hi,

I'm new to puppet and a java developer.

I'm looking for a way to force the puppet server to connect to my java 
app to get the configuration of a node ?


If it is possible, could you please give an example of the code like a 
hello world.


I just simply want to generate file type configs dynamically 
(configuration inside database) without to write directly the sites.pp 
file.


Thanks a lot for your help.


--
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/47676c1a-6302-4936-8d26-938e9177d4fb%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/56D76749.3030502%40alter3d.ca.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] running puppet cert list as a regular user - not root

[warron.french]

Have you checked the Unix perms?
On Feb 28, 2016 8:30 PM, "solarflow 99"  wrote:

> Does anyone know if this can be done with puppet OSS?
>
>
> --
> 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/b1352b8f-9094-4eb4-8496-e862b192c3a7%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/CAJdJdQmVP%2BXSwRhyBmb0bgkS-vepFGag0ioTK-hL0Dx%3DoUdzfw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Nagios installation with puppet

[moonsun1124]

Hi, do we have any good document on installation of nagios by using puppet.
 
I am using puppet 4.3 enterprise version and cent os 7. I have checked 
couple of url but those are not working. 


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/6ccbaedc-9cd9-46fc-9381-0e90e2fec593%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Nagios installation with puppet

[Leonardo]

Try to install puppet module.
#puppet module search nagios


Em quarta-feira, 2 de março de 2016 20:45:23 UTC-3, moons...@gmail.com 
escreveu:
>
> Hi, do we have any good document on installation of nagios by using puppet.
>  
> I am using puppet 4.3 enterprise version and cent os 7. I have checked 
> couple of url but those are not working. 
>
>
> 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/5637cfe1-0183-4208-9700-0a4094fb5169%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.