Best practice assigning ip addresses to containers (that can have multiple instances)

[Marc Roos]

Yes thanks, had to even set it to get unique ip addresses on the 
containers. Without it, some containers were getting the same ip 
address. Using the vendorid to classify tasks.



-----Original Message-----
From: Bruce Hudson [mailto:Bruce.Hudson at dal.ca] 
Sent: zondag 11 augustus 2019 21:59
To: Marc Roos
Subject: Re: Best practice assigning ip addresses to containers (that 
can have multiple instances)

    I think you misunderstand the role of the dhcp-client-identifier. It 
is meant to be a UNIQUE key to identify a client in cases where you 
cannot use the ethernet address; perhaps simply so you can rebuild a 
system quickly on new hardware. You cannot have multiple clients with 
the same identifier as the server will treat them as a single client, 
re-assigning the same IP to all. 

    The best way to do what you want is probably classes. I suppose you 
can have multiple, unique identifiers for your LDAP servers and then 
assign the class membership based on a common prefex. Alternatively, you 
could just use the ethernet addresses. Once you have a class, you simply 
set up a pool with an "allow LDAP-SERVERS" restriction.
-- 
Bruce A. Hudson				| Bruce.Hudson at Dal.CA
ITS, Networks and Systems		|
Dalhousie University			|
Halifax, Nova Scotia, Canada		| (902) 494-3405