I am quite new to foreman and am yet to install and start using the same. I
am planning to use foreman in datacenter environment with multiple
customers and assets on cloud as well as well physical setup.
Atleast to start with evaluation I am planning to use the following h.w
8 GB RAM
CPU - 4 cores
2 NICs…
Now I understand that I will be using one NIC for internet traffic and
other nic to connect to the host that I need to provision. Now what should
be the ideal architecture wherein all the bare-metal hosts placed in
different racks in the DC come to the foreman server for provisioning… do
I need to extend the cable from the second nic to each and every switch in
my DC ?
I understand my question might sound silly but would be really grateful if
someone can confirm
Hardware & network config.
How to scale to multiple foreman servers.
How to reach out to all bare metal hosts in the DC so that they can
install from my foreman server.
Your correct it is silly, If your hosts are all on the same backend VLAN then you’re good to go, if not then explore trunking in the necessary VLAN’s to your foreman host. Be sure to include dhcp helper configs to your switches.
your hardware spec looks fine
not sure why you would want more than one foreman host - you ought to investigate proxies
see above
Cheers
···
On Sep 9, 2014, at 8:30 PM, Rakesh Kathpal wrote:
Hi,
I am quite new to foreman and am yet to install and start using the same. I am planning to use foreman in datacenter environment with multiple customers and assets on cloud as well as well physical setup.
Atleast to start with evaluation I am planning to use the following h.w
8 GB RAM
CPU - 4 cores
2 NICs…
Now I understand that I will be using one NIC for internet traffic and other nic to connect to the host that I need to provision. Now what should be the ideal architecture wherein all the bare-metal hosts placed in different racks in the DC come to the foreman server for provisioning… do I need to extend the cable from the second nic to each and every switch in my DC ?
I understand my question might sound silly but would be really grateful if someone can confirm
Hardware & network config.
How to scale to multiple foreman servers.
How to reach out to all bare metal hosts in the DC so that they can install from my foreman server.
As Luke mentioned, there is no need to have multiple NICs in most
environments. If you have something (ie, a router) that is routing between
your various networks for you, all you typically need are DHCP helpers
configured.
Josh
···
On Tue, Sep 9, 2014 at 7:58 AM, Luke Kearney wrote:
I am quite new to foreman and am yet to install and start using the
same. I am planning to use foreman in datacenter environment with multiple
customers and assets on cloud as well as well physical setup.
Atleast to start with evaluation I am planning to use the following h.w
8 GB RAM
CPU - 4 cores
2 NICs…
Now I understand that I will be using one NIC for internet traffic and
other nic to connect to the host that I need to provision. Now what should
be the ideal architecture wherein all the bare-metal hosts placed in
different racks in the DC come to the foreman server for provisioning… do
I need to extend the cable from the second nic to each and every switch in
my DC ?
I understand my question might sound silly but would be really grateful
if someone can confirm
Hardware & network config.
How to scale to multiple foreman servers.
How to reach out to all bare metal hosts in the DC so that they can
install from my foreman server.
Your correct it is silly, If your hosts are all on the same backend VLAN
then you’re good to go, if not then explore trunking in the necessary
VLAN’s to your foreman host. Be sure to include dhcp helper configs to your
switches.
your hardware spec looks fine
not sure why you would want more than one foreman host - you ought to
investigate proxies
···
On Tue, Sep 9, 2014 at 5:33 PM, Josh Baird wrote:
As Luke mentioned, there is no need to have multiple NICs in most
environments. If you have something (ie, a router) that is routing between
your various networks for you, all you typically need are DHCP helpers
configured.
Josh
On Tue, Sep 9, 2014 at 7:58 AM, Luke Kearney luke@kearney.jp wrote:
I am quite new to foreman and am yet to install and start using the
same. I am planning to use foreman in datacenter environment with multiple
customers and assets on cloud as well as well physical setup.
Atleast to start with evaluation I am planning to use the following h.w
8 GB RAM
CPU - 4 cores
2 NICs…
Now I understand that I will be using one NIC for internet traffic and
other nic to connect to the host that I need to provision. Now what should
be the ideal architecture wherein all the bare-metal hosts placed in
different racks in the DC come to the foreman server for provisioning… do
I need to extend the cable from the second nic to each and every switch in
my DC ?
I understand my question might sound silly but would be really grateful
if someone can confirm
Hardware & network config.
How to scale to multiple foreman servers.
How to reach out to all bare metal hosts in the DC so that they can
install from my foreman server.
Your correct it is silly, If your hosts are all on the same backend VLAN
then you’re good to go, if not then explore trunking in the necessary
VLAN’s to your foreman host. Be sure to include dhcp helper configs to your
switches.
your hardware spec looks fine
not sure why you would want more than one foreman host - you ought to
investigate proxies
