On Wed, 2017-09-06 at 15:23 +0000, Sage Weil wrote: > Hi everyone, > > Traditionally, we have done a major named "stable" release twice a year, > and every other such release has been an "LTS" release, with fixes > backported for 1-2 years. > > With kraken and luminous we missed our schedule by a lot: instead of > releasing in October and April we released in January and August. > > A few observations: [snip] Firstly, I'd like to qualify my comments by saying that I haven't yet tried Ceph[1], though I have been loosely following its progress. This is partly because I've been busy doing other things. [1] OK, this is a slight fib - I had a very brief play with it a few years back but didn't really get anywhere with it and then got diverted onto other things. Unless I absolutely have to deploy now, I find myself doing this: 10 not long for new release, wait a bit 20 new release is here, but there's talk of a new one 30 goto 10 Having frequent minor updates and fixes is reassuring, but having frequent major update changes with the "L" in "LTS" not being particularly long tends to put me off a bit, largely because I find the thought of upgrading something so mission critical quite daunting. I can't speak from any Ceph experience on this one, obviously, but if there's an easy rollback (even if it's never needed) without having to rebuild the entire cluster then that would make me more willing to do it. -- Cheers, Kingsley. _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |