projects / corosync-pve.git / blame
| Commit | Line | Data |
|---|---|---|
| 8a4032e5 TL |
1 | corosync (3.0.2-pve4) pve; urgency=medium |
| 2 | ||
| 3 | * backport a fix ensuring that the messages during recovery (retransmission) | |
| 4 | do not exceed the maximum possible KNET package size. | |
| 5 | ||
| 6 | -- Proxmox Support Team <support@proxmox.com> Thu, 10 Oct 2019 18:16:02 +0200 | |
| 7 | ||
| 6282e6ca TL |
8 | corosync (3.0.2-pve3) pve; urgency=medium |
| 9 | ||
| 10 | * totemknet: Disable forwarding on shutdown to make knet flush all messages | |
| 11 | (especially LEAVE one) | |
| 12 | ||
| 13 | * totemknet: Add locking for log call to ensure no log message is lost from | |
| 14 | different threads | |
| 15 | ||
| 16 | * totempg: Check sanity (length) of received message | |
| 17 | ||
| 18 | -- Proxmox Support Team <support@proxmox.com> Thu, 03 Oct 2019 16:13:54 +0200 | |
| 19 | ||
| fa960e0c TL |
20 | corosync (3.0.2-pve2) pve; urgency=medium |
| 21 | ||
| 22 | * cherry pick totem config patches to improve compatibillity with setups | |
| 23 | without a (currently) configured link0 | |
| 24 | ||
| 25 | -- Proxmox Support Team <support@proxmox.com> Fri, 21 Jun 2019 14:26:28 +0200 | |
| 26 | ||
| 4e762dd4 FG |
27 | corosync (3.0.2-pve1) pve; urgency=medium |
| 28 | ||
| 29 | * update to Corosync 3.0.2 | |
| 30 | ||
| 31 | -- Proxmox Support Team <support@proxmox.com> Wed, 19 Jun 2019 13:47:17 +0200 | |
| 32 | ||
| 06d5370e FG |
33 | corosync (3.0.1-pve1) pve; urgency=medium |
| 34 | ||
| 35 | * update to Corosync 3.0.1-2 | |
| 36 | ||
| 37 | * cherry-pick crypto changes for upgrade compatibility | |
| 38 | ||
| 39 | * cherry-pick CPG callback joinlist merging (PR 468) | |
| 40 | ||
| 41 | * drop transitional corosync-pve/libcorosync4-pve packages | |
| 42 | ||
| 43 | * corosync-qdevice/corosync-qnetd are now shipped separately | |
| 44 | ||
| 45 | * drop discontinued libtotem-pq library packages | |
| 46 | ||
| 47 | -- Proxmox Support Team <support@proxmox.com> Wed, 22 May 2019 12:40:27 +0200 | |
| 48 | ||
| 459f4daa FG |
49 | corosync (2.4.4-pve1) unstable; urgency=medium |
| 50 | ||
| 51 | * update to corosync 2.4.4 | |
| 52 | ||
| 53 | -- Proxmox Support Team <support@proxmox.com> Wed, 24 Oct 2018 12:48:36 +0200 | |
| 54 | ||
| 013929b6 TL |
55 | corosync (2.4.2-pve5) unstable; urgency=medium |
| 56 | ||
| 57 | * cpg: Inform clients about left nodes during pause | |
| 58 | ||
| 59 | -- Proxmox Support Team <support@proxmox.com> Wed, 25 Apr 2018 10:26:48 +0200 | |
| 60 | ||
| c01206f1 FG |
61 | corosync (2.4.2-pve4) unstable; urgency=medium |
| 62 | ||
| 63 | * fix CVE-2018-1084 | |
| 64 | ||
| 65 | -- Proxmox Support Team <support@proxmox.com> Fri, 13 Apr 2018 10:29:34 +0200 | |
| 66 | ||
| e4647070 FG |
67 | corosync (2.4.2-pve3) unstable; urgency=medium |
| 68 | ||
| 69 | * don't install corosync-qdevice init script | |
| 70 | ||
| 71 | -- Proxmox Support Team <support@proxmox.com> Thu, 8 Jun 2017 14:13:22 +0200 | |
| 72 | ||
| 3dbd0db6 FG |
73 | corosync (2.4.2-pve2) unstable; urgency=medium |
| 74 | ||
| 75 | * add libcorosync4-pve transitional package | |
| 76 | ||
| 77 | * only start corosync service if config exists | |
| 78 | ||
| 79 | -- Proxmox Support Team <support@proxmox.com> Mon, 13 Mar 2017 13:31:34 +0100 | |
| 80 | ||
| bcf18111 FG |
81 | corosync (2.4.2-pve1) unstable; urgency=medium |
| 82 | ||
| 83 | * switch to Debian's corosync package as base | |
| 84 | ||
| 85 | -- Proxmox Support Team <support@proxmox.com> Wed, 8 Mar 2017 14:16:58 +0100 | |
| 86 | ||
| 6f6e3e0d FG |
87 | corosync-pve (2.4.2-2) unstable; urgency=medium |
| 88 | ||
| 89 | * rebuild for PVE 5.0 / Debian Stretch | |
| 90 | ||
| 91 | -- Proxmox Support Team <support@proxmox.com> Mon, 6 Mar 2017 09:30:57 +0100 | |
| 92 | ||
| 63916ea1 TL |
93 | corosync-pve (2.4.2-1) unstable; urgency=medium |
| 94 | ||
| 95 | * update to corosync 2.4.2 | |
| 96 | ||
| 97 | -- Proxmox Support Team <support@proxmox.com> Wed, 08 Feb 2017 14:08:49 +0100 | |
| 98 | ||
| 275a2fbe DM |
99 | corosync-pve (2.4.0-1) unstable; urgency=medium |
| 100 | ||
| 101 | * update to v2.4.0 | |
| 102 | ||
| 103 | -- Proxmox Support Team <support@proxmox.com> Sat, 16 Jul 2016 10:27:49 +0200 | |
| 104 | ||
| df03257c DM |
105 | corosync-pve (2.3.5-2) unstable; urgency=medium |
| 106 | ||
| 107 | * update to latest versions from branch needle | |
| 108 | (commit e2b6b25126a3e8f2caefcb8ccde67788c63fbeb5) | |
| 109 | ||
| 110 | * remove patch 0001-totem-swap-unicast-and-multicast-bind-order.patch (upstream) | |
| 111 | ||
| 112 | -- Proxmox Support Team <support@proxmox.com> Thu, 03 Dec 2015 14:49:43 +0100 | |
| 113 | ||
| 0a8764f4 DM |
114 | corosync-pve (2.3.5-1) unstable; urgency=medium |
| 115 | ||
| 116 | * update to v2.3.5 | |
| 117 | ||
| 118 | -- Proxmox Support Team <support@proxmox.com> Mon, 21 Sep 2015 12:02:49 +0200 | |
| 119 | ||
| d05fb358 DM |
120 | corosync-pve (2.3.4-2) unstable; urgency=medium |
| 121 | ||
| 122 | * update to latest upstream (commit 82526d2fe9137e8b604f1bbae6d6e39ba41377f9) | |
| 123 | ||
| 124 | -- Proxmox Support Team <support@proxmox.com> Mon, 30 Mar 2015 19:10:35 +0200 | |
| 125 | ||
| 013101f0 DM |
126 | corosync-pve (2.3.4-1) unstable; urgency=medium |
| 127 | ||
| 128 | * update to 2.3.4 | |
| 129 | ||
| 130 | * recompile for Debian Jessie | |
| 131 | ||
| 132 | -- Proxmox Support Team <support@proxmox.com> Mon, 23 Feb 2015 08:20:52 +0100 | |
| 133 | ||
| 0320eacf DM |
134 | corosync-pve (1.4.7-1) unstable; urgency=low |
| 135 | ||
| 136 | * update to 1.4.7 | |
| 137 | ||
| 138 | -- Proxmox Support Team <support@proxmox.com> Tue, 22 Jul 2014 06:17:13 +0200 | |
| 139 | ||
| 728d91c3 DM |
140 | corosync-pve (1.4.6-1) unstable; urgency=low |
| 141 | ||
| 142 | * update to 1.4.6 | |
| 143 | ||
| 144 | -- Proxmox Support Team <support@proxmox.com> Fri, 09 May 2014 07:14:06 +0200 | |
| 145 | ||
| 1d458e36 DM |
146 | corosync-pve (1.4.5-1) unstable; urgency=low |
| 147 | ||
| 148 | * update to 1.4.5 | |
| 149 | ||
| 150 | -- Proxmox Support Team <support@proxmox.com> Fri, 15 Mar 2013 06:35:02 +0100 | |
| 151 | ||
| af5eee0c DM |
152 | corosync-pve (1.4.4-3) unstable; urgency=low |
| 153 | ||
| 154 | * run at high priority using setpriority(-20) | |
| 155 | ||
| 156 | -- Proxmox Support Team <support@proxmox.com> Tue, 15 Jan 2013 12:54:02 +0100 | |
| 157 | ||
| e0a6828c DM |
158 | corosync-pve (1.4.4-2) unstable; urgency=low |
| 159 | ||
| 160 | * disable SCHED_RR (RT_GROUP_SCHED was disabled in our kernel | |
| 161 | anyways). In newer kernels this is enabled, but causes corosync to | |
| 162 | crash. | |
| 163 | ||
| 164 | -- Proxmox Support Team <support@proxmox.com> Fri, 11 Jan 2013 15:39:40 +0100 | |
| 165 | ||
| deb86d56 DM |
166 | corosync-pve (1.4.4-1) unstable; urgency=low |
| 167 | ||
| 168 | * update to 1.4.4 | |
| 169 | ||
| 170 | -- Proxmox Support Team <support@proxmox.com> Tue, 02 Oct 2012 09:41:59 +0200 | |
| 171 | ||
| aeb347a9 DM |
172 | corosync-pve (1.4.3-1) unstable; urgency=low |
| 173 | ||
| 174 | * update to 1.4.3 | |
| 175 | ||
| 176 | -- Proxmox Support Team <support@proxmox.com> Thu, 12 Apr 2012 12:54:10 +0200 | |
| 177 | ||
| 930e051d DM |
178 | corosync-pve (1.4.1-1) unstable; urgency=low |
| 179 | ||
| 180 | * update to 1.4.1 | |
| 181 | ||
| 182 | -- Proxmox Support Team <support@proxmox.com> Tue, 26 Jul 2011 11:49:17 +0200 | |
| 183 | ||
| 184 | corosync-pve (1.4.0-1) unstable; urgency=low | |
| 185 | ||
| 186 | * update to 1.4.0 | |
| 187 | ||
| 188 | * remove fix-schedrr-warning.patch (alread in 1.4.0) | |
| 189 | ||
| 190 | -- Proxmox Support Team <support@proxmox.com> Tue, 19 Jul 2011 12:36:54 +0200 | |
| 191 | ||
| 192 | corosync-pve (1.3.1-1) unstable; urgency=low | |
| 193 | ||
| 194 | * update to latest stable | |
| 195 | ||
| 196 | -- Proxmox Support Team <support@proxmox.com> Thu, 23 Jun 2011 06:52:20 +0200 | |
| 197 | ||
| 198 | corosync-pve (1.3.0-1) unstable; urgency=low | |
| 199 | ||
| 200 | * update to latest stable | |
| 201 | ||
| 202 | -- Proxmox Support Team <support@proxmox.com> Thu, 02 Dec 2010 07:11:10 +0100 | |
| 203 | ||
| 204 | corosync-pve (1.2.8-1) unstable; urgency=low | |
| 205 | ||
| 206 | * update to latest stable | |
| 207 | ||
| 208 | -- Proxmox Support Team <support@proxmox.com> Wed, 06 Oct 2010 13:24:24 +0200 | |
| 209 | ||
| 210 | corosync-pve (1.2.0-1) unstable; urgency=low | |
| 211 | ||
| 212 | * add patches/cpg-join-fix.diff, see | |
| 213 | https://bugzilla.redhat.com/show_bug.cgi?id=568356 | |
| 214 | ||
| 215 | * update to latest stable | |
| 216 | ||
| 217 | * do not create/installe /etc/corosync/* - we use cman instead | |
| 218 | ||
| 219 | * delete init.d script - we use cman instead | |
| 220 | ||
| 221 | -- Proxmox Support Team <support@proxmox.com> Thu, 21 Jan 2010 13:50:43 +0100 | |
| 222 | ||
| 223 | corosync-pve (1.1.2-1) unstable; urgency=low | |
| 224 | ||
| 225 | * update to latest stable | |
| 226 | ||
| 227 | -- Proxmox Support Team <support@proxmox.com> Fri, 23 Oct 2009 11:41:04 +0200 | |
| 228 | ||
| 229 | corosync-pve (1.1.1-1) unstable; urgency=low | |
| 230 | ||
| 231 | * update to latest stable | |
| 232 | ||
| 233 | -- Proxmox Support Team <support@proxmox.com> Thu, 22 Oct 2009 12:46:53 +0200 | |
| 234 | ||
| 235 | corosync-pve (1.0-1) unstable; urgency=low | |
| 236 | ||
| 237 | * update to latest trunc | |
| 238 | ||
| 239 | * use quilt instead of dpatch | |
| 240 | ||
| 241 | * use /dev/urandom instead of /dev/random for key generation | |
| 242 | ||
| 243 | * new config file localtion: /etc/corosync/corosync.conf | |
| 244 | ||
| 245 | * new key location: /etc/corosync/authkey | |
| 246 | ||
| 247 | * new default configuration: secauth = on | |
| 248 | ||
| 249 | * auto-generate authkey in postinst script if it does not exist | |
| 250 | ||
| 251 | -- Proxmox Support Team <support@proxmox.com> Mon, 08 Jun 2009 03:28:34 -0400 | |
| 252 | ||
| 253 | corosync-pve (0.95-1) unstable; urgency=low | |
| 254 | ||
| 255 | * update to 0.95 | |
| 256 | ||
| 257 | -- Proxmox Support Team <support@proxmox.com> Wed, 01 Apr 2009 10:07:13 -0400 | |
| 258 | ||
| 259 | corosync-pve (0.94-1) unstable; urgency=low | |
| 260 | ||
| 261 | * Initial release. | |
| 262 | ||
| 263 | -- Proxmox Support Team <support@proxmox.com> Mon, 30 Mar 2009 06:55:24 -0400 | |
| 264 |