Here is what i tried[0].
- pin ceph version in ceph-* container to Jewel.
- the clients (nova/gnocchi/cinder) container use ceph Luminous.
I made some test locally with a env: nova + glance + gnocchi + ceph, seems
it works.
[0] https://review.openstack.org/549466
On Tue, Feb 27, 2018 at 12:53
I'm for option 1 definitely. accidental ceph upgrade during routine
minor version upgrade is something we don't want. We will need big
warning about this version mismatch in release notes.
On 26 February 2018 at 07:01, Eduardo Gonzalez wrote:
> I prefer option 1, breaking stable policy is not goo
I prefer option 1, breaking stable policy is not good for users. They will
be forced to upgrade a major ceph version during a minor upgrade, which is
not good and not excepted to be done ever.
Regards
2018-02-26 9:51 GMT+01:00 Shake Chen :
> I prefer to the option 2.
>
> On Mon, Feb 26, 2018 at
I prefer to the option 2.
On Mon, Feb 26, 2018 at 4:39 PM, Jeffrey Zhang
wrote:
> Recently, the Ubuntu jobs on pike branch are red[0]. With some debugging,
> i found it is caused by
> package dependency.
>
>
> *Background*
>
> Since we have no time to upgrade ceph from Jewel to Luminous at the e
Recently, the Ubuntu jobs on pike branch are red[0]. With some debugging, i
found it is caused by
package dependency.
*Background*
Since we have no time to upgrade ceph from Jewel to Luminous at the end of
pike cycle, we pinned
Ceph to Jewel on pike branch. This works on CentOS, because ceph jew