On 01/21/2014 07:41 AM, Dirk Heinrichs wrote:
> Opposed to what Felix is thinking, my previous message was meant
I thought so, but have issues with the notion that /etc/hosts is to be
ignored in favor of DNS in any production environment.
> seriously. I don't see a trivial solution to your proble
The fundamental problem is that such information is only going to be
accurate to the last
Puppet run, it's not realtime. Hence the need for some sort of
external orchestration (which
you'd get for free with DNS/DHCP data). Other options are of course available.
On 21 January 2014 07:25, Jose Luis
Am 21.01.2014 08:25, schrieb Jose Luis Ledesma:
> I think this could be accomplished with exported resources, on every node
> export a file with his IP, and collect the other ones. Then with a custom
> script you could verify if the entry is on the hosts file.
But still, how do you cope with n
In fact, I think that is easier, with host exported resources.
See:https://groups.google.com/forum/m/#!topic/puppet-users/uAxbiIYH6Q4
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from
I think this could be accomplished with exported resources, on every node
export a file with his IP, and collect the other ones. Then with a custom
script you could verify if the entry is on the hosts file.
About the offtopic dhcp vs hosts file, most clusters like to have the ips
defined on t
well in the end i would have to add dns healthchecks too to the node
spawning. The puppet /etc/hosts approach just looked nice and easy.
I am on Amazon AWS, but i should be able to to it with nagios and some
scripts
On Tue, Jan 21, 2014 at 2:41 PM, Dirk Heinrichs wrote:
> Am 21.01.2014 03:37,
Am 21.01.2014 03:37, schrieb Peter Romfeld:
> I have a cluster where all nodes must use hostnames, so we use
> /etc/hosts. I want to configure autoscaling for this cluster, but my
> biggest problem is the hosts file, so when a new node comes up all
> other nodes need to be notify that the hosts fi
yes.
I have a cluster where all nodes must use hostnames, so we use /etc/hosts.
I want to configure autoscaling for this cluster, but my biggest problem is
the hosts file, so when a new node comes up all other nodes need to be
notify that the hosts file changed, so the make pull the new file.
Tha
Hi,
On 01/20/2014 07:57 AM, Dirk Heinrichs wrote:
>> I am using the puppet example42/hosts module to have a dynamic
>> /etc/hosts file.
>> Its working fine so far but i have one more requirement, i need to
>> force update on all other nodes if one node changes or get added.
>
> This is what it is
Am 20.01.2014 07:52, schrieb Peter Romfeld:
> I am using the puppet example42/hosts module to have a dynamic
> /etc/hosts file.
> Its working fine so far but i have one more requirement, i need to
> force update on all other nodes if one node changes or get added.
This is what it is: an example.
Hi,
I just started learning puppet, and still have problems understanding the
advanced puppet language.
I am using the puppet example42/hosts module to have a dynamic /etc/hosts
file.
Its working fine so far but i have one more requirement, i need to force
update on all other nodes if one node ch
11 matches
Mail list logo
