Thanks! That's interesting because the documentation consistently refers to
the first string following the type of a resource as the "title". Hence, my
confusion. I'll email the puppet folks and ask them just to put a note in
the docs to clarify this.
On Wednesday, May 29, 2013 5:09:50 PM UTC+8
Hi Vlad,
This is all more or less dictated by the auth.conf file, although the
implications can take a little while to chase down. You can see
http://docs.puppetlabs.com/guides/rest_auth_conf.html for the syntax of
this file and its general capabilities. The default rules in Puppet 3.x are
her
On 31 May 2013 01:02, przemol wrote:
> Hello,
>
> we have been using puppet 3 with hiera based config and several (usually
> "typical") environments:
> test
> predev
> dev
> preprod
> prod
> ...
> Basically we apply the puppet config to test, then predev, then dev, etc
> But within each environme
When packages for Ubuntu 13.04 Raring going to be released?
--
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 post to
Hey There!
I have been recently looking for SysAdmins with DevOps mindset for my
team and I usually receive lot of profiles from all across the world and
screening of the candidate profile is a tedious task. I prefer to give
candidates a real sysadmin challenge instead of theoretical linux qu
Hi,
I am trying to install gcc-4.7 on Ubuntu in puppet. Ubuntu comes with
gcc-4.6.3 as default. I have following puppet code:
apt::ppa {"ppa:ubuntu-toolchain-r/test":
}
package {["gcc-4.7", "g\+\+-4.7"]:
ensure => installed,
require => [Apt::Ppa["ppa:ubuntu-toolchain
Pretty much everything in puppet is secured with SSL certificates. If
someone has root access to one of your client machines, they have that
certificate. They can then retrieve anything that that node is allowed to
retrieve, which is generally specified in auth.conf. By default, I think
this in
Short Answer: You need to create a custom fact that would drive the decision to
create the new file resource.
I just went thru this issue and also performing an action based on whether or
not a package (RPM in my case) is installed.
Same answer to both.
For the existence of a file, you can do
Hi all,
I have experience using puppet, however I am new to setting puppet up as it
was already done for me in past environments. I am running into an issue
while trying to set puppet up for the first time on RHEL 6.4. I was hoping
y'all might be able to help me!
I get the following error fr
Hello,
I am trying to better understand the security impact a compromised host
managed by puppet could have on our infrastructure.
Suppose an attacker gained root on a machine called 'owned', and we have
this in site.pp:
node owned {
file {'foo':
content => 'puppet:///modules/modul
Hi,
I would like to run the File resource below:
file { 'autoconfig.php':
path=>
'/var/www/owncloud/config/autoconfig.php',
ensure => file,
owner => 'www-data',
group => 'www-data',
So right now we use environment to both control specialized parameters
related to different networks such as LDAP server, DNS servers, and other
things that are related to the environment variable. We also use unique
environment names to setup different instances of our application. For
example,
I don't think there's a wildcard match functionality for hiera like that.
If you interpolate the environment variable in you hierarchy, it will try
to match the result exactly.
On the other hand, if all of you "aw*" environments need the same data, I'm
inclined to ask what they're doing in diff
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Stan,
You could try setting refreshonly to 'true' in the exec, that way it
will only run when the /etc/fstab file it is subscribed to changes.
However, I don't know if this will work as you're only ensuring the
file is present.
http://docs.puppetl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Stan,
You could try setting refreshonly to 'true' in the exec, that way it
will only run when the /etc/fstab file it is subscribed to changes.
However, I don't know if this will work as you're only ensuring the
file is present.
http://docs.puppetl
I am not positive exactly what you are trying to accomplish, but I believe
you can do this in a couple of ways.
First, if puppet manages snmpd.conf and /etc/fstab simply set "refreshonly
=> true" on the exec and set those two file resources to notify the exec.
If puppet does not manage those fi
Really awesome.
On Tue, May 28, 2013 at 12:53 AM, Martijn wrote:
> That is very cool, Erik, and looks very useful.
>
> Thanks,
> Martijn
>
> Op maandag 27 mei 2013 20:44:19 UTC+2 schreef Erik Dalén het volgende:
>
>> I just released dalen-puppetdbquery 1.1.0, one cool new feature in this
>> rel
Hello
Here is my manifest for snmpd, my problem now is that my manifest will run
every time because my snmpd.conf file changes after the "exec"!! I want
that my manifest run when the snmpd.conf (only snmpd.conf source and not
with exec) file change or when my /etc/fstab file on the client chang
Fedora stock ships Puppet 2.7.18 and Ruby 1.9.3, which are not compatible.
I suggest adding yum.puppetlabs.com and upgrading to Puppet 3.
Either that or downgrade Ruby to 1.8.7.
This is a known issue with Puppet 2.7 and Ruby 1.9.3.
On Fri, Aug 17, 2012 at 6:51 AM, Peter Bukowinski wrote:
> Gr
This approach requires to keep all the users in *.pp files.
Currently we keep users in yaml file:
accounts::users::accounts:
sysadmin:
ensure: present
home: /home/sysadmin
managehome: "true"
shell: /bin/bash
uid: 4000
gid: sysadmin
comment: Systems Admin
etc
and creat
You can always use tags with virtual resources of some sort. Let's say
that user1 is in group app1, user2 and user3 are in group app2. You can
"tag" those user accounts with that:
user{'user1'
...
tag => 'app1',
}
user {['user2', 'user3']:
...
tag => '
- Original Message -
> From: "Mario Abajo"
> To: puppet-users@googlegroups.com
> Sent: Thursday, May 30, 2013 3:28:23 AM
> Subject: [Puppet Users] Stages and concat
>
> Hi!,
> I'm working on a module that's being called in a different stage than main,
> a previous one. THis modules is c
- Original Message -
> From: "Daniel Siechniewicz"
> To: puppet-users@googlegroups.com
> Sent: Thursday, May 30, 2013 5:54:39 AM
> Subject: [Puppet Users] Mcollective + ActiveMQ 5.8.0 - direct addressing
> problems
>
> Hi,
>
> I've decided to try the new shiny and installed ActiveMQ 5
Hello,
we have been using puppet 3 with hiera based config and several (usually
"typical") environments:
test
predev
dev
preprod
prod
...
Basically we apply the puppet config to test, then predev, then dev, etc
But within each environment we have quite a large number of hosts
(20/50/100/300/...)
Looking through some additional code that does similar things, I'm fairly
certain that the first method will work but I'm not sure if my follow on
suggestions will.
The 'package' and 'user' types use alternative providers but they do some
interesting things with manipulating the provider directly
Greetings,
Has this issue been fix yet? I have about 300 fedora/ubuntu boxes that has
this error when importing into dashboad.
Clayton
On Friday, August 17, 2012 7:51:06 AM UTC-6, pmbuko wrote:
> Greetings,
>
> I'm testing Fedora 17 in our environment and have come across an
> inter
Hi,
I've decided to try the new shiny and installed ActiveMQ 5.8.0 (my own rpm
for Centos 5). It seems that Mcollective (2.2.3 in this case) doesn't play
nice with ActiveMQ 5.8.0. It causes problems with direct addressing. In
fact, it mostly stops working, but occasionally, rarely, does "go thr
Hi!,
I'm working on a module that's being called in a different stage than main,
a previous one. THis modules is composed of various "defines" and use the
concat module inside. My question is ¿may i use concat different stages? i
was having cycle problems because of the class concat::setup.
Is t
This seems useful for Ocado-specific problems and/or those containing
sensitive information. Also for announcements as you've mentioned.
If it's a vanilla Puppet problem I'd advocate the official mailing list
instead, where many answers can be found and people beyond Ocado can learn
from your own
Looking at the 'host' provider from puppet, it looks like, to use a single
provider, you'll need to both confine it and to use the :operatingsystem
fact to create a case statement inside the provider.
So, yes, you can do what you want but not exactly in the most obvious
fashion.
Something like th
On Wednesday, May 29, 2013 10:29:22 AM UTC-5, Fabio Sangiovanni wrote:
>
> Hi everybody,
>
> I'm a new puppet user, and I have a question about defined types and
> relationships.
>
> I want a defined type to be part of a module.
> It manages optional configuration files, so the user can decide t
Thank you for your reply; let me share
Sentry is the server, lockbox is the client and scribe is activemq
iptables shut off on all, all sit in same vlan
Port up and listening with connection from server
[root@scribe activemq]# netstat -na | grep 61614
tcp0 0 :::61614
Hello Trevor,
Thanks for the reply. I did knew that I should use confine statement to
reach that goal but I did not know whether I did need a new provider for
each OS or if I can share it.
Sample:
File rar-windows.rb
Puppet::Type.type(:zipfile).provide(:rar, ...)
confine :operatingsystem => :
33 matches
Mail list logo
