Re: [ceph-users] Changing the release cadence

2019-07-21 Thread Brent Kennedy
12 months sounds good to me, I like the idea of march as well since we plan on doing upgrades in June/July each year. Gives it time to be discussed and marinate before we decide to upgrade. -Brent -Original Message- From: ceph-users On Behalf Of Sage Weil Sent: Wednesday, June 5, 2019 1

Re: [ceph-users] Changing the release cadence

2019-07-18 Thread Konstantin Shalygin
Arch Linux packager for Ceph here o/ I take this opportunity to consider the possibility of the appearance not in Ceph packaging, but Archlinux+Ceph related. Currently with Archlinux packaging impossible to build "Samba CTDB Cluster with CephFS backend". This caused by lack of build options,

Re: [ceph-users] Changing the release cadence

2019-07-15 Thread Sage Weil
On Mon, 15 Jul 2019, Kaleb Keithley wrote: > On Mon, Jul 15, 2019 at 10:10 AM Sage Weil wrote: > > > On Mon, 15 Jul 2019, Kaleb Keithley wrote: > > > > > > If Octopus is really an LTS release like all the others, and you want > > > bleeding edge users to test/use it and give early feedback, then

Re: [ceph-users] Changing the release cadence

2019-07-15 Thread Thore Bödecker
Hey, On 15.07.19 09:58, Kaleb Keithley wrote: > Speaking as (one of) the Ceph packager(s) in Fedora: Arch Linux packager for Ceph here o/ > If Octopus is really an LTS release like all the others, and you want > bleeding edge users to test/use it and give early feedback, then Fedora is > probabl

Re: [ceph-users] Changing the release cadence

2019-07-15 Thread Sage Weil
On Mon, 15 Jul 2019, Kaleb Keithley wrote: > On Wed, Jun 5, 2019 at 11:58 AM Sage Weil wrote: > > > ... > > > > This has mostly worked out well, except that the mimic release received > > less attention that we wanted due to the fact that multiple downstream > > Ceph products (from Red Has and SU

Re: [ceph-users] Changing the release cadence

2019-06-26 Thread Lars Marowsky-Bree
On 2019-06-26T14:45:31, Sage Weil wrote: Hi Sage, I think that makes sense. I'd have preferred the Oct/Nov target, but that'd have made Octopus quite short. Unsure whether freezing in December with a release in March is too long though. But given how much people scramble, setting that as a goal

Re: [ceph-users] Changing the release cadence

2019-06-26 Thread Bob Farrell
March seems sensible to me for the reasons you stated. If a release gets delayed, I'd prefer it to be on the spring side of Christmas (again for the reasons already mentioned). That aside, I'm now very impatient to install Octopus on my 8-node cluster. : ) On Wed, 26 Jun 2019 at 15:46, Sage Weil

Re: [ceph-users] Changing the release cadence

2019-06-26 Thread Sage Weil
Hi everyone, We talked a bit about this during the CLT meeting this morning. How about the following proposal: - Target release date of Mar 1 each year. - Target freeze in Dec. That will allow us to use the holidays to do a lot of testing when the lab infrastructure tends to be somewhat idl

Re: [ceph-users] Changing the release cadence

