Hey,
While installing servers in new datacenter I failed to install puppet from
the apt repo.
When curl to the server I got stalled:
root@mgmt01:~# curl http://apt.puppetlabs.com -v
* About to connect() to apt.puppetlabs.com port 80 (#0)
* Trying 198.58.114.168... connected
> GET / HTTP/1.1
> U
Hi,
I've got the following code that works as expected:
class { "c1": }
class { "c2": }
class c1 {
notice "+++"
}
class c2 {
require "c1"
notice "+++"
}
But switching the declaration order of class c1 and c2:
class { "c2": }
class { "c1": }
class c1 {
notice "+++"
}
class c2 {
req
On Monday, March 31, 2014 3:55:03 PM UTC-5, Henrik Lindberg wrote:
>
> Going forward, I think the Puppet Language should handle the situation
> where more than one resource definition / class definition is made and
> where the two are considered compatible (they describe the "same
> state"). W
Hello.
I wantaed to ask, if is a better way to change user groups then this:
exec {"process $usr":
command =>"chgrp . $newGroup",
path=>[ "/bin/", "/sbin/" , "/usr/bin/", "/usr/sbin/" ]
}
I need to make the user move and he was only in the new group
Hello there,
i'll pass the ppt-202 exam (Puppet for sysadmins) next week.
I love the product but unfortunatly i have no profesionnal experience at
Puppet, so passing the certification is a good way for staying up to date
and practising the product.
I was wondering if having a real experience on c
On Monday, March 31, 2014 1:08:25 PM UTC-5, Dan Bode wrote:
>
>
> That being said, there are two reasons it may be problematic.
>
> 1. Behavior depends on parse order - this is probably the best reason not
> to use it.
>
And that is indeed an excellent reason not to use it.
> The behavior
Hi All,
I'm trying to use puppet to manage some application servers. I'm having an
issue that I can't seem to figure out. Binary files that I copy to the
Windows host are incomplete, and if I run puppet agent -t several times the
file usually comes through. I'm testing this with single file
Sounds like a local configuration issue, not a Puppet problem.
On Tue, Apr 1, 2014 at 4:11 AM, Shahar Mintz wrote:
> Hey,
> While installing servers in new datacenter I failed to install puppet from
> the apt repo.
>
> When curl to the server I got stalled:
> root@mgmt01:~# curl http://apt.puppet
Hi folks,
In my common.yaml file I have the following hiera hashes:
system::packages:
sshd:
ensure: 'present'
...
...
more stuff here
...
system::packages:
ntpd:
ensure: 'present'
I naively assumed that Hiera would merge those 2 hashes together, just as
it does if the
Hi,
long story short: This is what the hiera_hash() function is for (as
opposed to hiera()).
HTH,
Felix
On 04/01/2014 06:15 PM, Matthew Burgess wrote:
> Hi folks,
>
> In my common.yaml file I have the following hiera hashes:
>
> system::packages:
> sshd:
> ensure: 'present'
> .
Thanks Felix.
I'm using the system module (https://forge.puppetlabs.com/erwbgy/system)
and the system::packages module *is* using hiera_hash() (
https://github.com/erwbgy/puppet-system/blob/master/manifests/packages.pp)
(as is system::services which is also causing me the same problem).
I assume
Hi,
Did you configure a filebucket?
filebucket { 'main':
server => 'fqdn_server',
path => false,
}
Dominique Arpin
Tél. Interne: 140-4156
Tél. 514 285.2929 Poste: 140-4156
De : puppet-users@googlegroups.com [mailto:puppet-users@googlegroups.com] De la
part de Nick Miller
Envoyé : 1 avri
Apologies for that last email; hiera_hash() is obviously doing *nearly* the
right thing, as it *does* merge hashes across different levels of the
hierarchy. It *doesn't* seem to be merging hashes within the same level of
the hierarchy.
Thanks,
Matt.
On 1 April 2014 17:35, Matthew Burgess wrot
Hmm, so you have the same key multiple times in one yaml file? Why?
On 04/01/2014 06:51 PM, Matthew Burgess wrote:
> Apologies for that last email; hiera_hash() is obviously doing *nearly*
> the right thing, as it *does* merge hashes across different levels of
> the hierarchy. It *doesn't* seem t
I suspect duplicate keys are not valid YAML.
R.
On 1 Apr 2014 17:51, "Matthew Burgess" wrote:
> Apologies for that last email; hiera_hash() is obviously doing *nearly*
> the right thing, as it *does* merge hashes across different levels of the
> hierarchy. It *doesn't* seem to be merging hashes
Like I said, it was purely for cosmetic/aesthetic purposes; I wanted to
write the YAML file in the same order as things were defined in our design
document so that it was easier to review that the implementation matched
the design. Section 1 of that doc might cover something like NTP
configuraiton
No, I'm just using the 'files' directory within the module. What would the
filebucket be used for in this situation?
On Tuesday, April 1, 2014 12:47:45 PM UTC-4, Arpin Dominique (Nter) wrote:
>
> Hi,
>
>
>
> Did you configure a filebucket?
>
>
>
> filebucket { 'main':
>
> server => 'fqdn
Sorry, brain-fart. Yes, I do have the filebucked configured, and it
appears to be correct.
On Tuesday, April 1, 2014 1:23:24 PM UTC-4, Nick Miller wrote:
>
> No, I'm just using the 'files' directory within the module. What would
> the filebucket be used for in this situation?
>
> On Tuesday,
Hello all, thanx in advance for listening to my sniffles as I am failing
at solving this problem.
I have CloudFormation template that builds out some servers. I have
parameterized a few values like. DatabseName DataBaseUser DataBaseLocation
and some others. The problem I seem to be faced
Hiera allows multiple backends, YAML being one and also being the one
with which most people start, some of which can be non-static. If you
Google for Craig Dunn's blog you'll see an example where he uses a
backend which enables Hiera data retrieval from a CouchDB backend.
That particular example i
> variables. In the case of AWS/EC2 facts this is done, if memory
> serves, via a Type and Provider that queries the 169.x node metadata
> service embedded in AWS/EC2.
Sorry, perils of multitasking... s/Type and Provider that/series of
custom facts which/g.
--
You received this message because y
Hiera is really great, but if you have to configure diferent parameters per
host the yaml backend could be a nightmare..
Note that i talk about the backend, you can switch it to a nosql database
( couchdb, redis) or sql( mysql) or ldap ...
Regards,
El 01/04/2014 22:26, escribió:
> Hello all,
http://puppetlabs.com/services/certification has a pretty solid list
of pre-cert study materials but, yes, the more hands-on experience you
have with Puppet/PE the better.
Of the self-study resources mentioned there, I highly recommend:
1) The Puppet Certification Practice Test
2) The Puppet Lear
I've actually figured this out. The problem was caused by mis-configured
DNS settings on the puppet master server. Once fixed, I haven't been able
to reproduce the problem.
On Tuesday, April 1, 2014 1:29:43 PM UTC-4, Nick Miller wrote:
>
> Sorry, brain-fart. Yes, I do have the filebucked conf
On 2014-01-04 15:22, jcbollinger wrote:
On Monday, March 31, 2014 3:55:03 PM UTC-5, Henrik Lindberg wrote:
Going forward, I think the Puppet Language should handle the situation
where more than one resource definition / class definition is made and
where the two are considered comp
thank you,
I found both your replies very useful.
On Saturday, March 29, 2014 1:48:26 PM UTC, Vishwa Kumba wrote:
>
> I was wondering if there is a way to define ordering between 2
> create_resources in puppet manifests.
>
> For example:
>
> create_resources('php::install', $php_packages) ->
I've been switching my modules from rspec-system to beaker-rspec and am
having some issues running any tests using the centos-510-x64 and
centos-59-x64 puppetlabs vagrant boxes. Every test fails to install
ntpdate due to "Temporary failure in name resolution". I do not have this
issue with th
This MAY be a bug with serverspec or specinfra gems, but I was hoping
someone here could help me identify the problem. I wrote some tests that
ensure file resources are removed and yumrepo resources are disabled. I
was using older beaker gem and recently updated to latest 1.9.1 to find
that m
Released April 1, 2014. (RC1: February 28; RC2: March 12; RC3: March 25; RC4:
March 28.)
Facter 2.0.1 is the first release in the Facter 2 series.
Headline Features
- Fact values can now be arbitrarily complex data structures instead of simple
strings.
- There's a new API for adding facts, whi
Hi all,
I am trying to work out the best way to solve something that does not get
configured correctly with puppetlabs-apache.
using puppetlabs-apache and WSGI defaults, it places the wsgi socket into
the default location according to:
http://code.google.com/p/modwsgi/wiki/ConfigurationDirecti
30 matches
Mail list logo