Updates for Proxmox VE 3.0 - including storage migration

martin · Jun 17, 2013

We just moved a bunch of packages from pvetest to our stable repository, including a lot of bug fixes, code cleanups, qemu 1.4.2 and also a new quite cool new feature - storage migration.

A big Thank-you to our active community for all feedback, testing, bug reporting and patch submissions.

Release Notes

- ceph (0.61.3-1~bpo70+1)

update of ceph-common, librbd1 and librados2

- libpve-storage-perl (3.0-8)

rdb: --format is deprecated, use --image-format instead
be more verebose on rbd commands to get progress
various fixes for nexenta plugin

- vncterm (1.1-4)

Allow to add intermediate certificates to /etc/pve/local/pve-ssl.pem (users previously used apache option SSLCertificateChainFile for that)

- pve-qemu-kvm (1.4-13)

update to qemu 1.4.2
remove rbd-add-an-asynchronous-flush.patch (upstream now)

- qemu-server (3.0-20)

new API to update VM config: this one is fully asynchronous.
snapshot rollback: use pc-i440fx-1.4 as default
config: implement new 'machine' configuration
migrate: pass --machine parameter to remote 'qm start' command
snapshot: store/use 'machine' confifiguration
imlement delete flag for move_disk
API: rename move to move_disk
implement storage migration ("qm move")
fix bug 395: correctly handle unused disk with storage alias
fix unused disk handling (do not hide unused disks when used with snapshot).

- pve-manager (3.0-23)

fix bug #368: use vtype 'DnsName' to verify host names
fix bug #401: disable connection timeout during API call processing
add suport for new qemu-server async configuration API
support 'delete' flag for 'Move disk'
add 'Move disk' button for storage migration

__________________
Best regards,

Martin Maurer
Proxmox VE project leader

lozair · Jun 17, 2013

First, thks for this release !!!

I have a question about storage live migration....

Can i use it to move vm's disks from LVM VolumeGroup to another LVM VolumeGroup ?
We plan to change our storage array which host proxmox kvm vms using shared LVM.
The idea is to mount new LUN from new storage array, create a new VolumeGroup in proxmox and live migrate storage from the old array.

Do you think it's a valid scenario with the new storage migration feature ?

Regards

mir · Jun 17, 2013

Any kvm storage can be migrated to any storage. This includes both shared and unshared storage both online and off-line. One limitation though is, if my initial implementation is used, that a HA enabled VM can only be migrated to shared storage.

ebiss · Jun 18, 2013

Usually I use "aptitude update && aptitude full-upgrade" to update the PVE system.

Now the wiki seem need three step to update PVE:
http://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_3.x_to_latest_3.0
1 apt-get update
2 stop all running VM
3 apt-get dist-upgrade

Which method is recommended ?
Does the step 2 is needed ?

spirit · Jun 18, 2013

ebiss said:
Does the step 2 is needed ?

No .
Only a reboot is needed after kernel update.

tom · Jun 18, 2013

if you update the qemu/kvm package, you need to stop/start your KVM based to use the new version.

if you update the kernel, you need to reboot the host.

bradmc · Jun 19, 2013

Probably a stupid question, but I don't see any storage migration option thru the web interface. Is it command-line only?

tom · Jun 19, 2013

its on the GUI, see screenshot on http://pve.proxmox.com/wiki/Storage_Migration

bradmc · Jun 19, 2013

Thanks! I kept looking for it by right-clicking over the VM on the left-side menu where the "Migrate" option is.

ppo · Jun 21, 2013

During upgrade from 3.0 to the latest 3.x that described here:
http://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_3.x_to_latest_3.0
I got question.
What is the right answer?

Code:

Processing triggers for man-db ...
Processing triggers for install-info ...
Setting up base-files (7.1wheezy1) ...
Installing new version of config file /etc/debian_version ...

Configuration file `/etc/issue'
 ==> Modified (by you or by a script) since installation.
 ==> Package distributor has shipped an updated version.
   What would you like to do about it ?  Your options are:
    Y or I  : install the package maintainer's version
    N or O  : keep your currently-installed version
      D     : show the differences between the versions
      Z     : start a shell to examine the situation
 The default action is to keep your current version.
*** issue (Y/I/N/O/D/Z) [default=N] ?

anthonysomerset · Jun 21, 2013

excellent news re migration, does this mean that i could create a cluster of PVE nodes without shared storage AND be able to do migrations between the nodes? I'm not looking for HA options here, just central management and easy manual migration between pve nodes

mmenaz · Jun 21, 2013

Yes, you can migrate, but of course not "live" migrate, you have to turn off the VM first, then migrate. Btw, since the migrate UI does not ask for destination storage, I guess you can migrate only to target "local" one

spirit · Jun 21, 2013

anthonysomerset said:
excellent news re migration, does this mean that i could create a cluster of PVE nodes without shared storage AND be able to do migrations between the nodes? I'm not looking for HA options here, just central management and easy manual migration between pve nodes

not yet, I'll try to work on this for next proxmox release. (live-migration + storage migration of local storage)

anthonysomerset · Jun 21, 2013

live migration isnt critical for me, but being able to press a few buttons and proxmox does it (offline if neccesary) would be awesome

dietmar · Jun 22, 2013

ppo said:
During upgrade from 3.0 to the latest 3.x that described here:
http://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_3.x_to_latest_3.0
I got question.
What is the right answer?

keep your currently-installed version

mmenaz · Jun 22, 2013

Urgh, I did the opposite (use the new one... isn't an upgrade, anyway?).
Is it a problem (why?)? How to fix?
thanks a lot

tom · Jun 22, 2013

its no problem.

thinputer · Jun 23, 2013

I just downloaded the 3.0 official iso to install in my box, in order to update the latest changes, what should I do? Just sudo apt-get update && sudo apt-get dist-upgrade?
Thank you in advance.

spirit · Jun 23, 2013

thinputer said:
I just downloaded the 3.0 official iso to install in my box, in order to update the latest changes, what should I do? Just sudo apt-get update && sudo apt-get dist-upgrade?
Thank you in advance.

Yes !

eislon · Jun 30, 2013

What is the best way to upgrade an cluster?
I got three nodes, two for KVM and one just for OpenVZ (with migration posibility to the other two nodes)?

Can I upgrade the "linux" only node without any problems?
And then migrate the KVM vm's to the other node --> update empty node --> migrate all vm's to updated node --> update other kvm node?

Updates for Proxmox VE 3.0 - including storage migration

Proxmox Staff Member

Member

Famous Member

Renowned Member

Distinguished Member

Proxmox Staff Member

Member

Proxmox Staff Member

Member

Well-Known Member

Member

Renowned Member

Distinguished Member

Member

Proxmox Staff Member

Renowned Member

Proxmox Staff Member

Renowned Member

Distinguished Member

Active Member