We understand that all site specific data should be in Hiera. We also
understand that modules shouldn't have to be modified when they are well
designed e.g. the puppetlabs/apache module. However, how do I setup apache
using this module with a virtual host without putting data into the
manifest.
Hi,
You can create another abstration level and put all your specific
logic inside. Have a look to the roles & profiles literature on the
Internet.
For example create a apache profile (eg: webserver.pp) with the following:
include apache
create_resources(apache::my_vhosts,hiera_hash('apache::my_
You could setup setup the host-specific yaml as:
vhost:“first.example.com”
port: “80”
priority:“10”
docroot:“/var/www/first”
Then your module:
$vhost = hiera(‘vhost’)
$port = hiera(‘port’)
$priority = hiera(‘priority’)
$docroot: = hiera(‘docroot’)
apache
That makes perfect sense and achieves exactly what we need. Thank you!
On Monday, August 25, 2014 11:34:06 AM UTC+2, Juan Sierra Pons wrote:
>
> Hi,
>
> You can create another abstration level and put all your specific
> logic inside. Have a look to the roles & profiles literature on the
> Inte
On Thursday, August 21, 2014 12:30:05 PM UTC-5, Wil Cooley wrote:
>
>
> On Aug 21, 2014 5:53 AM, "jcbollinger" > wrote:
>
> > No new parameter, but you could also repackage your RPM so that it
> handles the permissions of /tmp itself.
>
> I suspect that would conflict with the package that alre
On Saturday, August 23, 2014 12:46:59 PM UTC-5, Matt W wrote:
>
> Will,
> Thanks for the response. I know its a bit of a unique model -- but when
> you think about it, it makes a decent amount of sense. We run hundreds of
> nodes that are fundamentally similar
>
And therein is one of the ke
On Friday, August 22, 2014 3:36:33 PM UTC-5, Nan Liu wrote:
>
> On Fri, Aug 22, 2014 at 12:10 PM, Nathan Brito > wrote:
>
>> I'm trying to apply settings on a Cisco Catalyst 2960S through the
>> puppet, but I can not.
>>
>> When I give the "device #puppet verbose" command, the puppet does not
On Friday, August 22, 2014 9:38:20 AM UTC-5, Matt W wrote:
>
> Even with the caching disabled, I think we ran into this again. Can one of
> the puppet-devs chime in here and let me know what might be going on?
>
>
I am not among the Puppet developers, but I think I already touched on the
likel
Hello all,
I'm trying to solve an issue with Puppet and I'm hoping you can help guide
me. We have an internal YUM repository that we build/deploy to quite
frequently, and several of the artifacts we publish to that repository need
to be pushed out (via puppet) to servers a couple of times per
sorry, I posted missing content.
I had already specified node.
Follow the correct manifest:
node switch.mydomain {
>interface {
> "GigabitEthernet1/0/1":
>description => "teste",
>}
> }
yet the problem continues.
Em sexta-feira, 22 de agosto de 2014 17h36min33s UTC-3, N
Use the zypprepo module to managing your zypper repositories.
https://forge.puppetlabs.com/darin/zypprepo
puppet module install darin-zypprepo
--
Later,
Darin
On Mon, Aug 25, 2014 at 10:35 AM, randal cobb wrote:
> Hello all,
>
> I'm trying to solve an issue with Puppet and I'm hoping you can h
Its tricky because we use an ELB in front of the puppet masters, and we
know that the calls to the /node/ REST API are coming from the
ELB, but because of the way we have the ELB configured (pure TCP
passthrough), we don't get the extra headers like the x_forwarded_for
header. This makes it hard to
Hi,
I'm studying the custom facts examples and I noticed that facts tend to be
scalars. (Perl speak)
Are they ever arrays? For instance I want to write a custom fact that
parses the /etc/fstab and returns the mounted file systems as a fact to
allow amanda to be automagically configured to back u
Thanks for the very quick reply! I'll give that a shot.
On Monday, August 25, 2014 11:37:26 AM UTC-4, Darin Perusich wrote:
>
> Use the zypprepo module to managing your zypper repositories.
>
> https://forge.puppetlabs.com/darin/zypprepo
>
> puppet module install darin-zypprepo
> --
> Later,
Comments inline
Matt Wise
Sr. Systems Architect
Nextdoor.com
On Mon, Aug 25, 2014 at 6:55 AM, jcbollinger
wrote:
>
>
> On Saturday, August 23, 2014 12:46:59 PM UTC-5, Matt W wrote:
>>
>> Will,
>> Thanks for the response. I know its a bit of a unique model -- but when
>> you think about it, i
On Mon, Aug 25, 2014 at 12:01:03PM -0400, Peter Berghold wrote:
>Hi,
>I'm studying the custom facts examples and I noticed that facts tend to be
>scalars. (Perl speak)
>Are they ever arrays? For instance I want to write a custom fact that
>parses the /etc/fstab and returns th
Trey,
The '>= 1.0.0' is referring to the libaugeas version, and it's based on the
`augeasversion` fact. You'll need to have augeas installed on the node
you're trying to include tomcat on.
Morgan
On Sun, Aug 24, 2014 at 12:38 PM, Trey Duskin wrote:
> Hi all,
>
> I'm trying to get a module to
Facter.add(:mounted_fs) do
setcode do
i=0
mountedfs = []
f=open("|egrep 'ext|reiser' /etc/fstab")
x=f.read
f.close
x.split(/[\n]+/).each do |line|
fields=line.split(/[\s\n
Well good, because it's now my second. ;)
Are you running facter -p, to pull in puppet-specific facts?
https://docs.puppetlabs.com/facter/latest/core_facts.html#summary
Have you seen pluginsync pull this fact to the agent node (look in syslog,
/var/log/messages on redhat derivatives)?
https://
On 08/14/2014 07:24 PM, Matt Wise wrote:
>
> 1. What is the purpose of calling the Node API? Is the agent doing
> this? Why?
That's a good one. Does your log not indicating where those calls originate?
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" g
On 08/24/2014 08:04 AM, Mickaël Canévet wrote:
> Hello,
>
> I'd like to know if there is a way to monkey patch a puppet type for
> example to add an auto requirement:
>
> https://github.com/puppetlabs/puppetlabs-firewall/pull/380/files
>
> Thanks,
> Mickaël
Well, you can always maintain your perso
The log shows the remote connecting IP -- but the IP is the ELB in front of
our puppet servers. Unfortunately because we're doing pure TCP-passthrough,
ELB logging itself is not useful either in this case. :/
Matt Wise
Sr. Systems Architect
Nextdoor.com
On Mon, Aug 25, 2014 at 2:08 PM, Felix Fra
Hi,
yes, you will need exported resources, and it won't be an easy design at
all.
I imagine it would work roughly like this (assuming Agent 1 runs
central_server and Agents 2 and 3 run slave_server instances).
Sketch of the manifest for the central server:
class central_server {
concat { '/
On 08/25/2014 11:17 PM, Matt Wise wrote:
> The log shows the remote connecting IP -- but the IP is the ELB in
> front of our puppet servers. Unfortunately because we're doing pure
> TCP-passthrough, ELB logging itself is not useful either in this case. :/
Uhm I see. Bummer.
Is that a Linux box? Co
On 08/22/2014 05:52 AM, Ed Lima wrote:
> /
> /
> I can get to port 443 on the master fine from the node:
>
Well, that's nice and all, but are you aware that Puppet uses port 8140
by default?
Are you using Passenger? Please check your Apache configuration then.
If you are not using Passenger, the
On 08/21/2014 12:53 AM, Frans Thamura wrote:
> hi all
>
> anyone have an example that run puppet script in 3 enviroment,
>
> 1. puppet vagrant
> 2. puppet apply
> 3. puppet master
>
> can share?
>
> thx
>
> F -> still stack test my own in that environment
Hi,
a manifest that is fit for the master
On 08/20/2014 11:23 PM, Frans Thamura wrote:
> I try the
>
> puppet apply --modulepath=/vagrant/data/puppet/modules
I think Yanis just misread your original invocation, which was fine.
The error message is quite obvious: The file
/vagrant/puppet/modules/tomcat/templates/tomcat-users.xml.erb does n
On 08/21/2014 04:25 PM, kaustubh chaudhari wrote:
>
> I want puppet agent to send this file or the output of the command #
> cat /etc/issue to the master?
>
> Is this possible, if yes can some one suggest or redirect me to some
> docs that i can refer too.
That requirement is practically the verba
On 08/18/2014 08:33 PM, jlittle wrote:
>
> I have two remote locations and my puppetmaster is behind a firewall
> and I want to allow access to it through stunnel so I tunneled the
> port to a client machine and aliased the puppetmasters name to
> localhost. I can connect to the puppetmaster and m
On 08/15/2014 09:34 PM, Mark Gardner wrote:
> I'm upgrading puppet from 3.3.1 to 3.6.2 on Suse Linux Enterprise 11 SP3
>
> The puppet service wont start with this error collected error from
> /var/log/puppet/puppet.conf
> Fri Aug 15 13:12:35 -0500 2014 Puppet (err): Could not parse
> application op
Hi,
We have been using Puppet Enterprise for a while now and we are very
interested on testing RabbitMQ as our solution for an application we are
testing. I have developed a demo using the Puppetlabs RabbitMQ Puppet
Module but it seems that i am stuck with the configuration.
https://gith
Facter 2.2.0 is a backward-compatible features-and-fixes release in the
Facter 2 series. The release adds structured versions of several core fact
types and contains backports of facts that were merged into Facter master
but were not released in Facter 2.0.1.
Headline features
- new structured f
Le lundi 25 août 2014 23:14:11 UTC+2, Felix.Frank a écrit :
>
> On 08/24/2014 08:04 AM, Mickaël Canévet wrote:
> > Hello,
> >
> > I'd like to know if there is a way to monkey patch a puppet type for
> > example to add an auto requirement:
> >
> > https://github.com/puppetlabs/puppetlabs-fir
33 matches
Mail list logo
