Distributed bare metal builds using Foreman

Is there a way to run Foreman with distributed DHCP/PXE environments?

I want to use Foreman for bare metal builds. It is working great as a
single instance in my lab environment. This instance in my lab controls
all services - DHCP/TFTP, etc, which are all running on the same host.
This works for the lab, however I'm trying to figure out how to scale it.
We have dozens of datacenters which are dispersed geographically, and I
need to be able to build bare metal hosts in these locations with DHCP/PXE
as well.

Is Foreman able handle multiple DHCP/PXE servers? Is there another way to
accomplish what I'm trying to achieve? The goal is to have a single
Foreman instance which can control booting/installation of these bare metal
servers, no matter their geographic location.

Thanks.

Yes, the smart-proxy handles this. You will need a smart-proxy in each
datacenter or location to handle DHCP/TFTP. The smart-proxy will
communicate back to your main Foreman instance and allow you to provision
hosts in these remote locations.

Josh

··· On Wed, Aug 19, 2015 at 5:40 PM, Kyle Flavin wrote:

Is there a way to run Foreman with distributed DHCP/PXE environments?

I want to use Foreman for bare metal builds. It is working great as a
single instance in my lab environment. This instance in my lab controls
all services - DHCP/TFTP, etc, which are all running on the same host.
This works for the lab, however I’m trying to figure out how to scale it.
We have dozens of datacenters which are dispersed geographically, and I
need to be able to build bare metal hosts in these locations with DHCP/PXE
as well.

Is Foreman able handle multiple DHCP/PXE servers? Is there another way to
accomplish what I’m trying to achieve? The goal is to have a single
Foreman instance which can control booting/installation of these bare metal
servers, no matter their geographic location.

Thanks.


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/d/optout.

Great, thanks. I'll look into the Smartproxy.

··· On Wednesday, August 19, 2015 at 3:37:19 PM UTC-7, Josh wrote: > > Yes, the smart-proxy handles this. You will need a smart-proxy in each > datacenter or location to handle DHCP/TFTP. The smart-proxy will > communicate back to your main Foreman instance and allow you to provision > hosts in these remote locations. > > Josh > > On Wed, Aug 19, 2015 at 5:40 PM, Kyle Flavin > wrote: > >> Is there a way to run Foreman with distributed DHCP/PXE environments? >> >> I want to use Foreman for bare metal builds. It is working great as a >> single instance in my lab environment. This instance in my lab controls >> all services - DHCP/TFTP, etc, which are all running on the same host. >> This works for the lab, however I'm trying to figure out how to scale it. >> We have dozens of datacenters which are dispersed geographically, and I >> need to be able to build bare metal hosts in these locations with DHCP/PXE >> as well. >> >> Is Foreman able handle multiple DHCP/PXE servers? Is there another way >> to accomplish what I'm trying to achieve? The goal is to have a single >> Foreman instance which can control booting/installation of these bare metal >> servers, no matter their geographic location. >> >> Thanks. >> >> >> -- >> 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 http://groups.google.com/group/foreman-users. >> For more options, visit https://groups.google.com/d/optout. >> > >

Hi Josh,

how about the scalability of the configuration management part? each smart
proxy will be on puppet master, correct? or one can have more than one load
balanced smart proxy?? how many hosts one smart proxy can handle?

··· On 20 August 2015 at 01:37, Josh Baird wrote:

Yes, the smart-proxy handles this. You will need a smart-proxy in each
datacenter or location to handle DHCP/TFTP. The smart-proxy will
communicate back to your main Foreman instance and allow you to provision
hosts in these remote locations.

Josh

On Wed, Aug 19, 2015 at 5:40 PM, Kyle Flavin kyle.flavin@gmail.com > wrote:

Is there a way to run Foreman with distributed DHCP/PXE environments?

I want to use Foreman for bare metal builds. It is working great as a
single instance in my lab environment. This instance in my lab controls
all services - DHCP/TFTP, etc, which are all running on the same host.
This works for the lab, however I’m trying to figure out how to scale it.
We have dozens of datacenters which are dispersed geographically, and I
need to be able to build bare metal hosts in these locations with DHCP/PXE
as well.

Is Foreman able handle multiple DHCP/PXE servers? Is there another way
to accomplish what I’m trying to achieve? The goal is to have a single
Foreman instance which can control booting/installation of these bare metal
servers, no matter their geographic location.

Thanks.


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/d/optout.


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/d/optout.

A smart proxy may or may not contain a puppet master - for speed reasons it may be desirable to have a puppet master on each smart proxy and keep traffic local to each datacenter you can separate out the functionality and have two smart proxies per DC one for Puppet and one for builds but until your thinking of 4k+ hosts per DC I am not sure what this would buy you other than more servers to manage. I have heard anecdotal evidence that a single foreman server scales to 5000+ hosts

YMMV

Luke

··· > On Aug 23, 2015, at 2:09 AM, Walid wrote: > > Hi Josh, > > how about the scalability of the configuration management part? each smart proxy will be on puppet master, correct? or one can have more than one load balanced smart proxy?? how many hosts one smart proxy can handle? > > On 20 August 2015 at 01:37, Josh Baird wrote: > Yes, the smart-proxy handles this. You will need a smart-proxy in each datacenter or location to handle DHCP/TFTP. The smart-proxy will communicate back to your main Foreman instance and allow you to provision hosts in these remote locations. > > Josh > > On Wed, Aug 19, 2015 at 5:40 PM, Kyle Flavin wrote: > Is there a way to run Foreman with distributed DHCP/PXE environments? > > I want to use Foreman for bare metal builds. It is working great as a single instance in my lab environment. This instance in my lab controls all services - DHCP/TFTP, etc, which are all running on the same host. This works for the lab, however I'm trying to figure out how to scale it. We have dozens of datacenters which are dispersed geographically, and I need to be able to build bare metal hosts in these locations with DHCP/PXE as well. > > Is Foreman able handle multiple DHCP/PXE servers? Is there another way to accomplish what I'm trying to achieve? The goal is to have a single Foreman instance which can control booting/installation of these bare metal servers, no matter their geographic location. > > Thanks. >