Feature pages are design documents that developers have created while collaborating on oVirt.

Most of them are outdated , but provide historical design context.

They are not user documentation and should not be treated as such.

Documentation is available here.

Host PM Proxy Preferences

Hosts Power Management Proxy Preferences

Summary

The Host Power Management feature allows the oVirt engine to remotely control the host power in order to execute the fencing command as part of the high availability features, or allow the user to manually commit remote operations as PowerOff, PowerOn, and Restart.

Owner

  • Name: Simon Grinberg (MyUser)
  • Email: sgrinber@redhat.com

Current status

The current implementation of the Power Management is focused on supporting the most popular power management device, while the fencing proxy selection is naive, and there is no support for topologies where redundant power supply exists which requires supporting additional power management device.

  • Last updated date: Nov 2, 2012

Detailed Description

When planing the power management feature for the hosts there are few orthogonal aspects to consider

  1. Supported Power Management Devices

  2. Fencing logic, meaning how to determine a host requires fencing.

  3. Power Management logic, meaning when and how to use the power management mechanism to automatically reduce power consumption in the data center

  4. Power Management Proxy Selection

This page is focused at the moment on item #4 and when discussion will go into the other then it will be split into relevant topics.

Power Management Proxy

oVirt uses the standard cluster fence_ script in order to perform power management related operations. These scripts are invoked by VDSM and controlled by the engine. The power management proxy may be any server in the system that has VDSM and fence-agents installed with the proper certificates, even if it is not a host.

Proper proxy selection depends on the networking topology of the data center and user preferences.

Current design assumes any host in the data center may be used for fencing which requires all the hosts to have route to all the fencing devices in the system, in reality out of band management networks are usually confined within the same clusters and sometimes even to specific hosts.

This requires to add the ability to specify, per host, multiple power management devices options in priority. Per option need to specify which device to use and which proxy to use, where there may be multiple proxies with set priorities for using these proxies.

Proxy options may be:

  1. Engine: The server hosting the engine. This requires to install VDSM ( or at least fencing agent) on this host
  2. DC: A host in the same data center
  3. Cluster: A host in the same cluster
  4. IP/FQDN: A specific host defined in the system.
    • Examples:
      • Cluster, Engine
      • fqdn1/ip1,fqdn2/ip2
      • Cluster
      • Cluster, DC

Benefit to oVirt

What is the benefit to the oVirt project? If this is a major capability update, what has changed? If this is a new feature, what capabilities does it bring? Why will oVirt become a better distribution or project because of this feature?

What other packages depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate? Other Features that might get affected by this feature?

Documentation / External references