Firstly, congrats Dietmar and the ProxMox team for a wonderful v2.0 release.
Couldn't find Debian Appliance Builder for ProxmoxVE v2.0.
The initial install resulted in:
After:
The updated version now shows:
The indented ones above are newly added / changed.
Is it advisable to / should we / and how do we / remove the older kernel that is still there and not chosen by default in the grub boot menu ?
The Storage now shows a local one being /var/lib/vz for Images, ISOs, VMs, etc. The Backup Job still needs a backup folder in a separate directory in the Storage menu.
Will the backup scripts need any changes to accommodate changes in the hooks to the Backup implementation in v2.0 ?
Couldn't find Debian Appliance Builder for ProxmoxVE v2.0.
The initial install resulted in:
Code:
# pveversion -v
pve-manager: 2.0-54 (pve-manager/2.0/4b59ea39)
running kernel: 2.6.32-10-pve
proxmox-ve-2.6.32: 2.0-63
pve-kernel-2.6.32-10-pve: 2.6.32-63
lvm2: 2.02.88-2pve2
clvm: 2.02.88-2pve2
corosync-pve: 1.4.1-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.8-3
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.7-2
pve-cluster: 1.0-26
qemu-server: 2.0-33
pve-firmware: 1.0-15
libpve-common-perl: 1.0-23
libpve-access-control: 1.0-17
libpve-storage-perl: 2.0-16
vncterm: 1.0-2
vzctl: 3.0.30-2pve2
vzprocps: 2.0.11-2
vzquota: 3.0.12-3
pve-qemu-kvm: 1.0-8
ksm-control-daemon: 1.1-1
After:
Code:
aptitude update
aptitude upgrade
shutdown -r now
The updated version now shows:
Code:
# pveversion -v
pve-manager: 2.0-57 (pve-manager/2.0/ff6cd700)
running kernel: 2.6.32-11-pve
proxmox-ve-2.6.32: 2.0-65
pve-kernel-2.6.32-10-pve: 2.6.32-63
pve-kernel-2.6.32-11-pve: 2.6.32-65
lvm2: 2.02.88-2pve2
clvm: 2.02.88-2pve2
corosync-pve: 1.4.1-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.8-3
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.7-2
pve-cluster: 1.0-26
qemu-server: 2.0-36
pve-firmware: 1.0-15
libpve-common-perl: 1.0-25
libpve-access-control: 1.0-17
libpve-storage-perl: 2.0-17
vncterm: 1.0-2
vzctl: 3.0.30-2pve2
vzprocps: 2.0.11-2
vzquota: 3.0.12-3
pve-qemu-kvm: 1.0-9
ksm-control-daemon: 1.1-1
The indented ones above are newly added / changed.
Is it advisable to / should we / and how do we / remove the older kernel that is still there and not chosen by default in the grub boot menu ?
The Storage now shows a local one being /var/lib/vz for Images, ISOs, VMs, etc. The Backup Job still needs a backup folder in a separate directory in the Storage menu.
Will the backup scripts need any changes to accommodate changes in the hooks to the Backup implementation in v2.0 ?