New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: ceph: add peer spec migration to upgrade doc #8435
docs: ceph: add peer spec migration to upgrade doc #8435
Conversation
* `interval`: frequency of the snapshots. The interval can be specified in days, hours, or minutes using d, h, m suffix respectively. | ||
* `startTime`: optional, determines at what time the snapshot process starts, specified using the ISO 8601 time format. | ||
* `peers`: to configure mirroring peers | ||
* `secretNames`: a list of peers to connect to. Currently (Ceph Octopus release) **only a single** peer is supported where a peer represents a Ceph cluster. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think the (Ceph Octopus release)
sidebar here is particularly useful for users. This only becomes relevant once a Ceph version does support multiple peers.
PendingReleaseNotes.md
Outdated
@@ -40,7 +40,9 @@ So the CephCLuster spec field `image` must be updated to point to quay, like `im | |||
- Add support for Kubernetes TLS secret for referring TLS certs needed for ceph RGW server. | |||
- Stretch clusters are considered stable | |||
- Ceph v16.2.5 or greater is required for stretch clusters | |||
- The use of peer secret names in CephRBDMirror is deprecated. Please use CephBlockPool CR to configure peer secret names and import peers. Checkout the `mirroring` section in the CephBlockPool [spec](Documentation/ceph-pool-crd.md#spec) for more details. | |||
- The use of `peer.secretNames` in `CephRBDMirror` is deprecated. Please use `CephBlockPool`s to |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- The use of `peer.secretNames` in `CephRBDMirror` is deprecated. Please use `CephBlockPool`s to | |
- The use of `peer.secretNames` in `CephRBDMirror` is deprecated. Please use `CephBlockPool` to |
?
Documentation/ceph-upgrade.md
Outdated
|
||
The pre-existing config location in `CephRBDMirror` `spec.peers` will continue to be supported for | ||
this release. Users are required to migrate this setting from `CephRBDMirror` to | ||
relevant `CephBlockPool` resources but may do so any time before upgrading to Rook v1.8. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@leseb I thought we won't be removing the spec.peers
in CephRBDMirror
. Is that not the case now? (asking because we are suggesting it would be removed in the upgrade doc)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, there is no plan to remove it concretely yet. So let's remove that statement for now :) .
This pull request has merge conflicts that must be resolved before it can be merged. @BlaineEXE please rebase it. https://rook.io/docs/rook/master/development-flow.html#updating-your-fork |
@BlaineEXE can we resume this? Thanks |
Add a section to the upgrade doc instructing users to (and how to) migrate `CephRBDMirror` `peers` spec to individual `CephBlockPools`. Adjust the pending release notes to refer to the upgrade section now, and clean up a few references in related docs to make sure users don't miss important documentation. Signed-off-by: Blaine Gardner <blaine.gardner@redhat.com>
d848df8
to
91ec1ac
Compare
The pre-existing config location in `CephRBDMirror` `spec.peers` will continue to be supported, but | ||
users are still encouraged to migrate this setting from `CephRBDMirror` to relevant `CephBlockPool` | ||
resources. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes it is.
ceph rbd mirror doc still suggesting to configure mirror peers. Should we remove that or add a not over there to use ceph block pools instead ? @BlaineEXE |
Remove legacy documentation for configuring RBD mirroring. While we still support legacy mirroring configs, we want to encourage new users to use the CephBlockPool configuration for mirroring. Signed-off-by: Blaine Gardner <blaine.gardner@redhat.com>
@sp98 (and @leseb) I also added a new commit per your recent question/suggestion. If it doesn't sound right, I can easily remove the commit. Remove legacy documentation for configuring RBD mirroring. While we |
docs: ceph: add peer spec migration to upgrade doc (backport #8435)
Add a section to the upgrade doc instructing users to (and how to)
migrate
CephRBDMirror
peers
spec to individualCephBlockPools
.Adjust the pending release notes to refer to the upgrade section now,
and clean up a few references in related docs to make sure users don't
miss important documentation.
Signed-off-by: Blaine Gardner blaine.gardner@redhat.com
Description of your changes:
Which issue is resolved by this Pull Request:
Resolves #
Checklist:
make codegen
) has been run to update object specifications, if necessary.