provisioning interface is private - how to assign a routed IP?

Hi,

I'm trying to setup the foreman on my home network, with VMWare Fusion Pro.

I've created an additional private network in Fusion that doesn't use DHCP.

I've created a VM with the first interface being in my LAN and the 2nd interface being in the provisioning net.
The VM PXE-boots from the foreman-server (really the smart-proxy, I imagine, but it's on the same host).

However, because it's private it can't download the installer-image etc.pp.

I setup a 2nd network (the LAN my router hands out), but I'm not sure how to tell the foreman that the DHCP of my router should assign IPs and it shouldn't do anything.
I also failed to set IPs manually.

In a real-world scenario, one would probably have a mirror reachable from the provisioning network, but I'm just getting started.

The documentation is a bit sparse on this kind of setup - though I imagine it's not too uncommon.

How would I configure this setup (1st interface=DHCP from router, 2nd interface=DHCP from foreman/smart-proxy)?

Hello,

you are doing it right. And yes, the general advice is to setup mirror
(Katello/Pulp backend can help you with that a lot if you use RPMs and
there's plugin for SUSE), or you can mirror manually.

Now, Foreman is able to configure two or more ifaces, you pick one as
primary which holds the default route, then you pick one as
provisioning and that's the one you will be booting from (PXE/DHCP).

Now, the problem is how installer behaves in this setup - this might
be different for Red Hats, Debians and SUSE, I have experience with
Red Hat and in that case the 1st (primary) interface is not used until
you do firstboot, thus you need to route IP packets to your
installation source or have mirror, because our PXELinux templates
allows you to configure only one interface. But Anaconda supports
more, you need to tune our templates and provide all interfaces via
kernel command line. This will be similar in other OSes.

If you test this setup, please file a patch to our community-templates
so others can use it. But it's pretty non-standard setup, as I
explained above. Your provisioning network should be capable of doing
things from start to the finish.

LZ

···

On Mon, Dec 18, 2017 at 12:44 AM, <rainer@ultra-secure.de> wrote:

Hi,

I'm trying to setup the foreman on my home network, with VMWare Fusion Pro.

I've created an additional private network in Fusion that doesn't use DHCP.

I've created a VM with the first interface being in my LAN and the 2nd
interface being in the provisioning net.
The VM PXE-boots from the foreman-server (really the smart-proxy, I imagine,
but it's on the same host).

However, because it's private it can't download the installer-image etc.pp.

I setup a 2nd network (the LAN my router hands out), but I'm not sure how to
tell the foreman that the DHCP of my router should assign IPs and it
shouldn't do anything.
I also failed to set IPs manually.

In a real-world scenario, one would probably have a mirror reachable from
the provisioning network, but I'm just getting started.

The documentation is a bit sparse on this kind of setup - though I imagine
it's not too uncommon.

How would I configure this setup (1st interface=DHCP from router, 2nd
interface=DHCP from foreman/smart-proxy)?

--
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.

--
Later,
  Lukas @lzap Zapletal

OK, I'll see what I can do.

I use CentOS and I really wanted to avoid having to setup a local mirror for it - my setup lives on my (somewhat nimble) local SSD...

Thanks.

Rainer

···

Am 2017-12-18 10:21, schrieb Lukas Zapletal:

Hello,

you are doing it right. And yes, the general advice is to setup mirror
(Katello/Pulp backend can help you with that a lot if you use RPMs and
there's plugin for SUSE), or you can mirror manually.

Now, Foreman is able to configure two or more ifaces, you pick one as
primary which holds the default route, then you pick one as
provisioning and that's the one you will be booting from (PXE/DHCP).

Now, the problem is how installer behaves in this setup - this might
be different for Red Hats, Debians and SUSE, I have experience with
Red Hat and in that case the 1st (primary) interface is not used until
you do firstboot, thus you need to route IP packets to your
installation source or have mirror, because our PXELinux templates
allows you to configure only one interface. But Anaconda supports
more, you need to tune our templates and provide all interfaces via
kernel command line. This will be similar in other OSes.

If you test this setup, please file a patch to our community-templates
so others can use it. But it's pretty non-standard setup, as I
explained above. Your provisioning network should be capable of doing
things from start to the finish.

You mirror does not need to be on the Foreman instance, just somewhere
on the provisioning network or nearby (routed).

You can try to configure 2nd interface via Anaconda options, this is
possible. Note CentOS 6 and 7 PXELinux syntax differs a lot, take care
and use documentation.

Good luck!

···

On Mon, Dec 18, 2017 at 10:49 AM, <rainer@ultra-secure.de> wrote:

Am 2017-12-18 10:21, schrieb Lukas Zapletal:

Hello,

you are doing it right. And yes, the general advice is to setup mirror
(Katello/Pulp backend can help you with that a lot if you use RPMs and
there's plugin for SUSE), or you can mirror manually.

Now, Foreman is able to configure two or more ifaces, you pick one as
primary which holds the default route, then you pick one as
provisioning and that's the one you will be booting from (PXE/DHCP).

Now, the problem is how installer behaves in this setup - this might
be different for Red Hats, Debians and SUSE, I have experience with
Red Hat and in that case the 1st (primary) interface is not used until
you do firstboot, thus you need to route IP packets to your
installation source or have mirror, because our PXELinux templates
allows you to configure only one interface. But Anaconda supports
more, you need to tune our templates and provide all interfaces via
kernel command line. This will be similar in other OSes.

If you test this setup, please file a patch to our community-templates
so others can use it. But it's pretty non-standard setup, as I
explained above. Your provisioning network should be capable of doing
things from start to the finish.

OK, I'll see what I can do.

I use CentOS and I really wanted to avoid having to setup a local mirror for
it - my setup lives on my (somewhat nimble) local SSD...

Thanks.

Rainer

--
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.

--
Later,
  Lukas @lzap Zapletal