Bug 1388515
| Summary: | [RFE] Enhance backwards compatibility of ceph 2 client against ceph 1.3 server | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | John Fulton <johfulto> |
| Component: | puppet-ceph | Assignee: | John Fulton <johfulto> |
| Status: | CLOSED ERRATA | QA Contact: | Yogev Rabl <yrabl> |
| Severity: | medium | Docs Contact: | Don Domingo <ddomingo> |
| Priority: | medium | ||
| Version: | 11.0 (Ocata) | CC: | ccollett, dbecker, ddomingo, gfidente, jefbrown, jjoyce, johfulto, jomurphy, jschluet, lbopf, mburns, morazi, nlevinki, rhel-osp-director-maint, sclewis, scohen, slinaber, tvignaud, yrabl |
| Target Milestone: | Upstream M3 | Keywords: | FutureFeature, Triaged |
| Target Release: | 11.0 (Ocata) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | puppet-ceph-2.2.1-0.20170116235834.8e01a41.el7ost.noarch.rpm, openstack-tripleo-heat-templates-6.0.0-0.20170120220935.el7ost.noarch.rpm | Doc Type: | Enhancement |
| Doc Text: |
When upgrading or deploying a Red Hat OpenStack Platform environment integrated with an external Ceph Storage Cluster from an earlier version (that is, Red Hat Ceph Storage 1.3), it is necessary to enable backwards compatibility. To do so uncomment the following line in environments/puppet-ceph-external.yaml during upgrade or deployment:
parameter_defaults:
# Uncomment if connecting to a pre-Jewel or RHCS1.3 Ceph Cluster
RbdDefaultFeatures: 1
|
Story Points: | --- |
| Clone Of: | 1385034 | Environment: | |
| Last Closed: | 2017-05-17 19:36:37 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1384079 | ||
| Bug Blocks: | 1387433, 1422742 | ||
|
Description
John Fulton
2016-10-25 14:34:36 UTC
The user may add the following to an environment file to workaround this issue:
parameter_defaults:
ExtraConfig:
ceph::conf::args:
client/rbd_default_features:
value: "1"
However, we prefer to simplify this to the following for OSP11:
parameter_defaults:
ExtraConfig:
ceph::profile::params::rbd_default_features: '1'
Thus, upstream fixes are linked from upstream LP bug 1633552.
If OSP10, then use the following and documentation should be updated to have the user use it. This has been verified.
parameter_defaults:
ExtraConfig:
ceph::conf::args:
client/rbd_default_features:
value: "1"
The target release of this BZ is now OSP11 and by that version, after the upstream fixes linked from upstream LP bug 1633552 are merged, users should be able to pass the following instead.
parameter_defaults:
ExtraConfig:
ceph::profile::params::rbd_default_features: '1'
Thus, I updated the status here from: "Target OSP10 and Verified" to "Target OSP11 and ON_DEV".
Documentation updates will be necessary for both releases. I'll follow up with docs team.
Doc team has triaged for OSP10 as per https://bugzilla.redhat.com/show_bug.cgi?id=1385034#c9 We are limiting the scope of the work for this release to getting a mistral workflow called from Heat. Giulio is making he appropriate changes for this feature. We are limiting the scope of the work for this release to getting a mistral workflow called from Heat. Giulio is making he appropriate changes for this feature. The necessary changes to close this are now upstream. I'll keep an eye on them to help them get downstream. This could make M3. https://review.openstack.org/#/c/283359/ https://review.openstack.org/#/c/420105/ https://review.openstack.org/#/c/420166/ https://review.openstack.org/#/c/386972/ 3/4 of the necessary changes have merged (all in puppet-ceph). Just waiting for the THT change (https://review.openstack.org/#/c/386972/) to merge but it has two +2s so it just needs workflow. Regarding this change for OSP11 vs the one in BZ 1385034 for OSP10. Deployers can still use the option from BZ 1385034 but the changes in this BZ let them do it more easily with just one line and by providing it in the example template with a comment about backwards compatibility it should increase the chances that deployers avoid the problem the first time around. In other words, instead of creating a new env file with the following in OSP10: parameter_defaults: ExtraConfig: ceph::conf::args: client/rbd_default_features: value: "1" They just uncomment the following line in environments/puppet-ceph-external.yaml which will be shipped containing the following in OSP11: parameter_defaults: # Uncomment if connecting to a pre-Jewel or RHCS1.3 Ceph Cluster # RbdDefaultFeatures: 1 All upstream changes have been merged. Moving bug from ON_DEV to POST. I verified that the upstream changes are in the following RPMs: puppet-ceph-2.2.1-0.20170116235834.8e01a41.el7ost.noarch.rpm openstack-tripleo-heat-templates-6.0.0-0.20170120220935.el7ost.noarch.rpm Verified on openstack-tripleo-heat-templates-6.0.0-0.20170127041112.ce54697.el7ost.1.noarch puppet-ceph-2.2.1-0.20170126233654.b1fa5e4.el7ost.noarch Tested on both Ceph 1.3.3 and Ceph 2.0. I set the doctype to enhancement. the doctext looks fine to me. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2017:1245 |