> As foreman writes to the leases file directly this is an issue for syncing.
Foreman Proxy does not write to the file directly. It uses omapi
command, which indeed writes to it. But remember, this is append-only
file.
Theoretically you can make a patch into Foreman Proxy DHCP provider and
introduce dhcp_servers option. We currently have dhcp_server which only
contains one server, maybe you could extend it so omapi connects to more
than one server making the changes in paralel. You'd need more than one
omapi keys and stuff, but this should work fine.
Or maybe you can make a change in foreman orchestration code so it
allows more than one DHCP server for a subnet.
I think you can also tail/stream the leases file to the backup machine
and after a failure you can startup your backup instance - this will
work just fine as long as the conf files are the same. There are perhaps
documented strategies for that.
I'm picking up on this but I'm not able to edit the code for this so far.
I have discussed this with the isc-dhcp guys and we need to write twice
using omapi, syncing the leases file is not working and also needs a
restart of the dhcp server.
There is already a 3year old ticket about it, I think this is prio to have
it HA available.
···
Op zaterdag 16 januari 2016 20:06:30 UTC+1 schreef Matt .:
>
> Hi,
>
> I was wondering if someone has a workaround for DHCP sync with failover.
>
> As foreman writes to the leases file directly this is an issue for
> syncing.
>
> Can't we write to a config file we include to the dhcpd.conf and
> reload dhcp when the proxy did something to dhcp ?
>
> Ideas are welcome.
>
> Cheers,
>
> Matt
>
Is this me or does no-one care about DHCP redundancy ?
···
Op zaterdag 16 januari 2016 20:06:30 UTC+1 schreef Matt .:
>
> Hi,
>
> I was wondering if someone has a workaround for DHCP sync with failover.
>
> As foreman writes to the leases file directly this is an issue for
> syncing.
>
> Can't we write to a config file we include to the dhcpd.conf and
> reload dhcp when the proxy did something to dhcp ?
>
> Ideas are welcome.
>
> Cheers,
>
> Matt
>
···
Op zaterdag 16 januari 2016 20:06:30 UTC+1 schreef Matt .:
>
> Hi,
>
> I was wondering if someone has a workaround for DHCP sync with failover.
>
> As foreman writes to the leases file directly this is an issue for
> syncing.
>
> Can't we write to a config file we include to the dhcpd.conf and
> reload dhcp when the proxy did something to dhcp ?
>
> Ideas are welcome.
>
> Cheers,
>
> Matt
>
I have wondered about the same problem.
Since foreman needs to read and write the leases and config files it
means that you cannot have a remote standalone DHCP server.
···
On 08/11/2016 04:32 PM, yamakasi.014@gmail.com wrote:
> Is this me or does no-one care about DHCP redundancy ?
>
>
>
> Op zaterdag 16 januari 2016 20:06:30 UTC+1 schreef Matt .:
>
> Hi,
>
> I was wondering if someone has a workaround for DHCP sync with
> failover.
>
> As foreman writes to the leases file directly this is an issue for
> syncing.
>
> Can't we write to a config file we include to the dhcpd.conf and
> reload dhcp when the proxy did something to dhcp ?
>
> Ideas are welcome.
>
> Cheers,
>
> Matt
>
> --
> You received this message because you are subscribed to the Google
> Groups "Foreman users" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to foreman-users+unsubscribe@googlegroups.com
> .
> To post to this group, send email to foreman-users@googlegroups.com
> .
> Visit this group at https://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
What do you mean by a standalone DHCP server ? The proxy handles that when
you installed the proxy on the DHCP server.
This goes about a second DHCP server that knows the same static leases as
the proxy knows for failover whent the primary, with proxy, fails.
···
Op donderdag 11 augustus 2016 22:39:40 UTC+2 schreef Alvin Starr:
>
> I have wondered about the same problem.
> Since foreman needs to read and write the leases and config files it means
> that you cannot have a remote standalone DHCP server.
>
>
> On 08/11/2016 04:32 PM, yamaka...@gmail.com wrote:
>
> Is this me or does no-one care about DHCP redundancy ?
>
>
>
> Op zaterdag 16 januari 2016 20:06:30 UTC+1 schreef Matt .:
>>
>> Hi,
>>
>> I was wondering if someone has a workaround for DHCP sync with failover.
>>
>> As foreman writes to the leases file directly this is an issue for
>> syncing.
>>
>> Can't we write to a config file we include to the dhcpd.conf and
>> reload dhcp when the proxy did something to dhcp ?
>>
>> Ideas are welcome.
>>
>> Cheers,
>>
>> Matt
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Foreman users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to foreman-user...@googlegroups.com .
> To post to this group, send email to forema...@googlegroups.com
> .
> Visit this group at https://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
>
>
> --
> Alvin Starr || voice: (905)513-7688
> Netvel Inc. || Cell: (416)806-0133al...@netvel.net ||
>
>
A standalone DHCP server without lots of extra software installed.
I do not want to install the whole forman-proxy on the DHCP or DNS servers
As an asidethe isc_dhcp proxy does not parse correctly formatted
dhcpd.conffiles(I just filed a bug report).
Looking at omapi I could be convinced that it is impossible to get
thecurrent dhcp config informationremotely.
···
On 08/11/2016 05:26 PM, yamakasi.014@gmail.com wrote:
> What do you mean by a standalone DHCP server ? The proxy handles that
> when you installed the proxy on the DHCP server.
>
> This goes about a second DHCP server that knows the same static leases
> as the proxy knows for failover whent the primary, with proxy, fails.
>
> Op donderdag 11 augustus 2016 22:39:40 UTC+2 schreef Alvin Starr:
>
> I have wondered about the same problem.
> Since foreman needs to read and write the leases and config files
> it means that you cannot have a remote standalone DHCP server.
>
>
> On 08/11/2016 04:32 PM, yamaka...@gmail.com wrote:
>> Is this me or does no-one care about DHCP redundancy ?
>>
>>
>>
>> Op zaterdag 16 januari 2016 20:06:30 UTC+1 schreef Matt .:
>>
>> Hi,
>>
>> I was wondering if someone has a workaround for DHCP sync
>> with failover.
>>
>> As foreman writes to the leases file directly this is an
>> issue for syncing.
>>
>> Can't we write to a config file we include to the dhcpd.conf and
>> reload dhcp when the proxy did something to dhcp ?
>>
>> Ideas are welcome.
>>
>> Cheers,
>>
>> Matt
>>
>> --
>> You received this message because you are subscribed to the
>> Google Groups "Foreman users" group.
>> To unsubscribe from this group and stop receiving emails from it,
>> send an email to foreman-user...@googlegroups.com .
>> To post to this group, send email to forema...@googlegroups.com
>> .
>> Visit this group at https://groups.google.com/group/foreman-users
>> .
>> For more options, visit https://groups.google.com/d/optout
>> .
>
> --
> Alvin Starr || voice: (905)513-7688
> Netvel Inc. || Cell: (416)806-0133
> al...@netvel.net ||
>
What we like to have is a second DHCP with a proxy where is talked to using
OMAPI by foreman so we have a replication about the static leases.
DHCP itself is unable to sync them this way and for Failover we need to
have 2 writes to 2 DHCP servers which are in clutser mode.
DNS is not involved here.
···
Op donderdag 11 augustus 2016 23:50:43 UTC+2 schreef Alvin Starr:
>
> A standalone DHCP server without lots of extra software installed.
> I do not want to install the whole forman-proxy on the DHCP or DNS servers
>
>
> As an aside the isc_dhcp proxy does not parse correctly formatted
> dhcpd.conf files(I just filed a bug report).
>
>
> Looking at omapi I could be convinced that it is impossible to get the
> current dhcp config information remotely.
>
>
> On 08/11/2016 05:26 PM, yamaka...@gmail.com wrote:
>
> What do you mean by a standalone DHCP server ? The proxy handles that when
> you installed the proxy on the DHCP server.
>
> This goes about a second DHCP server that knows the same static leases as
> the proxy knows for failover whent the primary, with proxy, fails.
>
> Op donderdag 11 augustus 2016 22:39:40 UTC+2 schreef Alvin Starr:
>>
>> I have wondered about the same problem.
>> Since foreman needs to read and write the leases and config files it
>> means that you cannot have a remote standalone DHCP server.
>>
>>
>> On 08/11/2016 04:32 PM, yamaka...@gmail.com wrote:
>>
>> Is this me or does no-one care about DHCP redundancy ?
>>
>>
>>
>> Op zaterdag 16 januari 2016 20:06:30 UTC+1 schreef Matt .:
>>>
>>> Hi,
>>>
>>> I was wondering if someone has a workaround for DHCP sync with failover.
>>>
>>> As foreman writes to the leases file directly this is an issue for
>>> syncing.
>>>
>>> Can't we write to a config file we include to the dhcpd.conf and
>>> reload dhcp when the proxy did something to dhcp ?
>>>
>>> Ideas are welcome.
>>>
>>> Cheers,
>>>
>>> Matt
>>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Foreman users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to foreman-user...@googlegroups.com.
>> To post to this group, send email to forema...@googlegroups.com.
>> Visit this group at https://groups.google.com/group/foreman-users.
>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>> --
>> Alvin Starr || voice: (905)513-7688
>> Netvel Inc. || Cell: (416)806-0133al...@netvel.net ||
>>
>>
> --
> Alvin Starr || voice: (905)513-7688
> Netvel Inc. || Cell: (416)806-0133al...@netvel.net ||
>
>
We have slightly different problems but are both limited by the nature
of foremans dhcp-proxy.
If you create static leases using omshell then I believe the data will
be replicated to a failover dhcp server.
Forman will create new hosts using omshell.
The comment about DNS is only because foreman can cleanly interact with
DNS remotely.
···
On 08/11/2016 06:05 PM, yamakasi.014@gmail.com wrote:
> You are completely wrong.
>
> What we like to have is a second DHCP with a proxy where is talked to
> using OMAPI by foreman so we have a replication about the static leases.
>
> DHCP itself is unable to sync them this way and for Failover we need
> to have 2 writes to 2 DHCP servers which are in clutser mode.
>
> DNS is not involved here.
>
> Op donderdag 11 augustus 2016 23:50:43 UTC+2 schreef Alvin Starr:
>
> A standalone DHCP server without lots of extra software installed.
> I do not want to install the whole forman-proxy on the DHCP or DNS
> servers
>
>
> As an asidethe isc_dhcp proxy does not parse correctly formatted
> dhcpd.conffiles(I just filed a bug report).
>
>
> Looking at omapi I could be convinced that it is impossible to get
> thecurrent dhcp config informationremotely.
>
>
> On 08/11/2016 05:26 PM, yamaka...@gmail.com wrote:
>> What do you mean by a standalone DHCP server ? The proxy handles
>> that when you installed the proxy on the DHCP server.
>>
>> This goes about a second DHCP server that knows the same static
>> leases as the proxy knows for failover whent the primary, with
>> proxy, fails.
>>
>> Op donderdag 11 augustus 2016 22:39:40 UTC+2 schreef Alvin Starr:
>>
>> I have wondered about the same problem.
>> Since foreman needs to read and write the leases and config
>> files it means that you cannot have a remote standalone DHCP
>> server.
>>
>>
>> On 08/11/2016 04:32 PM, yamaka...@gmail.com wrote:
>>> Is this me or does no-one care about DHCP redundancy ?
>>>
>>>
>>>
>>> Op zaterdag 16 januari 2016 20:06:30 UTC+1 schreef Matt .:
>>>
>>> Hi,
>>>
>>> I was wondering if someone has a workaround for DHCP
>>> sync with failover.
>>>
>>> As foreman writes to the leases file directly this is an
>>> issue for syncing.
>>>
>>> Can't we write to a config file we include to the
>>> dhcpd.conf and
>>> reload dhcp when the proxy did something to dhcp ?
>>>
>>> Ideas are welcome.
>>>
>>> Cheers,
>>>
>>> Matt
>>>
>>> --
>>> You received this message because you are subscribed to the
>>> Google Groups "Foreman users" group.
>>> To unsubscribe from this group and stop receiving emails
>>> from it, send an email to foreman-user...@googlegroups.com.
>>> To post to this group, send email to forema...@googlegroups.com.
>>> Visit this group at
>>> https://groups.google.com/group/foreman-users
>>> .
>>> For more options, visit https://groups.google.com/d/optout
>>> .
>>
>> --
>> Alvin Starr || voice: (905)513-7688
>> Netvel Inc. || Cell: (416)806-0133
>> al...@netvel.net ||
>>
>
> --
> Alvin Starr || voice: (905)513-7688
> Netvel Inc. || Cell: (416)806-0133
> al...@netvel.net ||
>
DHCP will not replicate the static leases as I said before, you need twice
the omapi using omshell.
I have discussed this with the ISC guys.
···
Op vrijdag 12 augustus 2016 00:26:15 UTC+2 schreef Alvin Starr:
>
> We have slightly different problems but are both limited by the nature of
> foremans dhcp-proxy.
>
> If you create static leases using omshell then I believe the data will be
> replicated to a failover dhcp server.
> Forman will create new hosts using omshell.
>
> The comment about DNS is only because foreman can cleanly interact with
> DNS remotely.
>
>
> On 08/11/2016 06:05 PM, yamaka...@gmail.com wrote:
>
> You are completely wrong.
>
> What we like to have is a second DHCP with a proxy where is talked to
> using OMAPI by foreman so we have a replication about the static leases.
>
> DHCP itself is unable to sync them this way and for Failover we need to
> have 2 writes to 2 DHCP servers which are in clutser mode.
>
> DNS is not involved here.
>
> Op donderdag 11 augustus 2016 23:50:43 UTC+2 schreef Alvin Starr:
>>
>> A standalone DHCP server without lots of extra software installed.
>> I do not want to install the whole forman-proxy on the DHCP or DNS ser
>> vers
>>
>>
>> As an aside the isc_dhcp proxy does not parse correctly formatted
>> dhcpd.conf files(I just filed a bug report).
>>
>>
>> Looking at omapi I could be convinced that it is impossible to get the
>> current dhcp config information remotely.
>>
>>
>> On 08/11/2016 05:26 PM, yamaka...@gmail.com wrote:
>>
>> What do you mean by a standalone DHCP server ? The proxy handles that
>> when you installed the proxy on the DHCP server.
>>
>> This goes about a second DHCP server that knows the same static leases as
>> the proxy knows for failover whent the primary, with proxy, fails.
>>
>> Op donderdag 11 augustus 2016 22:39:40 UTC+2 schreef Alvin Starr:
>>>
>>> I have wondered about the same problem.
>>> Since foreman needs to read and write the leases and config files it
>>> means that you cannot have a remote standalone DHCP server.
>>>
>>>
>>> On 08/11/2016 04:32 PM, yamaka...@gmail.com wrote:
>>>
>>> Is this me or does no-one care about DHCP redundancy ?
>>>
>>>
>>>
>>> Op zaterdag 16 januari 2016 20:06:30 UTC+1 schreef Matt .:
>>>>
>>>> Hi,
>>>>
>>>> I was wondering if someone has a workaround for DHCP sync with
>>>> failover.
>>>>
>>>> As foreman writes to the leases file directly this is an issue for
>>>> syncing.
>>>>
>>>> Can't we write to a config file we include to the dhcpd.conf and
>>>> reload dhcp when the proxy did something to dhcp ?
>>>>
>>>> Ideas are welcome.
>>>>
>>>> Cheers,
>>>>
>>>> Matt
>>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Foreman users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to foreman-user...@googlegroups.com.
>>> To post to this group, send email to forema...@googlegroups.com.
>>> Visit this group at https://groups.google.com/group/foreman-users.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>>
>>> --
>>> Alvin Starr || voice: (905)513-7688
>>> Netvel Inc. || Cell: (416)806-0133al...@netvel.net ||
>>>
>>>
>> --
>> Alvin Starr || voice: (905)513-7688
>> Netvel Inc. || Cell: (416)806-0133al...@netvel.net ||
>>
>>
> --
> Alvin Starr || voice: (905)513-7688
> Netvel Inc. || Cell: (416)806-0133al...@netvel.net ||
>
>
I have looked at this a bit more and your right.
Its hard to believe that the ISC develpers would be that short sighted
to not extend the design so that changes made to the primary are copied
to the secondary.
I can see 3 possible solutions.
fix the ISC DHCP server.
Fixing the DHCP server would be a major pain and there may be some
fundamental reason that its not possible to copy the static entries
change dhcp_isc_main.rb to contact both primary and secondary DHCP
servers.
Looking at the code it would be possible to change the omcmd
routine to talk to a secondary server.
This would require adding configuration items to handle the secondary.
The problem I can see here is what to do in the case of an error
condition from one server and not the other?
replace omshell with a shell that writes to both servers.
An omshell wrapper could parse the dhcpd.conf file and determine if
there is a secondary server.
If there is a secondary server the commands could be piped to both
servers.
Once again there is the issue of what to do about errors in one
server and not the other.
This solution would also likely require a small patch to
dhcp_isc_main.rb to allow for changing.
I could supply a patch to the dhcp_isc_main.rb and do some testing on my
environment so that it would pass the initial sniff test but I am not in
a position to do a full pull request and then submit the patches via
usual developer channel.
···
On 08/11/2016 06:40 PM, yamakasi.014@gmail.com wrote:
> DHCP will not replicate the static leases as I said before, you need
> twice the omapi using omshell.
>
> I have discussed this with the ISC guys.
>
>
> Op vrijdag 12 augustus 2016 00:26:15 UTC+2 schreef Alvin Starr:
>
> We have slightly different problems but are both limited by the
> nature of foremans dhcp-proxy.
>
> If you create static leases using omshell then I believe the data
> will be replicated to a failover dhcp server.
> Forman will create new hosts using omshell.
>
> The comment about DNS is only because foreman can cleanly interact
> with DNS remotely.
>
>
> On 08/11/2016 06:05 PM, yamaka...@gmail.com wrote:
>> You are completely wrong.
>>
>> What we like to have is a second DHCP with a proxy where is
>> talked to using OMAPI by foreman so we have a replication about
>> the static leases.
>>
>> DHCP itself is unable to sync them this way and for Failover we
>> need to have 2 writes to 2 DHCP servers which are in clutser mode.
>>
>> DNS is not involved here.
>>
>> Op donderdag 11 augustus 2016 23:50:43 UTC+2 schreef Alvin Starr:
>>
>> A standalone DHCP server without lots of extra software
>> installed.
>> I do not want to install the whole forman-proxy on the DHCP
>> or DNS servers
>>
>>
>> As an asidethe isc_dhcp proxy does not parse correctly
>> formatted dhcpd.conffiles(I just filed a bug report).
>>
>>
>> Looking at omapi I could be convinced that it is impossible
>> to get thecurrent dhcp config informationremotely.
>>
>>
>> On 08/11/2016 05:26 PM, yamaka...@gmail.com wrote:
>>> What do you mean by a standalone DHCP server ? The proxy
>>> handles that when you installed the proxy on the DHCP server.
>>>
>>> This goes about a second DHCP server that knows the same
>>> static leases as the proxy knows for failover whent the
>>> primary, with proxy, fails.
>>>
>>> Op donderdag 11 augustus 2016 22:39:40 UTC+2 schreef Alvin >>> Starr:
>>>
>>> I have wondered about the same problem.
>>> Since foreman needs to read and write the leases and
>>> config files it means that you cannot have a remote
>>> standalone DHCP server.
>>>
>>>
>>> On 08/11/2016 04:32 PM, yamaka...@gmail.com wrote:
>>>> Is this me or does no-one care about DHCP redundancy ?
>>>>
>>>>
>>>>
>>>> Op zaterdag 16 januari 2016 20:06:30 UTC+1 schreef Matt .:
>>>>
>>>> Hi,
>>>>
>>>> I was wondering if someone has a workaround for
>>>> DHCP sync with failover.
>>>>
>>>> As foreman writes to the leases file directly this
>>>> is an issue for syncing.
>>>>
>>>> Can't we write to a config file we include to the
>>>> dhcpd.conf and
>>>> reload dhcp when the proxy did something to dhcp ?
>>>>
>>>> Ideas are welcome.
>>>>
>>>> Cheers,
>>>>
>>>> Matt
>>>>
>>>> --
>>>> You received this message because you are subscribed to
>>>> the Google Groups "Foreman users" group.
>>>> To unsubscribe from this group and stop receiving
>>>> emails from it, send an email to
>>>> foreman-user...@googlegroups.com.
>>>> To post to this group, send email to
>>>> forema...@googlegroups.com.
>>>> Visit this group at
>>>> https://groups.google.com/group/foreman-users
>>>> .
>>>> For more options, visit
>>>> https://groups.google.com/d/optout
>>>> .
>>>
>>> --
>>> Alvin Starr || voice: (905)513-7688
>>> Netvel Inc. || Cell: (416)806-0133
>>> al...@netvel.net ||
>>>
>>
>> --
>> Alvin Starr || voice: (905)513-7688
>> Netvel Inc. || Cell: (416)806-0133
>> al...@netvel.net ||
>>
>
> --
> Alvin Starr || voice: (905)513-7688
> Netvel Inc. || Cell: (416)806-0133
> al...@netvel.net ||
>
Thanks for your reply, I'm happy you picked this up, I really am!
My responses to your points:
I think it's not needed for them, but as foreman can use the dhcp always
instead with static leases instead of bootstrapping only we have this issue
indeed. Also because foreman deployment is DNS based, isc doesn't think
about this I think but I know the new DHCP server they developed does this
different.
2.I think this is the best solution as you can even chose then which DNS is
primary and which one is not. You can also select a dhcp server in a whole
different subnet as long as they are in your dhcp-helpers in your switch. I
think this would be best. About failing, if it can contact one server you
will be noticed and you need to click a proceed button again ? If the
machine is build you can always do later on an edit and submit of the host
again to update the second dhcp, or first dhcp server. Maybe some button @
the host page, or in the overview in the dropdown would be nice to have,
something like… redeploy/update dhcp and dns. We can always show an
overviews of which servers were deplyed with one of the two servers
available so you can easy update them.
Sounds good, but I think it's best to handle this from foreman as we are
in control what happens where then. you can also deploy as in point 2 with
one dhcp server failing.
I can't wait to test this as this would be awesome for redundancy!
Thanks for catching up so far!!
Cheers,
Matt
···
Op maandag 15 augustus 2016 18:02:50 UTC+2 schreef Alvin Starr:
>
> I have looked at this a bit more and your right.
> Its hard to believe that the ISC develpers would be that short sighted to
> not extend the design so that changes made to the primary are copied to the
> secondary.
>
> I can see 3 possible solutions.
> 1) fix the ISC DHCP server.
> Fixing the DHCP server would be a major pain and there may be some
> fundamental reason that its not possible to copy the static entries
>
> 2) change dhcp_isc_main.rb to contact both primary and secondary DHCP
> servers.
> Looking at the code it would be possible to change the omcmd routine
> to talk to a secondary server.
> This would require adding configuration items to handle the secondary.
> The problem I can see here is what to do in the case of an error
> condition from one server and not the other?
>
> 3) replace omshell with a shell that writes to both servers.
> An omshell wrapper could parse the dhcpd.conf file and determine if
> there is a secondary server.
> If there is a secondary server the commands could be piped to both
> servers.
> Once again there is the issue of what to do about errors in one server
> and not the other.
> This solution would also likely require a small patch to dhcp_isc_main.rb
> to allow for changing.
>
> I could supply a patch to the dhcp_isc_main.rb and do some testing on my
> environment so that it would pass the initial sniff test but I am not in a
> position to do a full pull request and then submit the patches via usual
> developer channel.
>
>
>
>
> On 08/11/2016 06:40 PM, yamaka...@gmail.com wrote:
>
> DHCP will not replicate the static leases as I said before, you need twice
> the omapi using omshell.
>
> I have discussed this with the ISC guys.
>
>
> Op vrijdag 12 augustus 2016 00:26:15 UTC+2 schreef Alvin Starr:
>>
>> We have slightly different problems but are both limited by the nature of
>> foremans dhcp-proxy.
>>
>> If you create static leases using omshell then I believe the data will be
>> replicated to a failover dhcp server.
>> Forman will create new hosts using omshell.
>>
>> The comment about DNS is only because foreman can cleanly interact with
>> DNS remotely.
>>
>>
>> On 08/11/2016 06:05 PM, yamaka...@gmail.com wrote:
>>
>> You are completely wrong.
>>
>> What we like to have is a second DHCP with a proxy where is talked to
>> using OMAPI by foreman so we have a replication about the static leases.
>>
>> DHCP itself is unable to sync them this way and for Failover we need to
>> have 2 writes to 2 DHCP servers which are in clutser mode.
>>
>> DNS is not involved here.
>>
>> Op donderdag 11 augustus 2016 23:50:43 UTC+2 schreef Alvin Starr:
>>>
>>> A standalone DHCP server without lots of extra software installed.
>>> I do not want to install the whole forman-proxy on the DHCP or DNS ser
>>> vers
>>>
>>>
>>> As an aside the isc_dhcp proxy does not parse correctly formatted
>>> dhcpd.conf files(I just filed a bug report).
>>>
>>>
>>> Looking at omapi I could be convinced that it is impossible to get the
>>> current dhcp config information remotely.
>>>
>>>
>>> On 08/11/2016 05:26 PM, yamaka...@gmail.com wrote:
>>>
>>> What do you mean by a standalone DHCP server ? The proxy handles that
>>> when you installed the proxy on the DHCP server.
>>>
>>> This goes about a second DHCP server that knows the same static leases
>>> as the proxy knows for failover whent the primary, with proxy, fails.
>>>
>>> Op donderdag 11 augustus 2016 22:39:40 UTC+2 schreef Alvin Starr:
>>>>
>>>> I have wondered about the same problem.
>>>> Since foreman needs to read and write the leases and config files it
>>>> means that you cannot have a remote standalone DHCP server.
>>>>
>>>>
>>>> On 08/11/2016 04:32 PM, yamaka...@gmail.com wrote:
>>>>
>>>> Is this me or does no-one care about DHCP redundancy ?
>>>>
>>>>
>>>>
>>>> Op zaterdag 16 januari 2016 20:06:30 UTC+1 schreef Matt .:
>>>>>
>>>>> Hi,
>>>>>
>>>>> I was wondering if someone has a workaround for DHCP sync with
>>>>> failover.
>>>>>
>>>>> As foreman writes to the leases file directly this is an issue for
>>>>> syncing.
>>>>>
>>>>> Can't we write to a config file we include to the dhcpd.conf and
>>>>> reload dhcp when the proxy did something to dhcp ?
>>>>>
>>>>> Ideas are welcome.
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Matt
>>>>>
>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "Foreman users" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to foreman-user...@googlegroups.com.
>>>> To post to this group, send email to forema...@googlegroups.com.
>>>> Visit this group at
>>>> https://groups.google.com/group/foreman-users.
>>>> For more options, visit
>>>> https://groups.google.com/d/optout.
>>>>
>>>>
>>>> --
>>>> Alvin Starr || voice: (905)513-7688
>>>> Netvel Inc. || Cell: (416)806-0133al...@netvel.net ||
>>>>
>>>>
>>> --
>>> Alvin Starr || voice: (905)513-7688
>>> Netvel Inc. || Cell: (416)806-0133al...@netvel.net ||
>>>
>>>
>> --
>> Alvin Starr || voice: (905)513-7688
>> Netvel Inc. || Cell: (416)806-0133al...@netvel.net ||
>>
>>
> --
> Alvin Starr || voice: (905)513-7688
> Netvel Inc. || Cell: (416)806-0133al...@netvel.net ||
>
>
Not a solution per say, but a reasonable work around. Call the attached
script in a frequent cron job.
···
On Monday, August 15, 2016 at 11:02:50 AM UTC-5, Alvin Starr wrote:
>
> I have looked at this a bit more and your right.
> Its hard to believe that the ISC develpers would be that short sighted to
> not extend the design so that changes made to the primary are copied to the
> secondary.
>
> I can see 3 possible solutions.
> 1) fix the ISC DHCP server.
> Fixing the DHCP server would be a major pain and there may be some
> fundamental reason that its not possible to copy the static entries
>
> 2) change dhcp_isc_main.rb to contact both primary and secondary DHCP
> servers.
> Looking at the code it would be possible to change the omcmd routine
> to talk to a secondary server.
> This would require adding configuration items to handle the secondary.
> The problem I can see here is what to do in the case of an error
> condition from one server and not the other?
>
> 3) replace omshell with a shell that writes to both servers.
> An omshell wrapper could parse the dhcpd.conf file and determine if
> there is a secondary server.
> If there is a secondary server the commands could be piped to both
> servers.
> Once again there is the issue of what to do about errors in one server
> and not the other.
> This solution would also likely require a small patch to dhcp_isc_main.rb
> to allow for changing.
>
> I could supply a patch to the dhcp_isc_main.rb and do some testing on my
> environment so that it would pass the initial sniff test but I am not in a
> position to do a full pull request and then submit the patches via usual
> developer channel.
>
>
>
>
> On 08/11/2016 06:40 PM, yamaka...@gmail.com wrote:
>
> DHCP will not replicate the static leases as I said before, you need twice
> the omapi using omshell.
>
> I have discussed this with the ISC guys.
>
>
> Op vrijdag 12 augustus 2016 00:26:15 UTC+2 schreef Alvin Starr:
>>
>> We have slightly different problems but are both limited by the nature of
>> foremans dhcp-proxy.
>>
>> If you create static leases using omshell then I believe the data will be
>> replicated to a failover dhcp server.
>> Forman will create new hosts using omshell.
>>
>> The comment about DNS is only because foreman can cleanly interact with
>> DNS remotely.
>>
>>
>> On 08/11/2016 06:05 PM, yamaka...@gmail.com wrote:
>>
>> You are completely wrong.
>>
>> What we like to have is a second DHCP with a proxy where is talked to
>> using OMAPI by foreman so we have a replication about the static leases.
>>
>> DHCP itself is unable to sync them this way and for Failover we need to
>> have 2 writes to 2 DHCP servers which are in clutser mode.
>>
>> DNS is not involved here.
>>
>> Op donderdag 11 augustus 2016 23:50:43 UTC+2 schreef Alvin Starr:
>>>
>>> A standalone DHCP server without lots of extra software installed.
>>> I do not want to install the whole forman-proxy on the DHCP or DNS ser
>>> vers
>>>
>>>
>>> As an aside the isc_dhcp proxy does not parse correctly formatted
>>> dhcpd.conf files(I just filed a bug report).
>>>
>>>
>>> Looking at omapi I could be convinced that it is impossible to get the
>>> current dhcp config information remotely.
>>>
>>>
>>> On 08/11/2016 05:26 PM, yamaka...@gmail.com wrote:
>>>
>>> What do you mean by a standalone DHCP server ? The proxy handles that
>>> when you installed the proxy on the DHCP server.
>>>
>>> This goes about a second DHCP server that knows the same static leases
>>> as the proxy knows for failover whent the primary, with proxy, fails.
>>>
>>> Op donderdag 11 augustus 2016 22:39:40 UTC+2 schreef Alvin Starr:
>>>>
>>>> I have wondered about the same problem.
>>>> Since foreman needs to read and write the leases and config files it
>>>> means that you cannot have a remote standalone DHCP server.
>>>>
>>>>
>>>> On 08/11/2016 04:32 PM, yamaka...@gmail.com wrote:
>>>>
>>>> Is this me or does no-one care about DHCP redundancy ?
>>>>
>>>>
>>>>
>>>> Op zaterdag 16 januari 2016 20:06:30 UTC+1 schreef Matt .:
>>>>>
>>>>> Hi,
>>>>>
>>>>> I was wondering if someone has a workaround for DHCP sync with
>>>>> failover.
>>>>>
>>>>> As foreman writes to the leases file directly this is an issue for
>>>>> syncing.
>>>>>
>>>>> Can't we write to a config file we include to the dhcpd.conf and
>>>>> reload dhcp when the proxy did something to dhcp ?
>>>>>
>>>>> Ideas are welcome.
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Matt
>>>>>
>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "Foreman users" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to foreman-user...@googlegroups.com.
>>>> To post to this group, send email to forema...@googlegroups.com.
>>>> Visit this group at
>>>> https://groups.google.com/group/foreman-users.
>>>> For more options, visit
>>>> https://groups.google.com/d/optout.
>>>>
>>>>
>>>> --
>>>> Alvin Starr || voice: (905)513-7688
>>>> Netvel Inc. || Cell: (416)806-0133al...@netvel.net ||
>>>>
>>>>
>>> --
>>> Alvin Starr || voice: (905)513-7688
>>> Netvel Inc. || Cell: (416)806-0133al...@netvel.net ||
>>>
>>>
>> --
>> Alvin Starr || voice: (905)513-7688
>> Netvel Inc. || Cell: (416)806-0133al...@netvel.net ||
>>
>>
> --
> Alvin Starr || voice: (905)513-7688
> Netvel Inc. || Cell: (416)806-0133al...@netvel.net ||
>
>
This would be a good starting point, the more simple the better, but I
was looking upfront as I think we once need to have some proxy
redeploy function in foreman itself for various settings. In this case
we could even start with a second server from scratch if it was never
involved by adding leases to it in the first place.
So you idea is good, but do you want to add a second select box in the
subnets where we normally select the only DHCP server at the moment ?
I think we could later on think about how to make a system which never
got a second DHCP server pushed with all static leases from foreman @
once. And there we are directly @ the point for proxy sync from
foreman, I will make some bugreport for that to see how people think
about that.
···
2016-08-16 13:50 GMT+02:00 Alvin Starr :
> I would not get all that excited.
> I was thinking of coding the secondary in the dhcp_isc.yml and just running
> the omapi calls against both servers.
>
> I was not thinking about displaying the server status at all.
> I was hoping to keep this really simple.
> If there is any error I think the answer will need to be "fix the DHCPD
> config and restart it".
>
>
>
> On 08/15/2016 03:49 PM, yamakasi.014@gmail.com wrote:
>
> Thanks for your reply, I'm happy you picked this up, I really am!
>
> My responses to your points:
>
> 1. I think it's not needed for them, but as foreman can use the dhcp always
> instead with static leases instead of bootstrapping only we have this issue
> indeed. Also because foreman deployment is DNS based, isc doesn't think
> about this I think but I know the new DHCP server they developed does this
> different.
>
> 2.I think this is the best solution as you can even chose then which DNS is
> primary and which one is not. You can also select a dhcp server in a whole
> different subnet as long as they are in your dhcp-helpers in your switch. I
> think this would be best. About failing, if it can contact one server you
> will be noticed and you need to click a proceed button again ? If the
> machine is build you can always do later on an edit and submit of the host
> again to update the second dhcp, or first dhcp server. Maybe some button @
> the host page, or in the overview in the dropdown would be nice to have,
> something like... redeploy/update dhcp and dns. We can always show an
> overviews of which servers were deplyed with one of the two servers
> available so you can easy update them.
>
> 3. Sounds good, but I think it's best to handle this from foreman as we are
> in control what happens where then. you can also deploy as in point 2 with
> one dhcp server failing.
>
> I can't wait to test this as this would be awesome for redundancy!
>
> Thanks for catching up so far!!
>
> Cheers,
>
> Matt
>
>
>
> Op maandag 15 augustus 2016 18:02:50 UTC+2 schreef Alvin Starr:
>>
>> I have looked at this a bit more and your right.
>> Its hard to believe that the ISC develpers would be that short sighted to
>> not extend the design so that changes made to the primary are copied to the
>> secondary.
>>
>> I can see 3 possible solutions.
>> 1) fix the ISC DHCP server.
>> Fixing the DHCP server would be a major pain and there may be some
>> fundamental reason that its not possible to copy the static entries
>>
>> 2) change dhcp_isc_main.rb to contact both primary and secondary DHCP
>> servers.
>> Looking at the code it would be possible to change the omcmd routine
>> to talk to a secondary server.
>> This would require adding configuration items to handle the secondary.
>> The problem I can see here is what to do in the case of an error
>> condition from one server and not the other?
>>
>> 3) replace omshell with a shell that writes to both servers.
>> An omshell wrapper could parse the dhcpd.conf file and determine if
>> there is a secondary server.
>> If there is a secondary server the commands could be piped to both
>> servers.
>> Once again there is the issue of what to do about errors in one server
>> and not the other.
>> This solution would also likely require a small patch to
>> dhcp_isc_main.rb to allow for changing.
>>
>> I could supply a patch to the dhcp_isc_main.rb and do some testing on my
>> environment so that it would pass the initial sniff test but I am not in a
>> position to do a full pull request and then submit the patches via usual
>> developer channel.
>>
>>
>>
>>
>> On 08/11/2016 06:40 PM, yamaka...@gmail.com wrote:
>>
>> DHCP will not replicate the static leases as I said before, you need twice
>> the omapi using omshell.
>>
>> I have discussed this with the ISC guys.
>>
>>
>> Op vrijdag 12 augustus 2016 00:26:15 UTC+2 schreef Alvin Starr:
>>>
>>> We have slightly different problems but are both limited by the nature of
>>> foremans dhcp-proxy.
>>>
>>> If you create static leases using omshell then I believe the data will be
>>> replicated to a failover dhcp server.
>>> Forman will create new hosts using omshell.
>>>
>>> The comment about DNS is only because foreman can cleanly interact with
>>> DNS remotely.
>>>
>>>
>>> On 08/11/2016 06:05 PM, yamaka...@gmail.com wrote:
>>>
>>> You are completely wrong.
>>>
>>> What we like to have is a second DHCP with a proxy where is talked to
>>> using OMAPI by foreman so we have a replication about the static leases.
>>>
>>> DHCP itself is unable to sync them this way and for Failover we need to
>>> have 2 writes to 2 DHCP servers which are in clutser mode.
>>>
>>> DNS is not involved here.
>>>
>>> Op donderdag 11 augustus 2016 23:50:43 UTC+2 schreef Alvin Starr:
>>>>
>>>> A standalone DHCP server without lots of extra software installed.
>>>> I do not want to install the whole forman-proxy on the DHCP or DNS
>>>> servers
>>>>
>>>>
>>>> As an aside the isc_dhcp proxy does not parse correctly formatted
>>>> dhcpd.conf files(I just filed a bug report).
>>>>
>>>>
>>>> Looking at omapi I could be convinced that it is impossible to get the
>>>> current dhcp config information remotely.
>>>>
>>>>
>>>> On 08/11/2016 05:26 PM, yamaka...@gmail.com wrote:
>>>>
>>>> What do you mean by a standalone DHCP server ? The proxy handles that
>>>> when you installed the proxy on the DHCP server.
>>>>
>>>> This goes about a second DHCP server that knows the same static leases
>>>> as the proxy knows for failover whent the primary, with proxy, fails.
>>>>
>>>> Op donderdag 11 augustus 2016 22:39:40 UTC+2 schreef Alvin Starr:
>>>>>
>>>>> I have wondered about the same problem.
>>>>> Since foreman needs to read and write the leases and config files it
>>>>> means that you cannot have a remote standalone DHCP server.
>>>>>
>>>>>
>>>>> On 08/11/2016 04:32 PM, yamaka...@gmail.com wrote:
>>>>>
>>>>> Is this me or does no-one care about DHCP redundancy ?
>>>>>
>>>>>
>>>>>
>>>>> Op zaterdag 16 januari 2016 20:06:30 UTC+1 schreef Matt .:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I was wondering if someone has a workaround for DHCP sync with
>>>>>> failover.
>>>>>>
>>>>>> As foreman writes to the leases file directly this is an issue for
>>>>>> syncing.
>>>>>>
>>>>>> Can't we write to a config file we include to the dhcpd.conf and
>>>>>> reload dhcp when the proxy did something to dhcp ?
>>>>>>
>>>>>> Ideas are welcome.
>>>>>>
>>>>>> Cheers,
>>>>>>
>>>>>> Matt
>>>>>
>>>>> --
>>>>> You received this message because you are subscribed to the Google
>>>>> Groups "Foreman users" group.
>>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>>> an email to foreman-user...@googlegroups.com.
>>>>> To post to this group, send email to forema...@googlegroups.com.
>>>>> Visit this group at https://groups.google.com/group/foreman-users.
>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>
>>>>>
>>>>> --
>>>>> Alvin Starr || voice: (905)513-7688
>>>>> Netvel Inc. || Cell: (416)806-0133
>>>>> al...@netvel.net ||
>>>>
>>>>
>>>> --
>>>> Alvin Starr || voice: (905)513-7688
>>>> Netvel Inc. || Cell: (416)806-0133
>>>> al...@netvel.net ||
>>>
>>>
>>> --
>>> Alvin Starr || voice: (905)513-7688
>>> Netvel Inc. || Cell: (416)806-0133
>>> al...@netvel.net ||
>>
>>
>> --
>> Alvin Starr || voice: (905)513-7688
>> Netvel Inc. || Cell: (416)806-0133
>> al...@netvel.net ||
>
>
> --
> Alvin Starr || voice: (905)513-7688
> Netvel Inc. || Cell: (416)806-0133
> alvin@netvel.net ||
I actually hacked up a wrapper to the /usr/bin/omshell that would write
data to multiple DHCP servers.
It worked and past my initial testing but I never got much of a chance
to implement it.
The requirement on my end for failover got eclipsed by other more
pressing problems.
I did post the script to yamakasi.014@gmail.com and I believe that he
was able to use it.
I could post it to the mail list in general if there is any interest.
···
On 02/17/2017 07:51 PM, Isabell Cowan wrote:
> Not a solution per say, but a reasonable work around. Call the
> attached script in a frequent cron job.
>
> On Monday, August 15, 2016 at 11:02:50 AM UTC-5, Alvin Starr wrote:
>
> I have looked at this a bit more and your right.
> Its hard to believe that the ISC develpers would be that short
> sighted to not extend the design so that changes made to the
> primary are copied to the secondary.
>
> I can see 3 possible solutions.
> 1) fix the ISC DHCP server.
> Fixing the DHCP server would be a major pain and there may be
> some fundamental reason that its not possible to copy the static
> entries
>
> 2) change dhcp_isc_main.rb to contact both primary and secondary
> DHCP servers.
> Looking at the code it would be possible to change the omcmd
> routine to talk to a secondary server.
> This would require adding configuration items to handle the
> secondary.
> The problem I can see here is what to do in the case of an
> error condition from one server and not the other?
>
> 3) replace omshell with a shell that writes to both servers.
> An omshell wrapper could parse the dhcpd.conf file and
> determine if there is a secondary server.
> If there is a secondary server the commands could be piped to
> both servers.
> Once again there is the issue of what to do about errors in
> one server and not the other.
> This solution would also likely require a small patch to
> dhcp_isc_main.rb to allow for changing.
>
> I could supply a patch to the dhcp_isc_main.rb and do some testing
> on my environment so that it would pass the initial sniff test but
> I am not in a position to do a full pull request and then submit
> the patches via usual developer channel.
>
>
>
>
> On 08/11/2016 06:40 PM, yamaka...@gmail.com wrote:
>> DHCP will not replicate the static leases as I said before, you
>> need twice the omapi using omshell.
>>
>> I have discussed this with the ISC guys.
>>
>>
>> Op vrijdag 12 augustus 2016 00:26:15 UTC+2 schreef Alvin Starr:
>>
>> We have slightly different problems but are both limited by
>> the nature of foremans dhcp-proxy.
>>
>> If you create static leases using omshell then I believe the
>> data will be replicated to a failover dhcp server.
>> Forman will create new hosts using omshell.
>>
>> The comment about DNS is only because foreman can cleanly
>> interact with DNS remotely.
>>
>>
>> On 08/11/2016 06:05 PM, yamaka...@gmail.com wrote:
>>> You are completely wrong.
>>>
>>> What we like to have is a second DHCP with a proxy where is
>>> talked to using OMAPI by foreman so we have a replication
>>> about the static leases.
>>>
>>> DHCP itself is unable to sync them this way and for Failover
>>> we need to have 2 writes to 2 DHCP servers which are in
>>> clutser mode.
>>>
>>> DNS is not involved here.
>>>
>>> Op donderdag 11 augustus 2016 23:50:43 UTC+2 schreef Alvin >>> Starr:
>>>
>>> A standalone DHCP server without lots of extra software
>>> installed.
>>> I do not want to install the whole forman-proxy on the
>>> DHCP or DNS servers
>>>
>>>
>>> As an asidethe isc_dhcp proxy does not parse correctly
>>> formatted dhcpd.conffiles(I just filed a bug report).
>>>
>>>
>>> Looking at omapi I could be convinced that it is
>>> impossible to get thecurrent dhcp config
>>> informationremotely.
>>>
>>>
>>> On 08/11/2016 05:26 PM, yamaka...@gmail.com wrote:
>>>> What do you mean by a standalone DHCP server ? The
>>>> proxy handles that when you installed the proxy on the
>>>> DHCP server.
>>>>
>>>> This goes about a second DHCP server that knows the
>>>> same static leases as the proxy knows for failover
>>>> whent the primary, with proxy, fails.
>>>>
>>>> Op donderdag 11 augustus 2016 22:39:40 UTC+2 schreef >>>> Alvin Starr:
>>>>
>>>> I have wondered about the same problem.
>>>> Since foreman needs to read and write the leases
>>>> and config files it means that you cannot have a
>>>> remote standalone DHCP server.
>>>>
>>>>
>>>> On 08/11/2016 04:32 PM, yamaka...@gmail.com wrote:
>>>>> Is this me or does no-one care about DHCP redundancy ?
>>>>>
>>>>>
>>>>>
>>>>> Op zaterdag 16 januari 2016 20:06:30 UTC+1 schreef >>>>> Matt .:
>>>>>
>>>>> Hi,
>>>>>
>>>>> I was wondering if someone has a workaround
>>>>> for DHCP sync with failover.
>>>>>
>>>>> As foreman writes to the leases file directly
>>>>> this is an issue for syncing.
>>>>>
>>>>> Can't we write to a config file we include to
>>>>> the dhcpd.conf and
>>>>> reload dhcp when the proxy did something to
>>>>> dhcp ?
>>>>>
>>>>> Ideas are welcome.
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Matt
>>>>>
>>>>> --
>>>>> You received this message because you are
>>>>> subscribed to the Google Groups "Foreman users" group.
>>>>> To unsubscribe from this group and stop receiving
>>>>> emails from it, send an email to
>>>>> foreman-user...@googlegroups.com.
>>>>> To post to this group, send email to
>>>>> forema...@googlegroups.com.
>>>>> Visit this group at
>>>>> https://groups.google.com/group/foreman-users.
>>>>> For more options, visit
>>>>> https://groups.google.com/d/optout.
>>>>
>>>> --
>>>> Alvin Starr || voice: (905)513-7688
>>>> Netvel Inc. || Cell: (416)806-0133
>>>> al...@netvel.net ||
>>>>
>>>
>>> --
>>> Alvin Starr || voice: (905)513-7688
>>> Netvel Inc. || Cell: (416)806-0133
>>> al...@netvel.net ||
>>>
>>
>> --
>> Alvin Starr || voice: (905)513-7688
>> Netvel Inc. || Cell: (416)806-0133
>> al...@netvel.net ||
>>
>
> --
> Alvin Starr || voice: (905)513-7688
> Netvel Inc. || Cell: (416)806-0133
> al...@netvel.net ||
>
I wouldn't mind seeing it. I'm not sure if I'd use it opposed to my
script, because if my script fails the records just don't get copied over,
rather than failing to modify the primary. But, it'd definitely test and
consider it, as it's more of a solution than my workaround.
···
On Friday, February 17, 2017 at 9:04:51 PM UTC-6, Alvin Starr wrote:
>
> I actually hacked up a wrapper to the /usr/bin/omshell that would write
> data to multiple DHCP servers.
>
> It worked and past my initial testing but I never got much of a chance to
> implement it.
>
> The requirement on my end for failover got eclipsed by other more pressing
> problems.
>
> I did post the script to yamaka...@gmail.com and I believe
> that he was able to use it.
>
> I could post it to the mail list in general if there is any interest.
>
>
>
> On 02/17/2017 07:51 PM, Isabell Cowan wrote:
>
> Not a solution per say, but a reasonable work around. Call the attached
> script in a frequent cron job.
>
> On Monday, August 15, 2016 at 11:02:50 AM UTC-5, Alvin Starr wrote:
>>
>> I have looked at this a bit more and your right.
>> Its hard to believe that the ISC develpers would be that short sighted
>> to not extend the design so that changes made to the primary are copied to
>> the secondary.
>>
>> I can see 3 possible solutions.
>> 1) fix the ISC DHCP server.
>> Fixing the DHCP server would be a major pain and there may be some
>> fundamental reason that its not possible to copy the static entries
>>
>> 2) change dhcp_isc_main.rb to contact both primary and secondary DHCP
>> servers.
>> Looking at the code it would be possible to change the omcmd routine
>> to talk to a secondary server.
>> This would require adding configuration items to handle the secondary.
>> The problem I can see here is what to do in the case of an error
>> condition from one server and not the other?
>>
>> 3) replace omshell with a shell that writes to both servers.
>> An omshell wrapper could parse the dhcpd.conf file and determine if
>> there is a secondary server.
>> If there is a secondary server the commands could be piped to both
>> servers.
>> Once again there is the issue of what to do about errors in one
>> server and not the other.
>> This solution would also likely require a small patch to dhcp_isc_main.rb
>> to allow for changing.
>>
>> I could supply a patch to the dhcp_isc_main.rb and do some testing on my
>> environment so that it would pass the initial sniff test but I am not in a
>> position to do a full pull request and then submit the patches via usual
>> developer channel.
>>
>>
>>
>>
>> On 08/11/2016 06:40 PM, yamaka...@gmail.com wrote:
>>
>> DHCP will not replicate the static leases as I said before, you need
>> twice the omapi using omshell.
>>
>> I have discussed this with the ISC guys.
>>
>>
>> Op vrijdag 12 augustus 2016 00:26:15 UTC+2 schreef Alvin Starr:
>>>
>>> We have slightly different problems but are both limited by the nature
>>> of foremans dhcp-proxy.
>>>
>>> If you create static leases using omshell then I believe the data will
>>> be replicated to a failover dhcp server.
>>> Forman will create new hosts using omshell.
>>>
>>> The comment about DNS is only because foreman can cleanly interact with
>>> DNS remotely.
>>>
>>>
>>> On 08/11/2016 06:05 PM, yamaka...@gmail.com wrote:
>>>
>>> You are completely wrong.
>>>
>>> What we like to have is a second DHCP with a proxy where is talked to
>>> using OMAPI by foreman so we have a replication about the static leases.
>>>
>>> DHCP itself is unable to sync them this way and for Failover we need to
>>> have 2 writes to 2 DHCP servers which are in clutser mode.
>>>
>>> DNS is not involved here.
>>>
>>> Op donderdag 11 augustus 2016 23:50:43 UTC+2 schreef Alvin Starr:
>>>>
>>>> A standalone DHCP server without lots of extra software installed.
>>>> I do not want to install the whole forman-proxy on the DHCP or DNS ser
>>>> vers
>>>>
>>>>
>>>> As an aside the isc_dhcp proxy does not parse correctly formatted
>>>> dhcpd.conf files(I just filed a bug report).
>>>>
>>>>
>>>> Looking at omapi I could be convinced that it is impossible to get the
>>>> current dhcp config information remotely.
>>>>
>>>>
>>>> On 08/11/2016 05:26 PM, yamaka...@gmail.com wrote:
>>>>
>>>> What do you mean by a standalone DHCP server ? The proxy handles that
>>>> when you installed the proxy on the DHCP server.
>>>>
>>>> This goes about a second DHCP server that knows the same static leases
>>>> as the proxy knows for failover whent the primary, with proxy, fails.
>>>>
>>>> Op donderdag 11 augustus 2016 22:39:40 UTC+2 schreef Alvin Starr:
>>>>>
>>>>> I have wondered about the same problem.
>>>>> Since foreman needs to read and write the leases and config files it
>>>>> means that you cannot have a remote standalone DHCP server.
>>>>>
>>>>>
>>>>> On 08/11/2016 04:32 PM, yamaka...@gmail.com wrote:
>>>>>
>>>>> Is this me or does no-one care about DHCP redundancy ?
>>>>>
>>>>>
>>>>>
>>>>> Op zaterdag 16 januari 2016 20:06:30 UTC+1 schreef Matt .:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I was wondering if someone has a workaround for DHCP sync with
>>>>>> failover.
>>>>>>
>>>>>> As foreman writes to the leases file directly this is an issue for
>>>>>> syncing.
>>>>>>
>>>>>> Can't we write to a config file we include to the dhcpd.conf and
>>>>>> reload dhcp when the proxy did something to dhcp ?
>>>>>>
>>>>>> Ideas are welcome.
>>>>>>
>>>>>> Cheers,
>>>>>>
>>>>>> Matt
>>>>>>
>>>>> --
>>>>> You received this message because you are subscribed to the Google
>>>>> Groups "Foreman users" group.
>>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>>> an email to foreman-user...@googlegroups.com.
>>>>> To post to this group, send email to forema...@googlegroups.com.
>>>>> Visit this group at https://groups.google.com/group/foreman-users.
>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>
>>>>>
>>>>> --
>>>>> Alvin Starr || voice: (905)513-7688
>>>>> Netvel Inc. || Cell: (416)806-0133al...@netvel.net ||
>>>>>
>>>>>
>>>> --
>>>> Alvin Starr || voice: (905)513-7688
>>>> Netvel Inc. || Cell: (416)806-0133al...@netvel.net ||
>>>>
>>>>
>>> --
>>> Alvin Starr || voice: (905)513-7688
>>> Netvel Inc. || Cell: (416)806-0133al...@netvel.net ||
>>>
>>>
>> --
>> Alvin Starr || voice: (905)513-7688
>> Netvel Inc. || Cell: (416)806-0133al...@netvel.net ||
>>
>>
> --
> Alvin Starr || voice: (905)513-7688
> Netvel Inc. || Cell: (416)806-0133al...@netvel.net ||
>
>
