<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Alexandre,<div class=""><br class=""><div class=""><div><blockquote type="cite" class=""><div class="">Am 14.04.2015 um 08:44 schrieb Alexandre DERUMIER <<a href="mailto:aderumier@odiso.com" class="">aderumier@odiso.com</a>>:</div><br class="Apple-interchange-newline"><div class=""><blockquote type="cite" class=""><blockquote type="cite" class="">Any idea what the upgrade / migration path from the older firefly release might look like? <br class=""></blockquote></blockquote><br class="">I have upgrade my current proxmox cluster (3.4) from firefly->giant->hammer, but firefly->hammer is working too.<br class=""><br class="">It's very simple:<br class=""><br class="">edit<br class="">/etc/apt/sources.list.d/ceph.list<br class=""><br class="">to<br class="">deb <a href="http://ceph.com/debian-hammer" class="">http://ceph.com/debian-hammer</a> wheezy main<br class=""><br class=""><br class="">then on each node:<br class=""><br class="">#apt-get update<br class="">#apt-get dist-upgrade<br class=""><br class="">then on each node:<br class=""><br class="">/etc/init.d/ceph restart mon<br class=""><br class="">then on each node:<br class=""><br class="">/etc/init.d/ceph restart osd<br class=""><br class=""><br class="">(between each restart, check status with #ceph -w)<br class=""></div></blockquote><div><blockquote type="cite" class=""><br class=""></blockquote>Simple indeed. Thanks!<br class=""><blockquote type="cite" class=""><br class="">librbd firefly is working with hammer, but I think for optimal performance, you need to stop/start (or live migrate) vm after librbd update.<br class=""><br class=""><br class=""><blockquote type="cite" class=""><blockquote type="cite" class="">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? <br class=""></blockquote></blockquote><br class="">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.<br class="">I'm not sure how to handle ceph update on the same time. (and hammer jessies packages are not yet available)<br class=""></blockquote></div><div><br class=""></div><div>Understood. It was my misconception anyway, since you have to specify the ceph version upon using pveceph —install. So apt-get upgrade would not force hammer on anyone automatically. ;-)</div><div><br class=""></div><div>While we are at it, the pve-manager package could be updated to allow hammer, though?</div><div><br class=""></div><div>(Note: I was unable to clone the pveceph related stuff from <a href="https://git.proxmox.com" class="">https://git.proxmox.com</a> so I was only able to diff against the versions installed on my system… - pointers welcome!)</div><div><br class=""></div><div>The only hints to ceph versions I found were in pveceph manpage and in pveceph itself (where firefly is the current default).</div><div>If there is nothing else I have missed, both could then be brought up to date:</div><div><br class=""></div><div>diff /usr/share/man/man1/pveceph.1.orig /usr/share/man/man1/pveceph.1<br class="">297c297<br class="">< \& \-version (dumpling | emperor | firefly | giant)<br class="">---<br class="">> \& \-version (dumpling | emperor | firefly | giant | hammer)</div><div><br class=""></div><div>and</div><div><br class=""></div><div>diff /usr/bin/pveceph.orig /usr/bin/pveceph<br class="">90c90<br class="">< <span class="Apple-tab-span" style="white-space:pre"> </span>enum => ['dumpling', 'emperor', 'firefly', 'giant'],<br class="">---<br class="">> <span class="Apple-tab-span" style="white-space:pre"> </span>enum => ['dumpling', 'emperor', 'firefly', 'giant', 'hammer'],<br class=""></div><div><br class=""></div><div>Martin</div></div></div></div></body></html>