I'm new to Foreman and only slightly less new with Puppet.
I've successfully installed Foreman.
Smart proxy seems to be working.
Facts for my foreman host machine successfully imported into foreman.
My foreman host has two ethernet interfaces.
eth0 sits on 192.168.53/24.
I would like foreman to manage DHCP on the 192.168.53 network so I've
enabled DHCP in the proxy and used the install command seen below.
eth1 sits on 172.20/16.
I'd like the DHCP to also serve requests in the 172.20 subnet AND only
respond to tftp/PXE boot requests in the 172.20 subnet but not in the
192.168.53 subnet.
Is there any way to specify multiple subnets on the install command?
After the initial install, I'm a little confused regarding when I should
be mucking with foreman configuration versus puppet configuration versus
hand-editing files to effect changes.
In particular, in this case, where and how should I define the additional
172.20 subnet? The foreman web interface has "More/Provisioning/Subnets"
which looks like a place to define additional subnets but I was puzzled
when I went to that screen that the original 192.168.53 subnet defined
during installation did not show up there – so thought that might not
represent what I think it should represent.
And, finally, maybe not exactly a foreman question, but how and where do
I configure the DHCP to only PXE/tftp in the 172.20 subnet and not the
192.168.53 subnet?
I'm trying to move past that "now what" feeling after the install. The
goal is to be able to PXE boot / install bare-metal servers which do have
BMC modules. I've enabled BMC in the proxy but have seen no screens in the
web interface that have any fields corresponding to the BMC (ip address,
username, password). Where do the BMC parameters manifest themselves? How
do I associate them with a host? I didn't see the fields in any of the
templates but may just have not looked hard enough yet.
>
> I'm new to Foreman and only slightly less new with Puppet.
I'm in the same position, so lets see if we can help each other
>
> I've successfully installed Foreman.
> Smart proxy seems to be working.
> Facts for my foreman host machine successfully imported into foreman.
>
> My foreman host has two ethernet interfaces.
>
> eth0 sits on 192.168.53/24.
> I would like foreman to manage DHCP on the 192.168.53 network so I've
> enabled DHCP in the proxy and used the install command seen below.
>
> eth1 sits on 172.20/16.
>
I have more ambitious plans, 2 or 3 more interfaces but the way it
should work is the same, going from 1 to 2 is the hard part.
> I'd like the DHCP to also serve requests in the 172.20 subnet AND only
> respond to tftp/PXE boot requests in the 172.20 subnet but not in the
> 192.168.53 subnet.
>
> 1) Is there any way to specify multiple subnets on the install command?
>
> 2) After the initial install, I'm a little confused regarding when I
> should be mucking with foreman configuration versus puppet
> configuration versus hand-editing files to effect changes.
> In particular, in this case, where and how should I define the
> additional 172.20 subnet? The foreman web interface has
> "More/Provisioning/Subnets" which looks like a place to define
> additional subnets but I was puzzled when I went to that screen that
> the original 192.168.53 subnet defined during installation did not
> show up there – so thought that might not represent what I think it
> should represent.
>
What I did during a previous test was to add networks to dhcpd.conf and
then import subnets.
> 3) And, finally, maybe not exactly a foreman question, but how and
> where do I configure the DHCP to only PXE/tftp in the 172.20 subnet
> and not the 192.168.53 subnet?
probably the tftp conf but I need to find that out too.
>
> 4) I'm trying to move past that "now what" feeling after the
> install. The goal is to be able to PXE boot / install bare-metal
> servers which do have BMC modules. I've enabled BMC in the proxy but
> have seen no screens in the web interface that have any fields
> corresponding to the BMC (ip address, username, password). Where do
> the BMC parameters manifest themselves? How do I associate them with a
> host? I didn't see the fields in any of the templates but may just
> have not looked hard enough yet.
Suggestion from #theforeman was to use the puppet modules which the
installer used, in foreman. That is what I'm currently trying out but
since I'm new to puppet I have some problems with the various concepts
that either build on each other or complement each other or just plain
have nothing todo with each other.
One extra thing I would like to accomplish is to have DNS in the mix
were each subnet corresponds to a different zone. I have got
development/test/accept/prod network (vlan) and zones which would map
back to foreman/puppet envs. So does someone have THE recipe to set this
up? Please wikify it
For one dhcp server on multiple subnet you can set dhcp relay to your
foreman server on your switch.
So only one nic interface is needed.
Xiaofei
锟斤拷 2013/10/16 3:32, Arnold Itterate wrote:
···
>
> I'm new to Foreman and only slightly less new with Puppet.
>
> I've successfully installed Foreman.
> Smart proxy seems to be working.
> Facts for my foreman host machine successfully imported into foreman.
>
> My foreman host has two ethernet interfaces.
>
> eth0 sits on 192.168.53/24.
> I would like foreman to manage DHCP on the 192.168.53 network so I've
> enabled DHCP in the proxy and used the install command seen below.
>
> eth1 sits on 172.20/16.
>
> I'd like the DHCP to also serve requests in the 172.20 subnet AND only
> respond to tftp/PXE boot requests in the 172.20 subnet but not in the
> 192.168.53 subnet.
>
> 1) Is there any way to specify multiple subnets on the install command?
>
> 2) After the initial install, I'm a little confused regarding when I
> should be mucking with foreman configuration versus puppet
> configuration versus hand-editing files to effect changes.
> In particular, in this case, where and how should I define the
> additional 172.20 subnet? The foreman web interface has
> "More/Provisioning/Subnets" which looks like a place to define
> additional subnets but I was puzzled when I went to that screen that
> the original 192.168.53 subnet defined during installation did not
> show up there -- so thought that might not represent what I think it
> should represent.
>
> 3) And, finally, maybe not exactly a foreman question, but how and
> where do I configure the DHCP to only PXE/tftp in the 172.20 subnet
> and not the 192.168.53 subnet?
>
> 4) I'm trying to move past that "now what" feeling after the install.
> The goal is to be able to PXE boot / install bare-metal servers which
> do have BMC modules. I've enabled BMC in the proxy but have seen no
> screens in the web interface that have any fields corresponding to the
> BMC (ip address, username, password). Where do the BMC parameters
> manifest themselves? How do I associate them with a host? I didn't see
> the fields in any of the templates but may just have not looked hard
> enough yet.
>
>
> My install configuration:
>
> foreman-installer \
> --enable-foreman \
> --enable-puppet \
> --enable-foreman-proxy \
> --foreman-proxy-tftp=true \
> --foreman-proxy-bmc=true
> --foreman-proxy-dhcp=true \
> --foreman-proxy-dhcp-gateway=192.168.53.1 \
> --foreman-proxy-dhcp-range="192.168.53.2 192.168.53.100" \
> --foreman-proxy-dhcp-nameservers="192.168.51.200,192.168.51.201"
>
>
> Thanks in advance for any and all help,
>
> Arnold
>
> --
> 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 http://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/groups/opt_out.
