Need an LDIF schema and group structure for hosts. In addition to organizing users, LDAP should categorize sites, hosts, and critical components.
An example structure should be cn=hdd1,ou=core,ou=msn0,ou=Hosts,dc=aninix,dc=net. This describes a hard drive inside the core.msn0.aninix.net chassis, which lives in the first datacenter erected in range of the Madison, WI (MSN) airport.
The schema should set address as the description on the site group, serial or MAC address as the description on the component entity, and chassis serial, function, and pipeline (dev, prd, etc.) on the host group.
Need an LDIF schema and group structure for hosts. In addition to organizing users, LDAP should categorize sites, hosts, and critical components.
An example structure should be `cn=hdd1,ou=core,ou=msn0,ou=Hosts,dc=aninix,dc=net`. This describes a hard drive inside the core.msn0.aninix.net chassis, which lives in the first datacenter erected in range of the Madison, WI (MSN) airport.
The schema should set address as the description on the site group, serial or MAC address as the description on the component entity, and chassis serial, function, and pipeline (dev, prd, etc.) on the host group.
Need an LDIF schema and group structure for hosts. In addition to organizing users, LDAP should categorize sites, hosts, and critical components.
An example structure should be
cn=hdd1,ou=core,ou=msn0,ou=Hosts,dc=aninix,dc=net
. This describes a hard drive inside the core.msn0.aninix.net chassis, which lives in the first datacenter erected in range of the Madison, WI (MSN) airport.The schema should set address as the description on the site group, serial or MAC address as the description on the component entity, and chassis serial, function, and pipeline (dev, prd, etc.) on the host group.
We're going to restrict Sora to just users and groups -- IPAM will happen in our inventory.