Hi,
Is there an a way how to setup multiple Foreman servers using only parts of
central Foreman server configuration? Central foreman server would have
all information about hosts (A,B,C ) , hostgroups (DC1,DC2,DC3 etc.),
subnets ( vlan1, vlan2, vlan3 etc.) . On the other Foreman server I would
have only part of the configuration - host A, hostgroup DC1 and subnet
vlan1, a proxy of course.
Would it be possible to build such a distributed setup?
Thanks,
Marek
Hey Marek,
> Is there an a way how to setup multiple Foreman servers using only parts of
> central Foreman server configuration? Central foreman server would have
> all information about hosts (A,B,C ) , hostgroups (DC1,DC2,DC3 etc.),
> subnets ( vlan1, vlan2, vlan3 etc.) . On the other Foreman server I would
> have only part of the configuration - host A, hostgroup DC1 and subnet
> vlan1, a proxy of course.
I haven't seen such a configuration, but that does not mean it is not
possible. Edge case is to run two separate Foreman instances on separate
networks, that is possible of course.
Although foreman-proxies are stateless in a sense that they do not have
a dedicated database, if you try to share them among multiple Foreman
instances you will likely run into issues when somebody deletes on a
wrong Foreman instance.
Each Foreman has it's very own database and there is no way to share the
information. We do support HA setups tho.
> Would it be possible to build such a distributed setup?
So it could be possible, but I don't recommend this. Foreman does its
best when deployed centrally. You can have multiple sites (datacenters)
across the world managed by the single instance. All you need is to
tunnel https connections for foreman-proxy communication.
> Hi,
>
> Is there an a way how to setup multiple Foreman servers using only parts
> of central Foreman server configuration? Central foreman server would
> have all information about hosts (A,B,C ) , hostgroups (DC1,DC2,DC3 etc.),
> subnets ( vlan1, vlan2, vlan3 etc.) . On the other Foreman server I would
> have only part of the configuration - host A, hostgroup DC1 and subnet
> vlan1, a proxy of course.
> Would it be possible to build such a distributed setup?
>
>
that is indeed very interesting approach, which sadly we don't support at
the moment, but in order to reflect on this, would you mind sharing the
reasoning, or actual requirements you have?
Ohad
Thanks,
Marek
–
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.
Hi Ohad and Lukas,
Thanks for your reply. In our setup it might happen the remote data center
won't be accessible all the time. Ideal case would be if we can still be
able to reinstall servers without the need of central Foreman server. Is
there any easier way in doing this?
Thanks,
Marek
Hey Marek,
Is there an a way how to setup multiple Foreman servers using only parts
of
central Foreman server configuration? Central foreman server would have
all information about hosts (A,B,C ) , hostgroups (DC1,DC2,DC3 etc.),
subnets ( vlan1, vlan2, vlan3 etc.) . On the other Foreman server I would
have only part of the configuration - host A, hostgroup DC1 and subnet
vlan1, a proxy of course.I haven’t seen such a configuration, but that does not mean it is not
possible. Edge case is to run two separate Foreman instances on separate
networks, that is possible of course.Although foreman-proxies are stateless in a sense that they do not have
a dedicated database, if you try to share them among multiple Foreman
instances you will likely run into issues when somebody deletes on a
wrong Foreman instance.Each Foreman has it’s very own database and there is no way to share the
information. We do support HA setups tho.Would it be possible to build such a distributed setup?
So it could be possible, but I don’t recommend this. Foreman does its
best when deployed centrally. You can have multiple sites (datacenters)
across the world managed by the single instance. All you need is to
tunnel https connections for foreman-proxy communication.–
Later,
Lukas #lzap Zapletal–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/c_zrSkisOPY/unsubscribe.
To unsubscribe from this group and all its topics, 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.
> Thanks for your reply. In our setup it might happen the remote data center
> won't be accessible all the time. Ideal case would be if we can still be
> able to reinstall servers without the need of central Foreman server. Is
> there any easier way in doing this?
I am afraid you can't achieve this with Foreman currently. Distributed
Foreman is something against what we are trying to achieve (one
instance, multiple on-line datacenters).
What kind of datacenter is this? A dial-up branch office or something?
If you want to use Foreman, I recommend you to install one instance and
create some kind of workaround for off-line situations.
Do you want to PXE boot systems, or spawn image-based VMs?