Re: [ceph-users] upgrade procedure to Luminous

2017-07-17 Thread Lars Marowsky-Bree
On 2017-07-14T15:18:54, Sage Weil wrote: > Yes, but how many of those clusters can only upgrade by updating the > packages and rebooting? Our documented procedures have always recommended > upgrading the packages, then restarting either mons or osds first and to > my

Re: [ceph-users] upgrade procedure to Luminous

2017-07-14 Thread Sage Weil
On Fri, 14 Jul 2017, Lars Marowsky-Bree wrote: > On 2017-07-14T14:12:08, Sage Weil wrote: > > > > Any thoughts on how to mitigate this, or on whether I got this all wrong > > > and > > > am missing a crucial detail that blows this wall of text away, please let > > > me > > >

Re: [ceph-users] upgrade procedure to Luminous

2017-07-14 Thread Mike Lowe
It was required for Bobtail to Cuttlefish and Cuttlefish to Dumpling. Exactly how many mons do you have such that you are concerned about failure? If you have let’s say 3 mons, you update all the bits, then it shouldn’t take you more than 2 minutes to restart the mons one by one. You can

Re: [ceph-users] upgrade procedure to Luminous

2017-07-14 Thread Joao Eduardo Luis
On 07/14/2017 03:12 PM, Sage Weil wrote: On Fri, 14 Jul 2017, Joao Eduardo Luis wrote: On top of this all, I found during my tests that any OSD, running luminous prior to the luminous quorum, will need to be restarted before it can properly boot into the cluster. I'm guessing this is a bug

Re: [ceph-users] upgrade procedure to Luminous

2017-07-14 Thread Lars Marowsky-Bree
On 2017-07-14T10:34:35, Mike Lowe wrote: > Having run ceph clusters in production for the past six years and upgrading > from every stable release starting with argonaut to the next, I can honestly > say being careful about order of operations has not been a problem.

Re: [ceph-users] upgrade procedure to Luminous

2017-07-14 Thread Mike Lowe
Having run ceph clusters in production for the past six years and upgrading from every stable release starting with argonaut to the next, I can honestly say being careful about order of operations has not been a problem. > On Jul 14, 2017, at 10:27 AM, Lars Marowsky-Bree wrote:

Re: [ceph-users] upgrade procedure to Luminous

2017-07-14 Thread Lars Marowsky-Bree
On 2017-07-14T14:12:08, Sage Weil wrote: > > Any thoughts on how to mitigate this, or on whether I got this all wrong and > > am missing a crucial detail that blows this wall of text away, please let me > > know. > I don't know; the requirement that mons be upgraded before

Re: [ceph-users] upgrade procedure to Luminous

2017-07-14 Thread Joao Eduardo Luis
On 07/14/2017 03:12 PM, Sage Weil wrote: On Fri, 14 Jul 2017, Joao Eduardo Luis wrote: Dear all, The current upgrade procedure to jewel, as stated by the RC's release notes, You mean (jewel or kraken) -> luminous, I assume... Yeah. *sigh* -Joao

Re: [ceph-users] upgrade procedure to Luminous

2017-07-14 Thread Sage Weil
On Fri, 14 Jul 2017, Joao Eduardo Luis wrote: > Dear all, > > > The current upgrade procedure to jewel, as stated by the RC's release notes, You mean (jewel or kraken) -> luminous, I assume... > can be boiled down to > > - upgrade all monitors first > - upgrade osds only after we have a

[ceph-users] upgrade procedure to Luminous

2017-07-14 Thread Joao Eduardo Luis
Dear all, The current upgrade procedure to jewel, as stated by the RC's release notes, can be boiled down to - upgrade all monitors first - upgrade osds only after we have a **full** quorum, comprised of all the monitors in the monmap, of luminous monitors (i.e., once we have the