This could work. I'll play with that to see what I can do.
Thanks for the replies!
Jason
On Fri, Jan 9, 2015 at 3:23 PM, Peter Bukowinski pmb...@gmail.com wrote:
On Jan 9, 2015, at 2:52 PM, Jason Price japr...@gmail.com wrote:
This doesn't make me happy, but fine. Major versions let you
This thread was very helpful and got me most of the way there. I started
with bare-bones legacy RHEL4 vms and had to add a couple steps to get
things working properly. Here's the complete procedure from start to finish:
*RHEL4 Client Installation:*
Set up some repos:
cd /etc/yum.repos.d
wget
Puppet version 3.7.3
Master and agent are running on Centos v7.0
When the manifest includes the following block, it fails with the error
below:
code block:
package {'s3cmd':
ensure = present,
provider = 'pip',
require = Package['python-pip']
}
(for reference, the
Hi,
I am having this issue:
*Error: Failed to parse template otrs/vhost-otrs.conf.erb:*
* Filepath:
/opt/puppet/lib/ruby/site_ruby/1.9.1/puppet/parser/templatewrapper.rb*
* Line: 81*
* Detail: Could not find value for 'serveraliases' at
You could likely use iteration in the future parser or recursion to build
up the string, but what sits in my mind as the path of least resistance is
inline templating (c.f.
https://docs.puppetlabs.com/references/latest/function.html#inlinetemplate).
I ran a quick test along these lines and it
Hi Martin,
I switched that to scoped variables. After that i am getting another issue.
*Here is .erb file:*
*# OTRS Config*
*# MaxRequestsPerChild (so no apache child will be to big!)*
*MaxRequestsPerChild 4000*
*VirtualHost *:%= scope.lookupvar(otrs::apache::port) %*
* ServerName %= @name
Testing for errors is part of the erb game. Comment all of that out and put
in just %= serveraliases -% just to see what is written to the file.
In your case above, it seems you have accounted for whether serveraliases
is an array or empty but not a simple string which is probably what it is.
Yknow, completely disregard the above answer :p
I was looking at stdlib and completely forgot about it before playing with
inline templating.
values and join in stdlib (https://github.com/puppetlabs/puppetlabs-stdlib)
do what is needed here. Much less code smell that way :p
On Fri, Jan 9, 2015
Seems to be an issue with unscoped variable inside the template.
https://docs.puppetlabs.com/guides/templating.html#referencing-variables
Please switch to scoped variables in your template:
# OTRS Config
# MaxRequestsPerChild (so no apache child will be to big!)
MaxRequestsPerChild 4000
On Mon, Jan 5, 2015 at 11:47 PM, Pushparaj BS pushparaj...@gmail.com
wrote:
Hi,
I have an XML file that has configuration for IIS Virtual settings for
many webservice Applications, and each application is a node in the XML.
Based on the XML, I have a Powershell script that can read the
Hi,
I am struggling with getting a LVM created and mounted before mysql is
installed on the volume.
Here my high level section:
node /test/ inherits resources {
###
##Create Percona Database Server
###
class { 'xxx::network::db': }
-
class { 'xxx::servercfg::dbvg':
On Jan 9, 2015, at 2:52 PM, Jason Price japr...@gmail.com wrote:
This doesn't make me happy, but fine. Major versions let you have breaking
changes.
My question is this: What do I replace it with?
My use case is as follows:
node default {
I'm seeing the same problem. $purge_inputs = true does not purge
anything in the inputs.conf file.
On Monday, October 27, 2014 at 3:59:52 PM UTC-7, Paul Krizak wrote:
Hi, all.
I'm having a hell of a time trying to figure out why the Puppet Labs'
Splunk module
I'm fooling around with some defined types and am struggling a little. The
following is just a small example of what I'm doing while I work it out:
#/etc/puppet/modules/testmodule/manifests/init.pp
define testmodule ( $message ){
testmodule::down { ${name}:
message = test message for
This doesn't make me happy, but fine. Major versions let you have breaking
changes.
My question is this: What do I replace it with?
My use case is as follows:
node default {
class{ 'ntp': }
class{ 'dns': }
class{ 'monitoring': }
class{
Clarification Request: NODE inheritance only, right ?
“Sometimes I think the surest sign that intelligent life exists elsewhere in the
universe is that none of it has tried to contact us.” (Bill Waterson: Calvin
Hobbes)
On Jan 09, 2015, at 02:52 PM, Jason Price japr...@gmail.com wrote:
Hi,
I am trying to figure out an API to add nodes to the puppet dashboard. Is
there a REST API on the puppet dashboard which lets me do so.
Thanks
Varun
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop
I've created a simple module to play with rspec-puppet, and I'm having
trouble getting my tests to pass because it appears I can't set the value
of $title -- It's always the name of my module.
I think perhaps I'm not understanding something about $title in puppet or
let( :title ) in
Hi,
Change filez from a class to a define (
https://docs.puppetlabs.com/learning/definedtypes.html).
Stephen
On 9 January 2015 at 23:08, Chris Galli gallil...@gmail.com wrote:
I've created a simple module to play with rspec-puppet, and I'm having
trouble getting my tests to pass because it
This thread was very helpful and got me most of the way there. I started
with bare-bones legacy RHEL4 vms and had to add a couple steps to get
things working properly. Here's the complete procedure from start to finish:
*RHEL4 Client Installation:*
Set up some repos:
cd /etc/yum.repos.d
wget
It seems you are using this as a way to classify nodes. Your best option is to
use an ENC (Foreman or Hiera) to classify your nodes, ideally using the roles
and profiles pattern to abstract your modules.
On Jan 9, 2015, at 1:52 PM, Jason Price japr...@gmail.com wrote:
This doesn't make me
I'm fooling around with some defined types and am struggling a little. The
following is just a small example of what I'm doing while I work it out:
#/etc/puppet/modules/testmodule/manifests/init.pp
define testmodule ( $message ){
testmodule::down { ${name}:
message = test message for
It's only drastic if you're worried about not having your machines' logs in the
same log file at the same time (because you log locally). 100 machines is as
good a time to start logging non-locally as any.
If anybody didn't want to get that drastic, they could always $rotateminute = 0
+
Hi,
with these options set, puppet itself tries to connect to the puppetmaster
through a proxy (which is not what i want). I still get errors like these:
err: /Stage[main]/Cmm_logstash/Apt::Source[logstash-forwarder]/Apt::Key[Add
key: D27D666CD88E42B4 from Apt::Source
Randomizing the time of logrotation as a workaround for this particular
issue seems drastic to me.
https://docs.puppetlabs.com/references/latest/configuration.html#splay
This may do the trick.
Cheers,
Felix
On 01/08/2015 08:27 PM, Christopher Wood wrote:
Yes it does, and that's something that
Hello,
given the following datastructure i want to create a resolv.conf file
dns:
nameservers:
'3': 10.200.1.230
'4': 10.200.1.231
...
search:
cust0: a41mgt.local all-for-one.local
cust1: A4T.local
..
for the nameserver
Hi
I'm trying to override a fact from facter 2.3, called partitions
with a custom version of this fact, via pluginsync.
The problem is that the base file in
/var/lib/puppet/lib/facter/partitions.rb, just like it's facter
brother in /usr/lib/ruby/vendor_ruby/facter/partitions.rb has a
require
27 matches
Mail list logo
