Feature #261

Configurable VM & Host Monitoring

Added by Ruben S. Montero over 10 years ago. Updated over 10 years ago.

Status:ClosedStart date:06/12/2010
Priority:NormalDue date:
Assignee:Carlos Martín% Done:

90%

Category:Core & System
Target version:Release 2.0
Resolution:fixed Pull request:

Description

For large-scale deployments monitoring can impose too much overhead and slow the responsiveness of the system in terms of time-to-deploy of VMs. Additionally the alternative driver backend is able to do monitoring in a pull mode (i.e actions are notified by the workernodes). This can relax the intervals in the core.

The ticket will add the following configuration parameters

1.- Max number of hosts & VMs per monitoring interval
2.- Disable Host/VM monitoring

Associated revisions

Revision 37f8c0d4
Added by Carlos Martín over 10 years ago

feature #261: Added support for limiting the number of VMs processed per monitoring interval.

Revision d175a078
Added by Ruben S. Montero over 10 years ago

feature #261: Moved host_limit to the information manager to ease configuratio

Revision 3ca2d5c7
Added by Ruben S. Montero over 10 years ago

feature #261: VM_POLLING_INTERVAL set to 0 disables VM monitoring

Revision 8ac4bb43
Added by Ruben S. Montero over 10 years ago

feature #261: Monitor VMs for the first time

Revision 9b25efef
Added by Ruben S. Montero over 10 years ago

feature #261: Do not wait HOST_MONITOR_INTERVAL to monitor a host the first time

Revision 343fd218
Added by John Noss over 3 years ago

fix libvirt network filter for vrouter IPs (#261)

This adds VROUTER_IP, if present, to the libvirt network filter; without
this traffic from the vrouter IP is blocked by ebtables if using the
libvirt network filter.

History

#1 Updated by Ruben S. Montero over 10 years ago

  • Assignee changed from Ruben S. Montero to Carlos Martín
  • % Done changed from 0 to 60
Branch 261, includes the patches for:
  1. limiting the number of simultaneous VM monitor operations to 5
  2. VM monitoring can be disabled
  3. Host limit is now easier to configure
  4. The first Host monitor operation does not wait for HOST_MONITOR_INTERVAL.
To close the issue:
  1. Complete integration tests with dummy backend
  2. Update documentation for 1.6, reference guide for oned.conf

#2 Updated by Jaime Melis over 10 years ago

  • % Done changed from 60 to 90

Updated documentation. Tested and merged.

To close the issue:

Develop integration tests

#3 Updated by Ruben S. Montero over 10 years ago

  • Status changed from New to Closed
  • Resolution set to fixed

Also available in: Atom PDF