Hi everyone, first post. I've got Puppet installed on a FreeBSD 8.3
client & server from the guides, and deploying simple packages from the
default node and a node which inherits it. I have /usr/ports mounted via
NFS from the puppet server.
I have two queries now:
1. For more complicated pack
Hi again,
From examples I have gleaned the following snippet for manifests/site.pp
Package {provider => $operatingsystem ? {
FreeBSD => freebsd,
#FreeBSD => ports,
debian => aptitude,
redhat => up2date}}
Are there providers documented somewhere? I'm not
On 29/06/12 02:18, R. Tyler Croy wrote:
On Thu, 28 Jun 2012, Gregory Orange wrote:
Are there providers documented somewhere? I'm not sure where to
The different package resource providers and their differences documented here:
<http://docs.puppetlabs.com/references/latest/type.html
On 29/06/12 14:38, Gregory Orange wrote:
I've settled upon portupgrade as the best provider,
since I can use it to build from the NFS mounted /usr/ports tree. Now I
am experiencing a quirk when a package is to be newly installed:
'ensure => installed' or 'ensure =&g
On 28/06/12 13:51, Gregory Orange wrote:
I have /usr/ports mounted via NFS from the puppet server.
1. For more complicated packages, a config dialogue comes up (i.e. cd
/usr/ports/category/port; make config). How do I automatically configure
that, with settings to my choosing?
I suppose I could
t
book, so I'm ignoring it all for the moment and asking for opinions here.
TIA,
Greg.
--
Gregory Orange
System Administrator
CalorieKing Wellness Solutions Incorporated
http://www.calorieking.com/
--
You received this message because you are subscribed to the Google Groups "Puppet
Hi all,
We have two environments: production (containing one module) and
experimental (two modules, one the same name as the module in
production). All of our other modules are in the main module directory.
Agent runs complete fine in the production environment, but not when
switched to exper
On 14/08/13 13:29, Gregory Orange wrote:
We have two environments: production (containing one module) and
experimental (two modules, one the same name as the module in
production). All of our other modules are in the main module directory.
Agent runs complete fine in the production environment
On 19/04/14 03:05, Alexander Gray II wrote:
I wanted puppet to stop immediately on error so that I could manually go
through Augeas and sniff around, but since puppet does a million-and-one
things after the error, and it's unreproducible after puppet runs.
I sometimes want that behaviour, but h
On 12/06/14 02:55, Brian Mathis wrote:
Once you're
operating in a Windows world, your life will be far better by doing
things the "Windows Way" instead of resisting it.
Unless it yields a natural path toward Windows machines and services
proliferating despite you (perhaps) not wanting that. If
How do people manage users? I'm slowly marching toward LDAP (someone
recently suggested FreeIPA, not sure if it's relevant), but trying to
stave it off for the time being. I've read a few blogs and posts on the
topic, but nothing clear comes out - except that if one gets too
complicated, one sh
On 22/08/14 02:45, Garrett Honeycutt wrote:
Here[1] is the code that I use to manage local users. You could use it
for your scenario by placing users in different levels in Hiera and
keying off the profile.
Thanks, I'll give that idea a try and see if it works out any better for
this setup.
I've been trying to use the module_data module, but cannot get it to
bring in values. Is there a worked example somewhere, including site.pp
and hiera.yaml?
https://github.com/zipkid/puppet3-hiera_data_in_module hasn't helped - I
get the class defaults from init.pp, not the data from the yaml
Hi Fraser,
On 02/04/15 19:56, Fraser Goffin wrote:
Here's a simple example that works for me :-
--snip--
Wonderful, thank you. Using your work plus
https://github.com/zipkid/puppet3-hiera_data_in_module/tree/master/modules/test,
I've got it working. I _think_ my only problem was that I was u
Hi Patrick,
On 10/08/15 17:10, Patrick G. wrote:
parameters:
sudoroles: 'root_users'
sudoroles: 'dba_users'
That reads to me like you've overwritten the first sudoroles value with
the second entry. If you want both, it would need to be e.g. an array:
parameters:
sudoroles:
- 'ro
15 matches
Mail list logo
