At the end of the post, I am giving an advice to turn off DHCP puppet
management so new declarations won't get overwritten as our puppet
modules (or installer not sure) do not support multiple declarations.
But when I edit foreman-installer answer files, it does not work
actually. I tried to do this via foreman-installer switches (changed
the blog post) to:
This seemed to work but I was fooled, I was running with dry run and
we have a bug that the installer actually commits some changes (!!!)
so it is actually not working at all and I had to fix my instance
after this screwup.
Now the question is - how the heck do I stop puppet or our installer
from modifying dhcpd.conf? Can someone tell me please so I can change
the post once again? I spent an hour trying to figure out.
I think this is the wrong approach and it's better to make the installer
set up the zones for you. While sadly we don't expose this option in the
installer, we can use hiera by placing the following content in
/etc/foreman-installer/custom-hiera.yaml:
Now if you re-run the installer you should get an additional subnet.
Sadly this is not possible for DNS but we could add that support.
···
On Tue, Aug 01, 2017 at 01:08:14PM +0200, Lukas Zapletal wrote:
>I wrote a short blogpost about how to add new DHCP subnet to Foreman:
>
>https://theforeman.org/2017/07/adding-new-subnet-for-provisioning.html
>
>At the end of the post, I am giving an advice to turn off DHCP puppet
>management so new declarations won't get overwritten as our puppet
>modules (or installer not sure) do not support multiple declarations.
>
>But when I edit foreman-installer answer files, it does not work
>actually. I tried to do this via foreman-installer switches (changed
>the blog post) to:
>
># foreman-installer -v -n --scenario katello \
>--foreman-proxy-dns=true --foreman-proxy-dns-managed=false \
>--foreman-proxy-dhcp=true --foreman-proxy-dhcp-managed=false
>
>This seemed to work but I was fooled, I was running with dry run and
>we have a bug that the installer actually commits some changes (!!!)
>so it is actually not working at all and I had to fix my instance
>after this screwup.
>
>Now the question is - how the heck do I stop puppet or our installer
>from modifying dhcpd.conf? Can someone tell me please so I can change
>the post once again? I spent an hour trying to figure out.
If anyone can take a look, this has been pain for a very long time.
Now, what workaround do you recommend for DNS today? How to
essentially stop updating it with our installer?
LZ
···
On Thu, Aug 10, 2017 at 5:48 PM, Ewoud Kohl van Wijngaarden wrote:
> On Tue, Aug 01, 2017 at 01:08:14PM +0200, Lukas Zapletal wrote:
>>
>> I wrote a short blogpost about how to add new DHCP subnet to Foreman:
>>
>> https://theforeman.org/2017/07/adding-new-subnet-for-provisioning.html
>>
>> At the end of the post, I am giving an advice to turn off DHCP puppet
>> management so new declarations won't get overwritten as our puppet
>> modules (or installer not sure) do not support multiple declarations.
>>
>> But when I edit foreman-installer answer files, it does not work
>> actually. I tried to do this via foreman-installer switches (changed
>> the blog post) to:
>>
>> # foreman-installer -v -n --scenario katello \
>> --foreman-proxy-dns=true --foreman-proxy-dns-managed=false \
>> --foreman-proxy-dhcp=true --foreman-proxy-dhcp-managed=false
>>
>> This seemed to work but I was fooled, I was running with dry run and
>> we have a bug that the installer actually commits some changes (!!!)
>> so it is actually not working at all and I had to fix my instance
>> after this screwup.
>>
>> Now the question is - how the heck do I stop puppet or our installer
>> from modifying dhcpd.conf? Can someone tell me please so I can change
>> the post once again? I spent an hour trying to figure out.
>
>
> I think this is the wrong approach and it's better to make the installer set
> up the zones for you. While sadly we don't expose this option in the
> installer, we can use hiera by placing the following content in
> /etc/foreman-installer/custom-hiera.yaml:
>
> dhcp::pools:
> isolated.lan:
> network: 192.168.99.0
> mask: 255.255.255.0
> gateway: 192.168.99.1
> range: 192.168.99.5 192.168.99.49
>
> Now if you re-run the installer you should get an additional subnet.
>
> Sadly this is not possible for DNS but we could add that support.
>
> --
> You received this message because you are subscribed to the Google Groups
> "foreman-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to foreman-dev+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>Now, what workaround do you recommend for DNS today? How to
>essentially stop updating it with our installer?
I expect --foreman-proxy-dns-managed=false to do exactly what you want
so it surprises me this doesn't work. I've tried it locally and I can
add things to /etc/named/zones.conf without it being overwritten.
···
On Fri, Aug 11, 2017 at 08:25:56AM +0200, Lukas Zapletal wrote:
At the end of the post, I am giving an advice to turn off DHCP puppet
management so new declarations won’t get overwritten as our puppet
modules (or installer not sure) do not support multiple declarations.
But when I edit foreman-installer answer files, it does not work
actually. I tried to do this via foreman-installer switches (changed
the blog post) to:
This seemed to work but I was fooled, I was running with dry run and
we have a bug that the installer actually commits some changes (!!!)
so it is actually not working at all and I had to fix my instance
after this screwup.
Now the question is - how the heck do I stop puppet or our installer
from modifying dhcpd.conf? Can someone tell me please so I can change
the post once again? I spent an hour trying to figure out.
I think this is the wrong approach and it’s better to make the installer set
up the zones for you. While sadly we don’t expose this option in the
installer, we can use hiera by placing the following content in
/etc/foreman-installer/custom-hiera.yaml:
For me, it is actually turning off DHCP smart proxy module (setting it
to false). I was testing this with Katello 3.4.
The only difference could be that I was performing this via installer
with -n (dry run) option.
LZ
···
On Fri, Aug 11, 2017 at 4:45 PM, Ewoud Kohl van Wijngaarden wrote:
> On Fri, Aug 11, 2017 at 08:25:56AM +0200, Lukas Zapletal wrote:
>>
>> Thanks, created http://projects.theforeman.org/issues/20555
>>
>> If anyone can take a look, this has been pain for a very long time.
>
>
> https://github.com/theforeman/puppet-dns/pull/95
>
>> Now, what workaround do you recommend for DNS today? How to
>> essentially stop updating it with our installer?
>
>
> I expect --foreman-proxy-dns-managed=false to do exactly what you want so it
> surprises me this doesn't work. I've tried it locally and I can add things
> to /etc/named/zones.conf without it being overwritten.
>
>
>> LZ
>>
>> On Thu, Aug 10, 2017 at 5:48 PM, Ewoud Kohl van Wijngaarden >> wrote:
>>>
>>> On Tue, Aug 01, 2017 at 01:08:14PM +0200, Lukas Zapletal wrote:
>>>>
>>>>
>>>> I wrote a short blogpost about how to add new DHCP subnet to Foreman:
>>>>
>>>> https://theforeman.org/2017/07/adding-new-subnet-for-provisioning.html
>>>>
>>>> At the end of the post, I am giving an advice to turn off DHCP puppet
>>>> management so new declarations won't get overwritten as our puppet
>>>> modules (or installer not sure) do not support multiple declarations.
>>>>
>>>> But when I edit foreman-installer answer files, it does not work
>>>> actually. I tried to do this via foreman-installer switches (changed
>>>> the blog post) to:
>>>>
>>>> # foreman-installer -v -n --scenario katello \
>>>> --foreman-proxy-dns=true --foreman-proxy-dns-managed=false \
>>>> --foreman-proxy-dhcp=true --foreman-proxy-dhcp-managed=false
>>>>
>>>> This seemed to work but I was fooled, I was running with dry run and
>>>> we have a bug that the installer actually commits some changes (!!!)
>>>> so it is actually not working at all and I had to fix my instance
>>>> after this screwup.
>>>>
>>>> Now the question is - how the heck do I stop puppet or our installer
>>>> from modifying dhcpd.conf? Can someone tell me please so I can change
>>>> the post once again? I spent an hour trying to figure out.
>>>
>>>
>>>
>>> I think this is the wrong approach and it's better to make the installer
>>> set
>>> up the zones for you. While sadly we don't expose this option in the
>>> installer, we can use hiera by placing the following content in
>>> /etc/foreman-installer/custom-hiera.yaml:
>>>
>>> dhcp::pools:
>>> isolated.lan:
>>> network: 192.168.99.0
>>> mask: 255.255.255.0
>>> gateway: 192.168.99.1
>>> range: 192.168.99.5 192.168.99.49
>>>
>>> Now if you re-run the installer you should get an additional subnet.
>>>
>>> Sadly this is not possible for DNS but we could add that support.
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "foreman-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to foreman-dev+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
