From: Michael King (mking@bridgew.edu)
Date: Tue Aug 27 2002 - 07:49:57 CDT
I think an important question would be Can Dynamic Leases be placed into a
Pool? Since it's via pools that we are denying them addresses to begin
with.
Mike
-----Original Message-----
From: owner-netreg@southwestern.edu
[mailto:owner-netreg@southwestern.edu]On Behalf Of Bekim Shala
Sent: Tuesday, August 27, 2002 7:08 AM
To: netreg@southwestern.edu
Subject: Re: NetReg: is anyone using OMAPI ?
Greetings David.
To your question 1.
Yes they are permanent, they will exist across reboots.
If the deletion occurrs afterwards it will be reflected in the
dhcpd.leases file as well at the bottom and the next time
the dhcpd.leases file is refreshed it will dissapear all-together.
To your question 2
Yes you do not have to do nothing with dhcpd.conf, therefore no reboots.
You can also do a query for the lease such that there is no need to
traverse the dhcpd.leases file as well and get the MAC in real-time.
I'll sugest you to use a swig (www.swig.org) as a glue instead of
XS, in case of other people that are inclined to use other
scripting languages.
I did Omapi wrapper with C++ -> swig -> perl but it is not of Beta
quality and it will be in such stage for the next 4-5 months.
(it's a part time project (:
Good luck.
Regards, Bekim
Programmer
George Mason University
David Bussenschutt wrote:
>Peter,
> I'm looking at the OMAPI stuff today, I'll try and get some of the
>functionality done. I'll be using the perl module OMAPI::DHCP (not yet
>on CPAN).
>
>On the note of "not disturbing the base code to much". I'm sorry, but I'm
>going to disturb it lots. For a start, you need error checking (like
>what happens if any one of the open commands fails?), warning reporting
>(perl -w), and 'use strict;'. You should also use file locking on all
>files that are read or wrtitten to, and a lot of other things. I don't
>expect that you'll be able to just use my modified version to replace the
>existing one, but once it's done you should be able to pull the parts you
>want from it, and merge them into your existing code.. or something.
>
>P.S. Robert Lowe and myself intend on making this "new improved" version
>as a colaborative effort. If you don't want to incorporate the changes
>back into your main version, that's ok by us (we've discussed it) we'll
>just branch off. ;-)
>
>I also have a question or two to all ppl on the list...
>
>when 'host' entries are created via OMAPI, I've just today read that they
>are written to the the dhcpd.leases (NOT the .conf) file thus:
>host some-host {
> dynamic;
> hardware ethernet .........;
> fixed-address ........;
>}
>where the 'dynamic;' line represents that they came from omapi.
>1) Now the question... I'm guessing that the host stanza is
>permanent..that it doesn't "timeout" or get removed with a restart of the
>server. Is this guess correct? (otherwise we'd need to write the info in
>two places to make it persistent over reboots etc)
>
>2) If so, then that means that we don't actually have to write anything at
>all (with netreg) to the dhcpd.conf file, since we can write all host
>entries with omapi too. correct?
>
>Now back to the coding for me...
>
>David.
>--------------------------------------------------------------------
>David Bussenschutt Email: D.Bussenschutt@mailbox.gu.edu.au
>Senior Computing Support Officer & Systems Administrator/Programmer
>RedHat Certified Engineer.
>Member of Systems Administrators Guild of Australia.
>Location: Griffith University. Information Technology Services
> Brisbane Qld. Aust. (TEN bldg. rm 1.33) Ph: (07)38757079
>--------------------------------------------------------------------
>
>
>
>
>Peter Valian <valianp@southwestern.edu>
>Sent by: owner-netreg@southwestern.edu
>27/08/2002 12:48 AM
>Please respond to netreg
>
>
> To: netreg@southwestern.edu
> cc:
> Subject: Re: NetReg: is anyone using OMAPI ?
>
>
>David,
>
>I would really like to get OMAPI working with NetReg. Last time I took
>a look all I had was source code from omapi and omshell. I really
>didn't want to be the one to port the C code over to perl...i was hoping
>someone would do it :)
>
>Systems calls to the "omshell" seemed like a kludge at the time. If
>someone has the time and wants to make a major contribution to
>NetReg...make an OMAPI module can can replace a few subroutines cleanly
>without disturbing the base code too much.
>
>I know practically no one is running a stock NetReg setup but hopefully
>everyone tried to keep with its modular design.
>
>Thanks,
>-peter
>
>
>David Bussenschutt wrote:
>
>
>>Hi all, I've found your netreg product, and it's a great concept.
>>I'm in the process of implementing it in our test environment. To make
>>
>>
>it
>
>
>>work in our distributed DHCP environment (5 pairs of failover DHCP
>>
>>
>servers
>
>
>>on 5 university campuses) I need to be able to modify the register.cgi
>>
>>
>to
>
>
>>work via omapi. (lets worry about the admin.cgi later!) This is no big
>>deal, but I was wondering if anyone's done it before, so you can save me
>>
>>
>
>
>
>>the sweat ;-) I've found the following mention in the archives, and it
>>
>>
>
>
>
>>looked hopeful, but it doesn't seem like 1) a very neat way of doing it
>>(what about STDERR?) 2) like it's been tested or used since (almost a
>>
>>
>year
>
>
>>ago)
>>
>>http://www.southwestern.edu/ITS/netreg/archive/0284.html
>>http://www.southwestern.edu/ITS/netreg/archive/0286.html
>>
>>I found another product also called netreg (by Canegie-Mellon
>>
>>
>University)
>
>
>>(which has a similar ideal to this netreg, but is MUCH more
>>
>>
>feature-full,
>
>
>>and so bloated that I gave up on it!) , and in their archives I found
>>mention of a perl module called OMAPI.pm, and they said (I quote from
>>http://asg.web.cmu.edu/archive/message.php?mailbox=archive.netreg-users&ms
g=340)"
>>I'm using
>>Bruce Hudson's OMAPI perl module. I believe the only source is his
>>webpage.
>>His message to me on this subject was (in part):
>>--
>> You are certainly welcome to the code if it will help. You can get
>>
>>
>it
>
>
>>via "http://BHudson.UCIS.Dal.Ca/~hudson/omapi.zip". I would appreciate any
>>changes or enhancements sent back. I also except feature requests
>>
>>
>although
>
>
>>I make no promises.
>>--
>>"(end quote)
>>
>>This perl module seems to not need to use omshell at all (doing the
>>innards in c with some dhcpctl and omapi calls). Perhaps you've seen
>>this (or similar) and used it?
>>
>>Any comments/help appreciated. If I hear from no-one, I'll just have to
>>
>>
>
>
>
>>go on my merry way, and give this OMAPI.pm a go.
>>
>>David
>>--------------------------------------------------------------------
>>David Bussenschutt Email: D.Bussenschutt@mailbox.gu.edu.au
>>Senior Computing Support Officer & Systems Administrator/Programmer
>>RedHat Certified Engineer.
>>Member of Systems Administrators Guild of Australia.
>>Location: Griffith University. Information Technology Services
>> Brisbane Qld. Aust. (TEN bldg. rm 1.33) Ph: (07)38757079
>>--------------------------------------------------------------------
>>**********************************************************************
>>To unsubscribe from this list, send an e-mail message to
>>majordomo@southwestern.edu containing a single line with the words:
>>unsubscribe netreg
>>Send requests for assistance to: owner-netreg@southwestern.edu
>>**********************************************************************
>>
>>
>
>
>
>
**********************************************************************
To unsubscribe from this list, send an e-mail message to
majordomo@southwestern.edu containing a single line with the words:
unsubscribe netreg
Send requests for assistance to: owner-netreg@southwestern.edu
**********************************************************************
**********************************************************************
To unsubscribe from this list, send an e-mail message to
majordomo@southwestern.edu containing a single line with the words:
unsubscribe netreg
Send requests for assistance to: owner-netreg@southwestern.edu
**********************************************************************
This archive was generated by hypermail 2.1.4 : Thu Aug 12 2004 - 12:01:37 CDT