From owner-freebsd-hackers Mon Feb 2 11:03:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA14106 for hackers-outgoing; Mon, 2 Feb 1998 11:03:14 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from webserver.smginc.com (webserver.smginc.com [204.170.176.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA14022; Mon, 2 Feb 1998 11:03:07 -0800 (PST) (envelope-from AdamT@smginc.com) Received: from smginc.com ([204.170.177.4]) by webserver.smginc.com (post.office MTA v2.0 0813 ID# 0-13723) with SMTP id AAA280; Mon, 2 Feb 1998 14:05:07 -0500 Received: by smginc.com with Microsoft Mail id <34D6422A@smginc.com>; Mon, 02 Feb 98 14:01:14 PST From: Adam Turoff To: "'hackers@freebsd.org'" , "'config@freebsd.org'" Cc: "'mike@smith.net.au'" Subject: Multi-faced admin Date: Mon, 02 Feb 98 14:03:00 PST Message-ID: <34D6422A@smginc.com> X-Mailer: Microsoft Mail V3.0 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe hackers" Looking at Mikael Karpberg page on his architecture for admin'ing a FreeBSD box, I came across a link to Caldera's COAS project: http://www.coas.org I'm rather sorry to say that I haven't looked deeply into some of the broad scope ideas that people have been posting to -hackers recently. (I feel rather guilty that I haven't committed my big picture to bits and bytes yet either.) We all know what it means to be spread thin, I guess. :-) Anyway, skimming over COAS, (Caldera Open Adminstration System), it looks like either it's something worth porting, or it's something worth improving upon. All of the standard knobs are there, like curses/X/Java interfaces, etc. (Sorry, I can't post a summary right now. The code is at v0.09, appears to use lots of python and is GPL'd.) --- Reading the post about UMich's LDAP engine, it sounds rather radical. So, as of the moment, here's a concise view of what I'm seeing/hearing for a FreeBSD framework: - httpd type server (easy to plug any client into/write new clients) - standardized CGI interface subset for admin modules - LDAP for config managment by admin modules Five layers (three for glue) to have any random client reconfigure any part of the system. The top glue is pretty dumb; it just standardizes the interface. The middle glue layer is where all the work is done. The bottom glue layer appears rather dumb, but it should hide the complexity of a bazillion different config file formats (if I'm reading what Mike is saying about LDAP correctly). Sound good? I'll start a prototype in my copious free time before the end of the month. :-) -- Adam. PS: Mike, where can I find some docs, etc. on the UMich LDAP server?