On 11/25/2014 05:38 AM, Nathanaël Blanchet wrote:
I already manage a first engine and I'm about to deploy a second engine
to an other site.
I have thought about several possibilities:
* create a new independant engine on the future site
* create a second datacenter in the first engine so that all my vms
are aggregated in a same place and contact hosts with public
addresses (hum...) or via a vpn.
* the last one is a question : like centreon does with monitoring, is
there a way to use the first engine as a master (or central) and the
second or many other ones as poller/satellite which are supposed to
deal locally with hosts?
This architecture is interesting because the workload is reparted
between several engines and once link is needed between poller and
central. More, all my vms are shown in the same ui.
Can someone give me his point of view about this?
Users mailing list
no nesting of engines. you can manage a remote cluster from a single
engine, or deploy 2 engines.
take a look at ManageIQ for orchestrating/monitoring across multiple