2019-06-26 Thread Sage Weil
On Wed, 26 Jun 2019, Alfonso Martinez Hidalgo wrote: > I think March is a good idea. Spring had a slight edge over fall in the twitter poll (for whatever that's worth). I see the appeal for fall when it comes to down time for retailers, but as a practical matter for Octopus specifically, a tar

Re: [ceph-users] Changing the release cadence

2019-06-26 Thread Sage Weil
On Tue, 25 Jun 2019, Alfredo Deza wrote: > On Mon, Jun 17, 2019 at 4:09 PM David Turner wrote: > > > > This was a little long to respond with on Twitter, so I thought I'd share > > my thoughts here. I love the idea of a 12 month cadence. I like October > > because admins aren't upgrading product

Re: [ceph-users] Changing the release cadence

2019-06-25 Thread Alfredo Deza
On Mon, Jun 17, 2019 at 4:09 PM David Turner wrote: > > This was a little long to respond with on Twitter, so I thought I'd share my > thoughts here. I love the idea of a 12 month cadence. I like October because > admins aren't upgrading production within the first few months of a new > release

Re: [ceph-users] Changing the release cadence

2019-06-17 Thread Daniel Baumann
Hi, I didn't bother to create a twitter account just to be able to participate in the poll.. so.. please count me in for October. Regards, Daniel ___ ceph-users mailing list ceph-users@lists.ceph.com http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.co

Re: [ceph-users] Changing the release cadence

2019-06-17 Thread David Turner
This was a little long to respond with on Twitter, so I thought I'd share my thoughts here. I love the idea of a 12 month cadence. I like October because admins aren't upgrading production within the first few months of a new release. It gives it plenty of time to be stable for the OS distros as we

Re: [ceph-users] Changing the release cadence

2019-06-17 Thread Sage Weil
On Wed, 5 Jun 2019, Sage Weil wrote: > That brings us to an important decision: what time of year should we > release? Once we pick the timing, we'll be releasing at that time *every > year* for each release (barring another schedule shift, which we want to > avoid), so let's choose carefully!

Re: [ceph-users] Changing the release cadence

2019-06-06 Thread Daniel Baumann
On 6/6/19 9:26 AM, Xiaoxi Chen wrote: > I will vote for November for several reasons: [...] as an academic institution we're aligned by August to July (school year) instead of the January to December (calendar year), so all your reasons (thanks!) are valid for us.. just shifted by 6 months, hence

Re: [ceph-users] Changing the release cadence

2019-06-06 Thread Xiaoxi Chen
We go with upstream release and mostly Nautilus now, probably the most aggressive ones among serious production user (i.e tens of PB+ ), I will vote for November for several reasons: 1. Q4 is holiday season and usually production rollout was blocked , especially storage related change, which u

Re: [ceph-users] Changing the release cadence

2019-06-05 Thread Dietmar Rieder
+1 Operators view: 12 months cycle is definitely better than 9. March seem to be a reasonable compromise. Best Dietmar On 6/6/19 2:31 AM, Linh Vu wrote: > I think 12 months cycle is much better from the cluster operations > perspective. I also like March as a release month as well.  > -

Re: [ceph-users] Changing the release cadence

2019-06-05 Thread Linh Vu
I think 12 months cycle is much better from the cluster operations perspective. I also like March as a release month as well. From: ceph-users on behalf of Sage Weil Sent: Thursday, 6 June 2019 1:57 AM To: ceph-us...@ceph.com; ceph-de...@vger.kernel.org; d...@ce

Re: [ceph-users] Changing the release cadence

2019-06-05 Thread Chris Taylor
It seems like since the change to the 9 months cadence it has been bumpy for the Debian based installs. Changing to a 12 month cadence sounds like a good idea. Perhaps some Debian maintainers can suggest a good month for them to get the packages in time for their release cycle. On 2019-06-0

Re: [ceph-users] Changing the release cadence

2019-06-05 Thread Alexandre DERUMIER
Hi, >>- November: If we release Octopus 9 months from the Nautilus release >>(planned for Feb, released in Mar) then we'd target this November. We >>could shift to a 12 months candence after that. For the 2 last debian releases, the freeze was around january-february, november seem to be a go

Re: [ceph-users] Changing the release cadence

2019-06-05 Thread Daniel Baumann
On 6/5/19 5:57 PM, Sage Weil wrote: > So far the balance of opinion seems to favor a shift to a 12 month > cycle [...] it seems pretty likely we'll make that shift. thanks, much appreciated (from an cluster operating point of view). > Thoughts? GNOME and a few others are doing April and October