| Table of Contents |
|---|
...
| Table of Contents |
|---|
Configure discovery manager checks
The Abiquo Discover Manager (or node collectorNARS) is an Abiquo remote service. The Abiquo Infrastructure check verifies the platform infrastructure at intervals. It does this by connecting to all of the hypervisors on all of the Abiquo racks and all of the public cloud regions, and their virtual machinesVMs, to compare them against the information recorded in the Abiquo database.
It checks the following components of physical machines:
Virtual CPU
RAM
NICS
Datastores
Initiator IQN
Any changes are recorded in the Abiquo database.
You can configure the node collector discovery manager as described below using the Abiquo Configuration Propertiesconfiguration properties for nars
Multiple
...
threads
The Abiquo Discovery Manager launches multiple threads in parallel. Each thread has a pool of plugin-clients. Each plugin-client connection checks different machines in the infrastructure. You can configure the number of threads with the abiquo.nodecollector.infcheck.threads propertyplugin-clients with Abiquo properties. This number should be related to the number of cores of the machine server that is running discovery manager service. The default is 5 threads.
...
Discarded machines
If a physical machine does not respond within the timeout period, Abiquo will
- mark the machine as a candidate for HA, if Abiquo HA is enabled on the rack OR
- discard the machine
The default timeout for the infrastructure check is 5 minutes (30000 milliseconds).
You can configure the timeout with the abiquo.nodecollector.infcheck.timeout property.
Discarded Machines
If a machine cannot be contacted within the timeout period, and HA is not enabled, it is discarded by the infrastructure check. Machines that are discarded are : logged in the Abiquo logs (
...
NARS and
...
Catalina.out) with the message
...
not checked again.
Maximum
...
duration
The maximum duration of the infrastructure check is the same as the infrastructure check timeout value.
Delay
...
between checks
After the check has completed, the Discovery Manager waits for the delay period before starting a new check. You can set the delay with the abiquo.nodecollector.infcheck property. The Abiquo properties. The default delay period is 5 minutes.
Check
...
frequency
The time between checks is equal to the duration of the check plus the delay between checks. Therefore So you may be able to increase the frequency of the infrastructure checks by decreasing the timeout value.
...
Configure
...
Abiquo High Availability is triggered after a certain number of failed infrastructure checks on a machine. You can configure the number of failed infrastructure checks to wait before starting HA using the abiquo.ha.infcheck.cycles property.
Note that the abiquo.ha.check.delay is the delay between checks of machines that already have HA in progress in order to determine if HA movements are complete.
...
virtual system monitor for public cloud
To ensure performance and scalability of the remote services in managing many public cloud regions, Abiquo introduced the following properties to tune the virtual system monitor
...
abiquo.vsm.pollingfrequency.<cloudprovider>
...
(VSM remote service).
Polling frequency per cloud provider
You can configure the delay between VSM polling of virtual machines in milliseconds in a cloud provider plugin
...
with the abiquo.vsm.
...
pollingfrequency.<cloudprovider>The property.
VM sync frequency per cloud provider
You can configure the delay between virtual machine synchronizer operations in milliseconds in a cloud provider plugin with the abiquo.vsm.vmsyncfrequency.
...
<cloudprovider>property.
Actor creation
...
delay
...
You can configure the delay in milliseconds added between the creation of actors for a cloud provider plugin type on VSM startup with the abiquo.vsm.actor.creation.delay.<cloudprovider> property.
Abiquo
...
SaaS example
The values An example of values that could be used in the Abiquo anyCloud system are as followsa SaaS system.
| Code Block |
|---|
abiquo.vsm.pollingfrequency.amazon = 600000 abiquo.vsm.vmsyncfrequency.amazon = 300000 abiquo.vsm.actor.creation.delay.amazon = 2500 |
...