1 pve-ha-manager (4.0.1) bookworm; urgency=medium
3 * test, simulator: make it possible to add already running service
5 * lrm: do not migrate via rebalance-on-start if service already running upon
8 * api: fix/add return description for status endpoint
10 * resources: pve: avoid relying on internal configuration details, use new
11 helpers in pve-container and qemu-server
13 -- Proxmox Support Team <support@proxmox.com> Fri, 09 Jun 2023 10:41:06 +0200
15 pve-ha-manager (4.0.0) bookworm; urgency=medium
17 * re-build for Proxmox VE 8 / Debian 12 Bookworm
19 -- Proxmox Support Team <support@proxmox.com> Wed, 24 May 2023 19:26:51 +0200
21 pve-ha-manager (3.6.1) bullseye; urgency=medium
23 * cli: assert that node exist when changing CRS request state to avoid
24 creating a phantom node by mistake
26 * manager: ensure node-request state gets transferred to new active CRM, so
27 that the request for (manual) maintenance mode is upheld, even if the node
28 that is in maintenace mode is also the current active CRM and gets
31 * lrm: ignore shutdown policy if (manual) maintenance mode is requested to
32 avoid exiting from maintenance mode to early.
34 -- Proxmox Support Team <support@proxmox.com> Thu, 20 Apr 2023 14:16:14 +0200
36 pve-ha-manager (3.6.0) bullseye; urgency=medium
38 * fix #4371: add CRM command to switch an online node manually into
39 maintenance (without reboot), moving away all active services, but
40 automatically migrate them back once the maintenance mode is disabled
43 * manager: service start: make EWRONG_NODE a non-fatal error, but try to
44 find its the actual node the service is residing on
46 * manager: add new intermediate 'request_started' state for stop->start
49 * request start: optionally enable automatic selection of the best rated
50 node by the CRS on service start up, bypassing the very high priority of
51 the current node on which a service is located.
53 -- Proxmox Support Team <support@proxmox.com> Mon, 20 Mar 2023 13:38:26 +0100
55 pve-ha-manager (3.5.1) bullseye; urgency=medium
57 * manager: update crs scheduling mode once per round to avoid the need for a
58 restart of the currently active manager.
60 * api: status: add CRS info to manager if not set to default
62 -- Proxmox Support Team <support@proxmox.com> Sat, 19 Nov 2022 15:51:11 +0100
64 pve-ha-manager (3.5.0) bullseye; urgency=medium
66 * env: datacenter config: include crs (cluster-resource-scheduling) setting
68 * manager: use static resource scheduler when configured
70 * manager: avoid scoring nodes if maintenance fallback node is valid
72 * manager: avoid scoring nodes when not trying next and current node is
75 * usage: static: use service count on nodes as a fallback
77 -- Proxmox Support Team <support@proxmox.com> Fri, 18 Nov 2022 15:02:55 +0100
79 pve-ha-manager (3.4.0) bullseye; urgency=medium
81 * switch to native version formatting
83 * fix accounting of online services when moving services due to their source
84 node going gracefully nonoperational (maintenance mode). This ensures a
85 better balance of services on the cluster after such an operation.
87 -- Proxmox Support Team <support@proxmox.com> Fri, 22 Jul 2022 09:21:20 +0200
89 pve-ha-manager (3.3-4) bullseye; urgency=medium
91 * lrm: fix getting stuck on restart due to finished worker state not
94 -- Proxmox Support Team <support@proxmox.com> Wed, 27 Apr 2022 14:01:55 +0200
96 pve-ha-manager (3.3-3) bullseye; urgency=medium
98 * lrm: avoid possible job starvation on huge workloads
100 * lrm: increase run_worker loop-time for doing actually work to 80%
103 -- Proxmox Support Team <support@proxmox.com> Thu, 20 Jan 2022 18:05:33 +0100
105 pve-ha-manager (3.3-2) bullseye; urgency=medium
107 * fix #3826: fix restarting LRM/CRM when triggered by package management
108 system due to other updates
110 * lrm: also check CRM node-status for determining if there's a fence-request
111 and avoid starting up in that case to ensure that the current manager can
112 get our lock and do a clean fence -> unknown -> online FSM transition.
113 This avoids a problematic edge case where an admin manually removed all
114 services of a to-be-fenced node, and re-added them again before the
115 manager could actually get that nodes LRM lock.
117 * manage: handle edge case where a node gets seemingly stuck in 'fence'
118 state if all its services got manually removed by an admin before the
119 fence transition could be finished. While the LRM could come up again in
120 previous versions (it won't now, see above point) and start/stop services
121 got executed, the node was seen as unavailable for all recovery,
122 relocation and migrate actions.
124 -- Proxmox Support Team <support@proxmox.com> Wed, 19 Jan 2022 14:30:15 +0100
126 pve-ha-manager (3.3-1) bullseye; urgency=medium
128 * LRM: release lock and close watchdog if no service configured for >10min
130 * manager: make recovery actual state in finite state machine, showing a
131 clear transition from fence -> reocvery.
133 * fix #3415: never switch in error state on recovery, try to find a new node
134 harder. This improves using the HA manager for services with local
135 resources (e.g., local storage) to ensure it always gets started, which is
136 an OK use-case as long as the service is restricted to a group with only
137 that node. Previously failure of that node would have a high possibility
138 of the service going into the errors state, as no new node can be found.
139 Now it will retry finding a new node, and if one of the restricted set,
140 e.g., the node it was previous on, comes back up, it will start again
143 * recovery: allow disabling a in-recovery service manually
145 -- Proxmox Support Team <support@proxmox.com> Fri, 02 Jul 2021 20:03:29 +0200
147 pve-ha-manager (3.2-2) bullseye; urgency=medium
149 * fix systemd service restart behavior on package upgrade with Debian
152 -- Proxmox Support Team <support@proxmox.com> Mon, 24 May 2021 11:38:42 +0200
154 pve-ha-manager (3.2-1) bullseye; urgency=medium
156 * Re-build for Debian Bullseye / PVE 7
158 -- Proxmox Support Team <support@proxmox.com> Wed, 12 May 2021 20:55:53 +0200
160 pve-ha-manager (3.1-1) pve; urgency=medium
162 * allow 'with-local-disks' migration for replicated guests
164 -- Proxmox Support Team <support@proxmox.com> Mon, 31 Aug 2020 10:52:23 +0200
166 pve-ha-manager (3.0-9) pve; urgency=medium
168 * factor out service configured/delete helpers
170 * typo and grammar fixes
172 -- Proxmox Support Team <support@proxmox.com> Thu, 12 Mar 2020 13:17:36 +0100
174 pve-ha-manager (3.0-8) pve; urgency=medium
176 * bump LRM stop wait time to an hour
178 * do not mark maintenaned nodes as unkown
180 * api/status: extra handling of maintenance mode
182 -- Proxmox Support Team <support@proxmox.com> Mon, 02 Dec 2019 10:33:03 +0100
184 pve-ha-manager (3.0-6) pve; urgency=medium
186 * add 'migrate' node shutdown policy
188 * do simple fallback if node comes back online from maintenance
190 * account service to both, source and target during migration
192 * add 'After' ordering for SSH and pveproxy to LRM service, ensuring the node
193 stays accessible until HA services got moved or shutdown, depending on
196 -- Proxmox Support Team <support@proxmox.com> Tue, 26 Nov 2019 18:03:26 +0100
198 pve-ha-manager (3.0-5) pve; urgency=medium
200 * fix #1339: remove more locks from services IF the node got fenced
202 * adapt to qemu-server code refactoring
204 -- Proxmox Support Team <support@proxmox.com> Wed, 20 Nov 2019 20:12:49 +0100
206 pve-ha-manager (3.0-4) pve; urgency=medium
208 * use PVE::DataCenterConfig from new split-out cluster library package
210 -- Proxmox Support Team <support@proxmox.com> Mon, 18 Nov 2019 12:16:29 +0100
212 pve-ha-manager (3.0-3) pve; urgency=medium
214 * fix #1919, #1920: improve handling zombie (without node) services
216 * fix # 2241: VM resource: allow migration with local device, when not running
218 * HA status: render removal transition of service as 'deleting'
220 * fix #1140: add crm command 'stop', which allows to request immediate
221 service hard-stops if a timeout of zero (0) is passed
223 -- Proxmox Support Team <support@proxmox.com> Mon, 11 Nov 2019 17:04:35 +0100
225 pve-ha-manager (3.0-2) pve; urgency=medium
227 * services: update PIDFile to point directly to /run
229 * fix #2234: fix typo in service description
231 * Add missing Dependencies to pve-ha-simulator
233 -- Proxmox Support Team <support@proxmox.com> Thu, 11 Jul 2019 19:26:03 +0200
235 pve-ha-manager (3.0-1) pve; urgency=medium
237 * handle the case where a node gets fully purged
239 * Re-build for Debian Buster / PVE 6
241 -- Proxmox Support Team <support@proxmox.com> Wed, 22 May 2019 19:11:59 +0200
243 pve-ha-manager (2.0-9) unstable; urgency=medium
245 * get_ha_settings: cope with (temporarily) unavailable pmxcfs
247 * lrm: exit on restart and agent lock lost for > 90s
249 * service data: only set failed_nodes key if needed
251 -- Proxmox Support Team <support@proxmox.com> Thu, 04 Apr 2019 16:27:32 +0200
253 pve-ha-manager (2.0-8) unstable; urgency=medium
255 * address an issue in dpkg 1.18 with wrong trigger cycle detections if cyclic
256 dependencies are involed
258 -- Proxmox Support Team <support@proxmox.com> Wed, 06 Mar 2019 07:49:58 +0100
260 pve-ha-manager (2.0-7) unstable; urgency=medium
262 * fix #1842: do not pass forceStop to CT shutdown
264 * fix #1602: allow one to delete ignored services over API
266 * fix #1891: Add zsh command completion for ha-manager CLI tools
268 * fix #1794: VM resource: catch qmp command exceptions
270 * show sent emails in regression tests
272 -- Proxmox Support Team <support@proxmox.com> Mon, 04 Mar 2019 10:37:25 +0100
274 pve-ha-manager (2.0-6) unstable; urgency=medium
276 * fix #1378: allow one to specify a service shutdown policy
278 * remove some unused external dependencies from the standalone simulator
281 * document api result for ha resources
283 -- Proxmox Support Team <support@proxmox.com> Mon, 07 Jan 2019 12:59:27 +0100
285 pve-ha-manager (2.0-5) unstable; urgency=medium
287 * skip CRM and LRM work if last cfs update failed
289 * regression test system: allow to simulate cluster fs failures
291 * postinst: drop transitional cleanup for systemd watchdog mux socket
293 -- Proxmox Support Team <support@proxmox.com> Wed, 07 Feb 2018 11:00:12 +0100
295 pve-ha-manager (2.0-4) unstable; urgency=medium
297 * address timing issues happening when pve-cluster.service is being restarted
299 -- Proxmox Support Team <support@proxmox.com> Thu, 09 Nov 2017 11:46:50 +0100
301 pve-ha-manager (2.0-3) unstable; urgency=medium
303 * add ignore state for resources
305 * lrm/crm service: restart on API changes
307 * lrm.service: do not timeout on stop
309 * fix #1347: let postfix fill in FQDN in fence mails
311 * fix #1073: do not count backup-suspended VMs as running
313 -- Proxmox Support Team <support@proxmox.com> Fri, 13 Oct 2017 11:10:51 +0200
315 pve-ha-manager (2.0-2) unstable; urgency=medium
317 * explicitly sync journal when disabling watchdog updates
319 * always queue service stop if node shuts down
321 * Fix shutdown order of HA and storage services
323 * Resource/API: abort early if resource in error state
325 -- Proxmox Support Team <support@proxmox.com> Wed, 14 Jun 2017 07:49:59 +0200
327 pve-ha-manager (2.0-1) unstable; urgency=medium
329 * rebuild for PVE 5.0 / Debian Stretch
331 -- Proxmox Support Team <support@proxmox.com> Mon, 13 Mar 2017 11:31:53 +0100
333 pve-ha-manager (1.0-40) unstable; urgency=medium
335 * ha-simulator: allow adding service on runtime
337 * ha-simulator: allow deleting service via GUI
339 * ha-simulator: allow new service request states over gui
341 * ha-simulator: use JSON instead of Dumper for manager status view
343 -- Proxmox Support Team <support@proxmox.com> Tue, 24 Jan 2017 10:03:07 +0100
345 pve-ha-manager (1.0-39) unstable; urgency=medium
347 * add setup_environment hook to CLIHandler class
349 * ha-simulator: fix typo s/Mode/Node/
351 * is_node_shutdown: check for correct systemd targets
353 * Simulator: fix scrolling to end of cluster log view
355 * Simulator: do not use cursor position to insert log
357 -- Proxmox Support Team <support@proxmox.com> Thu, 12 Jan 2017 13:15:08 +0100
359 pve-ha-manager (1.0-38) unstable; urgency=medium
363 -- Proxmox Support Team <support@proxmox.com> Wed, 23 Nov 2016 11:46:21 +0100
365 pve-ha-manager (1.0-37) unstable; urgency=medium
367 * HA::Status: provide better/faster feedback
369 * Manager.pm: store flag to indicate successful start
371 * ha status: include common service attributes
373 * Groups.pm: add verbose_description for 'restricted'
375 * Resources.pm: use verbose_description for state
377 * pve-ha-group-node-list: add verbose_description
379 * ha-manager: remove 'enabled' and 'disabled' commands
381 * rename request state 'enabled' to 'started'
383 * get_pve_lock: correctly send a lock update request
385 -- Proxmox Support Team <support@proxmox.com> Tue, 22 Nov 2016 17:04:57 +0100
387 pve-ha-manager (1.0-36) unstable; urgency=medium
389 * Resources: implement 'stopped' state
391 * ha-manager: remove obsolet pod content
393 * Fix #1189: correct spelling in fence mail
395 * API/Status: avoid using HA Environment
397 * factor out resource config check and default set code
399 -- Proxmox Support Team <support@proxmox.com> Tue, 15 Nov 2016 16:42:07 +0100
401 pve-ha-manager (1.0-35) unstable; urgency=medium
403 * change service state to error if no recovery node is available
405 * cleanup backup & mounted locks after recovery (fixes #1100)
407 * add possibility to simulate locks from services
409 * don't run regression test when building the simulator package
411 -- Proxmox Support Team <support@proxmox.com> Thu, 15 Sep 2016 13:23:00 +0200
413 pve-ha-manager (1.0-34) unstable; urgency=medium
415 * fix race condition on slow resource commands in started state
417 -- Proxmox Support Team <support@proxmox.com> Mon, 12 Sep 2016 13:07:05 +0200
419 pve-ha-manager (1.0-33) unstable; urgency=medium
421 * relocate policy: try to avoid already failed nodes
423 * allow empty json status files
425 * more regression tests
427 -- Proxmox Support Team <support@proxmox.com> Fri, 22 Jul 2016 12:16:48 +0200
429 pve-ha-manager (1.0-32) unstable; urgency=medium
431 * use correct verify function for ha-group-node-list
433 * send email on fence failure and success
435 -- Proxmox Support Team <support@proxmox.com> Wed, 15 Jun 2016 17:01:12 +0200
437 pve-ha-manager (1.0-31) unstable; urgency=medium
439 * selcet_service_node: include all online nodes in default group
441 * LRM: do not count erroneous service as active
443 * fix relocate/restart trial count leak on service deletion
445 -- Proxmox Support Team <support@proxmox.com> Fri, 06 May 2016 08:26:10 +0200
447 pve-ha-manager (1.0-30) unstable; urgency=medium
449 * Env: allow debug logging
451 -- Proxmox Support Team <support@proxmox.com> Fri, 29 Apr 2016 16:50:34 +0200
453 pve-ha-manager (1.0-29) unstable; urgency=medium
455 * Resources: deny setting nonexistent group
457 -- Proxmox Support Team <support@proxmox.com> Wed, 20 Apr 2016 18:22:28 +0200
459 pve-ha-manager (1.0-28) unstable; urgency=medium
461 * Config: add get_service_status method
463 -- Proxmox Support Team <support@proxmox.com> Tue, 19 Apr 2016 08:41:22 +0200
465 pve-ha-manager (1.0-27) unstable; urgency=medium
467 * use pve-doc-generator to generate man pages
469 -- Proxmox Support Team <support@proxmox.com> Fri, 08 Apr 2016 08:25:07 +0200
471 pve-ha-manager (1.0-26) unstable; urgency=medium
473 * status: show added but not yet active services
475 * status: mark CRM as idle if no service is configured
477 -- Proxmox Support Team <support@proxmox.com> Tue, 15 Mar 2016 12:49:18 +0100
479 pve-ha-manager (1.0-25) unstable; urgency=medium
481 * Use config_file from PVE::QemuConfig
483 -- Proxmox Support Team <support@proxmox.com> Tue, 08 Mar 2016 11:50:49 +0100
485 pve-ha-manager (1.0-24) unstable; urgency=medium
487 * simulator: install all virtual resources
489 -- Proxmox Support Team <support@proxmox.com> Wed, 02 Mar 2016 10:30:40 +0100
491 pve-ha-manager (1.0-23) unstable; urgency=medium
493 * fix infinite started <=> migrate cycle
495 * exec_resource_agent: process error state early
497 * avoid out of sync command execution in LRM
499 * do not pass ETRY_AGAIN back to the CRM
501 -- Proxmox Support Team <support@proxmox.com> Wed, 24 Feb 2016 12:15:21 +0100
503 pve-ha-manager (1.0-22) unstable; urgency=medium
505 * fix 'change_service_location' misuse and recovery from fencing
507 * add VirtFail resource and use it in new regression tests
509 * improve relocation policy code in manager and LRM
511 * improve verbosity of API status call
513 -- Proxmox Support Team <support@proxmox.com> Mon, 15 Feb 2016 10:57:44 +0100
515 pve-ha-manager (1.0-21) unstable; urgency=medium
517 * Fix postinstall script not removing watchdog-mux.socket
519 -- Proxmox Support Team <support@proxmox.com> Thu, 04 Feb 2016 18:23:47 +0100
521 pve-ha-manager (1.0-20) unstable; urgency=medium
523 * LRM: do not release lock on shutdown errors
525 * Split up resources and move them to own sub folder
527 * Add virtual resources for tests and simulation
529 * add after_fork method to HA environment and use it in LRM
531 -- Proxmox Support Team <support@proxmox.com> Wed, 27 Jan 2016 17:05:23 +0100
533 pve-ha-manager (1.0-19) unstable; urgency=medium
535 * remove 'running' from migrate/relocate log message
537 * LRM: release agent lock on graceful shutdown
539 * LRM: release agent lock also on restart
541 * CRM: release lock on shutdown request
543 * TestHardware: correct shutdown/reboot behaviour of CRM and LRM
545 * resource agents: fix relocate
547 -- Proxmox Support Team <support@proxmox.com> Mon, 18 Jan 2016 12:41:08 +0100
549 pve-ha-manager (1.0-18) unstable; urgency=medium
551 * pve-ha-lrm.service: depend on lxc.service
553 * output watchdog module name if it gets loaded
555 * remove watchdog-mux.socket
557 -- Proxmox Support Team <support@proxmox.com> Tue, 12 Jan 2016 12:27:49 +0100
559 pve-ha-manager (1.0-17) unstable; urgency=medium
561 * Resources.pm: use PVE::API2::LXC
563 -- Proxmox Support Team <support@proxmox.com> Mon, 11 Jan 2016 12:25:38 +0100
565 pve-ha-manager (1.0-16) unstable; urgency=medium
567 * check_active_workers: fix typo /uuid/uid/
569 -- Proxmox Support Team <support@proxmox.com> Mon, 21 Dec 2015 10:21:30 +0100
571 pve-ha-manager (1.0-15) unstable; urgency=medium
573 * stop all resources on node shutdown (instead of freeze)
575 -- Proxmox Support Team <support@proxmox.com> Wed, 16 Dec 2015 10:33:30 +0100
577 pve-ha-manager (1.0-14) unstable; urgency=medium
579 * allow to configure watchdog module in /etc/default/pve-ha-manager
581 -- Proxmox Support Team <support@proxmox.com> Thu, 03 Dec 2015 11:09:47 +0100
583 pve-ha-manager (1.0-13) unstable; urgency=medium
585 * HA API: Fix permissions
587 -- Proxmox Support Team <support@proxmox.com> Fri, 30 Oct 2015 11:16:50 +0100
589 pve-ha-manager (1.0-12) unstable; urgency=medium
591 * Adding constants to gain more readability
593 * exec_resource_agent: return valid exit code instead of die's
597 -- Proxmox Support Team <support@proxmox.com> Thu, 29 Oct 2015 10:21:49 +0100
599 pve-ha-manager (1.0-11) unstable; urgency=medium
601 * add workaround for bug #775
603 -- Proxmox Support Team <support@proxmox.com> Wed, 21 Oct 2015 08:58:41 +0200
605 pve-ha-manager (1.0-10) unstable; urgency=medium
607 * better resource status check on addition and update
609 -- Proxmox Support Team <support@proxmox.com> Mon, 12 Oct 2015 18:26:24 +0200
611 pve-ha-manager (1.0-9) unstable; urgency=medium
613 * delete node from CRM status when deleted from cluster
615 -- Proxmox Support Team <support@proxmox.com> Tue, 29 Sep 2015 07:35:30 +0200
617 pve-ha-manager (1.0-8) unstable; urgency=medium
619 * Use new lock domain sub instead of storage lock
621 -- Proxmox Support Team <support@proxmox.com> Sat, 26 Sep 2015 10:36:09 +0200
623 pve-ha-manager (1.0-7) unstable; urgency=medium
625 * enhance ha-managers group commands
627 * vm_is_ha_managed: allow check on service state
631 -- Proxmox Support Team <support@proxmox.com> Mon, 21 Sep 2015 12:17:41 +0200
633 pve-ha-manager (1.0-6) unstable; urgency=medium
635 * implement bash completion for ha-manager
637 * implement recovery policy for services
639 * simulator: fix random output of manager status
641 -- Proxmox Support Team <support@proxmox.com> Wed, 16 Sep 2015 12:06:12 +0200
643 pve-ha-manager (1.0-5) unstable; urgency=medium
645 * Replacing hardcoded qemu commands with plugin calls
647 * improve error state behaviour
649 -- Proxmox Support Team <support@proxmox.com> Tue, 08 Sep 2015 08:45:36 +0200
651 pve-ha-manager (1.0-4) unstable; urgency=medium
653 * groups: encode nodes as hash (internally)
655 * add trigger for pve-api-updates
657 -- Proxmox Support Team <support@proxmox.com> Tue, 16 Jun 2015 09:59:03 +0200
659 pve-ha-manager (1.0-3) unstable; urgency=medium
661 * CRM: do not start if there is no resource.cfg file to avoid warnings
663 -- Proxmox Support Team <support@proxmox.com> Tue, 09 Jun 2015 14:35:09 +0200
665 pve-ha-manager (1.0-2) unstable; urgency=medium
667 * use Wants instead of Requires inside systemd service definitions
669 -- Proxmox Support Team <support@proxmox.com> Tue, 09 Jun 2015 09:33:24 +0200
671 pve-ha-manager (1.0-1) unstable; urgency=medium
673 * enable/start crm and lrm services by default
675 -- Proxmox Support Team <support@proxmox.com> Fri, 05 Jun 2015 10:03:53 +0200
677 pve-ha-manager (0.9-3) unstable; urgency=medium
679 * regression test improvements
681 -- Proxmox Support Team <support@proxmox.com> Fri, 10 Apr 2015 06:53:23 +0200
683 pve-ha-manager (0.9-2) unstable; urgency=medium
685 * issue warning if ha group does not exist
687 -- Proxmox Support Team <support@proxmox.com> Tue, 07 Apr 2015 09:52:07 +0200
689 pve-ha-manager (0.9-1) unstable; urgency=medium
691 * rename vm resource prefix: pvevm: => vm:
693 * add API to query ha status
695 * allow to use simply VMIDs as resource id
699 -- Proxmox Support Team <support@proxmox.com> Fri, 03 Apr 2015 06:18:05 +0200
701 pve-ha-manager (0.8-2) unstable; urgency=medium
703 * lrm: reduce TimeoutStopSec to 95
705 * lrm: set systemd killmode to 'process'
707 -- Proxmox Support Team <support@proxmox.com> Thu, 02 Apr 2015 08:48:24 +0200
709 pve-ha-manager (0.8-1) unstable; urgency=medium
711 * currecrtly send cfs lock update request
713 -- Proxmox Support Team <support@proxmox.com> Thu, 02 Apr 2015 08:18:00 +0200
715 pve-ha-manager (0.7-1) unstable; urgency=medium
717 * create /etc/pve/ha automatically
719 * use correct package for lock_ha_config
721 * fix ha-manager status when ha is unconfigured
723 * do not unlink watchdog socket when started via systemd
727 -- Proxmox Support Team <support@proxmox.com> Wed, 01 Apr 2015 11:05:08 +0200
729 pve-ha-manager (0.6-1) unstable; urgency=medium
731 * move configuration handling into PVE::HA::Config
733 * ha-manager status: add --verbose flag
735 * depend on qemu-server
737 -- Proxmox Support Team <support@proxmox.com> Fri, 27 Mar 2015 12:28:50 +0100
739 pve-ha-manager (0.5-1) unstable; urgency=medium
741 * implement service migration
743 * fix service dependencies (allow restart, reboot)
745 * freeze services during reboot/restart
747 -- Proxmox Support Team <support@proxmox.com> Thu, 26 Mar 2015 13:22:58 +0100
749 pve-ha-manager (0.4-1) unstable; urgency=medium
751 * increase fence_delay to 60 seconds
753 * fix regression test environment
755 * fix failover after master crash with pending fence action
757 -- Proxmox Support Team <support@proxmox.com> Wed, 25 Mar 2015 13:59:28 +0100
759 pve-ha-manager (0.3-1) unstable; urgency=medium
761 * really activate softdog
763 * correctly count active services
765 * implement fence_delay to avoid immediate fencing
767 * pve-ha-simulator: reset watchdog with poweroff
769 * pve-ha-simulator: use option nofailback for default groups
771 -- Proxmox Support Team <support@proxmox.com> Mon, 16 Mar 2015 13:03:23 +0100
773 pve-ha-manager (0.2-1) unstable; urgency=medium
775 * add ha-manager command line tool
777 * start implementing resources and groups API
779 -- Proxmox Support Team <support@proxmox.com> Fri, 13 Mar 2015 09:26:12 +0100
781 pve-ha-manager (0.1-1) unstable; urgency=low
785 -- Proxmox Support Team <support@proxmox.com> Wed, 18 Feb 2015 11:30:21 +0100