On Wednesday, January 29, 2014 3:41:43 PM UTC+1, jcbollinger wrote:
>
>
> I'm uncertain what you mean. If "doing this" refers to enumerating the
> cluster members in advance, then that can only be something that you, as
> cluster planner, do yourself, outside the scope of Puppet (c.f. "in
> a
On Friday, January 31, 2014 11:27:49 AM UTC+1, Daniele Sluijters wrote:
>
> Facts get sent at the start to the Puppet master so bringing an interface
> online during a Puppet run won't make it available as a Fact during that
> run, only on the next run as then the Facts are collected again. You
Hello,
I run puppet with foreman, and want to do the following:
- Initalize a network interface
- Start a service, bound to that interface.
eg:
#Start an interface for vlan 301 on interface em1
network::if::dynamic { 'em1.301':
ensure => up,
}
#Start an openstack L2 agent
cl
On Tuesday, January 28, 2014 10:11:58 PM UTC+1, jcbollinger wrote:
>
>
>
> Not any good ways. In any case, that idea doesn't look like a good fit
> for the module in question. A quick examination leads me to believe that
> it will set up the cluster only once (on each node that has the
> pac
Hello,
I am using the Radez/Paxemaker modules, and this allows me to define a
cluster like this:
class {'pacemaker::corosync':
cluster_name => $control_clu_name,
cluster_members => $control_clu_members,
require => [ Package['ccs'],
}
I currently define the cluster name
On Friday, January 24, 2014 12:51:07 PM UTC+1, LoreLLo wrote:
>
> >Basically my situation is the following:
> >- A database server
> >- Several web application servers.
>
> We have a similar environment and the solution we adopted is very simple: put
> the "if ! defined" inside the exported res
On Thursday, January 23, 2014 7:25:47 PM UTC+1, Xav Paice wrote:
>
>
> We have something quite similar - as we use hiera extensively we managed
> to have a common yaml file with a list of databases in a hash, and used
> create_resources to create the databases (and users, and haproxy
> liste
On Thursday, January 23, 2014 2:59:29 PM UTC+1, jcbollinger wrote:
>
>
> It only makes sense to export resources that are somehow specific to or
> characteristic of the node whose catalog is being compiled. If you have
> such a resource to export, then structure your manifests so that no more
Hello,
I have a need for an exported resource that only gets exported once. So a
class that exports this resource should test first if it hasn't already
been exported, and only then export it.
In pseudo code:
if
!exists X
then
@@X
The problem is that I can't seem to find out how to tes
On Thursday, January 9, 2014 6:20:08 PM UTC+1, jcbollinger wrote:
>
>
>
>
> The error message says that the problem is two distinct declarations of a
> resource "Swift::Ringsync[account]". The most likely cause is that you are
> both collecting that resource and declaring it locally for the sa
Hello all,
I am configuring a openstack swift cluster using puppet. For this I use
exported resources, and here I run in to a problem...
I'm getting an error like this:
Error: Could not retrieve catalog from remote server: Error 400 on SERVER:
Another local or imported resource exists with th
11 matches
Mail list logo
