OMAPI support for ISC DHCPd must die

[Michael DeHaan]

Two things:

(A)  It's been pointed out to me the OMAPI support in cobbler results in 
permanently deleting leases in nasty ways when "cobbler sync" is run or 
systems are edited.  

(B)  I've been told dhcpd support of OMAPI is slated for removal in a 
future version of ISC dhcpd.

Cobbler's DHCP management is much more solid with OMAPI disabled, and 
based on comments I've gotten on it, I propose we remove the feature for 
1.4.  It just does not feel particularly robust, and the feature seems 
to be going away anyhow.

Comments welcome.

The only downside to removing OMAPI is that to apply new MAC -> IP 
reservations (or in turn, MAC -> IP -> Hostname) DNS setups (if so 
enabled), it would require a "cobbler sync" once again.   

We could potentially add options to cobbler sync to just refresh 
DHCP/DNS without doing other sync activity if that helps with speed.

The only limitations I really see is that there is a window when doing 
the sync when the service restarts, but that would only affect machines 
rebooting at that particular point in time.

Sounds good?

--Michael

[Jeroen van Meeuwen]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Michael DeHaan wrote:
| Two things:
|
| (A)  It's been pointed out to me the OMAPI support in cobbler results in
| permanently deleting leases in nasty ways when "cobbler sync" is run or
| systems are edited.
|
| (B)  I've been told dhcpd support of OMAPI is slated for removal in a
| future version of ISC dhcpd.
|
| Cobbler's DHCP management is much more solid with OMAPI disabled, and
| based on comments I've gotten on it, I propose we remove the feature for
| 1.4.  It just does not feel particularly robust, and the feature seems
| to be going away anyhow.
|
| Comments welcome.
|

+1

Additionally, OMAPI does not do the trick when dhcp.template has been
altered and you do a cobbler sync (thus dhcpd.conf has been altered);
the dhcpd service will have to be reloaded or restarted.

| The only limitations I really see is that there is a window when doing
| the sync when the service restarts, but that would only affect machines
| rebooting at that particular point in time.
|

Could reloading the service(s) be considered rather then restarting them?

Kind regards,

Jeroen van Meeuwen
- -kanarip
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
>
> iEYEARECAAYFAkkpHqAACgkQKN6f2pNCvwhO+QCdE3NX8VIBl0GSB5R1ftpWH8/h
> YewAniVimJwpic7992YGeywQs+KGYi2c
> =N6EZ
> -----END PGP SIGNATURE-----

[Pablo Iranzo Gómez]

On Sun, 23 Nov 2008, Jeroen van Meeuwen wrote:

>  -----BEGIN PGP SIGNED MESSAGE-----
>  Hash: SHA1
>
>  Michael DeHaan wrote:
>  | Two things:
>  |
>  | (A)  It's been pointed out to me the OMAPI support in cobbler results in
>  | permanently deleting leases in nasty ways when "cobbler sync" is run or
>  | systems are edited.
>  |
>  | (B)  I've been told dhcpd support of OMAPI is slated for removal in a
>  | future version of ISC dhcpd.
>  |
>  | Cobbler's DHCP management is much more solid with OMAPI disabled, and
>  | based on comments I've gotten on it, I propose we remove the feature for
>  | 1.4.  It just does not feel particularly robust, and the feature seems
>  | to be going away anyhow.
>  |
>  | Comments welcome.
>  |
>
>  +1 
+1




-- 
Pablo Iranzo Gómez
(http://Alufis35.uv.es/~iranzo/)
(PGPKey Available on http://www.uv.es/~iranzop/PGPKey.pgp)
                   --
Postulado de Boling sobre la Ley de Murphy:

Si se encuentra bien, no se preocupe. Se le pasará