, andreash wrote:
Hi,
thanks for your input. I had already thought about that, but initially
wanted to be able to set the ip addresses using puppet. Or is that a
bad idea?
Hi, you should probably use DHCP static leases, but in situations where
you can't, it is possible to create a define
Hi,
naturally, there are many places in a typical puppet manifest where
one needs to use IP addresses:
* network config
* Listen directives in server daemons
* hosts file
* ...
I was wondering if there is some 'best practice' way of specifying the
IP addresses of all the hosts in one place and
it in your puppet classes,
templates ...)
Benoit
Le 22/05/2010 11:08, andreash a écrit :
Hi,
naturally, there are many places in a typical puppet manifest where
one needs to use IP addresses:
* network config
* Listen directives in server daemons
* hosts file
* ...
I
hi there,
i'm not sure as to how to call the subject of this post, as i'm
totally new to puppet -- so please forgive me if this is
misleading ...
for my servers, i'm planning to do something like this (pseudo-code):
class (?) base-config:
include ntp::client
include resolver
...
