Identify or Create LDIF Schema for Sora #4
Labels
No Label
Blocked
Duplicate
On-hold
Peer-review
RFC
Wontfix
Blocked
Duplicate
In-progress
On-hold
Peer-review
RFC
Wontfix
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: AniNIX/Kapisi#4
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.