[pve-devel] ceph hammer : new objetmap features (fast resize, snapshot, ....)

Alexandre DERUMIER aderumier at odiso.com
Tue Apr 14 08:44:03 CEST 2015


>>Any idea what the upgrade / migration path from the older firefly release might look like? 

I have upgrade my current proxmox cluster (3.4) from firefly->giant->hammer, but firefly->hammer is working too.

It's very simple:

edit
/etc/apt/sources.list.d/ceph.list

to
deb http://ceph.com/debian-hammer wheezy main


then on each node:

#apt-get update
#apt-get dist-upgrade

then on each node:

/etc/init.d/ceph restart mon

then on each node:

/etc/init.d/ceph restart osd


(between each restart, check status with #ceph -w)


librbd firefly is working with hammer, but I think for optimal performance, you need to stop/start (or live migrate) vm after librbd update.


>>Does it make sense to tie hammer to a pve version upgrade (say restrict 3.4 to firefly, hammer comes with version 3.5+ / 4.x?) or could firefly be upgraded to hammer on a current pve install? 

Well, for proxmox 4.0, I'm not sure it's the good time to force hammer update, as we'll update to jessie + corosync2, that's already a lot of changes.
I'm not sure how to handle ceph update on the same time. (and hammer jessies packages are not yet available)




----- Mail original -----
De: "Martin Waschbüsch" <service at waschbuesch.it>
À: "pve-devel" <pve-devel at pve.proxmox.com>
Cc: "aderumier" <aderumier at odiso.com>
Envoyé: Mardi 14 Avril 2015 07:41:37
Objet: Re: [pve-devel] ceph hammer : new objetmap features (fast resize, snapshot, ....)

Hi, 

/slightly/ OT w/r to your question, but... 
> Am 14.04.2015 um 07:01 schrieb Alexandre DERUMIER <aderumier at odiso.com>: 
> 
> Hi, 
> 
> Ceph hammer has been released and have a cool new feature called object map 
> https://wiki.ceph.com/Planning/Blueprints/Hammer/librbd%3A_shared_flag%2C_object_map 
> 
> which allow fast resize, snapshots,.... (and also async). 
> 

Any idea what the upgrade / migration path from the older firefly release might look like? 
Does it make sense to tie hammer to a pve version upgrade (say restrict 3.4 to firefly, hammer comes with version 3.5+ / 4.x?) or could firefly be upgraded to hammer on a current pve install? 

E.g. If my current pve cluster uses ceph already, is it feasible to just edit /etc/apt/sources.list.d/ceph.list and switch to hammer by means of an 'aptitude upgrade‘ ? Or will that just lead to a *really* nasty mess? 

Martin 


More information about the pve-devel mailing list