LDAP structure to share config for more than one site

[Márcio Merlone]

On 02-12-2014 12:14, Brendan Kearney wrote:
> On Mon, 2014-12-01 at 11:57 -0200, Márcio Merlone wrote:
>> What I want in short:
>> - Shared among all servers: known-hosts, classes and subclasses
>> - Specific for each server: shared networks, subnets, pools and
>> ranges.
> i make no guarantees that the ldif will work for you.  see attached.
Hi Brendan, thank you very much for your time!

As I understood from your ldif you have a fail-over for the same site 
and subnet, while I want to have a bunch of independent, spread servers 
each with its own config, subnets and pools, while sharing classes, 
subclasses and hosts, something like this:

+--------------------+     +-----------------+ +--------------------+
|Main Office         |     |Shared for all   |     |Branch Office 1     |
|                    |     |                 | |                    |
|dhcpServer 1        +---> |dhcpClass'es     | <---+dhcpServer 2        |
|dhcpSharedNetwork 1 |     |dhcpSubClass'es  | |dhcpSharedNetwork 2 |
|dhcpSubnet 1        |     |known-hosts      | |dhcpSubnet 2        |
|dhcpPool 1          |     |                 | |dhcpPool 2          |
+--------------------+     +-----------------+ +--------------------+

I am playing with LDAP structure, but could not yet find how to sew the 
branches in a way it works like that, but in general, even using 
dhcpXxxxxDN on almost all objects I cannot get dhcpd to either know 
about classes and subclasses or about subnets and pools, with errors 
like this:

No subnet declaration for eth0 (10.1.1.1).
or
LDAP line 22: no such class: clsDesktop

Any idea?

Regards,

-- 
*Marcio Merlone*