<commit_before>---
title: DetailedHostPMProxyPreferences
category: feature
authors: emesika, <NAME>
wiki_category: Feature
wiki_title: Features/Design/DetailedHostPMProxyPreferences
wiki_revision_count: 81
wiki_last_updated: 2014-04-08
wiki_warnings: list-item?
---

# Detailed Host PM Proxy Preferences

## Host Power Management Proxy Preferences

### Summary

When Power Management is defined on the Host and the host becomes non-responding , the engine will attempt to restart the Host after a graceful period is passed
The Host non-responding treatment is doing the following actions
 Send a Stop command

        Wait for status 'off' (controlled by FenceStopStatusDelayBetweenRetriesInSec and FenceStopStatusRetries configuration values)
        Send a Start command
        Wait for status 'on'  (controlled by FenceStartStatusDelayBetweenRetriesInSec and FenceStartStatusRetries configuration values)

The current implementation of PM proxy selection is based on selection of host from the data center with 'UP' status.
 This implementation is not robust enough, since fence action such as 'RestartVds' which is comprised of two fence actions (stop & start) might be able to complete the first action, but fails to detect a proxy for the second. In some cases the entire DC become non-responsive or even stopped. In that case no host on DC could act as a proxy.

This document describes an extension to the current proxy selection algorithm that enables each Host to define its proxy chain as a priority list.

### Owner

*   Feature owner: [ <NAME>](User:emesika)

    * GUI Component owner: [ Eli Mesika](User:emesika)

    * REST Component owner: [ <NAME>ika](User:emesika)

    * Engine Component owner: [ <NAME>ika](User:emesika)

    * QA Owner: [ <NAME>](User:ykaul)

*   Email: <EMAIL>

### Current status

*   Target Release: 3.2
*   Status: Design
*   Last updated date: Nov 4 2012

### Detailed Description

### CRUD<commit_msg>Summary<commit_after>---
title: DetailedHostPMProxyPreferences
category: feature
authors: emesika, <NAME>
wiki_category: Feature
wiki_title: Features/Design/DetailedHostPMProxyPreferences
wiki_revision_count: 81
wiki_last_updated: 2014-04-08
wiki_warnings: list-item?
---

# Detailed Host PM Proxy Preferences

## Host Power Management Proxy Preferences

### Summary

When Power Management is defined on the Host and the host becomes non-responding , the engine will attempt to restart the Host after a graceful period is passed
The Host non-responding treatment is doing the following actions
 Send a Stop command

        Wait for status 'off' (controlled by FenceStopStatusDelayBetweenRetriesInSec and FenceStopStatusRetries configuration values)
        Send a Start command
        Wait for status 'on'  (controlled by FenceStartStatusDelayBetweenRetriesInSec and FenceStartStatusRetries configuration values)

The current implementation of PM proxy selection is based on selection of host from the data center with 'UP' status.
 This implementation is not robust enough, since fence action such as 'RestartVds' which is comprised of two fence actions (stop & start) might be able to complete the first action, but fails to detect a proxy for the second. In some cases the entire DC become non-responsive or even stopped. In that case no host on DC could act as a proxy.

This document describes an extension to the current proxy selection algorithm that enables each Host to define its proxy chain as a priority list.

Specifically, the local host may be chosen as a proxy for fencing operations
This may be achieved by installing a full VDSM packages on the local machine of by using [http://wiki.ovirt.org/wiki/Features/Design/DetailedHostPMProxyPreferences#Local_VDSM Local VDSM](http://wiki.ovirt.org/wiki/Features/Design/DetailedHostPMProxyPreferences#Local_VDSM_Local_VDSM)

### Owner

*   Feature owner: [ <NAME>](User:emesika)

    * GUI Component owner: [ <NAME>](User:emesika)

    * REST Component owner: [ <NAME>](User:emesika)

    * Engine Component owner: [ <NAME>](User:emesika)

    * QA Owner: [ <NAME>](User:ykaul)

*   Email: <EMAIL>

### Current status

*   Target Release: 3.2
*   Status: Design
*   Last updated date: Nov 4 2012

### Detailed Description

### CRUD
{'fraction_non_alphanumeric': 0.06485849056603774, 'fraction_numerical': 0.008018867924528302, 'mean_word_length': 4.6246684350132625, 'pattern_counts': {'":': 0, '<': 16, '<?xml version=': 0, '>': 16, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1212437', 'n_tokens_mistral': 1242, 'n_tokens_neox': 1167, 'n_words': 507}