I think the general consensus on multiple masters managing a node is
"don't do it".
I personally can't see a reason why this sort of thing is even necessary.
Why do you need two separate masters managing the same node?
What specific reason do you need to split the resource management
between two
Hi,
Over the last few days I've spent some time refactoring the puppetlabs-ntp
module to be a little bit more modern in style and not to be one giant
class. As a result I've released a release candidate and I wanted to give
users of the module a headsup to take a look at the differences and
possib
I'm trying to do the same thing and running into two minor problems.. I
would like to rename the puppet command
to something like puppet3. We're running two versions for two separate
teams for 2.7 and 3.x However, when I try to do a symlink I get the
following error.
I've found a hack to forbid File resources with source attribute to be
applied before all ifup's:
Exec["ifup $iface"] -> File <| source != [] |>
Unfortunatelly, it's undefined undocumented behavior, so the problem is
still here.
--
You received this message because you are subscribed to the G
I need to collect all File resources with defined source attribute.
I've try to use
File <| source != undef |>
but it's collect even
file {$file:
ensure => file,
force => true,
group => $group,
mode => $mode,
owner => $owner,
}
Why? And how can I collect only files with defined source attribut
On Monday, July 8, 2013 11:02:25 AM UTC-5, Ashley Penney wrote:
>
>
> This is definitely something we want to do and need to do. I've been a
> little hesitant to wade down into the whole "these are the specific
> parameter names we want to use" and building out a huge set of guidelines,
> but
Unfortunatelly, stages is absolutely useless because of strict limitations
(notify between stages, only classes), and I can't use one script because
of ifup|ifdown commands and interfaces file is in different modules.
I have a defined type with ifup/ifdown commands for specified interface.
Some
On Tuesday, July 9, 2013 3:12:20 AM UTC-5, Igor Galić wrote:
>
>
> Hi folks,
>
> last week I asked a question on how to sensibly structure
> a puppet setup:
>
> https://ask.puppetlabs.com/question/1932/how-to-tier-a-puppet-setup/
>
> I received a quite sensible request, even though it's not
We are looking to implement a code review system that will require a review
of the code before it gets to production servers. I have been looking into
many different options, and would love some feedback and experiences from
other users.
Our puppet is in a git repo. We have 3 primary enviro
I had to install the puppet stdlib module with:
*puppet module install puppetlabs/stdlib*
and that fixed the issue. It wasn't available in my /etc/puppet/modules.
I'm not sure if its *supposed* to be installed by default. I'm running
puppet 3.x and had upgraded from 2.7.
On Monday, January
On Monday, July 8, 2013 2:56:07 PM UTC-5, Wil Cooley wrote:
>
> I have a case where I need to somehow access a variable in a defined
> type, which is built from the parameters of the defined type (and
> possibly other sources). As far as I can tell, doing this directly is
> not possible, nor h
at the risk of replying to myself, here's an example from another host -
runs now take ~2.5 times as long to complete.
Jul 8 20:22:24 testhost puppet-agent[14221]: Finished catalog run in 4.93
seconds
Jul 8 20:32:25 testhost puppet-agent[14221]: Finished catalog run in 4.72
seconds
Jul 8 20
Hi,
i've just upgraded my infrastructure to 3.2.1 - had the puppet master (via
mod_passenger) running on 3.2.1 and after a month of stability, upgraded
the clients from 2.7.18
I noticed this across the board - the runtime on the client side has
increased by approx 50% immediately following the
Hi,
Am Mittwoch, 3. Oktober 2012 19:00:15 UTC+2 schrieb Juan José Presa Rodal:
> Ok, I was missing the following line in the nginx location statement:
>
> uwsgi_modifier1 7;
>
>
> Now seems that works correctly (and very fast). When thoroughly adjusted I
> will publish the complete configuration
On Monday, July 8, 2013 11:45:14 AM UTC-5, Alejo Granero wrote:
>
> Hi! when I try to link de node with de master I do that:
>
> $ puppet agent --server ipofthemaster --waitforcert 60 --test
>
> Then I have thats errors:
>
> err: Could not retrieve catalog from remote server: Connection refused -
Putting them in a separate stage is also a possibility.
On 9 July 2013 15:34, David Schmitt wrote:
> On 09.07.2013 14:01, Nevorotin Vadim wrote:
>
>> I need to apply three resources one immediatelly after another. It's a
>> ifdown/ifup commands, and command to generate /etc/network/interfaces
>
On Tue, Jul 9, 2013 at 2:21 AM, Josh Cooper wrote:
>
>>
>>
>
> You have multiple versions of facter installed. This typically happens
> when facter gets installed both as a gem and via your package manager.
>
>
Josh,
Thanks for the reply.
I suspected as much and went through the system in ques
>
> $ puppet agent --server ipofthemaster --waitforcert 60 --test
You must have hostnames for puppet. The SSL certificates are valid for some
certain cn, which corresponds to hostname. The ip address doesn't match
hostname, so SSL refuses the connection. Set up DNS or hosts files.
Cheers,
Pau
On 09.07.2013 14:01, Nevorotin Vadim wrote:
I need to apply three resources one immediatelly after another. It's a
ifdown/ifup commands, and command to generate /etc/network/interfaces
file. I need to do ifdown, then rebuild interfaces, then ifup. I try to
add simple relationship, but in this cas
I need to apply three resources one immediatelly after another. It's a
ifdown/ifup commands, and command to generate /etc/network/interfaces file.
I need to do ifdown, then rebuild interfaces, then ifup. I try to add
simple relationship, but in this case some File resources are trying to be
app
Given that
https://github.com/stdmod/puppet-modules/blob/master/Parameters_List.md is
based on the same resource_argument pattern can we make a step further and
define names that can be used for any module and call them "suggested
standards"?
Restricting the discussion to PuppetLabs modules only is
On 08.07.2013 20:06, Nan Liu wrote:
This is definitely something we want to do and need to do. I've
been a little hesitant to wade down into the whole "these are the
specific parameter names we want to use" and building out a huge set
of guidelines, but I do have a straightforwar
Hi folks,
last week I asked a question on how to sensibly structure
a puppet setup:
https://ask.puppetlabs.com/question/1932/how-to-tier-a-puppet-setup/
I received a quite sensible request, even though it's not
what I wanted to hear. The reason it's not, might be because
I haven't been quite
23 matches
Mail list logo
