Dear All,
I've upgraded my 4-node cluster from 3.4 to 4.2. Everything went very well without issues. The minimum downtime of my core vm's like DNS server was about 10 seconds!
In my environment I use xymon for monitoring servers and vm's and I installed the xymon client on each of the proxmox hosts (from the debian repositories). After the upgrade xymon reports from the hosts:
I've upgraded my 4-node cluster from 3.4 to 4.2. Everything went very well without issues. The minimum downtime of my core vm's like DNS server was about 10 seconds!
In my environment I use xymon for monitoring servers and vm's and I installed the xymon client on each of the proxmox hosts (from the debian repositories). After the upgrade xymon reports from the hosts:
Packages not installed from apt repositories (35):
ceph-common (0.80.8-1~bpo70+1)
libbind9-80 (1:9.8.4.dfsg.P1-6+nmu2+deb7u10)
libboost-iostreams1.49.0 (1.49.0-3.2)
libboost-system1.49.0 (1.49.0-3.2)
libboost-thread1.49.0 (1.49.0-3.2)
libconsole (1:0.2.3dbs-70)
libdns88 (1:9.8.4.dfsg.P1-6+nmu2+deb7u10)
libffi5:amd64 (3.0.10-3)
libgcrypt11:amd64 (1.5.0-5+deb7u4)
libgnutls26:amd64 (2.12.20-8+deb7u5)
libicu48:amd64 (4.8.1.1-12+deb7u3)
libisc84 (1:9.8.4.dfsg.P1-6+nmu2+deb7u10)
libisccc80 (1:9.8.4.dfsg.P1-6+nmu2+deb7u10)
libisccfg82 (1:9.8.4.dfsg.P1-6+nmu2+deb7u10)
libiscsi1 (1.9.0-1)
libjpeg8:amd64 (8d-1+deb7u1)
libkadm5clnt-mit8:amd64 (1.10.1+dfsg-5+deb7u7)
libkadm5srv-mit8:amd64 (1.10.1+dfsg-5+deb7u7)
libkdb5-6:amd64 (1.10.1+dfsg-5+deb7u7)
liblwres80 (1:9.8.4.dfsg.P1-6+nmu2+deb7u10)
libmpc2:amd64 (0.9-4)
libopenais3-pve (1.1.4-3)
libparted0debian1:amd64 (2.3-12)
libprocps0:amd64 (1:3.3.3-3)
librados2 (0.80.8-1~bpo70+1)
librbd1 (0.80.8-1~bpo70+1)
librtmp0:amd64 (2.4+20111222.git4e06e21-1)
libtasn1-3:amd64 (2.13-2+deb7u2)
libts-0.0-0:amd64 (1.0-11)
libudev0:amd64 (175-7.2)
python-ceph (0.80.8-1~bpo70+1)
python2.6-minimal (2.6.8-1.1)
tsconf (1.0-11)
vzprocps (2.0.11-2)
vzquota (3.1-2)
I assume that these packages are relicts from Debian weezy, but I'm not sure if it is save to remove them. Can you help me out, maybe by comparing with your systems? To check your system for obsolete packages, just type "aptitude search ~o". This might not reveal all old packages, because some of them seem to be on a higher version number on Debian weezy, e.g. vzquota:ceph-common (0.80.8-1~bpo70+1)
libbind9-80 (1:9.8.4.dfsg.P1-6+nmu2+deb7u10)
libboost-iostreams1.49.0 (1.49.0-3.2)
libboost-system1.49.0 (1.49.0-3.2)
libboost-thread1.49.0 (1.49.0-3.2)
libconsole (1:0.2.3dbs-70)
libdns88 (1:9.8.4.dfsg.P1-6+nmu2+deb7u10)
libffi5:amd64 (3.0.10-3)
libgcrypt11:amd64 (1.5.0-5+deb7u4)
libgnutls26:amd64 (2.12.20-8+deb7u5)
libicu48:amd64 (4.8.1.1-12+deb7u3)
libisc84 (1:9.8.4.dfsg.P1-6+nmu2+deb7u10)
libisccc80 (1:9.8.4.dfsg.P1-6+nmu2+deb7u10)
libisccfg82 (1:9.8.4.dfsg.P1-6+nmu2+deb7u10)
libiscsi1 (1.9.0-1)
libjpeg8:amd64 (8d-1+deb7u1)
libkadm5clnt-mit8:amd64 (1.10.1+dfsg-5+deb7u7)
libkadm5srv-mit8:amd64 (1.10.1+dfsg-5+deb7u7)
libkdb5-6:amd64 (1.10.1+dfsg-5+deb7u7)
liblwres80 (1:9.8.4.dfsg.P1-6+nmu2+deb7u10)
libmpc2:amd64 (0.9-4)
libopenais3-pve (1.1.4-3)
libparted0debian1:amd64 (2.3-12)
libprocps0:amd64 (1:3.3.3-3)
librados2 (0.80.8-1~bpo70+1)
librbd1 (0.80.8-1~bpo70+1)
librtmp0:amd64 (2.4+20111222.git4e06e21-1)
libtasn1-3:amd64 (2.13-2+deb7u2)
libts-0.0-0:amd64 (1.0-11)
libudev0:amd64 (175-7.2)
python-ceph (0.80.8-1~bpo70+1)
python2.6-minimal (2.6.8-1.1)
tsconf (1.0-11)
vzprocps (2.0.11-2)
vzquota (3.1-2)
root@proxmox01:~# apt-cache policy vzquota
vzquota:
Installed: 3.1-2
Candidate: 3.1-2
Version table:
*** 3.1-2 0
100 /var/lib/dpkg/status
3.1-1 0
500 http://ftp.de.debian.org/debian/ jessie/main amd64 Packages
vzquota:
Installed: 3.1-2
Candidate: 3.1-2
Version table:
*** 3.1-2 0
100 /var/lib/dpkg/status
3.1-1 0
500 http://ftp.de.debian.org/debian/ jessie/main amd64 Packages